Re: Increasing the size of VERSION in tabular status output

On 19/09/16 08:09, James Page wrote: > Could this field be expandable on demand? I think our longest example > would currently be: > > 13.0.0~rc1 (10 chars) Yes I think it could be expandable and would suggest up to 14 chars with truncation in the middle. Mark -- Juju mailing list

Re: Bootstraping Rackspace

On 19/09/16 16:19, James Beedy wrote: > I am trying to bootstrap the rackspace provider and cannot seem to get > past "ERROR failed to bootstrap model: no image metadata found". Do I > need to generate metadata for rackspace provider? I feel like I need > to get some images in rackspace and

Re: Bootstraping Rackspace

On 19/09/16 16:19, James Beedy wrote: > I am trying to bootstrap the rackspace provider and cannot seem to get > past "ERROR failed to bootstrap model: no image metadata found". Do I > need to generate metadata for rackspace provider? I feel like I need > to get some images in rackspace and

Re: Bootstraping Rackspace

James, what good timing. The streams with image info is just going through getting setup. https://bugs.launchpad.net/juju/+bug/1625243 It took a bit for the images for trusty/xenial to get setup and the team's working to make it all work out of the box. We had demo streams up for testing and

Re: Increasing the size of VERSION in tabular status output

Yesterday we changed the limit to 15 from 7. Tim On 20/09/16 04:41, Rick Harding wrote: The primary trouble is that we really want to enforce a limit so that there's room for the arbitrary text at the end of the same line. I think we could try 10. I do think we need that hard cutoff. If you

Bootstraping Rackspace

I am trying to bootstrap the rackspace provider and cannot seem to get past "ERROR failed to bootstrap model: no image metadata found". Do I need to generate metadata for rackspace provider? I feel like I need to get some images in rackspace and generate the image metadata using the image ids for

Bootstraping Rackspace

I am trying to bootstrap the rackspace provider and cannot seem to get past "ERROR failed to bootstrap model: no image metadata found". Do I need to generate metadata for rackspace provider? I feel like I need to get some images in rackspace and generate the image metadata using the image ids for

Re: Specify lxd container bridge

This was a custom build to verify a fix from the team today. It wasn't distributed. The team is working to land the changes today for the RC1 release tomorrow now that it's been verified to work for a couple of folks. On Mon, Sep 19, 2016 at 4:52 PM Ryan Beisner

Re: Specify lxd container bridge

Where can I get fresh RC builds? On Mon, Sep 19, 2016 at 1:52 PM, Corey Bryant wrote: > I just wanted to follow up on this thread to say I tested with a > pre-release of juju rc1 and it fixed up the issues I was hitting. > > On Sat, Sep 17, 2016 at 9:04 AM, Dimiter

Re: Specify lxd container bridge

I just wanted to follow up on this thread to say I tested with a pre-release of juju rc1 and it fixed up the issues I was hitting. On Sat, Sep 17, 2016 at 9:04 AM, Dimiter Naydenov < dimiter.nayde...@canonical.com> wrote: > Hey Corey, > > That specific error I haven't seen at that stage -

Re: Snap layer for Juju reactive charms

Thanks Stuart! This is huge. Snaps are a great way to deliver the software that composes a charm. And charms are a great way to put those snaps to good use. With both teams working together we can make a consistent and smooth story to grow the adoption. I'm eager to start playing with your layer.

Re: Increasing the size of VERSION in tabular status output

The primary trouble is that we really want to enforce a limit so that there's room for the arbitrary text at the end of the same line. I think we could try 10. I do think we need that hard cutoff. If you need to see the full value going to the json/yaml format output should display the full value.

Re: Increasing the size of VERSION in tabular status output

I'm not sure if the unicode ellipsis would cause table alignment issues depending on your terminal and font. We could consider it as it does give quite a few characters back. The longest I can come up with that doesn't feel just gratuitous is 15 10.10.10alpha10 But that might be going to far. I do

Re: Increasing the size of VERSION in tabular status output

Perhaps also using the utf-8 ellipsis (…) would save some characters as well. --Greg On Mon, Sep 19, 2016 at 10:09 AM, James Page wrote: > Hi All > > We've been experimenting with the new application-version-set feature in > Juju 2.0 in the OpenStack charms team; it

Re: Feedback wanted: Changes to the Ubuntu Charm

Obsoleted, their aliases eventually removed On Mon, Sep 19, 2016, 4:03 AM Ryan Beisner wrote: > On Fri, Sep 16, 2016 at 2:00 PM, Marco Ceppi > wrote: > >> I am the upstream (for this charm) and this is an entire rework of the >> charm