Patent Application
20250094194
Many software applications run within containers, such as virtual machines (VMs). In order to install these containerized applications, a pre-packaged VM image containing both application software and an operating system may be copied onto a server.
In one embodiment, a computer program product is described. The computer program product includes a non-transitory computer-readable storage medium storing instructions, which when performed by processing circuitry of a set of one or more computing devices, cause the set of computing devices to configure a new containerized application operating in a first container to replace an old containerized application operating in a second container. This configuration includes (a) the new containerized application receiving a license identifier (ID) of a licensing service, the license ID being associated with the old containerized application; (b) sending an instruction directing the old containerized application to dissociate with the license ID; and (c) in response to the old containerized application dissociating with the license ID, associating the new containerized application with the license ID to become licensed with the licensing service.
In one embodiment, a method of configuring a new containerized application operating in a first container to replace an old containerized application operating in a second container is described. The method, performed by a set of one or more computing devices, includes (a) the new containerized application receiving a license identifier (ID) of a licensing service, the license ID being associated with the old containerized application; (b) sending an instruction directing the old containerized application to dissociate with the license ID; and (c) in response to the old containerized application dissociating with the license ID, associating the new containerized application with the license ID to become licensed with the licensing service.
In one embodiment, a computer program product is described. The computer program product includes a non-transitory computer-readable storage medium storing instructions, which when performed by processing circuitry of a set of one or more computing devices, cause the set of computing devices to operate a licensing service to: (I) receive a dissociation request from an old containerized application operating in a first container to dissociate with a license ID; (II) in response to receiving the dissociation request, dissociate the license ID from the old containerized application; (III) receive an association request from a new containerized application operating in a second container to associate with the license ID; and (IV) in response to receiving the association request, associate the license ID with the new containerized application.
The foregoing and other objects, features, and advantages will be apparent from the following description of particular embodiments of the invention, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of various embodiments of the invention. In the figures:
Examples of the methods and systems discussed herein are not limited in application to the details of construction and the arrangement of components set forth in the following description or illustrated in the accompanying drawings. The methods and systems are capable of implementation in other embodiments and of being practiced or of being carried out in various ways. Examples of specific implementations are provided herein for illustrative purposes only and are not intended to be limiting. In particular, acts, components, elements and features discussed in connection with any one or more examples are not intended to be excluded from a similar role in any other examples.
Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. Any references to examples, embodiments, components, elements or acts of the systems and methods herein referred to in the singular may also embrace embodiments including a plurality, and any references in plural to any embodiment, component, element or act herein may also embrace embodiments including only a singularity. References in the singular or plural form are not intended to limit the presently disclosed systems or methods, their components, acts, or elements. The use herein of “including,” “comprising,” “having,” “containing,” “involving,” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
References to “or” may be construed as inclusive so that any terms described using “or” may indicate any of a single, more than one, and all of the described terms. In addition, in the event of inconsistent usages of terms between this document and documents incorporated herein by reference, the term usage in the incorporated features is supplementary to that of this document; for irreconcilable differences, the term usage in this document controls.
Conventional containerized applications, as described above, may suffer from various limitations. For example, when a conventional containerized application is upgraded, a new image is installed, but various configuration details need to be transferred over from the previous version manually. This process can be especially tedious in the case of the configuration details for a software license,
Thus, it would be desirable to implement an automated installation tool to allow configuration details, including a license identifier (ID), to be automatically transferred from an old (not yet upgraded) version of a containerized application to a new version of the containerized application during the installation process. In the case of a license ID, this may be accomplished by sending an instruction to the old containerized application directing it to dissociate itself from its license ID prior to the new containerized application associating itself with that license ID.
System 30 includes at least one computing device 32 connected to a licensing server 60 over a network 34. Each computing device 32 may be any kind of computing device, such as, for example, a personal computer, laptop, workstation, server, enterprise server, tablet, smartphone, router, etc. In an example embodiment, computing device 32 is a virtualization server.
Network 34 may be any kind of communications network or set of communications networks, such as, for example, a LAN, WAN, SAN, the Internet, a wireless communication network, a virtual network, a fabric of interconnected switches, etc.
Computing device 32 includes network interface circuitry 37, processing circuitry 36, and memory 40. Computing device 32 may also include various additional features as is well-known in the art, such as, for example, user interface circuitry, interconnection traces and buses, etc.
Network interface circuitry 37 may include one or more Ethernet cards, cellular modems, Fibre Channel (FC) adapters, InfiniBand adapters, wireless networking adapters (e.g., Wi-Fi), and/or other devices for connecting to a network 31.
Processing circuitry 36 may include any kind of processor or set of processors configured to perform operations, such as, for example, a microprocessor, a multi-core microprocessor, a digital signal processor, a field-programmable gate array (FPGA), a system on a chip (SoC), a collection of electronic circuits, a similar kind of controller, or any combination of the above.
Memory 40 may include any kind of digital system memory, such as, for example, random access memory (RAM). Memory 110 stores an operating system (OS, not depicted, e.g., a Linux, UNIX, Windows, MacOS, or similar operating system) and various drivers and other applications and software modules configured to execute on processing circuitry 104 as well as various data.
Memory 40 stores a hypervisor 42 configured to operate on processing circuitry 36.
Hypervisor 42 operates to run a set of containers 50, such as virtual machines (VMs), at least including an old container 50A and a new container 50B. Each container 50 may include an operating system (OS, not depicted, e.g., a Linux, UNIX, Windows, MacOS, or similar OS), at least one application 52, and various drivers and software modules configured to execute on processing circuitry 36 as well as various data. Old container 50A includes an old containerized application 52A, and new container 50B includes a new containerized application 52B.
Each containerized application 52 stores a license ID 54 provided by a licensing service 62 (e.g., operating on a licensing server 60). The license ID 54 is uniquely associated by the licensing service 62 with a particular containerized application 52, authorizing that containerized application 62 to run. Each containerized application 52 may also store various other configuration parameters 56.
In some embodiments, memory 40 of the computing device 32 may also store an installer application 44 that also runs on the processing circuitry 36.
It should be understood that although the installer application 44, old container 50A, and new container 50B are all depicted on the same computing device 32, that is by way of example only. In other embodiments (not depicted), one or more of the installer application 44, old container 50A, and new container 50B may operate on separate computing devices 32 linked together by network 34.
Licensing server 60 may be any kind of computing device, such as, for example, a personal computer, laptop, workstation, server, enterprise server, tablet, smartphone, router, etc.
In an example embodiment, computing device 32 is a server. Licensing server 60 may also include network interface circuitry 37, processing circuitry 36, and memory 40. Computing device 32 may also include various additional features as is well-known in the art, such as, for example, user interface circuitry, interconnection traces and buses, etc.
In operation a user or the installer application 44 may initiate installation 68 of new container 50B and its new containerized application 52B on hypervisor 42 to replace old containerized application 52A running on old container 50A. In an embodiment, new containerized application 52B is a newer version of the same software as the old containerized application 52A having more advanced or upgraded code and features. For example, the old containerized application 52A and the new containerized application 52B may both be network shutdown applications.
New containerized application 52B obtains (step 70) the license ID 54 from the old containerized application 52A. In some embodiments, step 70 may be performed by old containerized application 52A directly sending the license ID 54 to the new containerized application 52B in response to the new containerized application 52B requesting the license ID 54 from the old containerized application 52A (e.g., an idempotent request such as an HTTP GET command). In other embodiments, step 70 may be performed by installer application 44 obtaining the license ID 54 (e.g., by requesting it from the old containerized application 52A) and the installer application 44 sending the license ID 54 to the new containerized application 52B. In some embodiments, step 70 may also include the new containerized application 52B receiving the configuration parameters 56 used by the old containerized application 52A (either directly from the old containerized application 52A or via the installer application 44), which the new containerized application 52B is then able to implement within itself.
Subsequently, in step 72, old containerized application 52A receives an instruction to dissociate from the license ID 54. In some embodiments, step 72 may be performed by new containerized application 52B directly sending the instruction to the old containerized application 52A in response to receiving the license ID 54. In other embodiments, step 72 may be performed by installer application 44 sending the instruction to the old containerized application 52A after sending the license ID 54 to the new containerized application 52B.
Subsequently, in step 74, old containerized application 52A dissociates itself (step 74) from the license ID 54 by sending a dissociation request to the licensing service 62. Once this is completed, a confirmation 76 of the dissociation is sent to the new containerized application 52B. In some embodiments, confirmation 76 may be directly sent by old containerized application 52A to the new containerized application 52B. In other embodiments, confirmation 76 may be sent by installer application 44 to the new containerized application 52B.
In response to receiving the confirmation 76 of the dissociation, new containerized application 52B associates itself (step 78) with the license ID 54 by sending an association request to the licensing service 62. In response, the licensing service 62 registers the license ID 54 with the new containerized application 52B.
A user or the installer application 44 may initiate installation 68′ of newer container 50C and its newer containerized application 52C on hypervisor 42 to replace new containerized application 52B running on new container 50B. In an embodiment, newer containerized application 52C is a newer version of the same software as the new containerized application 52B having more advanced or upgraded code and features.
Newer containerized application 52C obtains (step 70′) the license ID 54 from the new containerized application 52B. In some embodiments, step 70′ may be performed by new containerized application 52B directly sending the license ID 54 to the newer containerized application 52C in response to the newer containerized application 52C requesting the license ID 54 from the new containerized application 52B (e.g., an idempotent request such as an HTTP GET command). In other embodiments, step 70′ may be performed by installer application 44 obtaining the license ID 54 (e.g., by requesting it from the new containerized application 52B) and the installer application 44 sending the license ID 54 to the newer containerized application 52C. In some embodiments, step 70′ may also include the newer containerized application 52C receiving the configuration parameters 56 used by the new containerized application 52B (either directly from the new containerized application 52B or via the installer application 44), which the new containerized application 52B is then able to implement within itself.
Subsequently, in step 72′, new containerized application 52B receives an instruction to dissociate from the license ID 54. In some embodiments, step 72′ may be performed by newer containerized application 52C directly sending the instruction to the new containerized application 52B in response to receiving the license ID 54. In other embodiments, step 72′ may be performed by installer application 44 sending the instruction to the new containerized application 52B after sending the license ID 54 to the newer containerized application 52C.
Subsequently, in step 74′, new containerized application 52B dissociates itself (step 74′) from the license ID 54 by sending a dissociation request to the licensing service 62. Once this is completed, a confirmation 76′ of the dissociation is sent to the newer containerized application 52C. In some embodiments, confirmation 76′ may be directly sent by new containerized application 52B to the newer containerized application 52C. In other embodiments, confirmation 76′ may be sent by installer application 44 to the newer containerized application 52C.
In response to receiving the confirmation 76′ of the dissociation, newer containerized application 52C associates itself (step 78′) with the license ID 54 by sending an association request to the licensing service 62. In response, the licensing service 62 registers the license ID 54 with the newer containerized application 52C.
Memory 40 may also store various other data structures used by the OS, hypervisor 42, installer application 44, old containerized application 52A, new containerized application 52B, newer containerized application 52C, licensing service 62, and/or various other applications and drivers. In some embodiments, memory 40 may also include a persistent storage portion.
Persistent storage portion of memory 40 may be made up of one or more persistent storage devices, such as, for example, magnetic disks, flash drives, solid-state storage drives, or other types of storage drives. Persistent storage portion of memory 40 is configured to store programs and data even while the computing device 32 or licensing server 60 is powered off. The OS, hypervisor 42, installer application 44, old containerized application 52A, new containerized application 52B, newer containerized application 52C, licensing service 62, and/or various other applications and drivers are typically stored in this persistent storage portion of memory 40 so that they may be loaded into a system portion of memory 40 upon a system restart or as needed.
The OS, hypervisor 42, installer application 44, old containerized application 52A, new containerized application 52B, newer containerized application 52C, licensing service 62, and/or various other applications and drivers, when stored in non-transitory form either in the volatile or persistent portion of memory 40, each form a computer program product. The processing circuitry 36 running one or more applications thus forms a specialized circuit constructed and arranged to carry out the various processes described herein.
In step 110, the new containerized application 52B receives the license ID 54, of the licensing service 62 (i.e., issued and/or managed by the licensing service 62) the license ID currently being associated with the old containerized application 52A. In some embodiments, the license ID is received by the new containerized application 52B from the installer application 44. In other embodiments, the license ID is received by the new containerized application 52B from the old containerized application 52A in response to the new containerized application 52B sending a request (e.g., an idempotent request such as an HTTP GET request) to the old containerized application 52A requesting the license ID 54.
In step 120, an instruction is sent directing the old containerized application 52A to dissociate with the license ID 54. In some embodiments, step 120 is performed by the new containerized application 52B in response to step 110. In other embodiments, step 120 is performed by the installer application 44.
In step 130, in response to the old containerized application 52A dissociating with the license ID 54 (e.g., as in step 78), the new containerized application 52B associates with the license ID 54 to become licensed with the licensing service 62. In some embodiments, step 130 is more particularly performed in response to the new containerized application 52B receiving the confirmation 76 from the containerized application 52A that it has successfully dissociated with the license ID 54.
In step 210, licensing service 62 receives a dissociation request from a first containerized application 52 (e.g., old containerized application 52A, new containerized application 52B, etc.) operating within a first container (e.g., old container 50A, 50B, etc.) to dissociate with a license ID 54 managed by the licensing service 62. In response, in step 220, the licensing service 62 dissociates (e.g., unregisters) the license ID 54 from the first containerized application 52 (e.g., old containerized application 52A, new containerized application 52B, etc.).
In step 230, licensing service 62 receives an association request from a second containerized application 52 (e.g., new containerized application 52B, newer containerized application 52C, etc.) operating within a second container (e.g., new container 50B, 50C, etc.) to associate with the license ID 54. In response, in step 240, the licensing service 62 associates (e.g., registers) the license ID 54 with the second containerized application 52 (e.g., new containerized application 52B, newer containerized application 52C, etc.).
While various embodiments of the invention have been particularly shown and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
It should be understood that although various embodiments have been described as being methods, software embodying these methods is also included. Thus, one embodiment includes a tangible computer-readable medium (such as, for example, a hard disk, a floppy disk, an optical disk, computer memory, flash memory, etc.) programmed with instructions, which, when performed by a computer or a set of computers, cause one or more of the methods described in various embodiments to be performed. Another embodiment includes a computer which is programmed to perform one or more of the methods described in various embodiments.
Furthermore, it should be understood that all embodiments which have been described may be combined in all possible combinations with each other, except to the extent that such combinations have been explicitly excluded.
Finally, nothing in this Specification shall be construed as an admission of any sort. Even if a technique, method, apparatus, or other concept is specifically labeled as “background” or as “conventional,” Applicant makes no admission that such technique, method, apparatus, or other concept is actually prior art under 35 U.S.C. § 102 or 103, such determination being a legal determination that depends upon many factors, not all of which are known to Applicant at this time.
