Re: Juju 2.0-beta9 ETA

On 10/06/16 19:20, Cheryl Jennings wrote: > - Addition of a `juju unregister` command to remove references to > controllers Seems we have two different cases * the opposite of register * the opposite of bootstrap Why not just remove-controller and remove-account ? Mark -- Juju-dev mailing l

Re: Juju 2.0-beta9 ETA

On the upgrade front, I think we should relax until we are comfortable calling something an RC. The reality is we are still making changes, I am concerned that making an upgrade promise too early will just slow down our ability to make changes we deem necessary before 2.0. I understand there are

Re: Juju 2.0-beta9 ETA

On 12/06/16 22:43, Tim Penhey wrote: > On 12/06/16 21:00, Mark Shuttleworth wrote: >> From an upgrade point of view, I would focus on the migration >> capability, because that provides the cleanest semantics. If we have >> everything we need there and upgrades happen to

Re: Juju 2.0-beta9 ETA

On 13/06/16 13:56, Rick Harding wrote: > I've felt like the least oddball of things was to tie the command to > remove the entry to the command you used to add it and so we've been > running with unregister. +1 At one stage we were using login with different parameters instead of register; I'm c

Re: Juju 2.0-beta9 ETA

On 13/06/16 14:35, Ian Booth wrote: > The above are model commands. So we need a way to set foo=bar on the > controller > itself (ie update the shared controller wide config). What are you proposing? > Did you intend that setting foo on the controller model would satisfy the > requirement? That se

Re: Juju 2.0-beta9 ETA

On 14/06/16 08:33, Ian Booth wrote: >> That's why I prefer: >> >> set-controller-config >> set-model-config >> set-model-default >> > I like the above too. But some folks we've talked to have thought that > introducing 3 commands (the ones above) is cognitive overhead. Heh. Ian, if you like, an

Beta9

Hi all Just to say, initial impressions of beta9 are great, the status output cleanup is super, thank you! Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: "juju attach"

We can change a CLI until RC, and its good for us to debate them. Here are the guiding principles. * shorter is better, much much better * we strongly prefer one word to always mean the same thing * we strongly prefer a unique verb to a common-verb-plus-noun For the latter reason I prefer no

Re: "juju attach"

On 18/06/16 16:45, Marco Ceppi wrote: > > Why not just "add" which is already pretty well used. Throughout the > Juju CLI. > Well, I think the context here is more attach-a-disk. I really like Roger's suggestion of 'mount', it immediately brings all the right elements into focus, and it's only one

Re: Windows and --race tests are now gating

On 11/07/16 09:26, Aaron Bentley wrote: > But is this week really any different from any other week? Won't there > always be something critical that has to land? I think it's fine to make it a plan that we will have Windows tests on for 2.0 GA, but at the moment we're focused on all the breaking

Re: model-migration feature branch has been merged into master

Thank you for steering it home, this will be a huge step forward for horizontal scalability and upgrade reliability. Mark On 19/07/16 06:52, John A Meinel wrote: > > Yay. Very good to hear. > > John > =:-> > > > On Jul 19, 2016 06:39, "Tim Penhey" > wrote: > >

Re: Juju API change - new ModelConfig facade

Thanks Ian, nice to see the change articulated clearly in advance with guidance as to how to accommodate it. Mark On 25/07/16 07:57, Ian Booth wrote: > In juju master, and landing with the next beta, 3 methods are moved off the > Client facade and now exist on a new ModelConfig facade: > > - Mod

Re: No help Topics in 2.0

Good catch Nate. Mark On 27/07/16 05:08, Nate Finch wrote: > Juju 1.x had a ton of help in the CLI, right at your fingertips: > > $ juju1 help topics > azure-provider How to configure a Windows Azure provider > basics Basic commands > commandsBasic help for all comm

Re: Juju stable 1.25.6 is released

On 27/07/16 11:35, Martin Packman wrote: > A stable release of Juju, juju-core 1.25.6, is now available. > This release replaces version 1.25.5. Thank you! Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-

Re: Schema for Juju RPC messages

On 27/07/16 19:43, Reed O'Brien wrote: > +1 > > On Wed, Jul 27, 2016 at 9:52 AM, Katherine Cox-Buday > > wrote: > > > I am a huge fan of publishing schema's and then generating SDKs > and documentation websites off of them. It brings your API close

Re: Schema for Juju RPC messages

On 28/07/16 05:30, Tim Penhey wrote: > Just doing this would catch the typos of keys, and would also make us > be more strict in the "I'll just add this extra field" to existing > facade versions, as they could then fail with older versions of the > server with "unknown field" type errors. Sounds

Re: Schema for Juju RPC messages

On 28/07/16 10:42, roger peppe wrote: > On 28 July 2016 at 01:07, Rick Harding wrote: >> However, an API client in any language should never be auto generated. > This is a strong statement. I feel that, as with most things in > software engineering, > there's a trade-off. Personally I'm with Kathe

Re: Schema for Juju RPC messages

On 28/07/16 12:57, roger peppe wrote: > On 28 July 2016 at 10:01, Mark Shuttleworth wrote: >> On 28/07/16 10:42, roger peppe wrote: >>> On 28 July 2016 at 01:07, Rick Harding wrote: >>>> However, an API client in any language should never be auto generated. >>

Re: Interactive bootstrap has landed

On 28/07/16 11:39, John Meinel wrote: > AIUI, the idea is that if you are not supplying the bootstrap target, > then we don't know what you want to create, so we might as well ask. > If you start supplying arguments (even incomplete ones), then we'll > expect that you were intending to tell us, and

Re: Schema for Juju RPC messages

On 28/07/16 13:47, roger peppe wrote: > I agree with that. But we're talking about sugar here, I think. Added > sugar doesn't *necessarily* imply a cleaner, less messy or better > articulated component IMHO. That's one of the reasons I like Go - more > layers of abstraction can make things harder t

Re: RFC: time to remove the "smart" output formatter?

On 09/08/16 18:47, William Reade wrote: > Kill it! > > ...except in hook tools, which I think we want to keep the same lest > we break charms. > That means (1) we don't remove the code or the bugs or the maintenance, and (2) those charms never get fixed :) I suggest we turn it off behind a featur

Re: Latest new about Juju master branch - upload-tools obsoleted

On 15/08/16 08:27, Ian Booth wrote: > So if you pull master you'll no longer need to use upload-tools. > Juju will Do the Right Thing*, when you type: Thanks Ian, this is a lovely simplification. Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https:

Re: Juju snap edge channel enabled

On 16/08/16 15:01, Nicholas Skaggs wrote: > Following up on Ian's work to remove the need for --upload-tools, I've > enabled daily publishing to the edge channel for the juju snap. The > snap utilizes this work so the snap 'just works' as expected. A new > snap is generated and published once a day

Re: juju-1.25.6 on xenial not using lxd containers

Hi Daniel The transition from "1.0 everything" to "2.0 everything" is significant. 1.x Juju, 1.x MAAS and 1.x LXC all line up pretty well, as do 2.x MAAS, 2.x LXC/D, and 2.x Juju. Crossing wires between those is not very easy at the moment - we do intend to provide upgrade mechanisms but are focu

Re: juju-1.25.6 on xenial not using lxd containers

On 01/09/16 10:17, John Meinel wrote: > > 1.25 does not support LXD managed containers as it uses the old > lxc-foo CLI to manage containers (lxc-start is not the same as "lxc > start"). > juju-2.0 will use LXD managed containers but there are no plans to > backport that support to 1.25 > To be cl

Re: JUJU Charm Certification

On 09/09/16 14:31, SivaRamaPrasad Ravipati wrote: > > I have a question. Can we do [MAAS+OpenStack base bundle] Setup on > Virtual machines?. (Or) Can We do [MAAS+OpenStack base bundle] Setup > on Single server? > It is possible to install openstack-on-openstack, or openstack-on-public-cloud, or

Re: JUJU Charm Certification

On 13/09/16 08:29, SivaRamaPrasad Ravipati wrote: > Hi marcoceppi, > > Here we are doing vertical Scaling. I mean same copy of the charm > deployed multiple times to a single cinder node. every time it will > add unique backend per charm to the same cinder node. This OK. > > But If I want to do Hor

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 generat

Re: Bootstraping Rackspace

On 19/09/16 23:36, James Beedy wrote: > Thanks, Mark! By interactive bootstrap, do you mean interactive > add-credentials? If so, I think it already exists for RAX, but isn't quite > spot on yet. It looks like I should be able to get bootstrapped with the > information contained in the bug link

Re: Timeout added to kill-controller

"--with-fire" :) Mark On 27/09/16 00:54, Tim Penhey wrote: > Hi all, > > NOTE: we do very much consider it a bug if the models don't die properly. > > I have just landed a fix for a kill-controller issue where it would > just sit there for a long time with nothing apparent happening. > > Now kil

Re: List plugins installed?

On 28/09/16 17:45, roger peppe wrote: > I've voiced discomfort with this before - I don't think that we should > arbitrarily run all executables that happen to have a "juju-" prefix. > It's potentially dangerous (for example, note that although git relies heavily > on plugins, it doesn't execute a

Re: Juju GUI 2.2.0 released!

Congrats folks, and *great* video Jeff! Mark On 03/10/16 09:58, Jeff Pihach wrote: > We’re pleased to announce the latest feature release of the Juju GUI. > > With the GA of Juju 2 release coming very soon we’re ready to unveil > the new enhanced model management in the Juju GUI. The new GUI all

Re: Juju 2.0-rc3 is here!

On 07/10/16 09:58, Adam Israel wrote: > It looks like rc3 introduced a minor change in the status output. Each > unit has an asterisk next to its name, i.e., mariadb/0* (full output > in pastebin). What is the asterisk meant to represent? > > http://pastebin.ubuntu.com/23289710/ I believe thats le

Re: Juju 2.0-rc3 is here!

On 07/10/16 11:49, Adam Israel wrote: > One potential way to display the information, using existing > whitespace so we're not changing the overall layout. > > http://pastebin.ubuntu.com/23290044/ Yeah, I like that, Though I would do it as: Unit (*leader) Workload ... If we're touching that co

Re: Juju 2.0-rc3 is here!

On 07/10/16 13:59, Curtis Hovey-Canonical wrote: > Tell the juju controller to use devel streams. Eg, to upgrade my own > deployment, I I set the streams to devel, then upgrade the controller > than the hosted model. Guys, there should be no devel streams in 2.0. One stream, with all releases, *

Re: Big memory usage improvements

On 12/10/16 22:39, Menno Smits wrote: > Christian (babbageclunk) has been busy fixing various memory leaks in > the Juju controllers and has made some significant improvements. Chris > (veebers) has been tracking resource usage for a long running test > which adds and removes a bunch of models and

Re: Juju 2.0 is here!

Congrats everyone, this is a release to be proud of. Multi-user multi-model, great CLI, it's a joy to train people on it. Well done. Mark On 14/10/16 06:34, Nicholas Skaggs wrote: > Juju 2.0 is here! This release has been a year in the making. We’d > like to thank everyone for their feedback, te

Re: AWS US East (Ohio) Region now supported for Juju 2.x

On 20/10/16 17:15, Aaron Bentley wrote: > To use it with 2.0.0, just run "juju update-clouds" once. You will see > the message: > Updated your list of public clouds with 1 cloud region added: > > added cloud region: > - aws/us-east-2 > > After that, the new region will work the same as

Re: Bootstrap Constraints

On 30/10/16 19:34, James Beedy wrote: > > Problem: Multiple 3rd party/vendors need access to application > environments and infrastructure. Network address space not segregated > correctly - no way to separate bootstrap controller from app env > subnets/spaces. Juju already has the concept of netw

Re: Support AWS EIP

On 05/11/16 17:42, James Beedy wrote: > How does everyone few about extending the AWS provider to support elastic ips? > > Capability to attach eips using juju would alleviate one more manual step I > have to preform from the aws console every time I spin up an instance. > > I have created a featu

Re: Juju 2.1-beta1 is here!

Thank you guys! Those folks who have access to VSphere, please do test this and file any relevant bugs. A good clean bootstrap on VSphere is a fine way to start every Kubernetes :) Mark On 18/11/16 19:05, Curtis Hovey-Canonical wrote: > A new development release of Juju, 2.1-beta1, is here! > >

Re: Deployment Oversight

Super difficult to document 'the ocean', there will always be fraying at the edges that what worked on clouds fails in the manual case. Mark On 28/11/16 15:49, Rick Harding wrote: > That's very true on the items that are different. I wonder if we could > work with the CPC team and note the thing

Re: Deployment Oversight

On 28/11/16 17:21, Merlijn Sebrechts wrote: > > What I suggest is that you stop trying to make Juju work in 'the > ocean' and focus the manual environment efforts on one thing: a > multi-machine LXD provider. *Fix the LXD networking and DNS issues and > tell everyone to only use LXD containers in a

Re: Deployment Oversight

On 28/11/16 21:53, James Beedy wrote: > Perfect deploys across lxd, ec2, and manual providers! > > EC2 - http://paste.ubuntu.com/23551492/ > LXD - http://paste.ubuntu.com/23551496/ > Manual - http://paste.ubuntu.com/23551498/ That's how we like it :) -- Juju-dev mailing list Juju-dev@lists.ubunt

Re: [charms] Barbican + Identity Standalone - AWS

Might be worth sharing this on some of the OpenStack lists too, for folks who are interested in using Horizon this way on other substrates. Mark On 29/11/16 21:36, James Beedy wrote: > Another great day of Juju driven successes - deploying the barbican > standalone stack for identity mgmt and se

Re: Application names starting with digits

On 02/12/16 07:46, Adam Collard wrote: > It'd be nice to have full Unicode support in both charm and > application names. Steady on, that would make it easy to have misleading charm names, or ones that are very difficult for people to type. I don't mind lifting the restriction on up-front digits,

Re: Application names starting with digits

On 02/12/16 09:23, Adam Collard wrote: > True, but we could do normalisation in the charm store to prevent > malicious names. I think it's an important aspect of software in the > modern world that it can support the wide array of languages that we > humans use. This just transfers the definition

Re: A (Very) Minimal Charm

On 09/12/16 06:32, John Meinel wrote: > > 1. "charm push cs:~jameinel/ubuntu-lite" fails ultimately with a TLS > timeout error: > ERROR cannot post archive: Post > https://api.jujucharms.com/charmstore/v5/~jameinel/ubuntu-lite/archive?.. > >

Re: A (Very) Minimal Charm

On 16/12/16 07:33, Katherine Cox-Buday wrote: > Tim Penhey writes: > >> Make sure you also run on LXD with a decent delay to the APT archive. > Open question: is there any reason we shouldn't expect charm authors to take > a hard-right towards charms with snaps embedded as resources? I know one o

Re: A new development release of Juju, 2.1-beta4, is here!

As we push to Juju 2.1 there are a couple of items that would be really good to get testing feedback on! On 06/01/17 15:06, Nicholas Skaggs wrote: > Model Migration is no longer behind a feature flag 'Model migration' is key to ongoing easy and automatic upgrades on the server. By migrating the

Re: RFC "bootstrap --config" should be treated as "--model-default" and add "--model-config"

Why do we have bootstrap-constraints as a weird and different constraint, when we are intending to represent the controller services as apps with endpoints in the controller model anyway? Surely these are normal constraints on those apps? Mark On 26/01/17 11:56, John Meinel wrote: > So we know h

Re: RFC "bootstrap --config" should be treated as "--model-default" and add "--model-config"

On 26/01/17 23:39, Andrew Wilkins wrote: > On Thu, Jan 26, 2017 at 9:16 PM Mark Shuttleworth <mailto:m...@ubuntu.com>> wrote: > > > Why do we have bootstrap-constraints as a weird and different > constraint, when we are intending to represent the controller >

Re: New in 2.1-beta5: Prometheus monitoring

On 07/02/17 10:59, Andrew Wilkins wrote: > Eventually, we intend for Juju itself to be described within the > model. When that is reality, it would be sensible for the Juju > controller application to have an endpoint for unauthenticated HTTP > access to metrics. You could then just bind that to a

Re: Juju 2.1.0, and Conjure-up, are here!

On 24/02/17 11:30, Andrew Wilkins wrote: > On Fri, Feb 24, 2017 at 6:15 PM Adam Collard > mailto:adam.coll...@canonical.com>> wrote: > > On Fri, 24 Feb 2017 at 10:07 Adam Israel > mailto:adam.isr...@canonical.com>> wrote: > > Thanks for calling this out, Simon! We should be shouting

Re: User Groups

On 08/03/17 07:52, James Beedy wrote: > Managing users with Juju currently does not scale. Can we associate > users with groups please? > > Find bug here -> https://bugs.launchpad.net/juju/+bug/1671149 Yes, this is on-roadmap. Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify sett

Re: Juju 2.2-alpha and conjure-up, are here!

On 16/03/17 14:19, Curtis Hovey-Canonical wrote: > ## How do I get it? > > If you are running Ubuntu, you can get Juju from the juju stable ppa: > >sudo add-apt-repository ppa:juju/devel; sudo apt-get update > >sudo apt-get install juju > > Or install Juju from the snap store: > >snap i

Re: Consuming MongoDB from a Snap

On 26/07/17 15:51, Felipe Reyes wrote: > Some users run the controller in fairly big bare metal machines (e.g. > 128G of RAM, I've seen even bigger controllers) and it won't be easy for > them to have an extra machine to setup a new controller and run model > migration, if their controller is HA th

Re: Consuming MongoDB from a Snap

On 31/07/17 01:34, Michael Hudson-Doyle wrote: > On 23 June 2017 at 11:47, Menno Smits > wrote: > > We've had some discussion this week about whether Juju could use > MongoDB from snap instead of a deb. This would make it easier for > Juju to stay up t

Re: No more non-voting tests

Thank you guys, that's exactly the right move. Mark On 02/08/17 22:48, Chris Lee wrote: > Hi All, > > Today we made the change to remove any "non voting" tests and make > them all voting. > > The non-voting test failures weren't being reviewed, there where many > that were passing and some that

Re: Effect of lease tweaks

Just to say the analytical approach is exactly right, thanks for setting the pace. Mark -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Juju 2.3 beta2 is here!

On 11/02/2017 04:56 AM, Chris Lee wrote: > > A new development release of Juju is here, 2.3-beta2. > 2.3 is looking great, and is worth a test run for those of you with larger models and an interest in cross-model relations. > ## New and Improved > > * Deploying bundles can now target existing m

Re: Juju 2.3 beta2 is here!

On 11/07/2017 03:11 PM, John Meinel wrote: > ... >   > > > Perhaps just: > > > >   juju deploy --map-machines A=B,C=D > > > > ... or some variant of that? > > > > Let's use the betas to refine and condense and clarify. > > +1 to that. I'm wondering if use-existing-ma

Re: Serverless Model Type

Yes, this is a very natural evolution for Juju. I think the concept of 'scale' is fundamentally different in serverless environments or models, but many of the other concepts in Juju map neatly and we can plan to get there. I also think that the different serverless implementations are much less c

Re: VMWare support in 2.3-rc1.1

Hi Merlijn Thanks for the feedback. Having 2.3.0 be good on VMware is very valuable for us. Have these issues been addressed in the RCs? Mark On 11/22/2017 09:53 AM, Merlijn Sebrechts wrote: > Hi all > > > I've been trying out Juju 2.3-rc1.1 on VMware. Good work on this, we > were finally able t

Re: Juju 2.3-rc2 is here!

On 12/06/2017 02:51 PM, Nicholas Skaggs wrote: > Is your agent stream set to released per chance? > > juju model-config -m controller > > If so, your client won't see the agent binaries as they aren't in the > release stream (2.3 isn't yet released). I wonder if we can be more user friendly about

Re: juju deploys with a vsphere controller using hardware vm version 10

Seems we should support a range of widely used versions, rather than only the latest. Mark On 02/07/2018 04:24 AM, Ian Booth wrote: > Hi Daniel > > The Juju vSphere provider currently only supports hardware version 10, but 14 > is > now the most recent according to the VMWare website. If we wer

Re: More juju upgrade-juju failings

I think this UX on the upgrade process has obvious problems. Nobody should have to guess at what to do, in which sequence. Can I suggest that we have a shared Google doc to mock up a nice experience starting with the simple command 'juju upgrade' which then walks people through the process, inclu