Edison,

A couple of questions for you:

1 - It looks like you are using password-based authentication for the
scp command (changed in lib/vagrant/ssh.rb ).  Am I reading that
change correctly?  I think we can get away with using the vagrant
"user" and standard vagrant public / private keys (including the
requirement to allow the vagrant user to run anything via sudo with no
password).

2 - Did you happen to reach out to the Vagrant project folks to see if
the copy via ssh support for the puppet provisioner would be accepted?
 I think it would be great to upstream this patch via a pull request
to the mitchellh/vagrant repo!

I'll install this patched version of Vagrant and start testing against
the puppet config I'm working on.

-chip

On Fri, Jul 20, 2012 at 1:23 AM, Edison Su <edison...@citrix.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Thursday, July 19, 2012 1:17 AM
> > To: cloudstack-dev@incubator.apache.org
> > Subject: Re: Update on wrapping DevCloud into a Vagrant Box
> >
> > On Mon, Jul 16, 2012 at 9:10 PM, Edison Su <edison...@citrix.com> wrote:
> >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > > Sent: Friday, July 13, 2012 8:17 AM
> > > > To: cloudstack-dev@incubator.apache.org
> > > > Subject: Re: Update on wrapping DevCloud into a Vagrant Box
> > > >
> > > > On Thu, Jul 12, 2012 at 6:17 PM, Edison Su <edison...@citrix.com>
> > wrote:
> > > > > If automate doesn't work, document it?,..
> > > >
> > > > I'm going to pivot a bit here, and aim for the following:
> > > >
> > > > 1 - Unattended Ubuntu 12.04 installation, per Edison's specs.
> > > > 2 - Puppet manifest to describe handle the pre-configuration phase.
> > > > 3 - Puppet manifest to provision the post-configuration phase.
> > >
> > > Hi Chip, the ubuntu 12.04 build is fixed. You can check out the
> > latest
> > > master branch, "./waf deb" will build deb packages under
> > artifacts/debbuild
> > >
> > > >
> > > > We can use the unattended install and puppet manifests in a number
> > of
> > > > different ways, which might include a Vagrant provisioning config
> > in
> > > > the future.
> > > >
> > > > Folks from Citrix - The puppet manifest for cloudstack is hosted on
> > > > Github still [1].  It's README file says that it's GPL (but also
> > has a
> > > > commentary about how manifests are probably not copyrightable).
> > > > Anyone have an issue using this as a starting point for step 3
> > above?
> > > >
> > > > [1] https://github.com/CloudStack/puppet-cloudstack
> > >
> > >
> > Fantastic!
> >
> > My "work-in-progress" is on GitHub here:
> > https://github.com/chipchilders/CloudStack/tree/master/tools/devcloud
> >
> > Specifically, please review the conversion of the devcloudsetup -p
> > process
> > to a "puppet-devcloudinitial" puppet module.
> >
>
> Vagrant is been fixed, without Addon, we can still provision devcloud.
> Get the last code vagrant code from: https://github.com/sudison/vagrant
> My sample Vagrantfile:
>   config.vm.provision :puppet do |puppet|
>      puppet.manifests_path = "puppet"
>      puppet.manifest_file  = "init.pp"
>      puppet.with_ssh       = true
>      puppet.pp_path        = "/opt/puppet"
>   end
>
> During "vagrant provision", vagrant will copy puppet/init.pp to 
> /opt/puppet/manifest/ before execute puppet on devcloud.
>
> > -chip
>

Reply via email to