Curious where this ended up. This would be awesome. Cheers, Paul
On Sunday, September 23, 2012 5:20:13 PM UTC-7, Romeo Theriault wrote: > > On Sun, Sep 23, 2012 at 12:50 PM, Michael DeHaan > <[email protected] <javascript:>> wrote: > >> > >> For example: > >> * enabling and disabling a service in aix requires editing /etc/inittab > file. > >> * Solaris SMF does not seperate the act of enabling a service and > >> starting it. To enable it you have to start it. Same goes for > >> disabling it. To disable it you have to stop it. (Yes it's silly, but > >> that's how it works.) > > > > I think that's ok if this just works that way under the covers. > > > > We can keep the user from worrying about how it works. > > > > > >> * etc... > >> > >> Just thinking aloud here to make sure we're on the same page. But my > >> thoughts are that If we're going to try to keep this as one module I > >> think it makes sense to have a base service module class and then > >> different platforms would need to subclass the base class to define > >> how they implement each of the features. I think this keeps it cleaner > >> and more maintainable. The tricky part of doing it this way though > >> would be the best way to determine what arch/platform they are running > >> on to automatically figure out which service subclass to use. > > > >> > >> Thoughts? Suggestions? > >> > > > > Subclassing sounds great to me. > > > > OS detection could work similar to the way the facts do it. > > Ok, I'll give it a go and see what I can come up with. > > -- > Romeo > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
