Autonomous configuration system for service infrastructure
Through the independent discovery and conversion services of the autonomous configuration system, the data center service infrastructure is automatically configured, which solves the problems of low configuration efficiency and insufficient security in the existing technology, and realizes automated and secure service infrastructure configuration.
Patent Information
- Application Number
- CN202210369578.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2016-10-28
- Filing Date
- 2017-10-23
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2037-10-23
AI Technical Summary
The existing technology has problems such as human intervention dependence, inefficiency, and error-prone to errors when configuring service infrastructure in data centers, especially the lack of administrator infrastructure and security brought about by sharing confidential configuration information in edge data centers. risk.
Adopt an independent configuration system to automatically discover and convert configuration data through autonomous discovery services or autonomous conversion services, and evade direct configuration of routing protocols by using sniffing or converting IP addresses to realize automated configuration and secure incremental supply of service infrastructure.
Simplifies the configuration process of service infrastructure, improves efficiency, reduces the risk of human error, and ensures configuration security of edge data centers through automation and secure incremental provisioning.
Smart Images

Figure CN114745263B_ABST
Abstract
Description
[0001] This application is a divisional application of an invention patent application with an international application date of October 23, 2017, which entered the Chinese national stage on April 26, 2019, with Chinese national application number 201780066925.8 and invention name “Autonomous Configuration System for Service Infrastructure”. Technical Field
[0002] Embodiments of the present disclosure relate to an autonomous configuration system for a service infrastructure. Background Art
[0003] Large-scale networking systems are common platforms used in various scenarios for running applications and maintaining data for business and operational functions. For example, a data center (e.g., a physical cloud computing platform) can provide various services (e.g., web applications, email services, search engine services, etc.) to multiple customers at the same time. These large-scale networking systems generally include a large amount of resources throughout the data center or across multiple data centers in a region or multiple regions across the globe. Resources can be similar to a physical machine or a virtual machine (VM) running on a physical node or host. Data centers run on hardware (e.g., power supply, rack, and network interface controller (NIC)) and software components (applications, application programming interfaces (APIs), SQL databases) that depend on each other to operate. In this regard, data centers provide housings for computing systems and related components (collectively referred to as infrastructure or service infrastructure). Service infrastructure can support computing and storage operations for various computing workloads and operations. Service infrastructure can be installed in a data center fully owned and operated by a service provider or entity, or in a data center not fully owned or operated by a service provider. The latter data center can be referred to as an edge data center or edge infrastructure by a service provider. In either case, the service infrastructure must be properly provisioned and configured in order to operate to support the different services. Therefore, the processes used to support the provisioning of the service infrastructure are an integral part of deploying the service infrastructure to the data center. Summary of the invention
[0004] Embodiments described herein provide methods and systems for implementing an autonomous configuration system for configuring a service infrastructure. The service infrastructure includes computing systems and related components—hardware and software—that support computing and storage operations from a data center where the service infrastructure is deployed. At a higher level, the autonomous configuration system implements a service infrastructure configuration manager to identify discovered configuration data or utilize casting configuration data for the service infrastructure. The discovered configuration data or casting configuration data supports circumventing routing protocols for service infrastructure communications via edge infrastructure. The service infrastructure is alternatively configured to access remote configuration data at a service provider infrastructure based on the discovered configuration data or casting configuration data to configure the service infrastructure.
[0005] The discovered configuration data is discovered based on an autonomous discovery service (e.g., a sniffing service) that utilizes a waiting state of the edge infrastructure and a pre-configured state of the service infrastructure to identify the discovered configuration data. The conversion configuration data is utilized based on an autonomous conversion service (e.g., a conversion service) that utilizes a conversion IP address to peer the service infrastructure with the edge infrastructure to make the service infrastructure Internet accessible. Based on the discovered configuration data or the conversion configuration data, an initial configuration state is configured in the service infrastructure. The service infrastructure can then communicate with a service provider infrastructure associated with the service infrastructure to access remote configuration data. The service infrastructure configuration manager accesses the remote configuration data from the service provider infrastructure and uses the remote configuration data to configure the final configuration state in the service infrastructure.
[0006] The present invention summary is provided to introduce some concepts in a simplified form, which will be further described in the following "Detailed Description". This "Invention Summary" is not intended to identify the key features or essential features of the claimed technical solution, nor is it intended to be used alone to help determine the scope of the claimed technical solution. BRIEF DESCRIPTION OF THE DRAWINGS
[0007] The present invention is described in detail below with reference to the accompanying drawings, in which:
[0008] Figure 1 is a block diagram of an exemplary distributed computing infrastructure and autonomic configuration system according to embodiments described herein.
[0009] Figure 2 is a block diagram of an exemplary distributed computing infrastructure and autonomic configuration system according to embodiments described herein;
[0010] Figure 3 is a flow chart illustrating an exemplary method for providing an autonomous configuration system according to embodiments described herein;
[0011] Figure 4 is a flow chart illustrating an exemplary method for providing an autonomous configuration system based on a sniffing service according to embodiments described herein;
[0012] Figure 5 is a flow chart illustrating an exemplary method for providing an autonomous configuration system based on a conversion service according to embodiments described herein;
[0013] Figure 6 is a block diagram of an exemplary computing environment suitable for implementing the embodiments described herein; and
[0014] Figure 7 is a block diagram of an exemplary computing environment suitable for implementing the embodiments described herein. DETAILED DESCRIPTION
[0015] A data center may provide a housing for computing systems and related components, collectively referred to as infrastructure or service infrastructure. A service infrastructure may support computing and storage operations for a variety of computing workloads and operations. A service infrastructure may be installed in a data center that is fully owned and operated by a service provider or entity, or in a data center that is not fully owned or operated by a service provider. The service provider may refer to the latter data center as an edge data center or edge infrastructure. In either case, the service infrastructure must be correctly provisioned and configured in order to operate to support different services. For example, the service infrastructure must be configured with a location-specific network configuration to operate properly.
[0016] The service infrastructure to be deployed to the data center usually does not have the network configuration of the data center where the service infrastructure is to be installed. For example, the top-of-rack switch (TOR) lacks the network configuration of the data center for connecting to the edge infrastructure to access data center resources or external resources. Access to the data center network supports the accessibility of the service infrastructure to data center resources and external resources. Through network access, the service infrastructure can communicate with the service provider infrastructure to receive configuration data. In this way, the service infrastructure must be configured to connect to the data center network and be able to access data center resources and external resources.
[0017] Conventional methods for configuring service infrastructure in data centers have several disadvantages due to the resource-intensive process involved in configuring service infrastructure in data centers. For example, TOR switches require manual configuration of service infrastructure with significant human intervention, which can be time-consuming, inefficient, and susceptible to human error. In one exemplary implementation, an alternative channel to the TOR switch can be configured by an operator to access and configure the TOR switch to communicate with the service provider infrastructure. The alternative channel can be configured using an additional network card, a server with a configured OS (e.g., a blade server), and an operator who accesses the server to configure the TOR. In addition, data centers that are not fully owned by cloud service providers lack a pre-existing administrator infrastructure that can facilitate the configuration of the service infrastructure.
[0018] Another exemplary implementation may include allowing edge infrastructure providers to use edge infrastructure to access configuration information of service providers; however, the configuration information is confidential, and sharing such confidential information may expose the service provider to unnecessary risk. There are other variations and combined disadvantages of traditional methods for configuring service infrastructure. As such, the process for supporting service infrastructure provisioning is an integral part of deploying service infrastructure to a data center.
[0019] The embodiments described herein provide a simple and effective method and system for implementing an autonomous configuration system for a service infrastructure. The service infrastructure includes a computing system and related components - hardware and software - that support computing and storage operations from a data center where the service infrastructure is deployed. As an initial matter, the service infrastructure is transported to an edge data center. For the purpose of providing a detailed description, the service infrastructure is a service infrastructure that is kept in a rack. The rack includes a standard frame for installing equipment, including blades (i.e., modular server computers), power supplies, and network components. The rack may specifically include a switch (e.g., a rack top switch or a TOR switch). The service infrastructure rack is installed at an edge data center based on a service provider specification (e.g., connecting power and network cables). The edge data center includes an edge infrastructure, which includes a network device (e.g., an edge infrastructure switch) that supports connecting the service infrastructure to the edge infrastructure. The service infrastructure is associated with a service provider that manages the service infrastructure, and the edge infrastructure is associated with an edge infrastructure provider that manages the edge infrastructure.
[0020] At a high level, the autonomous configuration system supports a mechanism for a service provider to configure a service infrastructure in a data center. In particular, a service provider can automatically and autonomously configure its service infrastructure in an edge data center or edge infrastructure that is not owned and / or controlled by the service provider. The autonomous configuration system can operate based on a service infrastructure (e.g., a service infrastructure configuration manager) of the autonomous configuration system automatically discovering at least a portion of the service infrastructure configuration data (e.g., the discovered configuration data) or automatically utilizing conversion configuration data (e.g., conversion IP address) and configuring the service infrastructure (e.g., initial configuration state) based on the discovered configuration data or conversion configuration data. The discovered configuration data can be identified based on an edge infrastructure (e.g., an edge infrastructure configuration manager or a switch) configured for a routing protocol. The conversion configuration data can be utilized based on a conversion IP address from a service infrastructure provider (e.g., an anycast IP address utilized by a conversion service or switch). In either case, the edge infrastructure maintains routing protocol configuration data for configuring the service infrastructure. The edge infrastructure configuration manager that maintains the routing protocol configuration data can include an edge infrastructure (e.g., a switch) configured based on the routing protocol configuration data. The edge infrastructure may also store a portion of the service infrastructure portion of routing protocol configuration data, wherein the routing protocol configuration data allows switches of the service infrastructure to communicate with switches of the edge infrastructure based on a routing protocol.
[0021] As background, the edge infrastructure can operate based on a predefined routing protocol (e.g., a border gateway protocol) associated with the routing protocol configuration data. At the edge data center, the service infrastructure that is ultimately fully configured also operates with the edge infrastructure based on the routing protocol. A routing protocol refers to an external gateway protocol for routing information between systems (e.g., autonomous networks or service providers) on the Internet. The routing protocol makes routing decisions on paths, network policies, or rule sets defined for reachability between systems. Thus, as an example, in the ultimately fully configured service infrastructure, a BGP link exists between a switch of the service infrastructure and a switch of the edge infrastructure. In this regard, the routing protocol configuration data can refer to edge infrastructure configuration data and service infrastructure configuration data that support BGP and a link between the edge infrastructure and the service infrastructure that uses BGP. The edge infrastructure configuration data can be used to configure the edge infrastructure switch. The edge infrastructure can be preconfigured (e.g., a wait state and performing wait state operations) to communicate with the service infrastructure using a routing protocol; however, using the embodiments described herein, the edge infrastructure and the routing protocol are utilized or circumvented (e.g., via an autonomous discovery service or an autonomous conversion service) to instead identify the discovered configuration data or utilize conversion configuration data, respectively.
[0022] The discovered configuration data from the autonomous discovery service (e.g., a sniffing service) or the converted configuration data from the autonomous conversion service allows the service infrastructure to be partially provisioned (e.g., an initial configuration state). The service infrastructure can then communicate with the service provider infrastructure (e.g., a service provider cluster) to access the provisioning data (e.g., remote configuration data). The service provider infrastructure can transmit the provisioning data to the service infrastructure at the edge data center. The remote configuration data allows the service infrastructure to be fully provisioned (e.g., a final configuration state). The autonomous configuration system configures the service infrastructure based on an autonomous configuration framework that includes an initial configuration state and a final configuration state and, in an embodiment, includes an intermediate configuration state for security purposes. The intermediate configuration state includes provisioning the service infrastructure using an incremental provisioning process based at least in part on a security check, which must be met as part of the incremental provisioning process, as described in more detail herein.
[0023] In operation, the autonomic configuration system may support two different types of implementations: an autonomic discovery service and an autonomic transformation service corresponding to the sniffing-based process and the transformation-based process, respectively. The service infrastructure configuration manager may support either or both of the autonomic configuration implementations based on the sniffing service and the transformation service, respectively.
[0024] Referring to the sniffing-based process, the sniffing-based process supports configuration of the service infrastructure based on a packet sniffing method, which allows the service infrastructure to inspect traffic packets from the edge infrastructure to identify service infrastructure configuration data (e.g., discovered configuration data). The discovered configuration data is used to configure the service infrastructure. The sniffing-based process utilizes edge infrastructure advertisements of the presence of the edge infrastructure to identify the discovered configuration data and at least temporarily circumvents direct configuration through a routing protocol.
[0025] The sniffing-based process can be described in more detail by example, which does not represent a limitation. When the edge infrastructure is configured with routing protocol configuration data, the sniffing-based process uses the action of the edge infrastructure (e.g., the edge infrastructure configuration manager or switch) to identify the portion of the service infrastructure configuration data (i.e., the configuration data discovered). The edge infrastructure (e.g., the switch) can be configured in a waiting state (e.g., a BGP-based state), which includes initiating and performing neighbor discovery operations (e.g., Internet Control Message Protocol--ICMPv6 Neighbor Discovery Request and Address Resolution Protocol--ARP Request). In an exemplary implementation, the waiting state can support IPv4 or IPv6 configuration of the service infrastructure, and also includes reserving IP addresses (e.g., at least 2 IP addresses--one for each of the edge infrastructure and service infrastructure TOR). The edge infrastructure in the waiting state periodically sends out data packets and listens for responses from the expected service infrastructure for direct configuration through the routing protocol. Basically, the edge infrastructure expects to discover who (e.g., the switch) to communicate with from the service infrastructure. However, without any manual intervention, the service infrastructure (e.g., a service configuration manager or a server) monitors the data traffic and inspects the data packets to discover and extract at least a portion of the service infrastructure configuration data (e.g., the discovered configuration data). The service infrastructure can be in a pre-configured state that allows the service infrastructure to monitor the data traffic. For example, a service infrastructure TOR switch can be configured in a transparent state to forward all traffic to a server on a rack, where the server includes a service infrastructure configuration manager that supports identifying the discovered configuration data. The discovered configuration data (e.g., a reserved IP address for a server) can be used to autonomously configure (e.g., an initial configuration state) the service infrastructure.
[0026] The autonomous configuration includes initializing the service infrastructure to an initial configuration state. Specifically, during the initial configuration state, the service infrastructure configuration manager communicates with the service provider infrastructure via the edge infrastructure while bypassing the configuration of the TOR switch using the routing protocol configuration data. The reserved IP address for the service infrastructure is an Internet accessible IP address that the edge infrastructure trusts and any device using the IP address is allowed to access the Internet based on the IP address. The initial configuration state includes the service infrastructure configuration manager accessing the service provider infrastructure to retrieve remote configuration data, as described in more detail herein.
[0027] With reference to a conversion-based process, the conversion-based process supports configuration of a service infrastructure based on a network addressing and routing method (e.g., anycast), which allows the service infrastructure to be accessible via an edge infrastructure using conversion configuration data (e.g., anycast, conversion IP address, etc.) by a service infrastructure provider. The conversion configuration data is used to configure the service infrastructure, and the conversion IP address of the conversion configuration data is used by the service infrastructure to peer with the edge infrastructure. Peering can refer to creating an interconnection between separate networks to exchange business. The conversion-based process utilizes an edge infrastructure that peers with the service infrastructure based on a conversion IP address to provide Internet accessibility to the service infrastructure. Utilizing Internet accessibility, the service infrastructure broadcasts the conversion IP address so that the service provider infrastructure can communicate with the service infrastructure to at least temporarily circumvent direct configuration through a routing protocol.
[0028] The conversion-based process can be described in more detail by way of example, which does not represent a limitation. The conversion-based process utilizes conversion configuration data (e.g., conversion IP addresses) and conversion services to configure a service infrastructure (e.g., a TOR switch) with a conversion IP address (e.g., an anycast IP address). For example, the service infrastructure may be in a pre-configured state, in which the service infrastructure is configured with an anycast IP address. The anycast IP address supports peering with the edge infrastructure based on the anycast IP address. The edge infrastructure is in a waiting state until the anycast IP address is used to peer the edge infrastructure with the service infrastructure. In an exemplary implementation, the conversion IP address (or conversion IP address range) allows data to be routed between the nearest devices with the same conversion IP address configuration, and then the edge infrastructure peers with the service infrastructure. In particular, the edge infrastructure peers with the service infrastructure using the anycast IP address. The service infrastructure is accessible to the Internet via the edge infrastructure and can be broadcast based on the anycast IP address and Internet accessibility.
[0029] Autonomous configuration includes initializing the service infrastructure to an initial configuration state. The conversion-based process utilizes the peering of the service infrastructure and the edge infrastructure to configure the initial configuration state in the service infrastructure (e.g., peering with the edge infrastructure and Internet accessibility). The service infrastructure in the initial configuration state also includes the service infrastructure broadcasting via the Internet using anycast IP addresses, and the service provider infrastructure can use the anycast IP address to configure the service infrastructure. In the initial configuration state, the edge infrastructure can receive communications from the service provider infrastructure via the anycast IP address. The service provider infrastructure (e.g., a predefined remote configuration data location) communicates with the service infrastructure in response to the broadcast for supply via the conversion IP address. In this regard, the edge infrastructure and the service infrastructure circumvent direct configuration using routing protocols. The service provider infrastructure (including the supply manager and remote configuration data) can now reach the service infrastructure via anycast IP address. In particular, the service provider infrastructure can reach the TOR switch without human intervention to configure the TOR switch and the service infrastructure using remote configuration data, as described in more detail herein.
[0030] The service infrastructure can be configured with remote configuration data. Remote configuration data can be provided from a service provider infrastructure (e.g., a cluster) to further configure the service infrastructure. Remote configuration data can refer to different types of computing configurations and settings for the service infrastructure so that the service infrastructure can operate appropriately and provide access to technical resources. Remote configuration data can also allow the service provider to manage the service infrastructure. Remote configuration data may include hardware and software configurations for the service infrastructure. For example, remote configuration data may include network configurations that support intra-rack and extra-rack communications. Other types of variations and combinations of remote configuration data are contemplated with embodiments of the present disclosure.
[0031] The autonomous configuration system configures the service infrastructure based on an autonomous configuration framework that includes an initial configuration state and a final configuration state and, in an embodiment, an intermediate configuration state for security purposes. The intermediate configuration state includes provisioning the service infrastructure using an incremental provisioning process based at least in part on security checks that must be satisfied as part of the incremental provisioning process. The incremental provisioning process operates to establish trust between the service infrastructure and a service provider infrastructure (e.g., via an intermediate service provider infrastructure having intermediate remote configuration data). The intermediate remote configuration data may be transmitted to the service infrastructure in the initial configuration state, wherein the intermediate remote configuration data is used to initialize the intermediate configuration state (e.g., a trust establishment state).
[0032] The intermediate configuration state may be based on any variation and combination of trusted computing (e.g., endorsement keys, memory shielding, sealed storage, remote attestation, trusted third parties, etc.) used to support communication between the service infrastructure and the service provider infrastructure. After trust is established during the trust establishment state, further communication with the master service infrastructure having master remote configuration data may occur. The master remote configuration data may then be transmitted to the service infrastructure so that the service infrastructure may be configured to a final configuration state.
[0033] In this way, autonomous configuration of the service infrastructure in the edge data center can be achieved based on avoiding direct configuration using routing protocol configuration data and relying on an autonomous discovery service (e.g., a sniffing service or a conversion service), which identifies the discovered configuration data used for the initial configuration of the service infrastructure to access remote configuration data for the final configuration of the service infrastructure.
[0034] refer to Figure 1 , embodiments of the present disclosure may be discussed with reference to an exemplary distributed computing environment, which is an operating environment for implementing the functionality described herein of the autonomous configuration system 100. The autonomous configuration system 100 includes an edge data center 110 having an edge infrastructure 120 and an edge infrastructure configuration manager 122. The edge data center 110 also includes a service infrastructure 130 having a service infrastructure configuration manager 132. The service infrastructure configuration manager 132 may operate an autonomous discovery service 134. The autonomous configuration system 100 also includes a service provider infrastructure 150 having a provisioning manager 160, which has remote configuration data 162. The components of the autonomous configuration system 100 may communicate with each other via a network 140, which may include, but is not limited to, one or more local area networks (LANs) and / or wide area networks (WANs). Such networking environments are common in offices, enterprise-wide computer networks, intranets, and the Internet.
[0035] Figure 2 An autonomous configuration system 100 in an alternative embodiment is shown in FIG. Figure 2 include Figure 1 The corresponding components shown have additional components that support self-configuring system capabilities. Figure 2 Included are edge data center 110, edge infrastructure 120, switch 120A, edge infrastructure configuration manager 122, and service infrastructure having switch 130A and server 130B (e.g., blades on a rack) running service infrastructure configuration manager 132. Service infrastructure configuration manager 132 may operate sniffing service 134A and / or conversion service 134B, as described in more detail herein. Figure 2Also included is a service provider infrastructure 150 which, in an exemplary embodiment, supports an incremental provisioning process for security purposes. The service provider infrastructure 150 includes an intermediate provisioning manager 160A having intermediate remote configuration data 162A and a master provisioning manager 160B having master remote configuration data 162B.
[0036] As used herein, a system refers to any device, process or service, or a combination thereof. A system can be implemented as hardware, software, firmware, a dedicated device, or any combination thereof using components. A system can be integrated into a single device, or it can be distributed across multiple devices. The various components of a system can be co-located or distributed. A system can be formed by other systems and their components. It should be understood that this and other arrangements described herein are set forth only as examples.
[0037] Having identified various components of a distributed computing environment, it should be noted that within the scope of the present disclosure, any number of components may be employed to achieve the desired functionality. Figure 1 and Figure 2 The various components are shown with lines. Figure 1 and Figure 2 Some components of the system 100 are depicted as single components, but the depiction is exemplary in nature and in number, and should not be interpreted as limiting all implementations of the present disclosure. The functions of the autonomous configuration system 100 can be further described based on the functions and features of the components listed above.
[0038] In addition to those shown or in place of those shown, other arrangements and elements (e.g., machines, interfaces, functions, sequences, and functional groupings, etc.) may be used, and some elements may be omitted completely. In addition, many elements described herein are functional entities that may be implemented as discrete or distributed components or implemented in conjunction with other components, and may be implemented in any suitable combination and position. The various functions described herein as being performed by one or more entities may be performed by hardware, firmware, and / or software. For example, the various functions may be performed by a processor that performs instructions stored in a memory.
[0039] Continue to refer Figure 2 , Figure 2An edge data center 110 includes hardware (e.g., power supplies, racks, and network interface controllers (NICs)) and software components (applications, application programming interfaces (APIs), SQL databases) that support operation and rely on each other to operate. When provided by a service provider who does not own and control the edge data center 110, the edge data center 110 provides a housing for computing systems and related components collectively referred to as edge infrastructure or service infrastructure. The edge data center can specifically provide network access to the Internet for a service infrastructure (e.g., service infrastructure 130) running in the edge data center 110. The edge data center 110 through the edge infrastructure (e.g., edge infrastructure 120) supports configuring the service infrastructure 130 to be able to access the Internet. For example, the edge infrastructure 120 includes a network device (e.g., switch 120A) that links to the service infrastructure 130 to reach other autonomous networks (e.g., service provider infrastructure 150). In particular, a routing protocol (e.g., border gateway protocol) can be configured on the switch 120A. When the edge infrastructure is linked to the service infrastructure 130 (eg, switch 130A) through a routing protocol, the routing protocol supports routing decisions for communications from the service infrastructure 130 based on paths, network policies, or rule sets configured for making routing decisions.
[0040] The switch 120A operates with the edge infrastructure configuration manager 122 to support operations that perform the functions of the switch 120A. The edge infrastructure configuration manager configures the switch 120A in a waiting state. With the embodiments described herein, in response to the final configuration state of the service infrastructure 130, the switch 120A ultimately operates based on the routing protocol; however, in order to achieve autonomous configuration of the service infrastructure 130, the routing protocol is circumvented based on the configuration data (e.g., the discovered configuration data) discovered from the switch 120A while in the waiting state. The switch 120A is in the waiting state because the switch has not yet been configured with a final configuration to operate using the routing protocol.
[0041] The waiting state of switch 120A can operate with an autonomous discovery service or an autonomous conversion service: a sniffing-based process or a conversion-based process. In the sniffing-based process in the waiting state of switch 120A, switch 120A is configured based on routing protocol configuration data, and switch 120A uses neighbor discovery operations to announce its existence. Switch 120A periodically sends out data packets and listens for responses from switch 130A. In the conversion-based process in the waiting state of switch 120A, switch 120A is also configured based on routing protocol configuration data and optionally (for example, provided in advance from a service infrastructure provider) based on a conversion IP address. Switch 120A responds to the announcement of the conversion IP address and then starts operations based on the conversion IP address. Traditionally, switch 130A can be manually and directly configured based on linking switch 130A with switch 120A using routing protocol configuration data. However, with embodiments of the present invention, configuring switch 130A for routing protocols is at least temporarily circumvented to support automatic configuration of service infrastructure.
[0042] Continue to refer Figure 2 , the service infrastructure 130 includes a switch 130A, which can be configured in a final configuration state of the service infrastructure 130 to operate with the switch 120A using a routing protocol. The switch 130A is in a pre-configuration state of the service infrastructure 130 for autonomous discovery of services, and the switch 130A is configured in a transparent state, where the switch 130A operates to forward traffic received at the switch. The switch 130A can forward data traffic to additional components in the service infrastructure 130 (e.g., a server 130B running a service infrastructure configuration manager 132). During the pre-configuration state, the service infrastructure configuration manager 132 can control operations in the service infrastructure 130 based on traffic (e.g., data packets) forwarded from the switch 130A in the transparent state. In this regard, the switch 130A, which is conventionally configured to operate with the switch 120A, is at least temporarily bypassed so that the service infrastructure configuration manager 132 begins autonomous configuration of the service infrastructure 130. The switch 130A in the state pre-configuration state of the service infrastructure 130 for autonomous switching services can be configured with a switching IP address. The switch 130A, alone or in combination with the translation service, is operable to perform translation IP based operations to initiate peering with the edge infrastructure 120. Other variations and combinations of pre-configured states are contemplated with embodiments of the present disclosure.
[0043] The service infrastructure configuration manager 132 runs on the server 130B to support the autonomous configuration function. The service infrastructure configuration manager 132 can implement an autonomous discovery service or an autonomous conversion service. For example, a sniffing service 134A that supports a sniffing-based process for autonomous discovery or a conversion service 134B that supports a conversion-based process for autonomous configuration. The service infrastructure configuration manager 132 can be initialized in a pre-configured state to support identifying the discovered configuration data for autonomous discovery or accessing configuration data (e.g., converting IP addresses) for autonomous configuration. The discovered configuration data is used to configure the service infrastructure to access the service provider infrastructure. For example, during the sniffing-based process, the service infrastructure configuration manager listens to the packets transmitted from the switch 120A and identifies the discovered configuration data. For example, the discovered configuration data can be a reserved IP address and corresponds to a paired IP address in the switch 120A, so that the service infrastructure is provided with access to other autonomous networks.
[0044] In the conversion-based process, the edge infrastructure 120 can be configured to listen for the presence of the conversion IP address. In one embodiment, the service infrastructure manager configures the switch 130A based on the conversion IP address so that the edge infrastructure can be peered with the service infrastructure via the switch. The conversion IP address is provided to the service infrastructure from the service provider to pre-configure the service infrastructure based on the conversion IP address. The conversion IP address links the server 130B and / or the switch 130A to the switch 120A to access other autonomous networks (i.e., Internet accessibility). In this regard, the service infrastructure configuration manager 132 can be in a pre-configured state to access the conversion configuration data to configure the service infrastructure in an initial configuration state to access the service provider infrastructure and remote configuration data.
[0045] The service provider infrastructure 150 is configured to support provisioning managers (e.g., provisioning manager 160, intermediate provisioning manager 160A, and master provisioning manager 160B) that provide remote configuration data (e.g., remote configuration data 162, intermediate remote configuration data 162A), and master remote configuration data 162B). The provisioning manager supports a provisioning process that allows the service infrastructure 130 to receive remote configuration data so that the service infrastructure 130 is configured to provide services of the service provider. The service infrastructure 130 can be configured to a final configuration that allows the service infrastructure 130 to support computing and storage operations for users to access technical resources via the service infrastructure 130. For example, users can be provided access to data repositories or authorization to systems, network applications, and databases based on appropriate credentials. In particular, the service infrastructure final configuration includes the switch 130A communicating with the switch 120A using a routing protocol to direct communications from the service infrastructure 130. In this regard, the switch 130A can be specifically reconfigured from a transparent state to a final configuration state as part of the final configuration of the service infrastructure 130. Additional components of the service infrastructure 130 are further fully provisioned using remote configuration data and processes defined for configuring the service infrastructure 130 .
[0046] like Figure 2 As shown, the service provider infrastructure 150 may include an intermediate provisioning manager 160A and a master provisioning manager 160B that provide intermediate remote configuration data 162A and master remote configuration data 162B. The automatic configuration system 100 supports an incremental provisioning process that provides enhanced security in an autonomous configuration system. The incremental provisioning process operates with the intermediate provisioning manager 160A to establish initial trust between the service infrastructure 130 and the intermediate provisioning manager 160A. The intermediate provisioning manager 160A can communicate with the service infrastructure in an initial configuration state, wherein the intermediate remote configuration data 162A is used to initialize the intermediate configuration state (e.g., a trust establishment state) at the service infrastructure. The trust establishment state can be based on any variation and combination of trusted computing (e.g., endorsement keys, memory shielding, sealed storage, remote attestation, trusted third parties, etc.) used to support communication between the service infrastructure 130 and the service provider infrastructure 150 as part of establishing trust with the service infrastructure 130. In an exemplary embodiment, the service infrastructure establishes a trust-based authentication credential (e.g., a hardware- or software-based authentication credential) that is transmitted to the intermediate provisioning manager 160A. In operation, after trust is established, further communication with the master provisioning manager 160B with the master remote configuration data 162B may occur. The master remote configuration data 162B may then be transmitted to the service infrastructure 130 so that the service infrastructure may be configured in a final configuration state, as described above.
[0047] Now turn to Figure 3 , a flowchart illustrating a method 300 for providing autonomous configuration of a service infrastructure is provided. The method 300 can be performed using the autonomous configuration system described herein. In particular, one or more computer storage media have computer executable instructions implemented thereon, which, when executed by one or more processors, can cause the one or more processors to perform the method 300. Initially, in box 310, discovered configuration data or transformation configuration data are identified or utilized for the service infrastructure, respectively. The discovered configuration data or transformation configuration data supports the service infrastructure to avoid routing protocols. The service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data or transformation configuration data, the discovered configuration data is discovered based on an autonomous discovery service, and the transformation configuration data is implemented based on an autonomous transformation service.
[0048] In a first embodiment, the autonomous discovery service is a sniffing service that circumvents configuration of an intended switch of the service infrastructure and, instead, identifies discovered configuration data based on monitoring data traffic including at least one reserved IP address. Using the autonomous discovery service, the discovered configuration data is identified from an edge infrastructure operating in a waiting state to configure the edge infrastructure to link with an intended switch of the service infrastructure based on a routing protocol (e.g., routing protocol configuration data). In a second embodiment, the autonomous conversion service is a conversion service that circumvents configuration of an intended switch of the service infrastructure and, instead, utilizes conversion configuration data including a conversion IP address.
[0049] At block 312, an initial configuration state is configured in the service infrastructure based on the discovered configuration data. In the initial configuration state, the service infrastructure may communicate with a service provider infrastructure associated with the service infrastructure to access remote configuration data. At block 314, a first portion of the remote configuration data is accessed from the service provider infrastructure, the first portion of the remote configuration data being intermediate remote configuration data from an intermediate provisioning manager. The intermediate provisioning manager in the service provider infrastructure operates to transmit intermediate remote configuration data for implementing an incremental provisioning process. The intermediate remote configuration data supports configuring the service infrastructure in an intermediate configuration state, the intermediate configuration state being a trust establishment state between the service infrastructure and the service provider infrastructure. At block 316, the intermediate configuration state is configured in the service infrastructure using the intermediate remote configuration data.
[0050] At block 318, a second portion of the remote configuration data is accessed from the service provider infrastructure. The second portion of the remote configuration data is master remote configuration data from the master provisioning manager. The master provisioning manager in the service infrastructure operates to transmit the master remote configuration data for implementing the incremental provisioning process. The master remote configuration data supports configuring the service infrastructure in a final configuration state. The final configuration state may include switches of the edge infrastructure and switches of the service infrastructure communicating using a routing protocol that was previously circumvented based on the discovered configuration data. At block 320, the final configuration state is configured in the service infrastructure using the master remote configuration data.
[0051] Now turn to Figure 4 , a flowchart illustrating a method 400 for providing autonomous configuration of a service infrastructure is provided. The method 400 can be performed using the autonomous configuration system described herein. Initially, at box 410, discovered configuration data is identified for a service infrastructure from an edge infrastructure in a waiting state, the waiting state including the edge infrastructure performing a neighbor discovery operation. The discovered configuration data supports the service infrastructure to avoid routing protocols. The service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data, the discovered configuration data being discovered based on a sniffing service. The sniffing service avoids the configuration of the service infrastructure using a routing protocol to identify the discovered configuration data. The sniffing service identifies the discovered configuration data based on monitoring data traffic including at least one reserved IP address. The sniffing service operates when the service infrastructure is in a pre-configured state, the pre-configured state including a switch of the service infrastructure being in a transparent state, the switch forwarding the monitored data traffic to a service infrastructure configuration manager. At box 412, an initial configuration state is configured in the service infrastructure based on the discovered configuration data. The service infrastructure can then communicate with a service provider infrastructure associated with the service infrastructure to access the remote configuration data. At block 414, remote configuration data is accessed from the service provider infrastructure. At block 416, the final configuration state is configured in the service infrastructure.
[0052] Now turn to Figure 5, a flowchart illustrating a method 500 for providing autonomous configuration of a service infrastructure is provided. The method 500 can be performed using the autonomous configuration system described herein. Initially, at box 510, discovered configuration data is identified for a service infrastructure from an edge infrastructure in a waiting state, the waiting state including the edge infrastructure performing a conversion IP address operation. The discovered configuration data supports the service infrastructure to avoid routing protocols. The service infrastructure is instead configured to access remote configuration data based on the discovered configuration data. The conversion service avoids the configuration of the service infrastructure using routing protocols to identify the discovered configuration data. The conversion service identifies the discovered configuration data based on monitoring data traffic including conversion IP addresses. The conversion service operates when the service infrastructure is in a pre-configured state, the pre-configured state including a switch of the service infrastructure in a transparent state, the switch forwarding the monitored data traffic to a service infrastructure configuration manager. At box 512, an initial configuration state is configured in the service infrastructure based on the discovered configuration data. The service infrastructure can then communicate with a service provider infrastructure associated with the service infrastructure to access the remote configuration data. At box 514, the remote configuration data is accessed from the service provider infrastructure. At block 516 , the final configuration state is configured in the service infrastructure.
[0053] With reference to an autonomous configuration system, the embodiments described herein support automatic and autonomous configuration of a service infrastructure. An autonomous configuration system component refers to an integrated component for autonomous configuration. An integrated component refers to a hardware architecture and a software framework that support data access functions using an autonomous configuration system. The hardware architecture refers to physical components and their interrelationships, and the software framework refers to software that provides functions that can be implemented with hardware implemented on a device. An end-to-end software-based autonomous configuration system can operate within an autonomous configuration system component to operate computer hardware to provide autonomous configuration system functions. In this way, the autonomous configuration system component can manage resources and provide services for autonomous configuration system functions. Any other variations and combinations thereof are considered together with the embodiments of the present disclosure.
[0054] As an example, the autonomous configuration system may include an API library including specifications for routines, data structures, object classes, and variables that may support interaction between the hardware architecture of the device and the software framework of the autonomous configuration system. These APIs include configuration specifications for the autonomous configuration system so that different components therein may communicate with each other in the autonomous configuration system, as described herein.
[0055] Having briefly described an overview of embodiments of the present invention, an exemplary operating environment in which embodiments of the present invention may be implemented is described below in order to provide a general context for various aspects of the present invention. Figure 6, in particular, an exemplary operating environment for implementing embodiments of the invention is shown and generally designated as computing device 600. Computing device 600 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should computing device 600 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated.
[0056] The present invention may be described in the general context of computer code or machine usable instructions, including computer executable instructions, such as program modules, executed by a computer or other machine, such as a personal data assistant or other handheld device. In general, program modules, including routines, programs, objects, components, data structures, etc., refer to code that performs specific tasks or implements specific abstract data types. The present invention may be implemented in a variety of system configurations, including handheld devices, consumer electronics, general-purpose computers, more specialized computing devices, etc. The present invention may also be implemented in distributed computing environments, where tasks are performed by remote processing devices linked through a communications network.
[0057] refer to Figure 6 , computing device 600 includes bus 610 that directly or indirectly couples the following devices: memory 612, one or more processors 614, one or more presentation components 616, input / output ports 618, input / output components 620, and an illustrative power supply 622. Bus 610 represents what may be one or more buses (e.g., an address bus, a data bus, or a combination thereof). Although for clarity, Figure 6 The various blocks of the computer are shown with lines, but in reality, delineating the various components is not so clear, and metaphorically, the lines would more accurately be gray and fuzzy. For example, a presentation component such as a display device may be considered an I / O component. Furthermore, a processor has memory. It is recognized that this is the nature of the art, and it is reiterated that Figure 6 The diagrams are merely illustrative of exemplary computing devices that may be used in conjunction with one or more embodiments of the present invention. No distinction is made between categories such as "workstation," "server," "laptop," "handheld device," etc., as all of these are referred to in the same manner. Figure 6 within the scope of and with reference to a “computing device”.
[0058] The computing device 600 typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computing device 600, and includes volatile and non-volatile media, removable and non-removable media. By way of example and not limitation, computer-readable media can include computer storage media and communication media.
[0059] Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and can be accessed by the computing device 600. Computer storage media excludes the signals themselves.
[0060] Communication media typically implement computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" means a signal that sets or changes one or more of its characteristics in a manner that can encode information in the signal. As an example and not limitation, communication media include wired media such as a wired network or a direct wired connection and wireless media such as acoustic, RF, infrared and other wireless media. Any combination of the above should also be included in the scope of computer readable media.
[0061] Memory 612 includes computer storage media in the form of volatile and / or non-volatile memory. Memory can be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard drives, optical drives, etc. Computing device 600 includes one or more processors that read data from various entities such as memory 612 or I / O components 620. Presentation component(s) 616 present data indications to a user or other device. Exemplary presentation components include display devices, speakers, printing components, vibration components, etc.
[0062] I / O ports 618 allow computing device 600 to be logically coupled to other devices including I / O components 620, some of which may be built-in. Exemplary components include microphones, joysticks, game pads, satellite dishes, scanners, printers, wireless devices, and the like.
[0063] Reference now Figure 7 , Figure 7 An exemplary distributed computing environment 700 is shown in which implementations of the present disclosure may be employed. In particular, Figure 7The high-level architecture of the autonomous configuration system ("system") in the cloud computing platform 710 is shown, wherein the system supports seamless modification of software components. It should be understood that this and other arrangements described herein are set forth as examples only. In addition to those shown or in place of those shown, other arrangements and elements (e.g., machines, interfaces, functions, sequences, and functional groupings, etc.) can be used, and some elements can be omitted completely. In addition, many of the elements described herein are functional entities that can be implemented as discrete or distributed components or in combination with other components, and can be implemented in any suitable combination and position. The various functions described herein as being performed by one or more entities can be performed by hardware, firmware, and / or software. For example, various functions can be performed by a processor that executes instructions stored in a memory.
[0064] The data center can support a distributed computing environment 700 including a cloud computing platform 710, a rack 720, and nodes 730 (e.g., computing devices, processing units, or blades) in the rack 720. The system can be implemented with a cloud computing platform 710 that runs cloud services across different data centers and geographic regions. The cloud computing platform 710 can implement a fabric controller 740 component for provisioning and managing resource allocation, deployment, upgrades, and management of cloud services. Typically, the cloud computing platform 710 is used to store data or run service applications in a distributed manner. The cloud computing infrastructure 710 in the data center can be configured to host and support the operation of endpoints of specific service applications. The cloud computing infrastructure 710 can be a public cloud, a private cloud, or a dedicated cloud.
[0065] The node 730 may be supplied with a host 750 (e.g., an operating system or runtime environment) running a defined software stack on the node 730. The node 730 may also be configured to perform a dedicated function (e.g., a computing node or a storage node) within the cloud computing platform 710. The node 730 is allocated to run one or more parts of a tenant's service application. A tenant may refer to a customer utilizing the resources of the cloud computing platform 710. The service application components of the cloud computing platform 710 that support a specific tenant may be referred to as a tenant infrastructure or lease. The terms service application, application, or service are used interchangeably herein and broadly refer to any software or software portion that runs on top of a data center or accesses storage and computing device locations within a data center.
[0066] When more than one separate service application is supported by the node 730, the node can be divided into virtual machines (e.g., virtual machine 752 and virtual machine 754). Physical machines can also run separate service applications at the same time. Virtual machines or physical machines can be configured as individualized computing environments supported by resources 760 (e.g., hardware resources and software resources) in the cloud computing platform 710. It can be expected that resources can be configured for specific service applications. In addition, each service application can be divided into functional parts so that each functional part can run on a separate virtual machine. In the cloud computing platform 710, multiple servers can be used to run service applications and perform data storage operations in a cluster. In particular, servers can perform data operations independently, but are disclosed as a single device called a cluster. Each server in a cluster can be implemented as a node.
[0067] The client device 780 may be linked to a service application in the cloud computing platform 710. The client device 780 may be any type of computing device, for example, it may correspond to a reference Figure 7 700 is described. Client device 780 may be configured to issue commands to cloud computing platform 710. In embodiments, client device 780 may communicate with service applications via a virtual Internet Protocol (IP) and a load balancer or other means of directing communication requests to designated endpoints in cloud computing platform 710. Components of cloud computing platform 710 may communicate with each other via a network (not shown), which may include, but is not limited to, one or more local area networks (LANs) and / or wide area networks (WANs).
[0068] Having described various aspects of the distributed computing environment 700 and the cloud computing platform 710, it is noted that within the scope of the present disclosure, any number of components may be employed to implement the desired functionality. Although for clarity, Figure 7 The various components of the MCU are shown with lines, but in reality, demarcating the various components is not so clear, and metaphorically, the lines may be more accurately gray or fuzzy. Figure 7 Some of the components of the present disclosure are depicted as a single component, but the depiction is exemplary in nature and in number and should not be construed as limiting all implementations of the present disclosure.
[0069] The embodiments described in the paragraphs may be combined with one or more specifically described alternatives. In particular, in alternatives, the claimed embodiments may contain references to more than one other embodiment. The claimed embodiments may specify further limitations to the claimed subject matter.
[0070] The technical solutions of the embodiments of the present invention are specifically described herein to meet the statutory requirements. However, the description itself is not intended to limit the scope of this patent. On the contrary, the inventors have anticipated that the claimed technical solutions may also be implemented in other ways to include steps different from the steps described in this document or a combination of similar steps in combination with other existing or future technologies. In addition, although the terms "step" and / or "block" may be used herein to represent different elements of the method employed, these terms should not be interpreted as implying any particular order among or between the various steps disclosed herein, unless and when the order of the various steps is explicitly described.
[0071] For purposes of this disclosure, the word "including" has the same broad meaning as the word "comprising," and the word "access" includes "receiving," "referencing," or "retrieving." Furthermore, unless otherwise indicated, words such as "a," and "an" include the plural as well as the singular. Thus, for example, the constraint of "feature" is satisfied where there is one or more of the feature. Furthermore, the term "or" includes conjunctions, disjunctive conjunctions, and both (thus, a or b includes a or b and a and b).
[0072] For the purposes of the above detailed discussion, embodiments of the present invention are described with reference to a distributed computing environment; however, the distributed computing environment described herein is exemplary only. Components may be configured to perform novel aspects of the embodiments, where the term "configured to" may refer to "programmed to" perform a specific task or implement a specific abstract data type using code. Furthermore, while embodiments of the present invention may generally refer to autonomous configuration systems and schematic diagrams described herein, it should be understood that the described techniques may be extended to other implementation contexts.
[0073] Embodiments of the present invention have been described with respect to particular embodiments, which are intended in all respects to be illustrative rather than restrictive. Alternative embodiments will become apparent to those skilled in the art to which the present invention pertains without departing from the scope of the present invention.
[0074] From the foregoing it will be seen that this invention is one well adapted to attain all ends and objects hereinbefore recited, together with other advantages which are obvious and inherent to the structure.
[0075] It will be understood that certain features and subcombinations are of utility and may be employed without reference to other features or subcombinations. This is contemplated by the claims and is within the scope of the claims.
Claims
1. A system for implementing autonomous configuration of a service infrastructure, the system comprising: One or more hardware processors and a memory storing computer-executable instructions and components embodied thereon that, when executed by the one or more hardware processors, cause the hardware processors to perform: Service infrastructure configuration manager to: identifying discovered configuration data for a service infrastructure, wherein the discovered configuration data is discovered based on an autonomous discovery service, wherein the discovered configuration data includes instructions to bypass a routing protocol; configuring an initial configuration state in the service infrastructure based on the discovered configuration data, such that the service infrastructure can communicate with a service provider infrastructure associated with the service infrastructure to access remote configuration data; accessing the remote configuration data from the service provider infrastructure; and A final configuration state in the configuration service infrastructure is configured.
2. The system according to claim 1, further comprising: Edge infrastructure configuration manager to: maintaining routing protocol configuration data for an edge infrastructure and the service infrastructure, wherein the edge infrastructure configuration manager supports the configuration of a routing protocol of the service infrastructure based on the routing protocol configuration data, wherein switches of the edge infrastructure are configured based on the routing protocol configuration data, and storing a portion of a service infrastructure portion of the routing protocol configuration data, the routing protocol configuration data allowing switches of the service infrastructure to communicate with switches of the edge infrastructure based on the routing protocol; as well as operating in a wait state to facilitate configuration of the service infrastructure, wherein the wait state includes the switches of the edge infrastructure being configured based on the routing protocol, and performing wait state operations in anticipation of configuring a link between the switches of the edge infrastructure and the switches of the service infrastructure.
3. A system according to claim 1, wherein the service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data, wherein the discovered configuration data is identified from an edge infrastructure, the edge infrastructure operating in a waiting state to configure the edge infrastructure to link with an expected switch of the service infrastructure based on the routing protocol.
4. The system of claim 1 , further comprising identifying transformation configuration data, wherein the transformation configuration data enables the service infrastructure to bypass the routing protocol such that the service infrastructure is instead configured to access remote configuration data based on the transformation configuration data, the transformation configuration data being identified based on an autonomous transformation service; and The conversion configuration data is configured in the service infrastructure, the conversion configuration data includes a conversion IP address for the service infrastructure to be peered with an edge infrastructure, and the edge infrastructure operates in a waiting state to configure the edge infrastructure to be linked to an expected switch of the service infrastructure based on the routing protocol.
5. The system of claim 4, wherein peering the service infrastructure with the edge infrastructure provides Internet accessibility to the service infrastructure such that the service infrastructure broadcasts based on the translated IP address to receive communications from a service provider infrastructure.
6. The system of claim 4, wherein the autonomous switching service is a switching service that bypasses the configuration of the service infrastructure using the routing protocol, wherein the switching service utilizes the switching configuration data to peer with an edge infrastructure.
7. The system of claim 1 , wherein the autonomous discovery service is a sniffing service that circumvents configuration of the service infrastructure using the routing protocol, wherein the sniffing service identifies the discovered configuration data based on monitoring data traffic, the data traffic comprising at least one reserved IP address.
8. The system according to claim 1 further includes an intermediate provisioning manager in the service provider infrastructure, which is used to transmit intermediate remote configuration data for implementing the incremental provisioning process, wherein the intermediate remote configuration data supports configuring the service infrastructure in an intermediate configuration state, and the intermediate configuration state is a trust establishment state between the service infrastructure and the service provider infrastructure.
9. The system according to claim 1 further includes a master provisioning manager in the service provider infrastructure for transmitting master remote configuration data for implementing an incremental provisioning process, wherein the master remote configuration data supports configuring the service infrastructure in a final configuration state, and the final configuration state includes switches of the edge infrastructure and switches of the service infrastructure communicating using the routing protocol that was previously avoided based on the discovered configuration data.
10. A computer-implemented method for providing autonomous configuration of a service infrastructure, the method comprising: identifying discovered configuration data for a service infrastructure, wherein the discovered configuration data is discovered based on an autonomous discovery service, wherein the discovered configuration data includes instructions to bypass a routing protocol; configuring an initial configuration state in the service infrastructure based on the discovered configuration data, such that the service infrastructure can communicate with a service provider infrastructure associated with the service infrastructure to access remote configuration data; accessing the remote configuration data from the service provider infrastructure; and A final configuration state in the configuration service infrastructure is configured.
11. A method according to claim 10, wherein the service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data, wherein the discovered configuration data is identified from an edge infrastructure, the edge infrastructure operating in a waiting state to configure the edge infrastructure to link with an expected switch of the service infrastructure based on the routing protocol.
12. The method of claim 11, wherein the edge infrastructure in the waiting state performs a neighbor discovery operation to link with the prospective switch of the service infrastructure.
13. The method of claim 10, wherein the autonomous discovery service is a sniffing service that circumvents configuration of the service infrastructure using the routing protocol to identify the discovered configuration data.
14. The method of claim 13, wherein the sniffing service identifies the discovered configuration data based on monitoring data traffic, the data traffic comprising at least one reserved IP address.
15. The method of claim 13, wherein the sniffing service operates when the service infrastructure is in a pre-configured state, the pre-configured state comprising a switch of the service infrastructure being in a transparent state, the switch forwarding the monitored data traffic to a service infrastructure configuration manager.
16. A computer storage medium having computer executable instructions embodied thereon, the computer executable instructions, when executed by one or more processors, causing the one or more processors to perform a method for providing autonomous configuration of a service infrastructure, the method comprising: identifying discovered configuration data for a service infrastructure, wherein the discovered configuration data is discovered based on an autonomous discovery service, wherein the discovered configuration data includes instructions to bypass a routing protocol; configuring an initial configuration state in the service infrastructure based on the discovered configuration data, such that the service infrastructure can communicate with a service provider infrastructure associated with the service infrastructure to access remote configuration data; accessing a first portion of the remote configuration data from the service provider infrastructure, wherein the first portion of the remote configuration data is intermediate remote configuration data from an intermediate provisioning manager; configuring an intermediate configuration state in the service infrastructure using the intermediate remote configuration data; accessing, from the service provider infrastructure, a second portion of the remote configuration data, wherein the second portion of the remote configuration data is master remote configuration data from a master provisioning manager; as well as A final configuration state in the service infrastructure is configured using the master remote configuration data.
17. A medium according to claim 16, wherein the service infrastructure is alternatively configured to access remote configuration data based on the discovered configuration data, wherein the discovered configuration data is identified from an edge infrastructure, the edge infrastructure operating in a waiting state to configure the edge infrastructure to link with an expected switch of the service infrastructure based on the routing protocol, wherein the autonomous discovery service is a sniffing service, the sniffing service circumvents the configuration of the expected switch, and the discovered configuration data is alternatively identified based on monitoring data services, the data services including at least one reserved IP address.
18. The medium of claim 16, wherein the discovered configuration data is identified from an edge infrastructure that operates in a wait state to configure the edge infrastructure to link with an expected switch of the service infrastructure based on the routing protocol, wherein the autonomous discovery service is a conversion service that circumvents configuration of the expected switch and instead identifies the discovered configuration data based on monitoring data services, the data services comprising converting IP addresses.
19. A medium according to claim 16, wherein the intermediate provisioning manager in the service provider infrastructure operates to transmit intermediate remote configuration data for implementing an incremental provisioning process, wherein the intermediate remote configuration data supports configuring the service infrastructure in the intermediate configuration state, and the intermediate configuration state is a trust establishment state between the service infrastructure and the service provider infrastructure.
20. A medium according to claim 16, wherein the master provisioning manager in the service infrastructure operates to transmit master remote configuration data for implementing an incremental provisioning process, wherein the master remote configuration data supports configuring the service infrastructure in the final configuration state, and the final configuration state includes switches of the edge infrastructure and switches of the service infrastructure communicating using the routing protocol that was previously avoided based on the discovered configuration data.
