Operations

The server has both a web interface and api endpoints. It is reasonably straightforward to set up the necessary data to maintain subscription-manager infrastructure.

Subscription Manager

This is all about Products, Entitlements, Content, Activation Keys, Owners and Consumers.

In the first place; you need to have RPM repositories; and they should be configured against the node hosting the server.

These repositories are set up as Content. Each Product is associated with a RPM package in your repository, and Content(s). This also needs a specially crafted X509 certificate which will be deployed/baked into the client node. The application has an action and api for this.

You may set up Entitlements, with or without ActivationKeys. How you utilise :code:subscription-manager on the client will determine how Consumers consume the Entitlements.

The Subscriptions tab is to manage all of the consumption activity of Consumers, Owners et al.

Cloud Vendors

This is the Provider, Listing, Release, Offer side of the application. Since baking the above software update mechanism into cloud images is core; this is the complementary management platform.

We have a sophisticated build pipeline based around this infrastructure.