Those instructions are indeed out of date. The correct attribute name is now
tools-metadata-url.
Having said that, Canonistack, along with AWS, HP Cloud, Azure is supported to
run Juju releases from PPA out-of-the-box without the need to upload any tools
or set the URL to locate the tools. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joey
>
> I'm curious to know if there is any reliable mechanism to detect a
> cowboyed change inside a juju environment and then report them.
>
> A non-juju synonym of what I'm trying to accomplish would be with puppet
> managing a system's /etc
Hi Stein
This does appear to be a bug in Juju's constraints handling for EC2.
I'd have to do an experiment to confirm, but certainly reading the code
appears to show a problem.
Given how EC2 works, in that Juju asks for the specified root disk size
when starting an instance, I don't have a wor
>
>
> On Thu, May 29, 2014 at 8:26 PM, Ian Booth wrote:
>
>> Hi Stein
>>
>> This does appear to be a bug in Juju's constraints handling for EC2.
>> I'd have to do an experiment to confirm, but certainly reading the code
>> appears to show a problem
On 05/09/14 09:02, David Britton wrote:
> Hi juju folks --
>
> I'm using MAAS + Juju to do some testing behind a firewall with LXCs. I
> want to accelerate the download of the large images that I am
> downloading from cloud-images.ubuntu.com.
>
> I see that MAAS has cloud images. Ideally, I'd
On 10/11/14 11:32, Michael Nelson wrote:
> On Fri, Nov 7, 2014 at 3:19 PM, Andrew Wilkins
> wrote:
>> Hi Sameer,
>>
>> The behaviour changed a few months ago to address a bug:
>> https://bugs.launchpad.net/juju-core/+bug/1353442
>>
>> Is this causing you problems, or were you just surprised/curi
On 10/11/14 11:43, José Antonio Rey wrote:
> Correct me if I'm wrong, but I'm seeing this targeted for 1.22?
>
You are correct, but it's also been targeted to 1.21-beta1 milestone.
>>
>> Note that for the EC2 case, using the DNS name for the unit's public address
>> has
>> been reported as a b
Hi Cory
This is part of what we are planning to deliver for this cycle as part of the
storage work. We also plan on being able to provide the container with access to
block devices eg loopback, either in container's filesystem or on the host
machine.
On 17/01/15 02:11, Corey Bryant wrote:
> Hi
>
> For the past year I have been charming in AWS t1.micro instances. These
> have been great resources, and allowed me and others to get started with
> charming and knowing the ecosystem. However, I have recently found out that
> the support for this instance type has been basically deprecated, a
Hi Peter
I seem to recall that at one time, the upgrade-juju command could fail to
determine implicitly what tools version it could upgrade to. A quick bug search
revealed this bug
https://bugs.launchpad.net/juju-core/+bug/1447899
The bug is fixed in the recently released 1.25-alpha1.
What you
Hi Peter
There's a lot to respond to in your email - I'll summarise the key points up
front.
Firstly, let me briefly explain a little about how the tools tarballs are
handled in Juju. I'll cover bootstrap as well as upgrades, just for
completeness, even though you are just upgrading.
Each machi
On 12/09/15 23:49, Peter Grandi wrote:
> Apologies for the late reply, I spent most the time in between
> reverse engineering some issues with other ("hipsterish")
> clusterized services.
>
> In the meantime I have written and just now uploaded my own
> draft overview of how Juju is structured,
+1 to what Stuart says below about container creation.
Plus, I have found just today in testing that about 1 in 4 times, the
provisioning simply fails silently. ie a new container is supposed to be started
to deploy a charm into, but nothing happens. lxc list shows nothing and the
machine remains
Login was bumped to v3 to prevent accidental logins from older Juju clients
which may appear to connect successfully but then fail later depending on what
operations are performed.
It also allows the "this version is incompatible message". This was done for 1.x
clients logging into Juju 2.0 server
The lxd cloud works on Juju 2.0 beta1 out of the box.
$ juju bootstrap mycontroller lxd
There is no need to edit any clouds.yaml. It Just Works.
It seems the confusion comes from not seeing lxd in the output of juju
list-clouds. list-clouds ostensibly shows available public clouds (aws, azure
et
2/16 09:21, Marco Ceppi wrote:
> Won't the user be able to create different LXD clouds by specifying a
> remote LXD host though?
>
> On Sun, Feb 21, 2016, 12:19 AM Ian Booth wrote:
>
>> The lxd cloud works on Juju 2.0 beta1 out of the box.
>>
>> $ juju bootstrap
t bootstrap instance: can't get info
for image 'ubuntu-trusty': json: cannot unmarshal string into Go value of type
int64
https://bugs.launchpad.net/juju-core/+bug/1547268
Also affects Juju 2.0 alpha2
On 21/02/16 16:46, Mark Shuttleworth wrote:
> On 21/02/16 00:18, Ian Booth
The admin user tag for aws is the same as described below. The @local suffix
pertains to the controller not the cloud - think of it as users for a controller
you bootstrap yourself are local to that controller.
On 27/02/16 11:29, Adam Stokes wrote:
> Thanks that makes sense now. I don't have aws o
On 01/03/16 11:25, Adam Stokes wrote:
> On Mon, Feb 29, 2016 at 7:24 PM, Tim Penhey
> wrote:
>
>> On 01/03/16 03:48, Adam Stokes wrote:
>>> Is there a way to list all models for a specific controller?
>>
>> Yes.
>
>
> Mind pointing me to the api docs that has that capability?
>
https://godo
to list the
>>> models for? The only way I can see is to manually `juju switch
>>> ` then re-login to the API and run the AllModels method. Is
>>> there a way (as an administrator) to specify which controller you want
>>> to list the models for?
>>&
ml" ? I'd really like to avoid tying 3rd party scripts to our
> on-disk configuration. We can keep CLI compatibility, but on-disk
> structures aren't something we really want to commit to forever.
>
> John
> =:->
>
> On Tue, Mar 1, 2016 at 8:22 AM, Ian Booth w
This is awesome news. I just wanted to acknowledge the tonne of extra work done
by the GUI folks for the GUI to support all of the API changes introduced by
Juju 2.0. Can't wait to try out the new GUI with the next Juju beta2 due out
this week (next day or so).
On 11/03/16 07:06, Jeff Pihach wrote
On 18/03/16 05:12, Adam Stokes wrote:
> Hi!
>
> Could I get this bug added to the list too?
>
> https://bugs.launchpad.net/juju-core/+bug/1554721
>
That bug is on the list for sure. We're aiming for beta3 but it could likely
slip. It will be fixed before 2.0. The priority is the feature backlo
Another feature which will be in the next beta is support for keystone 3 in
Openstack.
On 18/03/16 04:51, Rick Harding wrote:
> tl;dr
> Juju 2.0 beta3 will not be out this week.
>
> The team is fighting a backlog of getting work landed. Rather than get the
> partial release out this week with the
tonio Rosales wrote:
> + Juju list for others awareness
>
>
> On Thu, Mar 10, 2016 at 1:53 PM, Ian Booth wrote:
>> Thanks Rick. Trivial change to make. This work should be in beta3 due next
>> week.
>> The work includes dropping support for local repositories in favo
Mar 28, 2016 at 9:45 PM Antonio Rosales <
> antonio.rosa...@canonical.com> wrote:
>
>>
>>
>> On Monday, March 28, 2016, Ian Booth wrote:
>>
>>> Hey Antonio
>>>
>>> I must apologise - the changes didn't make beta3 due to al
On 03/05/16 23:09, Andreas Hasenack wrote:
> On Wed, Apr 20, 2016 at 7:07 PM, Andrew Wilkins <
> andrew.wilk...@canonical.com> wrote:
>
>> On Thu, Apr 21, 2016 at 2:44 AM Andreas Hasenack
>> wrote:
>>
>>> Hi,
>>>
>>> I was trying to add another "cloud" so that I could have multiple MAAS
>>> ser
On 03/05/16 23:16, Andreas Hasenack wrote:
> On Tue, May 3, 2016 at 10:09 AM, Andreas Hasenack
> wrote:
>
>> On Wed, Apr 20, 2016 at 7:07 PM, Andrew Wilkins <
>> andrew.wilk...@canonical.com> wrote:
>>
>>> On Thu, Apr 21, 2016 at 2:44 AM Andreas Hasenack
>>> wrote:
>>>
Hi,
I was
On 03/05/16 23:55, Andreas Hasenack wrote:
> On Tue, May 3, 2016 at 10:28 AM, Ian Booth wrote:
>
>>
>> The syaml referred to above is for cloud definitions. The command being
>> run is
>> for adding a credential. The credential data model is different to clouds.
On 08/06/16 23:59, roger peppe wrote:
> On 8 June 2016 at 10:41, Andrew Wilkins wrote:
>> Hi folks,
>>
>> We're in the midst of making some changes to model configuration in Juju
>> 2.0, separating out things that are not model specific from those that are.
>> For many things this is very clear-
Just to provide a little more clarity on the Azure issue.
The recent Azure SDK update changed the Azure behaviour as exposed to Juju. We
were previously not waiting for machines to be marked as fully provisioned; the
SDK now does this for us. MS says this is what you must do. The effect on Juju
is
Hi Sergio
Courtesy of Rick Harding, here's the information you need.
The openstack provider has a network configuration attribute which needs to be
set to specify the network label or UUID to bring machines up on when multiple
networks exist.
You pass it as an argument to bootstrap. eg
$ juju b
0/16 00:26, sergio gonzalez wrote:
> Hello Ian
>
> Thanks for your support. Where can I find all the configuration
> options to be passed during bootstrap?
>
> Regards
>
> Sergio
>
> 2016-10-13 15:58 GMT+02:00 Ian Booth :
>> Hi Sergio
>>
>> Courtesy o
As part of the cross model relations work, the provider interface is being
reworked such that Open/Close Port() API calls can now take as parameters
ingress rules, ie a collection of port ranges and allowed source CIDRs.
With the above work, it will be possible to use that new provider
capability
On 11/04/17 07:11, Daniel Bidwell wrote:
> I need to add openstack as a cloud to juju 2.1.2-xenial. I don't seem
> to find the right howto. What authentication method do I use? And
> where do I get the authentication string? User name and password for
> dashboard user?
>
The authentication m
FWIW, Juju itself still sets JUJU_UNIT_NAME
https://github.com/juju/juju/blob/develop/worker/uniter/runner/context/context.go#L582
On 23/05/17 05:59, James Beedy wrote:
> Juju 2.1.2
>
> I'm getting this "JUJU_UNIT_NAME not in env" error on legacy-non-reactive
> xenial charm using service_name()
Indeed. And just landing today is support for btrfs as well. So there'll be a
choice of:
lxd (the default, directory based)
lxd-zfs
lxd-btrfs
On 14/07/17 13:46, Menno Smits wrote:
> Nice work Andrew! These changes make Juju's storage support much more
> powerful.
>
>
>
> On 13 July 2017 at 20:5
On 24/07/17 20:02, Paul Gear wrote:
> On 08/07/17 03:36, Rick Harding wrote:
>> As I noted in The Juju Show [1] this week I've put together a blog
>> post around the cross model relations feature that folks can test out
>> in Juju 2.2. Please test it out and provide your feedback.
>>
>> http://m
On 24/07/17 23:12, Ian Booth wrote:
>
>
> On 24/07/17 20:02, Paul Gear wrote:
>> On 08/07/17 03:36, Rick Harding wrote:
>>> As I noted in The Juju Show [1] this week I've put together a blog
>>> post around the cross model relations feature that folks can
t; Is possibile to scale out some units using cross models?
>>
>> For instance: in a onpestack tenant i deploy a kubernates cluster. Than in
>> another tenant i add k8-workers, the add-unit command will refer to the
>> parent deployment to get needed params (i.e. master IP addres
Hi folks
TL;DR; I want to rename a yaml/json attribute in network-get output. I want to
see if any charmers would find this to be an issue. IIANM, we don't (yet) have a
tool to easily scrape the charm store to see what charms use network-get
directly. Charm helpers calls network-get with the --pri
Hey
The -m argument is what you want. It accepts wither just a model name or a
controller:model for when you have multiple controllers. eg
$ juju status -m prod
$ juju status -m ctrl:prod
The first command above works on the prod model on the current controller. The
second selects a specific con
After many months of effort, we're pleased to announce the release of the first
beta for the upcoming Juju 2.3 release. This release has many long requested new
features, some of which are highlighted below.
Please note that because this is a beta release (the first one at that), there
may likely
Copying in the Juju list also
On 12/10/17 22:18, Ian Booth wrote:
> I'd like to understand the use case you have in mind a little better. The
> premise of the network-get output is that charms should not think about public
> vs private addresses in terms of what to put into relat
On 19/10/17 15:22, John Meinel wrote:
> So at the moment, I don't think Juju supports what you're looking for,
> which is cross model relations without public addresses. We've certainly
> discussed supporting all private for cross model. The main issue is that we
> often drive parts of the firewa
On 19/10/17 16:33, Ian Booth wrote:
>
>
> On 19/10/17 15:22, John Meinel wrote:
>> So at the moment, I don't think Juju supports what you're looking for,
>> which is cross model relations without public addresses. We've certainly
>> discussed suppor
Of the top of my head, you want to do something like:
$ juju create-storage-pool ssd-disks maas tags=ssd
$ juju deploy postgresql --storage pgdata=ssd-disks,32G
The above assumes you have tagged in MAAS any SSD disks with the "ssd" tag. You
can select whatever criteria you want and whatever tags
Thanks for raising the issue - we'll get the docs updated!
On 01/11/17 07:44, James Beedy wrote:
> I knew it would be something simple and sensible :)
>
> Thank you!
>
> On Tue, Oct 31, 2017 at 2:38 PM, Ian Booth wrote:
>
>> Of the top of my head, you want to do
>
> Here machines 1 and 2 are deployed without the `--constraints`,
> http://paste.ubuntu.com/25862219/
>
>
> Am I missing something? Possibly like one more input to the `--storage` arg?
>
>
> Thanks
>
> [0] https://jujucharms.com/u/jamesbeedy/elasticsearch/27
>
:
>>
>> Yes, deploying without —storage results in a successful deploy.
>>
>>> On Oct 31, 2017, at 7:52 PM, Ian Booth wrote:
>>>
>>> And just to ask the obvious: deploying without the --storage constraint
>>> results
>>> in a successful
> * Parallelization of the Machine Provisioner
>>
>> Provisioning of machines is now faster! Groups of machines will now be
>> provisioned in parallel reducing deployment time, especially on large
>> bundles. Please give it a try and let us know what you think.
>>
>> Benchmarks for time to deplo
On 08/12/17 09:39, Micheal B wrote:
> Looks great here other than the LDX on VMware which is what I need or at
> least part of it is. Wanting to run containerized openstack in kubernetes on
> vmware. Unless someones has a better idea, I could try.
>
Sorry about that issue. This LXD on VMWare
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 were simply to track
and support the most recent hardware version, would that work for you?
On 05/02/18 12:38, Daniel Bidwell wrote:
> Is there any
A new development release of Juju is here, 2.4-rc3.
This release candidate addresses an issue upgrading from earlier Juju versions
as described below.
## Fixes
An upgrade step has been added to initialise the Raft configuration. This would
normally be done at bootstrap time but needs to be done
54 matches
Mail list logo
