Juju Digest, Vol 43, Issue 3
Nilaxan Satgunanantham
snilaxan at gmail.com
Wed Aug 6 06:42:29 UTC 2014
Hi All,
# Can please explain the following status of juju charms and let me know
the steps to create those.
1. installed
2. started
# I have created a juju charms, Installed and running locally fine. but
still the charms status colour is yellow (In Juju-Gui)
please explain it as well ?
Thanks
Best Regards
S.Nilaxan
On Tue, Aug 5, 2014 at 5:30 PM, <juju-request at lists.ubuntu.com> wrote:
> Send Juju mailing list submissions to
> juju at lists.ubuntu.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ubuntu.com/mailman/listinfo/juju
> or, via email, send a message with subject or body 'help' to
> juju-request at lists.ubuntu.com
>
> You can reach the person managing the list at
> juju-owner at lists.ubuntu.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Juju digest..."
>
>
> Today's Topics:
>
> 1. Re: Manual juju upgrade (Curtis Hovey-Canonical)
> 2. Re: Manual juju upgrade (John Meinel)
> 3. Re: generate a local file during execute of my charm
> (Gaurav Pandit)
> 4. RE: generate a local file during execute of my charm
> (Sameer Zeidat)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 4 Aug 2014 08:01:38 -0400
> From: Curtis Hovey-Canonical <curtis at canonical.com>
> To: Juju email list <juju at lists.ubuntu.com>
> Subject: Re: Manual juju upgrade
> Message-ID:
> <
> CAHXxHLu5DhYMztJx_uLOi7_f+HU4i1LbEik-Te19iFpvE6_zmA at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On Mon, Aug 4, 2014 at 8:00 AM, Curtis Hovey-Canonical
> <curtis at canonical.com> wrote:
> > On Mon, Aug 4, 2014 at 6:36 AM, Henning Eggers <henning at keeeb.com>
> wrote:
> >> Hi,
> >>
> >> I have a couple of machines running an older juju version (1.16.6 on
> precise)
> >> and I cannot manage them through my current workstation installation
> (1.20.1
> >> on trusty). I get errors like "no such request "FullStatus" on Client"
> and now
> >> even a panic and stackdump (that's new).
> >>
> >> The environment only has 4 units. Since I cannot run (or rather don't
> dare to
> >> run) upgrade-juju right now, can I upgrade them manually through ssh
> somehow?
> >> Does the control bucket or environment file need upgrading, too?
> >
> > I think you need to upgrade in stable minor steps.
> > 1.16.6 > 1.18.4
> > 1.18.4 > 1.20.1
> >
> > The juju client and server APIs evolved rapidly between 1.12.0 and
> > 1.18.0. The client-server combinations only work in single minor
> > version hops. The API used by the client is stable as of 1.18 and
> > future clients can have large hops, but the servers still upgraded in
> > single hops so that the envs are upgraded in the proper order.
>
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 4 Aug 2014 16:17:12 +0400
> From: John Meinel <john at arbash-meinel.com>
> To: Curtis Hovey-Canonical <curtis at canonical.com>
> Cc: Juju email list <juju at lists.ubuntu.com>
> Subject: Re: Manual juju upgrade
> Message-ID:
> <CAHE3fn5F5KXD=
> 7X03kmPNWbdMFkfti9wRmfBfCnwrrVHHgELLQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> There are ways to do an upgrade manually if you take a lot of care.
> However, I think if you did "juju upgrade-juju --version=1.18.4" you'll
> provide yourself more of the sanity and safety around the upgrade than
> trying to reproduce all of the steps that we recorded inside of juju.
>
> If you really want to work it out for yourself:
> https://github.com/juju/juju/blob/master/upgrades/steps118.go
> Is the list of steps that need to be done to upgrade something from 1.16 to
> 1.18, and AFAIK there aren't any explicit steps for upgrading from 1.18 =>
> 1.20.
>
> As far as "stable only upgrades with 1 hop" that is only true up to 1.18.
> >From 1.18 onward the new client should remain compatible with 1.18 for the
> foreseeable future. (So 1.20, 1.21, 1.22, etc should all continue to work
> with a 1.18 server.)
>
> John
> =:->
>
>
>
>
> On Mon, Aug 4, 2014 at 4:01 PM, Curtis Hovey-Canonical <
> curtis at canonical.com
> > wrote:
>
> > On Mon, Aug 4, 2014 at 8:00 AM, Curtis Hovey-Canonical
> > <curtis at canonical.com> wrote:
> > > On Mon, Aug 4, 2014 at 6:36 AM, Henning Eggers <henning at keeeb.com>
> > wrote:
> > >> Hi,
> > >>
> > >> I have a couple of machines running an older juju version (1.16.6 on
> > precise)
> > >> and I cannot manage them through my current workstation installation
> > (1.20.1
> > >> on trusty). I get errors like "no such request "FullStatus" on Client"
> > and now
> > >> even a panic and stackdump (that's new).
> > >>
> > >> The environment only has 4 units. Since I cannot run (or rather don't
> > dare to
> > >> run) upgrade-juju right now, can I upgrade them manually through ssh
> > somehow?
> > >> Does the control bucket or environment file need upgrading, too?
> > >
> > > I think you need to upgrade in stable minor steps.
> > > 1.16.6 > 1.18.4
> > > 1.18.4 > 1.20.1
> > >
> > > The juju client and server APIs evolved rapidly between 1.12.0 and
> > > 1.18.0. The client-server combinations only work in single minor
> > > version hops. The API used by the client is stable as of 1.18 and
> > > future clients can have large hops, but the servers still upgraded in
> > > single hops so that the envs are upgraded in the proper order.
> >
> >
> >
> > --
> > Curtis Hovey
> > Canonical Cloud Development and Operations
> > http://launchpad.net/~sinzui
> >
> > --
> > 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/20140804/b40b1a36/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Mon, 4 Aug 2014 09:13:37 -0400
> From: Gaurav Pandit <pandit.gaurav at gmail.com>
> To: Ilisia Felane <felane.ili at gmail.com>
> Cc: Juju email list <juju at lists.ubuntu.com>
> Subject: Re: generate a local file during execute of my charm
> Message-ID:
> <
> CAHZWmqrT_bKnbSVYQKTxg5hnxc1Q5M0N69BcadKVuPTCtBciTw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I am looking for exactly the same functionality.
> In my case, I am looking for ways to copy a predefined config file on to,
> say machine 1 from somewhere locally (machine 0?). Currently, I am using
> "here-doc" in the shell script to create such config files during the charm
> install/relationship change steps, but being able to copy it without having
> to put it up on the internet can be very helpful.
>
> Thanks
> Gaurav
> On Jul 30, 2014 5:30 AM, "Ilisia Felane" <felane.ili at gmail.com> wrote:
>
> > Hi,
> >
> > I create a charm to deploy a application, but I need to recover
> > information about installing as OS installed, some open port, and other
> > system information.
> >
> > Is it possible to get this information on my machine running juju? If
> yes,
> > how can I get this information automatically on my provision machine
> > during the execution of my charm ?
> >
> > best regards,
> > Felane
> >
> > --
> > 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/20140804/fceadf23/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Tue, 5 Aug 2014 09:15:29 +1000
> From: Sameer Zeidat <sameerz at yahoo.com>
> To: Gaurav Pandit <pandit.gaurav at gmail.com>, Ilisia Felane
> <felane.ili at gmail.com>
> Cc: Juju email list <juju at lists.ubuntu.com>
> Subject: RE: generate a local file during execute of my charm
> Message-ID: <1697.11456.bm at smtp108.mail.bf1.yahoo.com>
> Content-Type: text/plain; charset="utf-8"
>
> Your charm can inject a public ssh key in root's authorized keys file and
> use the private key in any of your hooks to scp files around.
>
> Regards,
> Sameer
>
> -----Original Message-----
> From: "Gaurav Pandit" <pandit.gaurav at gmail.com>
> Sent: ?4/?08/?2014 11:14 PM
> To: "Ilisia Felane" <felane.ili at gmail.com>
> Cc: "Juju email list" <juju at lists.ubuntu.com>
> Subject: Re: generate a local file during execute of my charm
>
> I am looking for exactly the same functionality.
> In my case, I am looking for ways to copy a predefined config file on to,
> say machine 1 from somewhere locally (machine 0?). Currently, I am using
> "here-doc" in the shell script to create such config files during the charm
> install/relationship change steps, but being able to copy it without having
> to put it up on the internet can be very helpful.
>
> Thanks
> Gaurav
> On Jul 30, 2014 5:30 AM, "Ilisia Felane" <felane.ili at gmail.com> wrote:
>
> Hi,
>
>
> I create a charm to deploy a application, but I need to recover
> information about installing as OS installed, some open port, and other
> system information.
>
> Is it possible to get this information on my machine running juju? If yes,
> how can I get this information automatically on my provision machine during
> the execution of my charm ?
>
>
> best regards,
>
> Felane
>
>
> --
> 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/20140805/171ee1e1/attachment-0001.html
> >
>
> ------------------------------
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
> End of Juju Digest, Vol 43, Issue 3
> ***********************************
>
--
Best Regards,
S.Nilaxan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140806/470a7dbf/attachment.html>
More information about the Juju
mailing list