A rollback method and device based on hierarchical release

Abstract

An embodiment of the present invention provides a rollback method and device based on hierarchical release, wherein the method includes: determining at least one area that needs to be rolled back in multiple areas; wherein each area includes at least one cluster, and the cluster includes at least one server; determining the priority of each area in the at least one area; and performing a rollback operation on the system of servers in each area according to the priority of each area in the at least one area. In the embodiment provided by the present invention, before performing the rollback operation, at least one area that needs to be rolled back is determined in multiple areas, instead of rolling back all areas, thereby increasing the rollback efficiency. In addition, during the rollback process, according to the priority of each area in the at least one area, the rollback is performed in the reverse hierarchical release order, thereby improving the stop-loss efficiency of the rollback.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer technology, and in particular to a rollback method and device based on hierarchical release. Background Art

[0002] The operation and maintenance system is an important component of the company's operation and maintenance platform. It is responsible for ensuring that all systems in the company can operate normally. Among them, the deployment system is a very important function in the operation and maintenance system. Operation and maintenance personnel upgrade and update services through the deployment system. In the traditional deployment system process, the rollback stop loss efficiency is low and the time is long, which is a problem that needs to be solved urgently. Summary of the invention

[0003] The embodiment of the present invention provides a rollback method and device based on hierarchical release, which are used to solve the problems of low loss-stopping efficiency and long time in rollback of a traditional deployment system.

[0004] In a first aspect, an embodiment of the present invention provides a rollback method based on hierarchical release, the method comprising: determining at least one area that needs to be rolled back among multiple areas; wherein each area includes at least one cluster, and the cluster includes at least one server; determining the priority of each area in the at least one area; and performing a rollback operation on the system of the server in each area according to the priority of each area in the at least one area.

[0005] Optionally, determining at least one region that needs to be rolled back among the multiple regions includes:

[0006] For any area among the multiple areas, if the server in the area was not online before the version of the system was updated, or the system of the server in the area was not updated to the latest version, it is determined that the area does not need to be rolled back; and the areas among the multiple areas except the areas that do not need to be rolled back are determined as at least one area that needs to be rolled back.

[0007] Optionally, determining the priority of each area in the at least one area includes:

[0008] For any one of the at least one areas, the priority of the area is determined according to the environment corresponding to the system in the server in the area; wherein, when the environment corresponding to the system in the server in the area is a test environment, the priority of the area is the lowest; and when the environment corresponding to the system in the server in the area is a production environment, the priority of the area is the highest.

[0009] Optionally, performing a rollback operation on a system of a server in each area of ​​the at least one area according to a priority of each area includes: performing a rollback operation on a system of a server in each area of ​​the at least one area in order of priority from high to low.

[0010] Optionally, the method further includes: for any one of the at least one areas, in the area, performing a rollback operation on the system of the servers within the cluster according to the cluster granularity; wherein, after the system rollback of the servers within each cluster is completed, skipping the step of performing a service check on the system.

[0011] Optionally, the method further includes: for any server in the at least one area, before performing a rollback operation on the server, determining whether an installation file required to perform a rollback operation exists in the server; if the installation file exists, implementing the rollback operation through the installation file.

[0012] Optionally, if the installation file does not exist, the installation file is downloaded according to the obtained download address; and the rollback operation is implemented through the downloaded installation file.

[0013] Optionally, determining whether the server has the installation file required to perform the rollback operation includes: obtaining a rollback instruction, the rollback instruction being used to instruct the server to perform the rollback operation, the rollback instruction including a file identifier of the installation file; if the server includes a file corresponding to the file identifier, determining that the installation file exists in the server; if the server does not include the file corresponding to the file identifier, determining that the installation file does not exist in the server.

[0014] In a second aspect, an embodiment of the present invention provides a rollback device based on hierarchical release, including:

[0015] A processing unit, configured to determine at least one region that needs to be rolled back among multiple regions; wherein each region includes at least one cluster, and the cluster includes at least one server;

[0016] The rollback unit is used to determine the priority of each area in the at least one area; according to the priority of each area in the at least one area, perform a rollback operation on the system of the server in each area.

[0017] In a third aspect, an embodiment of the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method provided in the first aspect when executing the program.

[0018] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the storage medium stores computer instructions. When the computer instructions are executed by a processor, the method provided in the first aspect is executed.

[0019] In a fifth aspect, an embodiment of the present invention further provides a computer program product, comprising computer executable instructions, wherein the computer executable instructions are used to enable a computer to execute the method provided in the first aspect.

[0020] Through the technical solutions in one or more of the above embodiments of the embodiments of the present invention, the embodiments of the present invention have at least the following technical effects:

[0021] In the embodiment provided by the present invention, before executing the rollback operation, at least one region that needs to be rolled back is determined among multiple regions, instead of rolling back all regions, thereby increasing the rollback efficiency. In addition, during the rollback process, according to the priority of each region in the at least one region, the rollback is performed in a reverse hierarchical release order, thereby increasing the stop-loss efficiency of the rollback. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0023] Figure 1 A schematic diagram of a network architecture provided by an embodiment of the present invention;

[0024] Figure 2 A schematic diagram of a rollback method based on hierarchical release provided in an embodiment of the present invention;

[0025] Figure 3 A schematic diagram of a method flow chart provided by an embodiment of the present invention;

[0026] Figure 4 A schematic diagram of a flow chart of an inspection method provided by an embodiment of the present invention;

[0027] Figure 5 A schematic diagram of a rollback method flow chart provided by an embodiment of the present invention;

[0028] Figure 6 A schematic diagram of the structure of a rollback device based on hierarchical release provided by an embodiment of the present invention;

[0029] Figure 7 A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose, technical solution and beneficial effects of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0031] For ease of understanding, the terms involved in the embodiments of the present invention are explained below.

[0032] Gradual release, also known as grayscale release, generally refers to the process of gradually expanding the traffic of software products during the iteration process. Each grading will be accompanied by certain data indicator analysis to decide whether to roll back or continue to expand the grayscale. In the process of graded release, some users can continue to use the original software version, and some users can start using the new software version. If there are no problems with the new software version, then gradually expand the scope and let all users use the new software version. This can ensure the stability of the overall system, and problems can be discovered and adjusted during the initial grayscale to ensure their impact.

[0033] Rollback refers to the act of restoring a program or data to its previous state, or it can refer to the act of restoring a system to its previous version. Rollback includes program rollback and data rollback.

[0034] Testing environment (testing): Generally, it is to clone the configuration of the production environment. If a program does not work properly in the testing environment, it must not be released to the production machine. After the programmer develops the system, it is handed over to the testing department for comprehensive testing to check whether there are any errors in the implemented functions. The testers will simulate various operating conditions for testing.

[0035] Production environment (production): refers to the environment that officially provides external services. Generally, error reporting is turned off and error logging is turned on. The production environment is the online environment that is released to the external environment and officially provided to users.

[0036] A cluster is a group of independent servers that appear as a single system on a network and are connected by a loosely integrated set of computer software or hardware to complete work.

[0037] refer to Figure 1 , which is a network architecture diagram applicable to an embodiment of the present invention, the network architecture includes multiple areas, each area includes at least one cluster, and each cluster includes at least one server. Figure 1In the description, two regions are used as an example, and each region includes two clusters. In actual applications, the number of regions is not limited, and the number of clusters included in the region is not limited. The network architecture may also include a management device, which may be a separate device or a server.

[0038] In the embodiment of the present invention, the division of regions is not fixed, and multiple clusters can be divided into different regions according to actual conditions.

[0039] In the embodiment of the present invention, when the system in the server is upgraded, the upgrade can be performed based on a hierarchical release method. Specifically, the system version upgrade can include multiple stages. During the version upgrade process, a version upgrade area can be added in each stage, so that the scope of the version upgrade is gradually expanded, so that all areas are upgraded to the new version.

[0040] For example, in an embodiment of the present invention, a system that is released and deployed online in stages may go through the following environments in sequence: a test environment, a regression environment, a pre-release environment, and a production environment.

[0041] Then the system version upgrade can include four stages: the first stage, the version corresponding to the test service; the second stage, the version corresponding to the regression service; the third stage, the version corresponding to the pre-release service; the fourth stage, the version corresponding to the online service.

[0042] In the first stage, the system version of the server in one area can be upgraded; in the second stage, the system version of the server in at least two areas can be upgraded, and so on until the fourth stage.

[0043] In the embodiment of the present invention, when an error occurs in the version upgrade, the system in the server can be rolled back to the version before the test service, that is, to a version before the current latest version.

[0044] like Figure 2 As shown, it is a schematic diagram of a rollback method based on hierarchical release provided by an embodiment of the present invention. The method can be applied to Figure 1 In the illustrated architecture, the method includes:

[0045] S201: Determine at least one region that needs to be rolled back among multiple regions.

[0046] Each region includes at least one cluster, and the cluster includes at least one server. The versions of the systems deployed in the servers in each region are the same.

[0047] Specifically, in one possible implementation, for any of the multiple regions, if all servers in the region are not online before the version of the system is updated, it is determined that the region does not need to be rolled back. In another possible implementation, for any of the multiple regions, if the systems of all servers in the region are not updated to the latest version, it is determined that the region does not need to be rolled back. For example, if the system in the server suddenly stops during the version update process and the version update is not completed, no rollback is required.

[0048] In the embodiment of the present invention, a region other than the region that does not need to be rolled back among the multiple regions may be determined as at least one region that needs to be rolled back.

[0049] S202: Determine the priority of each area in the at least one area.

[0050] In an embodiment of the present invention, for any one of the at least one areas, the priority of the area can be determined according to the environment corresponding to the system in the server in the area; wherein, when the environment corresponding to the system in the server in the area is a test environment, the priority of the area is the lowest; and when the environment corresponding to the system in the server in the area is a production environment, the priority of the area is the highest.

[0051] For example, a system that is released and deployed in stages on a server can go through the following environments in sequence: test environment, regression environment, pre-release environment, and production environment.

[0052] Then, if the system version of the server in a region corresponds to the test environment, the priority of this region is the fourth priority, which is the lowest priority;

[0053] If the server system version in a region corresponds to the regression environment, the priority of this region is the third priority;

[0054] If the server system version in a region corresponds to the pre-release environment, the priority of this region is the second priority;

[0055] If the system version of the server in a region corresponds to the production environment, the priority of this region is the first priority, that is, the highest priority.

[0056] S203: Perform a rollback operation on the system of the server in each area according to the priority of each area in the at least one area.

[0057] In the embodiment of the present invention, the rollback operation can be performed on the system of the server in each area of ​​the at least one area in descending order of priority. The specific process of performing the rollback operation is not limited in the embodiment of the present invention and will not be described in detail here.

[0058] In combination with the example in the previous S202, if the system version of the servers in a region corresponds to the production environment, the servers in the region may be rolled back first.

[0059] After the rollback of servers in the first priority area is completed, the servers in the second priority area are rolled back, then the servers in the third priority area are rolled back, and finally the servers in the fourth priority area are rolled back.

[0060] Combined with the previous description, such as Figure 3 The figure is a schematic diagram of a method flow chart provided by an embodiment of the present invention.

[0061] S301: Determine whether all of the multiple regions need to perform a rollback operation, if yes, go to S302, if no, go to S303.

[0062] S302: Determine all regions as regions that need to be rolled back.

[0063] S303: Determine at least one region that needs to be rolled back among the multiple regions.

[0064] S304: Determine the priority of each region in the at least one region that needs to be rolled back.

[0065] S305: Determine the server that needs to be rolled back in each region that needs to be rolled back.

[0066] Specifically, in one possible implementation, for any server in a region, if the server is not online before the system version is updated, it is determined that the server does not need to be rolled back. In another possible implementation, for any server in a region, if the system of the server is not updated to the latest version, it is determined that the server does not need to be rolled back. For example, if the system in the server suddenly stops during the version update process and the version update is not completed, no rollback is required.

[0067] S306: Perform a rollback operation on the system of the server in each area of ​​all areas that need to be rolled back in order from high to low priority.

[0068] In the embodiment of the present invention, when performing a rollback operation on the system of the server in each area, it is also possible to choose whether to check the rolled back services according to the current environment. If all the checking steps are skipped, the rollback efficiency can be improved. In the embodiment of the present invention, for any area in the at least one area, when performing a rollback operation on the system of the server in the cluster according to the cluster granularity in the area, after the system rollback of each server in the cluster is completed, the step of checking the service of the system can be skipped. Specifically, Figure 4 As shown, it is a schematic flow chart of an inspection method provided by an embodiment of the present invention.

[0069] S401: Select a cluster from the region for a rollback operation.

[0070] A cluster may be selected arbitrarily, or a cluster including more servers may be preferentially selected, which is not limited in the embodiment of the present invention.

[0071] S402: The servers in the cluster complete the rollback operation.

[0072] S403: Check whether the service in the server has been rolled back. If so, execute S404; otherwise, execute S405.

[0073] S404: Is there any cluster in the region that has performed the rollback operation? If yes, return to S401; if no, go to S408.

[0074] S405: Check the rolled-back services in the server.

[0075] The specific method of checking is not limited in the embodiment of the present invention. It can be checked manually or through a specific program, which will not be described in detail here.

[0076] S406: Check whether the service meets expectations. If so, go to S404; otherwise, go to S407.

[0077] S407: Determine that the rollback fails, and terminate the rollback operation.

[0078] S408: Determine that the rollback is successful.

[0079] In the embodiment of the present invention, there is a corresponding installation file for the corresponding version of the system in each environment. Each server can store and back up each received installation file, and each installation file corresponds to a file identifier. Before performing a rollback operation on the server, it is determined whether the server has the installation file required to perform the rollback operation; if the installation file exists, the rollback operation is implemented by directly calling the locally backed-up installation file, so that there is no need to download the installation file, which saves the download and deployment link and greatly increases the rollback efficiency of each server.

[0080] Specifically, for any server in the at least one region, the process of the server performing the rollback operation can refer to Figure 5 As shown. Figure 5 The figure is a schematic diagram of a rollback method flow provided by an embodiment of the present invention.

[0081] S501: The server obtains a rollback instruction, where the rollback instruction is used to instruct the server to perform a rollback operation, and the rollback instruction includes a file identifier of an installation file.

[0082] The rollback instruction may be sent by the management device of the at least one zone, or may be sent by other devices, which is not limited in the embodiment of the present invention.

[0083] S502: The server determines whether there is an installation file required for performing the rollback operation in the server; if the installation file exists, the process goes to S503; otherwise, the process goes to S504.

[0084] Specifically, if the server includes the file corresponding to the file identifier, it is determined that the installation file exists in the server; if the server does not include the file corresponding to the file identifier, it is determined that the installation file does not exist in the server.

[0085] S503: Implement a rollback operation through the installation file in the server.

[0086] S504: Obtain the download address of the installation file.

[0087] The specific method of obtaining the download address is not limited in the embodiment of the present invention. In one implementation, the download address may be located in the rollback instruction.

[0088] S505: Download the installation file according to the obtained download address.

[0089] S506: Implement a rollback operation using the downloaded installation file.

[0090] The various embodiments described herein may be independent solutions or may be combined according to internal logic, and all of these solutions fall within the protection scope of this application.

[0091] Based on the same technical concept, the embodiment of the present invention provides a rollback device based on hierarchical release, such as Figure 6As shown, the device 600 includes: a processing unit 601 and a rollback unit 602. The division of modules in the embodiments of the present application is schematic, which is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application can be integrated into a processor, or it can exist physically separately, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional modules.

[0092] A processing unit, configured to determine at least one region that needs to be rolled back among multiple regions; wherein each region includes at least one cluster, and the cluster includes at least one server;

[0093] The rollback unit is used to determine the priority of each area in the at least one area; according to the priority of each area in the at least one area, perform a rollback operation on the system of the server in each area.

[0094] The device may also perform other steps, for which please refer to the previous description for details, which will not be repeated here.

[0095] Based on the same technical concept, an embodiment of the present invention provides a computer device, which may be a terminal or a server. Figure 7 As shown, the device 700 includes at least one processor 701 and a memory 702 connected to the at least one processor. The specific connection medium between the processor 701 and the memory 702 is not limited in the embodiment of the present invention. Figure 7 For example, the processor 701 and the memory 702 are connected via a bus. The bus can be divided into an address bus, a data bus, a control bus, etc. Figure 7 The device shown can be Figure 6 The communication device can be applied to the flowchart shown above to perform the steps in the above method embodiment. For ease of description, Figure 7 Only the main components of the communication device are shown.

[0096] In the embodiment of the present invention, the memory 702 stores instructions that can be executed by at least one processor 701. The at least one processor 701 can execute the above instructions by executing the instructions stored in the memory 702. Figure 5 The steps included in the method shown.

[0097] The processor 701 is the control center of the computer device, and can use various interfaces and lines to connect various parts of the computer device, by running or executing instructions stored in the memory 702 and calling data stored in the memory 702. Optionally, the processor 701 may include one or more processing units, and the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 701. In some embodiments, the processor 701 and the memory 702 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0098] The processor 701 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present invention may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0099] The memory 702 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 702 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 702 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 702 in the embodiment of the present invention can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0100] Based on the same inventive concept, an embodiment of the present invention provides a computer-readable storage medium storing a computer program executable by a computer device. When the program runs on the computer device, the computer device executes the steps of the above method.

[0101] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0102] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data transmission device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data transmission device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0103] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data transmission device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0104] These computer program instructions may also be loaded onto a computer or other programmable data transmission device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0105] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims

1. A rollback method based on hierarchical release, characterized in that: include: Determine at least one region that needs to be rolled back among the multiple regions; wherein each region includes at least one cluster, and the cluster includes at least one server; determining a priority for each of the at least one area; According to the priority of each area in the at least one area, a rollback operation is performed on the system of the server in each area; For any one of the at least one area, a rollback operation is performed on the systems of the servers in the cluster in the area according to the cluster granularity; wherein after the system rollback of the servers in each cluster is completed, the step of performing a service check on the system is skipped.

2. The method according to claim 1, characterized in that The determining at least one region that needs to be rolled back from among the multiple regions includes: For any area among the multiple areas, if the server in the area is not online before the version of the system is updated, or the system of the server in the area is not updated to the latest version, it is determined that the area does not need to be rolled back; An area among the multiple areas except the area that does not need to be rolled back is determined as at least one area that needs to be rolled back.

3. The method according to claim 1 or 2, characterized in that The determining the priority of each area of ​​the at least one area comprises: For any one of the at least one areas, the priority of the area is determined according to the environment corresponding to the system in the server in the area; wherein, when the environment corresponding to the system in the server in the area is a test environment, the priority of the area is the lowest; and when the environment corresponding to the system in the server in the area is a production environment, the priority of the area is the highest.

4. The method according to claim 3, characterized in that The step of performing a rollback operation on a system of a server in each area according to a priority of each area in the at least one area includes: A rollback operation is performed on the system of the server in each of the at least one area in order of priority from high to low.

5. The method according to claim 1 or 2, characterized in that: The method further comprises: For any server in the at least one area, before performing a rollback operation on the server, determining whether an installation file required to perform the rollback operation exists in the server; If the installation file exists, the rollback operation is implemented through the installation file.

6. The method according to claim 5, characterized in that If the installation file does not exist, download the installation file according to the obtained download address; The rollback operation is implemented through the downloaded installation file.

7. The method according to claim 5, characterized in that The determining whether the server has the installation files required for performing the rollback operation includes: Obtaining a rollback instruction, wherein the rollback instruction is used to instruct the server to perform a rollback operation, and the rollback instruction includes a file identifier of the installation file; If the server includes the file corresponding to the file identifier, determining that the installation file exists in the server; If the server does not include the file corresponding to the file identifier, it is determined that the installation file does not exist in the server.

8. A rollback device based on hierarchical release, characterized in that: include: A processing unit, configured to determine at least one region that needs to be rolled back among the multiple regions; wherein each region includes at least one cluster, and the cluster includes at least one server; a rollback unit, configured to determine a priority of each of the at least one region; According to the priority of each area in the at least one area, a rollback operation is performed on the system of the server in each area; For any one of the at least one area, a rollback operation is performed on the systems of the servers in the cluster in the area according to the cluster granularity; wherein after the system rollback of the servers in each cluster is completed, the step of performing a service check on the system is skipped.

9. A computer-readable storage medium, characterized in that: The storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images