David, that was a terrible post on my part. I've already apologized to
jimi_c on IRC. Was very frustrated that day.
For what it's worth, I too am trying to move toward Ansible, but it's hard
to get buy-in.
On Tue, Jul 30, 2013 at 4:28 PM, David Birdsong <david.birdsong(a)gmail.com>wrote:
On Sat, Jul 27, 2013 at 4:49 PM, Greg Chavez <greg.chavez(a)gmail.com>wrote:
> Ah ha. So for the time being I have to create a separate management
> class object for every unique declaration of a parameterized class.
>
> At a certain point, doesn't it just make sense to say "Cobbler supports
> puppet 100% and support for other tools vary" instead of "Cobbler supports
> configuration management 100%"? How many people use Cobbler with a config
> tool that is not Puppet?
>
I do. I've used Cfengine, Chef, Puppet, and now days I use Ansible.
Please do not cater only to Puppet.
>
> I only say this because I fear we're going in a direction with config
> management that is no longer intuitive. How can I help?
>
>
>
>
> On Sat, Jul 27, 2013 at 12:50 PM, James Cammarata <jimi(a)sngx.net> wrote:
>
>> The parameters go in the variables section of the mgmt class, not in
>> ksmeta (I will do variable substitutions from ksmeta in the future, but for
>> now it doesn't).
>>
>> On Sat, Jul 27, 2013 at 11:42 AM, Greg Chavez
<greg.chavez(a)gmail.com>wrote:
>>
>>>
>>> I suspect I am being obtuse here. I'm trying to use the arusso/vnc
>>> module from puppet forge which is declared like this:
>>>
>>> class { 'vnc':
>>> refresh => true,
>>> servers => [ 'user' => 'pete',
>>> 'args' => '-geometry 1920x1200 -depth
16' ],
>>> service_ensure => true,
>>> xstartup_template => 'myclass/xstartup.erb',
>>> }
>>>
>>> Via the Web console, I did the following:
>>>
>>> --------------------
>>>
>>> (1) Created management class "vnc":
>>> **** name: vnc
>>> **** class name: vnc
>>> **** parameters/variables: service_ensure xstartup_template refresh
>>> servers
>>>
>>> (2) In system object:
>>> **** selected class "vnc"
>>> **** Added yaml to management parameters which was converted to:
>>>
>>> { service_ensure: True, xstartup_template: vnc/xstartup.erb, refresh:
>>> True, servers: [{'user': 'pete'}, {'args':
'-geometry 1920x1200 -depth
>>> 16'}] }
>>>
>>> --------------------
>>>
>>> However, this is what cobbler-ext-node returns for the system:
>>>
>>> ~> cobbler-ext-nodes pete.local
>>> classes:
>>> site: {}
>>> vnc:
>>> refresh: '~'
>>> servers: '~'
>>> service_ensure: '~'
>>> xstartup_template: '~'
>>> environment: production
>>> parameters:
>>> from_cobbler: 1
>>> refresh: true
>>> servers:
>>> - user: pete
>>> - args: -geometry 1920x1200 -depth 16
>>> service_ensure: true
>>> tree: http://@@http_server@@/cblr/links/centos-6.4-x86_64
>>> xstartup_template: vnc/xstartup.erb
>>>
>>> I didn't think that this would work the way I did it, but I was hoping
>>> the resultant breakage would give me a clue as to how to fix. No such
>>> luck. I am stumped.
>>>
>>> Can anyone tell me what I'm doing wrong? Mahalo in advance.
>>>
>>> --
>>> \*..+.-
>>> --Greg Chavez
>>> +//..;};
>>>
>>> _______________________________________________
>>> cobbler mailing list
>>> cobbler(a)lists.fedorahosted.org
>>>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
>>>
>>>
>>
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
>>
>>
>
>
> --
> \*..+.-
> --Greg Chavez
> +//..;};
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler