Abstract: In one embodiment, configuration information for a microservices application is obtained, the microservices application comprising a plurality of microservice containers, and the configuration information comprising version information for each of the plurality of microservice containers. A graphical representation of the microservices application is displayed, wherein the graphical representation of the microservices application comprises a representation of each of the plurality of microservice containers. It is determined, based on the version information, whether each of the plurality of microservice containers is updated or outdated. A graphical indication of an updated microservice container is displayed; a graphical indication of an outdated microservice container is displayed; and a graphical indication of an extent to which the outdated microservice container is out-of-date is displayed.

Abstract: A particular software container hosting a particular microservice is identified that is to implement at least a portion of a software program. A set of other containers hosting other microservices are determined to be interoperable with the particular microservice and an affinity value corresponding to the particular container is determined for each other container in the set, each of the affinity values representing a respective degree of correspondence between the particular container and the corresponding other container. A listing of at least a subset of the set of other containers are presented together with an indication of the corresponding affinity value of each of the subset of other containers.

Abstract: In one embodiment, a microservice container of a microservices application may be launched. The runtime environment of the microservices application may be monitored to identify one or more microservice resources to configure for the microservices application. A microservice resource to configure for the microservices application may be identified based on the runtime environment of the microservices application, and the microservice resource may be configured based on the runtime environment of the microservices application. In some embodiments, one or more additional microservice resources may be configured until determining, based on the runtime environment of the microservices application, that configuration of the microservices application is complete.

Abstract: In one embodiment, configuration information for a microservices application is obtained, the microservices application comprising a plurality of microservice containers, and the configuration information comprising version information for each of the plurality of microservice containers. A graphical representation of the microservices application is displayed, wherein the graphical representation of the microservices application comprises a representation of each of the plurality of microservice containers. It is determined, based on the version information, whether each of the plurality of microservice containers is updated or outdated. A graphical indication of an updated microservice container is displayed; a graphical indication of an outdated microservice container is displayed; and a graphical indication of an extent to which the outdated microservice container is out-of-date is displayed.

Abstract: Systems and methods include receiving notification of an anomaly in a particular component within a data center environment. Such systems and methods include receiving configuration information identifying positions of tags disposed proximate to and representing respective infrastructure components within the data center environment. Such systems and methods include detecting a first tag representing a first infrastructure component and, in response thereto, determining, using the configuration information, a first positional relationship between the first tag and a second tag representing the particular component. Such systems and methods include determining a second positional relationship between the mobile device and the particular component based on the first positional relationship and providing, based on the second positional relationship, directional guidance from the first infrastructure component to the particular component.

Abstract: Systems and methods include receiving notification of an anomaly in a particular component within a data center environment. Such systems and methods include receiving configuration information identifying positions of tags disposed proximate to and representing respective infrastructure components within the data center environment. Such systems and methods include detecting a first tag representing a first infrastructure component and, in response thereto, determining, using the configuration information, a first positional relationship between the first tag and a second tag representing the particular component. Such systems and methods include determining a second positional relationship between the mobile device and the particular component based on the first positional relationship and providing, based on the second positional relationship, directional guidance from the first infrastructure component to the particular component.