Juju architecture questions - nonprovider

[Clint Byrum]

Excerpts from Thomas Leonard's message of 2012-09-21 07:16:53 -0700:
> On 2012-09-20 10:41, Thomas Leonard wrote:
> > On 2012-09-17 17:57, Clint Byrum wrote:
> >> Excerpts from Thomas Leonard's message of 2012-09-17 02:06:03 -0700:
> > [...]
> >>> It's also usually uncertain where we will be deploying, so being able to
> >>> handle several different cloud types is useful. Often there is no cloud at
> >>> all, so having something which could deploy LXC containers over a fixed set
> >>> of existing machines would be very useful (like an extended "local"
> >>> deployment method).
> >>>
> >>
> >> I've often thought about a more static "nonprovider" environment type
> >> where the addresses of machines are just listed somewhere and SSH is
> >> used to install the juju agents. It comes up often enough, I think its
> >> time we put this on our "experiments to try soon" list.
> >>
> >> https://bugs.launchpad.net/juju/+bug/1052065
> >
> > OK, I had a look into this. How should the cloud init stuff work? For EC2,
> > EC2LaunchMachine creates a CloudInit and passes that to the new machine,
> > which causes everything to be installed and the machine agents started.
> [...]
> 
> OK, I've got a prototype of this working now:
> 
>    bzr branch lp:~tal-it-innovation/juju/provided
> 
> Using this I was able to follow the tutorial to deploy mysql + wordpress 
> onto a pre-allocated machine.

I haven't tried it yet Thomas, but this is very exciting! Thanks for
taking the initiative, and I'm excited to try it out over the next
couple of days.  You're certainly not the first person to want this,
but definitely the first to put some code out there for it. :)