[Spacewalk-list] A/B update process?
Matt Warren
mwarren at hnw.com
Thu Dec 6 18:21:29 UTC 2012
Thanks. Martineg_ on IRC also mentioned creating a system profile of A and
applying it to B.
Or using a compare of B against A and doing a sync.
Sounds like a few ways to skin it.
So cloned channels can be "frozen" so they don't acquire new updates?
On 12/6/12 1:13 PM, "Tom Brown" <tom at ng23.net> wrote:
>Clone channel at time system a is updated. Update b to that channel.
>
>On 6 Dec 2012, at 18:02, Matt Warren <mwarren at hnw.com> wrote:
>
>>Been trying to glean this from docs and failing.
>>Can spacewalk solve this: Update system A, weeks later update system B
>>with same and ONLY same updates put to A. Even if new updates in channel
>>have come out in the interval?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3515 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20121206/31f8b055/attachment.p7s>
More information about the Spacewalk-list
mailing list