In one embodiment, a system for managing a virtualization environment includes a set of host machines, each of which includes a hypervisor, virtual machines, and a virtual machine controller, and a data migration system configured to identify one or more existing storage items stored at one or more existing File Server Virtual Machines (FSVMs) of an existing virtualized file server (VFS). For each of the existing storage items, the data migration system is configured to identify a new FSVMs of a new VFS based on the existing FSVM, send a representation of the storage item from the existing FSVM to the new FSVM, such that representations of storage items are sent between different pairs of FSVMs in parallel, and store a new storage item at the new FSVM, such that the new storage item is based on the representation of the existing storage item received by the new FSVM.

A discovery computing system may receive an account identifier (ID) and a set of credentials required to access a first service account. The discovery computing system may transmit a first API query to a remote computing system. The discovery computing system may receive an organization identifier (ID) of the organization from the remote computing system. The discovery computing system may further transmit a second API query to the remote computing system. The discovery computing system may be further configured to receive information about a set of projects, in the organization, from the remote computing system. The discovery computing system may further generate a set of service accounts and further determine the set of resources, in the remote computing system, associated with each of the generated set of service accounts. The discovery computing system may further store the determined set of resources, as configuration items in a persistent storage.

A discovery computing system may receive an account identifier (ID) and a set of credentials required to access a first service account. The discovery computing system may transmit a first API query to a remote computing system. The discovery computing system may receive an organization identifier (ID) of the organization from the remote computing system. The discovery computing system may further transmit a second API query to the remote computing system. The discovery computing system may be further configured to receive information about a set of projects, in the organization, from the remote computing system. The discovery computing system may further generate a set of service accounts and further determine the set of resources, in the remote computing system, associated with each of the generated set of service accounts. The discovery computing system may further store the determined set of resources, as configuration items in a persistent storage.

In one embodiment, a system for managing communication connections in a virtualization environment includes a plurality of host machines implementing a virtualization environment, wherein each of the host machines includes a hypervisor, at least one user virtual machine (user VM), and a distributed file server that includes file server virtual machines (FSVMs) and associated local storage devices. Each FSVM and associated local storage device are local to a corresponding one of the host machines, and the FSVMs conduct I/O transactions with their associated local storage devices based on I/O requests received from the user VMs. Each of the user VMs on each host machine sends each of its respective I/O requests to an FSVM that is selected by one or more of the FSVMs for each I/O request based on a lookup table that maps a storage item referenced by the I/O request to the selected one of the FSVMs.

A persistent version-controlled is provided the enables automated configuration of VNFs/CNFs following deployment or re-deployment of VNF/CNF instances throughout the life cycle of the VNFs/CNFs. Immutable copies of NF configurations for a VNF/CNF are stored in the version controlled data storage 100. Multiple versions of a NF configuration can be associated with a common configuration reference (e.g., URL). Metadata associated with the different versions of a NF configuration indicates which of two or more different versions is the current version. The collection of different versions of a NF configuration associated with the same stable reference provide a complete history of the NF configuration, thus allowing rollback to any previous version of the NF configuration by simply modifying the metadata to mark that version as the current version. If a VNF/CNF needs to be re-deployed, the same configuration reference used during the initial deployment is used to download the most recent version of the NF configuration based on the metadata.

A persistent version-controlled is provided the enables automated configuration of VNFs/CNFs following deployment or re-deployment of VNF/CNF instances throughout the life cycle of the VNFs/CNFs. Immutable copies of NF configurations for a VNF/CNF are stored in the version controlled data storage 100. Multiple versions of a NF configuration can be associated with a common configuration reference (e.g., URL). Metadata associated with the different versions of a NF configuration indicates which of two or more different versions is the current version. The collection of different versions of a NF configuration associated with the same stable reference provide a complete history of the NF configuration, thus allowing rollback to any previous version of the NF configuration by simply modifying the metadata to mark that version as the current version. If a VNF/CNF needs to be re-deployed, the same configuration reference used during the initial deployment is used to download the most recent version of the NF configuration based on the metadata.

Systems and methods are disclosed for updating network configuration documentation. In an example, a user can upload network configuration documentation with updates to a network to a server. The server can create an update topology corresponding to the documentation by identifying symbols that represent network components. The server can identify changes by comparing the update topology to a configuration data of an existing network. For example, the address of a gateway or the connections to the gateway can change. The server can cause the changes to be presented to a user, such as by highlighting the changes in a diagram. The user can confirm the changes, such as with a conversational workflow, and the server can save the changes to a database. The system can also send commands to the applicable network components to effectuate the confirmed changes.

Systems and methods are disclosed for updating network configuration documentation. In an example, a user can upload network configuration documentation with updates to a network to a server. The server can create an update topology corresponding to the documentation by identifying symbols that represent network components. The server can identify changes by comparing the update topology to a configuration data of an existing network. For example, the address of a gateway or the connections to the gateway can change. The server can cause the changes to be presented to a user, such as by highlighting the changes in a diagram. The user can confirm the changes, such as with a conversational workflow, and the server can save the changes to a database. The system can also send commands to the applicable network components to effectuate the confirmed changes.

A faulty node is identified in a cloud native environment by retrieving a topology that describes a relationship between a plurality of nodes in a network, retrieving a list of alarms in the network, determining a child node in the network located at the bottom of the topology that has a first alarm based on the alarm list, determining a parent node of the child node located above the child node and below or on an apex node of the network that has a second alarm based on the topology, determining whether the parent node is an apex node in the network based on the topology, and based on a determination that the parent node is the apex node in the network, identify the parent node as the faulty node.

A faulty node is identified in a cloud native environment by retrieving a topology that describes a relationship between a plurality of nodes in a network, retrieving a list of alarms in the network, determining a child node in the network located at the bottom of the topology that has a first alarm based on the alarm list, determining a parent node of the child node located above the child node and below or on an apex node of the network that has a second alarm based on the topology, determining whether the parent node is an apex node in the network based on the topology, and based on a determination that the parent node is the apex node in the network, identify the parent node as the faulty node.