I have a Katello server (the 'primary') which synchronises with public
repositories. I want to build and maintain another Katello server (the
'secondary') on another network which cannot see the internet or the
primary; I want the primary to be the source for secondary. The secondary
needs to be a full-featured Katello instance.
My goals are thus:
Build of the secondary (the primary has the repos).
Populate and maintain the repos of the secondary.
katello-disconnected[1] looks to mess with my working primary instance (is
a synchronisation host a different beast?) and appears geared towards RHEL
(needing a manifest file). Should I just tarball the published (via http)
content from the primary, unpack it to a webserver that the secondary can
see and synchronise with that?
···
On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
>
> I have a Katello server (the 'primary') which synchronises with public
> repositories. I want to build and maintain another Katello server (the
> 'secondary') on another network which cannot see the internet or the
> primary; I want the primary to be the source for secondary. The secondary
> needs to be a full-featured Katello instance.
>
> My goals are thus:
>
> 1. Build of the secondary (the primary has the repos).
> 2. Populate and maintain the repos of the secondary.
>
> katello-disconnected[1] looks to mess with my working primary instance (is
> a synchronisation host a different beast?) and appears geared towards RHEL
> (needing a manifest file). Should I just tarball the published (via http)
> content from the primary, unpack it to a webserver that the secondary can
> see and synchronise with that?
>
> Many thanks.
>
> 1. http://www.katello.org/docs/2.3/user_guide/disconnected/index.html
>
>
On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
I have a Katello server (the ‘primary’) which synchronises with public
repositories. I want to build and maintain another Katello server (the
’secondary’) on another network which cannot see the internet or the
primary; I want the primary to be the source for secondary. The secondary
needs to be a full-featured Katello instance.
My goals are thus:
Build of the secondary (the primary has the repos).
Populate and maintain the repos of the secondary.
katello-disconnected[1] looks to mess with my working primary instance
(is a synchronisation host a different beast?) and appears geared towards
RHEL (needing a manifest file). Should I just tarball the published (via
http) content from the primary, unpack it to a webserver that the secondary
can see and synchronise with that?
Oh, apologies, your Secondary is completely disconnected from the rest of
Katello? How do expect the systems to be synchronised then?
John
···
On Monday, 28 September 2015 14:06:50 UTC+1, JC wrote:
>
> Thanks for the reply John.
>
> I saw a capsule server as something that was dependent on the Katello
> server. That is, it needs network connectivity to the Katello server...
>
> On 28 September 2015 at 13:24, John Beranek - PA < > john.b...@pressassociation.com > wrote:
>
>> If I'm not mistaken, your described "Secondary" is a "Capsule" in Katello
>> terms:
>>
>> http://www.katello.org/docs/2.3/user_guide/capsules/index.html
>>
>> John
>>
>> On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
>>>
>>> I have a Katello server (the 'primary') which synchronises with public
>>> repositories. I want to build and maintain another Katello server (the
>>> 'secondary') on another network which cannot see the internet or the
>>> primary; I want the primary to be the source for secondary. The secondary
>>> needs to be a full-featured Katello instance.
>>>
>>> My goals are thus:
>>>
>>> 1. Build of the secondary (the primary has the repos).
>>> 2. Populate and maintain the repos of the secondary.
>>>
>>> katello-disconnected[1] looks to mess with my working primary instance
>>> (is a synchronisation host a different beast?) and appears geared towards
>>> RHEL (needing a manifest file). Should I just tarball the published (via
>>> http) content from the primary, unpack it to a webserver that the secondary
>>> can see and synchronise with that?
>>>
>>> Many thanks.
>>>
>>> 1. http://www.katello.org/docs/2.3/user_guide/disconnected/index.html
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
Well, yes, that's the bit I'm looking for help with.
katello-disconnected provides a mechanism to produce 'exports' which can be
moved by other media (hard disk, DVDs). That is workable, in principal,
but I'm looking for confirmation on the operation/suitability, and whether
other methods have been used by the community.
···
On 28 September 2015 at 14:39, John Beranek - PA < john.beranek@pressassociation.com> wrote:
Oh, apologies, your Secondary is completely disconnected from the rest of
Katello? How do expect the systems to be synchronised then?
John
On Monday, 28 September 2015 14:06:50 UTC+1, JC wrote:
Thanks for the reply John.
I saw a capsule server as something that was dependent on the Katello
server. That is, it needs network connectivity to the Katello server…
On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
I have a Katello server (the ‘primary’) which synchronises with public
repositories. I want to build and maintain another Katello server (the
’secondary’) on another network which cannot see the internet or the
primary; I want the primary to be the source for secondary. The secondary
needs to be a full-featured Katello instance.
My goals are thus:
Build of the secondary (the primary has the repos).
Populate and maintain the repos of the secondary.
katello-disconnected[1] looks to mess with my working primary instance
(is a synchronisation host a different beast?) and appears geared towards
RHEL (needing a manifest file). Should I just tarball the published (via
http) content from the primary, unpack it to a webserver that the secondary
can see and synchronise with that?
The disconnect mode of Katello is working as expected more if you want to
use for secure zone when no one can access the servers via internet or is
isolated totally from internet the only pain is create the iso and go to
the datacenter for upload but after that works like as expected without
issues
···
On Monday, September 28, 2015 at 11:46:03 PM UTC+10, JC wrote:
>
> Well, yes, that's the bit I'm looking for help with. ;-)
>
> katello-disconnected provides a mechanism to produce 'exports' which can
> be moved by other media (hard disk, DVDs). That is workable, in principal,
> but I'm looking for confirmation on the operation/suitability, and whether
> other methods have been used by the community.
>
> On 28 September 2015 at 14:39, John Beranek - PA < > john.b...@pressassociation.com > wrote:
>
>> Oh, apologies, your Secondary is completely disconnected from the rest of
>> Katello? How do expect the systems to be synchronised then?
>>
>> John
>>
>> On Monday, 28 September 2015 14:06:50 UTC+1, JC wrote:
>>>
>>> Thanks for the reply John.
>>>
>>> I saw a capsule server as something that was dependent on the Katello
>>> server. That is, it needs network connectivity to the Katello server...
>>>
>>> On 28 September 2015 at 13:24, John Beranek - PA < >>> john.b...@pressassociation.com> wrote:
>>>
>>>> If I'm not mistaken, your described "Secondary" is a "Capsule" in
>>>> Katello terms:
>>>>
>>>> http://www.katello.org/docs/2.3/user_guide/capsules/index.html
>>>>
>>>> John
>>>>
>>>> On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
>>>>>
>>>>> I have a Katello server (the 'primary') which synchronises with public
>>>>> repositories. I want to build and maintain another Katello server (the
>>>>> 'secondary') on another network which cannot see the internet or the
>>>>> primary; I want the primary to be the source for secondary. The secondary
>>>>> needs to be a full-featured Katello instance.
>>>>>
>>>>> My goals are thus:
>>>>>
>>>>> 1. Build of the secondary (the primary has the repos).
>>>>> 2. Populate and maintain the repos of the secondary.
>>>>>
>>>>> katello-disconnected[1] looks to mess with my working primary instance
>>>>> (is a synchronisation host a different beast?) and appears geared towards
>>>>> RHEL (needing a manifest file). Should I just tarball the published (via
>>>>> http) content from the primary, unpack it to a webserver that the secondary
>>>>> can see and synchronise with that?
>>>>>
>>>>> Many thanks.
>>>>>
>>>>> 1. http://www.katello.org/docs/2.3/user_guide/disconnected/index.html
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Foreman users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> foreman-user...@googlegroups.com.
>>>> To post to this group, send email to forema...@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> Hi JC
>
> The disconnect mode of Katello is working as expected more if you want
> to use for secure zone when no one can access the servers via internet
> or is isolated totally from internet the only pain is create the iso
> and go to the datacenter for upload but after that works like as
> expected without issues
Katello does not currently provide a good solution for this but this a
feature we are hoping to add soon and your feedback is good!
Are you interested in just syncing "Library" content, or also content
views? Are you interested in syncing entire Lifecycle Environments, or
just particular content views within particular Lifecycle environments?
We're looking to eventually provide both connected and disconnected
syncing between katello servers. Look for a design discussion to occur
soon on the foreman-dev mailing list in the next couple weeks.
I would not suggest looking into katello-disconnected as it generally
will not provide the functionality you want.
-Justin
···
On 10/11/2015 05:28 AM, Mario Gamboa wrote:
>
> On Monday, September 28, 2015 at 11:46:03 PM UTC+10, JC wrote:
>
> Well, yes, that's the bit I'm looking for help with. ;-)
>
> katello-disconnected provides a mechanism to produce 'exports'
> which can be moved by other media (hard disk, DVDs). That is
> workable, in principal, but I'm looking for confirmation on the
> operation/suitability, and whether other methods have been used by
> the community.
>
> On 28 September 2015 at 14:39, John Beranek - PA > <john.b...@pressassociation.com > wrote:
>
> Oh, apologies, your Secondary is completely disconnected from
> the rest of Katello? How do expect the systems to be
> synchronised then?
>
> John
>
> On Monday, 28 September 2015 14:06:50 UTC+1, JC wrote:
>
> Thanks for the reply John.
>
> I saw a capsule server as something that was dependent on
> the Katello server. That is, it needs network
> connectivity to the Katello server...
>
> On 28 September 2015 at 13:24, John Beranek - PA > wrote:
>
> If I'm not mistaken, your described "Secondary" is a
> "Capsule" in Katello terms:
>
> http://www.katello.org/docs/2.3/user_guide/capsules/index.html
>
>
> John
>
> On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
>
> I have a Katello server (the 'primary') which
> synchronises with public repositories. I want to
> build and maintain another Katello server (the
> 'secondary') on another network which cannot see
> the internet or the primary; I want the primary to
> be the source for secondary. The secondary needs
> to be a full-featured Katello instance.
>
> My goals are thus:
>
> 1. Build of the secondary (the primary has the repos).
> 2. Populate and maintain the repos of the secondary.
>
> katello-disconnected[1] looks to mess with my
> working primary instance (is a synchronisation
> host a different beast?) and appears geared
> towards RHEL (needing a manifest file). Should I
> just tarball the published (via http) content from
> the primary, unpack it to a webserver that the
> secondary can see and synchronise with that?
>
> Many thanks.
>
> 1.
> http://www.katello.org/docs/2.3/user_guide/disconnected/index.html
>
>
> --
> You received this message because you are subscribed
> to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe
> .
> To unsubscribe from this group and all its topics,
> send an email to foreman-user...@googlegroups.com.
> To post to this group, send email to
> forema...@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/foreman-users
> .
> For more options, visit
> https://groups.google.com/d/optout
> .
>
>
> --
> You received this message because you are subscribed to a
> topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an
> email to foreman-user...@googlegroups.com .
> To post to this group, send email to
> forema...@googlegroups.com .
> Visit this group at
> http://groups.google.com/group/foreman-users
> .
> For more options, visit https://groups.google.com/d/optout
> .
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-users+unsubscribe@googlegroups.com
> .
> To post to this group, send email to foreman-users@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Justin - yes, I really just want the library content (none of the fancy
stuff). It's great to hear this is an evolving area, because the method
I've outlined feels like a kludge. It would be super-nice if Katello could
remember (as a view?) what I last exported, so I can just grab the
differences the next time.
···
On 12 October 2015 at 09:48, Justin Sherrill wrote:
On 10/11/2015 05:28 AM, Mario Gamboa wrote:
Hi JC
The disconnect mode of Katello is working as expected more if you want to
use for secure zone when no one can access the servers via internet or is
isolated totally from internet the only pain is create the iso and go to
the datacenter for upload but after that works like as expected without
issues
Katello does not currently provide a good solution for this but this a
feature we are hoping to add soon and your feedback is good!
Are you interested in just syncing “Library” content, or also content
views? Are you interested in syncing entire Lifecycle Environments, or
just particular content views within particular Lifecycle environments?
We’re looking to eventually provide both connected and disconnected
syncing between katello servers. Look for a design discussion to occur
soon on the foreman-dev mailing list in the next couple weeks.
I would not suggest looking into katello-disconnected as it generally will
not provide the functionality you want.
-Justin
On Monday, September 28, 2015 at 11:46:03 PM UTC+10, JC wrote:
Well, yes, that’s the bit I’m looking for help with.
katello-disconnected provides a mechanism to produce ‘exports’ which can
be moved by other media (hard disk, DVDs). That is workable, in principal,
but I’m looking for confirmation on the operation/suitability, and whether
other methods have been used by the community.
On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
I have a Katello server (the ‘primary’) which synchronises with
public repositories. I want to build and maintain another Katello server
(the ‘secondary’) on another network which cannot see the internet or the
primary; I want the primary to be the source for secondary. The secondary
needs to be a full-featured Katello instance.
My goals are thus:
Build of the secondary (the primary has the repos).
Populate and maintain the repos of the secondary.
katello-disconnected[1] looks to mess with my working primary
instance (is a synchronisation host a different beast?) and appears geared
towards RHEL (needing a manifest file). Should I just tarball the
published (via http) content from the primary, unpack it to a webserver
that the secondary can see and synchronise with that?
i am too looking for sync facility so i can sync "Content Views" in
different life cycle environments from one DC to another DC.
it's good to have, individual repositories sync ( like we do sync for
Redhat repos ) from one satellite to another satellite.
is this discussion started yet?
Regards,
DJ
···
On Monday, 12 October 2015 19:49:27 UTC+5:30, JC wrote:
>
> Thanks for coming back to me Mario.
>
> Justin - yes, I really just want the library content (none of the fancy
> stuff). It's great to hear this is an evolving area, because the method
> I've outlined feels like a kludge. It would be super-nice if Katello could
> remember (as a view?) what I last exported, so I can just grab the
> differences the next time.
>
> On 12 October 2015 at 09:48, Justin Sherrill > wrote:
>
>> On 10/11/2015 05:28 AM, Mario Gamboa wrote:
>>
>> Hi JC
>>
>> The disconnect mode of Katello is working as expected more if you want to
>> use for secure zone when no one can access the servers via internet or is
>> isolated totally from internet the only pain is create the iso and go to
>> the datacenter for upload but after that works like as expected without
>> issues
>>
>>
>> Katello does not currently provide a good solution for this but this a
>> feature we are hoping to add soon and your feedback is good!
>>
>> Are you interested in just syncing "Library" content, or also content
>> views? Are you interested in syncing entire Lifecycle Environments, or
>> just particular content views within particular Lifecycle environments?
>>
>> We're looking to eventually provide both connected and disconnected
>> syncing between katello servers. Look for a design discussion to occur
>> soon on the foreman-dev mailing list in the next couple weeks.
>>
>> I would not suggest looking into katello-disconnected as it generally
>> will not provide the functionality you want.
>>
>> -Justin
>>
>>
>> On Monday, September 28, 2015 at 11:46:03 PM UTC+10, JC wrote:
>>>
>>> Well, yes, that's the bit I'm looking for help with. ;-)
>>>
>>> katello-disconnected provides a mechanism to produce 'exports' which can
>>> be moved by other media (hard disk, DVDs). That is workable, in principal,
>>> but I'm looking for confirmation on the operation/suitability, and whether
>>> other methods have been used by the community.
>>>
>>> On 28 September 2015 at 14:39, John Beranek - PA < >>> john.b...@pressassociation.com> wrote:
>>>
>>>> Oh, apologies, your Secondary is completely disconnected from the rest
>>>> of Katello? How do expect the systems to be synchronised then?
>>>>
>>>> John
>>>>
>>>> On Monday, 28 September 2015 14:06:50 UTC+1, JC wrote:
>>>>>
>>>>> Thanks for the reply John.
>>>>>
>>>>> I saw a capsule server as something that was dependent on the Katello
>>>>> server. That is, it needs network connectivity to the Katello server...
>>>>>
>>>>> On 28 September 2015 at 13:24, John Beranek - PA < >>>>> john.b...@pressassociation.com> wrote:
>>>>>
>>>>>> If I'm not mistaken, your described "Secondary" is a "Capsule" in
>>>>>> Katello terms:
>>>>>>
>>>>>> http://www.katello.org/docs/2.3/user_guide/capsules/index.html
>>>>>>
>>>>>> John
>>>>>>
>>>>>> On Monday, 28 September 2015 12:23:48 UTC+1, JC wrote:
>>>>>>>
>>>>>>> I have a Katello server (the 'primary') which synchronises with
>>>>>>> public repositories. I want to build and maintain another Katello server
>>>>>>> (the 'secondary') on another network which cannot see the internet or the
>>>>>>> primary; I want the primary to be the source for secondary. The secondary
>>>>>>> needs to be a full-featured Katello instance.
>>>>>>>
>>>>>>> My goals are thus:
>>>>>>>
>>>>>>> 1. Build of the secondary (the primary has the repos).
>>>>>>> 2. Populate and maintain the repos of the secondary.
>>>>>>>
>>>>>>> katello-disconnected[1] looks to mess with my working primary
>>>>>>> instance (is a synchronisation host a different beast?) and appears geared
>>>>>>> towards RHEL (needing a manifest file). Should I just tarball the
>>>>>>> published (via http) content from the primary, unpack it to a webserver
>>>>>>> that the secondary can see and synchronise with that?
>>>>>>>
>>>>>>> Many thanks.
>>>>>>>
>>>>>>> 1.
>>>>>>> http://www.katello.org/docs/2.3/user_guide/disconnected/index.html
>>>>>>>
>>>>>>> --
>>>>>> You received this message because you are subscribed to a topic in
>>>>>> the Google Groups "Foreman users" group.
>>>>>> To unsubscribe from this topic, visit
>>>>>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe
>>>>>> .
>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>> foreman-user...@googlegroups.com.
>>>>>> To post to this group, send email to forema...@googlegroups.com.
>>>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "Foreman users" group.
>>>> To unsubscribe from this topic, visit
>>>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> foreman-user...@googlegroups.com.
>>>> To post to this group, send email to forema...@googlegroups.com.
>>>> Visit this group at http://groups.google.com/group/foreman-users.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/R-CPwRi0rS0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-user...@googlegroups.com .
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
