Installing Cached Version

There is an Ansible installer option allowing you to install CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. using a cached version of the required Red Hat Package Manager. This allows for a deployment to happen without ever needing to contact external systems and go outside the network In the context of CMP, the infrastructure on which usage of registered customers will be measured – this could be a mobile phone network, broadband network or other non-telecommunications network..

This is facilitated by splitting the deployment into two parts, pre-deploy.yaml which is run before an installation, and deploy.yaml for the system install. The pre-deploy.yaml must always be executed before a full installation using the deploy.yaml, as it is required to pre-configure certain aspects of the system and run various validations of the overall system readiness for a deployment to take place.

The pre-deploy.yaml can be executed at any time before the deploy.yaml is run, meaning it could be executed multiple times, hours or even days before a full deployment is performed.

When the pre-deploy is executed, based on the option selected from within the Inventory Configuration Tool - CMP Repository Source, if this set to Cached it will configure an Apache HTTP Web Server and sync down all required external repositories onto a locally configured system. The first time this is run can take some time as it syncs everything down, but subsequent executions will only sync any changes and run much quicker. The main deploy will then install the required rpms from this local location instead of making calls to external repositories. The main advantage of this is to prevent installer failures due to unknown external influences when repositories can’t be reached or other external network related connectivity issues.

If the option selected from within the Inventory Configuration Tool - CMP Repository Source is set to From Source, then the installation will continue to install components from the external repositories as previously.

For the hosting of the internal cached repositories, we recommend using the Ansible controller node as this will already be present and negates the need for setting up another additional box. However, there is the option to use any system you choose.

To host these cached repositories, it will require additional disk space on the chosen box, approximate sizes for the repositories are 70GB for Rocky Linux A well-known widely used open source operating system. and 220GB for RedHat on the initial setup. These will grow over time, so allow for this in your configuration.