Justin & Brad,
As part of the docker registry work I have the following setup:
±------------------+ ±------------------+
···
+--------------------+
> https://katello | <---> | https://capsule | <---> | https://registry
>
+-------------------+ +-------------------+
+--------------------+
From a system that can see the capsule, I would like to run:
% hammer repository synchronize
–server https://capsule
–name docker-repository
–source-url https://registry
This would initiate a sync from registry through the capsule to katello.
In addition, I’d like sync plans on the repo to know that the source-url is
through the capsule.
As a user, I want to sync content to katello that is visible only to the
capsule.
How do I accomplish this?
> Justin & Brad,
> As part of the docker registry work I have the following setup:
>
>
> ±------------------+ ±------------------+ ±-------------------+
> > https://katello | <—> | https://capsule | <—> | https://registry |
> ±------------------+ ±------------------+ ±-------------------+
>
> From a system that can see the capsule, I would like to run:
>
> % hammer repository synchronize
> --server https://capsule
> --name docker-repository
> --source-url https://registry
>
> This would initiate a sync from registry through the capsule to katello.
>
> In addition, I'd like sync plans on the repo to know that the
> source-url is through the capsule.
>
> As a user, I want to sync content to katello that is visible only to
> the capsule.
>
> How do I accomplish this?
At first glance I can think of two options:
- Setup an HTTP proxy on the capsule that only the katello/foreman
server has access to. Configure the repo on the katello server to use
that for an http proxy
Using this method sync plans would work as is.
- Talk to the capsule and create a repository that syncs the registry
locally to the capsule, then have the satellite sync that repo from the
capsule.
Sync plans would NOT work with 2) as they exist today. You'd need some
sort of orchestrated action on both the capsule and the katello server.
···
On 08/05/2016 11:04 AM, Tom McKay wrote:
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev+unsubscribe@googlegroups.com
mailto:foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
