Provisioning machines having virtual storage resources

Information

  • Patent Grant
  • 9952845
  • Patent Number
    9,952,845
  • Date Filed
    Friday, August 29, 2008
    16 years ago
  • Date Issued
    Tuesday, April 24, 2018
    6 years ago
  • CPC
  • Field of Search
    • US
    • 717 122000
    • 717 168-178
    • 709 220-222
    • 703 023-028
    • CPC
    • G06F3/067
    • G06F3/0643
    • G06F11/1464
    • G06F3/0607
    • G06F17/30067
    • G06F3/0605
    • G06F3/0637
    • G06F3/0647
    • G06F11/1469
    • G06F21/78
    • G06F9/52
    • G06F17/30194
    • G06F17/302
    • G06F17/30212
    • G06F8/60-78
  • International Classifications
    • G06F9/445
    • Term Extension
      1346
Abstract
Embodiments relate to systems and methods for provisioning machines having virtual storage resources, such as virtual disks. A provisioning (or “cobbler”) server can interact with a local virtual machine installation client to initiate software provisioning to a set of target machines. Each virtualization profile or virtualized system record can have one or more virtual disks associated with it for installation and storage. The provisioning process can entail, for example, the delivery of an operating system, applications, or other software to the targets. The virtual machine installation client can identify potential locations for virtual disks on the target, such as volume identifiers, media types, and/or file systems. The cobbler server can generate a distribution to the target machine taking the configuration of the virtual disk into account, and install the provisioned software to that storage resource without a need to manually specify storage parameters. Diskless machines can also be provisioned.
Description
FIELD

The present teachings relate to systems and methods for provisioning machines having virtual storage resources, and more particularly to platforms and techniques for generating distributions to be installed to the virtual disks associated with machines configured to use virtual storage, including diskless configurations.


BACKGROUND OF RELATED ART

Provisioning platforms are known which allow a systems administrator to select, configure, and push a set of software to new machines on a network. It is a shortcoming in existing provisioning platforms that the systems administrator may have to make manual selections and perform other tasks manually in order to carry out that installation process. In the case of software provisioning to sets of machines which use virtual storage rather than installed local hard disks, the installation difficulties can include the fact that the provisioning server may not be configured to be aware of the assigned location of a possible virtual disk installation. The provisioning server may also not be aware or have the configuration flexibility to generate a distribution which incorporates directory or other configurations to permit an operating system or other installation to operate correctly in machines having no local hard disks and which rely upon virtualized storage. Similar issues can occur in the case of diskless client systems which rely upon network-backed storage.


It may be desirable to provide methods and systems for provisioning machines having virtual storage resources, in which operating system and other distributions can be reliably made to machines lacking permanent local hard disk or other storage.





DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the present teachings and together with the description, serve to explain the principles of the present teachings. In the figures:



FIG. 1 illustrates an overall system for software provisioning on a network, according to various embodiments of the present teachings;



FIG. 2 illustrates an overall system for software provisioning on a network, including provisioning to machines having virtual storage resources, according to various embodiments;



FIG. 3 illustrates an exemplary hardware configuration for a provisioning server and related resources that can be used to configure and install software in a network, according to various embodiments; and



FIG. 4 illustrates a flowchart of overall processing for provisioning machines having virtual storage resources, according to various embodiments.





DESCRIPTION OF EMBODIMENTS

Embodiments of the present teachings relate to systems and methods for provisioning machines having virtual storage resources. More particularly, embodiments relate to platforms and techniques for the identification of machines having virtual disk or other storage resources, and the automatic generation and installation of operating system or other distributions to the virtual disks or other virtual storage resources of those machines. In embodiments, a remote virtual machine installation client on a network can host a virtual disk management engine which detects and registers the configurations, volume assignments, directory structures, mappings, and other settings for the virtual disks associated with the set of target machines. The virtual disk management engine can determine an appropriate disk location and other parameters for the installation of the software distribution, based on the virtual disk configurations operated by the set of target machines. In embodiments, the virtual disk management engine can also generate a distribution to be installed on a diskless machine which operates using electronic memory and using only network-backed storage.


Reference will now be made in detail to exemplary embodiments of the present teachings, which are illustrated in the accompanying drawings. Where possible the same reference numbers will be used throughout the drawings to refer to the same or like parts.



FIG. 1 illustrates an overall provisioning environment 100 consistent with systems and methods for provisioning machines having virtual storage resources, according to various embodiments of the present teachings. Embodiments described herein can be implemented in or supported by the exemplary environment illustrated in FIG. 1. The provisioning environment 100 provides a unified provisioning environment, which comprehensively manages the tasks related to software provisioning.


In particular, the provisioning environment 100 can manage software provisioning using a hierarchy of commands. In exemplary embodiments, the hierarchy can include at least four levels of commands. The lowest level in the hierarchy can comprise distribution commands, which primarily handle base operating system specific tasks of provisioning. The second level can comprise profile commands, which associate a configuration file, such as a kickstart file for Linux or other operating system, with a distribution and optionally allow for customization. The third level comprises system commands, which associate remote systems that are involved with the provisioning of the software. The fourth level comprises repository commands, which address configurations and tasks related to updating the software, remote installation procedures, and optionally customizing the software.


The provisioning environment 100 provides several capabilities and advantages over the known provisioning solutions. For example, the present invention is capable of handling a variety of forms of installations, such as preboot execution environment (“PXE”), virtualization, re-installations, and image installations.


In exemplary aspects, the provisioning environment 100 enables integrating virtualization into a PXE provisioning infrastructure and provides several options to reinstall running machines as well. The provisioning environment 100 can integrate mirroring of package repositories with the provisioning process, so that a provisioning server may serve as a central mirror point of contract for all of an organization's software needs. In aspects, a set of remote mirrored repositories can automatically be used by provisioned systems without additional setup.


Reference will now be made in detail to the exemplary aspects the provisioning environment 100. The provisioning environment 100 can be applied to provisioning any form of software, such as Windows systems, UNIX systems, and Linux systems. In the exemplary description that follows, FIG. 1 is presented to explain the provisioning environment 100 for provisioning software, such as Linux, and Linux based software, such as Fedora and Red Hat Enterprise Linux by Red Hat, Inc.


In provisioning of software such as Linux, many system administrators use what is known as the “kickstart” installation method. Kickstart files are files that specify the intended configuration of the software being provisioned. Kickstart files can be kept on a server and can be read by individual computers during the installation. This installation method allows the use a single or relatively few standard kickstart files to install Linux on multiple machines, making it ideal for network and system administrators.


The kickstart file can be a simple text file, containing a list of items, each identified by a keyword. In general, a kickstart file can be edited with any text editor or word processor that can save files as ASCII text. One skilled in the art will recognize that the present invention may be applied to non-kickstart files in software provisioning. For example, configuration files such as AutoYAST Answer files used in Novell SuSe Linux and Sun Solaris Jumpstart files may also be used by the provisioning environment 100.


Typically, a kickstart file can be copied to the boot disk, or made available on the network. The network-based approach is most commonly used, as most kickstart installations for software provisioning, such as Linux systems, tend to be performed via a network using NFS, FTP, or HTTP on networked computers. Administrators also find it desirable that kickstart installations can be performed using a local CD-ROM, or a local hard drive.


Using kickstart files, a system administrator can create a single file containing the parameters that are needed to complete a typical software installation. For example, kickstart files specify parameters related to: language selection; mouse configuration; keyboard selection; boot loader installation; disk partitioning; network configuration; NIS, LDAP, Kerberos, Hesiod, and Samba authentication; firewall configuration; and package selection.


According to exemplary aspects illustrated in FIG. 1, the provisioning environment 100 can include a provisioning server 102, a code repository 104 which provides access to distributions 106 and 108, a set of installation templates 110, a set of exception plugins 112, a helper client 114 running on target machines 116 in a network 115, a provisioning database 120 which comprises a distribution tree list 122 and template list 124. Each of these components will now be further described.


The provisioning server (from herein referred to as a “cobbler”) 102 is responsible for: serving as a extensible markup language remote procedure call (XMLRPC) handler; linking to or mirroring install distribution trees and a configuration database; hosting kickstart templates; hosting plugins, generating installation images, and the like. The cobbler server 102 can be implemented as software, such as Python code, installed on a boot server machine and provides a command line interface for configuration of the boot server. In addition, the cobbler server 102 can make itself available as a Python application programming interface (API) for use by higher level management software (not shown). The cobbler server 102 supports provisioning via PXE, image (ISO) installation, virtualization, re-provisioning. As will be described later, the last two modes are performed with the assistance of a helper client 114.


The code repository 104 is responsible for hosting distributions 106 and 108. The code repository 104 may be implemented using well known components of hardware and software. Additionally, the code repository 104 can be or include one or more repositories hosting distributions. The distributions 106 and 108 can include bundles of software that is already compiled and configured. The distributions 106 and 108 may be in the form of either rpm, deb, tgz, msi, exe formats, and the like. For example, as Linux distributions, the distributions 106 and 108 are bundles of software that comprise the Linux kernel, the non-kernel parts of the operating system, and assorted other software. The distributions 106 and 108 can take a variety of forms, from fully-featured desktop and server operating systems to minimal environments.


In exemplary aspects, the installation templates 110 are any data structure or processing element that can be combined with a set of installation configurations and processed to produce a resulting configuration file, such as a kickstart file.


In exemplary aspects, exception plugins 112 is software that interacts with cobbler server 102 to customize the provisioning of software. In general, the exceptions plugins 112 are intended to address infrequent customization needs.


In exemplary aspects, the helper client (known as “koan”, which stands for “kickstart-over-a-network”) 114 can assist the cobbler server 102 during the provisioning processes. The koan 114 can allow for both network provisioning of new virtualized guests and destructive provisioning of any existing system. When invoked, the koan 114 can request profile information from a remote boot server that has been configured with the cobbler server 102. In some aspects, what the koan 114 does with the profile data depends on whether it was invoked with -virt or -replace-self.


In exemplary aspects, the koan 114 can enable replacing running systems as well as installing virtualized profiles. The koan 114 can also be pushed out to systems automatically from the boot server. In some aspects, the koan client 114 is also written in Python code to accommodate a variety of operating systems, machine architectures, etc.


In exemplary aspects, the network 115 can include a number of the target machines 116. The target machines 116 can represent the particular machines to which software provisioning is directed. The target machines 116 may represent a wide variety of computing devices, such as personal computers, servers, laptop computers, personal mobile devices, and the like. In some aspects, the target machines 116 can represent distributed computing environments such as cloud computing environments. Although FIG. 1 shows several of the target machines 116, the provisioning environment 100 can be capable of managing a wide range of environments, such as datacenters with thousands of machines or server pools with just a few machines. Additionally, the cobbler server 102 can be connected to multiple networks 115.


In exemplary aspects, the provisioning database 120 can serve as a data storage location for holding data used by the cobbler server 102. For example, as shown, the provisioning database 120 can comprise the distribution tree list 122 and the template list 124. The distribution tree list 122 can provide an inventory of the distributions 106 and 108 that are hosted or mirrored by the cobbler server 102. The template list 124 can provide an inventory of the templates 110 that are hosted by the cobbler server 102.


As noted above, the cobbler server 102 can manage provisioning using a hierarchical concept of distribution commands, profile commands, system commands, and repository commands. This framework enables the cobbler server 102 to abstract the differences between multiple provisioning types (installation, reinstallation, and virtualization) and allows installation of all three from a common platform. This hierarchy of commands also permits the cobbler server 102 to integrate software repositories 126 with the provisioning process, thus allowing systems to be configured as a mirror for software updates and third party content as well as distribution content.


Distributions can contain information about base operating system tasks, such as what kernel and initial ramdisk (“initrd”) are used in the provisioning, along with other information, such as required kernel parameters. Profiles associate one of the distributions 106 and 108 with a kickstart file and optionally customize it further, for example, using plugins 112. Systems commands associate a hostname, IP, or MAC with a distribution and optionally customize the profile further. Repositories contain update information, such as yum mirror information that the cobbler server 102 uses to mirror repository 104. The cobbler server 102 can also manage (generate) DHCP configuration files using the templates 110.


In exemplary aspects, the cobbler server 102 can use a provisioning environment that is fully templated, allowing for kickstarts and PXE files to be customized by the user. The cobbler server 102 uses the concept of “profiles” as an intermediate step between the operating system and the installed system. A profile is a description of what a system does rather than the software to be installed. For instance, a profile might describe a virtual web server with X amount of RAM, Y amounts of disk space, running a Linux distribution Z, and with an answer file W.


In exemplary aspects, the cobbler server 102 can provide a command line interface to configure a boot server in which it is installed. For example, the format of the cobbler server 102 commands can be generally in the format of: cobbler command [subcommand] [-arg1=][-arg 2=]. Thus, a user can specify various aspects of software provisioning via a single interface, such as a command line interface or other known interface. Examples of exemplary cobbler commands can be found in U.S. patent application Ser. No. 11/763,315, U.S. Patent Application Publication No. 2008/0288938 and U.S. patent application Ser. No. 11/763,333, U.S. Patent Publication No. 2008/0288939, the disclosures of which are incorporated herein, in their entirety, by reference.


According to exemplary aspects, a user can use various commands of the provisioning environment 100 to specify distributions and install trees hosted by the code repository 104, such as a distribution from the distributions 106 or 108. A user can add or import a distribution or import it from installation media or an external network location.


According to exemplary aspects, in order to import a distribution, the cobbler server 102 can auto-add distributions and profiles from remote sources, whether this is an installation media (such as a DVD), an NFS path, or an rsync mirror. When importing a rsync mirror, the cobbler server 102 can try to detect the distribution type and automatically assign kickstarts. By default in some embodiments, the cobbler server can provision by erasing the hard drive, setting up eth0 for DHCP, and using a default password. If this is undesirable, an administrator may edit the kickstart files in /etc/cobbler to do something else or change the kickstart setting after the cobbler server 102 creates the profile.


According to exemplary aspects, a user may map profiles to the distributions and map systems to the profiles using profile commands and systems commands of the provisioning environment 100. A profile associates a distribution to additional specialized options, such as a kickstart automation file. In the cobbler server 102, profiles are the unit of provisioning and at least one profile exists for every distribution to be provisioned. A profile might represent, for instance, a web server or desktop configuration.


According to exemplary aspects, a user can map systems to profiles using system commands. Systems commands can assign a piece of hardware with cobbler server 102 to a profile. Systems can be defined by hostname, Internet Protocol (IP) address, or MAC address. When available, use of the MAC address to assign systems can be preferred.


According to exemplary aspects, the user can map repositories and profiles using repository commands. Repository commands can address configurations and tasks related to updating the software, remote installation procedures, and optionally customizing the software. These repository commands can also specify mirroring of the provisioned software to remote servers. Repository mirroring can allow the cobbler server 102 to not only mirror/install the trees 106 and 108, but also optional packages, third party content, and updates. Mirroring can be useful for faster, more up-to-date installations and faster updates, or providing software on restricted networks. The cobbler server 102 can also include other administrative features, such as allowing the user to view their provisioning configuration or information tracking the status of a requested software installation.


According to exemplary aspects, a user can utilize commands to create a provisioning infrastructure from a distribution mirror. Then a default PXE configuration is created, so that by default systems will PXE boot into a fully automated install process for that distribution. The distribution mirror can be a network rsync mirror or a mounted DVD location.


According to exemplary aspects, the administrator uses a local kernel and initrd file (already downloaded), and shows how profiles would be created using two different kickstarts—one for a web server configuration and one for a database server. Then, a machine can be assigned to each profile.


According to exemplary aspects, a repo mirror can be set up for two repositories, and create a profile that will auto install those repository configurations on provisioned systems using that profile.


According to exemplary aspects, in addition to normal provisioning, the cobbler server 102 can support yet another option, called “enchant”. Enchant takes a configuration that has already been defined and applies it to a remote system that might not have the remote helper program installed. Users might want to use this command to replace a server that is being repurposed, or when no PXE environment can be created. Thus, the enchant option allows the remote the koan client 114 to be executed remotely from the cobbler server 102.


According to aspects, if the cobbler server 102 is configured to mirror certain repositories, the cobbler server 102 can then be used to associate profiles with those repositories. Systems installed under those profiles can be auto configured to use these repository mirrors in commands and, if supported, these repositories can be leveraged. This can be useful for a large install base, fast installation and upgrades for systems are desired, or software not in a standard repository exists and provisioned systems are desired to know about that repository.


According to exemplary aspects, the cobbler server 102 may also keep track of the status of kickstarting machines. For example, the “cobbler status” will show when the cobbler server 102 thinks a machine started kickstarting and when it last requested a file. This can be a desirable way to track machines that may have gone inactive during kickstarts. The cobbler server 102 can also make a special request in the post section of the kickstart to signal when a machine is finished kickstarting.


According to exemplary aspects, for certain commands, the cobbler server 102 will create new virtualized guests on a machine in accordance to the orders from the cobbler server 102. Once finished, an administrator may use additional commands on the guest or other operations. The cobbler server 102 can automatically name domains based on their MAC addresses. For re-kickstarting, the cobbler server 102 can reprovision the system, deleting any current data and replacing it with the results of a network install.


According to exemplary aspects, the cobbler server 102 can configure boot methods for the provisioning requested by the user. For example, the cobbler server 102 can configure a PXE environment, such as a network card BIOS. Alternatively, the cobbler server 102 can compile and configure information for koan client 104. The cobbler server 102 can also optionally configured DHCP and DNS configuration information.


According to exemplary aspects, the cobbler server 102 can serve the request of the koan client 114. The koan client 114 can acknowledge the service of information of the cobbler server 102 and then can initiate installation of the software being provisioned. Additionally, the koan client 114 can either install the requested software, e.g., replace the existing operating system, or install a virtual machine.



FIG. 2 illustrates an overall network 100 consistent with systems and methods for provisioning machines having virtual storage resources, according to various aspects of the present teachings in further regards. In embodiments as shown, remote virtual machine installation client 244 can manage the instantiation and provisioning of a set of targets 116, some or all of which can be configured with a virtual disk 222. The virtual disk 222 of each of the targets 116 equipped with that type of virtual storage resources can be managed by a virtual storage logic or module in each of the targets 116, which maps or translates requests for directories, files, disk locations, or other storage access to a physical virtual disk address or location in set of shared storage 226. Set of shared storage 226 can be or include a set of hard disk drives, hard disk drive arrays, databases, electronic storage, optical storage, tape storage, RAID (redundant array of independent disk) arrays, backup storage, or other storage resources, media, or assets.


In embodiment, one or more remote virtual machine installation client 114 can host or contain a virtual disk management engine 224 which interfaces with the virtual disk 222 and/or set of shared storage 226 to install distribution(s) 106, 108 to targets 116. In embodiments, virtual disk management engine 224 can interact with the virtual disk logic of each of the targets 116 to determine an address, location, directory, or other access parameter to write and install the operating system or other distribution(s) 106, 108 to virtual disk 222 and/or set of shared storage 226. For instance, virtual disk management engine 224 can determine that the operating system kernel should be installed on the host in a particular directory of one of targets 116. Other mappings, addresses, or references to storage locations are possible.


Virtual disk management engine 224 can initiate the imaging and installation of distribution(s) 106, 108 to each of targets 116 without a necessity for intervention by a systems administrator or other user. In embodiments as shown, virtual disk management engine 224 can likewise manage the installation of one or more of distribution(s) 106, 108 to a diskless machine 228. Diskless machine 228 can run primarily based on electronic memory, requiring only network-backed storage 230 as a storage option for configuration or other data. In embodiments, distribution(s) 106, 108 to a diskless machine 228 can include an installation to electronic memory of that machine, and/or to network-backed storage 230.


It may be noted that in embodiments, the configuration and type of virtual disk 222 associated with different ones of targets 116 can be different or variable. Virtual disk management engine 224 can identify types and/or configurations of different types of virtual storage, and manage the provisioning of the respective machines accordingly. For example, different ones of virtual disk 222 for different targets 116 can have different sizes. In embodiments, one or more of targets 116 can have a varied number of virtual disks, which can in embodiments be of different sizes. According to embodiments in further regards, a varied number of virtual disks in varied sizes can be associated with a virtual profile or system yet to be instantiated. According to embodiments, virtual disk 222 can be installed to the file system, an LVM (logical volume manager) container, or a partition on an associated one of targets 116 or other gues. In embodiments, virtual disk management engine 224 can coordinate the provisioning of targets 116 having those variable virtual storage types, and still permit consistent provisioning of desired targets 116. A systems administrator or other user therefore need not manually intervene to detect and/or assign different parameters to targets 116 having different types or configurations of virtual disk 222, as those machines are operated or provisioned.



FIG. 3 illustrates an exemplary diagram of hardware and other resources that can be incorporated in the cobbler server 102 configured to communicate with the network 115 and the target machines 116 in network 115, according to embodiments. In embodiments as shown, the cobbler server 102 can comprise a processor 300 communicating with memory 302, such as electronic random access memory, operating under control of or in conjunction with operating system 306. Operating system 306 can be, for example, a distribution of the Linux™ operating system, the Unix™ operating system, or other open-source or proprietary operating system or platform. Processor 300 also communicates with the provisioning database 120, such as a database stored on a local hard drive. While illustrated as a local database in the cobbler server 102, the provisioning database 120 can be separate from the cobbler server 102 and the cobbler server 102 can be configured to communicate with the remote provisioning database 120.


Processor 300 further communicates with network interface 304, such as an Ethernet or wireless data connection, which in turn communicates with one or more networks 115, such as the Internet or other public or private networks. Processor 300 also communicates with the provisioning database 120, the virtual disk management engine 224 and other resources to execute control logic and perform the storage allocation and provisioning processes described herein. Other configurations of the cobbler server 102, associated network connections, and other hardware and software resources are possible.


While FIG. 3 illustrates the cobbler server 102 as a standalone system comprising a combination of hardware and software, the cobbler server 102 can also be implemented as a software application or program capable of being executed by a convention computer platform. Likewise, the cobbler server 102 can also be implemented as a software module or program module capable of being incorporated in other software applications and programs. In either case, the cobbler server 102 can be implemented in any type of conventional proprietary or open-source computer language.



FIG. 4 illustrates overall provisioning and storage allocation processing in systems and methods for provisioning machines having virtual storage resources, according to various embodiments of the present teachings. In 402, processing can begin. In 404, a software provisioning process can be initiated for a set of targets 106 each having a virtual disk 222 via a remote virtual machine installation client 114 communicating with a provisioning or cobbler server 102. In embodiments, the provisioning process can be initiated after receipt of an initiation message or network process, for example, submitted by a systems administrator or other user. In 406, configuration data for the targets 106 can be received in cobbler server 102 via remote virtual machine installation client 114. In 408, the cobbler server 102 can identify the virtual disk configuration and related information for each of targets 116 and any different types of virtual disk 222. In embodiments, volume size, file system type or format, platter number, magnetic or other media density, data rates, physical interface types (e.g., SATA or other), error correction schemes, and other parameters can be detected. In 410, cobbler server 102 can access installation templates 110 and generate distribution(s) 106, 108 based on the detected configuration information.


In 412, the cobbler server 102 can initiate the provisioning process to targets 116. In 414, distribution(s) 106, 108 can be installed to virtual disk 222 of each target via the virtual disk management engine 224. In 416, distribution(s) 106, 108 can be installed to one or more diskless machine 228, as appropriate. In 418, an installation log of the set of installed distribution(s) 106, 108 can be stored to provisioning database 120, or otherwise. In 420, processing can repeat, return to a prior processing point, jump to a further processing point, or end.


The foregoing description is illustrative, and variations in configuration and implementation may occur to persons skilled in the art. For example, while embodiments have been described in which one remote virtual machine installation client 114 accesses and manages the provisioning of one of targets 116 with one associated virtual disk 222, in embodiments one koan client and/or virtual disk management engine 224 can manage the provisioning of multiple target machines and/or virtual disks. For further example, while embodiments have been described in which each machine in targets 116 has one virtual disk 222, in embodiments, a machine in targets 116 can have multiple virtual disks associated with that client or other device. Yet further, while embodiments have been described in which targets 116 are configured with at least one virtual disk 222, in embodiments, one or more of targets 116 can also host local hard disk or other storage. Other resources described as singular or integrated can in embodiments be plural or distributed, and resources described as multiple or distributed can in embodiments be combined. The scope of the present teachings is accordingly intended to be limited only by the following claims.

Claims
  • 1. A method comprising: receiving, by a server, a request to provision a software distribution associated with a machine that has a virtual storage resource, wherein the machine is diskless and uses a network-backed storage;obtaining, by the server, configuration data, a volume assignment, a directory structure detected for the virtual storage resource, and a map of the directory structure of the virtual storage resource to a set of shared physical storage resources accessed by a plurality of machines;selecting a template file, from a plurality of template files, comprising parameters associated with configuring the software distribution in view of a file system type of the virtual storage resource and a volume size of the virtual storage resource;generating, by the server, the software distribution in view of the parameters of the template file, configuration data, the volume assignment, the directory structure detected for the virtual storage resource, and the map of the directory structure of the virtual storage resource, the software distribution to be installed on the virtual storage resource;determining, by a processor of the server, a location to install the generated software distribution on the virtual storage resource in view of the configuration data, the volume assignment, the directory structure detected for the virtual storage resource, and the map of the directory structure of the virtual storage resource to the set of shared physical storage resources accessed by the plurality of machines;erasing a physical storage resource associated with the determined location in view of the request to provision the software distribution; andprovisioning the software distribution in view of the determined location and a hierarchy of commands, wherein the hierarchy of commands comprises: a first level of distribution commands to handle distribution tasks relating to an operating system of the server;a second level of profile commands to associate the template file with the software distribution;a third level of system commands to associate remote systems to the software distribution, wherein each of the remote systems is specified by an address; anda fourth level of repository commands to perform, in view of the software distribution, at least one of configuration or updating software on the remote systems.
  • 2. The method of claim 1, wherein the virtual storage resource comprises a virtual disk associated with the machine.
  • 3. The method of claim 2, wherein at least a portion of the software distribution is installed to the virtual disk.
  • 4. The method of claim 2, wherein the virtual storage resource comprises a plurality of virtual disks.
  • 5. The method of claim 1, wherein the parameters of the template file relate to at least one of language selection, boot loader installation, disk partitioning, or firewall configuration.
  • 6. A system comprising: a network device; anda processor, operatively coupled with the network device, to: receive a request to provision a software distribution associated with a machine that has a virtual storage resource, wherein the machine is diskless and uses a network-backed storage;obtain, via the network device, configuration data, a volume assignment, a directory structure detected for the virtual storage resource and a map of the directory structure of the virtual storage resource to a set of shared physical storage resources accessed by a plurality of machines;select a template file, from a plurality of template files, comprising parameters associated with configuring the software distribution in view of a file system type of the virtual storage resource and a volume size of the virtual storage resource;generate the software distribution in view of the parameters of the template file, configuration data, the volume assignment, the directory structure detected for the virtual storage resource, and the map of the directory structure of the virtual storage resource, the software distribution to be installed on the virtual storage resource;determine a location to install the generated software distribution on the virtual storage resource in view of the configuration data, the volume assignment, the directory structure detected for the virtual storage resource, and the map of the directory structure of the virtual storage resource to the set of shared physical storage resources accessed by the plurality of machines;erase a physical storage resource associated with the determined location in view of the request to provision the software distribution; andprovision the software distribution in view of the determined location and a hierarchy of commands, wherein the hierarchy of commands comprises: a first level of distribution commands to handle distribution tasks relating to an operating system of the server;a second level of profile commands to associate the template file with the software distribution;a third level of system commands to associate remote systems to the software distribution, wherein each of the remote system is specified by an address; anda fourth level of repository commands to perform, in view of the software distribution, at least one of configuration or updating software on the remote systems.
  • 7. The system of claim 6, wherein the virtual storage resource comprises a virtual disk associated with the machine.
  • 8. The system of claim 7, wherein at least a portion of the software distribution is installed to the virtual disk.
  • 9. The system of claim 7, wherein the virtual storage resource comprises a plurality of virtual disks.
  • 10. A method comprising: receiving a request for data associated with a virtual storage resource of a machine where software is to be provisioned, wherein the machine is diskless and uses a network-backed storage;selecting a template file, from a plurality of template files, comprising parameters associated with configuring a software distribution in view of a file system type of the virtual storage resource and a volume size of the virtual storage resource;detecting, by a processor, configuration data, a volume assignment, a directory structure, and a map of the directory structure of the virtual storage resource to a set of shared physical storage resources accessed by a plurality of machines for the virtual storage resource, wherein the parameters of the template file, the detected configuration data, the detected volume assignment, the detected directory structure, and the detected map are for generating the software distribution to install on the virtual storage resource and for determining a location to install the generated software distribution on the virtual storage resource;erasing a physical storage resource associated with the determined location in view of the request associated with the software to be provisioned; andprovisioning the software distribution in view of the determined location and a hierarchy of commands, wherein the hierarchy of commands comprises: a first level of distribution commands to handle distribution tasks relating to an operating system of the server;a second level of profile commands to associate the template file with the software distribution;a third level of system commands to associate remote systems to the software distribution, wherein each of the remote systems is specified by an address; anda fourth level of repository commands to perform, in view of the software distribution, at least one of configuration or updating software on the remote systems.
  • 11. The method of claim 10, wherein the virtual storage resource comprises a virtual disk associated with a machine.
  • 12. The method of claim 11, wherein at least a portion of the software distribution is installed to the virtual disk.
  • 13. The method of claim 11, wherein the virtual storage resource comprises a plurality of virtual disks.
US Referenced Citations (188)
Number Name Date Kind
5787246 Lichtman et al. Jul 1998 A
5835719 Gibson et al. Nov 1998 A
5838916 Domenikos Nov 1998 A
5948062 Tzelnic et al. Sep 1999 A
6101508 Wolff Aug 2000 A
6105100 Dean et al. Aug 2000 A
6212585 Chrabaszcz Apr 2001 B1
6243747 Lewis et al. Jun 2001 B1
6272536 van Hoff et al. Aug 2001 B1
6381742 Forbes et al. Apr 2002 B2
6397242 Devine et al. May 2002 B1
6415289 Williams et al. Jul 2002 B1
6438711 Woodruff Aug 2002 B2
6516427 Keyes et al. Feb 2003 B1
6526442 Stupek et al. Feb 2003 B1
6550021 Dalphy et al. Apr 2003 B1
6557169 Erpeldinger Apr 2003 B1
6594664 Estrada et al. Jul 2003 B1
6625742 Owhadi et al. Sep 2003 B1
6686838 Rezvani et al. Feb 2004 B1
6751659 Fenger et al. Jun 2004 B1
6757837 Platt et al. Jun 2004 B1
6769022 DeKoning et al. Jul 2004 B1
6779004 Zintel Aug 2004 B1
6845464 Gold Jan 2005 B2
6865737 Lucas et al. Mar 2005 B1
6941518 French et al. Sep 2005 B2
6947939 Fujibayashi et al. Sep 2005 B2
6966058 Earl et al. Nov 2005 B2
6986033 Miyamoto et al. Jan 2006 B2
7013461 Hellerstein et al. Mar 2006 B2
7051101 Dubrovsky et al. May 2006 B1
7058797 Miyamoto et al. Jun 2006 B2
7107330 Hamilton et al. Sep 2006 B1
7107385 Rajan et al. Sep 2006 B2
7133822 Jacobson Nov 2006 B1
7165109 Chiloyan et al. Jan 2007 B2
7185071 Berg et al. Feb 2007 B2
7200845 Morrison et al. Apr 2007 B2
7228379 Bress Jun 2007 B2
7330967 Pujare et al. Feb 2008 B1
7340637 Nagoya Mar 2008 B2
7350112 Fox et al. Mar 2008 B2
7356679 Le et al. Apr 2008 B1
7395322 Harvey et al. Jul 2008 B2
7506040 Rabe et al. Mar 2009 B1
7506151 Miyamoto et al. Mar 2009 B2
7516218 Beason Apr 2009 B2
7519691 Nichols et al. Apr 2009 B2
7574481 Moore et al. Aug 2009 B2
7577722 Khandekar Aug 2009 B1
7600005 Jamkhedkar et al. Oct 2009 B2
7606868 Le et al. Oct 2009 B1
7640325 DeKoning et al. Dec 2009 B1
7673130 Miyamoto et al. Mar 2010 B2
7681080 Abali et al. Mar 2010 B2
7716316 Nichols et al. May 2010 B2
7734717 Saarimaki et al. Jun 2010 B2
7814554 Ragner Oct 2010 B1
7827261 Griswold et al. Nov 2010 B1
7831692 French et al. Nov 2010 B2
7831997 Eldar et al. Nov 2010 B2
7937437 Fujii May 2011 B2
7971047 Vlaovic Jun 2011 B1
8000451 Aubuchon Aug 2011 B1
8166128 Faulkner et al. Apr 2012 B1
8776050 Plouffe Jul 2014 B2
9003406 Hodge Apr 2015 B1
9015712 Hodge Apr 2015 B1
20020062259 Katz et al. May 2002 A1
20020078186 Engel et al. Jun 2002 A1
20020095522 Hayko et al. Jul 2002 A1
20020138567 Ogawa Sep 2002 A1
20020162028 Kennedy Oct 2002 A1
20030005097 Barnard et al. Jan 2003 A1
20030022657 Herschberg et al. Jan 2003 A1
20030055919 Fong et al. Mar 2003 A1
20030069884 Nair et al. Apr 2003 A1
20030069946 Nair et al. Apr 2003 A1
20030070110 Aija et al. Apr 2003 A1
20030074549 Paul et al. Apr 2003 A1
20030097422 Richards et al. May 2003 A1
20030110173 Marsland Jun 2003 A1
20030119480 Mohammed Jun 2003 A1
20030126585 Parry Jul 2003 A1
20030130832 Schulter et al. Jul 2003 A1
20030130833 Brownell et al. Jul 2003 A1
20030195921 Becker et al. Oct 2003 A1
20030212992 Ronning et al. Nov 2003 A1
20030233648 Earl et al. Dec 2003 A1
20040006616 Quinn et al. Jan 2004 A1
20040015831 Bowhill Jan 2004 A1
20040015957 Zara et al. Jan 2004 A1
20040019876 Dravida et al. Jan 2004 A1
20040024984 Lanzatella et al. Feb 2004 A1
20040044643 deVries et al. Mar 2004 A1
20040054789 Breh et al. Mar 2004 A1
20040059703 Chappell et al. Mar 2004 A1
20040064501 Jan et al. Apr 2004 A1
20040128375 Rockwell Jul 2004 A1
20040143664 Usa et al. Jul 2004 A1
20040167976 Hwang et al. Aug 2004 A1
20040215755 O'Neill Oct 2004 A1
20040223469 Bahl et al. Nov 2004 A1
20050028025 Zalewski et al. Feb 2005 A1
20050050175 Fong et al. Mar 2005 A1
20050114474 Anderson et al. May 2005 A1
20050125525 Zhou et al. Jun 2005 A1
20050177829 Vishwanath Aug 2005 A1
20050182796 Chu et al. Aug 2005 A1
20050198629 Vishwanath Sep 2005 A1
20050223374 Wishart et al. Oct 2005 A1
20060041767 Maxwell et al. Feb 2006 A1
20060080659 Ganji Apr 2006 A1
20060095230 Grier et al. May 2006 A1
20060095702 Hickman et al. May 2006 A1
20060155857 Feenan et al. Jul 2006 A1
20060173912 Lindvall et al. Aug 2006 A1
20060174018 Zhu et al. Aug 2006 A1
20060190575 Harvey et al. Aug 2006 A1
20060190773 Rao et al. Aug 2006 A1
20060200658 Penkethman Sep 2006 A1
20060215575 Horton et al. Sep 2006 A1
20060218544 Chakraborty et al. Sep 2006 A1
20060230165 Zimmer et al. Oct 2006 A1
20060282479 Johnson et al. Dec 2006 A1
20070015538 Wang Jan 2007 A1
20070067419 Bennett Mar 2007 A1
20070074290 Kobayashi et al. Mar 2007 A1
20070101118 Raghunath et al. May 2007 A1
20070118654 Jamkhedkar et al. May 2007 A1
20070168721 Luiro et al. Jul 2007 A1
20070169093 Logan et al. Jul 2007 A1
20070192158 Kim Aug 2007 A1
20070204338 Aiello et al. Aug 2007 A1
20070226810 Hotti Sep 2007 A1
20070244996 Ahmed et al. Oct 2007 A1
20070276905 Durand et al. Nov 2007 A1
20070288612 Hall Dec 2007 A1
20070294376 Ayachitula et al. Dec 2007 A1
20070299951 Krithivas Dec 2007 A1
20080028048 Shekar et al. Jan 2008 A1
20080040452 Rao et al. Feb 2008 A1
20080046708 Fitzgerald et al. Feb 2008 A1
20080059959 Chen et al. Mar 2008 A1
20080086614 Canis Apr 2008 A1
20080130639 Costa-Requena et al. Jun 2008 A1
20080134175 Fitzgerald et al. Jun 2008 A1
20080189693 Pathak Aug 2008 A1
20080196043 Feinleib et al. Aug 2008 A1
20080222366 Hieda Sep 2008 A1
20080235266 Huang et al. Sep 2008 A1
20080235361 Crosbie et al. Sep 2008 A1
20080244325 Tyulenev Oct 2008 A1
20080270674 Ginzton Oct 2008 A1
20080294777 Karve et al. Nov 2008 A1
20080301666 Gordon et al. Dec 2008 A1
20080313716 Park Dec 2008 A1
20080320110 Pathak Dec 2008 A1
20090007091 Appiah et al. Jan 2009 A1
20090055901 Kumar et al. Feb 2009 A1
20090064132 Suchy et al. Mar 2009 A1
20090089567 Boland et al. Apr 2009 A1
20090089852 Randolph et al. Apr 2009 A1
20090106291 Ku et al. Apr 2009 A1
20090129597 Zimmer et al. May 2009 A1
20090132682 Counterman May 2009 A1
20090132710 Pelley May 2009 A1
20090158148 Vellanki et al. Jun 2009 A1
20090158272 El-Assir et al. Jun 2009 A1
20090164522 Fahey Jun 2009 A1
20090165099 Eldar et al. Jun 2009 A1
20090172430 Takenouchi Jul 2009 A1
20090240835 Adelman et al. Sep 2009 A1
20090259665 Howe et al. Oct 2009 A1
20090265707 Goodman et al. Oct 2009 A1
20090282404 Khandekar et al. Nov 2009 A1
20090285199 Strahs et al. Nov 2009 A1
20100023740 Moon et al. Jan 2010 A1
20100100876 Glover et al. Apr 2010 A1
20100217837 Ansari et al. Aug 2010 A1
20100220584 DeHaan et al. Sep 2010 A1
20100223504 DeHaan et al. Sep 2010 A1
20100223608 DeHaan et al. Sep 2010 A1
20100223609 DeHaan et al. Sep 2010 A1
20100262558 Edwards et al. Oct 2010 A1
20110153697 Nickolov et al. Jun 2011 A1
20130132950 McLeod May 2013 A1
Non-Patent Literature Citations (53)
Entry
Blomer, Jakob, et al. “Distributing LHC application software and conditions databases using the CernVM file system.” Journal of Physics: Conference Series. vol. 331. No. 4. IOP Publishing, 2011.pp. 1-6.
Zhou, Yuezhi, Yaoxue Zhang, and Yinglian Xie. “Virtual disk based centralized management for enterprise networks.” Proceedings of the 2006 SIGCOMM workshop on Internet network management. ACM, 2006.pp. 23-28.
Zhang, Yaoxue, and Yuezhi Zhou. “Separating computation and storage with storage virtualization.” Computer Communications 34.13 (2011): pp. 1539-1548.
Doc Searls “Linux for Suits”, 2005, Specialized System Consultants Inc., vol. 2005.
Grosse, “Repository Mirroring”, 1995.
Butt et al., “Automated Installation of Large-Scale Linux Networks”, 2000.
Agarwalla, “Automating Provisioning of Complete Software Stack in a Grid Environment”, 2004.
Anderson et al., “Technologies for Large-Scale Configuration Management”, Dec. 9, 2002.
eBook “Microsoft System Management Server 2003 Administrator's companion”, Microsoft Press, c2004, Ch. 13, Patch Management, pp. 471-507.
HP Storage Essentials SRM 6.0 Installation Guide. Jan. 2008. HP. 1st ed. Part No. T4283-96113. pp. 1-5, 97-136, 219-228.
HP Storage Essentials SRM 6.0 User Guide, Jan. 2008. HP. 1st ed. Part No. T4238-96114, pp. 1-83.
Michael DeHaan. “Unfiled Provisioning”, 2007.
Michael DeHaan. “Provisioning With Cobbler”, 2007.
Tan et al. “A WBEM Basked Disk Array Management Provider”. 2005. IEEE. 2005 International Conference on Cyberworlds.
Lovelace et al. Managing Disk Subsystems using IBM TotalStorage Productivity Center. Sep. 2005. IBM. 2nd ed. SG24-7097-01. pp. 1-42.
DeHaan, “Systems and Methods for Message-Based Installation Management Using Message Bus”, U.S. Appl. No. 12/495,077, filed Jun. 30, 2009.
Henson, “Systems and Methods for Integrating Storage Resources from Storage Area Network in Machine Provisioning Platform”, U.S. Appl. No. 12/628,041, filed Nov. 30, 2009.
Henson, “Systems and Methods for Mounting Specified Storage Resources from Storage Area Network in Machine Provisioning Platform”, U.S. Appl. No. 12/627,988, filed Nov. 30, 2009.
DeHaan, “Systems and Methods for Providing Configuration Management Services from a Provisioning Server”, U.S. Appl. No. 12/414,941, filed Mar. 31, 2009.
DeHaan, “Systems and Methods for Retiring Target Machines by a Provisioning Server”, U.S. Appl. No. 12/475,427, filed May 29, 2009.
DeHaan, “Methods and Systems for Centrally Managing Multiple Provisioning Servers”, U.S. Appl. No. 12/201,193, filed Aug. 29, 2008.
DeHaan, “Methods and Systems for Assigning Provisioning Servers in a Software Provisioning Environment”, U.S. Appl. No. 12/201,646, filed Aug. 29, 2008.
DeHaan, “Methods and Systems for Providing Remote Software Provisioning to Machines”, U.S. Appl. No. 12/195,633, filed Aug. 21, 2008.
DeHaan, “Systems and Methods for Storage Allocation in Provisioning of Virtual Machines”, U.S. Appl. No. 12/202,178, filed Aug. 29, 2008.
DeHaan, “Methods and Systems for Providing Customized Actions Related to Software Provisioning”, U.S. Appl. No. 12/200,552, filed Aug. 28, 2008.
DeHaan, “Methods and Systems for Automatically Locating a Provisioning Server”, U.S. Appl. No. 12/198,290, filed Aug. 26, 2008.
DeHaan, “Methods and Systems for Managing Access in a Software Provisioning Environment”, U.S. Appl. No. 12/201,832, filed Aug. 29, 2008.
DeHaan, “Methods and Systems for Importing Software Distributions in a Software Provisioning Environment”, U.S. Appl. No. 12/200,631, filed Aug. 28, 2008.
DeHaan et al., “Methods and Systems for Managing Network Connections Associated with Provisioning Objects in a Software Provisioning Environment”, U.S. Appl. No. 12/239,690, filed Sep. 26, 2008.
DeHaan, “Methods and Systems for Monitoring Software Provisioning”, U.S. Appl. No. 12/198,378, filed Aug. 26, 2008.
DeHaan, “Systems and Methods for Software Provisioning in Multiple Network Configuration Environment”, U.S. Appl. No. 12/202,194, filed Aug. 29, 2008.
DeHaan, “Systems and Methods for Differential Software Provisioning on Virtual Machines Having Different Configurations”, U.S. Appl. No. 12/202,019, filed Aug. 29, 2008.
DeHaan, “Methods and Systems for Automatically Registering New Machines in a Software Provisioning Environment”, U.S. Appl. No. 12/194,754, filed Aug. 20, 2008.
DeHaan et al., “Methods and Systems for Managing Network Connections in a Software Provisioning Environment”, U.S. Appl. No. 12/239,681, filed Sep. 26, 2008.
DeHaan et al., “Methods and Systems for Providing a Rescue Environment in a Software Provisioning Environment”, U.S. Appl. No. 12/325,007, filed Nov. 28, 2008.
DeHaan et al., “Systems and Methods for Monitoring Hardware Resources in a Software Provisioning Environment”, U.S. Appl. No. 12/325,056, filed Nov. 28, 2008.
DeHaan, “Methods and Systems for Providing Power Management Services in a Software Provisioning Environment”, U.S. Appl. No. 12/277,518, filed Nov. 25, 2008.
DeHaan et al., “Methods and Systems for Providing Hardware Updates in a Software Provisioning Environment”, U.S. Appl. No. 12/324,991, filed Nov. 28, 2008.
DeHaan et al., “Methods and Systems for Supporting Multiple Name Servers in a Software Provisioning Environment”, U.S. Appl. No. 12/324,572, filed Nov. 26, 2008.
DeHaan et al., “Methods and Systems for Secure Gated File Deployment Associated with Provisioning”, U.S. Appl. No. 12/393,754, filed Feb. 26, 2009.
DeHaan, “Systems and Methods for Integrating Software Provisioning and Configuration Management”, U.S. Appl. No. 12/395,379, filed Feb. 27, 2009.
DeHaan, “Systems and Methods for Abstracting Software Content Management in a Software Provisioning Environment”, U.S. Appl. No. 12/395,273, filed Feb. 27, 2009.
DeHaan et al., “Systems and Methods for Providing a Library of Virtual Images in a Software Provisioning Environment”, U.S. Appl. No. 12/395,351, filed Feb. 27, 2009.
DeHaan et al., “Systems and Methods for Inventorying Un-Provisioned Systems in a Software Provisioning Environment”, U.S. Appl. No. 12/391,588, filed Feb. 24, 2009.
DeHaan et al., “Systems and Methods for Managing Configurations of Storage Devices in a Software Provisioning Environment”, U.S. Appl. No. 12/393,613, filed Feb. 26, 2009.
DeHaan et al., “Systems and Methods for Collecting and Altering Firmware Configurations of Target Machines in a Software Provisioning Environment”, U.S. Appl. No. 12/393,319, filed Feb. 26, 2009.
DeHaan et al., “Methods and Systems for Replicating Provisioning Servers in a Software Provisioning Environment”, U.S. Appl. No. 12/392,508, filed Feb. 25, 2009.
DeHaan, “Systems and Methods for Cloning Target Machines in a Software Provisioning Environment”, U.S. Appl. No. 12/473,014, filed May 27, 2009.
DeHaan, “Methods and Systems for Provisioning Software”, U.S. Appl. No. 11/763,315, filed Jun. 14, 2007.
DeHaan, “Methods and Systems for Provisioning Software”, U.S. Appl. No. 11/763,333, filed Jun. 14, 2007.
Maghraoui et al., “Model Driven Provisioning: Bridging the Gap Between Declarative Object Models and Procedural Provisioning Tools”, 2006.
Novak Judit, “Automatic Installation and Configuration for Large Scale Farms”, 2005.
Quintero et al., “Introduction to pSeries Provisioning”, 2004.
Related Publications (1)
Number Date Country
20100058332 A1 Mar 2010 US