Data-powered shipwright for network cloud maintenance
A system comprising a network cloud configured for a point of deployment containerized environment, a plurality of servers in communication with the network cloud, configured to establishing a point of deployment (POD) in one of the plurality of servers, receiving a determination that the POD is not operational, mapping the topology of the POD, and based on the mapping step, troubleshooting the POD in accordance with a set of rules.
1. A system, comprising:
a network cloud that is configured for a point of deployment (POD) containerized environment;
a plurality of servers in communication with the network cloud;
an input-output interface;
a processor coupled to the input-output interface wherein the processor is further coupled to a memory, the memory having stored thereon executable instructions that when executed by the processor cause the processor to effectuate operations comprising:
mapping a topology of connections to and from a POD that is not operational;
based on the mapping, testing the connections of the POD;
responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection;
responsive to a second determination of failing to automatically repair the connection, generating a trouble ticket; and
responsive to a third determination of no failure of the connections of the POD, troubleshooting a configuration of the POD in accordance with a set of rules.
2. The system of claim 1 , wherein the network cloud is configured in one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration.
3. The system of claim 1 , wherein the operations further comprise correcting errors in the configuration of the POD based on the troubleshooting.
4. The system of claim 3 , wherein the set of rules comprises verifying the operations of one of a platform, a VM status, a proxy service, and a performance.
5. The system of claim 1 , wherein the POD is a network POD.
6. The system of claim 1 , wherein the POD is a compute POD.
7. The system of claim 6 , wherein the troubleshooting further comprises testing a Kubernetes configuration and an OpenStack configuration.
8. The system of claim 7 , wherein the operations further comprise receiving a physical alarm and a virtual alarm and correlating the virtual alarm to the physical alarm.
9. The system of claim 8 , wherein the operations further comprise verifying link aggregation interfaces and issuing an alert of P-function/access network failure responsive to verifying the link aggregation interfaces.
10. The system of claim 9 , wherein correlating the virtual alarm to the physical alarm comprises correlating a compute node alarm to a C_Leaf alarm, the C_Leaf alarm to OAM switches, the C_Leaf alarm to a R_Leaf alarm, the C_Leaf alarm to a Spine, the C_Leaf alarm to an AGC_Leaf, the AGC_Leaf to network side management switches, the network side management switches to a terminal server, or a combination thereof.
11. A method comprising:
mapping, by a processing system comprising a processor, a topology of connections of a point of deployment (POD) that is not operational in one of a plurality of servers;
based on the mapping, testing, by the processing system, the connections of the POD;
responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection by the processing system;
responsive to a second determination of failing to automatically repair the connection, generating, by the processing system, a trouble ticket and
responsive to a third determination of no failure of the connections of the POD, troubleshooting, by the processing system, a configuration of the POD in accordance with a set of rules.
12. The method of claim 11 , further comprising verifying link aggregate interfaces.
13. The method of claim 11 , wherein the configuration is one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration.
14. The method of claim 11 , further comprising correcting errors in the POD based on the troubleshooting.
15. The method of claim 11 , further comprising correlating virtual alarms to physical alarms.
16. A non-transitory, machine-readable medium, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations, comprising:
mapping a topology of connections of a point of deployment (POD) that is not operational;
based on the mapping, testing the connections of the POD;
responsive to a first determination of a failure of a connection of the POD, automatically repairing the connection;
responsive to a second determination of failing to automatically repair the connection, generating a trouble ticket; and
responsive to a third determination of no failure of the connections of the POD, troubleshooting a configuration of the POD in accordance with a set of rules.
17. The non-transitory, machine-readable medium of claim 16 , wherein the operations further comprise issuing an alert of P-function/access network failure responsive to verifying all link aggregation interfaces.
18. The non-transitory, machine-readable medium of claim 16 , wherein the configuration is one of a proxy configuration, a Kubernetics configuration, or an OpenStack configuration.
19. The non-transitory, machine-readable medium of claim 16 , wherein the operations further comprise correcting errors in the POD based on the troubleshooting.
20. The non-transitory, machine-readable medium of claim 16 , wherein the operations further comprise correlating virtual alarms to physical alarms.