Juju on existing VM

[Andrew Wilkins]

Hi Ibha,

There have been a bunch of manual provisioning bugs fixed in 1.17.0 and
1.17.1.

I *think* you need to set default-series in your environment for this
particular problem. I would recommend moving to 1.17.1, though.

Cheers,
Andrew


On Fri, Jan 24, 2014 at 2:14 PM, Gandhi, Ibha (HP Software) <ibhag at hp.com>wrote:

>  Thanks Kapil. I tried giving the IP address of the VM in same network.
>
>
>
> When I run juju bootstrap, I get this error:
>
> 2014-01-24 06:12:58 INFO juju.environs.manual bootstrap.go:67 Filtering
> possible tools: 1.16.5-precise-amd64;1.16.5-precise-i386
>
> 2014-01-24 06:12:58 ERROR juju.tools list.go:113 cannot match
> tools.Filter{Released:false, Number:version.Number{Major:0, Minor:0,
> Patch:0, Build:0}, Series:"raring", Arch:"amd64"}
>
> 2014-01-24 06:12:58 ERROR juju supercommand.go:282 no matching tools
> available
>
>
>
> Please advise.
>
>
>
> Thanks,
>
> Ibha
>
>
>
> *From:* Kapil Thangavelu [mailto:kapil.thangavelu at canonical.com]
> *Sent:* Thursday, January 23, 2014 3:59 PM
>
> *To:* Gandhi, Ibha (HP Software)
> *Cc:* John Arbash Meinel; Juju email list
>
> *Subject:* Re: Juju on existing VM
>
>
>
> Juju provides for manual placement so that you can place a workload on an
> existing machine within an environment without provisioning a new machine..
> ie juju deploy  charm --to=existing_machine   it also supports creating
> containers (either lxc or kvm) to run those workloads in isolation from the
> host (see juju deploy --help for more details). This is also supported for
> add-unit --to=existing_machine.
>
>
>
> If you want to setup a single machine environment with a workload and the
> capacity to grow on virtual machines using manual provisioning in
> conjunction with manual placement makes this use case relatively
> straightforward.
>
>
>
> configure a 'null' aka manual environment in environments.yaml pointing to
> the ip address of the vm (don't use localhost but the ip address that other
> machines in the environment will use). Then juju bootstrap. Then juju
> deploy charm --to=0.
>
>
>
> cheers,
>
>
>
> Kapil
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Jan 23, 2014 at 1:55 AM, Gandhi, Ibha (HP Software) <ibhag at hp.com>
> wrote:
>
> Thanks John for the quick reply.
>
>
> -----Original Message-----
> From: John Arbash Meinel [mailto:john at arbash-meinel.com]
> Sent: Thursday, January 23, 2014 12:13 PM
> To: Gandhi, Ibha (HP Software); Juju email list
> Subject: Re: Juju on existing VM
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2014-01-23 10:33, Gandhi, Ibha (HP Software) wrote:
> > Hi,
> >
> >
> >
> > I want to deploy application on a specific VM and don?t want to
> > provision a new VM.
> >
> > This is something I have been doing with chef, please let me know if
> > it?s possible to deploy
> >
> > application on a particular VM through juju without provisioning a new
> > one.
> >
> >
> >
> > Thanks,
> >
> > -Ibha
>
> We are currently polishing some work we call "manual provisioning"
> where you have a machine, which you then add into an existing environment.
> The syntax is something like:
>   juju add-machine ssh:user at host
>
> I believe that work isn't very polished in the latest stable release
> (1.16.5) but is quite a bit better in our current unstable snapshot
> (1.17.0) and should be polished for the next stable (1.18).
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.13 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlLgufsACgkQJdeBCYSNAANpEgCbBTV0vD7DXjzQCy4VWQqHVS37
> voMAn3uLE4lwV+9ZvmWpOCQw4BP3sbGv
> =pb7H
> -----END PGP SIGNATURE-----
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140129/3fe09a12/attachment.html>