[ec2-beta] Some suggestions

[Joel Natividad]

Eric Hammond wrote:

> Joel Natividad wrote:
> >  * Include ec2-ami-tools in image by default.
>
> Frequently requested, not yet possible, but folks are working on the legal
> issues.
>
> In the meantime, it is possible to apt-get install the ec2-ami-tools
> package from Intrepid multiverse which makes it pretty easy.


Yes.  But it wasn't mentioned in the Starter's Guide and I only stumbled on
it when I tried installing the python-vmbuilder-ec2 package mentioned in the
EC2 FAQ.  Hope people don't mind but I thought that it merited a mention in
the Starter's Guide and added it in the wiki.


>
>
> >  * On firstboot, perhaps give an option to create an Elastic Block
> > Store Volume.
>
> Does this mean that you like the current menu on first ssh that prompts you
> to install common server software?  Most of the feedback so far has
> indicated this gets in the way of setting up and running EC2 instances.
>
> The prompt seems useful the first couple times, but when starting dozens of
> instances over months do you think you'd still want this required step if
> the same functionality were also available by typing a command when you
> needed it?
>
> (sorry, I had difficulty asking in an unbiased manner, but I do think folks
> would be interested in hearing opposing views :) )
>

Hey, that's what I love about OSS communities!  So no offense taken.  Its
only through considered discussions do we distill the best solutions :)

Anywhoo, to the topic of firstlogin, I refer back to the ec2-ami-tools
package as part of the default.  In my mind, the typical use-case is to use
the Ubuntu EC2 images, customize it, then create your own private AMI.

Firstlogin will only truly be first login and won't show up again after the
Ubuntu EC2 image has been customized (which makes a case for some firstlogin
clean-up scripts)

>
>
> > * If EBS option is selected, create scripts to automount EBS volume on
> > boot
>
> Automounting EBS volumes is something folks are often asking for on the EC2
> forum.  However, if I understand what you're describing, it would require an
> additional layer of information storage above what EC2 currently provides.
>
> RightScale adds this concept where a specific "server" maps to an image,
> plus packages, plus startup scripts, plus EBS volumes, etc. but they have to
> keep track of these mappings in their own systems.
>

Which leads back to the landscape EC2 integration.  Looking at the case for
landscape, perhaps it can have greater success and penetration in the
enterprise if it is cloud-enabled.  Even for me, a big fan of Ubuntu in the
Enterprise, the pitch for landscape is not that compelling having done
similar stuff like patches, updates, etc. using Webmin.

However, if landscape becomes Cloud-aware, it makes it easier for me to
pitch it to the CFO/CEO since it now becomes much greater than an
infrastructure management solution, but a quick way to move the Cloud and
control cost.

And yes, if Canonical does decide to go this direction, perhaps they will
need to store maps, packages, scripts in landscape.

Along these lines, some other "pipe dream" idears:
 * ability to prep AMI image offline in Xen and then "transconfigure" it as
it "ascends" into the cloud (sorry, can't help the metaphors :) )

* ability to move images on and off the cloud (Xen<->AMI).

 * ability to create base configuration image running in local Xen
hypervisor, and when certain thresholds are met, additional capacity can be
provisioned  using the same image in EC2.


-- 
=======================================================
joel at natividads.com * wireless at natividads.com
Think Different! (http://en.wikipedia.org/wiki/Think_different#Text)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/mailman/private/ec2/attachments/20090121/5f8e4e32/attachment-0001.htm