WO2002039313A2 - A data model for automated server configuration - Google Patents

A data model for automated server configuration Download PDF

Info

Publication number
WO2002039313A2
WO2002039313A2 PCT/US2001/042869 US0142869W WO0239313A2 WO 2002039313 A2 WO2002039313 A2 WO 2002039313A2 US 0142869 W US0142869 W US 0142869W WO 0239313 A2 WO0239313 A2 WO 0239313A2
Authority
WO
WIPO (PCT)
Prior art keywords
entities
many
relationship
data model
relate
Prior art date
Application number
PCT/US2001/042869
Other languages
French (fr)
Other versions
WO2002039313A9 (en
WO2002039313A3 (en
Inventor
Glenn Ferguson
Raymond E. Suorsa
Christopher Dorsey
Original Assignee
Loudcloud, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Loudcloud, Inc. filed Critical Loudcloud, Inc.
Priority to AU2002214683A priority Critical patent/AU2002214683A1/en
Publication of WO2002039313A2 publication Critical patent/WO2002039313A2/en
Publication of WO2002039313A9 publication Critical patent/WO2002039313A9/en
Publication of WO2002039313A3 publication Critical patent/WO2002039313A3/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02Standardisation; Integration
    • H04L41/024Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/10Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/101Access control lists [ACL]

Definitions

  • the present invention is directed to the provisioning, or configuration, of servers and other devices that provide support for sites that are hosted on the Internet, intranets, and other communication networks. More particularly, the present invention is directed to a data model which can be implemented using a database and which serves as a repository for information pertinent to the provisioning or configuration, of devices on a communications network.
  • a data model which can be implemented using a database and which serves as a repository for information pertinent to the provisioning or configuration, of devices on a communications network.
  • each website requires an infrastructure that stores the information provided by that site, responds to user requests for the information, and conducts other types of transactions appropriate to the site.
  • a significant component of this infrastructure is a web server, which receives requests for information, retrieves it from the appropriate sources, and provides it to the requestor.
  • Websites which provide more complex services, such as online ordering, may also include application servers to support these additional functions.
  • the infrastructure to support a website may be as simple as a single server, or even a portion of a server.
  • a large, popular website that consists of several thousand pages of information and that is accessed quite frequently may require numerous web servers to provide the necessary support.
  • websites for commercial entities, via which transactional operations are conducted may employ multiple application servers to support transactions with a large number of customers at one time.
  • the present invention is particularly directed to a data model which supports a website by facilitating provisioning of the servers, allowing appropriate software necessary for the site to be identified, located, and transferred to a server, and generally defining all aspects of the network.
  • provisioning initially occurs when the website is first launched. Thereafter, there may be a need for further provisioning, particularly in the case of a successful website, when additional servers must be added to support increased traffic, which requires accurate modeling of all aspects of the network.
  • provisioning of the servers may be required as part of a disaster recovery operation, for example a sudden interruption in power, an attack by a hacker, or corruption of stored software and/or data.
  • the provisioning of a server or other device that supports the operation of a website involves several discrete steps. First, the appropriate operating system software must be loaded onto the device, followed by networking software that enables the device to communicate over a network. Thereafter, software applications that are required to support the particular site are loaded, such as database software for retrieving web pages, credit card processing software, order processing software, etc. Finally, the content associated with the individual pages of the website must be loaded. The order in which these various components are loaded onto the server can be quite critical, to ensure compatibility of the various programs with one another. In the past, the provisioning of web servers was often carried out manually.
  • each item of software was individually loaded onto the server by a person having responsibility for that task.
  • One problem with such an approach is the fact that it consumes a significant amount of time. For a relatively large site that is supported by multiple servers, the provisioning could take several hours or days to be completed, thereby delaying the time before the site can be launched and/or upwardly scaled to accommodate increasing traffic.
  • Another, and perhaps more significant, limitation associated with the manual provisioning of devices is the lack of repeatability in the software configurations. More particularly, whenever manual operations are involved in the installation of software, there is always the possibility of human error, such as the failure to install one of the required components, or the loading of the various items of software in the wrong order.
  • the foregoing objectives are achieved by way of a data model to support the automated provisioning of servers and other devices that support various types of services, such as hosting of an Internet or intranet website.
  • This data model provides relationships between various software, configuration, monitoring, hardware, network, domain name server (DNS), and queues entities.
  • DNS domain name server
  • the present invention facilitates allowing access to and configuration of each aspect of a database which implements the model and thus, to each aspect of the network.
  • This allows for automated provisioning by devices located remotely on the network with which the data model of the present invention is associated.
  • the central database which implements the data model of the present invention contains all information that is relevant to the provisioning of devices contained on the network.
  • This information includes information regarding the hardware devices used on the network, the software components that make up the various software roles installed on a device, logical network information such as IP addresses, configuration information of the various software, hardware, and network components, domain name information, and the like. Additionally, information regarding monitoring status of the network, and devices contained thereon is provided for. Additionally, an interface for various network agents associated with each host on the network for reporting configuration regarding devices connected to the network, reporting version information, upgrading software contained thereon, and so forth, is provided for.
  • the data model allows for modeling of all information relating to a computer network to be conveniently stored in a database in a manner which minimizes the effort associated with the addition of new devices to the network and maximizes software code reuse.
  • This is accomplished by designing a model wherein each of the model's entities interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the network (or portion thereof) that the model is intended to capture.
  • these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new software, new hardware devices, new monitoring techniques and equipment, new configurations, etc., without requiring the rewriting of software code which relies upon the model and the database implementation thereof.
  • the schema described herein facilitate the reuse of existing software code to interact with the database model regarding newly added software, hardware, configurations, etc. by virtue of this design aspect of the model.
  • Figure 1 is block diagram of one embodiment of the hardware configuration for website hosting.
  • Figure 2 is a block diagram of services associated with a network, in connection with one embodiment of the present invention.
  • Figure 3 is a block diagram of a website maintenance system, associated with one embodiment of the present invention.
  • Figure 4 is a block diagram of roles used in connection with one embodiment of the present invention.
  • Figure 5 is a role-centric entity relationship diagram, used in connection with one embodiment of the present invention.
  • Figure 6 is a service-centric entity relationship diagram, used in connection with one embodiment of the present invention.
  • Figure 7 is a block diagram illustrating the relationship between various elements of one embodiment of the present invention.
  • Figure 8 is a block diagram illustrating the relationship between various elements of one embodiment of the present invention.
  • Figure 9 is a block diagram illustrating the relationship between units, bundles, and roles, in accordance with one embodiment of the present invention.
  • Figure 10 is an entity relationship diagram illustrating the relationship between units, roles, and packages, in accordance with one embodiment of the present invention.
  • Figure 11 is an entity relationship diagram illustrating the relationship between various aspects of the data model, in accordance with one embodiment of the present invention.
  • Figure 12 is an entity relationship diagram illustrating the relationship between various entities relating to software within the data model of one embodiment of the present invention.
  • Figure 13 is an entity relationship diagram illustrating the relationship between various entities relating to configuration within the data model of one embodiment of the present invention.
  • Figure 14 is an entity relationship diagram illustrating the relationship between various entities relating to monitoring within the data model of one embodiment of the present invention.
  • Figure 15 is an entity relationship diagram illustrating the relationship between various entities relating to hardware within the data model of one embodiment of the present invention.
  • Figure 16 is an entity relationship diagram illustrating the relationship between various entities relating to DNS capabilities within the data model of one embodiment of the present invention.
  • Figure 17 is an entity relationship diagram illustrating the relationship between various entities relating to network within the data model of one embodiment of the present invention.
  • Figure 18 is an entity relationship diagram illustrating the relationship between various entities relating to queues within the data model of one embodiment of the present invention.
  • the data model of the present invention will be described within the context of a database which implements the model, which database is used in a computer network for the automated provisioning, and remote configuration and maintenance, of multiple computer devices connected to the network. It will be appreciated, however, that the implementation of the invention that is described hereinafter is merely exemplary, and that the invention can find practical application in any environment where it is desirable to model a database associated with a server on a computer network of any kind.
  • Figure 1 illustrates, in block diagram form, the hardware configuration of one embodiment of the present invention.
  • a typical, three-tier web hosting system 100 which may be implemented using the data model of the present invention, is illustrated.
  • databases 102A, 102B are accessible to the web servers 104A, 104B, and the application servers 106A, 106B of the three- tier web hosting system 100 illustrated in Figure 1.
  • redundancy is used, whereby a duplicate web server 104B, application server 106B, and database 102B are each used as backups for the primary web server 104A, application server 106A, and database 102A, respectively.
  • Each of the web servers receives and handles requests received by way of a network. Requests received by way of such a network may require functionality from various applications. When this is the case, the web server 104A, 104B forwards the requests to the application server 106A, 106B, which may then process the application, and also has access to the database 102A, 102B.
  • the application server 106A, 106B may, therefore, require information regarding software, configuration, monitoring, hardware, the network, DNS, or queues, which may be contained within the database 102A, 102B. This information is modeled by one embodiment of the present invention to allow for rapid and convenient access by the application server 106A, 106B to this information contained within the database 102 A, 102B.
  • Network requests are received by the web server 104A, 104B by way of a firewall 108, and are distributed by the load balancer 110.
  • the firewall 108 provides security from any malicious network forces outside the local access of the three-tier web hosting system, 100. Any remote host, or agent, which is outside the locality of the three-tier web hosting system 100 may be required to authenticate itself to the firewall 108 in order to access, maintain, monitor, or reconfigure the web server 104A, 104B, the application server 106A, 106B, or the database 102A, 102B.
  • the load balancer 110 distributes the network transactions received by way of the firewall 108.
  • FIG. 1 is a block diagram illustrating the relationship of various services provided by a web hosting system in which the present invention can be implemented.
  • the relationship model 200 illustrated in Figure 2 comprises a variety of functional components, which relate to a web server 202, and an application server 204 connected to a network, such as the Internet 205.
  • Functions relating to the web server 202 and the application server 204 include a software maintenance component 206, and a monitoring component 208.
  • the web server 202 and application server 204 may access information, and functionality, possessed by the software maintenance component 206 and the monitoring component 208.
  • the software maintenance component 206 and monitoring component 208 may provide the web server 202 and application server 204 with information, and may access information contained on the servers 202, 204.
  • the web server 202 which is in communication with the application server 204, may request functionality to be performed by various applications. This functionality may be subdivided into two categories: website content and personalized information.
  • Website content is represented by the content feed component 210
  • personalized information is represented by the personalization component 212, which are both in communication with the application server.
  • Both the content feed component 210 and the personalization component 212 may be monitored by the monitoring component 208, and may receive software maintenance support from the software maintenance component 206.
  • the manner in which the monitoring component 208, the software maintenance component 206, the network 205, the hardware devices 202, 204, and the configuration components 210, 212 are related is defined by the data model of the present invention.
  • the web server 202 may comprise a layer 7 proxy server.
  • the monitoring component 208 monitors the status of the hardware components, such as the web server 202 and application server 204, and monitors the content feed 210 and the personalization component 212.
  • the web server 202 or application server 204 may request the software maintenance component 206 to provide maintenance, which may be in the form of software updates, to any of the hardware components 202, 204, the content feed component 210, or the personalization component 212.
  • the content feed component 210 may communicate any information which is fed into the system 200, while the personalization component 212 provides data and information that is specific to a particular site hosted by a web server, or layer 7 proxy server 202.
  • FIG. 3 One example of information that is fed into the system 200 by way of the content feed component 210 is streaming data from an external source, such as stock market ticker data.
  • a system 300 is illustrated, which is suitable for automated provisioning, remote access and maintenance of network devices.
  • Another system in which models according to the present invention can be implemented is described in U.S. Patent Application Serial No. 09/699,329, entitled “AUTOMATED PROVISIONING FRAMEWORK FOR INTERNET SITE SERVERS" to Raymond Suorsa et al. filed on an even date herewith, the disclosure of which is incorporated here by reference.
  • a database 302 can be used to implement the data model according to exemplary embodiments of the present invention. This database 302 may reside on any large scale storage device.
  • suitable storage devices upon which the database associated with the data model of the present invention may be stored include redundant array of independent disks (RAID) systems, such as those provided by EMC Corporation of Hopkinton, MA, or other similar devices.
  • This database 302 may be accessed by the various agents 304A, 304B, 304C, whose level of access may be determined by a hierarchy of trust component 306.
  • a user interface 308 may be provided for the convenience of a user in accessing information contained within the database 302, or software contained within the software file system 310. The determination of the level of access granted by the user interface 308 is made by the hierarchy of trust component 306. Access determination information is stored by the access determination component 312, which is accessible by way of database 302.
  • FIG. 4 a block diagram of a customer role package 400 is illustrated. Such customer role packages are used to provide repeatability, and eliminate the need for manual configuration by designating software components to be installed on a particular device connected to a network. Roles as illustrated in Figure 4 define the functionality of device, and may be considered to define the role, or part, the device is to play within the network.
  • LDAP lightweight directory access protocol
  • the software components to be installed are divided into three types of software roles that are related to the frequency with which they are likely to change or be upgraded. These roles include an application role 402, a customer code role 404, and an operating system (OS) role 406.
  • the OS role 406 contains the software that has the lowest probability of being changed during the life cycle of the particular device on which it is installed. This role consists of the OS of the device, plus other general software, such as the intelligent agents 304A, 304B, 304C, illustrated in Figure 3.
  • the customer code role 404 contains content specific to, and provided by, a customer, and therefore contains software that can change on a regular basis for a website or other network site.
  • Examples of software contained within the customer code role 404 might include hypertext markup language (HTML) pages, Java server pages (JSP), active server pages (ASP), image files, and other content that is regularly updated by a website host.
  • the application role 402 consists of software components that change relatively infrequently when compared to software of the customer code role 404, but perhaps more often than software contained within the OS role 406.
  • the hierarchical structure of such a customer role package 400 is described hereinafter in connection with Figure 9.
  • FIG. 5 An entity relationship diagram of a role-centric network model 500 is illustrated in Figure 5.
  • the role-centric model 500 is used for relating devices 502 connected to a network to software roles 504. This is accomplished by way of a role instance 506, which is used as a place holder for devices until a device 502 is present, and connected to the network by way of which the role 504 may communicate the software contained therein to the devices 502.
  • This role-centric model 500 allowed for a role instance 506 that reserved IP addresses, or other network addresses, and allowed for general network configuration without the devices being attached to the network.
  • the IP addresses used by the various devices connected to the network may be maintained, and need not be reassigned each time a device is reconnected to the network at a different location.
  • Entity relationship diagrams such as the entity relationship diagram of the role-centric model 500, show the relationship between various entities, which are represented by rectangular blocks and labeled to indicate their significance connected by way of connection lines.
  • Each connection line has a single connection on one end and multiple connections on the opposite end, indicating a one-to-many relationship. This means that a single entity is related to multiple entities on the end of the connection line having multiple connections.
  • the devices entity 502 relates to the role instance entity 506 in a one-to-many fashion, meaning that each device entity 502 is directly related to many role instance entities 506.
  • the role entity 504 is related to the role instance entity 506 in a one-to-many relationship.
  • each role entity 504 is related to multiple role instances 506.
  • Figure 6 illustrates an improved approach to the traditional role-centric network model approach illustrated in Figure 5.
  • a service-centric network model 600 that allows one to monitor service information related to devices 602 associated with a computer network is shown. This type of model is accomplished, as illustrated in the entity relationship diagram of Figure 6, by relating devices entities 602 to service instance entities 604 in a one-to-many relationship. The service instance entities 604 are then related to services 606 in a many-to-one relationship. The services entity 606 is related to the roles entity 608 in a one-to-many relationship. The service instance entities 604 act as a relationship table between the devices 602 and the services 606.
  • the advantages of the service-centric model 600 which is employed by one embodiment of the present invention include all of the advantages of the role-centric model 500, illustrated in Figure 5, as the network may be configured using place holders instead of devices connected to the network.
  • the service-centric model has the additional advantage of relating the roles to services, which are an important quantity for customers to monitor and configure.
  • An embodiment of the present invention utilizes a service-centric model, such as the one illustrated in Figure 6.
  • the block diagram in Figure 7 illustrates a service-centric concept, relating services 702 to various other quantities associated with the network that in accordance with an embodiment of the present invention.
  • the services 702 are centrally related to each of: the devices 704, the configuration component 706 of the network, the monitoring 708 of the network, hardware, and software, and the software 710, such as the OS software, packages, and roles hereinbefore described.
  • the monitoring component 708 may monitor the software component, ensuring that each of the software roles is properly maintained, and up to date.
  • Figure 8 illustrates a similar configuration, wherein services are centrally related to a configuration component 706, a monitoring component 708, and software 710.
  • the service-centric relationship illustrated in Figure 8 differs from the one illustrated in Figure 7 in that the services 702 are not related directly to devices. Rather, the services 702 are related directly to a service instance 802, which allows for the configuration of an IP address by a configuration device. This service instance 802 is related to devices 804 upon which an IP is configured.
  • Role 902 of Figure 9 comprises a combination of software bundles and units.
  • the software units 904, 906, 908 each comprise multiple software installation packages.
  • One example of such software installation packages that may be contained within units 904, 906, 908 includes software bundles for the Linux OS, such as Redhat package manager (RPM) files. Such packages would be saved in a file having a name using the extension RPM, such as file x.rpm.
  • RPM Redhat package manager
  • a bundle 912 may be made up of a combination of units, such as unit 908, and other bundles, such as bundle 910. These bundles are then combined into a role, such as role 902.
  • This role 902 is stored as a list of packages, such as RPMs, to be installed on a device, and the order in which those packages are to be installed. These roles may, therefore, be used to rebuild a machine automatically, should a critical failure occur.
  • the role 902 illustrated in Figure 9 may comprise a customer role package, such as the package 400 illustrated in Figure 4, which contains three roles: the application role 402, the customer code role 404, and the OS role 406.
  • Figure 10 illustrates the same relationships shown in Figure 9 in the form of an entity relationship diagram.
  • roles entities 1002 are related to units entities 1004 and packages entities 1006. These three groups of entities are related by way of two relationship tables 1008, 1010.
  • the roles entities 1002 represent a role, such as role 902 of Figure 9, or a group of roles.
  • These roles entities 1002 are made up of multiple units entities 1004, which represent units, such as units 904, 906, 908 of Figure 9. This is illustrated by the one-to-many relationship between the units entities 1004 and the relationship table 1008, which is related in a one-to-many relationship with the relationship table 1010.
  • This relationship table 1010 is related to the roles entities 1002 in a many-to-one relationship.
  • the roles represented by the roles entities 1002 may be made up of multiple units, which are represented by the units entities 1004.
  • the units represented by the units entities 1004 may be made up of multiple packages, such as the RPMs discussed above.
  • These packages are represented by the packages entities 1006, which are related in a one-to-many relationship with the relationship table 1008 which is in turn related to the units entities 1004 in a many-to-one relationship.
  • the packages 1006 are illustrated as having a one-to-many relationship with other packages, which indicates that any single package may contain multiple packages.
  • the relationship diagram illustrated in Figure 10 is a particularly useful way to illustrate the relationship between the various components of a data model. As can be seen, much information can be gleaned from the entity relationship diagram of Figure 10, and less space is required to express the same idea illustrated in Figure 9.
  • the entity relationship diagram also allows for convenient access to each aspect of the database being modeled for quick, accurate, and repeatable configuration of that database.
  • An entity relationship diagram of the data model according to one embodiment of the present invention is illustrated in Figure 11.
  • the data model 1100 is represented as having multiple entities related to one another.
  • Each of these entities illustrated in Figure 11 represents a group of entities and therefore Figure 11 represents the data model on a macro level only.
  • Each of the entities represented in the data model 1100 of Figure 11 is broken into its components, and illustrated in more detail in subsequent figures, which are denoted in Figure 11.
  • the data model 1100 in Figure 11 relates the following entities: software 1102, configuration 1104, monitoring 1106, hardware 1108, DNS 1110, network 1112, and queues 1114.
  • the software entities 1102 represent various software packages to be installed in devices, applications, and operating system software of the various network devices.
  • the software entities 1102 are directly related to the configuration entities 1104, the hardware entities 1108, and the network entities 1112.
  • the software entities 1102 have an optional many- to-one relationship with the hardware entities 1108, and shares a combination of many-to-one and one-to-many relationships with both the configuration entities 1104 and the network entities 1112.
  • the configuration entities 1104 are related to the software entities 1102 with a many-to-one and one-to-many relationship, and similarly share a many-to-one and one-to-many relationships with the hardware entities 1108. Additionally, the configuration entities are related to the monitoring entities 1106 in a one-to-many relationship. The configuration entities 1104 relate to both the DNS entities 1110 and the network entities 1112 in a many-to-one relationship. The relationship with the DNS entities 1110 is optional, as indicated by the broken line connecting the configuration entities 1104 and the DNS entities 1110. These configuration entities 1104 represent the configuration of various network addresses, software packages, and device addresses.
  • the monitoring entities 1106 are related to the configuration entities 1104 as described above, and to the hardware entities 1108 in many-to-one relationships.
  • the monitoring entities 1106 monitor the status and condition of entities within the configuration entities group 1104 and the hardware entities group 1108.
  • the hardware entities 1108 represent multiple hardware devices in communication with a network. These entities are related to the software entities 1102 in an optional one-to-many relationship, and as described above to the monitoring entities 1106 in a one-to-many relationship. Additionally, as described above, the hardware entities 1108 are related in both a many-to-one and one-to- many relationship with the configuration entities 1104.
  • the DNS entities 1110 represent all DNS transfers, queries, entries, configurations, and posts. They are optionally related to the configuration entities 1104 in a one-to-many relationship, and to the network entities 1112 in an optional many-to-one relationship.
  • the network entities 1112 are related to the software entities 1102 in a combination of many-to-one and one-to-many relationships, and to the configuration entities 1104 in a one-to-many relationship. Additionally, the network entities 1112 are optionally related to the DNS entities 1110 in a one-to- many relationship.
  • a group of entities called the queues entities 1114 are also illustrated in the database model 1100 of Figure 11. However, the queues entities are not illustrated as having a direct relationship with any of the other entities of this model 1100.
  • a relationship between the queues entities 1114 and the other entities within the data model 1100 is created by either business logic contained outside of the data model, or by intelligent agents, such as the agents 304A, 304B, 304C illustrated in Figure 3. This type of relationship will be described hereinafter with greater detail.
  • Figures 12-18 illustrate in greater detail the entities of the data model 1100 illustrated in Figure 11.
  • entity relationship diagrams In this type of diagram, the one-to-many or many-to-one relationships between the entities will be illustrated in the same manner as in Figure 11. Optional relationships will be illustrated by way of broken lines. Connections to entities within other groups of entities (i.e. written other entities of the data model 1100 in Figure 11), will be indicated by lines at the edge of the page with a designation indicating the figure upon which those relationships are continued.
  • Each of the entities contained within Figures 12-18 have a set of variables associated with them, specific values of which characterize instances of each of the entities and their functionalities. These variables will be described hereinafter in tables. In these tables identifying variables associated with each entity, a variable name, variable definition, variable type, and an indication regarding whether the variable is required by the entity or optional to the entity will be given. Those skilled in the art will appreciate that the reference herein to "required” or “option” with respect to the individual variables in each table is purely exemplary and that, in other exemplary embodiments which are not explicitly described herein, the status of these variables as “required” or “optional” may change.
  • an indication of the primary key of each entity of each variable set will be given by an asterisk immediately following the variable name. In some cases, multiple primary keys will be indicated.
  • the primary key of a particular entity must be contained within each of the entities to which that entity relates and is the main variable associated with the entity.
  • the primary key of an entity acts as a type of pointer, referring to the first entity.
  • FIG 12 a detailed entity relationship diagram of the software entities 1102 is illustrated.
  • Each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture.
  • these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g. , new software packages, without requiring the rewriting of software code which relies upon the model and the database implementation thereof.
  • the units entities 1202 represent the software units described in connection with Figure 10.
  • the variable set associated with the units entities 1202 is set forth below in Table 1.
  • the units entities 1202 relate to unit monitor types entities 1204, unit contents entities 406, application role units 1208, unit packages entities 1212, account role units entities 1214, device pool role units entities 1216 and one-to- many relationships.
  • the one-to-many relationship between the units entities 1202 and the unit conflicts entities 1206 includes dual one-to-many relationships.
  • the units entities 1202 may be related by the many-to-one relationship 1238 illustrated in Figure 12 with entities within the network entities 1112 which is illustrated in detail in Figure 17. Specifically, the units entities 1202 is related by this many-to-one relationship with the accounts entities 1702 of Figure 17. An optional many-to-one relationship may exist between units entities 1202 and the platforms entities 1210.
  • the unit monitor types entities 1204 indicate the type of monitoring associated with the units related to the unit entities 1202.
  • the variable set associated with the unit monitor types entities 1204 is set forth below in Table 2.
  • VARIABLE SET OF MONITOR TYPES ENTITIES 1204 As mentioned above, the unit monitor types entities 1204 relates to the units entities 1202 in a many-to-one relationship.
  • the unit conflicts entities 1206 are used to identify any potential conflicts between units related to the units entities 1202.
  • the variable set associated with the unit conflicts entities 1206 is set forth below in Table 3.
  • the unit conflicts entities 1206 relate to the units entities 1202 in dual many-to-one relationships.
  • Application Role Units Entities 1208 relate application roles entities 1236 with units entities 1202, much in the same manner that roles are related to units in the relationships described in connection with Figure 10.
  • the variable set associated with the application role units entities 1208 is set forth below in Table 4.
  • the application role units entities 1208 relate to the units entities 1202 in a many-to-one relationship, as discussed above. Additionally, the application role units entities 1208 relate to the application roles entities 1236 in a many -to-one relationship.
  • Platforms entities 1210 indicate the platforms of the various computer devices connected to the network, upon which the units, packages, and roles run.
  • the variable set associated with the platforms entities 1210 is set forth below in Table 5.
  • the platforms entities 1210 may have multiple optional one-to-many relationships with other entities illustrated in Figure 12. These entities with which the platforms entities 1210 may be related in an optional one-to-many relationship include the units entities 1202, as previously discussed, the account roles entities 1224, and the application roles entities 1236. Additionally, the platforms entities 1210 relates in a many-to-one fashion with the device pool roles entities 1218 and the packages entities 1220.
  • the unit packages entities 1212 serve to relate the units represented by the units entities 1202 with the packages represented by the packages entities 1220, in much the same manner as described in connection with Figure 10.
  • the variable set associated with the unit packages entities 1212 is set forth below in Table 6.
  • the unit package entities 1212 have many-to-one relationships with the units entities 1202, as previously discussed, and the packages entities 1220.
  • Account role units entities 1214 are used in relating the units represented by the units entities 1202 with the account roles of the account roles entities 1224 in a similar manner as described in Figure 10 using relational tables.
  • the variable set associated with the account role units entities 1214 is set forth below in Table 7.
  • the account role units entities 1214 have many -to-one relationships with the unit entities 1202, as previously indicated, and the account roles entities 1224.
  • the device pool role units entities 1216 serve to relate devices contained in device pools, which are associated with the device pool roles entities 1218, with the various software units associated with the units entities 1202 that are necessary to properly configure the devices.
  • the variable set associated with the device pool role units entities 1216 is set forth below in Table 8.
  • the device pool role units 1216 have many-to-one relationships with the units entities 1202, as previously indicated, and the device pool roles entities 1218.
  • Device pool poles entities 1218 relate the device pool packages, the device roles, and the platforms of the various devices with the device pool role units associated with the device pool role units entities 1216.
  • the variable set associated with the device pool roles entities 1218 is set forth below in Table 9. These variables relate to the device pool role, or the software associated with a particular device pool. Thus, the variable STATUS, indicated below in Table 9, may indicate the status of a device role.
  • the device pool roles entities 1218 are related to the device pool role units entities 1216 in a one-to-many relationship as previously discussed. Also, the device pool roles entities 1218 are related to the platforms entities 1210 in a many- to-one relationship, as previously discussed. In addition to these relationships, the device pool roles entities 1218 are related to the device roles entities 1226, and the device pool packages entities 1234 in one-to-many relationships.
  • the packages entities 1220 represent the various software packages, such as those described in connection with Figure 10.
  • the variable set associated with the packages entities 1220 is set forth below in Table 10.
  • the packages entities 1220 are related to the platforms entities 1210 in a many -to-one relationship, and the unit packages entities 1212 in a one-to-many relationship, as discussed above. Additionally, the packages entities 1220 is related to the account packages of entities 1222, the included packages entities 1230, the application packages entities 1232, and the device pool packages 1234 in one-to-many relationships. The relationship between the packages entities 1220 and the included packages entities 1230 is a dual one-to-many relationship. Also, the packages entities 1220 are related by way of the many-to-one relationship 1240 to an entity within the network entities 1112 shown in Figure 17. Specifically, the packages entities 1220 relates to the accounts entities 1702 of Figure 17 by way of a many-to-one relationship 1214.
  • the account packages entities 1222 serves to relate the packages entities 1220 with the account roles entities 1224, in a manner similar to the manner in which packages are related to roles in Figure 10.
  • the variable set associated with the account packages entities 1222 is set forth below in Table 11.
  • the account packages entities 1222 relate to the packages entities 1220 as previously described, and the account roles entities 1224 in many -to-one relationships.
  • the account roles entities 1224 represent the various software roles associated with particular customer accounts.
  • the variable set associated with the account roles entities 1224 is set forth below in Table 12. These variables relate to the account roles, or software packages for each account.
  • the STATUS variable may indicate the status of an account role as active, inactive, deprecated, experimental, and so forth.
  • the account roles entities 1224 relates in one-to- many relationships with the account role units entities 1214 and the account packages entities 1222. Also, as previously described, the account roles entities 1224 may optionally relate to the platforms entities 1210 in a many -to-one relationship. The account roles entities 1224 may also optionally relate to the device roles entities 1226 in a one-to-many relationship. The account roles entities 1224 may also relate, by way of a many-to-one relationship 1242, to an entity within the network entities 1112 illustrated in Figure 17. Specifically, the account roles entities 1224 relates to the account entities 1702 illustrated in Figure 17 by way of a many-to-one relationship 1242.
  • the device roles entities 1226 represent the various software roles associated with each device connected to the network.
  • the variable set associated with the device roles entities 1226 is set forth below in Table 13.
  • the device roles entities 1226 relate to the device pool roles entities 1218, and optionally to the account roles entities 1224 in many- to-one relationships.
  • the device roles entities also has optional many-to-one relationships with the application roles entities 1236, the customer tiers entities 1708 of Figure 17 by way of relationship 1246, and the devices entities 1512 of Figure 15 by way of relationship 1248.
  • the device roles entities 1226 also relates in dual one-to-many and a single many -to-one relationship with elements of the configuration entities 1104 illustrated in Figure 13.
  • the device roles entities 1226 relate to the device role configuration entities 1320 of Figure 13 and the device role IP host entities 1308 of Figure 13 in one-to-many relationships 1256, 1260, respectively.
  • the device roles entities 1226 also relates to the status entities 1322 of Figure 13 by a many -to-one relationship 1258.
  • the dependent roles entities 1228 relate to the application roles represented by the application roles entities 1236.
  • the dependent roles entities 1228 serve to identify various application roles that are dependent upon other roles, and to describe this dependency.
  • the variable set associated with the dependent roles entities 1228 is set forth below in Table 14.
  • the dependent roles entities relate in dual many-to-one relationships with the application roles entities 1236.
  • the included packages entities 1230 is related to the packages entities 1220 and identifies packages that are included within a particular installation package, and the order in which it is to be installed.
  • the variable set associated with the included packages entities 1230 is set forth below in Table 15.
  • the application packages entities 1232 relates the packages represented by the packages entities 1220 and the application roles represented by the application roles entities 1236.
  • the relationship of the roles in packages is similar to the manner in which the roles in packages are related in Figure 10.
  • the variable set associated with the application packages entities 1232 is set forth below in Table 16.
  • the application packages entities 1232 relate to the packages entities 1220 as previously described, and the application roles entities 1236 in many-to-one relationships.
  • the device pool packages entities 1234 serve to relate the device pool roles represented by the device pool roles entities 1218 with the packages represented by the packages entities 1220. This occurs in a similar manner as described in connection with Figure 10.
  • the variable set associated with the device pool packages entities 1234 is set forth below in Table 17.
  • the device pool packages entities 1234 relate to the packages entities 1220 on the device pool roles entities 1218 in many-to-one relationships, as described above.
  • the application roles entities 1236 represent the various application software roles.
  • the variable set associated with the application roles entities 1236 is set forth below in Table 18. These variables relate to the application role.
  • the STATUS variable may give an indicator that an application role is active, inactive, experimental, deprecated, supported, unsupported, and so forth.
  • the application roles entities 1236 relates in a one- to-many relationship with the application role units entities 1208, the application packages entities 1232, and optionally the device roles entities 1226. Additionally, the application roles entities 1236, as indicated above, relates to the dependent roles entities 1228 in dual one-to-many relationships. The application roles entities 1236 also optionally relates in a many-to-one relationship with the platforms entities 1210. In addition to these relationships previously described, the application roles entities 1236 relates in a one-to-many relationship 1244 with the data center tiers 1724 of Figure 7. The application roles entities 1236 also relates in a one-to-many relationship 1254 with the role configurations entities 1316 of Figure 13. The application roles entities 1236 also relates to the status entities 1322 of Figure 13, and optionally to the services entities 1314 of Figure 13 by way of many -to-one relationships 1252, 1250, respectively.
  • the relationships 1238, 1240, 1242, 1244, 1246 relate to various entities within the network entities 1112, which is illustrated in Figure 17. These relationships have been labeled in Figure 17 to indicate the direct relationship between entities of the software entities 1102 in Figure 12 and the network entities 1112 in Figure 17. Additionally, an optional relationship 1248 with the hardware entities 1108, which is illustrated in Figure 15, is also indicated. Further, the relationships 1250, 1252, 1254, 1256, 1258 relate to entities within the configuration entities 1104, which is illustrated in Figure 13.
  • CONFIGURATION 1104 The entities of the configuration entities 1104 are illustrated in Figure 13.
  • configuration entities 1104 represent various configuration information relating to software, hardware, the network, and the like. Those entities which are not illustrated as having a direct relationship with any of the other entities are used by business logic, or intelligent agents, for various purposes. Like the software entities from Figure 12, each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new configurations, without requiring the rewriting of software code which uses the model and the database implementation thereof.
  • the manufacturing model entities 1302 is used to identify a manufacturing model identification number, manufacturing name, model name, and manufacturing model description. For example, if a Sun Spore 5 server is used by the present invention, the manufacturer name would be Sun, and the model name would be Spore 5. The description could be any indication that it is a server.
  • the variable set associated with the manufacturing model entities 1302 is set forth below in Table 19.
  • the manufacturing model entities 1302 does not directly relate to any of the other entities illustrated in Figure 13. This group of entities 1302 is used by business logic associated with the present invention to determine manufacturer name, model name, and manufacturer description for each of the devices used on the network associated with the present invention.
  • the component objects entities 1304 provide an indication of what table a particular value is stored in. For example, a location of the table in which values relating to the specific hardware or software object may be obtained by way of the component object entities 1304.
  • the variable set associated with the component objects entities 1304 is set forth below in Table 20.
  • the component objects entities 1304 does not directly relate to any of the entities illustrated in Figure 13. This group of entities 1304 is used by business logic associated with the present invention to determine which tables should be used to look up values relating to specific objects on the network associated with the present invention.
  • the objects whose values may be found by way of the component objects entities 1304 may be hardware objects or software objects.
  • the conduits entities 1306 relate to the devices of the network associated with the present invention. These conduits entities 1306 relate to conduits by which information may be passed through a firewall. In essence, the conduits through a firewall constitute holes through a firewall by which devices may communicate from outside of the firewall to devices contained within the firewall. Thus, the conduits entities 1306 define the source and destination addresses that involved in communications across the firewall. The present invention also maintains a history, which records all of the traffic across the firewall.
  • the variable set associated with the conduits entities 1306 is set forth below in Table 21.
  • the conduits entities 1306 relate to the devices entities 1512 of Figure 15 in a many-to-one relationship 1332.
  • the device role IP host entities 1308 act a place holder for the various devices of the network, and allow IP addresses to be assigned without having a specific device connected to the network.
  • the IP addresses of the devices used on the network associated with the present invention may be of a physical type or a logical type. This means that the IP address may physically relate to the specific device connected to the network, or may be a logical IP address, which does not correspond to the actual physical IP address, but relates the same device.
  • the variable set associated with the device role IP host entities 1308 is set forth below in Table 22.
  • the device role IP host entities 1308 relates to the interface IP type entities 1310 in a many -to-one relationship. Also, as previously discussed, the device role IP host entities 1308 relates to the device roles entities 1226 of Figure 12 in a many-to-one relationship 1260. The device role IP host also relates in a many-to- one relationship 1340 to the IP addresses entities 1730 of Figure 17. The device role IP host entities 1308 may optionally relate to the DNS hosts entities 1604 of Figure 16 in a many-to-one relationship 1336.
  • the interface IP type entities 1310 indicate the type of interface associated with each IP address.
  • the variable set associated with the interface IP type entities 1310 is set forth below in Table 23.
  • the interface IP type entities 1310 is related to the device role IP host entities 1308 in a one-to-many relationship.
  • the virtual IPs entities 1312 relate to virtual IP addresses, which allow for virtual IP addressing, and allow for multiple machines to have the same IP address, or group of addresses mapped to them by way of a load balancer.
  • a variable called STICKY may be set to require that each time a specific device accesses an IP address it is mapped to the same server by the load balancer. This "sticky" routing allows cookies to be used that were placed on the device by that server.
  • the variable set associated with the virtual IPs entities 1312 is set forth below in Table 24.
  • the virtual IPs entities 1312 relates to the VIP groups entities 1424 of Figure 14 in a one-to-many relationship 1328, the devices entities 1512 of Figure 15 in a many-to-one relationship 1330, and to the IP addresses entities 1730 of Figure 17 in a many-to-one relationship 1338.
  • the services entities 1314 relate application roles to services for the convenience of users and network customers. This allows a customer to view and configure application roles in terms of services offered, which is a useful quality to customers.
  • the variable set associated with the services entities 1314 is set forth below in Table 25.
  • the services entities 1314 may optionally relate to the application roles entities 1236 of Figure 12 in a one-to-many relationship 1250, as discussed above.
  • the role configurations entities 1316 relate to the actual configurations of software roles. These role configuration associated with the configurations entities 1316 may include such information as the types of components to be used, such as specific memory types, CPU types, video card types. Also, the quantity of components to be used may be indicated, along with the component size and type. For example, if an Intel processor is used as a CPU, the quantity may be designated as two or three, and so on depending upon the number of the processor occupied by a particular customer. The component size associated with such a CPU would-be expressed in megahertz, indicating the processing scheme. The configuration type would be expressed in a brand name, or perhaps a minimum specification requirement.
  • the variable set associated with the role configurations entities 1316 is set forth below in Table 26.
  • the role configuration entities 1316 relate to the component type entities 1324 in a many-to-one relationship, and, as previously discussed, the application roles entities 1236 of Figure 12 in a many-to-one relationship 1254.
  • the device roles history entities 1318 is a history of all roles executed by a particular device. That is, the history of all software that has ever been employed by a specific device is indicated in the device roles history entities 1318. Thus, many of the entries within the device roles history entries 1318 are similar to those of the device roles entities 1226.
  • the variable set associated with the device roles history entities 1318 is set forth below in Table 27.
  • the device roles history entities 1318 cannot relate directly to any other entities illustrated on Figure 13.
  • the information contained within these entities 1318 is used by business logic associated with the present invention.
  • the type of operation that may be performed by business logic using the device roles history entities 1318 may include, for example, a software rollback when software contained on a particular device has failed.
  • the device role configuration entities 1320 relate to the configuration of various software roles. These device role configuration entities 1320 are a way in which generic name-value pairs may be defined, which are associated with device roles of the present invention. One instance in which this might be used is if a particular device has four processors, but a particular customer is only paid to use two processors of that server, a name-value pair may be used to indicate these specific device role configurations. Thus, a generic keyname may be generated associated with the two processors that have been paid for by a customer. The values associated with the name-value pair for which the name is expressed in the device role configuration entities 1320 is expressed within the device role configuration values entities 1326. The variable set associated with the device role configuration entities 1320 is set forth below in Table 28.
  • the device role configuration entities 1320 is related to a device role configuration values entities 1326 in a one-to-many relationship, and to the device roles entities 1226 of Figure 12 in a many-to-one relationship 1256.
  • the status entities 1322 provide status reports regarding various software and hardware configurations.
  • the variable set of the status entities 1322 is set forth below in Table 29.
  • the status entities 1322 relate to the application roles entities 1236, and the device roles entities 1226, both of Figure 12, in one-to-many relationships 1252, 1258, respectively. Also, the status entities 1322 relate to the devices entities 1512 of Figure 15 in a one-to-many relationship 1324.
  • the component type entities 1324 is related to the various types of components associated with the devices of the network.
  • the variable set associated with the component type entities 1324 is set forth below in Table 30.
  • the component type entities 1324 relate to the role configurations entities 1316 in a one-to-many relationship.
  • the device role configuration values entities 1326 relate to values
  • the device role configuration values 1326 are the value portion of the main- value pair associated with the device roles, for which the names are expressed within the device role configuration entities 1320, as previously described.
  • the variable set associated with the device role 0 configuration values entities 1326 is set forth below in Table 31.
  • the device role configuration values entities 1326 relate to the device role configuration entities 1320 in a many-to-one relationship.
  • the entities of the monitoring entities 1106 are illustrated in Figure 14 and an entity relationship diagram form. These entities relate to components that maintain the network and various hardware and software components of the networks, as well as configuration information. As with the aforementioned entities, the monitoring entities are described in terms of specific interrelations and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new monitoring functions, without requiring the rewriting of software code which relies upon the model and the database implementation thereof.
  • the autonomous system map entities are used to create an autonomous system map of the entire system associated with the present invention.
  • the variable set associated with the autonomous system map entities 1402 is set forth below in Table 32.
  • the autonomous system map entities 1402 of the monitoring entities 1106 illustrated in Figure 14 are not directly related to any other entities of Figure 14. However, the information contained within the autonomous system map entities 1402 is used by business logic and intelligent agents network in ascertaining system map information regarding the network of the present invention.
  • the device request classes entities 1404 are used to relate device classes, and requests associated with those devices.
  • the device classes associated with the device request classes entities may include a particular group of devices, such as load balancers, routers, or servers.
  • the variable set associated with the device request classes entities 1404 is set forth below in Table 33.
  • the device request classes entities 1404 are related in a many-to-one relationship with the request class entities 1406.
  • the device request classes entities portion of four are related in a many-to-one relationship 1428 with the devices entities 1512 of Figure 15.
  • the request class entities 1406 may be optionally related to request class variables entities 1408.
  • the request class entities 1406 define suitable names for device classes used in connection with the present invention.
  • the variable set associated with the request class entities 1406 is set forth below in Table 34.
  • the request class entities 1406 may be optionally related to the request class variables entities 1408 in a one-to-many relationship.
  • the request class variables entities 1408 act as a relationship table between the request class entities 1406 and the SNMP variable entities 1420.
  • the request class variables entities identify all variables collected for specific request class, and identify a foreign key to the request class table which relates the request classes to SNMP variables within the SNMP variable entities 1420.
  • the variable set associated with the request class variables entities 1408 is set forth below in Table 35.
  • the request class variables entities 1408 may be optionally related in many- to-one relationships with the request class entities 1406, as discussed above, and to the SNMP variables entities 1420.
  • the manager applications entities 1410 is a list of internal applications that defines all applications allowed to communicate with devices and access these devices, such as software applications.
  • the variable set associated with the manager applications entities 1410 is set forth below in Table 36.
  • the manager applications entities 1410 are related to the monitor ACLs entities 1412 and the device application configuration entities 1414.
  • the monitor ACLs entities 1412 allows for monitoring of access control list (ACLs) associated with devices of the present invention.
  • ACLs access control list
  • the variable set associated with the monitor ACLs entities 1412 is set forth below in Table 37.
  • the monitor ACLs entities 1412 are related to the manager applications entities 1410 in a many-to-one relationship, as discussed above.
  • the monitor ACLs entities 1412 are also related to the device ACLs entities 1418 and the ACL entries entities 1422 in one-to-many relationships.
  • the device application configuration entities 1414 relate devices with manager applications, and provide a mechanism whereby the configuration of device applications may be monitored.
  • the device application configuration entities 1414 are a name-value pair for device applications configured on the network. A date or text value may be entered and associated with the devices, depending upon the specific device type.
  • the variable set associated with the device application configuration entities 1414 is shown below in Table 38.
  • the device application configuration entities is related in many-to-one relationships with the manager applications entities 1410, as previously discussed, and with the devices entities 1512 of Figure 15 by way of relationship 1430.
  • the device authorization entities 1416 are used for authorizing use of devices by way of user names, passwords, and the like.
  • the device authorization entities 1416 describe specific device authorizations required by the simple network management protocol (SNMP), used in connection with one embodiment of the present invention.
  • SNMP simple network management protocol
  • the device authorization entities 1416 allow for current and future, or next values, of user names and passwords to be read, written, and trapped (having an alert sent regarding an erroneous user name or password).
  • the variable set associated with the device authorization entities 1416 is set forth below in Table 39.
  • the device authorization entities 1416 relate to the device ACLs entities 1418 in a one-to-many relationship and to the devices entities 1512 of Figure 15 in a many-to-one relationship 1426.
  • the device ACLs entities 1418 are used to provide the device authorizations entities 1416 with the correct access control lists (ACLs).
  • the variable set associated with the device ACLs entities 1418 is set forth below in Table 40.
  • the device ACLs entities 1418 are related to the monitor ACLs entities 1412 and the device authorizations entities 1416 in many-to-one relationships, as previously discussed.
  • the SNMP variables entities 1420 provide information regarding variables associated with the simple network management protocol (SNMP) associated with the devices connected to the network of the present invention. Generally, standard SNMP variables are assigned to specific devices or objects and a unique object identification must be determined for internal purposes.
  • the variable set associated with the SNMP variables entities 1420 is set forth below in Table 41.
  • the SNMP variables entities 1420 may optionally be related to the request class variables entities 1408 in a one-to-many relationship.
  • the ACL entries entities 1422 relate to the entries on the access control lists associated with the various devices connected to the network of the present invention.
  • the variable set associated with the ACL entries entities 1422 is set forth below in Table 42.
  • ACL entries entities 1422 is related in a many-to-one relationship with the monitor ACLs entities 1412.
  • the Virtual IP (VIP) groups entities 1424 relate to devices grouped into VIP groups.
  • the VIP groups entities 1424 are used by load balancers within the system to route single IP addresses to multiple servers by way of VIP mapping.
  • An interface identification number is provided, and an interface port may be specified.
  • the variable set associated with the VIP groups entities 1424 is shown below in Table 43.
  • VARIABLE SET OF GROUPS ENTITIES 1424 The VIP groups entities 1424 are related to the virtual IPs entities 1312 of Figure 13 in a many-to-one relationship 1428, and to the interface IPs entities 1524 of Figure 15.
  • the entities illustrated in Figure 15 are part of the hardware entities 1108, and are illustrated in entity relationship diagram form. Each of these entities is described below. Each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the hardware portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new hardware devices, without requiring the rewriting of software code which relies upon the model and the database implementation thereof and permitting the reuse of existing software code to interact with the database model regarding the newly added hardware device.
  • the memory components entities 1502 describe various memory components of the devices related to the device entities 1512.
  • the variable set associated with the memory components entities 1502 is set forth below in Table 44.
  • the storage components entities 1504 relate to the storage components of devices associated with the devices entities 1512.
  • the variable set associated with the storage components entities 1504 is set forth below in Table 45.
  • the storage components entities 1504 relate to the devices entities 1512 in a many -to-one relationship.
  • the bus components entities 1506 are related to the bus components of the devices represented by the devices entities 1512.
  • the variable set associated with the bus components entities 1506 is set forth below in Table 46.
  • the bus components entities 1506 relate to the devices entities 1512 in a many-to-one relationship.
  • the interface components entities 1508 relate to interface components contained within interface cards of the devices represented by the devices entities 1512.
  • the variable set associated with the interface components entities 1508 is set forth below in Table 47.
  • the interface components entities 1508 relate to the interface cards entities 1510 and the interface type entities 1514 in many-to-one relationships. Also, the interface components interface 1508 relate to the sub interfaces entities 1520 in a one-to-many relationship. Interface Cards Entities 1 10
  • the interface cards entities 1510 relate to the interface cards contained within the devices represented by the devices entities 1512.
  • the variable set associated with the interface cards entities 1510 is set forth below in Table 48.
  • the interface cards entities 1510 relate to the devices entities 1512 in a many-to-one relationship.
  • the devices entities 1512 relate to the various devices connected to the network associated with the present invention. Multiple variables are for defining devices and communication with the network associated with the present invention. For example, information such as device and manufacturer identifications, serial numbers, device types, status, and other similar descriptions are provided for, along with other convenient variables, such as a flag which indicates whether a device should be monitored or not.
  • the MONITOR _FLG variable may be used in the future to determine the level of monitoring that should be performed for each device identified within the device's entities 1512.
  • the variable set associated with the devices entities 1512 is set forth below in Table 49.
  • the device's entities 1512 relates to the memory components entities 1502, the storage components entities 1504, the bus components entities 1506, the interface cards entities 1510, the device console entities 1516, and the CPU components entities 1518 in one-to-many relationships.
  • the devices entities 1512 also relate to the device authorizations entities 1416 in a one-to-many relationship 1426, the device request classes entities 1404 in a one-to-many relationship 1428, and the device application configuration entities 1414 in a one-to-many relationship 1430, all of which entities are illustrated in Figure 14.
  • the devices entities 1512 relate to the virtual IPS entities 1312 in a one-to-many relationship 1330, the conduits entities 1306 in a one-to-many relationship 1332, the status entities 1322 in a many-to-one relationship 1324, all of which are illustrated in Figure 13. Also, the devices entities may optionally be related in a one-to-many relationship 1248 to the device roles 1226 of Figure 12.
  • Interface Type Entities 1514 relate to the type of interface achieved through the interface components represented by the interface components entities 1508.
  • the variable set associated with the interface type entities 1514 is set forth below in Table 50.
  • the interface type entities 1514 relate to the interface components entities 1508 in a one-to-many relationship.
  • Device Console Entities 1516 relate to the interface components entities 1508 in a one-to-many relationship.
  • the device console entities 1516 relate to consoles that may be attached to devices represented by the device entities 1512.
  • the consoles may be for the convenience of a user in accessing information contained within the devices, or by accessing the network by way of the devices.
  • the variable set associated with the device console entities 1516 is set forth below in Table 51.
  • the device console entities 1516 relate to the device entities 1512 in a many-to-one relationship, as previously mentioned.
  • the CPU components entities 1518 relate to the various components of the CPUs of the devices which are represented by the device entities 1512.
  • the CPU components entities 1518 have a series of variables associated therewith indicate information regarding the type of CPU, the speed, the family, the model, the slot, and other such information, which may be necessary in provisioning servers, to ensure that software is installed can be adequately handled by the CPU on a particular device.
  • the variable set associated with the CPU components entities 1518 is set forth below in Table 52.
  • the CPU components entities 1518 relate to the devices entities 1512 in a many-to-one relationship, as previously mentioned.
  • the SUB interfaces 1520 relate the interface components of the interface components entities 1508 with the interface IP addresses of the interface IPs entities 1524. These SUB interfaces entities 1520 may be used with asynchronous transfer mode (ATM) frame relay systems, for example.
  • ATM asynchronous transfer mode
  • the variable set associated with the SUB interfaces entities 1520 is set forth below in Table 53.
  • the SUB interfaces entities 1320 is related to the interface components entities 1508 in a many -to-one relationship, and to the interface IPs 1524 in a one- to-many relationship.
  • the SUB interfaces entities 1520 may also be optionally related to the circuits entities 1522 in a many -to-one relationship. Circuits Entities 1522
  • the circuits entities 1522 may be use to optionally relate to the SUB interfaces entities 1520. These entities 1522 allow for specific identification of the circuits associated with the SUB interfaces and the interface components, and the type and description of the circuits.
  • the variable set associated with the circuits entities 1522 is set forth below in Table 54.
  • the circuits entities 1522 may optionally relate to the SUB interfaces entities 1520 in a one-to-many relationship.
  • the interface IPs entities 1524 may be used to relate the SUB interfaces represented by the SUB interfaces entities 1520 with VIP groups of the VIP groups entities 1424 shown in Figure 14.
  • the variable set associated with the interface IPs entities 1524 is set forth below in Table 55.
  • the interface IPs entities 1524 relates to the SUB interfaces entities 1520 in a many-to-one relationship and to the VIP groups entities 1424 of Figure 14 in a one-to-many relationship 1432.
  • the entities illustrated in Figure 16 are part of the DNS entities 1110.
  • the DNS entities 1110 relate to the assignment of DNS domain names. These entities are related in an entity relationship diagram fashion.
  • the DNS configuration entities 1602 allow for the translation of DNS names to DNS values, and may be used by the business logic associated with the network of the present invention. These DNS names and values may be translated into addresses related to various network hosts.
  • the variable set associated with the DNS configuration entities 1602 is set forth below in Table 56.
  • the DNS configuration entities 1602 are illustrated in Figure 16 as having no direct relationship with any of the other entities illustrated therein.
  • the values contained within the DNS configuration entities 1602 are used by business logic associated with the present invention, which is able to query the DNS configuration entity 1602 to relate between the entries of the name-value pairer associated with these entities 1602.
  • DNS Hosts Entities 1604 are used by business logic associated with the present invention, which is able to query the DNS configuration entity 1602 to relate between the entries of the name-value pairer associated with these entities 1602.
  • the DNS host entities 1604 relate to DNS hosts associated with the present invention.
  • the DNS host entities 1604 provide for a unique manner in which multiple DNS hosts may be identified. Using multiple DNS hosts provided customer with a more efficient DNS service. For example, if a primary DNS host is not able to handle a request within a predefined time, the expire time set on a second DNS may lapse, causing the secondary DNS to handle the pending request. This is also known as a time to live (TTL).
  • TTL time to live
  • the variable set associated with the DNS hosts entities 1604 are indicated below in Table 57.
  • the DNS hosts entities 1604 are related to the DNS domains entities 1616, and the DNS host types entities 1606 in many-to-one relationships.
  • the DNS host types entities 1606 in many-to-one relationships, the DNS hosts entities 1604 may optionally be related to the device role IP host entities 1308 illustrated in Figure 3 in a one-to-many relationship 1336.
  • the DNS host types entities 1606 indicate the types of DNS hosts associated with the DNS hosts entities 1604.
  • the variable set associated with the DNS hosts types entities 1606 is set forth below in Table 58.
  • the DNS host types entities 1606 are related to the DNS hosts entities 1604 in a one-to-many relationship.
  • the DNS ACLs entities 1608 relate to the access control lists associated with various DNS.
  • the variable set associated with the DNS ACLs entities 1608 is set forth below in Table 59.
  • the DNS ACLs entities 1608 are related to the DNS ACL entries entities
  • the DNS ACL entries entities 1610 relate to the ACL entries for the DNS.
  • the variable set associated with the DNS ACL entries entities 1610 is set forth below in Table 60.
  • the DNS ACL entries entities are related to the DNS ACLs entities 1608 in a many -to-one relationship, as previously mentioned.
  • the DNS allow transfers entities 1612 is used to determine whether or not DNS transfers may take place between given DNs domains according to the ACLs of the DNS ACLs entities 1608.
  • the variable set associated with the DNS allow transfers entities 1612 is set forth below in Table 61.
  • the DNS domain types entities 1614 relate to the types of DNS domains associated with the DNS domain entities 1616.
  • the variable set associated with the DNS domain types entities 1614 is set forth below in Table 62.
  • the DNS domain types entities 1614 relate to the DNS domain entities 1614 in a one-to-many relationship.
  • the DNS domain entities 1616 relate to the various DNS domains associated with devices connected to the network of the present invention.
  • the variables associated with the DNS domain entities 1616 relate to domains maintained by a host, in accordance with an embodiment of the present invention.
  • a DNS term "SOA" or start of authority is used to define several variables. For example, a serial variable is given, which indicates the revision number of the DNS file used to look up domain names.
  • a refresh rate is set, which may be adjusted according to the speed with which the DNS file is updated on a primary DNS, to control how often a secondary DNS updates its DNS file. Also, an expire time, which indicates the time that a secondary DNS will wait until taking over a domain name request may be set.
  • a minimum cash time for a particular entry, and a name server are provided for variables of the DNS domain entity 1616. Also, an admnistrative contact e-mail address is provided for each domain.
  • a retry variable may also be provided whereby after a certain amount of time, or a certain amount of attempts, a DNS must assume the role of the primary DNS. A rebuilt date is given, whereby the system, or agents of the system, know that if this date is changed, then the server needs to rebuild.
  • DNS entries are not created in the DNS server, but rather are contained within a separate database with specific forms that define acceptable DNS entries.
  • the variable set associated with the DNS domain entities 1616 is set forth below in Table 63.
  • a DNS domain entities 1616 are related in many-to-one relationships with the DNS domain types entities 1614, as previously discussed, and the DNS domain masters entities 1620. Additionally, the DNS domains entities 1616 relate to the DNS hosts entities 1604, the DNS allow transfers entities 1612, and the DNS queries entities 1618 in one-to-many relationships. Also, the DNS domains entities 1616 may optionally relate to the accounts entities 1702 of the network entities 1112, illustrated in Figure 17, in a many-to-one relationship 1624. DNS Allow Queries Entities 1618
  • the DNS allow queries entities 1618 assist in determining whether or not queries may be allowed between certain DNS domains, according to the DNs ACLs of the DNS ACLs entities 1608.
  • the variable set associated with the DNS allow queries entities 1618 is set forth below in Table 64.
  • the DNS allow queries entities 1618 related to the DNS ACLs entities 1608 and the DNS domains entities 1616 in many-to-one relationships.
  • DNS Domain Masters Entities 1620 The DNS domain masters entities 1620 relates the DNS domain of the DNS domain entities 1616 with the DNS master IPs of the DNS master IPs entities 1622.
  • the variable set associated with the DNS domain masters entities 1620 is set forth below in Table 65.
  • the DNS domain masters entities 1620 are related to the DNS domains entities 1616 in a one-to-many relationship, and to the DNS master IPs entities 1622 in a many-to-one relationship.
  • the DNS master IPs entities 1622 relate to the DNS master IP addresses of the devices on the network associated with the present invention.
  • the variable set associated with the DNS master IPs entities 1622 is set forth below in Table 66.
  • the DNS master IPs entities 1622 relate to the DNS domain masters entities 1620 in a one-to-many relationship.
  • the relationship 1336 is between the DNS host entities 1604 and an entity illustrated in Figure 13, within the configuration entities 1104. Additionally, the relationship 1624 relates the DNS domain entities 1616 with an entity in Figure 17 of the network entities 1112. The entities illustrated in an entity relationship diagram in Figure 17 form part of the network entities 1112.
  • the Network entities 1112 define various aspects of the network with which the present invention may be used. Each of these entities is described below.
  • the accounts entities 1702 relate directly to customer network accounts.
  • the variable set associated with the accounts entities 1702 is set forth below in Table 67.
  • the accounts entities 1702 relate to the account configuration entities 1704 and the customer tiers entities 1708 in one-to-many relationships. Additionally, as previously indicated, the accounts entities 1702 relate to the units entities 1202, the packages entities 1240, and the account roles entities 1224 of Figure 12, in one-to- many relationships. Also, the accounts entities 1702 may optionally be related in a one-to-many relationship 1624 with the DNS hosts entities 1604 of Figure 16. Account Configuration Entities 1704
  • the account configuration entities 1704 relate to the configuration of the accounts associated with the account entities 1702.
  • the variable set associated with the account configuration entities 1704 is set forth below in Table 68.
  • the account configuration entities 1704 relate to the accounts entities 1702 in a many -to-one relationship.
  • the account configuration values entities 1706 indicate various values associated with the configuration of various accounts related to the account configuration entities 1704.
  • the variable set associated with the account configuration values entities 1706 is set forth below in Table 69.
  • the account configuration values entities 1706 relate to the account configuration entities 1704 in many-to-one relationships.
  • the customer tiers entities 1708 relate to various customer tiers, whereby customers may receive, and have access to, specific services associated with specific tiers. For example, a specific customer may desire to distribute his webhosting servers to multiple data centers. Therefore, the variables associated with the Customer tiers entities 1708 may indicate a data center or identification number, which informs one as to the location of the customer tier represented by the customer tier entity 1708. Also, a flag may be set to indicate whether or not monitoring is desired or needed within that particular network.
  • the variable set associated with the customer tiers entities 1708 is illustrated below in Table 70.
  • the customer tiers entities 1708 relate to the accounts entities 1702, as previously discussed, and the data centers entities 1716, in many-to-one relationships.
  • the customer tiers entities 1708 also relate to the VLAM compartments entities 1714 in a one-to-many relationship.
  • the data center configuration values entities 1710 relate to the configuration values associated with the data center configuration, which are associated with the data center configuration entities 1712.
  • the variables associated with the data center configuration values entities 1710 are the value portion of a name-value pair relating to the data center.
  • a configuration value, associated with such a name-value pair is given by the data center configuration values entities 1710.
  • the variable set associated with the data center configuration values entities 1710 is set forth below in Table 71.
  • the data center configuration values entities 1710 relate to the data center configuration entities 1712 in a many-to-one relationship.
  • the data center configuration entities 1712 relate to the configuration of specific data centers that house specific servers, and other network equipment associated with services of the various customer tiers.
  • the data center configuration entities 1712 form the name portion of the name-value pair associated with the data center configuration values entities 1710.
  • a key name which serves as the name in the name-value pair.
  • the variable set associated with the data center configuration entities 1712 is set forth below in Table 72.
  • the data center configuration entities 1712 relate to the data centers entities
  • the VLAN compartments entities 1714 are used to relate the customer tiers of the customer tiers entities 1708 with various VLAN IP pools of the VLAN IP pools entities 1722.
  • the variable set associated with the VLAN compartments entities 1714 is set forth below in Table 73.
  • the VLAN compartments entities relate to the customer tiers entities 708 in a many -to-one relationship as previously discussed, also, the VLAN compartments entities 1714 relate to the VLAN IP pools 1722 in a one-to-many relationship.
  • the data centers entities 1716 relate to various data centers in which server equipment, and other network devices are housed.
  • the data centers entities 1716 contain variables that describe various aspects of the data centers to which these entities 1716 relate. For example, a DNS sequence is given, which is a sequential number, that is used in an algorithm to provide a next random DNS name.
  • the DNS names used by each of the data center entitties 1716 contain the name of the data center therein, with which they most closely relate, and therefore there is no conflict of DNS names between data centers.
  • a mask may be given that indicates how a particular server may be located by way of parsing the location of its rack.
  • the variable set associated with the data centers entities 1716 is set forth below in Table 74.
  • the data center entities 1716 relate to the customer tiers entities 1708 and the data center configuration entities 1712 in one-to-many relationships.
  • Site Configuration Entities 1718
  • the site configuration entities 1718 relate to a configuration of various data center sites.
  • the site configuration entities 1718 is a name- value pairer that may be used for any convenient purpose, such as accounting, data center, maintenance, device configuration, and the like. This relationship table may be used by way of business logic associated with the present invention, or with agents residing on particular devices connected to the network.
  • the variable set associated with the site configuration entities 1718 is set forth below in Table 75.
  • the site configuration entities 1718 illustrated in Figure 17 is not directly related to the entities illustrated in the same figure. However, the values contained therein may relate to other entities illustrated in Figure 17, and may be used by business logic associated with the present invention, or by intelligent agents of the system.
  • the device pool VLAN platforms entities 1720 relate to platforms of the device pool within the VLAN. That is, the device pool VLAN platforms entities 1720 is used to relate a base OS to the VLAN with which a particular device is associated.
  • the variable set associated with the device pool VLAN platforms entities 1720 is set forth below in Table 76.
  • the device pool VLAN platforms entities 1720 relate to the VLAN IP pools entities in a many -to-one relationship.
  • the VLAN IP pools entities 1722 relate to IP pools of the VLAN, which are associated with the VLAN compartments of the customer tiers that are associated with the customer tiers entities 1708.
  • the variable set associated with the VLAN IP pools entities 1722 is set forth below in Table 77.
  • VARIABLE SET OF VLAN IP POOLS ENTITIES 1722 The VLAN IP pools entities 1722 relate to the VLAN compartments 1714 in a many to one relationship, and to the device pool VLAN platforms 1720 in a one to many relationship, as previously described. Also, the VLAN IP pools entities 1722 relate to the IP addresses entities 1730 in a one to many relationship, and the VLAN subtype entities 1728 in a many to one relationship. Data Center Tiers Entities 1724
  • the data center tiers entities 1724 relate to a specific group of services, or tiers, associated with the data centers, which are represented by the data centers entities 1716.
  • the variable set associated with the data center tiers entities 1724 is set forth below in Table 78.
  • the data center tiers entities 1724 relate to the data centers entities 1716 in a many to one relationship, as previously explained.
  • the data center tiers entities 1724 also relate to the application rules entities 1236, illustrated in Figure 12, in a many to one relationship 1244.
  • the VLAN pool type entities 1726 define the various valid types of VLANs for use on the network associated with the present invention.
  • the variable set associated with the VLAN pool type entities is set forth below in Table 79.
  • VLAN pool type entities 1726 are not illustrated as directly relating to any entities within Figure 17. However, the variables stored within the VLAN pool type entities 1726 are used by the logic associated with the present invention for determining the valid types of VLANs that may be used with the present invention.
  • the VLAN SUB type entities 1728 are used to relate to the VLAN IP pools, which are represented by the VLAN IP pools entities 1722.
  • the VLAN SUB type entities 1728 define valid VLAN types, or types in which VLANs may be used. Some examples might include development, quality assurance, production, and the like.
  • the VLAN subtype entities 1728 relate to the VLAN IP pools 1722 in a one to many relationship, as previously described.
  • the variable set of the VLAN SUB type entities 1728 is shown below in Table 80.
  • the IP address entities 1730 relate to the IP addresses of the network associated with the present invention.
  • the variable set associated with the IP address entities 1730 is shown below in Table 81.
  • the IP address entities 1730 relate to the VLAN IP pools 1722 in a many to one relationship, as previously discussed. Also, the IP addresses entities 1730 relate to the virtual IPs entities 1312, and the device role IP host entities 1308 by one to many relationships, 1338, 1340, respectively
  • the VLAN CIDR reserve entities 1732 is related to the classless inter- domain routing (CIDR) of the VLAN associated with the present invention.
  • the VLAN CIDR reserve entities indicates the CIDR number used for the network, and the number of addresses that are reserved and that are available for dynamic assignment as DHCP generated addresses.
  • the variable set associated with the VLAN CIDR entities 1732 is set forth below in Table 82.
  • VARIABLE SET OF VLAN CD3R RESERVE ENTITIES 1732 The VLAN CIDR reserve entities 1732 is illustrated in Figure 17 as not directly relating to any of the other entities. These entities 1732 are used by the business logic of the present invention to determine the number of network addresses that may be reserved, and the number that may be generated as DHCP generated addresses for a given network or subnetwork. QIJEUES 1114
  • the entities illustrated in the entity relationship diagram of Figure 18 form the queues entities 1114. These entities are described in detail below. These entities are not directly related to the entities of the rest of the data model 1100 shown in Figure 11 but rather are used by agents of specific devices connected to the network in performing various tasks. These tasks are represented in queues, which may be executed in a specific, given order.
  • the agent queues entities 1802 queues entities are essentially a list of tasks to be performed by an intelligent agent operating on a device connected to the network, which is associated with the present invention.
  • the variable set of agent queues entities 1802 is shown below in Table 83.
  • agent queues entities 1802 is illustrated as having a one to many relationship with the agent queue commands entities 1804.
  • agent queues entities 1802 may also have an optional one to many relationship with other agent queues, as illustrated by the broken line in Figure 18.
  • the agent queue commands entities 1804 serves to relate the agent queues entities 1802 with specific agent commands and agent command outputs.
  • the variable set of agent queue commands entities 1804 is shown below in Table 84.
  • agent queue commands entities 1804 are related to the agent queues entities 1802, as previously discussed, and the agent commands 1808 in many to one relationships. Also, the agent queue commands entities 1804 are related to the agent command output entities 1806 in a one to many relationship. Agent Command Output Entities 1806
  • the agent command output entities 1806 relate to the output of specific commands to agents of the present invention.
  • the variable set of agent command output entities 1806 is shown below in Table 85.
  • the agent command output entities 1806 relate to the agent queue commands entities 1804 in a many to one relationship.
  • agent commands entities 1808 represent specific commands to be executed by agents associated with the present invention.
  • the variable set of agent commands entities 1808 is shown below in Table 86.
  • the agent commands entities 1808 relate to the agent queue commands entities 1804, as previously indicated, and the agent command text entities 1810, in one to many relationships.
  • the agent command text entities 1810 represents specific text associated with the agent commands, which are represented by the agent command entities 1808. Additionally, an order of the text may be given, thereby allowing the agent to determine the order of the text to be executed.
  • the variable set of agent command text entities 1810 is shown below in Table 87.
  • the agent command text entities 1810 relate to the agent commands entities 1808 in a many to one relationship.
  • the agent queue mutex entities 1812 serves as a locking device, which signals to an agent at a particular device is currently busy, and prevents the agent from executing a second queue on that device until the device is not busy.
  • the variable set of agent queue mutex entities 1812 is shown below in Table 88.
  • agent queue mutex entities 1812 do not relate directly to any of the entities illustrated in Figure 18, but rather are either queried by the agents with which they are associated, or broadcast information to those agents.
  • the agent command mutex entities 1814 serve as a locking device whereby only a single agent queue may be executed by the agent at any given time. This prevents an agent from attempting to accomplish more than one task at a single time.
  • the variable set of agent command mutex entities 1814 is shown below in Table 89.
  • agent command mutex entities 1814 do not relate directly to any of the entities illustrated in Figure 18, but rather are either queried by the agents with which they are associated, or broadcast information to those agents.
  • the present invention provides a data model for use in system for the automated provisioning of devices which constitute the infrastructure of a website, such as servers.
  • Two significant advantages provided by the data model are flexibility and the repeatability of the results that are obtained.
  • the flexibility permits the varied needs of different websites to be readily accommodated, and thereby avoids the limitation of having to configure the architecture of every site the same way.
  • the repeatability ensures that every server will have the proper set of software components once it has been provisioned, and thereby be ready to operate immediately.
  • the automated provisioning that is provided through this system achieves a significant time savings, enabling the entire process to be accomplished in substantially less than one hour for each device.

Abstract

The present invention is directed to a data model. The data model allows for modeling of all information relating to a computer network to be conveniently stored in a database in a manner which minimizes the effort associated with the addition of new devices to the network and maximizes software code reuse. The information relating to the network that may be modeled in the data model of the present invention include: software information, configuration information, monitoring information, hardware information, domain name server (DNS) information, network information, and information regarding queues that may be used by business logic, or intelligent agents in accessing and maintaining various portions of the network.

Description

A DATA MODEL FOR AUTOMATED SERVER CONFIGURATION
BACKGROUND
The present invention is directed to the provisioning, or configuration, of servers and other devices that provide support for sites that are hosted on the Internet, intranets, and other communication networks. More particularly, the present invention is directed to a data model which can be implemented using a database and which serves as a repository for information pertinent to the provisioning or configuration, of devices on a communications network. The growing popularity and increasing accessibility of the Internet has resulted in its becoming a major source of information, as well as a vehicle for inter-party transactions, in a variety of environments. For instance, a number of different types of entities, from government agencies to school systems to organized groups, host Internet and/or intranet websites that provide informational content about themselves and topics related to their interests. Similarly, commercial enterprises employ websites to disseminate information about their products or services, as well as conduct commercial transactions, such as the buying and selling of goods. To support these activities, each website requires an infrastructure that stores the information provided by that site, responds to user requests for the information, and conducts other types of transactions appropriate to the site. A significant component of this infrastructure is a web server, which receives requests for information, retrieves it from the appropriate sources, and provides it to the requestor. Websites which provide more complex services, such as online ordering, may also include application servers to support these additional functions.
In the case of relatively small entities, the infrastructure to support a website may be as simple as a single server, or even a portion of a server. Conversely, a large, popular website that consists of several thousand pages of information and that is accessed quite frequently may require numerous web servers to provide the necessary support. Similarly, websites for commercial entities, via which transactional operations are conducted, may employ multiple application servers to support transactions with a large number of customers at one time.
The present invention is particularly directed to a data model which supports a website by facilitating provisioning of the servers, allowing appropriate software necessary for the site to be identified, located, and transferred to a server, and generally defining all aspects of the network. Such provisioning initially occurs when the website is first launched. Thereafter, there may be a need for further provisioning, particularly in the case of a successful website, when additional servers must be added to support increased traffic, which requires accurate modeling of all aspects of the network. In another instance, provisioning of the servers may be required as part of a disaster recovery operation, for example a sudden interruption in power, an attack by a hacker, or corruption of stored software and/or data. In such an instance, it would be necessary to have an accurate model of all aspects of the server to allow for accurate reproduction of the server in need of recovery. The provisioning of a server or other device that supports the operation of a website involves several discrete steps. First, the appropriate operating system software must be loaded onto the device, followed by networking software that enables the device to communicate over a network. Thereafter, software applications that are required to support the particular site are loaded, such as database software for retrieving web pages, credit card processing software, order processing software, etc. Finally, the content associated with the individual pages of the website must be loaded. The order in which these various components are loaded onto the server can be quite critical, to ensure compatibility of the various programs with one another. In the past, the provisioning of web servers was often carried out manually. In other words, each item of software was individually loaded onto the server by a person having responsibility for that task. One problem with such an approach is the fact that it consumes a significant amount of time. For a relatively large site that is supported by multiple servers, the provisioning could take several hours or days to be completed, thereby delaying the time before the site can be launched and/or upwardly scaled to accommodate increasing traffic. Another, and perhaps more significant, limitation associated with the manual provisioning of devices is the lack of repeatability in the software configurations. More particularly, whenever manual operations are involved in the installation of software, there is always the possibility of human error, such as the failure to install one of the required components, or the loading of the various items of software in the wrong order. Each of these types of errors can result in misoperation or total failure of the website, and can be extremely time consuming to discover and correct. To overcome some of these limitations, various techniques have been developed which permit software to be automatically deployed to computers. However, these techniques are limited in the types of environments in which they can be utilized. For example, in an enterprise where all of the users interact with the same legacy applications, a "cookie cutter" type of approach can be used to deploy the software. In this approach, every computer can have the same, standard configuration. Once the configuration has been developed, therefore, it can be packaged into a fixed format, and automatically disseminated to all of the appropriate computers.
However, this type of automated deployment is not effective for situations in which computers, such as servers, need to be customized to accommodate the individual requirements of varied users. One example of such a situation is a data center which may house the infrastructure for hundreds of different websites. The hardware and software requirements for these sites will vary among each site. For instance, different website developers may employ different platforms for the sites, thereby necessitating various combinations of operating systems and application programs on the servers of the respective sites. Furthermore, different types of equipment may be utilized for the sites, thereby adding to the complexity of the provisioning process. In some cases, the same site may require a variety of different hardware devices, operating systems and application programs to handle all of the different services provided by that site. Known approaches to automate software deployment are not adapted to the needs of these types of situations. Rather, because of the flexibility that is required to accommodate a different configuration of hardware and/or software for each site, manual provisioning is still being practiced to a large extent, with all of its attendant disadvantages.
It is desirable, therefore, to provide a data model to support the automated provisioning of servers and other devices that support various types of services, such as the hosting of an Internet or intranet website. Such a data model should exhibit sufficient flexibility to accommodate the differing needs of the providers of such services, while maintaining repeatability, and hence reliability, in the provisioning process.
SUMMARY
In accordance with the present invention, the foregoing objectives are achieved by way of a data model to support the automated provisioning of servers and other devices that support various types of services, such as hosting of an Internet or intranet website. This data model provides relationships between various software, configuration, monitoring, hardware, network, domain name server (DNS), and queues entities. By representing the model in an entity relationship form, the present invention facilitates allowing access to and configuration of each aspect of a database which implements the model and thus, to each aspect of the network. This, in turn, allows for automated provisioning by devices located remotely on the network with which the data model of the present invention is associated. The central database which implements the data model of the present invention contains all information that is relevant to the provisioning of devices contained on the network. This information includes information regarding the hardware devices used on the network, the software components that make up the various software roles installed on a device, logical network information such as IP addresses, configuration information of the various software, hardware, and network components, domain name information, and the like. Additionally, information regarding monitoring status of the network, and devices contained thereon is provided for. Additionally, an interface for various network agents associated with each host on the network for reporting configuration regarding devices connected to the network, reporting version information, upgrading software contained thereon, and so forth, is provided for.
According to exemplary embodiments of the present invention, the data model allows for modeling of all information relating to a computer network to be conveniently stored in a database in a manner which minimizes the effort associated with the addition of new devices to the network and maximizes software code reuse. This is accomplished by designing a model wherein each of the model's entities interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the network (or portion thereof) that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new software, new hardware devices, new monitoring techniques and equipment, new configurations, etc., without requiring the rewriting of software code which relies upon the model and the database implementation thereof. Moreover, the schema described herein facilitate the reuse of existing software code to interact with the database model regarding newly added software, hardware, configurations, etc. by virtue of this design aspect of the model.
Various segments of models according to exemplary embodiments of the present invention are separately implementable. These and other features of the present invention are explained in greater detail hereinafter with reference to an exemplary embodiment of the invention illustrated in the accompanying drawings, wherein like components are designated by like reference numerals.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 is block diagram of one embodiment of the hardware configuration for website hosting.
Figure 2 is a block diagram of services associated with a network, in connection with one embodiment of the present invention. Figure 3 is a block diagram of a website maintenance system, associated with one embodiment of the present invention.
Figure 4 is a block diagram of roles used in connection with one embodiment of the present invention.
Figure 5 is a role-centric entity relationship diagram, used in connection with one embodiment of the present invention.
Figure 6 is a service-centric entity relationship diagram, used in connection with one embodiment of the present invention.
Figure 7 is a block diagram illustrating the relationship between various elements of one embodiment of the present invention. Figure 8 is a block diagram illustrating the relationship between various elements of one embodiment of the present invention.
Figure 9 is a block diagram illustrating the relationship between units, bundles, and roles, in accordance with one embodiment of the present invention.
Figure 10 is an entity relationship diagram illustrating the relationship between units, roles, and packages, in accordance with one embodiment of the present invention. Figure 11 is an entity relationship diagram illustrating the relationship between various aspects of the data model, in accordance with one embodiment of the present invention.
Figure 12 is an entity relationship diagram illustrating the relationship between various entities relating to software within the data model of one embodiment of the present invention.
Figure 13 is an entity relationship diagram illustrating the relationship between various entities relating to configuration within the data model of one embodiment of the present invention. Figure 14 is an entity relationship diagram illustrating the relationship between various entities relating to monitoring within the data model of one embodiment of the present invention.
Figure 15 is an entity relationship diagram illustrating the relationship between various entities relating to hardware within the data model of one embodiment of the present invention.
Figure 16 is an entity relationship diagram illustrating the relationship between various entities relating to DNS capabilities within the data model of one embodiment of the present invention.
Figure 17 is an entity relationship diagram illustrating the relationship between various entities relating to network within the data model of one embodiment of the present invention.
Figure 18 is an entity relationship diagram illustrating the relationship between various entities relating to queues within the data model of one embodiment of the present invention.
DETAILED DESCRIPTION
To facilitate an understanding of the principles of the present invention, it is described hereinafter with reference to its application in a specific embodiment. Specifically, the data model of the present invention will be described within the context of a database which implements the model, which database is used in a computer network for the automated provisioning, and remote configuration and maintenance, of multiple computer devices connected to the network. It will be appreciated, however, that the implementation of the invention that is described hereinafter is merely exemplary, and that the invention can find practical application in any environment where it is desirable to model a database associated with a server on a computer network of any kind.
Figure 1 illustrates, in block diagram form, the hardware configuration of one embodiment of the present invention. In Figure 1, a typical, three-tier web hosting system 100, which may be implemented using the data model of the present invention, is illustrated. Therein, databases 102A, 102B are accessible to the web servers 104A, 104B, and the application servers 106A, 106B of the three- tier web hosting system 100 illustrated in Figure 1. In the three-tier system 100 illustrated in Figure 1, redundancy is used, whereby a duplicate web server 104B, application server 106B, and database 102B are each used as backups for the primary web server 104A, application server 106A, and database 102A, respectively.
Each of the web servers receives and handles requests received by way of a network. Requests received by way of such a network may require functionality from various applications. When this is the case, the web server 104A, 104B forwards the requests to the application server 106A, 106B, which may then process the application, and also has access to the database 102A, 102B. The application server 106A, 106B may, therefore, require information regarding software, configuration, monitoring, hardware, the network, DNS, or queues, which may be contained within the database 102A, 102B. This information is modeled by one embodiment of the present invention to allow for rapid and convenient access by the application server 106A, 106B to this information contained within the database 102 A, 102B. Network requests are received by the web server 104A, 104B by way of a firewall 108, and are distributed by the load balancer 110. The firewall 108 provides security from any malicious network forces outside the local access of the three-tier web hosting system, 100. Any remote host, or agent, which is outside the locality of the three-tier web hosting system 100 may be required to authenticate itself to the firewall 108 in order to access, maintain, monitor, or reconfigure the web server 104A, 104B, the application server 106A, 106B, or the database 102A, 102B. The load balancer 110 distributes the network transactions received by way of the firewall 108. It should be noted that a common practice is to insert an additional firewall between the application servers 106A, 106B and the databases 102A, 102B. While many people feel that this provides additional security, this redundancy is often not required if the firewall 108 is correctly configured. However, it should be noted that the present invention could be utilized in a system wherein a second firewall is used between the application servers 106A, 106B, and the databases 102A, 102B. The three-tier web hosting system 100 illustrated in Figure 1 is a robust architecture, which is suitable for use in almost any business situation. Thus, the data model of the present invention finds utility in almost any business situation. Figure 2 is a block diagram illustrating the relationship of various services provided by a web hosting system in which the present invention can be implemented. The relationship model 200 illustrated in Figure 2 comprises a variety of functional components, which relate to a web server 202, and an application server 204 connected to a network, such as the Internet 205. Functions relating to the web server 202 and the application server 204 include a software maintenance component 206, and a monitoring component 208. As illustrated by the bi-directional arrows in Figure 2, the web server 202 and application server 204 may access information, and functionality, possessed by the software maintenance component 206 and the monitoring component 208. Likewise, the software maintenance component 206 and monitoring component 208 may provide the web server 202 and application server 204 with information, and may access information contained on the servers 202, 204.
The web server 202, which is in communication with the application server 204, may request functionality to be performed by various applications. This functionality may be subdivided into two categories: website content and personalized information. Website content is represented by the content feed component 210, and personalized information is represented by the personalization component 212, which are both in communication with the application server. Both the content feed component 210 and the personalization component 212 may be monitored by the monitoring component 208, and may receive software maintenance support from the software maintenance component 206. The manner in which the monitoring component 208, the software maintenance component 206, the network 205, the hardware devices 202, 204, and the configuration components 210, 212 are related is defined by the data model of the present invention.
According to an embodiment of the present invention, the web server 202 may comprise a layer 7 proxy server. The monitoring component 208 monitors the status of the hardware components, such as the web server 202 and application server 204, and monitors the content feed 210 and the personalization component 212. In response to this monitoring, the web server 202 or application server 204 may request the software maintenance component 206 to provide maintenance, which may be in the form of software updates, to any of the hardware components 202, 204, the content feed component 210, or the personalization component 212. The content feed component 210 may communicate any information which is fed into the system 200, while the personalization component 212 provides data and information that is specific to a particular site hosted by a web server, or layer 7 proxy server 202. One example of information that is fed into the system 200 by way of the content feed component 210 is streaming data from an external source, such as stock market ticker data. In Figure 3, a system 300 is illustrated, which is suitable for automated provisioning, remote access and maintenance of network devices. Another system in which models according to the present invention can be implemented is described in U.S. Patent Application Serial No. 09/699,329, entitled "AUTOMATED PROVISIONING FRAMEWORK FOR INTERNET SITE SERVERS" to Raymond Suorsa et al. filed on an even date herewith, the disclosure of which is incorporated here by reference. A database 302 can be used to implement the data model according to exemplary embodiments of the present invention. This database 302 may reside on any large scale storage device. For example, suitable storage devices upon which the database associated with the data model of the present invention may be stored include redundant array of independent disks (RAID) systems, such as those provided by EMC Corporation of Hopkinton, MA, or other similar devices. This database 302 may be accessed by the various agents 304A, 304B, 304C, whose level of access may be determined by a hierarchy of trust component 306. Additionally, a user interface 308 may be provided for the convenience of a user in accessing information contained within the database 302, or software contained within the software file system 310. The determination of the level of access granted by the user interface 308 is made by the hierarchy of trust component 306. Access determination information is stored by the access determination component 312, which is accessible by way of database 302. This is accomplished by using a hierarchical file structure in which specific access is determined and operated only to those users to whom it should be granted. This is accomplished by user authentication via a lightweight directory access protocol (LDAP) server that authenticates users within particular domain names that map to specific customer accounts. The hierarchy of trust component 306 interprets the data related to it from the database 302, and communicates this data, or the interpretation thereof to the various agents 304A, 304B, 304C, and/or the user interface 308. In Figure 4, a block diagram of a customer role package 400 is illustrated. Such customer role packages are used to provide repeatability, and eliminate the need for manual configuration by designating software components to be installed on a particular device connected to a network. Roles as illustrated in Figure 4 define the functionality of device, and may be considered to define the role, or part, the device is to play within the network.
In one embodiment of the invention, the software components to be installed (i.e., the customer role package 400) are divided into three types of software roles that are related to the frequency with which they are likely to change or be upgraded. These roles include an application role 402, a customer code role 404, and an operating system (OS) role 406. The OS role 406 contains the software that has the lowest probability of being changed during the life cycle of the particular device on which it is installed. This role consists of the OS of the device, plus other general software, such as the intelligent agents 304A, 304B, 304C, illustrated in Figure 3. The customer code role 404 contains content specific to, and provided by, a customer, and therefore contains software that can change on a regular basis for a website or other network site. Examples of software contained within the customer code role 404 might include hypertext markup language (HTML) pages, Java server pages (JSP), active server pages (ASP), image files, and other content that is regularly updated by a website host. The application role 402 consists of software components that change relatively infrequently when compared to software of the customer code role 404, but perhaps more often than software contained within the OS role 406. The hierarchical structure of such a customer role package 400 is described hereinafter in connection with Figure 9.
An entity relationship diagram of a role-centric network model 500 is illustrated in Figure 5. The role-centric model 500 is used for relating devices 502 connected to a network to software roles 504. This is accomplished by way of a role instance 506, which is used as a place holder for devices until a device 502 is present, and connected to the network by way of which the role 504 may communicate the software contained therein to the devices 502. This role-centric model 500 allowed for a role instance 506 that reserved IP addresses, or other network addresses, and allowed for general network configuration without the devices being attached to the network. Thus, the IP addresses used by the various devices connected to the network may be maintained, and need not be reassigned each time a device is reconnected to the network at a different location.
Entity relationship diagrams, such as the entity relationship diagram of the role-centric model 500, show the relationship between various entities, which are represented by rectangular blocks and labeled to indicate their significance connected by way of connection lines. Each connection line has a single connection on one end and multiple connections on the opposite end, indicating a one-to-many relationship. This means that a single entity is related to multiple entities on the end of the connection line having multiple connections. Thus, the devices entity 502 relates to the role instance entity 506 in a one-to-many fashion, meaning that each device entity 502 is directly related to many role instance entities 506. Additionally, the role entity 504 is related to the role instance entity 506 in a one-to-many relationship. Hence, each role entity 504 is related to multiple role instances 506. Figure 6 illustrates an improved approach to the traditional role-centric network model approach illustrated in Figure 5. In Figure 6, a service-centric network model 600 that allows one to monitor service information related to devices 602 associated with a computer network is shown. This type of model is accomplished, as illustrated in the entity relationship diagram of Figure 6, by relating devices entities 602 to service instance entities 604 in a one-to-many relationship. The service instance entities 604 are then related to services 606 in a many-to-one relationship. The services entity 606 is related to the roles entity 608 in a one-to-many relationship. The service instance entities 604 act as a relationship table between the devices 602 and the services 606. The advantages of the service-centric model 600, which is employed by one embodiment of the present invention include all of the advantages of the role-centric model 500, illustrated in Figure 5, as the network may be configured using place holders instead of devices connected to the network. The service-centric model has the additional advantage of relating the roles to services, which are an important quantity for customers to monitor and configure. An embodiment of the present invention utilizes a service-centric model, such as the one illustrated in Figure 6.
The block diagram in Figure 7 illustrates a service-centric concept, relating services 702 to various other quantities associated with the network that in accordance with an embodiment of the present invention. The services 702 are centrally related to each of: the devices 704, the configuration component 706 of the network, the monitoring 708 of the network, hardware, and software, and the software 710, such as the OS software, packages, and roles hereinbefore described. By way of the service-centric system illustrated in Figure 7, the monitoring component 708 may monitor the software component, ensuring that each of the software roles is properly maintained, and up to date.
Figure 8 illustrates a similar configuration, wherein services are centrally related to a configuration component 706, a monitoring component 708, and software 710. However, the service-centric relationship illustrated in Figure 8 differs from the one illustrated in Figure 7 in that the services 702 are not related directly to devices. Rather, the services 702 are related directly to a service instance 802, which allows for the configuration of an IP address by a configuration device. This service instance 802 is related to devices 804 upon which an IP is configured. Thus, although the services 702 in Figure 8 are not directly related to devices, as is the case in Figure 7, in Figure 8, the services 702 are related to a service instance 802 which allows for the configuration of IP addresses until a device 804 may be configured with an IP address, and acts as a place holder for devices to be connected and utilize the IP addresses. Figure 9 illustrates the hierarchy of individual software roles. Role 902 of Figure 9 comprises a combination of software bundles and units. The software units 904, 906, 908 each comprise multiple software installation packages. One example of such software installation packages that may be contained within units 904, 906, 908 includes software bundles for the Linux OS, such as Redhat package manager (RPM) files. Such packages would be saved in a file having a name using the extension RPM, such as file x.rpm.
Several units, such as units 904, 906, make up a bundle, 910. In addition, a bundle 912 may be made up of a combination of units, such as unit 908, and other bundles, such as bundle 910. These bundles are then combined into a role, such as role 902. This role 902 is stored as a list of packages, such as RPMs, to be installed on a device, and the order in which those packages are to be installed. These roles may, therefore, be used to rebuild a machine automatically, should a critical failure occur. Also, the role 902 illustrated in Figure 9 may comprise a customer role package, such as the package 400 illustrated in Figure 4, which contains three roles: the application role 402, the customer code role 404, and the OS role 406.
Figure 10 illustrates the same relationships shown in Figure 9 in the form of an entity relationship diagram. In Figure 10, roles entities 1002 are related to units entities 1004 and packages entities 1006. These three groups of entities are related by way of two relationship tables 1008, 1010. The roles entities 1002 represent a role, such as role 902 of Figure 9, or a group of roles. These roles entities 1002 are made up of multiple units entities 1004, which represent units, such as units 904, 906, 908 of Figure 9. This is illustrated by the one-to-many relationship between the units entities 1004 and the relationship table 1008, which is related in a one-to-many relationship with the relationship table 1010. This relationship table 1010 is related to the roles entities 1002 in a many-to-one relationship. Thus, the roles represented by the roles entities 1002 may be made up of multiple units, which are represented by the units entities 1004. Additionally, the units represented by the units entities 1004 may be made up of multiple packages, such as the RPMs discussed above. These packages are represented by the packages entities 1006, which are related in a one-to-many relationship with the relationship table 1008 which is in turn related to the units entities 1004 in a many-to-one relationship. The packages 1006 are illustrated as having a one-to-many relationship with other packages, which indicates that any single package may contain multiple packages.
The relationship diagram illustrated in Figure 10 is a particularly useful way to illustrate the relationship between the various components of a data model. As can be seen, much information can be gleaned from the entity relationship diagram of Figure 10, and less space is required to express the same idea illustrated in Figure 9. The entity relationship diagram also allows for convenient access to each aspect of the database being modeled for quick, accurate, and repeatable configuration of that database. An entity relationship diagram of the data model according to one embodiment of the present invention is illustrated in Figure 11. In Figure 11, the data model 1100 is represented as having multiple entities related to one another. Each of these entities illustrated in Figure 11 represents a group of entities and therefore Figure 11 represents the data model on a macro level only. Each of the entities represented in the data model 1100 of Figure 11 is broken into its components, and illustrated in more detail in subsequent figures, which are denoted in Figure 11.
The data model 1100 in Figure 11 relates the following entities: software 1102, configuration 1104, monitoring 1106, hardware 1108, DNS 1110, network 1112, and queues 1114. The software entities 1102 represent various software packages to be installed in devices, applications, and operating system software of the various network devices. The software entities 1102 are directly related to the configuration entities 1104, the hardware entities 1108, and the network entities 1112. As shown in Figure 11, the software entities 1102 have an optional many- to-one relationship with the hardware entities 1108, and shares a combination of many-to-one and one-to-many relationships with both the configuration entities 1104 and the network entities 1112.
As described above, the configuration entities 1104 are related to the software entities 1102 with a many-to-one and one-to-many relationship, and similarly share a many-to-one and one-to-many relationships with the hardware entities 1108. Additionally, the configuration entities are related to the monitoring entities 1106 in a one-to-many relationship. The configuration entities 1104 relate to both the DNS entities 1110 and the network entities 1112 in a many-to-one relationship. The relationship with the DNS entities 1110 is optional, as indicated by the broken line connecting the configuration entities 1104 and the DNS entities 1110. These configuration entities 1104 represent the configuration of various network addresses, software packages, and device addresses.
The monitoring entities 1106 are related to the configuration entities 1104 as described above, and to the hardware entities 1108 in many-to-one relationships. The monitoring entities 1106 monitor the status and condition of entities within the configuration entities group 1104 and the hardware entities group 1108.
The hardware entities 1108 represent multiple hardware devices in communication with a network. These entities are related to the software entities 1102 in an optional one-to-many relationship, and as described above to the monitoring entities 1106 in a one-to-many relationship. Additionally, as described above, the hardware entities 1108 are related in both a many-to-one and one-to- many relationship with the configuration entities 1104. The DNS entities 1110 represent all DNS transfers, queries, entries, configurations, and posts. They are optionally related to the configuration entities 1104 in a one-to-many relationship, and to the network entities 1112 in an optional many-to-one relationship. The network entities 1112 are related to the software entities 1102 in a combination of many-to-one and one-to-many relationships, and to the configuration entities 1104 in a one-to-many relationship. Additionally, the network entities 1112 are optionally related to the DNS entities 1110 in a one-to- many relationship.
A group of entities called the queues entities 1114 are also illustrated in the database model 1100 of Figure 11. However, the queues entities are not illustrated as having a direct relationship with any of the other entities of this model 1100. A relationship between the queues entities 1114 and the other entities within the data model 1100 is created by either business logic contained outside of the data model, or by intelligent agents, such as the agents 304A, 304B, 304C illustrated in Figure 3. This type of relationship will be described hereinafter with greater detail.
Figures 12-18 illustrate in greater detail the entities of the data model 1100 illustrated in Figure 11. In each of these figures, multiple entities that make up the entities represented in Figure 11, will be shown as entity relationship diagrams. In this type of diagram, the one-to-many or many-to-one relationships between the entities will be illustrated in the same manner as in Figure 11. Optional relationships will be illustrated by way of broken lines. Connections to entities within other groups of entities (i.e. written other entities of the data model 1100 in Figure 11), will be indicated by lines at the edge of the page with a designation indicating the figure upon which those relationships are continued.
Each of the entities contained within Figures 12-18 have a set of variables associated with them, specific values of which characterize instances of each of the entities and their functionalities. These variables will be described hereinafter in tables. In these tables identifying variables associated with each entity, a variable name, variable definition, variable type, and an indication regarding whether the variable is required by the entity or optional to the entity will be given. Those skilled in the art will appreciate that the reference herein to "required" or " optional" with respect to the individual variables in each table is purely exemplary and that, in other exemplary embodiments which are not explicitly described herein, the status of these variables as "required" or "optional" may change. Additionally, an indication of the primary key of each entity of each variable set will be given by an asterisk immediately following the variable name. In some cases, multiple primary keys will be indicated. Generally, the primary key of a particular entity must be contained within each of the entities to which that entity relates and is the main variable associated with the entity. When the primary key of an entity is contained within another entity to which the first entity relates, it acts as a type of pointer, referring to the first entity.
SOFTWARE 1102
In Figure 12, a detailed entity relationship diagram of the software entities 1102 is illustrated. Each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g. , new software packages, without requiring the rewriting of software code which relies upon the model and the database implementation thereof.
Units Entities 1202
The units entities 1202 represent the software units described in connection with Figure 10. The variable set associated with the units entities 1202 is set forth below in Table 1.
Figure imgf000022_0001
TABLE 1: VARIABLE SET OF UNITS ENTITIES 1202
The units entities 1202 relate to unit monitor types entities 1204, unit contents entities 406, application role units 1208, unit packages entities 1212, account role units entities 1214, device pool role units entities 1216 and one-to- many relationships. The one-to-many relationship between the units entities 1202 and the unit conflicts entities 1206 includes dual one-to-many relationships. Also, the units entities 1202 may be related by the many-to-one relationship 1238 illustrated in Figure 12 with entities within the network entities 1112 which is illustrated in detail in Figure 17. Specifically, the units entities 1202 is related by this many-to-one relationship with the accounts entities 1702 of Figure 17. An optional many-to-one relationship may exist between units entities 1202 and the platforms entities 1210.
Unit Monitor Types Entities 1204
The unit monitor types entities 1204 indicate the type of monitoring associated with the units related to the unit entities 1202. The variable set associated with the unit monitor types entities 1204 is set forth below in Table 2.
Figure imgf000023_0001
TABLE 2: VARIABLE SET OF MONITOR TYPES ENTITIES 1204 As mentioned above, the unit monitor types entities 1204 relates to the units entities 1202 in a many-to-one relationship.
Unit Conflicts Entities 1206
The unit conflicts entities 1206 are used to identify any potential conflicts between units related to the units entities 1202. The variable set associated with the unit conflicts entities 1206 is set forth below in Table 3.
Figure imgf000024_0001
TABLE 3: VARIABLE SET OF UNIT CONFLICTS ENTITIES 1206
As previously mentioned, the unit conflicts entities 1206 relate to the units entities 1202 in dual many-to-one relationships.
Application Role Units Entities 1208 The application role units entities 1208 relate application roles entities 1236 with units entities 1202, much in the same manner that roles are related to units in the relationships described in connection with Figure 10. The variable set associated with the application role units entities 1208 is set forth below in Table 4.
Figure imgf000025_0001
TABLE 4: VARIABLE SET OF APPLICATION ROLE UNITS ENTITIES 1208
The application role units entities 1208 relate to the units entities 1202 in a many-to-one relationship, as discussed above. Additionally, the application role units entities 1208 relate to the application roles entities 1236 in a many -to-one relationship.
Platforms Entities 1210
Platforms entities 1210 indicate the platforms of the various computer devices connected to the network, upon which the units, packages, and roles run. The variable set associated with the platforms entities 1210 is set forth below in Table 5.
Figure imgf000025_0002
TABLE 5: VARIABLE SET OF PLATFORMS ENTITIES 1210 The platforms entities 1210 may have multiple optional one-to-many relationships with other entities illustrated in Figure 12. These entities with which the platforms entities 1210 may be related in an optional one-to-many relationship include the units entities 1202, as previously discussed, the account roles entities 1224, and the application roles entities 1236. Additionally, the platforms entities 1210 relates in a many-to-one fashion with the device pool roles entities 1218 and the packages entities 1220.
Unit Packages Entities 1212
The unit packages entities 1212 serve to relate the units represented by the units entities 1202 with the packages represented by the packages entities 1220, in much the same manner as described in connection with Figure 10. The variable set associated with the unit packages entities 1212 is set forth below in Table 6.
Figure imgf000026_0001
TABLE 6: VARIABLE SET OF UNIT PACKAGES ENTITIES 1212
The unit package entities 1212 have many-to-one relationships with the units entities 1202, as previously discussed, and the packages entities 1220.
Account Role Units Entities 1214
Account role units entities 1214 are used in relating the units represented by the units entities 1202 with the account roles of the account roles entities 1224 in a similar manner as described in Figure 10 using relational tables. The variable set associated with the account role units entities 1214 is set forth below in Table 7.
Figure imgf000027_0001
TABLE 7: VARIABLE SET OF ACCOUNT ROLE UNITS ENTITIES 1214
The account role units entities 1214 have many -to-one relationships with the unit entities 1202, as previously indicated, and the account roles entities 1224.
Device Pool Role Units Entities 1216
The device pool role units entities 1216 serve to relate devices contained in device pools, which are associated with the device pool roles entities 1218, with the various software units associated with the units entities 1202 that are necessary to properly configure the devices. The variable set associated with the device pool role units entities 1216 is set forth below in Table 8.
Figure imgf000028_0001
TABLE 8: VARIABLE SET OF DEVICE POOL ROLE UNITS ENTITTES 1216
The device pool role units 1216 have many-to-one relationships with the units entities 1202, as previously indicated, and the device pool roles entities 1218.
Device Pool Roles Entities 1218
Device pool poles entities 1218 relate the device pool packages, the device roles, and the platforms of the various devices with the device pool role units associated with the device pool role units entities 1216. The variable set associated with the device pool roles entities 1218 is set forth below in Table 9. These variables relate to the device pool role, or the software associated with a particular device pool. Thus, the variable STATUS, indicated below in Table 9, may indicate the status of a device role.
Figure imgf000028_0002
Figure imgf000029_0001
TABLE 9: VARIABLE SET OF DEVICE POOL ROLES ENTITIES 1218
The device pool roles entities 1218 are related to the device pool role units entities 1216 in a one-to-many relationship as previously discussed. Also, the device pool roles entities 1218 are related to the platforms entities 1210 in a many- to-one relationship, as previously discussed. In addition to these relationships, the device pool roles entities 1218 are related to the device roles entities 1226, and the device pool packages entities 1234 in one-to-many relationships.
Packages Entities 1220
The packages entities 1220 represent the various software packages, such as those described in connection with Figure 10. The variable set associated with the packages entities 1220 is set forth below in Table 10.
Figure imgf000029_0002
Figure imgf000030_0001
TABLE 10: VARIABLE SET OF PACKAGES ENTITIES 1220
The packages entities 1220 are related to the platforms entities 1210 in a many -to-one relationship, and the unit packages entities 1212 in a one-to-many relationship, as discussed above. Additionally, the packages entities 1220 is related to the account packages of entities 1222, the included packages entities 1230, the application packages entities 1232, and the device pool packages 1234 in one-to-many relationships. The relationship between the packages entities 1220 and the included packages entities 1230 is a dual one-to-many relationship. Also, the packages entities 1220 are related by way of the many-to-one relationship 1240 to an entity within the network entities 1112 shown in Figure 17. Specifically, the packages entities 1220 relates to the accounts entities 1702 of Figure 17 by way of a many-to-one relationship 1214.
Account Packages Entities 1222
The account packages entities 1222 serves to relate the packages entities 1220 with the account roles entities 1224, in a manner similar to the manner in which packages are related to roles in Figure 10. The variable set associated with the account packages entities 1222 is set forth below in Table 11.
Figure imgf000030_0002
Figure imgf000031_0001
TABLE 11: VARIABLE SET OF ACCOUNT PACKAGES ENTITIES 1222
The account packages entities 1222 relate to the packages entities 1220 as previously described, and the account roles entities 1224 in many -to-one relationships.
Account Roles Entities 1224
The account roles entities 1224 represent the various software roles associated with particular customer accounts. The variable set associated with the account roles entities 1224 is set forth below in Table 12. These variables relate to the account roles, or software packages for each account. For example, the STATUS variable may indicate the status of an account role as active, inactive, deprecated, experimental, and so forth.
Figure imgf000031_0002
Figure imgf000032_0001
TABLE 12: VARIABLE SET OF ACCOUNT ROLES ENTITIES 1224
As previously mentioned, the account roles entities 1224 relates in one-to- many relationships with the account role units entities 1214 and the account packages entities 1222. Also, as previously described, the account roles entities 1224 may optionally relate to the platforms entities 1210 in a many -to-one relationship. The account roles entities 1224 may also optionally relate to the device roles entities 1226 in a one-to-many relationship. The account roles entities 1224 may also relate, by way of a many-to-one relationship 1242, to an entity within the network entities 1112 illustrated in Figure 17. Specifically, the account roles entities 1224 relates to the account entities 1702 illustrated in Figure 17 by way of a many-to-one relationship 1242.
Device Roles Entities 1226 The device roles entities 1226 represent the various software roles associated with each device connected to the network. The variable set associated with the device roles entities 1226 is set forth below in Table 13.
Figure imgf000032_0002
Figure imgf000033_0001
TABLE 13: VARIABLE SET OF DEVICE ROLES ENTITIES 1226
As mentioned before, the device roles entities 1226 relate to the device pool roles entities 1218, and optionally to the account roles entities 1224 in many- to-one relationships. The device roles entities also has optional many-to-one relationships with the application roles entities 1236, the customer tiers entities 1708 of Figure 17 by way of relationship 1246, and the devices entities 1512 of Figure 15 by way of relationship 1248. The device roles entities 1226 also relates in dual one-to-many and a single many -to-one relationship with elements of the configuration entities 1104 illustrated in Figure 13. Specifically, the device roles entities 1226 relate to the device role configuration entities 1320 of Figure 13 and the device role IP host entities 1308 of Figure 13 in one-to-many relationships 1256, 1260, respectively. The device roles entities 1226 also relates to the status entities 1322 of Figure 13 by a many -to-one relationship 1258. Dependent Roles Entities 1228
The dependent roles entities 1228 relate to the application roles represented by the application roles entities 1236. The dependent roles entities 1228 serve to identify various application roles that are dependent upon other roles, and to describe this dependency. The variable set associated with the dependent roles entities 1228 is set forth below in Table 14.
Figure imgf000034_0001
TABLE 14: VARIABLE SET OF DEPENDENT ROLES ENTITIES 1228
The dependent roles entities relate in dual many-to-one relationships with the application roles entities 1236.
Included Packages Entities 1230
The included packages entities 1230 is related to the packages entities 1220 and identifies packages that are included within a particular installation package, and the order in which it is to be installed. The variable set associated with the included packages entities 1230 is set forth below in Table 15.
Figure imgf000034_0002
TABLE 15: VARIABLE SET OF INCLUDED PACKAGES ENTITIES 1230 The included packages 1230 are related to the packages entities 1220 in dual many-to-one relationships, as described above.
Application Packages Entities 1232
The application packages entities 1232 relates the packages represented by the packages entities 1220 and the application roles represented by the application roles entities 1236. The relationship of the roles in packages is similar to the manner in which the roles in packages are related in Figure 10. The variable set associated with the application packages entities 1232 is set forth below in Table 16.
Figure imgf000035_0001
TABLE 16: VARIABLE SET OF APPLICATION PACKAGES ENTITIES 1232
The application packages entities 1232 relate to the packages entities 1220 as previously described, and the application roles entities 1236 in many-to-one relationships.
Device Pool Packages Entities 1234
The device pool packages entities 1234 serve to relate the device pool roles represented by the device pool roles entities 1218 with the packages represented by the packages entities 1220. This occurs in a similar manner as described in connection with Figure 10. The variable set associated with the device pool packages entities 1234 is set forth below in Table 17.
Figure imgf000036_0001
TABLE 17: VARIABLE SET OF DEVICE POOL PACKAGES ENTITIES 1234
The device pool packages entities 1234 relate to the packages entities 1220 on the device pool roles entities 1218 in many-to-one relationships, as described above.
Application Roles Entities 1236
The application roles entities 1236 represent the various application software roles. The variable set associated with the application roles entities 1236 is set forth below in Table 18. These variables relate to the application role. For example, the STATUS variable may give an indicator that an application role is active, inactive, experimental, deprecated, supported, unsupported, and so forth.
Figure imgf000036_0002
Figure imgf000037_0001
TABLE 18: VARIABLE SET OF APPLICATION ROLES ENTITIES 1236
As previously described, the application roles entities 1236 relates in a one- to-many relationship with the application role units entities 1208, the application packages entities 1232, and optionally the device roles entities 1226. Additionally, the application roles entities 1236, as indicated above, relates to the dependent roles entities 1228 in dual one-to-many relationships. The application roles entities 1236 also optionally relates in a many-to-one relationship with the platforms entities 1210. In addition to these relationships previously described, the application roles entities 1236 relates in a one-to-many relationship 1244 with the data center tiers 1724 of Figure 7. The application roles entities 1236 also relates in a one-to-many relationship 1254 with the role configurations entities 1316 of Figure 13. The application roles entities 1236 also relates to the status entities 1322 of Figure 13, and optionally to the services entities 1314 of Figure 13 by way of many -to-one relationships 1252, 1250, respectively.
Multiple entities within the software entities 1102 relate to entities illustrated in various other figures. For example, the relationships 1238, 1240, 1242, 1244, 1246 relate to various entities within the network entities 1112, which is illustrated in Figure 17. These relationships have been labeled in Figure 17 to indicate the direct relationship between entities of the software entities 1102 in Figure 12 and the network entities 1112 in Figure 17. Additionally, an optional relationship 1248 with the hardware entities 1108, which is illustrated in Figure 15, is also indicated. Further, the relationships 1250, 1252, 1254, 1256, 1258 relate to entities within the configuration entities 1104, which is illustrated in Figure 13.
CONFIGURATION 1104 The entities of the configuration entities 1104 are illustrated in Figure 13.
These configuration entities 1104 represent various configuration information relating to software, hardware, the network, and the like. Those entities which are not illustrated as having a direct relationship with any of the other entities are used by business logic, or intelligent agents, for various purposes. Like the software entities from Figure 12, each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new configurations, without requiring the rewriting of software code which uses the model and the database implementation thereof.
Manufacturing Model Entities 1302
The manufacturing model entities 1302 is used to identify a manufacturing model identification number, manufacturing name, model name, and manufacturing model description. For example, if a Sun Spore 5 server is used by the present invention, the manufacturer name would be Sun, and the model name would be Spore 5. The description could be any indication that it is a server. The variable set associated with the manufacturing model entities 1302 is set forth below in Table 19.
Figure imgf000039_0001
TABLE 19: VARIABLE SET OF MANUFACTURING MODEL ENTITIES 1302
The manufacturing model entities 1302 does not directly relate to any of the other entities illustrated in Figure 13. This group of entities 1302 is used by business logic associated with the present invention to determine manufacturer name, model name, and manufacturer description for each of the devices used on the network associated with the present invention.
Component Objects Entities 1304
The component objects entities 1304 provide an indication of what table a particular value is stored in. For example, a location of the table in which values relating to the specific hardware or software object may be obtained by way of the component object entities 1304. The variable set associated with the component objects entities 1304 is set forth below in Table 20.
Figure imgf000040_0001
TABLE 20: VARIABLE SET OF COMPONENT OBJECTS ENTITIES 1304
The component objects entities 1304 does not directly relate to any of the entities illustrated in Figure 13. This group of entities 1304 is used by business logic associated with the present invention to determine which tables should be used to look up values relating to specific objects on the network associated with the present invention. The objects whose values may be found by way of the component objects entities 1304 may be hardware objects or software objects.
Conduits Entities 1306
The conduits entities 1306 relate to the devices of the network associated with the present invention. These conduits entities 1306 relate to conduits by which information may be passed through a firewall. In essence, the conduits through a firewall constitute holes through a firewall by which devices may communicate from outside of the firewall to devices contained within the firewall. Thus, the conduits entities 1306 define the source and destination addresses that involved in communications across the firewall. The present invention also maintains a history, which records all of the traffic across the firewall. The variable set associated with the conduits entities 1306 is set forth below in Table 21.
Figure imgf000041_0001
TABLE 21: VARIABLE SET OF CONDUITS ENTITIES 1306
The conduits entities 1306 relate to the devices entities 1512 of Figure 15 in a many-to-one relationship 1332.
Device Role IP Host Entities 1308
The device role IP host entities 1308 act a place holder for the various devices of the network, and allow IP addresses to be assigned without having a specific device connected to the network. The IP addresses of the devices used on the network associated with the present invention may be of a physical type or a logical type. This means that the IP address may physically relate to the specific device connected to the network, or may be a logical IP address, which does not correspond to the actual physical IP address, but relates the same device. The variable set associated with the device role IP host entities 1308 is set forth below in Table 22.
Figure imgf000041_0002
Figure imgf000042_0001
TABLE 22: VARIABLE SET OF DEVICE ROLE IP HOST ENTITIES 1308
The device role IP host entities 1308 relates to the interface IP type entities 1310 in a many -to-one relationship. Also, as previously discussed, the device role IP host entities 1308 relates to the device roles entities 1226 of Figure 12 in a many-to-one relationship 1260. The device role IP host also relates in a many-to- one relationship 1340 to the IP addresses entities 1730 of Figure 17. The device role IP host entities 1308 may optionally relate to the DNS hosts entities 1604 of Figure 16 in a many-to-one relationship 1336.
Interface IP Type Entities 1310
The interface IP type entities 1310 indicate the type of interface associated with each IP address. The variable set associated with the interface IP type entities 1310 is set forth below in Table 23.
Figure imgf000042_0002
TABLE 23: VARIABLE SET OF INTERFACE IP TYPE ENTITIES 1310 The interface IP type entities 1310 is related to the device role IP host entities 1308 in a one-to-many relationship.
Virtual IPs Entities 1312
The virtual IPs entities 1312 relate to virtual IP addresses, which allow for virtual IP addressing, and allow for multiple machines to have the same IP address, or group of addresses mapped to them by way of a load balancer. A variable called STICKY may be set to require that each time a specific device accesses an IP address it is mapped to the same server by the load balancer. This "sticky" routing allows cookies to be used that were placed on the device by that server. The variable set associated with the virtual IPs entities 1312 is set forth below in Table 24.
Figure imgf000043_0001
TABLE 24: VARIABLE SET OF VIRTUAL IPS ENTITIES 1312
The virtual IPs entities 1312 relates to the VIP groups entities 1424 of Figure 14 in a one-to-many relationship 1328, the devices entities 1512 of Figure 15 in a many-to-one relationship 1330, and to the IP addresses entities 1730 of Figure 17 in a many-to-one relationship 1338.
Services Entities 1314 The services entities 1314 relate application roles to services for the convenience of users and network customers. This allows a customer to view and configure application roles in terms of services offered, which is a useful quality to customers. The variable set associated with the services entities 1314 is set forth below in Table 25.
Figure imgf000044_0001
TABLE 25: VARIABLE SET OF SERVICES ENTITIES 1314
The services entities 1314 may optionally relate to the application roles entities 1236 of Figure 12 in a one-to-many relationship 1250, as discussed above.
Role Configurations Entities 1316
The role configurations entities 1316 relate to the actual configurations of software roles. These role configuration associated with the configurations entities 1316 may include such information as the types of components to be used, such as specific memory types, CPU types, video card types. Also, the quantity of components to be used may be indicated, along with the component size and type. For example, if an Intel processor is used as a CPU, the quantity may be designated as two or three, and so on depending upon the number of the processor occupied by a particular customer. The component size associated with such a CPU would-be expressed in megahertz, indicating the processing scheme. The configuration type would be expressed in a brand name, or perhaps a minimum specification requirement. The variable set associated with the role configurations entities 1316 is set forth below in Table 26.
Figure imgf000045_0001
TABLE 26: VARIABLE SET OF ROLE CONFIGURATIONS ENTITIES 1316
The role configuration entities 1316 relate to the component type entities 1324 in a many-to-one relationship, and, as previously discussed, the application roles entities 1236 of Figure 12 in a many-to-one relationship 1254.
Device Roles History Entities 1 1
The device roles history entities 1318 is a history of all roles executed by a particular device. That is, the history of all software that has ever been employed by a specific device is indicated in the device roles history entities 1318. Thus, many of the entries within the device roles history entries 1318 are similar to those of the device roles entities 1226. The variable set associated with the device roles history entities 1318 is set forth below in Table 27.
Figure imgf000045_0002
Figure imgf000046_0001
TABLE 27: VARIABLE SET OF DEVICE ROLES HISTORY ENTITIES 1318
The device roles history entities 1318 cannot relate directly to any other entities illustrated on Figure 13. The information contained within these entities 1318 is used by business logic associated with the present invention. The type of operation that may be performed by business logic using the device roles history entities 1318 may include, for example, a software rollback when software contained on a particular device has failed.
Device Role Configuration Entities 1320
The device role configuration entities 1320 relate to the configuration of various software roles. These device role configuration entities 1320 are a way in which generic name-value pairs may be defined, which are associated with device roles of the present invention. One instance in which this might be used is if a particular device has four processors, but a particular customer is only paid to use two processors of that server, a name-value pair may be used to indicate these specific device role configurations. Thus, a generic keyname may be generated associated with the two processors that have been paid for by a customer. The values associated with the name-value pair for which the name is expressed in the device role configuration entities 1320 is expressed within the device role configuration values entities 1326. The variable set associated with the device role configuration entities 1320 is set forth below in Table 28.
Figure imgf000047_0001
TABLE 28: VARIABLE SET OF DEVICE ROLE CONFIGURATION ENTITIES 1320
The device role configuration entities 1320 is related to a device role configuration values entities 1326 in a one-to-many relationship, and to the device roles entities 1226 of Figure 12 in a many-to-one relationship 1256.
Status Entities 1322 The status entities 1322 provide status reports regarding various software and hardware configurations. The variable set of the status entities 1322 is set forth below in Table 29.
Figure imgf000047_0002
TABLE 29: VARIABLE SET OF STATUS ENTITIES 1322
The status entities 1322 relate to the application roles entities 1236, and the device roles entities 1226, both of Figure 12, in one-to-many relationships 1252, 1258, respectively. Also, the status entities 1322 relate to the devices entities 1512 of Figure 15 in a one-to-many relationship 1324.
Component Type Entities 1324
The component type entities 1324 is related to the various types of components associated with the devices of the network. The variable set associated with the component type entities 1324 is set forth below in Table 30.
Figure imgf000048_0001
10 TABLE 30: VARIABLE SET OF COMPONENT TYPE ENTITIES 1324
The component type entities 1324 relate to the role configurations entities 1316 in a one-to-many relationship.
Device Role Configuration Values Entities 1326
The device role configuration values entities 1326 relate to values
15. associated with the role configurations, which are represented by the device role configuration entities 1320. The device role configuration values 1326 are the value portion of the main- value pair associated with the device roles, for which the names are expressed within the device role configuration entities 1320, as previously described. The variable set associated with the device role 0 configuration values entities 1326 is set forth below in Table 31.
Figure imgf000048_0002
Figure imgf000049_0001
TABLE 31: VARIABLE SET OF DEVICE ROLE CONFIGURATION VALUES ENTITIES 1326
The device role configuration values entities 1326 relate to the device role configuration entities 1320 in a many-to-one relationship.
As discussed in connection with Figure 12, the various entities within the configuration entities 1104 of Figure 13 are related to entities within the software entities 1102 of Figure 12. The relationships 1250, 1252, 1254, 1256, 1258, 1260 are indicated as continuing on Figure 12. Additionally, relationship 1328 is continued on Figure 14, relationships 1330, 1332, 1334 are continued on Figure 15, optional relationship 1336 may be continued on Figure 16, and relationships 1338, 1340 are continued on Figure 17. Each of these relationships is designated with the same numeral in the figure in which it continues, and illustrates the entity with which it relates directly.
MONITORING 1106
The entities of the monitoring entities 1106 are illustrated in Figure 14 and an entity relationship diagram form. These entities relate to components that maintain the network and various hardware and software components of the networks, as well as configuration information. As with the aforementioned entities, the monitoring entities are described in terms of specific interrelations and are characterized by variable sets which provide enough specificity to accurately characterize the software portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new monitoring functions, without requiring the rewriting of software code which relies upon the model and the database implementation thereof.
Autonomous System Map Entities 1402
The autonomous system map entities are used to create an autonomous system map of the entire system associated with the present invention. The variable set associated with the autonomous system map entities 1402 is set forth below in Table 32.
Figure imgf000050_0001
TABLE 32: VARIABLE SET OF AUTONOMOUS SYSTEM MAP ENTITIES 1402
The autonomous system map entities 1402 of the monitoring entities 1106 illustrated in Figure 14 are not directly related to any other entities of Figure 14. However, the information contained within the autonomous system map entities 1402 is used by business logic and intelligent agents network in ascertaining system map information regarding the network of the present invention.
Device Request Classes Entities 1404 The device request classes entities 1404 are used to relate device classes, and requests associated with those devices. The device classes associated with the device request classes entities may include a particular group of devices, such as load balancers, routers, or servers. The variable set associated with the device request classes entities 1404 is set forth below in Table 33.
Figure imgf000051_0001
TABLE 33: VARIABLE SET OF DEVICE REQUEST CLASSES ENTITIES 1404
The device request classes entities 1404 are related in a many-to-one relationship with the request class entities 1406. The device request classes entities portion of four are related in a many-to-one relationship 1428 with the devices entities 1512 of Figure 15.
Request Class Entities 1406
The request class entities 1406 may be optionally related to request class variables entities 1408. The request class entities 1406 define suitable names for device classes used in connection with the present invention. The variable set associated with the request class entities 1406 is set forth below in Table 34.
Figure imgf000052_0001
TABLE 34: VARIABLE SET OF REQUEST CLASS ENTITIES 1406 The request class entities 1406 may be optionally related to the request class variables entities 1408 in a one-to-many relationship.
Request Class Variables Entities 1408
The request class variables entities 1408 act as a relationship table between the request class entities 1406 and the SNMP variable entities 1420. The request class variables entities identify all variables collected for specific request class, and identify a foreign key to the request class table which relates the request classes to SNMP variables within the SNMP variable entities 1420. The variable set associated with the request class variables entities 1408 is set forth below in Table 35.
Figure imgf000053_0001
TABLE 35: VARIABLE SET OF REQUEST VARIABLES ENTITIES 1408
The request class variables entities 1408 may be optionally related in many- to-one relationships with the request class entities 1406, as discussed above, and to the SNMP variables entities 1420.
Manager Applications Entities 1410
The manager applications entities 1410 is a list of internal applications that defines all applications allowed to communicate with devices and access these devices, such as software applications. The variable set associated with the manager applications entities 1410 is set forth below in Table 36.
Figure imgf000054_0001
TABLE 36: VARIABLE SET OF MANAGER APPLICATIONS ENTITIES 1410
The manager applications entities 1410 are related to the monitor ACLs entities 1412 and the device application configuration entities 1414.
Monitor ACLs Entities 1412
The monitor ACLs entities 1412 allows for monitoring of access control list (ACLs) associated with devices of the present invention. The variable set associated with the monitor ACLs entities 1412 is set forth below in Table 37.
Figure imgf000054_0002
Figure imgf000055_0001
TABLE 37: VARIABLE SET OF MONITOR ACLS ENTITIES 1412
The monitor ACLs entities 1412 are related to the manager applications entities 1410 in a many-to-one relationship, as discussed above. The monitor ACLs entities 1412 are also related to the device ACLs entities 1418 and the ACL entries entities 1422 in one-to-many relationships.
Device Application Configuration Entities 1414
The device application configuration entities 1414 relate devices with manager applications, and provide a mechanism whereby the configuration of device applications may be monitored. The device application configuration entities 1414 are a name-value pair for device applications configured on the network. A date or text value may be entered and associated with the devices, depending upon the specific device type. The variable set associated with the device application configuration entities 1414 is shown below in Table 38.
Figure imgf000055_0002
Figure imgf000056_0001
TABLE 38: VARIABLE SET OF DEVICE APPLICATION CONFIGURATION ENTITTES 1414
The device application configuration entities is related in many-to-one relationships with the manager applications entities 1410, as previously discussed, and with the devices entities 1512 of Figure 15 by way of relationship 1430.
Device Authorization Entities 1416
The device authorization entities 1416 are used for authorizing use of devices by way of user names, passwords, and the like. The device authorization entities 1416 describe specific device authorizations required by the simple network management protocol (SNMP), used in connection with one embodiment of the present invention. The device authorization entities 1416 allow for current and future, or next values, of user names and passwords to be read, written, and trapped (having an alert sent regarding an erroneous user name or password). The variable set associated with the device authorization entities 1416 is set forth below in Table 39.
Figure imgf000057_0001
TABLE 39: VARIABLE SET OF DEVICE AUTHORIZATION ENTITIES 1416
The device authorization entities 1416 relate to the device ACLs entities 1418 in a one-to-many relationship and to the devices entities 1512 of Figure 15 in a many-to-one relationship 1426. Device ACLs Entities 1418
The device ACLs entities 1418 are used to provide the device authorizations entities 1416 with the correct access control lists (ACLs). The variable set associated with the device ACLs entities 1418 is set forth below in Table 40.
Figure imgf000058_0001
TABLE 40: VARIABLE SET OF DEVICE ACLS ENTITIES 1418
The device ACLs entities 1418 are related to the monitor ACLs entities 1412 and the device authorizations entities 1416 in many-to-one relationships, as previously discussed.
SNMP Variables Entities 1420
The SNMP variables entities 1420 provide information regarding variables associated with the simple network management protocol (SNMP) associated with the devices connected to the network of the present invention. Generally, standard SNMP variables are assigned to specific devices or objects and a unique object identification must be determined for internal purposes. The variable set associated with the SNMP variables entities 1420 is set forth below in Table 41.
Figure imgf000059_0001
TABLE 41: VARIABLE SET OF SNMP VARIABLES ENTITIES 1420
The SNMP variables entities 1420 may optionally be related to the request class variables entities 1408 in a one-to-many relationship.
ACL Entries Entities 1422
The ACL entries entities 1422 relate to the entries on the access control lists associated with the various devices connected to the network of the present invention. The variable set associated with the ACL entries entities 1422 is set forth below in Table 42.
Figure imgf000059_0002
Figure imgf000060_0001
TABLE 42: VARIABLE SET OF ACL ENTRIES ENTITIES 1422
ACL entries entities 1422 is related in a many-to-one relationship with the monitor ACLs entities 1412.
VIP Groups Entities 1424
The Virtual IP (VIP) groups entities 1424 relate to devices grouped into VIP groups. The VIP groups entities 1424 are used by load balancers within the system to route single IP addresses to multiple servers by way of VIP mapping. An interface identification number is provided, and an interface port may be specified. The variable set associated with the VIP groups entities 1424 is shown below in Table 43.
Figure imgf000060_0002
TABLE 43: VARIABLE SET OF GROUPS ENTITIES 1424 The VIP groups entities 1424 are related to the virtual IPs entities 1312 of Figure 13 in a many-to-one relationship 1428, and to the interface IPs entities 1524 of Figure 15.
Various relationships 1426, 1428, 1430, 1432 in Figure 14 are indicated as relating entities within the monitoring entities 1106, with entities illustrated on Figure 15, associated with the hardware entities 1108. Additionally, as discussed in connection with Figure 13, the relationship 1328 from Figure 13 relates to the VIP groups elements 1424, as shown in Figure 14.
HARDW ARE 1108
The entities illustrated in Figure 15 are part of the hardware entities 1108, and are illustrated in entity relationship diagram form. Each of these entities is described below. Each of the entities within this diagram interrelate and are characterized by variable sets which provide enough specificity to accurately characterize the hardware portion of the network that the model is intended to capture. At the same time, however, these entities and their respective variables are sufficiently generic to readily permit the addition of, e.g., new hardware devices, without requiring the rewriting of software code which relies upon the model and the database implementation thereof and permitting the reuse of existing software code to interact with the database model regarding the newly added hardware device.
Memory Components Entities 1502
The memory components entities 1502 describe various memory components of the devices related to the device entities 1512. The variable set associated with the memory components entities 1502 is set forth below in Table 44.
Figure imgf000062_0001
TABLE 44: VARIABLE SET OF MEMORY COMPONENTS ENTITIES 1502 The memory components entities 1502 relates to the devices entities 1512 in a many -to-one relationship. Storage Components Entities 1 04
The storage components entities 1504 relate to the storage components of devices associated with the devices entities 1512. The variable set associated with the storage components entities 1504 is set forth below in Table 45.
Figure imgf000063_0001
TABLE 45: VARIABLE SET OF STORAGE COMPONENTS ENTITIES 1504
The storage components entities 1504 relate to the devices entities 1512 in a many -to-one relationship. Bus Components Entities 1506
The bus components entities 1506 are related to the bus components of the devices represented by the devices entities 1512. The variable set associated with the bus components entities 1506 is set forth below in Table 46.
Figure imgf000064_0001
TABLE 46: VARIABLE SET OF BUS COMPONENTS ENTITIES 1506
The bus components entities 1506 relate to the devices entities 1512 in a many-to-one relationship.
Interface Components Entities 1 08
The interface components entities 1508 relate to interface components contained within interface cards of the devices represented by the devices entities 1512. The variable set associated with the interface components entities 1508 is set forth below in Table 47.
Figure imgf000065_0001
TABLE 47: VARIABLE SET OF COMPONENTS ENTITIES 1508
The interface components entities 1508 relate to the interface cards entities 1510 and the interface type entities 1514 in many-to-one relationships. Also, the interface components interface 1508 relate to the sub interfaces entities 1520 in a one-to-many relationship. Interface Cards Entities 1 10
The interface cards entities 1510 relate to the interface cards contained within the devices represented by the devices entities 1512. The variable set associated with the interface cards entities 1510 is set forth below in Table 48.
Figure imgf000066_0001
TABLE 48: VARIABLE SET OF INTERFACE CARDS ENTITIES 1510
The interface cards entities 1510 relate to the devices entities 1512 in a many-to-one relationship.
Devices Entities 1512
The devices entities 1512 relate to the various devices connected to the network associated with the present invention. Multiple variables are for defining devices and communication with the network associated with the present invention. For example, information such as device and manufacturer identifications, serial numbers, device types, status, and other similar descriptions are provided for, along with other convenient variables, such as a flag which indicates whether a device should be monitored or not. The MONITOR _FLG variable may be used in the future to determine the level of monitoring that should be performed for each device identified within the device's entities 1512. The variable set associated with the devices entities 1512 is set forth below in Table 49.
Figure imgf000068_0001
TABLE 49: VARIABLE SET OF DEVICES ENTITIES 1512
The device's entities 1512 relates to the memory components entities 1502, the storage components entities 1504, the bus components entities 1506, the interface cards entities 1510, the device console entities 1516, and the CPU components entities 1518 in one-to-many relationships. The devices entities 1512 also relate to the device authorizations entities 1416 in a one-to-many relationship 1426, the device request classes entities 1404 in a one-to-many relationship 1428, and the device application configuration entities 1414 in a one-to-many relationship 1430, all of which entities are illustrated in Figure 14. Additionally, the devices entities 1512 relate to the virtual IPS entities 1312 in a one-to-many relationship 1330, the conduits entities 1306 in a one-to-many relationship 1332, the status entities 1322 in a many-to-one relationship 1324, all of which are illustrated in Figure 13. Also, the devices entities may optionally be related in a one-to-many relationship 1248 to the device roles 1226 of Figure 12.
Interface Type Entities 1514 The interface type entities 1514 relate to the type of interface achieved through the interface components represented by the interface components entities 1508. The variable set associated with the interface type entities 1514 is set forth below in Table 50.
Figure imgf000069_0001
TABLE 50: VARIABLE SET OF INTERFACE TYPE ENTITIES 1514
The interface type entities 1514 relate to the interface components entities 1508 in a one-to-many relationship. Device Console Entities 1516
The device console entities 1516 relate to consoles that may be attached to devices represented by the device entities 1512. The consoles may be for the convenience of a user in accessing information contained within the devices, or by accessing the network by way of the devices. The variable set associated with the device console entities 1516 is set forth below in Table 51.
Figure imgf000070_0001
TABLE 51: VARIABLE SET OF DEVICE CONSOLE ENTITIES 1516
The device console entities 1516 relate to the device entities 1512 in a many-to-one relationship, as previously mentioned.
CPU Components Entities 1518
The CPU components entities 1518 relate to the various components of the CPUs of the devices which are represented by the device entities 1512. The CPU components entities 1518 have a series of variables associated therewith indicate information regarding the type of CPU, the speed, the family, the model, the slot, and other such information, which may be necessary in provisioning servers, to ensure that software is installed can be adequately handled by the CPU on a particular device. The variable set associated with the CPU components entities 1518 is set forth below in Table 52.
Figure imgf000071_0001
TABLE 52: VARIABLE SET OF CPU COMPONENTS ENTITIES 1518
The CPU components entities 1518 relate to the devices entities 1512 in a many-to-one relationship, as previously mentioned. SUB Interfaces Entities 1520
The SUB interfaces 1520 relate the interface components of the interface components entities 1508 with the interface IP addresses of the interface IPs entities 1524. These SUB interfaces entities 1520 may be used with asynchronous transfer mode (ATM) frame relay systems, for example. The variable set associated with the SUB interfaces entities 1520 is set forth below in Table 53.
Figure imgf000072_0001
TABLE 53: VARIABLE SET OF SUB INTERFACES ENTITIES 1520
The SUB interfaces entities 1320 is related to the interface components entities 1508 in a many -to-one relationship, and to the interface IPs 1524 in a one- to-many relationship. The SUB interfaces entities 1520 may also be optionally related to the circuits entities 1522 in a many -to-one relationship. Circuits Entities 1522
The circuits entities 1522 may be use to optionally relate to the SUB interfaces entities 1520. These entities 1522 allow for specific identification of the circuits associated with the SUB interfaces and the interface components, and the type and description of the circuits. The variable set associated with the circuits entities 1522 is set forth below in Table 54.
Figure imgf000073_0001
TABLE 54: VARIABLE SET OF CIRCUITS ENTITIES 1522
The circuits entities 1522 may optionally relate to the SUB interfaces entities 1520 in a one-to-many relationship.
Interface IPs Entities 1524
The interface IPs entities 1524 may be used to relate the SUB interfaces represented by the SUB interfaces entities 1520 with VIP groups of the VIP groups entities 1424 shown in Figure 14. The variable set associated with the interface IPs entities 1524 is set forth below in Table 55.
Figure imgf000074_0001
TABLE 55: VARIABLE SET OF INTERFACE DPS ENTITIES 1524
The interface IPs entities 1524 relates to the SUB interfaces entities 1520 in a many-to-one relationship and to the VIP groups entities 1424 of Figure 14 in a one-to-many relationship 1432.
As indicated previously in connection with Figures 12-14, various relationships 1248, 1330, 1332, 1334, 1426, 1428, 1430, 1432 are directly related to entities within the hardware 1108 illustrated in Figure 15 from these other figures representing the software 1102, the configuration 1104, and the monitoring 1106. DNS 1110
The entities illustrated in Figure 16 are part of the DNS entities 1110. The DNS entities 1110 relate to the assignment of DNS domain names. These entities are related in an entity relationship diagram fashion.
DNS Configuration Entities 1602
The DNS configuration entities 1602 allow for the translation of DNS names to DNS values, and may be used by the business logic associated with the network of the present invention. These DNS names and values may be translated into addresses related to various network hosts. The variable set associated with the DNS configuration entities 1602 is set forth below in Table 56.
Figure imgf000075_0001
TABLE 56: VARIABLE SET OF DNS CONFIGURATION ENTITIES 1602
The DNS configuration entities 1602 are illustrated in Figure 16 as having no direct relationship with any of the other entities illustrated therein. The values contained within the DNS configuration entities 1602 are used by business logic associated with the present invention, which is able to query the DNS configuration entity 1602 to relate between the entries of the name-value pairer associated with these entities 1602. DNS Hosts Entities 1604
The DNS host entities 1604 relate to DNS hosts associated with the present invention. The DNS host entities 1604 provide for a unique manner in which multiple DNS hosts may be identified. Using multiple DNS hosts provided customer with a more efficient DNS service. For example, if a primary DNS host is not able to handle a request within a predefined time, the expire time set on a second DNS may lapse, causing the secondary DNS to handle the pending request. This is also known as a time to live (TTL). The variable set associated with the DNS hosts entities 1604 are indicated below in Table 57.
Figure imgf000076_0001
TABLE 57 VARIABLE SET OF DNS HOSTS ENTITIES 1604
The DNS hosts entities 1604 are related to the DNS domains entities 1616, and the DNS host types entities 1606 in many-to-one relationships. The DNS host types entities 1606 in many-to-one relationships, the DNS hosts entities 1604 may optionally be related to the device role IP host entities 1308 illustrated in Figure 3 in a one-to-many relationship 1336. DNS Host Types Entities 1 06
The DNS host types entities 1606 indicate the types of DNS hosts associated with the DNS hosts entities 1604. The variable set associated with the DNS hosts types entities 1606 is set forth below in Table 58.
Figure imgf000077_0001
TABLE 58: VARIABLE SET OF DNS HOST TYPES ENTITIES 1606
The DNS host types entities 1606 are related to the DNS hosts entities 1604 in a one-to-many relationship.
DNS ACLs Entities 1608
The DNS ACLs entities 1608 relate to the access control lists associated with various DNS. The variable set associated with the DNS ACLs entities 1608 is set forth below in Table 59.
Figure imgf000077_0002
TABLE 59: VARIABLE SET OF DNS ACLS ENTITTES 1608
The DNS ACLs entities 1608 are related to the DNS ACL entries entities
1610, the DNS allow transfers entities 1612, and the DNS allow queries entities 1618 in one-to-many relationships. DNS ACL Entries Entities 1610
The DNS ACL entries entities 1610 relate to the ACL entries for the DNS. The variable set associated with the DNS ACL entries entities 1610 is set forth below in Table 60.
Figure imgf000078_0001
TABLE 60: VARIABLE SET OF DNS ACL ENTRIES ENTITIES 1610
The DNS ACL entries entities are related to the DNS ACLs entities 1608 in a many -to-one relationship, as previously mentioned. DNS Allow Transfers Entities 1612
The DNS allow transfers entities 1612 is used to determine whether or not DNS transfers may take place between given DNs domains according to the ACLs of the DNS ACLs entities 1608. The variable set associated with the DNS allow transfers entities 1612 is set forth below in Table 61.
Figure imgf000078_0002
TABLE 61: VARIABLE SET OF DNS ALLOW TRANSFERS ENTITIES 1612 The DNS allow transfers entities 1612 are related to the DNS ACLs entities 1608 and the DNS domains entities 1616 in many-to-one relationships. DNS Domain Types Entities 1614
The DNS domain types entities 1614 relate to the types of DNS domains associated with the DNS domain entities 1616. The variable set associated with the DNS domain types entities 1614 is set forth below in Table 62.
Figure imgf000079_0001
TABLE 62: VARIABLE SET OF DNS DOMAIN TYPES ENTITIES 1614
The DNS domain types entities 1614 relate to the DNS domain entities 1614 in a one-to-many relationship.
DNS Domain Entities 1616
The DNS domain entities 1616 relate to the various DNS domains associated with devices connected to the network of the present invention. The variables associated with the DNS domain entities 1616 relate to domains maintained by a host, in accordance with an embodiment of the present invention. A DNS term "SOA" or start of authority, is used to define several variables. For example, a serial variable is given, which indicates the revision number of the DNS file used to look up domain names. A refresh rate is set, which may be adjusted according to the speed with which the DNS file is updated on a primary DNS, to control how often a secondary DNS updates its DNS file. Also, an expire time, which indicates the time that a secondary DNS will wait until taking over a domain name request may be set. A minimum cash time for a particular entry, and a name server are provided for variables of the DNS domain entity 1616. Also, an admnistrative contact e-mail address is provided for each domain. A retry variable may also be provided whereby after a certain amount of time, or a certain amount of attempts, a DNS must assume the role of the primary DNS. A rebuilt date is given, whereby the system, or agents of the system, know that if this date is changed, then the server needs to rebuild. One of the advantages of the present invention is that DNS entries are not created in the DNS server, but rather are contained within a separate database with specific forms that define acceptable DNS entries. The variable set associated with the DNS domain entities 1616 is set forth below in Table 63.
Figure imgf000080_0001
Figure imgf000081_0001
TABLE 63: VARIABLE SET OF DNS DOMAINS ENTITIES 1616
A DNS domain entities 1616 are related in many-to-one relationships with the DNS domain types entities 1614, as previously discussed, and the DNS domain masters entities 1620. Additionally, the DNS domains entities 1616 relate to the DNS hosts entities 1604, the DNS allow transfers entities 1612, and the DNS queries entities 1618 in one-to-many relationships. Also, the DNS domains entities 1616 may optionally relate to the accounts entities 1702 of the network entities 1112, illustrated in Figure 17, in a many-to-one relationship 1624. DNS Allow Queries Entities 1618
The DNS allow queries entities 1618 assist in determining whether or not queries may be allowed between certain DNS domains, according to the DNs ACLs of the DNS ACLs entities 1608. The variable set associated with the DNS allow queries entities 1618 is set forth below in Table 64.
Figure imgf000082_0001
TABLE 64: VARIABLE SET OF DNS ALLOW QUERIES ENTITIES 1618
The DNS allow queries entities 1618 related to the DNS ACLs entities 1608 and the DNS domains entities 1616 in many-to-one relationships. DNS Domain Masters Entities 1620 The DNS domain masters entities 1620 relates the DNS domain of the DNS domain entities 1616 with the DNS master IPs of the DNS master IPs entities 1622. The variable set associated with the DNS domain masters entities 1620 is set forth below in Table 65.
Figure imgf000082_0002
TABLE 65: VARIABLE SET OF DNS DOMAIN MASTERS ENTITIES 1620 The DNS domain masters entities 1620 are related to the DNS domains entities 1616 in a one-to-many relationship, and to the DNS master IPs entities 1622 in a many-to-one relationship.
DNS Master IPs Entities 1622
The DNS master IPs entities 1622 relate to the DNS master IP addresses of the devices on the network associated with the present invention. The variable set associated with the DNS master IPs entities 1622 is set forth below in Table 66.
Figure imgf000083_0001
TABLE 66: VARIABLE SET OF DNS MASTER IPS ENTITIES 1622
The DNS master IPs entities 1622 relate to the DNS domain masters entities 1620 in a one-to-many relationship.
The relationship 1336 is between the DNS host entities 1604 and an entity illustrated in Figure 13, within the configuration entities 1104. Additionally, the relationship 1624 relates the DNS domain entities 1616 with an entity in Figure 17 of the network entities 1112. The entities illustrated in an entity relationship diagram in Figure 17 form part of the network entities 1112. The Network entities 1112 define various aspects of the network with which the present invention may be used. Each of these entities is described below.
Accounts Entities 1702
The accounts entities 1702 relate directly to customer network accounts. The variable set associated with the accounts entities 1702 is set forth below in Table 67.
Figure imgf000084_0001
TABLE 67: VARIABLE SET OF ACCOUNTS ENTITIES 1702
The accounts entities 1702 relate to the account configuration entities 1704 and the customer tiers entities 1708 in one-to-many relationships. Additionally, as previously indicated, the accounts entities 1702 relate to the units entities 1202, the packages entities 1240, and the account roles entities 1224 of Figure 12, in one-to- many relationships. Also, the accounts entities 1702 may optionally be related in a one-to-many relationship 1624 with the DNS hosts entities 1604 of Figure 16. Account Configuration Entities 1704
The account configuration entities 1704 relate to the configuration of the accounts associated with the account entities 1702. The variable set associated with the account configuration entities 1704 is set forth below in Table 68.
Figure imgf000085_0001
TABLE 68: VARIABLE SET OF ACCOUNT CONFIGURATION ENTITIES 1704
The account configuration entities 1704 relate to the accounts entities 1702 in a many -to-one relationship.
Account Configuration Values Entities 1706
The account configuration values entities 1706 indicate various values associated with the configuration of various accounts related to the account configuration entities 1704. The variable set associated with the account configuration values entities 1706 is set forth below in Table 69.
Figure imgf000086_0001
TABLE 69: VARIABLE SET OF ACCOUNT CONFIGURATION VALUES ENTITIES
1706
The account configuration values entities 1706 relate to the account configuration entities 1704 in many-to-one relationships.
Customer Tiers Entities 1708
The customer tiers entities 1708 relate to various customer tiers, whereby customers may receive, and have access to, specific services associated with specific tiers. For example, a specific customer may desire to distribute his webhosting servers to multiple data centers. Therefore, the variables associated with the Customer tiers entities 1708 may indicate a data center or identification number, which informs one as to the location of the customer tier represented by the customer tier entity 1708. Also, a flag may be set to indicate whether or not monitoring is desired or needed within that particular network. The variable set associated with the customer tiers entities 1708 is illustrated below in Table 70.
Figure imgf000087_0001
TABLE 70: VARIABLE SET OF CUSTOMER TIERS ENTITIES 1708
The customer tiers entities 1708 relate to the accounts entities 1702, as previously discussed, and the data centers entities 1716, in many-to-one relationships. The customer tiers entities 1708 also relate to the VLAM compartments entities 1714 in a one-to-many relationship. Data Center Configuration Values Entities 1710
The data center configuration values entities 1710 relate to the configuration values associated with the data center configuration, which are associated with the data center configuration entities 1712. The variables associated with the data center configuration values entities 1710 are the value portion of a name-value pair relating to the data center. Thus, a configuration value, associated with such a name-value pair is given by the data center configuration values entities 1710. The variable set associated with the data center configuration values entities 1710 is set forth below in Table 71.
Figure imgf000088_0001
TABLE 71: VARIABLE SET OF DATA CENTER CONFIGURATION VALUES
ENTITIES 1710
The data center configuration values entities 1710 relate to the data center configuration entities 1712 in a many-to-one relationship.
Data Center Configuration Entities 1712
The data center configuration entities 1712 relate to the configuration of specific data centers that house specific servers, and other network equipment associated with services of the various customer tiers. The data center configuration entities 1712 form the name portion of the name-value pair associated with the data center configuration values entities 1710. Thus, a key name, which serves as the name in the name-value pair. The variable set associated with the data center configuration entities 1712 is set forth below in Table 72.
Figure imgf000089_0001
TABLE 72: VARIABLE SET OF DATA CENTER CONFIGURATION ENTITIES 1712
The data center configuration entities 1712 relate to the data centers entities
1716 in a many-to-one relationship.
VLAN Compartments Entities 1714
The VLAN compartments entities 1714 are used to relate the customer tiers of the customer tiers entities 1708 with various VLAN IP pools of the VLAN IP pools entities 1722. The variable set associated with the VLAN compartments entities 1714 is set forth below in Table 73.
Figure imgf000090_0001
TABLE 73: VARIABLE SET OF VLAN COMPARTMENTS ENTITIES 1714
The VLAN compartments entities relate to the customer tiers entities 708 in a many -to-one relationship as previously discussed, also, the VLAN compartments entities 1714 relate to the VLAN IP pools 1722 in a one-to-many relationship.
Data Centers Entities 1716
The data centers entities 1716 relate to various data centers in which server equipment, and other network devices are housed. The data centers entities 1716 contain variables that describe various aspects of the data centers to which these entities 1716 relate. For example, a DNS sequence is given, which is a sequential number, that is used in an algorithm to provide a next random DNS name. Generally, the DNS names used by each of the data center entitties 1716 contain the name of the data center therein, with which they most closely relate, and therefore there is no conflict of DNS names between data centers. Additionally, a mask may be given that indicates how a particular server may be located by way of parsing the location of its rack. The variable set associated with the data centers entities 1716 is set forth below in Table 74.
Figure imgf000091_0001
TABLE 74: VARIABLE SET OF DATA CENTERS ENTITIES 1716
The data center entities 1716 relate to the customer tiers entities 1708 and the data center configuration entities 1712 in one-to-many relationships. Site Configuration Entities 1718
The site configuration entities 1718 relate to a configuration of various data center sites. The site configuration entities 1718 is a name- value pairer that may be used for any convenient purpose, such as accounting, data center, maintenance, device configuration, and the like. This relationship table may be used by way of business logic associated with the present invention, or with agents residing on particular devices connected to the network. The variable set associated with the site configuration entities 1718 is set forth below in Table 75.
Figure imgf000092_0001
TABLE 75: VARIABLE SET OF SITE CONFIGURATION ENTITIES 1718
The site configuration entities 1718 illustrated in Figure 17 is not directly related to the entities illustrated in the same figure. However, the values contained therein may relate to other entities illustrated in Figure 17, and may be used by business logic associated with the present invention, or by intelligent agents of the system.
Device Pool VLAN Platforms Entities 1720
The device pool VLAN platforms entities 1720 relate to platforms of the device pool within the VLAN. That is, the device pool VLAN platforms entities 1720 is used to relate a base OS to the VLAN with which a particular device is associated. The variable set associated with the device pool VLAN platforms entities 1720 is set forth below in Table 76.
Figure imgf000093_0001
TABLE 76: VARIABLE SET OF DEVICE POOL VLAN PLATFORMS ENTITTES 1720
The device pool VLAN platforms entities 1720 relate to the VLAN IP pools entities in a many -to-one relationship.
VLAN IP pools Entities 1722
The VLAN IP pools entities 1722 relate to IP pools of the VLAN, which are associated with the VLAN compartments of the customer tiers that are associated with the customer tiers entities 1708. The variable set associated with the VLAN IP pools entities 1722 is set forth below in Table 77.
Figure imgf000094_0001
TABLE 77: VARIABLE SET OF VLAN IP POOLS ENTITIES 1722 The VLAN IP pools entities 1722 relate to the VLAN compartments 1714 in a many to one relationship, and to the device pool VLAN platforms 1720 in a one to many relationship, as previously described. Also, the VLAN IP pools entities 1722 relate to the IP addresses entities 1730 in a one to many relationship, and the VLAN subtype entities 1728 in a many to one relationship. Data Center Tiers Entities 1724
The data center tiers entities 1724 relate to a specific group of services, or tiers, associated with the data centers, which are represented by the data centers entities 1716. The variable set associated with the data center tiers entities 1724 is set forth below in Table 78.
Figure imgf000095_0001
TABLE 78: VARIABLE SET OF DATA CENTER TTERS ENTITIES 1724
The data center tiers entities 1724 relate to the data centers entities 1716 in a many to one relationship, as previously explained. The data center tiers entities 1724 also relate to the application rules entities 1236, illustrated in Figure 12, in a many to one relationship 1244.
VLAN Pool Type Entities 1726
The VLAN pool type entities 1726 define the various valid types of VLANs for use on the network associated with the present invention. The variable set associated with the VLAN pool type entities is set forth below in Table 79.
Figure imgf000096_0001
TABLE 79: VARIABLE SET OF VLAN POOL TYPE ENTITTES 1726
The VLAN pool type entities 1726 are not illustrated as directly relating to any entities within Figure 17. However, the variables stored within the VLAN pool type entities 1726 are used by the logic associated with the present invention for determining the valid types of VLANs that may be used with the present invention.
VLAN SUB Type Entities 1728
The VLAN SUB type entities 1728 are used to relate to the VLAN IP pools, which are represented by the VLAN IP pools entities 1722. The VLAN SUB type entities 1728 define valid VLAN types, or types in which VLANs may be used. Some examples might include development, quality assurance, production, and the like. The VLAN subtype entities 1728 relate to the VLAN IP pools 1722 in a one to many relationship, as previously described. The variable set of the VLAN SUB type entities 1728 is shown below in Table 80.
Figure imgf000097_0001
TABLE 80: VARIABLE SET OF VLAN SUB TYPE ENTITIES 1728
IP Address Entities 1730
The IP address entities 1730 relate to the IP addresses of the network associated with the present invention. The variable set associated with the IP address entities 1730 is shown below in Table 81.
Figure imgf000097_0002
TABLE 81: VARIABLE SET OF IP ADDRESSES ENTITIES 1730
The IP address entities 1730 relate to the VLAN IP pools 1722 in a many to one relationship, as previously discussed. Also, the IP addresses entities 1730 relate to the virtual IPs entities 1312, and the device role IP host entities 1308 by one to many relationships, 1338, 1340, respectively
VLAN CIDR Reserve Entities 1732
The VLAN CIDR reserve entities 1732 is related to the classless inter- domain routing (CIDR) of the VLAN associated with the present invention. The VLAN CIDR reserve entities indicates the CIDR number used for the network, and the number of addresses that are reserved and that are available for dynamic assignment as DHCP generated addresses. The variable set associated with the VLAN CIDR entities 1732 is set forth below in Table 82.
Figure imgf000098_0001
TABLE 82: VARIABLE SET OF VLAN CD3R RESERVE ENTITIES 1732 The VLAN CIDR reserve entities 1732 is illustrated in Figure 17 as not directly relating to any of the other entities. These entities 1732 are used by the business logic of the present invention to determine the number of network addresses that may be reserved, and the number that may be generated as DHCP generated addresses for a given network or subnetwork. QIJEUES 1114
The entities illustrated in the entity relationship diagram of Figure 18 form the queues entities 1114. These entities are described in detail below. These entities are not directly related to the entities of the rest of the data model 1100 shown in Figure 11 but rather are used by agents of specific devices connected to the network in performing various tasks. These tasks are represented in queues, which may be executed in a specific, given order.
Agent Queues Entities 1802
The agent queues entities 1802 queues entities are essentially a list of tasks to be performed by an intelligent agent operating on a device connected to the network, which is associated with the present invention. The variable set of agent queues entities 1802 is shown below in Table 83.
Figure imgf000099_0001
TABLE 83: VARIABLE SET OF AGENT QUEUES ENTITIES 1802 The agent queues entities 1802 is illustrated as having a one to many relationship with the agent queue commands entities 1804. The agent queues entities 1802 may also have an optional one to many relationship with other agent queues, as illustrated by the broken line in Figure 18.
Agent Queue Commands Entities 1804
The agent queue commands entities 1804 serves to relate the agent queues entities 1802 with specific agent commands and agent command outputs. The variable set of agent queue commands entities 1804 is shown below in Table 84.
Figure imgf000100_0001
TABLE 84: VARIABLE SET OF AGENT QUEUE COMMANDS ENTITIES 1804
The agent queue commands entities 1804 are related to the agent queues entities 1802, as previously discussed, and the agent commands 1808 in many to one relationships. Also, the agent queue commands entities 1804 are related to the agent command output entities 1806 in a one to many relationship. Agent Command Output Entities 1806
The agent command output entities 1806 relate to the output of specific commands to agents of the present invention. The variable set of agent command output entities 1806 is shown below in Table 85.
Figure imgf000101_0001
TABLE 85: VARIABLE SET OF AGENT COMMAND OUTPUT ENTITIES 1806
The agent command output entities 1806 relate to the agent queue commands entities 1804 in a many to one relationship.
Agent Commands Entities 1808
The agent commands entities 1808 represent specific commands to be executed by agents associated with the present invention. The variable set of agent commands entities 1808 is shown below in Table 86.
Figure imgf000102_0001
TABLE 86: VARIABLE SET OF AGENT COMMANDS ENTITIES 1808
The agent commands entities 1808 relate to the agent queue commands entities 1804, as previously indicated, and the agent command text entities 1810, in one to many relationships.
Agent Command Text Entities 1810
The agent command text entities 1810 represents specific text associated with the agent commands, which are represented by the agent command entities 1808. Additionally, an order of the text may be given, thereby allowing the agent to determine the order of the text to be executed. The variable set of agent command text entities 1810 is shown below in Table 87.
Figure imgf000103_0001
TABLE 87: VARIABLE SET OF AGENT COMMAND TEXT ENTITIES 1810
The agent command text entities 1810 relate to the agent commands entities 1808 in a many to one relationship.
Agent Queue Mutex Entities 1812
The agent queue mutex entities 1812 serves as a locking device, which signals to an agent at a particular device is currently busy, and prevents the agent from executing a second queue on that device until the device is not busy. The variable set of agent queue mutex entities 1812 is shown below in Table 88.
Figure imgf000104_0001
TABLE 88: VARIABLE SET OF AGENT QUEUE MUTEX ENTITIES 1812
The agent queue mutex entities 1812 do not relate directly to any of the entities illustrated in Figure 18, but rather are either queried by the agents with which they are associated, or broadcast information to those agents.
Agent Command Mutex Entities 1814
The agent command mutex entities 1814 serve as a locking device whereby only a single agent queue may be executed by the agent at any given time. This prevents an agent from attempting to accomplish more than one task at a single time. The variable set of agent command mutex entities 1814 is shown below in Table 89.
Figure imgf000105_0001
TABLE 89: VARIABLE SET OF AGENT COMMAND MUTEX ENTITIES 1814 The agent command mutex entities 1814 do not relate directly to any of the entities illustrated in Figure 18, but rather are either queried by the agents with which they are associated, or broadcast information to those agents.
The foregoing description has been provided in the context of one data model used in connection with one provisioning network that may be used to control devices at one data center. It will be appreciated that such a network can be part of a larger network which controls devices at several data centers. The data model entities would merely need to be expanded to include networks located offsite. Hence, if an entity has its website infrastructure apportioned over several data centers, the provisioning operations can be coordinated amongst the various centers by using the data model of the present invention.
From the foregoing, therefore, it can be seen that the present invention provides a data model for use in system for the automated provisioning of devices which constitute the infrastructure of a website, such as servers. Two significant advantages provided by the data model are flexibility and the repeatability of the results that are obtained. The flexibility permits the varied needs of different websites to be readily accommodated, and thereby avoids the limitation of having to configure the architecture of every site the same way. The repeatability ensures that every server will have the proper set of software components once it has been provisioned, and thereby be ready to operate immediately. In addition to these features, the automated provisioning that is provided through this system achieves a significant time savings, enabling the entire process to be accomplished in substantially less than one hour for each device.
It will be appreciated by those of ordinary skill in the art that the present invention can be embodied in other forms without departing from the spirit or essential characteristics thereof. For instance, while an exemplary embodiment of the invention has been described in the context provisioning website servers in a data center, it will be appreciated that the principles underlying the invention can be applied in any environment where computing devices need to be configured and/or updated on a relatively large scale. The foregoing description is therefore considered to be illustrative, and not restrictive. The scope of the invention is indicated by the following claims, and all changes that come within the meaning and range of equivalents are therefore intended to be embraced therein.

Claims

WHAT IS CLAIMED IS:
1. A data model for characterizing the interaction of all elements of a computer network comprising: a plurality of software entities for representing software, which is contained within said data model; a plurality of configuration entities for modeling configuration information of the network, which is contained within said data model; a plurality of monitoring entities for modeling monitoring information of the network, which is contained within said data model; a plurality of hardware entities for modeling hardware device information of the hardware devices connected to the network, which is contained within said data model; a plurality of domain name server (DNS) entities for modeling DNS information of the network, which is contained within said data model; and a plurality of network entities for modeling network information of the network, which is contained within said data model.
2. The data model of claim 1, further comprising: a plurality of queues entities that may be used by agents in accessing information from said data model regarding any of the information contained therein.
3. The data model of claim 1, wherein: at least one of said plurality of software entities is related to: at least one of said plurality of configuration entities in at least one many-to-one relationship and at least one one-to-many relationship, and at least one of said plurality of network entities in at least one many -to-one relationship and at least one one-to-many relationship; and at least one of said plurality of configuration entities is related to: at least one of said plurality of monitoring entities in at least one one-to-many relationship, at least one of said plurality of network entities in at least one many -to-one relationship, and at least one of said plurality of hardware entities in at least one many-to-one relationship and at least one one-to-many relationship; and at least one of said plurality of monitoring entities is related to at least one of said plurality of hardware entities in at least one many -to-one relationship.
4. The data model of claim 3, wherein at least one of said plurality of software entities is optionally related to at least one of said plurality of hardware entities in a many-to-one relationship.
5. The data model of claim 3, wherein at least one of said plurality of configuration entities is optionally related to at least one of said plurality of DNS entities in a many-to-one relationship.
6. The data model of claim 3, wherein at least one of said plurality of
DNS entities is optionally related to at least one of said plurality of network entities in a many-to-one relationship.
7. The data model of claim 1, wherein said plurality of software entities comprises: a plurality of units entities; a plurality of unit monitor types entities; a plurality of unit conflicts entities; a plurality of application role units entities; a plurality of platforms entities; a plurality of unit packages entities; a plurality of account role units entities; a plurality of device pool role units entities; a plurality of device pool roles entities; a plurality of packages entities; a plurality of account packages entities; a plurality of account roles entities; a plurality of device roles entities; a plurality of dependent roles entities; a plurality of included packages entities; a plurality of application packages entities; a plurality of device pool packages entities; and a plurality of application roles entities.
8. The data model of Claim 7, wherein said units entities represent software units that form part of a software package, and wherein said units entities are related to: said unit monitor types entities by a one-to-many relationship; said unit conflicts entities by at least one-to-many relationship; said application role units entities by a one-to-many relationship; said unit packages entities by a one-to-many relationship; said account role units entities by a one-to-many relationship; said device pool role units entities by a one-to-many relationship; and said plurality of network entities by a many -to-one relationship.
9. The data model of Claim 7, wherein said unit monitor types entities represent the type of monitoring associated with individual units, and wherein said unit monitor types entities relate to said units entities by a many-to-one relationship.
10. The data model of Claim 7, wherein said unit conflicts entities identify conflicts between units represented by said units entities, and wherein said unit conflicts entities are related to said units entities by at least one many-to-one relationships.
11. The data model of Claim 7, wherein said application role units relate said units entities to said software application roles entities by way of a many-to-one relationship with said units entities and a many-to-one relationship with said application roles entities.
12. The data model of Claim 7, wherein said platforms entities represent the computer platform upon which software units, represented by said units entities, are to run, and wherein said platforms entities are related to: said units entities by an optional one-to-many relationship; said application roles entities by an optional one-to-many relationship; said account roles entities by an optional one-to-many relationship; said device pool roles entities by a one-to-many relationship; and said packages entities by a one-to-many relationship.
13. The data model of Claim 7, wherein said unit packages entities relate said units entities to said packages entities by way of a many-to-one relationship with said units entities and a many-to-one relationship with said packages entities.
14. The data model of Claim 7, wherein said account role units entities relate said units entities to said account roles entities by way of a many-to-one relationship with said units entities and a many-to-one relationship with said account roles entities.
15. The data model of Claim 7, wherein said device pool role units entities relate said units entities to said device pool roles entities by way of a many-to-one relationship with said units entities and a many-to-one relationship with said device pool roles entities.
16. The data model of Claim 7, wherein said device pool roles entities represent software roles of a device pool, and wherein said device pool roles are related to: said platforms entities by a many-to-one relationship; said device pool role units entities by a one-to-many relationship; said device roles entities by a one-to-many relationship; and said device pool packages entities by a one-to-many relationship.
17. The data model of Claim 7, wherein said packages entities represent software packages, and wherein said packages entities are related to: said unit packages entities by a one-to-many relationship; said platforms entities by a many -to-one relationship; said plurality of network entities by a many-to-one relationship; said included packages entities by at least one one-to-many relationship; said application packages entities by a one-to-many relationship; said device pool packages entities by a one-to-many relationship; and said account packages entities by a one-to-many relationship.
18. The data model of Claim 7, wherein said account packages entities relates said packages entities to said account roles entities by way of a many-to-one relationship with said packages entities and a many-to-one relationship with said account roles entities.
19. The data model of Claim 7, wherein said account roles represent software roles relating to specific customer accounts, wherein said account roles entities relate to: said account role units entities by a one-to-many relationship; said account packages entities by a one-to-many relationship; said plurality of network entities by a many-to-one relationship; and said device roles entities by an optional one-to-many relationship.
20. The data model of Claim 7, wherein said device roles entities represent software roles relating to specific devices, wherein said device roles entities relate to: said device pool roles by a many -to-one relationship; and said plurality of configuration entities by at least one one-to-many relationship.
21. The data model of Claim 7, wherein said dependent roles entities represent software roles dependent upon application software roles, wherein said dependent roles entities relate to said application roles entities by at least one many-to-one relationship.
22. The data model of Claim 7, wherein said included packages entities represent software packages that are included in a specific software installation, and wherein said included packages entities are related to said packages entities by at least one many -to-one relationship.
23. The data model of Claim 7, wherein said application packages relate said packages entities to said application roles entities by way of a many-to-one relationship with said package entities and a many-to-one relationship with said application roles entities.
24. The data model of Claim 7, wherein said device pool packages entities relate said packages entities to said device pool roles entities by way of a many-to-one relationship with said package entities and a many-to-one relationship with said device pool roles entities.
25. The data model of Claim 7, wherein said application roles entities represent software application roles, and said application roles entities relate to: said dependent roles entities by at least one one-to-many relationship; said application role units entities by a one-to-many relationship; said plurality of configuration entities by a one-to-many relationship; said plurality of network entities by a one-to-many relationship; and said plurality of configuration entities by at least one many-to-one relationship.
26. The data model of Claim 1, wherein said plurality of configuration entities further comprises: a plurality of conduits entities; a plurality of device role IP host entities; a plurality of interface IP type entities; a plurality of virtual IPs entities; a plurality of services entities; a plurality of role configurations entities; a plurality of device role configuration entities; a plurality of status entities; a plurality of component type entities; and a plurality of device role configuration values entities.
27. The data model of Claim 26, wherein said plurality of configuration entities further comprises a plurality of manufacturing model entities.
28. The data model of Claim 26, wherein said plurality of configuration entities further comprises a plurality of configuration entities further comprises a plurality of component objects entities.
29. The data model of Claim 26, further comprising a plurality of device roles history entities.
30. The data model of Claim 26, wherein said conduits entities represent communications portholes across a firewall via which two devices may communicate across the firewall, wherein said conduits entities relate to said plurality of hardware entities by a many -to-one relationship.
31. The data model of Claim 26, wherein said device role IP host entities relates an IP host address to a device role, and relates to: said interface IP type entities by a many -to-one relationship; said plurality of network entities by a many-to-one relationship; and said plurality of software entities by a many-to-one relationship.
32. The data model of Claim 26, wherein said interface IP type entities represent allowed types of IP addresses within the network, and wherein said interface IP type entities relate to said device role IP host entities in a one-to-many relationship.
33. The data model of Claim 26, wherein said virtual IPs entities represent virtual IP addresses that are used by a router to route traffic for a single IP address to multiple computers, and wherein said virtual IPs entities relates to: said plurality of monitoring entities by a one-to-many relationship; said plurality of hardware entities by a many -to-one relationship; and said plurality of network entities by a many-to-one relationship.
34. The data model of Claim 26, wherein said services entities represent services to be performed by a series of applications accessible by a network server, and wherein said services entities relate to said software entities by an optional one-to-many relationship.
35. The data model of Claim 26, wherein said role configurations entities represent configurations related to software roles, and wherein said role configurations relate to: said plurality of software entities by a many-to-one relationship; and said component type entities by a many -to-one relationship.
36. The data model of Claim 26, wherein said device role configuration entities represent configurations of software roles for specific devices, and wherein said device role configuration entities relate to: said device role configuration values entities by a one-to-many relationship; and said plurality of software entities by a many-to-one relationship.
37. The data model of Claim 26, wherein said status entities represent status conditions of various hardware and software objects, and wherein said status entities relate to: said plurality of software entities by at least one one-to-many relationship; and said plurality of hardware entities by a one-to-many relationship.
38. The data model of Claim 26, wherein said component type entities represent types of components used with the data model, and wherein said component type entities relate to said role configurations entities with a one-to-many relationship.
39. The data model of Claim 26, wherein said device role configuration values entities represent configuration values associated with software roles of a specific device, wherein said device role configuration values entities relate to device role configuration entities by a many -to-one relationship.
40. The data model of Claim 1, wherein said plurality of monitoring components further comprises: a plurality of device request classes entities; a plurality of request class entities; a plurality of request class variables entities; a plurality of manager applications entities; a plurality of monitor ACLs entities; a plurality of device application configuration entities; a plurality of device authorizations entities; a plurality of device ACLs entities; a plurality of SNMP variables entities; a plurality of ACL entries entities; and a plurality of VIP groups entities.
41. The data model of Claim 40, further comprising a plurality of autonomous system map entities.
42. The data model of Claim 40 wherein said device request classes entities relate said request class entities to hardware devices by way of a many-to-one relationship with said request class entities and a many-to-one relationship with said plurality of hardware entities.
43. The data model of Claim 40 wherein said request class entities represent specific classes of requests that may be made, and wherein said request class entities relate to: said device request classes entities by a one-to-many relationship; and said request class variables entities by an optional one-to-many relationship.
44. The data model of Claim 40 wherein said request class variables may be used to relate request classes associated with said request class entities with simple network management protocol (SNMP) variables associated with said SNMP variables entities by way of an optional many-to-one relationship with said request class entities, and optional many-to-one relationship with said SNMP variables entities.
45. The data model of Claim 40 wherein said manager applications entities relate the monitor access control lists (ACLs) represented by the monitor ACLs entities with the device application configurations represented by the device application configuration entities by way of a one-to-many relationship with the monitor ACLs entities and a one-to-many relationship with the device application configuration entities.
46. The data model of Claim 40 wherein said monitor ACLs entities represent the monitoring of the ACLs for various devices on the network, wherein said monitor ACLs entities relate to: said manager applications entities by a many-to-one relationship; said device ACLs entities by a one-to-many relationship; and . said ACL entries entities by a one-to-many relationship.
47. The data model of Claim 40 wherein said device application configuration entities represent the configuration of applications contained on a device, and wherein said device application configuration entities relate to: said manager applications entities by a many-to-one relationship; and said plurality of hardware entities by a many-to-one relationship.
48 The data model of Claim 40 wherein said device authorizations entities represent the authorization levels of particular devices, and wherein said device authorizations entities relate to: said device ACLs entities by a one-to-many relationship; and said plurality of hardware entities by a many-to-one relationship.
49. The data model of Claim 40 wherein said device ACLs entities represent device access control lists (ACLs) for specific devices on a network, wherein said device ACLs entities relate to: said monitor ACLs entities by a many-to-one relationship; and said device authorizations entities by a many-to-one relationship.
50. The data model of Claim 40 wherein said SNMP variables entities represent specific variables associated with the simple network management protocol (SNMP) used by devices on the network, wherein said SNMP variable entities relate to said request class variables entities by an optional one-to-many relationship.
51. The data model of Claim 40 wherein said ACL entries entities represent entries within an ACL, wherein said ACL entries entities relate to said monitor ACLs by a many -to-one relationship.
52. The data model of Claim 40 wherein said virtual IP (VIP) groups entities represent particular groups sharing virtual IP addresses, wherein said VIP groups entities relate to: said plurality of configuration entities by a many-to-one relationship; and said plurality of hardware entities by a many-to-one relationship.
53. The data model of Claim 1, wherein said plurality of hardware entities further comprises: a plurality of memory components entities; a plurality of storage components entities; a plurality of bus components entities; a plurality of interface components entities; a plurality of interface cards entities; a plurality of devices entities; a plurality of interface type entities; a plurality of device console entities; a plurality of CPU components entities; a plurality of SUB interfaces entities; a plurality of circuits entities; and a plurality of interface IPs entities.
54. The data model of Claim 53, wherein said memory components entities represent memory components, and wherein said memory components entities relate to said devices entities by a many -to-one relationship.
55. The data model of Claim 53, wherein said storage components entities represent storage components, and wherein said memory components entities relate to said devices entities by a many-to-one relationship.
56. The data model of Claim 53, wherein said bus components entities represent storage components, and wherein said bus components entities relate to said devices entities by a many-to-one relationship.
57. The data model of Claim 53, wherein said interface components entities represent interface components, and wherein said interface components entities relate to: said interface cards entities by a many -to-one relationship; said interface type entities by a many-to-one relationship; and said SUB interfaces entities by a one-to-many relationship.
58. The data model of Claim 53, wherein said interface cards entities represent interface cards for hardware devices, and wherein said interface cards entities relate to said devices entities by a many-to-one relationship.
59. The data model of Claim 53, wherein said devices entities represent hardware devices connected to the network, and wherein said devices entities relate to: said memory components entities by a one-to-many relationship; said storage components entities by a one-to-many relationship; said bus components entities by a one-to-many relationship; said interface cards entities by a one-to-many relationship; said device console entities by a one-to-many relationship; said CPU components entities by a one-to-many relationship; said plurality of monitoring components by at least one one-to-many relationship; and said plurality of configuration components by at least one one-to-many relationship and a many-to-one relationship.
60. The data model of Claim 53, wherein said interface type entities represent valid types of interfaces, and wherein said interface type entities relate to said interface components by a one-to-many relationship.
61. The data model of Claim 53, wherein said device console entities represent a device console, whereby a user may access devices represented by said devices entities, and wherein said device console entities relate to said devices entities by a many-to-one relationship.
62. The data model of Claim 53, wherein said CPU components entities represent hardware CPU components, and wherein said CPU components entities relate to said devices entities by a many -to-one relationship.
63. The data model of Claim 53, wherein said SUB interfaces entities represent virtual local area network (VLAN) interfaces between interface components represented by said interface components entities and interface IPs represented by said interface IPs, and wherein said SUB interfaces entities relate to: said interface components entities by a many-to-one relationship; and said interface IPs entities by a one-to-many relationship.
64. The data model of Claim 53, wherein said circuits entities represent specific hardware circuits, and wherein said circuits entities relates to said SUB interfaces entities by an optional one-to-many relationship.
65. The data model of Claim 53, wherein said interface IPs entities represents actual interface IP addresses associated with hardware devices, and wherein said interface IPs entities relate to: said plurality of monitoring components by a one-to-many relationship; and said SUB interfaces entities by a many-to-one relationship.
66. The data model of Claim 1, wherein said DNS entities further comprises: a plurality of DNS hosts entities; a plurality of DNS host types entities; a plurality of DNS ACLs DNS ACLs entities; a plurality of DNS ACL entries entities; a plurality of DNS allow transfers entities; a plurality of DNS domain types entities; a plurality of DNS domains entities; a plurality of DNS allow queries; a plurality of DNS domain masters entities; and a plurality of DNS master IPs.
67. The data model of Claim 66, further comprising a plurality of DNS configuration entities .
68. The data model of Claim 66, wherein said DNS hosts entities represent DNS host devices, and wherein said DNS hosts entities relate to: said DNS host types entities by a many -to-one relationship; said DNS domains entities by a many -to-one relationship; and said plurality of configuration entities by an optional one-to-many relationship.
69. The data model of Claim 66, wherein said DNS host types entities represent allowed DNS host types, and wherein said DNS host types entities relate to said DNS hosts entities in a one-to-many relationship.
70. The data model of Claim 66, wherein said DNS ACLs entities represent ACLs associated with specific DNS names, and wherein said DNS ACLs entities relate to: said DNS ACL entries entities by a one-to-many relationship; said DNS allow transfers entities by a one-to-many relationship; and said DNS allow queries entities by a one-to-many relationship.
71. The data model of Claim 66, wherein said DNS ACL entries entities relate to said DNS ACLs entities by a many -to-one relationship.
72. The data model of Claim 66, wherein said DNS allow transfers entities relate to: said DNS ACLs entities by a many-to-one relationship; and said DNS domains entities by a many-to-one relationship.
73. The data model of Claim 66, wherein said DNS domain types entities - represent the allowed types of DNS names for the network, and wherein said DNS domain types entities relate to said DNS domains entities by a one-to-many relationship.
74. The data model of Claim 66, wherein said DNS domains entities represent the various DNS domains of the network, and wherein said DNS domains entities relate to: said DNS hosts entities by a one-to-many relationship; said DNS allow transfers entities by a one-to-many relationship; said DNS allow queries entities by a one-to-many relationship; said DNS domain types entities by a many-to-one relationship; said DNS domain masters entities by a many-to-one relationship; and said plurality of network entities by an optional many-to-one relationship; .
75. The data model of Claim 66, wherein said DNS allow queries entities represent specific DNS queries allowed on the network, and wherein said DNS allow queries entities relate to: said DNS domains entities by a many-to-one relationship; and said DNS ACLs entities by a many -to-one relationship.
76. The data model of Claim 66, wherein said DNS domain masters entities relate DNS domains represented by said DNS domains entities and DNS master IPs represented by DNS master IPs entities by way of a one-to-many relationship with said DNS domains entities and a many-to-one relationship with said DNS master IPs entities.
77. The data model of Claim 66, wherein said DNS master IPs entities relate to DNS master IP addresses of the network, and relate to said DNS domain masters entities by a one-to-many relationship.
78. The data model of Claim 1, wherein said plurality of network entities further comprises: a plurality of accounts entities; a plurality of account configuration entities; a plurality of account configuration values entities; a plurality of customer tiers entities; a plurality of data center configuration values entities; a plurality of data center configuration entities; a plurality of VLAN compartments entities; a plurality of data centers entities; a plurality of device pool VLAN platforms entities; a plurality of VLAN IP pools entities; a plurality of data centered tiers entities; a plurality of VLAN pool type entities; a plurality of VLAN sub type entities; a plurality of IP addresses entities; and a plurality of VLAN CIDR reserved entities.
79. The data model of Claim 78, further comprising a plurality of Site configuration entities.
80. The data model of Claim 78 wherein said accounts entities represent customer account on a network, and wherein said accounts entities relate to: said plurality of software entities by at least one one-to-many relationship; said account configuration entities by a one-to-many relationship; said customer tiers entities by a one-to-many relationship; and said plurality of DNS entities by an optional one-to-many relationship;.
81. The data model of Claim 78 wherein said account configuration entities represent configuration information of a customer account, wherein said account configuration entities relate to: said accounts entities by a many-to-one relationship; and said account configuration values entities by a one-to-many relationship.
82. The data model of Claim 78 wherein said account configuration values represent configuration values associated with configurations of customer accounts, and wherein said account configuration values relate to: said account configuration entities by a many-to-one relationship.
83. The data model of Claim 78 wherein said customer tiers entities represent tiers of services accessible to customers on a network, and wherein said customer tiers entities relate to: said accounts entities by a many -to-one relationship; said VLAN compartments entities by a one-to-many relationship; said data centers entities by a many-to-one relationship; and said plurality of software entities by an optional one-to-many relationship;.
84. The data model of Claim 78 wherein said data centered configuration values entities relate to said data center configuration entities by a many-to-one relationship.
85. The data model of Claim 78 wherein the data center configuration entities relate to said data center configuration values entities by a one-to-many relationship, and to said data centers entities by a many-to-one relationship.
86. The data model of Claim 78 wherein said VLAN compartments entities relate to said customer tiers entities by a many -to-one relationship, and to said VLAN IP pools by a one-to-many relationship.
87. The data model of Claim 78 wherein said data centers entities relate to said customer tiers entities by a one-to-many relationship and to said data center configuration entities by a one-to-many relationship.
88. The data model of Claim 78 wherein said device pool VLAN platforms entities relate to said VLAN IP pools entities by a many-to-one relationship.
89. The data model of Claim 78 wherein said VLAN IP pools entities relate to said VLAN compartments entities and said VLAN SUB Type entities by many-to-one relationships, and to said device pool VLAN platforms entities and IP addresses entities by one-to-many relationships.
90. The data model of Claim 78 wherein said data centered tiers entities relate to said data centers entities and to said plurality of software entities by many-to-one relationships.
91. The data model of Claim 78 wherein said VLAN pool type entities represent information regarding the allowed types of VLAN pools.
92. The data model of Claim 78 wherein said VLAN sub type entities relate to said VLAN IP Pools by a one-to-many relationship.
93. The data model of Claim 78 wherein said IP addresses entities relate to said VLAN IP pools by a many-to-one relationship, and to said plurality of configuration entities by at least one one-to-many relationship.
94. The data model of Claim 78 wherein said VLAN CIDR reserve entities indicate the CIDR VLAN addresses that are reserved for network operation and the addresses that are available for assignment.
95. The data model of Claim 1, wherein said queues entities further comprises: a plurality of agent queues entities; a plurality of agent queue commands entities; a plurality of agent command output entities; a plurality of agent commands entities; and a plurality of agent command text entities.
96. The data model of Claim 95, further comprising a plurality of agent queue Mutex entities.
97. The data model of Claim 95, further comprising a plurality of agent command Mutex entities.
98. The data model of Claim 25 wherein said agent queues entities is used to indicate to agents a list of tasks to be performed and may optionally relate to multiple agent queues entities and may relate to said agent queue commands entities by a one-to-many relationship.
99. The data model of Claim 25 wherein said agent queue commands entities relate to said agent queues entities and said agent commands in many-to- one relationships and to said agent command output entities in a one-to-many relationship.
100. The data model of Claim 25 wherein said agent command text entities relate to said agent commands entities by a many-to-one relationship.
101. A software data model for relating software objects of a computer network to other software objects, and for expressing the software objects of a computer network in a form accessible by other network components, comprising: application roles entities that represent application software roles to be implemented on network devices; account roles entities that represent software relating to accounts of various customers on a network; device roles entities that represent software relating to particular devices on a network; and device pool roles entities that represent software relating to specific device pools to be deployed on a network.
102. The software data model of claim 101, wherein each of said roles entities comprises multiple packages entities.
103. The software data model of claim 102, wherein said multiple packages entities comprise: application packages entities related to application software; account packages entities related to customer accounts; and device pool packages entities related to device pools containing devices to be deployed on a network.
104. The software data model of claim 103, wherein each of said packages comprises multiple software units entities.
105. The software data model of claim 104, wherein said multiple software units entities comprise: unit packages entities; application packages entities; and device pool packages entities.
106. A software data model for relating software objects of a computer network to other software objects, and for expressing the software objects of a computer network in a form accessible by other network components, comprising: roles entities; packages entities; and units entities; wherein said roles entities comprise at least one of said packages entities; and wherein said packages entities comprise at least one of said units entities.
107. The software data model of claim 106, wherein said roles entities, said packages entities, and said units entities are all related by way of at least one relationship table.
PCT/US2001/042869 2000-10-31 2001-10-31 A data model for automated server configuration WO2002039313A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002214683A AU2002214683A1 (en) 2000-10-31 2001-10-31 A data model for automated server configuration

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US69935300A 2000-10-31 2000-10-31
US69934100A 2000-10-31 2000-10-31
US09/699,353 2000-10-31
US09/699,341 2000-10-31

Publications (3)

Publication Number Publication Date
WO2002039313A2 true WO2002039313A2 (en) 2002-05-16
WO2002039313A9 WO2002039313A9 (en) 2003-02-13
WO2002039313A3 WO2002039313A3 (en) 2003-06-26

Family

ID=27106394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/042869 WO2002039313A2 (en) 2000-10-31 2001-10-31 A data model for automated server configuration

Country Status (2)

Country Link
AU (1) AU2002214683A1 (en)
WO (1) WO2002039313A2 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104239334A (en) * 2013-06-19 2014-12-24 腾讯科技(北京)有限公司 Interactive page configuration method and system, server and client
US9100283B2 (en) 2002-06-12 2015-08-04 Bladelogic, Inc. Method and system for simplifying distributed server management

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991008542A1 (en) * 1989-11-30 1991-06-13 Seer Technologies, Inc. Software distribution system
US5872928A (en) * 1995-02-24 1999-02-16 Cabletron Systems, Inc. Method and apparatus for defining and enforcing policies for configuration management in communications networks
US6052720A (en) * 1998-05-14 2000-04-18 Sun Microsystems, Inc. Generic schema for storing configuration information on a server computer

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1991008542A1 (en) * 1989-11-30 1991-06-13 Seer Technologies, Inc. Software distribution system
US5872928A (en) * 1995-02-24 1999-02-16 Cabletron Systems, Inc. Method and apparatus for defining and enforcing policies for configuration management in communications networks
US6052720A (en) * 1998-05-14 2000-04-18 Sun Microsystems, Inc. Generic schema for storing configuration information on a server computer

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9100283B2 (en) 2002-06-12 2015-08-04 Bladelogic, Inc. Method and system for simplifying distributed server management
US9794110B2 (en) 2002-06-12 2017-10-17 Bladlogic, Inc. Method and system for simplifying distributed server management
US10659286B2 (en) 2002-06-12 2020-05-19 Bladelogic, Inc. Method and system for simplifying distributed server management
CN104239334A (en) * 2013-06-19 2014-12-24 腾讯科技(北京)有限公司 Interactive page configuration method and system, server and client

Also Published As

Publication number Publication date
WO2002039313A9 (en) 2003-02-13
AU2002214683A1 (en) 2002-05-21
WO2002039313A3 (en) 2003-06-26

Similar Documents

Publication Publication Date Title
US7451071B2 (en) Data model for automated server configuration
JP4533474B2 (en) Method for converting data within a computer network
US6058426A (en) System and method for automatically managing computing resources in a distributed computing environment
US6785713B1 (en) Method and apparatus for communicating among a network of servers utilizing a transport mechanism
US6922724B1 (en) Method and apparatus for managing server load
US6785726B1 (en) Method and apparatus for delivering local and remote server events in a similar fashion
US6789112B1 (en) Method and apparatus for administering a server having a subsystem in communication with an event channel
US8019835B2 (en) Automated provisioning of computing networks using a network database data model
US7856496B2 (en) Information gathering tool for systems administration
EP1636711B1 (en) System and method for distribution of software licenses in a networked computing environment
US7444395B2 (en) Method and apparatus for event handling in an enterprise
US20080256248A1 (en) Single server access in a multiple tcp/ip instance environment
US20040054793A1 (en) System and method for high performance shared web hosting
JP2004227127A (en) Program having multiple pieces of environmental information, and information processor having the program
US11223519B2 (en) Storage system for network information
JP2009193545A (en) Computer system for managing multiple configuration items, its method and computer program
US6058425A (en) Single server access in a multiple TCP/IP instance environment
EP1228425A2 (en) Method and apparatus for synchronizing function values in a multiple protocol system
WO2002039313A2 (en) A data model for automated server configuration
CN107491361B (en) The method for being classified other redundant storage is carried out to column in tables of data
EP1297412B1 (en) A system and method for directing runtime data in a server network
AU2001257513B2 (en) A system and method for directing runtime data in a server network
JPH10143478A (en) Distributed computer system
WO2001095129A1 (en) Centralized multi-domain server for network management
AU2001257513A1 (en) A system and method for directing runtime data in a server network

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PH PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
COP Corrected version of pamphlet

Free format text: PAGES 1/16-16/16, DRAWINGS, REPLACED BY NEW PAGES 1/16-16/16; DUE TO LATE TRANSMITTAL BY THE RECEIVING OFFICE

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP