Make juju installation optional in community installer

Proposers

• Gerardo García (Telefónica)
• Francisco Javier Ramón (Telefónica)
• Francisco Rodríguez (Indra)

Description

Upon discontinuation of Juju support in future releases, this feature will make the installation of Juju controller and its dependencies optional in the community installer. As a result, Juju-based EE and Juju-based KDU will be available only if the juju controller was installed. The implementation should guarantee that the NS instantiation fails with a proper message when there is no Juju controller.

Since the default option for the community installer will be to install OSM without Juju, it is possible that some E2E Robot tests might have to be adapted or re-tagged, for instance to remove the sanity tag from tests using Juju-based EE and Juju-based KDU in master.

Demo or definition of done

Two Robot tests will be created or updated to assert the failure of a NS with Juju-based EE, and to assert the failure of a NS with a Juju-based KDU.