SFCB/Pegasus patches to prioritize Pegasus installation

Russell Doty rdoty at redhat.com
Wed Aug 21 13:32:13 UTC 2013


On Wed, 2013-08-21 at 09:08 -0400, Stephen Gallagher wrote:
> On 08/21/2013 08:56 AM, Roman Rakus wrote:
> > This seems to be correct. What I can imagine is also a group of
> > packages. What other thinks about it? Having all stuff (CIMOM,
> > providers, lmishell, ...) in one group will inform people what
> > other thing are available.
> > 
> 
> 
> 
> I was thinking about having us provide a set of meta-packages like
> 'openlmi-server' and 'openlmi-enterprise' that would bind up the set
> of providers, CIMOMs and dependencies that we want people to be
> installing most of the time.
> 
> openlmi-server (normal set of providers for all servers):
> tog-pegasus
> openlmi-storage
> openlmi-networking
> openlmi-software
> openlmi-account
> openlmi-realmd
I would make realmd optional, or at least put it in the enterprise
package.
> openlmi-service
The hardware (inventory) Provider should be in the base package.

What about the lmi-tools package?
Do we want to install anything from sblim? (I don't think so, but want
to raise the question.)
> 
> openlmi-enterprise (comprehensive providers and discovery):
> openlmi-server
> openslp
> openlmi-fan
> openlmi-hardware
> openlmi-logicalfile
> openlmi-powermanagement
> 
> 
Looking ahead, which package (if any) should new Providers be included
in?
* firewall
* SELinux
* SCAP
* Monitoring (general, Performance Copilot)
* logging
* other?
> _______________________________________________
> openlmi-devel mailing list
> openlmi-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/openlmi-devel




More information about the openlmi-devel mailing list