After EMCO has been installed in a central cluster and some 'edge' clusters have been prepared, this section describes the basic operational sequences that are used to onboard clusters and create and deploy composite applications.

EMCO API

Interaction with the EMCO REST API is primary interface to EMCO.

View the EMCO API documentation with the swagger editor:  https://editor.swagger.io/?url=https://raw.githubusercontent.com/onap/multicloud-k8s/master/docs/emco_apis.yaml

A Postman collection can be found here:  https://github.com/onap/multicloud-k8s/blob/master/docs/EMCO.postman_collection.json

The EMCO REST API is the foundation for the other interaction facilities like the EMCO CLI and EMCO GUI.

EMCO CLI

EMCO has a CLI tool called emcoctl.  More information can be found here: https://github.com/onap/multicloud-k8s/tree/master/src/tools/emcoctl

EMCO GUI

EMCO has a GUI - details:  TBD

EMCO Setup

The EMCO architecture is extensible via the use of controllers which can be used to handle specific placement and configuration (i.e. actions) operations.  The EMCO orchestrator communicates with these controllers via a gRPC interface.  EMCO supports a controller API to allow the administrator to register these controllers with EMCO to provide the necessary connection information (name, port) as well as controller type and relative priority.

The EMCO rsync microservice also exposes it's API via gRPC to the EMCO microservices.  So, while rsync is not a placement or action controller, it is also registered with the controller API so that EMCO microservices that interact with rsync as a gRPC client can obtain the gRPC connections details in the same manner as with other controllers.