As further shown in FIG. 1F, and by reference number 155, the endpoint device may receive the service requirements from the network devices. For example, the network devices may receive the information included in the service design, and may perform the functions that satisfy the service requirements based on the information included in the service design. Performance of the functions may cause the network devices to provide service requirements (e.g., for the service) the endpoint device, and the endpoint device may receive the service requirements (e.g., the service) from the network devices.

As further shown in FIG. 1F, and by reference number 160, the management system may provide the service design to the endpoint device. For example, the management system may provide the service design to the endpoint device, and the endpoint device may display the service design to the user of the endpoint device. In some implementations, the service design (e.g., including the orphan service instance and the service instances) may be viewed by the user via a user interface provided for display by the endpoint device. The user interface may also include other orphan service instances (e.g., for other service requests) so that user may view all of the orphaned network devices associated with the network. The user interface may assist the user in determining whether the orphaned network devices are ready for reuse. The user may perform necessary steps to ensure that stale references to the orphaned network devices have been released, such as manually removing stale configurations from the orphaned network devices, disconnecting the orphaned network devices from the network, and/or the like.

As shown in FIG. 1G, and by reference number 165, the management system may receive an indication that the unreachable network device is to be reused. For example, if the user deems an orphaned network device (e.g., the unreachable network device) fit for reuse, the user may cause the endpoint device to generate the indication that the unreachable network device is to be reused. The endpoint device may provide the indication that the unreachable network device is to be reused to the management system, and the management system may receive the indication from the endpoint device.

As further shown in FIG. 1G, and by reference number 170, the management system may delete the orphan service instance and may cause the unreachable network device to be available for reuse based on the indication. For example, when the management system receives the indication that the unreachable network device is to be reused, the management system may delete the orphan service instance, which removes the unreachable network device from the orphan service instance. The management system may cause the unreachable network device to be available for reuse and reallocation by returning the identifier of the unreachable network device to an available network device pool. Thus, the unreachable network device may be available for reuse by other service requests.

As shown in FIG. 1H, and by reference number 175, the management system may receive an indication that the unreachable network device is not to be reused. For example, if the user deems an orphaned network device (e.g., the unreachable network device) unfit for reuse, the user may cause the endpoint device to generate the indication that the unreachable network device is not to be reused. The endpoint device may provide the indication that the unreachable network device is not to be reused to the management system, and the management system may receive the indication from the endpoint device.

As further shown in FIG. 1H, and by reference number 180, the management system may delete the orphan service instance and may cause the unreachable network device to not be available for reuse based on the indication. For example, when the management system receives the indication that the unreachable network device is not to be reused, the management system may delete the orphan service instance, which removes the unreachable network device from the orphan service instance. The management system may cause the unreachable network device to not be available for reuse and reallocation by removing the identifier of the unreachable network device from the available network device pool. Thus, the unreachable network device may not be available for reuse by other service requests. In some implementations, the management system may remove the identifier of the unreachable network device from the available network device pool during a maintenance time window (e.g., when no services requests are pending with the management system) so that the unreachable network device is not accidentally claimed for use during the short time period before the identifier of the unreachable network device is removed from the available network device pool.

In this way, the management system may handle inconsistencies between service provisioning by network devices. For example, when the management system identifies an unreachable network device and a user insists on utilizing the unreachable network device for service provision, the management system may orphan the unreachable network device that would otherwise have been released. The management system may create an orphan service instance that adopts ownership of the orphaned network device. The transfer of ownership may prevent the network device from being claimed by another service request. Except for the transfer of ownership, the orphan service instance may appear like a regular service instance to the placement model and the management system. The management system may treat the orphaned network device like a network device in use for service provisioning.

Thus, the management system may conserve computing resources, networking resources, and/or the like that would otherwise have been consumed by causing severe network disruption when a removed network device is brought back online, failing to provide service based on utilizing unreachable network devices, handling a poor user experience caused by failing to provide service, banning re-use of expensive unreachable network devices, and/or the like. Furthermore, the management system safely handles inconsistencies and ensures that reuse of network devices with questionable statuses occurs only after due consideration and explicit approval by the user. The management system may enable the user to quickly review and perform actions on orphaned network devices, such reusing an orphaned network device or banning reuse of an orphaned network device.

As indicated above, FIGS. 1A-1H are provided as an example. Other examples may differ from what is described with regard to FIGS. 1A-1H. The number and arrangement of devices shown in FIGS. 1A-1H are provided as an example. In practice, there may be additional devices, fewer devices, different devices, or differently arranged devices than those shown in FIGS. 1A-1H. Furthermore, two or more devices shown in FIGS. 1A-1H may be implemented within a single device, or a single device shown in FIGS. 1A-1H may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) shown in FIGS. 1A-1H may perform one or more functions described as being performed by another set of devices shown in FIGS. 1A-1H.

FIG. 2 is a diagram of an example environment 200 in which systems and/or methods described herein may be implemented. As shown in FIG. 2, the environment 200 may include a management system 201, which may include one or more elements of and/or may execute within a cloud computing system 202. The cloud computing system 202 may include one or more elements 203-212, as described in more detail below. As further shown in FIG. 2, the environment 200 may include a network 220, a network device 230, an endpoint device 240, and/or a data structure 250. Devices and/or elements of the environment 200 may interconnect via wired connections and/or wireless connections.

The cloud computing system 202 may include computing hardware 203, a resource management component 204, a host operating system (OS) 205, and/or one or more virtual computing systems 206. The cloud computing system 202 may execute on, for example, an Amazon Web Services platform, a Microsoft Azure platform, or a Snowflake platform. The resource management component 204 may perform virtualization (e.g., abstraction) of the computing hardware 203 to create the one or more virtual computing systems 206. Using virtualization, the resource management component 204 enables a single computing device (e.g., a computer or a server) to operate like multiple computing devices, such as by creating multiple isolated virtual computing systems 206 from the computing hardware 203 of the single computing device. In this way, the computing hardware 203 can operate more efficiently, with lower power consumption, higher reliability, higher availability, higher utilization, greater flexibility, and lower cost than using separate computing devices.

The computing hardware 203 may include hardware and corresponding resources from one or more computing devices. For example, the computing hardware 203 may include hardware from a single computing device (e.g., a single server) or from multiple computing devices (e.g., multiple servers), such as multiple computing devices in one or more data centers. As shown, the computing hardware 203 may include one or more processors 207, one or more memories 208, and/or one or more networking components 209. Examples of a processor, a memory, and a networking component (e.g., a communication component) are described elsewhere herein.

The resource management component 204 may include a virtualization application (e.g., executing on hardware, such as the computing hardware 203) capable of virtualizing the computing hardware 203 to start, stop, and/or manage one or more virtual computing systems 206. For example, the resource management component 204 may include a hypervisor (e.g., a bare-metal or Type 1 hypervisor, a hosted or Type 2 hypervisor, or another type of hypervisor) or a virtual machine monitor, such as when the virtual computing systems 206 are virtual machines 210. Additionally, or alternatively, the resource management component 204 may include a container manager, such as when the virtual computing systems 206 are containers 211. In some implementations, the resource management component 204 executes within and/or in coordination with a host operating system 205.

A virtual computing system 206 may include a virtual environment that enables cloud-based execution of operations and/or processes described herein using the computing hardware 203. As shown, the virtual computing system 206 may include a virtual machine 210, a container 211, or a hybrid environment 212 that includes a virtual machine and a container, among other examples. The virtual computing system 206 may execute one or more applications using a file system that includes binary files, software libraries, and/or other resources required to execute applications on a guest operating system (e.g., within the virtual computing system 206) or the host operating system 205.

Although the management system 201 may include one or more elements 203-212 of the cloud computing system 202, may execute within the cloud computing system 202, and/or may be hosted within the cloud computing system 202, in some implementations, the management system 201 may not be cloud-based (e.g., may be implemented outside of a cloud computing system) or may be partially cloud-based. For example, the management system 201 may include one or more devices that are not part of the cloud computing system 202, such as a device 300 of FIG. 3, which may include a standalone server or another type of computing device. The management system 201 may perform one or more operations and/or processes described in more detail elsewhere herein.

The network 220 may include one or more wired and/or wireless networks. For example, the network 220 may include a cellular network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a private network, the Internet, and/or a combination of these or other types of networks. The network 220 enables communication among the devices of the environment 200.

The network device 230 may include one or more devices capable of receiving, processing, storing, routing, and/or providing traffic (e.g., a packet and/or other information or metadata) in a manner described herein. For example, the network device 230 may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router or a provider core router), a virtual router, or another type of router. Additionally, or alternatively, the network device 230 may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, or a data center server), a load balancer, and/or a similar device. In some implementations, the network device 230 may be a physical device implemented within a housing, such as a chassis. In some implementations, the network device 230 may be a virtual device implemented by one or more computing devices of a cloud computing environment or a data center. In some implementations, a group of network devices 230 may be a group of data center nodes that are used to route traffic flow through a network.

The endpoint device 240 may include one or more devices capable of receiving, generating, storing, processing, and/or providing information, as described elsewhere herein. The endpoint device 240 may include a communication device and/or a computing device. For example, the endpoint device 240 may include a wireless communication device, a mobile phone, a user equipment, a laptop computer, a tablet computer, a desktop computer, a gaming console, a set-top box, a wearable communication device (e.g., a smart wristwatch, a pair of smart eyeglasses, a head mounted display, or a virtual reality headset), or a similar type of device.

The data structure 250 may include one or more devices capable of receiving, generating, storing, processing, and/or providing information, as described elsewhere herein. The data structure 250 may include a communication device and/or a computing device. For example, the data structure 250 may include a database, a server, a database server, an application server, a client server, a web server, a host server, a proxy server, a virtual server (e.g., executing on computing hardware), a server in a cloud computing system, a device that includes computing hardware used in a cloud computing environment, or a similar type of device. The data structure 250 may communicate with one or more other devices of the environment 200, as described elsewhere herein.

The number and arrangement of devices and networks shown in FIG. 2 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may be implemented within a single device, or a single device shown in FIG. 2 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of the environment 200 may perform one or more functions described as being performed by another set of devices of the environment 200.

FIG. 3 is a diagram of example components of one or more devices of FIG. 2. The example components may be included in a device 300, which may correspond to the management system 201, the network device 230, the endpoint device 240, and/or the data structure 250. In some implementations, the management system 201, the network device 230, the endpoint device 240, and/or the data structure 250 may include one or more devices 300 and/or one or more components of the device 300. As shown in FIG. 3, the device 300 may include a bus 310, a processor 320, a memory 330, an input component 340, an output component 350, and a communication interface 360.

The bus 310 includes one or more components that enable wired and/or wireless communication among the components of the device 300. The bus 310 may couple together two or more components of FIG. 3, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling. The processor 320 includes a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a controller, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and/or another type of processing component. The processor 320 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the processor 320 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

The memory 330 includes volatile and/or nonvolatile memory. For example, the memory 330 may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory). The memory 330 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection). The memory 330 may be a non-transitory computer-readable medium. The memory 330 stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of the device 300. In some implementations, the memory 330 includes one or more memories that are coupled to one or more processors (e.g., the processor 320), such as via the bus 310.

The input component 340 enables the device 300 to receive input, such as user input and/or sensed input. For example, the input component 340 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator. The output component 350 enables the device 300 to provide output, such as via a display, a speaker, and/or a light-emitting diode. The communication interface 360 enables the device 300 to communicate with other devices via a wired connection and/or a wireless connection. For example, the communication interface 360 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

The device 300 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., the memory 330) may store a set of instructions (e.g., one or more instructions or code) for execution by the processor 320. The processor 320 may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions, by one or more processors 320, causes the one or more processors 320 and/or the device 300 to perform one or more operations or processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more operations or processes described herein. Additionally, or alternatively, the processor 320 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 3 are provided as an example. The device 300 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 3. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 300 may perform one or more functions described as being performed by another set of components of the device 300.

FIG. 4 is a diagram of example components of one or more devices of FIG. 2. The example components may be included in a device 400. The device 400 may correspond to the network device 230. In some implementations, the network device 230 may include one or more devices 400 and/or one or more components of the device 400. As shown in FIG. 4, the device 400 may include one or more input components 410-1 through 410-B (B≥1) (hereinafter referred to collectively as input components 410, and individually as input component 410), a switching component 420, one or more output components 430-1 through 430-C (C≥1) (hereinafter referred to collectively as output components 430, and individually as output component 430), and a controller 440.

The input component 410 may be one or more points of attachment for physical links and may be one or more points of entry for incoming traffic, such as packets. The input component 410 may process incoming traffic, such as by performing data link layer encapsulation or decapsulation. In some implementations, the input component 410 may transmit and/or receive packets. In some implementations, the input component 410 may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memories, and/or input queues. In some implementations, the device 400 may include one or more input components 410.

The switching component 420 may interconnect the input components 410 with the output components 430. In some implementations, the switching component 420 may be implemented via one or more crossbars, via busses, and/or with shared memories. The shared memories may act as temporary buffers to store packets from the input components 410 before the packets are eventually scheduled for delivery to the output components 430. In some implementations, the switching component 420 may enable the input components 410, the output components 430, and/or the controller 440 to communicate with one another.

The output component 430 may store packets and may schedule packets for transmission on output physical links. The output component 430 may support data link layer encapsulation or decapsulation, and/or a variety of higher-level protocols. In some implementations, the output component 430 may transmit packets and/or receive packets. In some implementations, the output component 430 may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and/or output queues. In some implementations, the device 400 may include one or more output components 430. In some implementations, the input component 410 and the output component 430 may be implemented by the same set of components (e.g., and input/output component may be a combination of the input component 410 and the output component 430).

The controller 440 includes a processor in the form of, for example, a CPU, a GPU, an APU, a microprocessor, a microcontroller, a DSP, an FPGA, an ASIC, and/or another type of processor. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the controller 440 may include one or more processors that can be programmed to perform a function.

In some implementations, the controller 440 may include a RAM, a ROM, and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by the controller 440.

In some implementations, the controller 440 may communicate with other devices, networks, and/or systems connected to the device 400 to exchange information regarding network topology. The controller 440 may create routing tables based on the network topology information, may create forwarding tables based on the routing tables, and may forward the forwarding tables to the input components 410 and/or output components 430. The input components 410 and/or the output components 430 may use the forwarding tables to perform route lookups for incoming and/or outgoing packets.

The controller 440 may perform one or more processes described herein. The controller 440 may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

Software instructions may be read into a memory and/or storage component associated with the controller 440 from another computer-readable medium or from another device via a communication interface. When executed, software instructions stored in a memory and/or storage component associated with the controller 440 may cause the controller 440 to perform one or more processes described herein. Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

The number and arrangement of components shown in FIG. 4 are provided as an example. In practice, the device 400 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 4. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 400 may perform one or more functions described as being performed by another set of components of the device 400.

FIG. 5 is a flowchart of an example process 500 for handling inconsistencies between service provisioning by network devices. In some implementations, one or more process blocks of FIG. 5 may be performed by a device (e.g., the management system 201). In some implementations, one or more process blocks of FIG. 5 may be performed by another device or a group of devices separate from or including the device, such as an endpoint device (e.g., the endpoint device 240) and/or a network device (e.g., the network device 230). Additionally, or alternatively, one or more process blocks of FIG. 5 may be performed by one or more components of the device 300, such as the processor 320, the memory 330, the input component 340, the output component 350, and/or the communication interface 360. Additionally, or alternatively, one or more process blocks of FIG. 5 may be performed by one or more components of the device 400, such as the input component 410, the switching component 420, the output component 430, and/or the controller 440.

As shown in FIG. 5, process 500 may include receiving a request for one or more service requirements (block 505). For example, the device may receive a request for one or more service requirements, as described above.

As further shown in FIG. 5, process 500 may include determining one or more network devices, associated with a network, that satisfy the one or more service requirements (block 510). For example, the device may determine one or more network devices, associated with a network, that satisfy the one or more service requirements, as described above.

As further shown in FIG. 5, process 500 may include identifying an unreachable network device from the one or more network devices determined to satisfy the one or more service requirements (block 515). For example, the device may identify an unreachable network device from the one or more network devices determined to satisfy the one or more service requirements, as described above. In some implementations, the unreachable network device is unreachable due to one of being removed from the network, a power failure, or a network error. In some implementations, the unreachable network device is a network device or a virtual network device.