OK. Lete me be more specific:

I have a module to handle user accounts that relies on hiera:

Accounts are defined at the lowest level of the hierarchy and instantiated 
(ensure => present) up at the node level of the hierarchy.  The issue with this 
is that I am getting complaints from other team members about having to touch 
multiple yaml files at multiple locations in the data store (rather than having 
to touch multiple servers), so I was hoping for a way to present it in one 
“page” of the console - like Inventory Service or Inventory Search

My next choice is to hack together a ruby script to do the job from a command 
line.

On Sep 11, 2013, at 3:42 PM, Rich Burroughs wrote:

> Dan,
> 
> You can do those things from the PE console but you don't have to. You can 
> assign classes to nodes the old school way too. It's really up to you whether 
> you prefer to do those kinds of things through the UI or in your Puppet code.
> 
> 
> 
> On Wednesday, September 11, 2013, Dan White wrote:
> I have bee using Open Source Puppet for about two years now -- and I have 
> enjoyed the ride so far.
> 
> I want to spin up a demo PE-Master because we are also spinning up a big 
> VMWare driven virtualization push and I want to try the Cloud Provisioning.  
> If it works for me as well as everything else has to date, I will have no 
> trouble making the pitch to The Customer to go for PE licensing.
> 
> The difficulty I am having is transitioning from nodes defined under 
> /etc/puppet/manifests/nodes to nodes defined in the PE console.
> 
> I think I have to somehow add all my modules into the console and then I can 
> assign them to nodes.
> 
> Is that in the right direction ?
> 
> “Sometimes I think the surest sign that intelligent life exists elsewhere in 
> the universe is that none of it has tried to contact us.”
> Bill Waterson (Calvin & Hobbes)
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" 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].
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Puppet Users" 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].
> Visit this group at http://groups.google.com/group/puppet-users.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" 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].
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to