Mike McCune wrote: Ok, it's early yet.. :) Oh, good. Glad to hear that. Both, actually. From the disk side, storing the same thing twice seems to be a waste. Though I do understand that having a shared repo like that means that changes by one org can affect the other. Security concerns, etc. For those situations, maybe a "read only" repo would be useful. Something an admin can set up but none of the orgs can change. Or maybe have an org listed as the admin for a repo. As for the usability side, it's more of a convenience than anything I guess. Having to re-create it in another org is just more work. Since I only have a few repos (so far) that need to be shared, it's not a big deal. But if there were a lot... Of course, that said, I'm not sure how many users of Katello have more than a single org configured. So maybe this is just something I'll have to deal with as a minority user. -- --------------------------- Jason 'XenoPhage' Frisvold xenophage(a)godshell.com --------------------------- "Any sufficiently advanced magic is indistinguishable from technology.\" - Niven's Inverse of Clarke's Third Law