Satellite 6.x Host groups/collections for different departments
I'm going round in circles trying to implement something relatively straightforward; I have several departments (~25) which ideally, should only be able to manage their own hosts which have been registered/activated using their own seperate activation key.
- There is no permission/role/filter which can be set which allows me to do this. ?
- Should I be using different organisations, having looked at this, it looks like I need to generate 25 odd manifests to import into RHS, then setup another 25 Libraries and environments for each organisation... really?
Does anyone have any hints as to how they have implemented their Satellite setup to achieve something similar?
Responses
Pro
798 points
Not until Satellite 6.2. In 6.1.x, there is a bug/design flaw that negates using separate Organizations as you described, since per-host errata details cannot be seen, and errata cannot be applied in the web GUI without granting "administrator" rights on the Satellite server. Or you can restrict your department-level users to viewing patching detail & applying patches via the "yum" command-line tools (many of our non-full-time sys admins really dislike that option).
I do not know when, or even if, "Host Collections" will be usable as a security barrier, as "system groups" in Satelllite 5.x are.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.