On Fri, Jun 28, 2013 at 11:30 AM, James Cammarata <jimi@sngx.net> wrote:
On Fri, Jun 28, 2013 at 12:55 PM, David Birdsong <david.birdsong@gmail.com> wrote:
I'm trying to understand the useful bridge between ansible and cobbler. I've leveraged cobbler for installation and early configuration and it works great.

I'm trying to figure out how to use cobbler variables to expose settings to ansible. It appears that the default cobbler inventory script uses mgmt classes to group machines and then ksmeta variables which follow the inheritance patterns of ksmeta variables.

What I don't see ansible using is the mgmtclass params field. Even the help message for
```cobbler mgmtclass edit ``` is a little confusing with the mention of ksmeta in the --clobber flag while there exists no --ksmeta flag--only params.

So what do people use mgmt params for?

I haven't looked, but do they trickle down to machine variables for kickstarts?

Those were just added, so the external inventory script for ansible will need to be updated to use them. Right now they are only used for parameterized puppet classes and defines.

Cool, so there's the issue of multiple inheritance with mgmt classes, no?

Machines can exist in one or many mgmt classes while distros -> profiles -> machines are single inheritance.

How do puppet folks cope?


 _______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler