A machine image is not the only deployment model to be sure, but is the kind of deployment model you need if you're offering something as a cloud service. I'm a big fan of the AWS Marketplace which of course is based on this kind of model. (I'm also about to make the stand-alone Myrrix server available this way as a test of this model.)
On Thu, May 3, 2012 at 6:06 PM, Nicholas Kolegraff <[email protected]>wrote: > Assumed this question was coming. > I had given this a lot of thought. > I have this crazy notion that nothing should ever be installed and > bootstrapping is really annoying. > I felt it was easier to just launch an AMI.....yet again, why not just > repackage another image. > > The automated build nature of what I do requires me to repackage some lower > level libraries so they can link easily and stably (is that a word?) across > multiple packages. > I also have some longer term objectives that will require me to have > complete control over the kernel and packaging. > It just seemed easier to start my own thing for this. > > Agree, this could prove insane. If that is the case, it wouldn't be *too* > hard for me to convert this to some package repo > >
