Candlepin uses Subscriptions to provide access to content. The system for getting access to content via these subscriptions is described below.

Products

Engineering Products

  • The low level products which provide actual content repos.
  • Always have numeric IDs. Content is packed into an entitlement cert as an OID which must be numeric.
  • These can appear as “installed” product certs on a system in /etc/pki/product. (aka installed products)
  • Does not normally carry product attributes, or rather Candlepin does not check their attributes.

Marketing Products

  • The top level product associated to a subscription. (each subscription has only one)
  • Carries all the attributes which control the business logic in Candlepin with regard to how that subscription can be used, and what will happen when it is.
  • Generally has an alpha-numeric ID.
  • Carries no content.
  • Will never appear as an installed/engineering product.

Subscriptions

  • Generally represents what a customer has purchased.
  • In the case of an on-site server which has created a distributor in the customer portal, assigned it entitlements, and exported/imported a manifest, one Subscription object will be created per entitlement given to the distributor. (even if they originate from the same pool/subscription)
  • Maps to one marketing product which defines all the business logic.
  • Provides potentially many engineering products for the content this subscription grants access too.
  • The subscription may live in a foreign system accessed through an adapter. (hosted) We also provide a default adapter which allows them to be stored in Candlepin itself.

Pools

  • In many ways, this is almost a copy of the Subscription, but they can differ slightly in some situations.
    • Multipliers may cause the quantity of the subscription to be multiplied on the pool.
    • Some subscription marketing products carry attributes that tell Candlepin to create multiple.
    • Some pools are created as a result of a bind/attach/entitlement, these are commonly called sub-pools or derived pools.
  • Stores a copy of all the provided products from the subscription. (both for speed and for detecting when something changed)
  • Stores a copy of all the attributes from the marketing product. (both for speed and for detecting when something changed)

Types of Pools

When a subscription object is imported, depending on the attributes of its main marketing product, one or more pools will be created.

  1. Master Pool
    • At least one pool will always be created for any subscription and this can be considered the parent or “main” pool.
  2. Derived Pool
    • Created as the result of an entitlement to a pool with a virt_limit attribute.
    • If the pool has a stacking_id, see Stack Derived Pool below.
    • When a host system binds to a pool with virt_limit, a derived pool is created for guests on that host.
    • Derived pool will have a pool attribute: requires_host = candlepin host consumer UUID
    • Access to this pool will be restricted to guests who have been reported as running on that host by virt-who.
  3. Stack Derived Pool
    • Similar to a Derived Pool, except that, when stacked, only one sub-pool will ever exist for that stack for a given consumer.
    • The pool is created when a host binds to the first virt limited pool with a given stack ID.
    • On subsequent binds to pools with that same stack ID (does not have to be virt limited), the stack derived pool is updated to have merged characteristics of all the pools in the stack.
      • Because of this, a stack derived pool can not have a single source subscription or source entitlement (null in DB/JSON).
    • Each stack derived pool is linked back to the source consumer and stack by means of a SourceStack
    • The entitlements that are contributing to the stack derived pool are associated with the source consumer.
    • As entitlements of a stack are consumed by the host, the stack derived pool is updated as follows:
      • The pool’s product (marketing) will be taken from the eldest entitlement (determined by entitlement creation date) in the stack (prefer the derived product, if set).
      • The pool’s provided products (engineering) are accumulated from all entitlements of the stack. If an entitlement has a derived product, the derived provided products defined for that entitlement are added instead of the provided products.
      • The contract, account and order numbers will be taken from the eldest entitlement (determined by entitlement creation date) in the stack.
      • The quantity will be updated from the eldest virt limited entitlement (determined by entitlement creation date). If the last entitlement remaining in the stack is NOT virt limited, the quantity remains as it is currently set.
      • The start/end date of the pool will be set based on all entitlements in the stack (earliest entitlement start date, latest entitlement end date).
    • A stack derived pool is only removed when all of the entitlements for its stack are removed from the source consumer (even if there are no virt limited entitlements remaining).
  4. Unmapped Guest Pool
    • To help customers struggling with timing issues between when a guest is created and tries to subscribe, and when virt-who reports the host to guest mapping (unlocking the pools for that guest), unmapped guest pools were added.
    • These pools are only usable by guest consumers who are less than 24 hours old, and who have not yet been linked to any host.
    • Entitlements will only be valid for 24h.
    • As soon as virt-who reports the host guest mapping any entitlements to unmapped guest pools are revoked.
    • An auto-bind is then performed on the guest, which includes attempting to attach any pools to the host which will unlock derived sub-pools for something the guest needs.
  5. Virt Bonus Pool
    • A legacy type of subscription which can exist only in hosted and is no longer used on new SKUs.
    • Triggered in hosted when marketing SKU specifies a virt_limit attribute but does not have host_limited = true.
    • Pool is created during refresh pools when subscription is first seen, as opposed to as the result of an entitlement as most other derived pools are.

Derived Products

Pools can also carry a “derived” product and provided products. This accomodates scenarios where the host is intended to get access to different (or no) content than the guests. The parent or master pool will use the normal product and provided products on the subscription. However any derived or unmapped guest pools will flip to use the derived product and provided products instead of the normal set.

Entitlements

  • Represents the consumption of a Pool for a given consumer.
  • Can have a quantity, a consumer system may require a greater quantity than just 1.
  • Carries the certificate sent to clients. Grants access to all of the provided products from the pool, and thus is used to authenticate when actually fetching content.
  • Can be revoked, returning the used quantity back to the pool.

Auto-attach

  • A major part of Candlepin is the auto-attach routine on the server which attempts to find the best fit of available subscriptions to cover the consumer’s installed products, and hardware requirements.
  • Subscriptions will frequently provide access to more product IDs than those which are installed. We’re simply looking for coverage, i.e. a combination of subscriptions which covers everything installed (if possible).
  • Rules are quite complex and there are a number of criteria considered to use one combination over another.
  • By default runs daily for each system to try to repair anything that is amiss. (aka healing)
  • Auto-attach run on a guest will automatically attempt to assign subscriptions to the host which would unlock virt_only (derived) pools for something the guest needs.

Manual Attach

  • Subscriptions can also be consumed manually, even if no engineering product cert is installed on the system.
    • This entitlement still counts as in use, so the quantity is debited from the pool, and the attributes on the marketing product are still enforced.
    • Sometimes the product cert will appear on the system after packages are installed, but this is not guaranteed, and it’s best to consider that the subscription is in use at attach time, not at yum install time.

Exporting Subscriptions to a Downstream Candlepin Server

Candlepin has been designed to allow for exporting subscriptions from a master/upstream Candlepin server for use in a standlone on-premises environment. (i.e. Katello, Satellite, SAM) This process involves a number of steps:

  1. A “distributor” consumer is created in the upstream candlepin server by some UI. (also sometimes referred to as a “Subscription Management Application”)
  2. A user assigns entitlements to the distributor consumer for export in whatever quantities they wish to use downstream. Once assigned those are marked as consumed in the upstream server.
  3. The user can then generate a manifest, which is a signed zip file containing the relevant subscription and product information to enable authorized access to the content on the downstream server.
  4. A manifest can then be imported on the downstream server.
    • Each entitlement in the manifest becomes a downstream Subscription, thus feeding into the exact same Subscription -> Pool -> Entitlement data model outlined above.
  5. When an updated manifest is generated and imported, Candlepin will synchronize the existing Pools to match the incoming manifest, revoking entitlements and creating new pools as necessary.

Some on-premises solutions support automatic updating of the manifest, where if possible the Satellite/SAM server will periodically call back to their upstream server and attempt to update the manifest if anything has changed.

Last modified on 3 August 2017