One last note. If you are going to build a template with a hardcoded password you need to make use of whirr.bootstrap-user (or whirr.login-user in 0.7.0) to let Whirr know how to login to the VMs.
See http://whirr.apache.org/docs/0.7.0/configuration-guide.html On Mon, Feb 13, 2012 at 11:43 PM, Andrei Savu <[email protected]> wrote: > Hi Steve, > > The focus in Apache Whirr is to make use (as much as possible) of vanilla > OS installs. We want to support both systems based on apt-get and on yum. > So far we've done most of our testing on Ubuntu 10.04 LTS but everything > should also work on an AMI like Amazon Linux. > > So if you create a template based on the standard Ubuntu 10.04 ISO > everything should work out of the box. > > This is the related JIRA issue, I've done some work on this in the past: > https://issues.apache.org/jira/browse/WHIRR-182 > > Let me know if I can help in any way as you make progress on this. > > -- Andrei Savu / andreisavu.ro > > > On Mon, Feb 13, 2012 at 11:29 PM, Steve Salevan > <[email protected]>wrote: > >> Hey guys, >> I'm building some VM images to enable Whirr to work on top of Eucalyptus, >> and I was wondering if you guys could point me to any documentation or >> code/scripts which you use to build out the EC2 and Rackspace images for >> each of the Whirr VM roles (hadoop-namenode, hadoop-datanode, zookeeper, >> etc.). >> >> Thanks very much for the consideration! >> -Steve Salevan >> [email protected] >> > >
