Puppet users - Jul 2011 - ANNOUNCE: Cloud Provisioner v0.6.0rc1 release

We are happy to announce the first public release candidate of our Puppet
Cloud Provisioner.

This release is available for download at our Module Forge:
http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/>

Extensive documentation can be found at:
http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html

Please report feedback via the Puppet Labs Redmine site, using an
affected version of 0.6.0rc1:
http://projects.puppetlabs.com/projects/cloud-pack<http://projects.puppetlabs.com/projects/dashboard>


Overview:

The Puppet  Cloud Provisioner was written to make it easier to deploy and
configure instances in EC2 using Puppet.

It contains the following command line actions:

puppet node create - Launches a new Amazon EC2 instance.

puppet node install - Installs Puppet on an EC2 instance.

puppet node init - Installs Puppet on a machine instance and automatically
signs its certificates.

puppet node list - Lists deployed EC2 instances in a certain region.

puppet node terminate - Terminates running EC2 instance.


For more detailed information about the available commands, download the
module and run:

puppet help node

More Details about the iteration leading up to this release
==* Add --type option to launch different EC2 instance sizes
* (#7510) Add inline documentation for actions and options
* (#8286) Warn if the payload used with the install action is not a tar.gz
file
* (#8265) Make the platform flag optional and default to ''AWS''
(Note,
puppet-provisioner provisions AWS EC2 instances in this release)
* (#7511) Add the ability to launch instances in any EC2 region using the
--region option.  The default region is us-east-1
* (#8157) Improve the feedback of the terminate action by explicitly stating
the instance has been terminated.
* (#8185) Add a list action to list EC2 instances and their current status.
* (#8343) Print the EC2 instance public DNS name as soon as it is available
* (#8350) Change all output to use Puppet''s configured log destination
* (#8348) Add a fingerprint action to make a best effort to obtain the SSH
public host key fingerprint from the launched EC2 instance.
* (#7508) Add the ability to install Puppet using rubygems on a target
system.
* (#7508) Improve the install action using template scripts to install
Puppet
on launched systems.
* (#8403) Replace dependency on uuidgen Mac OS X executable with guid gem.
* (#8422) Catch the exit status of installation script and display an error
if
they''re non zero.
* (#8204) Include a puppet enterprise install script that downloads from S3.
This should improve install times on low bandwidth connections.
* (#8472) Add support for non-root logins when installing puppet on a target
system.
* (#8493) Rename cloudpack to cloud-provisioner

-- 
Jeff McCune
@0xEFF
Join us for PuppetConf <http://links.puppetlabs.com/puppetconf>, Sept
22-23
in Portland, OR

-- 
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.

''Cloud Provisioner'' seems like a funny name if it''s
only designed to manage
Amazon EC2 instances. Why didn''t you just call it the ''Amazon
Provisioner'' ?

On Thu, Jul 21, 2011 at 4:18 PM, Jeff McCune <jeff@puppetlabs.com> wrote:
> We are happy to announce the first public release candidate of our Puppet
> Cloud Provisioner.
>
> This release is available for download at our Module Forge:
>
http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/>
>
> Extensive documentation can be found at:
> http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected version of 0.6.0rc1:
>
http://projects.puppetlabs.com/projects/cloud-pack<http://projects.puppetlabs.com/projects/dashboard>
>
>
> Overview:
>
> The Puppet  Cloud Provisioner was written to make it easier to deploy and
> configure instances in EC2 using Puppet.
>
> It contains the following command line actions:
>
> puppet node create - Launches a new Amazon EC2 instance.
>
> puppet node install - Installs Puppet on an EC2 instance.
>
> puppet node init - Installs Puppet on a machine instance and automatically
> signs its certificates.
>
> puppet node list - Lists deployed EC2 instances in a certain region.
>
> puppet node terminate - Terminates running EC2 instance.
>
>
> For more detailed information about the available commands, download the
> module and run:
>
> puppet help node
>
> More Details about the iteration leading up to this release
> ==> * Add --type option to launch different EC2 instance sizes
> * (#7510) Add inline documentation for actions and options
> * (#8286) Warn if the payload used with the install action is not a tar.gz
> file
> * (#8265) Make the platform flag optional and default to
''AWS'' (Note,
> puppet-provisioner provisions AWS EC2 instances in this release)
> * (#7511) Add the ability to launch instances in any EC2 region using the
> --region option.  The default region is us-east-1
> * (#8157) Improve the feedback of the terminate action by explicitly
> stating
> the instance has been terminated.
> * (#8185) Add a list action to list EC2 instances and their current status.
> * (#8343) Print the EC2 instance public DNS name as soon as it is available
> * (#8350) Change all output to use Puppet''s configured log
destination
> * (#8348) Add a fingerprint action to make a best effort to obtain the SSH
> public host key fingerprint from the launched EC2 instance.
> * (#7508) Add the ability to install Puppet using rubygems on a target
> system.
> * (#7508) Improve the install action using template scripts to install
> Puppet
> on launched systems.
> * (#8403) Replace dependency on uuidgen Mac OS X executable with guid gem.
> * (#8422) Catch the exit status of installation script and display an error
> if
> they''re non zero.
> * (#8204) Include a puppet enterprise install script that downloads from
> S3.
> This should improve install times on low bandwidth connections.
> * (#8472) Add support for non-root logins when installing puppet on a
> target
> system.
> * (#8493) Rename cloudpack to cloud-provisioner
>
> --
> Jeff McCune
> @0xEFF
> Join us for PuppetConf <http://links.puppetlabs.com/puppetconf>, Sept
> 22-23 in Portland, OR
>
> --
> 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.
>


-- 
Regards,

Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garstang@gmail.com
Cell: +1-805-340-5627

-- 
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.

Gonna take a wild guess that there are plans to support other providers..

On Thu, Jul 21, 2011 at 6:32 PM, Douglas Garstang
<doug.garstang@gmail.com>wrote:
> ''Cloud Provisioner'' seems like a funny name if
it''s only designed to manage
> Amazon EC2 instances. Why didn''t you just call it the
''Amazon Provisioner'' ?
>
>
> On Thu, Jul 21, 2011 at 4:18 PM, Jeff McCune <jeff@puppetlabs.com>
wrote:
>
>> We are happy to announce the first public release candidate of our
Puppet
>> Cloud Provisioner.
>>
>> This release is available for download at our Module Forge:
>>
http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/>
>>
>> Extensive documentation can be found at:
>> http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
>>
>> Please report feedback via the Puppet Labs Redmine site, using an
>> affected version of 0.6.0rc1:
>>
http://projects.puppetlabs.com/projects/cloud-pack<http://projects.puppetlabs.com/projects/dashboard>
>>
>>
>> Overview:
>>
>> The Puppet  Cloud Provisioner was written to make it easier to deploy
and
>> configure instances in EC2 using Puppet.
>>
>> It contains the following command line actions:
>>
>> puppet node create - Launches a new Amazon EC2 instance.
>>
>> puppet node install - Installs Puppet on an EC2 instance.
>>
>> puppet node init - Installs Puppet on a machine instance and
automatically
>> signs its certificates.
>>
>> puppet node list - Lists deployed EC2 instances in a certain region.
>>
>> puppet node terminate - Terminates running EC2 instance.
>>
>>
>> For more detailed information about the available commands, download
the
>> module and run:
>>
>> puppet help node
>>
>> More Details about the iteration leading up to this release
>> ==>> * Add --type option to launch different EC2 instance sizes
>> * (#7510) Add inline documentation for actions and options
>> * (#8286) Warn if the payload used with the install action is not a
tar.gz
>> file
>> * (#8265) Make the platform flag optional and default to
''AWS'' (Note,
>> puppet-provisioner provisions AWS EC2 instances in this release)
>> * (#7511) Add the ability to launch instances in any EC2 region using
the
>> --region option.  The default region is us-east-1
>> * (#8157) Improve the feedback of the terminate action by explicitly
>> stating
>> the instance has been terminated.
>> * (#8185) Add a list action to list EC2 instances and their current
>> status.
>> * (#8343) Print the EC2 instance public DNS name as soon as it is
>> available
>> * (#8350) Change all output to use Puppet''s configured log
destination
>> * (#8348) Add a fingerprint action to make a best effort to obtain the
SSH
>> public host key fingerprint from the launched EC2 instance.
>> * (#7508) Add the ability to install Puppet using rubygems on a target
>> system.
>> * (#7508) Improve the install action using template scripts to install
>> Puppet
>> on launched systems.
>> * (#8403) Replace dependency on uuidgen Mac OS X executable with guid
gem.
>> * (#8422) Catch the exit status of installation script and display an
>> error if
>> they''re non zero.
>> * (#8204) Include a puppet enterprise install script that downloads
from
>> S3.
>> This should improve install times on low bandwidth connections.
>> * (#8472) Add support for non-root logins when installing puppet on a
>> target
>> system.
>> * (#8493) Rename cloudpack to cloud-provisioner
>>
>> --
>> Jeff McCune
>> @0xEFF
>> Join us for PuppetConf <http://links.puppetlabs.com/puppetconf>,
Sept
>> 22-23 in Portland, OR
>>
>> --
>> 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.
>>
>
>
>
> --
> Regards,
>
> Douglas Garstang
> http://www.linkedin.com/in/garstang
> Email: doug.garstang@gmail.com
> Cell: +1-805-340-5627
>
>
>  --
> 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.
>
-- 
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.

Any plans to support other cloud providers? Specifically VMWare?

On Jul 21, 4:18 pm, Jeff McCune <j...@puppetlabs.com>
wrote:
> We are happy to announce the first public release candidate of our Puppet
> Cloud Provisioner.
>
> This release is available for download at our Module
Forge:http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/>
>
> Extensive documentation can be found
at:http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html
>
> Please report feedback via the Puppet Labs Redmine site, using an
> affected version of
0.6.0rc1:http://projects.puppetlabs.com/projects/cloud-pack<http://projects.puppetlabs.com/projects/dashboard>
>
> Overview:
>
> The Puppet  Cloud Provisioner was written to make it easier to deploy and
> configure instances in EC2 using Puppet.
>
> It contains the following command line actions:
>
> puppet node create - Launches a new Amazon EC2 instance.
>
> puppet node install - Installs Puppet on an EC2 instance.
>
> puppet node init - Installs Puppet on a machine instance and automatically
> signs its certificates.
>
> puppet node list - Lists deployed EC2 instances in a certain region.
>
> puppet node terminate - Terminates running EC2 instance.
>
> For more detailed information about the available commands, download the
> module and run:
>
> puppet help node
>
> More Details about the iteration leading up to this release
> ==> * Add --type option to launch different EC2 instance sizes
> * (#7510) Add inline documentation for actions and options
> * (#8286) Warn if the payload used with the install action is not a tar.gz
> file
> * (#8265) Make the platform flag optional and default to
''AWS'' (Note,
> puppet-provisioner provisions AWS EC2 instances in this release)
> * (#7511) Add the ability to launch instances in any EC2 region using the
> --region option.  The default region is us-east-1
> * (#8157) Improve the feedback of the terminate action by explicitly
stating
> the instance has been terminated.
> * (#8185) Add a list action to list EC2 instances and their current status.
> * (#8343) Print the EC2 instance public DNS name as soon as it is available
> * (#8350) Change all output to use Puppet''s configured log
destination
> * (#8348) Add a fingerprint action to make a best effort to obtain the SSH
> public host key fingerprint from the launched EC2 instance.
> * (#7508) Add the ability to install Puppet using rubygems on a target
> system.
> * (#7508) Improve the install action using template scripts to install
> Puppet
> on launched systems.
> * (#8403) Replace dependency on uuidgen Mac OS X executable with guid gem.
> * (#8422) Catch the exit status of installation script and display an error
> if
> they''re non zero.
> * (#8204) Include a puppet enterprise install script that downloads from
S3.
> This should improve install times on low bandwidth connections.
> * (#8472) Add support for non-root logins when installing puppet on a
target
> system.
> * (#8493) Rename cloudpack to cloud-provisioner
>
> --
> Jeff McCune
> @0xEFF
> Join us for PuppetConf <http://links.puppetlabs.com/puppetconf>, Sept
22-23
> in Portland, OR
-- 
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.

Scott Smith wrote:
> Gonna take a wild guess that there are plans to support other providers..
> 
Correct!

Regards

James


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

Join us for PuppetConf <http://www.bit.ly/puppetconfsig>, September 22nd
and 23rd in Portland, Oregon, USA.

-- 
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.

Jared Curtis wrote:
> Any plans to support other cloud providers? Specifically VMWare?
> 
Jared

There are such plans.  Obviously it''s also open source so
we''ll add some
further support and hopefully the community will chime in with other
updates and enhancements that they require.

Regards

James

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

Join us for PuppetConf <http://www.bit.ly/puppetconfsig>, September 22nd
and 23rd in Portland, Oregon, USA.

-- 
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 Tue, Jul 26, 2011 at 9:21 AM, James Turnbull
<james@puppetlabs.com>wrote:
> Jared Curtis wrote:
> > Any plans to support other cloud providers? Specifically VMWare?
> >
>
> Jared
>
> There are such plans.  Obviously it''s also open source so
we''ll add some
> further support and hopefully the community will chime in with other
> updates and enhancements that they require.
>
>
We''re also very much aware that this isn''t a fully pluggable
and extensible
system as it stands, and we''re going to be redesigning a bunch of the
underlying code to make it much simpler to support all sorts of
environments.

We will be seeking input from the community, cloud providers, interested
third parties etc for this design, and even more ideally we''ll get
people
interested in contributing actual code.

Look for a call for input/feedback in the not too distant future once
we''ve
got more people using it.


-- 
Nigel Kersten
Product Manager, Puppet Labs

*Join us for **PuppetConf *
<http://www.bit.ly/puppetconfsig>
Sept 22/23 Portland, Oregon, USA.
*
*

-- 
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.