Puppet users - Mar 2011 - Dashboard "write" API (was Re: Role-based access in Dashboard)

Brian Gupta wrote:
> Randall, sorry for the offtopic response, but our team needs a
"write"
> API before RBAC. WIthout it Dashboard is a non-starter in our shop.
Brian

Can you articulate what you''d like to see from this API whilst
we''re
here and I''ll capture it in a ticket.

Thanks

James

-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

We find it frequently useful to be able to set variables from within puppet
to communicate information from one module or class to another, or to save
state across puppet runs.  It also makes cloud management and bootstrapping
easier to be able to specify classes/variables from a command line script
being used to spin up nodes.

Also, going forward, it would be very helpful for the API to be an equal
citizen of the GUI. IE: There shouldn''t really be anything that you can
do
via the GUI, that you can''t do programmatically. This will also allow
for
the creation of CLI based tools that can interact with Puppet Dashboard,
which is rather important to us.

Please let me know if you have any further questions.

-Brian

On Wed, Mar 2, 2011 at 7:28 PM, James Turnbull <james@puppetlabs.com>
wrote:
> Brian Gupta wrote:
> > Randall, sorry for the offtopic response, but our team needs a
"write"
> > API before RBAC. WIthout it Dashboard is a non-starter in our shop.
>
> Brian
>
> Can you articulate what you''d like to see from this API whilst
we''re
> here and I''ll capture it in a ticket.
>
> Thanks
>
> James
>
> --
> James Turnbull
> Puppet Labs
>  <1-503-734-8571> <1-503-734-8571>1-503-734-8571
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
<http://aws.amazon.com/solutions/solution-providers/brandorr/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mar 3, 2011, at 9:20 AM, Brian Gupta wrote:
> Also, going forward, it would be very helpful for the API to be an equal
citizen of the GUI.
I agree, Brian.  While we plan to improve Dashboard''s GUI for those who
want it, it''s often hard to beat a CLI for efficiency and
repeatability.
> Please let me know if you have any further questions.
Absolutely.  I''ll keep your name on my list, and we''ll make
our plans in public.

r


-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Brian Gupta wrote:
> We find it frequently useful to be able to set variables from within
> puppet to communicate information from one module or class to another,
> or to save state across puppet runs.  It also makes cloud management and
> bootstrapping easier to be able to specify classes/variables from a
> command line script being used to spin up nodes.
> 
> Also, going forward, it would be very helpful for the API to be an equal
> citizen of the GUI. IE: There shouldn''t really be anything that
you can
> do via the GUI, that you can''t do programmatically. This will also
allow
> for the creation of CLI based tools that can interact with Puppet
> Dashboard, which is rather important to us.
> 
> Please let me know if you have any further questions.
> 
>
Brian

The API is currently much more fully featured than the GUI. Have you
seen Luke and Dan''s Puppet-Interfaces work?

I think it''ll give you most (and perhaps more) of what you want.

https://github.com/lak/puppet-interfaces
https://github.com/bodepd/puppet-interfaces

Regards

James

-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Mar 3, 2011 at 12:27 PM, Randall Hansen
<randall@puppetlabs.com>wrote:
> On Mar 3, 2011, at 9:20 AM, Brian Gupta wrote:
>
> > Also, going forward, it would be very helpful for the API to be an
equal
> citizen of the GUI.
>
> I agree, Brian.  While we plan to improve Dashboard''s GUI for
those who
> want it, it''s often hard to beat a CLI for efficiency and
repeatability.
>
Yes it will also make it possible to integrate with Ubuntu''s cloud-init
framework, which has quickly become the standard for cloud-based post-spinup
node customization and configuration, with CentOS and other distro support
included. Amazon has even adopted it now. That said, cloud-init is no longer
just an EC2 option, with Eculyptus and Openstack support builtin for private
cloud deployments. The way I envision using it is is to pass the node
it''s
hostname, classes, custom puppet variables and a user-data script that
cloud-init would use to install puppet, and have the node register itself
with DNS and Dashboard.
> Please let me know if you have any further questions.
>
> Absolutely.  I''ll keep your name on my list, and we''ll
make our plans in
> public.
>
Any sense on a timeframe? (I just saw James'' email. I will reply
separately
later tonight.)

> r
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
<http://aws.amazon.com/solutions/solution-providers/brandorr/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Thu, Mar 3, 2011 at 4:25 PM, James Turnbull <james@puppetlabs.com>
wrote:
> Brian Gupta wrote:
> > We find it frequently useful to be able to set variables from within
> > puppet to communicate information from one module or class to another,
> > or to save state across puppet runs.  It also makes cloud management
and
> > bootstrapping easier to be able to specify classes/variables from a
> > command line script being used to spin up nodes.
> >
> > Also, going forward, it would be very helpful for the API to be an
equal
> > citizen of the GUI. IE: There shouldn''t really be anything
that you can
> > do via the GUI, that you can''t do programmatically. This will
also allow
> > for the creation of CLI based tools that can interact with Puppet
> > Dashboard, which is rather important to us.
> >
> > Please let me know if you have any further questions.
> >
> >
>
> Brian
>
> The API is currently much more fully featured than the GUI. Have you
> seen Luke and Dan''s Puppet-Interfaces work?
>
> I think it''ll give you most (and perhaps more) of what you want.
>
> https://github.com/lak/puppet-interfaces
> https://github.com/bodepd/puppet-interfaces
>
> Regards
>
> James
>
We''ll definably check it out. I''m wondering right now
who''s version we
should start testing, and where we install it? Also does it interface
directly with dashboard, or is everything proxied through the puppetmaster?

--
> James Turnbull
> Puppet Labs
> 1-503-734-8571
>
>

-- 
<http://aws.amazon.com/solutions/solution-providers/brandorr/>

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Brian Gupta wrote:
> 
> Yes it will also make it possible to integrate with Ubuntu''s
cloud-init
> framework, which has quickly become the standard for cloud-based
> post-spinup node customization and configuration, with CentOS and other
> distro support included. Amazon has even adopted it now. That said,
> cloud-init is no longer just an EC2 option, with Eculyptus and Openstack
> support builtin for private cloud deployments. The way I envision using
> it is is to pass the node it''s hostname, classes, custom puppet
> variables and a user-data script that cloud-init would use to install
> puppet, and have the node register itself with DNS and Dashboard.
> 
Brian

Puppet is supported in cloud-init now.

http://ubuntumathiaz.wordpress.com/2010/03/24/using-puppet-in-uecec2-puppet-support-in-ubuntu-images/

http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config-puppet.txt

Regards

James


-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Brian Gupta wrote:
> We''ll definably check it out. I''m wondering right now
who''s version we
> should start testing, and where we install it? Also does it interface
> directly with dashboard, or is everything proxied through the puppetmaster?
> 
Brian

Use Luke''s (lak). It''s largely a CLI for interacting with the
Puppet
master but it opens up a lot more paths for interfacing and extracting
data from Puppet that can be used elsewhere.

Installation:

"Note that this only works with Puppet 2.6.next (and thus will work with
2.6.5), because there is otherwise a bug in finding Puppet applications.
You also have to either install the lib files into your Puppet libdir,
or you need to add this lib directory to your RUBYLIB."

It''s in beta right now but we''d love feedback on it.

James

-- 
James Turnbull
Puppet Labs
1-503-734-8571

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

On Mar 3, 2011, at 1:40 PM, Brian Gupta wrote:
>> Absolutely.  I''ll keep your name on my list, and
we''ll make our plans in public.
> 
> Any sense on a timeframe?
Not at all.  I don''t like that answer either, but it''s the
only truth we have.  We''ll have a better idea when our roadmap for
Dashboard improves.

r

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.