CN106325909B - Method and system for updating multiple images in private cloud system - Google Patents
Method and system for updating multiple images in private cloud system Download PDFInfo
- Publication number
- CN106325909B CN106325909B CN201510381730.5A CN201510381730A CN106325909B CN 106325909 B CN106325909 B CN 106325909B CN 201510381730 A CN201510381730 A CN 201510381730A CN 106325909 B CN106325909 B CN 106325909B
- Authority
- CN
- China
- Prior art keywords
- server
- information
- private cloud
- package
- version number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a method and a system for updating a plurality of mirror images in a private cloud system, wherein the private cloud system is respectively communicated with a first server and a third server, and a second server is respectively communicated with the first server and the third server, and the method comprises the following steps: the method comprises the steps that a first server sends mirror image information query requests to a private cloud system to obtain current information of each mirror image; the second server sends a package version information query request to the third server to obtain package version information of each mirror image; the first server or the second server compares the current information with the package version information, and if the level of the package version information is higher than that of the current information, the package version information is stored in the first server to serve as update package information; and the first server sends an instruction to the private cloud system according to the update package information, so that the private cloud system acquires the update package from the third server, updates by using the update package, and stores the updated corresponding mirror image as a new mirror image in the private cloud system.
Description
Technical Field
The present invention relates to a private cloud system, and more particularly, to a method and system for updating a plurality of images in a private cloud system.
Background
Currently, cloud computing has become a widely used IT technology. Depending on the Service-providing layer, cloud computing can be roughly divided into IaaS (Infrastructure-as-a-Service) cloud, PaaS (Platform-as-a-Service) cloud, SaaS (Software-as-a-Service) cloud, and the like. In the IaaS cloud, such technologies mainly focus on providing users with available infrastructure services based on customization, enabling users to freely and conveniently manage the lifecycle of virtual resources. Private cloud (Private cloud) systems are cloud computing systems that are built for individual use by a customer to ensure effective control over data, security, and quality of service. The customer owns the infrastructure and can control the manner in which applications are deployed on this infrastructure. Private cloud systems may be deployed within the firewall of an enterprise data center, or they may be deployed at a secure host hosting site. The private cloud of the IaaS layer mainly provides functions of user authority management, mirror image/snapshot management, virtual machine management, virtual network management, virtual storage management and the like. An image (image) is a file storage form, and the image used in cloud computing contains contents necessary for starting a new virtual machine; the snapshot (snapshot) is a product after snapshot backup operation is performed on the current file system state of the virtual machine, and under a general full snapshot mechanism, the generated snapshot can be used as an effective backup copy of the virtual machine and can also be used for starting another new virtual machine. Thus, in the software/framework of most private cloud systems, the mirror is essentially equivalent in utility to the snapshot when the virtual machine is created.
In the software/framework of the mainstream private cloud system, the mirror image/snapshot management function mainly includes the following sub-functions:
mirror/snapshot making: enabling users to upload images/take snapshots of the virtual machine, allowing users to customize general image/snapshot information (such as simple information of name, size, usage authority, etc.) and save to the database.
Mirror/snapshot delete.
Mirror/snapshot viewing.
Mirror/snapshot calls.
It can be seen that the mirror image/snapshot management function in the private cloud system mainly focuses on the implementation of the basic function, and in an actual production environment, the actual requirements of the user on the mirror image/snapshot management cannot be met. Along with the increase of the number of the mirror images, the manual judgment and updating are unrealistic and unreasonable, the judgment decision depends on experience, the error probability is high (the misjudgment causes endless resource occupation), an effective recovery mechanism is not provided, and the judgment and the manual deletion completely depend on the self judgment of a user.
When a user creates a new virtual machine using the image/snapshot, it needs to be called from the existing image/snapshot in the database. As the size of the database grows, the number, variety and version complexity of the images/snapshots will continuously increase, and the usability of the images/snapshots faces a great challenge. The mirror image/snapshot contains a file system, the main contents of which include an operating system and its related configuration, and custom-installed software and its related configuration, and these contents need to be upgraded/patched over time to ensure the reliability of the provided service. In the current private cloud system, the limitation of functions provided by the system for users exists, and the users can only rely on frequent manual judgment and tedious manual operation for carrying out the operation. The manual judgment means that: whether the images/snapshots need to be updated or not is checked one by one, and the number of the images/snapshots may vary from tens to tens of thousands according to different actual environments. The manual operation is as follows: and manually starting the virtual machine by using the mirror image/snapshot to be updated, inputting an upgrading/patching command, making a new snapshot for the virtual machine after the command is executed, and storing the new snapshot in a database to replace the old mirror image/snapshot.
Disclosure of Invention
The invention aims to provide a method and a system for updating a plurality of images in a private cloud system, which can solve the problem of version validity of the images in the private cloud system, and can ensure that the private cloud system can periodically monitor and judge upgrading/patching time and perform related operation upgrading/patching operation when needed by providing an autonomous mechanism based on user-defined parameters, thereby maintaining the availability of an Operating System (OS) in the images, and performing version upgrading and patching operation on the operating system to prevent the safety problem of the operating system caused by security loopholes, component loss or over-low version. And meanwhile, the usability of software contained in the mirror image is kept, and the software is subjected to version upgrading and patching operation, so that the safety problem and the compatibility problem caused by security holes and excessively low versions of the software are prevented.
The invention provides a method for updating a plurality of mirror images in a private cloud system, wherein the private cloud system is respectively communicated with a first server and a third server, a second server is respectively communicated with the first server and the third server, and the method comprises the following steps:
a) the first server sends a mirror image information query request to the private cloud system at a first preset time period so as to obtain the current information of each mirror image in the plurality of mirror images, and the current information is stored in the first server;
b) the second server sends a package version information query request to the third server at a second preset time period so as to obtain the package version information of each mirror image from the third server and store the package version information in the second server;
c) comparing the current information with the package version information by the first server or the second server for a third predetermined time period, and if the level of the package version information is higher than that of the current information, storing the package version information in the first server as update package information;
d) and the first server sends an instruction to the private cloud system according to the update package information, so that the private cloud system acquires the update packages corresponding to the update package information one to one from the third server, updates the corresponding mirror images by using the update packages, and stores the updated corresponding mirror images as new mirror images in the private cloud system.
The current information comprises the name of an operating system and the current version number of the operating system and/or the name of software loaded on the operating system and the current version number of the software.
The package version information includes an updatable version number of the operating system and/or an updatable version number of the software.
The level of the packet version information being higher than the level of the current information means that the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software is greater than the current version number of the software, wherein if the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software is greater than the current version number of the software, the updatable version number of the operating system and/or the updatable version number of the software is stored in the first server as the updated packet information.
By this comparison, only update package information with a large version number can be extracted to update the updateable image, thereby improving the update efficiency.
And sequencing the update packages according to a preset priority. Therefore, when the number of the update packages is large, the update packages can be updated in sequence according to the needs of users.
And c), the current information of the new mirror image comprises a mirror image new storage mark, and the first server executes the step c) when the first server detects the mirror image new storage mark.
Therefore, all the images are not needed to be compared and updated, and only the new images are compared and updated, so that the updating efficiency can be improved.
And c), when the second server detects that the package version information contains a package version new storage mark, the second server executes the step c).
Therefore, the mirror image can be compared and updated when a new update package or patch package appears, and the updating efficiency can be further improved.
The method further comprises e), when the first server judges that the storage quantity of the plurality of images exceeds a preset threshold value, sending an instruction to the private cloud system to enable the private cloud system to delete or compress a part of the plurality of images until the storage quantity of the plurality of images is smaller than the threshold value.
In this manner, the private cloud system may be assured of having sufficient storage space to store new images that are later updated.
The invention also provides a system for updating the plurality of mirror images in the private cloud system, which comprises the private cloud system, the first server, the second server and the third server, wherein the private cloud system, the first server, the second server and the third server execute the method.
The method and the system can automatically carry out version upgrading on the mirror image with the upgraded updating package/patch package without manually judging whether the mirror image needs to be updated or not, thereby greatly improving the updating efficiency and reducing the error probability. And performing related upgrading/patching operation when needed, thereby maintaining the availability of an Operating System (OS) in the image and preventing the security problem of the OS caused by security holes, component loss or excessively low version. And meanwhile, the usability of software loaded on an operating system in the image is kept, so that the safety problem and the compatibility problem of the software caused by security holes and excessively low versions are prevented.
Drawings
FIG. 1 is a flow diagram of a method of updating a plurality of images in a private cloud system in accordance with an embodiment of the present invention;
fig. 2 is a block diagram of a system for updating multiple images in a private cloud system in accordance with an embodiment of the present invention.
Detailed Description
The present invention will be described in detail below with reference to the accompanying drawings.
Fig. 1 is a flowchart of a method of updating a plurality of images in a private cloud system according to an embodiment of the present invention, and fig. 2 is a block diagram of a system of updating a plurality of images in a private cloud system according to an embodiment of the present invention. The private cloud system 21 is, for example, an OpenStack private cloud system, and communicates with the first server and the third server, respectively, and the second server communicates with the first server and the third server, respectively. In this embodiment, the first server is, for example, a mirror image information server 22, which is a Linux operating system and is deployed with a MySQL database, the second server is, for example, a package version information server 23, which is a Limux operating system and is deployed with a MySOL database, and the third server is, for example, an update package source server 24 and is built with a software source corresponding to the Limux operating system.
In step S11, the image information server 22 sends an image information query request to the private cloud system 21 for a first predetermined period of time to obtain current information of each of the plurality of images, and stores the current information in the image information server 22. The current information includes the name of the operating system and the current version number of the operating system and/or the name of the software piggybacked on the operating system and the current version number of the software. In this example, there are 3 mirror images, mirror 1, mirror 2 and mirror 3. The current information of image 1 contains the operating system Ubuntu 14.0464 bit Server version, the current version number of the operating system 14.04.201503_07, the software loaded on the operating system is MySOL, and the current version number of the software 5.1.32. The current information of image 2 contains the operating system Ubuntu 12.0464 bit Desktop, the current version number of the operating system 12.04.201407_12, no piggybacked software. The current information of image 3 contains the operating system CentOS 7.164 bit, the current version number of the operating system 7.1.201503_01, the piggybacked software on the operating system is Tomcat, the current version number of the software is 7.0.2.
In step S12, the package version information server 23 issues a package version information query request to the update package source server 24 at a second predetermined time period to obtain the package version information of each mirror image from the update package source server 24 and stores the package version information in the package version information server 23.
The update package source server 24 stores the mirrored update package or patch package as in the related art, and the user can store the desired update package or patch package in the update package source server 24 as needed. The mirrored update package or patch package contains mirrored package version information.
The package version information for each image contains an updatable version number of the operating system and/or an updatable version number of the software hosted thereon. In this example, the package version information 1 of the image 1 includes an updatable version number 14.04.201503-07 of the Server version of Ubuntu 14.0464 bit of the operating system and an updatable version number 5.1.32 of the loaded software MySOL; the package version information 2 of the image 2 contains an updatable version number 12.04.201409_17 of the Ubuntu 12.0464 bit Desktop; the package version information 3 of the image 3 includes an updatable version number 7.1.201503_01 of the operating system CentOS 7.164 bit and an updatable version number 7.0.6 of the piggybacked software Tomcat. Here, the updatable version number of the operating system may be the same as or different from the current version number of the operating system described above, and the updatable version number of the piggybacked software may be the same as or different from the current version number of the piggybacked software described above.
Next, in step S13, the current information of each mirror is compared with the package version information at a third predetermined time period, and if the level of the package version information is higher than that of the current information, the package version information is stored in the mirror information server 22 as the update package information. Here, the package version information having a higher level than the current information means that the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software loaded thereon is greater than the current version number of the software.
In this example, for image 1, the updatable version number 14.04.201503-07 of the Ubuntu 14.0464 bit Server version of the operating system is the same as the current version number 14.04.201503-07 of the operating system, and the updatable version number 5.1.32 of the software MySOL is the same as the current version number 5.1.32 of the software. For image 2, the updatable version number 12.04.201409_17 of the operating system Ubuntu 12.0464 bit Desktop is greater than the current version number 12.04.201407_12 of the operating system. For image 3, the updateable version number 7.1.201503_01 of the operating system CentOS 7.164 bit is the same as the current version number 7.1.201503_01 of the operating system, and the updateable version number 7.0.6 of the software Tomcat is greater than the current version number 7.0.2 of the software.
As such, if the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software is greater than the current version number of the software, the updatable version number of the operating system and/or the updatable version number of the software is stored in the image information server 22 as the update package information.
In this example, as described above, the updatable version number 12.04.201409_17 of the operating system Ubuntu 12.0464 bit Desktop in the package version information 2 of the image 2 and the updatable version number 7.0.6 of the software Tomcat in the package version information 3 of the image 3 are stored in the image information server 22 as the update package information 2 and the update package information 3, respectively. Here, both the current version number and the updatable version number refer to a serial number.
Further, there may be a plurality of updatable version numbers of the operating system, and if the plurality of updatable version numbers are all larger than the current version number of the operating system, the plurality of updatable version numbers are stored in the mirror information server 22 as update package information. There may be a plurality of updatable version numbers of the software, and if the plurality of updatable version numbers are all larger than the current version number of the software, the plurality of updatable version numbers are stored in the mirror information server 22 as update package information. That is, the update package information may include information of a plurality of update packages, and in the subsequent update step, the plurality of update packages may all be updated using.
Then, in step S14, the image information server 22 issues instructions corresponding to the update package information 2 and the update package information 3 to the private cloud system 21 according to the update package information 2 and the update package information 3, respectively, so that the private cloud system 21 acquires the update package 2 and the update package 3, which correspond to the update package information 3 and the update package information 3, respectively, one to one, from the update package source server 24, updates the corresponding images (i.e., the image 2 and the image 3) using the update package 2 and the update package 3, and stores the updated image 2 and the updated image 3 in the private cloud system 21 as a new image 4 and an updated image 5, respectively.
In this example, the update package 2 is, for example, an update package of the updateable version number 12.04.201409_17 of the Desktop at Ubuntu 12.0464 bit, and the update package 3 is, for example, an update package of the updateable version number 7.0.6 of the software Tomcat. The private cloud system 21 updates the operating system Ubuntu 12.0464 Desktop in the image 2 by using the update package 2, updates the software Tomcat in the image 3 by using the update package 3, and stores the updated image 2 as a new image 4 and the updated image 3 as a new image 5 in the private cloud system 21. The current information of the new image 4 includes the Ubuntu 12.0464 bits Desktop and the updated version number 12.04.201409_17 of the operating system, and the current information of the new image 5 includes the CentOS 7.164 bits and its version number 7.1.201503_01 of the operating system, and the loaded software Tomcat and its updated version number 7.0.6.
Here, the specific process of updating the mirror image by the private cloud system 21 using the plurality of update packages/the plurality of patch packages obtained from the update package source server is the same as that of the related art, and thus will not be described in detail here.
Further, the 2 update packages may be sorted in accordance with a predetermined priority. For example, if the priority of the update package 2 is high and the priority of the update package 3 is low, the update is performed on the image 2 first and then the update is performed on the image 3. The priority level here is preset by the user. Because the actual number of the images may be very large, the setting of the priority can update the images to be updated in sequence according to the order desired by the user, so as to meet the requirements of the user.
The first predetermined time period, the second predetermined time period, and the third predetermined time period mentioned above are preset by the user, and may be the same or different, for example, the first predetermined time period is 1 day, the second predetermined time period is 2 days, and the third predetermined time period is 3 days, or the first predetermined time period is 2 hours, the second predetermined time period is 2 hours, and the third predetermined time period is 3 hours, or all of the first predetermined time period, the second predetermined time period, and the third predetermined time period are 1 week, and so on.
Through the comparison and the updating, the mirror image with the upgraded version can be automatically updated without manual judgment and operation, so that the updating efficiency can be improved, and the error rate can be reduced.
Further, the current information of the new image 4 and the new image 5 further include an image new storage flag, respectively, the image information server 22 obtains the current information of the new image 4 and the new image 5 from the private cloud system 21, and when the image information server 21 detects the image new storage flag in the new image 4 and the new image 5, the image information server 21 performs the step S13.
Therefore, all images are not needed to be compared and updated, and only the new images are compared and updated, so that the updating efficiency can be further improved.
When a user stores a new/upgraded update package or patch package in the update package source server 24, the package version information of the new/upgraded update package or patch package may include a new storage flag. The package version information server 23 obtains the package version information including the new deposit flag from the update package source server 24, and when detecting the new deposit flag, the package version information server 23 performs the above-described step S13.
Therefore, the mirror image can be compared and updated when a new update package or patch package appears, and the updating efficiency can be further improved.
Further, after step S14, when the image information server 22 determines that the storage amount of the plurality of images exceeds the predetermined threshold, an instruction is issued to the private cloud system 21 so that the private cloud system 21 deletes or compresses a part of the plurality of images until the storage amount of the plurality of images is less than the threshold.
Before the update, only image 1, image 2, and image 3 are stored in the private cloud system 21, for example, and the storage amount of the current information of these 3 images is, for example, 2 GB. The predetermined threshold of the storage of the private cloud system 21 is set to, for example, 2.5 GB.
After step S14 is performed as described above, a new image 4 and a new image 5 are obtained, the new image 4 being, for example, 0.5GB and the new image 5 being, for example, 0.5 GB. Then the private cloud system 21 stores mirror 1, mirror 2, mirror 3, new mirror 4 and new mirror 5, and then the storage is 3 GB. At this time, the image information server 22 determines that the storage amount of the 5 images exceeds the threshold 2.5GB, and sends an instruction to the private cloud system 21, so that the private cloud system 21 deletes or compresses a part of the 5 images until the storage amount of the 5 images is less than the threshold. In this manner, the private cloud system 21 may be assured of having sufficient storage space to store new images that are later updated.
Here, a specific manner of deleting or compressing a part of the image is the same as the related art, and thus will not be described in detail.
In addition, the present invention further provides a system for updating a plurality of images in a private cloud system, in this example, as shown in fig. 2, the system includes a private cloud system 21, a first server (image information server) 22, a second server (package version information server) 23, and a third server (update package source server) 24, and the private cloud system 21, the image information server 22, the package version information server 23, and the update package source server 24 execute the method described above.
The method and the system for updating the plurality of images in the private cloud system can solve the problem of version validity of the images in the private cloud system, and can ensure that the private cloud system can periodically monitor and judge the upgrading/patching time and perform related upgrading/patching operation when needed by providing an autonomous mechanism based on user-defined parameters, thereby keeping the availability of an Operating System (OS) in the images, and performing version upgrading and patching operation on the operating system to prevent the safety problem of the operating system caused by security holes, component loss or over-low version. Meanwhile, the usability of the software loaded on the operating system in the mirror image is kept, and the software is subjected to version upgrading and patching operation, so that the safety problem and the compatibility problem caused by security holes and excessively low versions of the software are prevented.
In addition, the method and the system can automatically carry out version upgrading on the mirror image with the upgraded updating package/patch package without manually judging whether the mirror image needs to be updated or not, thereby greatly improving the updating efficiency and reducing the error probability.
While particular embodiments of the invention have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the invention. Indeed, the innovative methods described herein can be implemented in a variety of other forms; furthermore, various omissions, substitutions and changes to the methods and systems described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such various forms or modifications as would fall within the scope and spirit of the inventions.
Claims (9)
1. A method of updating a plurality of images in a private cloud system, the private cloud system in communication with a first server and a third server, respectively, a second server in communication with the first server and the third server, respectively, the method comprising the steps of:
a) the first server sends a mirror image information query request to the private cloud system at a first preset time period so as to obtain the current information of each mirror image in the plurality of mirror images, and the current information is stored in the first server;
b) the second server sends a package version information query request to the third server at a second preset time period so as to obtain the package version information of each mirror image from the third server and store the package version information in the second server;
c) comparing the current information with the package version information by the first server or the second server for a third predetermined time period, and if the level of the package version information is higher than the level of the current information, storing the package version information in the first server as update package information;
d) and the first server sends an instruction to the private cloud system according to the update package information, so that the private cloud system acquires the update packages corresponding to the update package information one to one from the third server, updates the corresponding mirror images by using the update packages, and stores the updated corresponding mirror images as new mirror images in the private cloud system.
2. The method of claim 1, wherein the current information includes a name of an operating system and a current version number of the operating system and/or a name of software mounted on the operating system and a current version number of the software.
3. The method of claim 2, wherein the package version information includes an updatable version number of the operating system and/or an updatable version number of the software.
4. The method of claim 3, wherein the package version information is ranked higher than the current information in that the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software is greater than the current version number of the software,
wherein if the updatable version number of the operating system is greater than the current version number of the operating system and/or the updatable version number of the software is greater than the current version number of the software, the updatable version number of the operating system and/or the updatable version number of the software is stored in the first server as the update package information.
5. The method of claim 4, wherein the update packets are ordered according to a predetermined priority.
6. The method of claim 5, wherein the current information of the new image comprises an image new deposit flag, and wherein the first server performs step c) when the first server detects the image new deposit flag.
7. The method according to claim 5, wherein said second server performs said step c) when said second server detects that said package version information contains a package version newly stored flag.
8. The method of any one of claims 1-7, further comprising e) when the first server determines that the amount of storage of the plurality of images exceeds a predetermined threshold, issuing an instruction to the private cloud system to cause the private cloud system to delete or compress a portion of the plurality of images until the amount of storage of the plurality of images is less than the threshold.
9. A system for updating a plurality of images in a private cloud system, comprising the private cloud system, a first server, a second server, and a third server, wherein the private cloud system, the first server, the second server, and the third server perform the methods of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510381730.5A CN106325909B (en) | 2015-07-02 | 2015-07-02 | Method and system for updating multiple images in private cloud system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510381730.5A CN106325909B (en) | 2015-07-02 | 2015-07-02 | Method and system for updating multiple images in private cloud system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106325909A CN106325909A (en) | 2017-01-11 |
| CN106325909B true CN106325909B (en) | 2021-03-23 |
Family
ID=57727351
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510381730.5A Expired - Fee Related CN106325909B (en) | 2015-07-02 | 2015-07-02 | Method and system for updating multiple images in private cloud system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106325909B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111382136B (en) * | 2018-12-29 | 2024-03-15 | 华为技术有限公司 | File system mirror image and file request method |
| CN110730090B (en) * | 2019-09-05 | 2023-02-03 | 深圳平安通信科技有限公司 | Batch updating method, device, medium and electronic equipment for agent terminals in cloud environment |
| CN113326053A (en) * | 2021-06-18 | 2021-08-31 | 上海钛米机器人股份有限公司 | Robot management system and method |
| US11909720B2 (en) | 2021-09-17 | 2024-02-20 | Kyndryl, Inc. | Secure remote support of systems deployed in a private network |
| CN114726836A (en) * | 2022-04-25 | 2022-07-08 | 四川智能建造科技股份有限公司 | Distributed application distribution deployment method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1598770A (en) * | 2003-09-19 | 2005-03-23 | 乐金电子（沈阳）有限公司 | System software updating method of domestic electrical equipment |
| CN1763713A (en) * | 2004-10-22 | 2006-04-26 | 华为技术有限公司 | Mobile terminal software edition updating method |
| CN104679527A (en) * | 2013-11-26 | 2015-06-03 | 中国银联股份有限公司 | Off-line upgrading method of virtual machine image |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5113699B2 (en) * | 2008-09-24 | 2013-01-09 | 株式会社日立ソリューションズ | Firmware update system and update image generation / distribution server device |
-
2015
- 2015-07-02 CN CN201510381730.5A patent/CN106325909B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1598770A (en) * | 2003-09-19 | 2005-03-23 | 乐金电子（沈阳）有限公司 | System software updating method of domestic electrical equipment |
| CN1763713A (en) * | 2004-10-22 | 2006-04-26 | 华为技术有限公司 | Mobile terminal software edition updating method |
| CN104679527A (en) * | 2013-11-26 | 2015-06-03 | 中国银联股份有限公司 | Off-line upgrading method of virtual machine image |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106325909A (en) | 2017-01-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106325909B (en) | Method and system for updating multiple images in private cloud system | |
| US20180067830A1 (en) | Healing cloud services during upgrades | |
| US11520669B2 (en) | System and method for efficient backup system aware direct data migration between cloud storages | |
| US10445186B1 (en) | Associating a guest application within a virtual machine to create dependencies in backup/restore policy | |
| US10911540B1 (en) | Recovering snapshots from a cloud snapshot lineage on cloud storage to a storage system | |
| US11199985B2 (en) | Tracking storage capacity usage by snapshot lineages using metadata in a multi-level tree structure | |
| US11537553B2 (en) | Managing snapshots stored locally in a storage system and in cloud storage utilizing policy-based snapshot lineages | |
| CN105867962A (en) | System upgrading method and device | |
| US11829609B2 (en) | Data loss recovery in a secondary storage controller from a primary storage controller | |
| CN110780912A (en) | Hierarchical spanning tree software patch with segmentation support | |
| US11392617B2 (en) | Recovering from a failure of an asynchronous replication node | |
| US11573923B2 (en) | Generating configuration data enabling remote access to portions of a snapshot lineage copied to cloud storage | |
| CN107463390B (en) | Software upgrading method and upgrading server | |
| US11288134B2 (en) | Pausing and resuming copying of snapshots from a local snapshot lineage to at least one cloud snapshot lineage | |
| US20200133709A1 (en) | System and method for content - application split | |
| CN107422991B (en) | Storage strategy management system | |
| US20220179664A1 (en) | Graphical user interface to specify an intent-based data management plan | |
| US11119753B2 (en) | Distributed autonomous patching system | |
| US11630736B2 (en) | Recovering a storage volume associated with a snapshot lineage from cloud storage | |
| US10318509B2 (en) | Populating text indexes | |
| CN112579247A (en) | Method and device for determining task state | |
| US20220335010A1 (en) | Synchronization system and method | |
| US20240143411A1 (en) | Method for automatically maintaining an infrastructure as code state of a resource space hosted on a cloud platform | |
| US20170105056A1 (en) | Bulk telephony control system subscriber data manipulation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20210323 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |