Day-2 primitives for CNF with proxy charms
Day-2 primitives for CNF with proxy charms
Proposers
- Gerardo García (Telefónica)
- Francisco Javier Ramón Salguero (Telefónica)
- David García (Canonical)
Target MDG/TF
IM, N2VC, LCM
Description
Currently it is not possible to run day-2 primitives with proxy charms over CNF. A CNF might have some configuration services for one or several of its KDUs, exposed via Kubernetes services.
This feature aims at providing the required changes to allow that those configuration services are reachable from the proxy charm, so that the IP address and port exposed by the service, together with potentially other information, reach the proxy charm. In that way, the proxy charm will have enough information to run configuration primitives over that CNF.
The specific mechanism to configure the CNF is out of the scope, and it is assumed that the proxy charm knows the protocol and how to talk to the CNF via the configuration service.
Demo or definition of done
A new package with a KDU will be created or an existing package with a KDU
(e.g. openldap_knf
) will be updated to include a proxy charm that performs
at least one day-2 primitive. The robot test using that package (e.g. K8s04)
will be updated to perform that day-2 primitive and check that it is working.
The feature will be considered done when the new/updated test is passed.