[Spacewalk-list] Syncing clone channels?

[McLeod, Matt]

It may be that I'm misunderstanding something fundamental.

 

I've got four parent channels configured, one each for CentOS 5.4 and
5.5 for i386 and x86_64.  This is a deliberate choice as we want more
control over when a host moves between OS releases than would be
possible with a single "CentOS 5" channel per architecture.

 

We also sync the entire EPEL5 repository for each architecture.  At the
moment this has been set up by syncing EPEL5 for i386 into a child
channel of "CentOS 5.4 i386" then cloning that via the web interface
into a child of "CentOS 5.5 i386".

 

Problem is, cloning seems to be a one-time operation.  Updates that go
into the source channel don't make it into the destination.

 

Is there some way to make this happen?  I suppose one could do something
via the API to delete then re-create the clone after updates have
finished syncing?  But would that then mean that all hosts subscribed to
the clone will lose that subscription?

 

The other obvious option would be to keep a "staging" copy of EPEL5 on
disk, sync that, then update the channels from there.  Not keen on it
though, we're running Spacewalk on a VMWare cluster so "storage is
cheap" does not really apply here.

 

Any alternatives I'm missing?

 

Thanks.

 

Matt

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20100629/8d6c52a4/attachment.htm>
-------------- next part --------------
++++++++++++++++++++++++++++++++++++++++++++++++ 
The information contained in this communication is strictly confidential and intended solely for the use of the intended recipient(s). The copyright in this communication belongs to ITG Australia Ltd, ITG Hong Kong Limited, ITG Singapore Pte Ltd and/or their related entities, including Investment Technology Group, Inc., (collectively referred to as ?ITG") and may contain information that is private, confidential or subject to legal professional or other privilege. No confidentiality or privilege is waived or lost by any mis-transmission of this email. 

Access to this email by anyone other than the intended recipient is unauthorized and further distribution of this email is strictly prohibited without the permission of ITG. If you are not the intended recipient of this email, any review, disclosure, copying, distribution, retention or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient of this email, you should not disseminate, distribute or copy this e-mail and you should delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ITG and/or its affiliates reserve the right to monitor and archive all electronic communications through its/their network. 

The information contained in this email is believed to be accurate at the time of publication. However, ITG disclaims all responsibility for any loss or damage howsoever arising as a result of any person or entity acting upon the information contained in this email and no liability will be accepted by ITG for any such loss or damage. Any views expressed in this email are those of the individual sender, except where the email states otherwise and the sender is authorized to state them to be the views of ITG. 
++++++++++++++++++++++++++++++++++++++++++++++++