Red Hat Bugzilla – Bug 76265
Channel cloning tools
Last modified: 2007-07-31 15:14:59 EDT
It should be possible for a satellite customer to easily clone a Red Hat public
channel for their own management. This is especially important for customers
who want to manage a subset of packages from a Red Hat release, or want subtly
different packages in their base channel. Currently, customers who want
channels that are very similar to Red Hat base channels must reimport all of the
packages by hand. We need to give them a better mechanism than this.
We've worked out some implementation details that need to be noted.
A cloned channel must share the same entitlement restrictions as those of the
original channel. Therefore:
* A cloned channel will be placed in the same channel family as its original;
* A cloned channel will be placed in its own org.
This means that we'll have to check the following things VERY closely in QA:
* Does syncing still work as expected? Does any nastiness crop up when syncing
a channel that has clones?
* Will the channel subscription limits work properly in the web interface with
the cloned channels as well as the original?
* Other things that I'm probably not thinking of now.
The above policy should now be in place in cvs.
This is Titan, not the web release (Titan Lite), reassigning.
This is more properly tracked both in Titan and in Titan Lite Point.
Changing broken dependency list here, associating with Titan web. Removing from
Titan backend tracking.
This really just needs to be QA'd thoroughly in the context of Titan.
Making this a dependancy of the 3/24 release so it can see some QA time.
I'm guessing that the test interface for this would be on the satellite itself,
rather than in the parent org - so there's really no way I can test this until I
have a 4version of titan that I can build. Correct?
please indicate which pages on the website I should check to ensure these
changes don't show up.
'Clone From' should not appear.
Should only allow the user to view packages in channels that his org owns.
/network/software/errata/manage/package_list.pxt gives me a 404.
That's because I made it up. Just...uh...testing you...yeah, that's it.
Looks good, over to QA.
ooh, pretty colors!
Disregard the previous post, have opened bug #87409 for non-XML-complient
pages.This looks good in QA, so closing.
*** Bug 86980 has been marked as a duplicate of this bug. ***