Re: charm build -s centos7 does nothing special?

I would imagine it would be something like that, but I don't actually know how 'series' is wired into the charm build tool. John =:-> On Wed, May 24, 2017 at 4:35 AM, fengxia wrote: > Interesting. So you mean the diff is really depending on what I put in > scripts. If so, my

Call for testers: preview of persistent storage support

Hi folks, One of the things we're working on for the 2.3 release (not 2.2!) is persistent storage. What this means is the ability to detach storage from a unit, and reattach it to another unit keeping the storage contents intact. We would like to get some feedback before this all gets set in

Call for testers: preview of persistent storage support

Hi folks, One of the things we're working on for the 2.3 release (not 2.2!) is persistent storage. What this means is the ability to detach storage from a unit, and reattach it to another unit keeping the storage contents intact. We would like to get some feedback before this all gets set in

Re: charm build -s centos7 does nothing special?

Interesting. So you mean the diff is really depending on what I put in scripts. If so, my immediate thought is that charm build does nothing special for series then, since I'm coding the "if series=='ubuntu'... else:", the build script cannot touch my code, right? On 05/20/2017 03:17 AM,

Re: JUJU_UNIT_NAME no longer set in env

On 23 May 2017 at 14:12, Jay Wren wrote: > I was under the impression that `juju run --unit` does run in a hook > context. In fact, the help for `juju help run` explicitly says: > ah yes, sorry, I missed the --unit bit. -- Nick Veitch, Documentation Canonical --

Re: JUJU_UNIT_NAME no longer set in env

juju run --application runs as every unit of the application, thus we have individual units (if you have 2 units of an application on a machine it will run twice on that machine). 'juju run --unit" obviously runs as a unit. 'juju machine' can't, because we don't have any unit associated with it.

Re: JUJU_UNIT_NAME no longer set in env

I was under the impression that `juju run --unit` does run in a hook context. In fact, the help for `juju help run` explicitly says: ``` Commands run for applications or units are executed in a 'hook context' for the unit. ``` A quick test: ``` > juju run --unit u4/0 'echo $JUJU_UNIT_NAME'

Re: JUJU_UNIT_NAME no longer set in env

On 23 May 2017 at 11:23, Junien Fridrick wrote: > > You can run some hooks like config-changed with e.g. : > > $ juju run --unit foo/0 hooks/config-changed > You can run any hook like that, but if it requires a hook context (as in the example of trying to read

Re: GUI Props

Happy to hear you like the new features in the release, James. You're right, current account page is just a start and we're excited about the things that are yet to come. SSH keys handling is on that list for sure. Thank you and the rest of the community for providing feedback and feature

Re: GUI Props

Happy to hear you like the new features in the release, James. You're right, current account page is just a start and we're excited about the things that are yet to come. SSH keys handling is on that list for sure. Thank you and the rest of the community for providing feedback and feature

Re: JUJU_UNIT_NAME no longer set in env

On Tue, May 23, 2017 at 10:08:45AM +0100, Nick Veitch wrote: > I don't believe you can (usually) execute hooks properly e.g. via 'juju > run' or ssh, precisely because the hook doesn't then run in a hook context. > If you run 'juju debug-hooks' and wait for a hook to fire, then the various > $ENV

Re: JUJU_UNIT_NAME no longer set in env

I don't believe you can (usually) execute hooks properly e.g. via 'juju run' or ssh, precisely because the hook doesn't then run in a hook context. If you run 'juju debug-hooks' and wait for a hook to fire, then the various $ENV variables should be available in that session.

Re: JUJU_UNIT_NAME no longer set in env

So you're running the 'install' hook directly, are you currently in a 'juju debug-hooks' session, or are you just changing into that directory? Juju sets it during the run of a charm hook, but it is not set globally on the machine (we can't set UNIT globally anyway, because you can colocate many