How to use just the repositories of a Satellite

Latest response

I would like to be able to let subscribed Satellite clients to just/only use its repositories as is, without having to publish the content views as often as a repositor sync occur.

I mean: publishing a new version of a content view and removing the previous version can not easily be scripted with hammer.

(Satellite 6 @ RHEL7Server)

Responses

Hi,

You can do that without using content view. If you are using Activation Keys to register a client just select the Subscriptions that you want to use under the Subscription tab. The same can be done by editing the host. If you are willing to use the Life Cycle Management feature provided by Satellite 6 you can do that using Content View & Content View Filter.

- Swapnil

So I can create an Activation Key without Life Cycle details? Or do I have to select the 'Default Organization View'? So the 'Default Organization View' does not contain any Content View?

I now have an Activication Key with these details:

Lifecycle Environment: Library
Content View:          Default Organization View

Seems I cannot get rid of that 'Library' thing, and I cannot find any documentation on 'Default Organization View' but this seems right nevertheless.

But,

hammer activation-key product-content --id 8 --organization XXXX

will list all repositories, but not if they are enable/disabled for this key.

I think what your are looking for is exactly what the "Orgnaization Default View" does - basically, systems subscribed to the Org. Default View will behave exactly like a system on Satellite 5.x with a "Red Hat base channel" (not cloned) or subscribed directly to redhat.com - they will see all current patches & updates, as often as the repository is sync'ed (daily, on my satellite servers).

The "Library" Lifecycle Environment is also a default (the ODV has no other environments, but Pulp seems to be incapable of functioning without having that variable filled in, so it has to be there).

I do wish Red Hat would document things like the ODV a little better (or at all). It performs a necessary function for me (supporting system that do not need and do not want full ITIL methodologies enforced), but all I know about it is based on empirical evidence; since it isn't documented, I don't know if Red Hat intends to keep supporting it, or if I am using it in an intended/supported way.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.