I would actually just use MaaS + LXC or KVM virtualization.
You should be able to bring up a MaaS environment, and then do:
juju deploy NEWSERVICE --to lxc:10
And Juju will create a new LXC container on machine 10 and deploy the
NEWSERVICE into it.
That gives you all the "give me baremetal" when
Notice that volume which is attached is a *new* volume. The reason is
because we are booting the images that use elastic block storage,
rather than only local temp files.
So yes, when you create new instances, you will see new volumes that
are mounted automatically. When those instances are destroy
Fantastic! Looks like streams.canonical.com is also nice and updated.
John
=:->
On Fri, Mar 21, 2014 at 5:03 AM, Curtis Hovey-Canonical
wrote:
> juju-core 1.17.6
>
> A new development release of Juju, juju-core 1.17.6, is now available.
>
>
> Getting Juju
>
> juju-core 1.17.6 is available for tru
juju-core 1.17.6
A new development release of Juju, juju-core 1.17.6, is now available.
Getting Juju
juju-core 1.17.6 is available for trusty and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Upgrading from stable releases to development rele
Is this expected? Notice one of my volumes is attached after the bootstrap
node comes up. The ec2-tools and aws dashboard show the same thing.
I've never seen this behavior before (I haven't looked that much), but I'm
having trouble finding anything other than the -b option to ec2-run-instances
I was chatting with some awesome people in #juju, but having trouble
deciding what to do. I was hoping that people with more juju experience
could tell me the right way to go for what I want to do, or if juju is just
a horrible idea in general and I should do something else.
I have spent a few day
Hello,
We have been following juju over the last few months @Orange with intense
interest and would like to be able to use it.
We just love the service approach that juju offers compared to other tools (we
use Chef right now)
Our problem is that we have a cloud based on CloudStack and we cannot
