[charms.reactive] http relation.available gets called on upgrade-charm hook, gives error.

Hi all I have the following piece of code that reacts to the httprelation.available hook (called rest2jfed in this case): @when('rest2jfed.available') def setup_rest2jfed(rest2jfed): hostname = rest2jfed.host() port = rest2jfed.port() # Do some stuff with hostname and port

Re: Juju-gui options: read-only and juju-gui-console-enabled

Hi Rick, thank you for this! I thought the console was a web-console where you could execute juju commands. This would be a great feature, I think. Kind regards Merlijn Op maandag 26 oktober 2015 heeft Rick Harding het volgende geschreven: > Howdy Merlijn. The team

Re: How to make Juju High Availability work properly?

Hi Mark & Marco, Really appreciate your help. I have already provide the logs to Marco. Hope it could help you to enhance the Juju HA feature. Sincerely yours, Leon On Sat, Oct 24, 2015 at 7:03 AM, Mark Shuttleworth wrote: > On 23/10/15 00:54, 曾建銘 wrote: > > Was the juju

Missing contrib.amulet in charm-helpers-hooks

Openstack-Charmers, I am hitting an error when shared-db-relation-changed executes, where it cannot create a logger due to https://bugs.launchpad.net/charms/+source/glance/+bug/1509540 . I found the cause of this issue, and is

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

On 24/10/15 04:05, Aaron Bentley wrote: > bzr has a similar feature, but the problem with such a feature is that > it can break scripts that expect the normal behaviour. That's why bzr > provides a --no-aliases option, which all scripts calling bzr should use. > > The same applies to Juju. If

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

On 24/10/15 00:40, Rick Harding wrote: > > > On Fri, Oct 23, 2015 at 12:12 AM Tim Penhey > wrote: > > Hi folks, > > Firstly, the ability to specify default flags for commands: > status = status --format=tabular > >

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

On 23/10/15 21:28, roger peppe wrote: > On 23 October 2015 at 05:12, Tim Penhey wrote: >> Hi folks, >> >> I scratched a personal itch yesterday and added the ability for users to >> specify their own aliases for juju commands. >> >> There are two primary use cases that I

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

Hi Wayne, While I can see your point of view, I do disagree. While it may be of no benefit to you, it doesn't mean that others will not find it useful. I believe it is useful to have one format to specify aliases, one that doesn't depend on the shell that you use. The overhead in complexity

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

What is the advantage of this over using a standard alias in my shell profile? On Fri, Oct 23, 2015 at 11:05 AM, Aaron Bentley wrote: > bzr has a similar feature, but the problem with such a feature is that > it can break scripts that expect the normal behaviour.

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

After looking at this and the code more, I find myself very against this feature. This adds code to core that is performing a tasks that most people already know is handled by their shell. Even our Windows users can install PowerShell and have aliases for commands. This adds no benefit to core, it

Re: How to make Juju High Availability work properly?

Thanks for following up! We will take a look at the logs and get back to you soon. --Mark Ramm On Mon, Oct 26, 2015 at 4:41 AM, 曾建銘 wrote: > Hi Mark & Marco, > > Really appreciate your help. I have already provide the logs to Marco. > > Hope it could help you to enhance the

Juju sessions for next week's Ubuntu summit

Hello everyone! Ubuntu is having an online summit next week and I've scheduled some sessions for us: http://summit.ubuntu.com/uos-1511/track/cloud/ Basically Wednesday will be our heavy day, with a day's worth of content, and then an office hours the day after to catch up any loose ends. All

[ANN] charm-tools 1.8.0

Hello everyone! I'm happy to announce another charm-tools release today, this is the 1.8.0 which succeeds 1.7.1 as the latest release of charm-tools. As always, you can verify the version you are running by executing: `charm version` # Changes ca0f40c [Benjamin Saller] fix issue with multiple