.
Please make sure to try it out and file bugs at
https://github.com/CanonicalLtd/jujucharms.com/issues
I want to thank the team for their hard work on this update!
--
Rick Harding
Juju UI Engineering
https://launchpad.net/~rharding
@mitechie
--
Juju mailing list
Juju@lists.ubuntu.com
Modify
. If you're willing a bug report
we can assign Luca, I mean the UX folks :) would be useful and we can get
them that feedback from outside folks.
--
Rick Harding
Juju UI Engineering
https://launchpad.net/~rharding
@mitechie
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings
-release-jan-14th/
Rick Harding
Juju UI Engineering
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Note that this is pre-support for a new feature in Juju 1.21 which is not
yet released. This is multiple users accessing the same deployed
environment and doesn't seem to quite match the requirements.
Rick Harding
On Mon, Jan 19, 2015 at 4:50 AM, Vahric Muhtaryan vah...@doruk.net.tr
wrote
-- Forwarded message --
From: Jeff Pihach jeff.pih...@canonical.com
Date: May 27, 2015 7:45 PM
Subject: [Juju-gui-peeps] Upcoming GUI release qa request
To: juju-gui-pe...@lists.launchpad.net juju-gui-pe...@lists.launchpad.net
Cc:
Hello peeps,
Tomorrow we're going to be cutting
Definitely think it'd be great to get some sessions going. Some ideas:
reactive framework from ben/cory and maybe some talk through how to join
into the community/guide folks to submitting new layers/stubs
using the big-data solutions to do something interesting, work on the reuse
of existing
Great stuff! Really shows of some great work.
On Fri, Oct 23, 2015 at 11:43 AM Charles Butler <
charles.but...@canonical.com> wrote:
> Greetings!
>
> As some of you may know, we've been talking quite a bit about the new
> emerging patterns in charming, which covers a few new tools, and a
>
Thanks Katherine. That's looking great. One request, next demo I'd be
curious to see how easy it is to run multiple lxd environments locally. I
know it's been possible with lxc before with a bunch of config. Ideally
we'd just be able to create a new named section and say it's lxd and boom,
I can
s locally.
>
> I forgot to mention, Wayne did a great blog post
> <http://waynewitzel.com/2015/11/05/juju-and-remote-lxd-host/> discussing
> using the LXD provider on remote hosts.
>
>
> On 11/09/2015 12:19 PM, Rick Harding wrote:
>
> Thanks Katherine. That's
as a feature
buddy and gets you a copy of the doc as it comes together.
Thanks for the feedback! It's great to see folks excited to use things and
to find guinea pigs as things land and become available.
--
Rick Harding
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
ne-0-lxc-2.maas
> 10.0.0.15
> tdvops@maascontroller:~$ dig +short -x 10.0.0.15
> machine-0-lxc-2.maas.
>
> kind regards
> Pshem
>
>
> On Tue, 3 Nov 2015 at 03:54 Rick Harding <rick.hard...@canonical.com>
> wrote:
>
>> Thanks for the details Andres.
&
Congratulations to the team! This is exciting to see the hard work from
design team putting in a ton of thought into juju and visualizing it, a
year ago, almost the way to the engineering team working so hard to bring
it all to life.
Thank you all for the great tool!
On Wed, Dec 23, 2015, 6:57
Great stuff Chuck and thanks for walking through this Adam. We should
definitely do some more of these and please make sure to share this stuff
out to folks who are interested in what we're up to and things like this
have some great real work examples to work with.
On Thu, Nov 19, 2015 at 6:32
Yes, there's some discussions we've had around letting charms provide
helpful data such as what sub path a url would be on and such. Just
providing a link to the machine:open-port isn't often enough to get the
user directly where they need to be. This also would be best if it could
transfer
The danger I think we've tried to avoid with the get/set is that if you
have just model-config you can accidentally mutate the state by messing up
your arguments you pass in via scripts/etc. It also keeps it consistent
across the read/write across the many things that can change now,
applications,
Thanks Tom, it's interesting to look at the "What can this do for me"
aspect with the current buzzwords and such. I've cc'd Tom from marketing
and Ale from design and will bring it up in the next sprint as they work on
the jujucharms.com design and IA of the site.
On Sat, Jun 4, 2016 at 2:37 PM
Merlijn, this is great and exactly what I've been hoping someone would do
for charms with the new tooling that's been put together.
Personally, we're a heavy jenkins shop internally and know that the best.
Charles did some good work with Drone, but I've not tried it out.
One other thing to think
Thanks Tom, that's a really good point and something we'll take as feedback
and see what we can come up with.
On Sat, Jun 4, 2016 at 2:45 PM Tom Barber wrote:
> Another thing:
>
> Puppet make it very easy to find out how to get platform support:
>
Yes Merlijn, it is and the team is investigating. I'll make sure to reach
out once they triage and report on the time to get things back running.
Thanks for your patience.
On Tue, Jun 14, 2016 at 12:16 PM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Is svg.juju.solutions down? The
Hi Zahra, yes it looks like it should be good to go. The logs demonstrate
that things are setup on 192.168.122.104, the port's are exposed, and the
logs don't seem to have anything that jumps out as a failure to start
something or error there.
According to the logs the service did start up:
Yes, this is the way that subordinates work. They can often do very
intrusive things. Imagine a django subordinate that installs and sets up a
plugin into the django application it's deployed to. We don't currently
support the removal of them. They kind of become one with the principle
t;
>> Awesome!
>>
>> What's the recommended approach for the test bundles? These bundles
>> should use the latest non-published dev version of the Charm. Is there a
>> way to specify this in the bundle or should I recreate the bundle after
>> each push?
>>
>
Not currently. There's a patch in Juju that is in testing to correct this
behavior and to remove the charm. I'd expect it to be in the next 1.25
point release. If you upgrade when that comes out you'll get the behavior
you're looking for.
Thanks for the feedback!
Rick
On Tue, Jun 21, 2016, 5:59
There are the annotations in Juju that aren't used for much but X/Y
coordinates for the GUI to lay out services. There might be something
really interesting in pulling charm metadata into annotations automatically
at deployment time.
On Fri, Jun 17, 2016 at 9:17 AM Ryan Beisner
Merlijn, thanks. I'm going to bet there's an issue with http request sizes
for the charmstore that the charm command talks do as we've got some layers
(Apache, Squid) in front of the actual application. The team is looking
into it. Thanks for giving us the heads up.
On Wed, Jun 15, 2016 at 10:28
Thanks Tim and I want to say that I really appreciate this change. The way
the API exposed the Go-ism that all exported attributes are capitalized has
been annoying for some time. I really appreciate you cleaning that up for
users of the API.
I think the only thing I'd change on this is that we
Appreciate any upvotes of this great post by Jorge.
https://news.ycombinator.com/item?id=11087503
On Fri, Feb 12, 2016 at 9:47 AM Tom Barber wrote:
> Oh Jorge
>
> You make me sad because I know I'll end up formatting my laptop and
> spending ages setting it back up
Thanks James and it was great to meet you in Ghent. I really appreciate
your thoughtful questions, feedback, and obvious excitement for the great
work the team is doing. We look forward to hearing your feedback as we work
to get the 2.0 development releases out to you to try out.
On Fri, Feb 5,
Thanks Andrew.
On Fri, Jan 29, 2016, 8:18 AM Andrew McDermott <
andrew.mcderm...@canonical.com> wrote:
> I will look into this this afternoon for you.
>
> On 29 January 2016 at 13:16, Rick Harding <rick.hard...@canonical.com>
> wrote:
>
>> Sorry dimiter, I know
Sorry dimiter, I know Andrew is out. Can you investigat please?
On Fri, Jan 29, 2016, 8:13 AM Merlijn Sebrechts
wrote:
> Any follow up to this? I'm also interested in using fan with lxc and Juju.
>
> 2016-01-07 19:19 GMT+01:00 Andrew McDermott <
>
Yes it's intended to auto switch for you. If it does not we need to correct
it.
On Wed, Feb 3, 2016, 2:49 PM James Page wrote:
> On Wed, 3 Feb 2016 at 13:23 Mark Shuttleworth wrote:
>
>> On 03/02/16 12:09, James Page wrote:
>> > juju create-model
Thanks for the feedback Patrik and Stuart, I've added a note to look at the
gateway revisions to our next set of discussions.
On Mon, Feb 29, 2016 at 7:00 AM Mark Shuttleworth wrote:
>
> The approach we are discussing in the snappy world is to use "gateway"
> revisions, which
Frank, there's a series of xenial charms for openstack in the -next repo.
You can see the list here:
https://jujucharms.com/q/openstack-charmers-next/?series=xenial
The openstack-base bundle is not there yet, but should be soon. You might
be able to get things working by just taking the
lways help by sponsoring the project
> <http://www.meteorite.bi/products/saiku/sponsorship>)
>
> On 14 February 2016 at 20:46, Rick Harding <rick.hard...@canonical.com>
> wrote:
>
>> It looks like the m4 type is available but seems to not be listed in all
>> regi
I tested this on xenial and it's not there. I've filed a bug for it.
https://bugs.launchpad.net/juju-core/+bug/1547966
To get it going I first created a lxd.yaml file with the config for the lxd
'cloud'.
clouds:
lxd:
type: lxd
Then I added that with
juju add-cloud lxd lxd.yaml
Andreas, yes that's the known bug Ian mentioned due to an API change in
the latest lxd beta3. We'll get that updated ASAP. It works with the lxd
beta2.
On Sun, Feb 21, 2016, 9:29 AM Andreas Hasenack
wrote:
> On Sat, Feb 20, 2016 at 9:18 PM, Ian Booth
Thanks Adam, I'll see what it'll take to get that taken care of.
On Thu, Mar 17, 2016 at 3:12 PM Adam Stokes <adam.sto...@canonical.com>
wrote:
> Hi!
>
> Could I get this bug added to the list too?
>
> https://bugs.launchpad.net/juju-core/+bug/1554721
>
> On Thu, Ma
Thanks Marco, if I understand what we're dealing with is there a pattern
here where we can get a little mix of both worlds?
What I'm wondering is that, if the charm author needs to make these default
changes for a good reason, that we can bring it to user's attention using
the blocked status? Can
Thanks Nate, great stuff. I know there's a lot of folks looking forward to
this helping our charming community out as we fill out the model more and
charms get to adapt and move forward.
On Thu, Mar 17, 2016 at 6:35 PM Nate Finch wrote:
> Yes, it'll be ignored, and the
I believe that went out and is ok Stuart. The charmstore update is deployed
and when you upload a multi-series charm to the charmstore it creates
separate charms that work on older clients. If you hit issues with that
please let me know.
On Mon, Mar 21, 2016 at 8:39 PM Stuart Bishop
been nicer if we had that version info all the time.
On Mon, Mar 21, 2016 at 10:08 AM Rick Harding <rick.hard...@canonical.com>
wrote:
> Thanks Ryan, good point. I'll check with the team. I think, at least in my
> mind, we were very focused on 2.0 feature set, such as resources, and s
Thanks Ryan, good point. I'll check with the team. I think, at least in my
mind, we were very focused on 2.0 feature set, such as resources, and so
anything that needed 2.0 would be in the new world order. Your desire to
actually reach out into the past and implement this via the charmstore for
Thanks Roger, can we get this to the list please and make sure/test that
the message that the client gets back is very clear and perhaps even points
the user to the documentation to the min-juju-version feature so that it's
clear.
Nate, do we have notes on the feature in the devel docs or have
hop wrote:
> > On 22 March 2016 at 11:42, Rick Harding <rick.hard...@canonical.com>
> wrote:
> >> I believe that went out and is ok Stuart. The charmstore update is
> deployed
> >> and when you upload a multi-series charm to the charmstore it creates
> >>
Thanks for the update James, glad things went so well! From our end, we
appreciate the awesome first hand user feedback you're always willing to
reach out and provide. Our stuff just gets better with folks like you
putting it to the test day in and day out. I can't wait to get you some of
the new
Hi Merlijn, that was Steven Baker
The charm looks like it's in his github repo here:
https://github.com/srbaker/neo4j-charm
I don't know what state it's in, but I'm sure it'll be fun to try out.
On Thu, Mar 3, 2016 at 9:26 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Hi all
>
>
The Juju team is working on a feature called "juju resources" that can be
used to provide a blob to a charm to be used in the deployment. It sounds
like it might be interesting as a way to deliver the WAR file to the Tomcat
charm. The current beta1 implemented the local version where you can
Thank Adam. That's good feedback. With tabular output the default now we
should be more verbose on the yaml output and display the uuids and other
data.
On Tue, Mar 1, 2016, 8:37 AM Adam Stokes wrote:
> One of the problems using `juju list-controllers --format yaml`
Awesome, appreciate it.
On Tue, Mar 1, 2016, 8:48 AM Adam Stokes <adam.sto...@canonical.com> wrote:
> Went ahead and filed a bug here:
> https://bugs.launchpad.net/juju-core/+bug/1551743
>
> On Tue, Mar 1, 2016 at 8:40 AM, Rick Harding <rick.hard...@canonical.com>
I know that Gabriel and some of the CloudBase folks seemed interested in
layers and possibly some tooling with powershell. I'm not sure how far that
went but I thought they were experimenting during the charmer's summit.
That would help with a charm build on windows, but not for some common code
Thanks, this is interesting to know. The fact that we've fixed it in
relation set means we have a pattern to move forward with. The team's
slammed on 2.0 work right now, but I've set this up to be something we try
to address across the board after the fact. We'll make sure to look for
other -set
+1 to reserving the juju* space just as we do with relations and such.
On Mon, Mar 28, 2016 at 10:12 PM Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> On Tue, Mar 29, 2016 at 10:03 AM Marco Ceppi
> wrote:
>
>> On Mon, Mar 28, 2016 at 9:49 PM Andrew Wilkins <
rm: /home/ubuntu/charms/trusty/apache-hadoop-compute-slave
>> > However, I got the following error:
>> > ERROR cannot deploy bundle: cannot resolve URL
>> > "/home/ubuntu/charms/trusty/apache-hadoop-compute-slave": charm or
>> > bundle URL has invalid form:
Yes he can
On Wed, Apr 27, 2016, 6:59 AM Andreas Hasenack
wrote:
> On Wed, Apr 27, 2016 at 1:04 PM, John Meinel
> wrote:
>
>>
>>
>> On Wed, Apr 27, 2016 at 6:43 PM, Andreas Hasenack
>> wrote:
>>
>>> On Wed, Apr 27, 2016 at
Yes, bootstrap is intended to be a rare task. Can any of the work done here
be updated to create new models on a single bootstrap controller? Then the
experience is even better with a single create-model call.
On Tue, Apr 26, 2016, 8:42 AM Andreas Hasenack
wrote:
> On
I'd be curious what MAAS folks say. I poked at their API docs and it looks
like you have a call to create a user:
https://maas.ubuntu.com/docs/api.html#users
but to create the api token it seems like a special call "for the currently
logged in user"
How big/long to upload was your resource Tom? I know the team bumped it
while they get some better insight into tracking/quota'ing sizes and I'm
curious where you got denied.
On Mon, Jul 18, 2016, 5:53 PM Tom Barber wrote:
> Awww Merlijn
>
> You got my hopes up
Awesome Tom, let us know if there's a recording or the like. I'd love to
see your presentation but can't make it there myself.
On Wed, Jul 20, 2016 at 11:48 AM Tom Barber wrote:
> Just a heads up folks. I'll be presenting: Flexibility across the cloud -
> Managing and
Robin, there's a few ways to go about it. CephFS has come up with some of
our team and at this time it's not something that folks are relying on
production so I'm hesitant to vote up/down on that.
You question on the NFS charm got me thinking that we do have a storage
subordinate that's been used
Merlijn, nothing at all to apologize for. It's not nitpicking and is a very
true pain point right now. Originally we had planned to have Juju 2.0 out
in Xenial and the default. Xenial is due to be supported for five years and
so there were calls we needed to make to set us up for success looking
Thanks for the feedback Jose. Merlijn also brought up a similar note and I
replied on the main juju list to help explain the current pain window we're
working through. Rather than copy/paste you can see it here:
https://lists.ubuntu.com/archives/juju/2016-August/007679.html
Please let me know if
Narinder, can you share the output of juju status --format=yaml and juju
show-machine 0
On Sat, Feb 4, 2017, 5:15 AM Narinder Gupta
wrote:
> Hi Nicholas,
> I am finding issues when do the deployment. Bundle i used to deploy with
> juju 2.1-beta4 does not get
reenode.net]+1.281.736.5150 <(281)%20736-5150>
> narindergupta2007[skype]
>
> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
>
>
> On Sat, Feb 4, 2017 at 9:20 AM, Rick Harding <rick.hard...@canonical.com>
> wrote:
>
Merlijn, you're correct that when you search for a solution we prefer and
promote the promulgated charms in place of the community ones.
You can find the list of charms for a user directly by clicking on the user
name in that list or going to the user pages which have a /u vs the /q for
query.
On Mon, Jan 16, 2017 at 11:57 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> Hi Jeff
>
>
> I'd like to use lets encrypt certs with the GUI. I'm not sure how to do
> that in a way that I don't break anything. I remember the Charm had config
> options for ssl certs.
>
> Another
On Thu, Aug 18, 2016 at 1:03 PM Stéphane Graber
> Hi Rick,
>
> Hmm, so it looks like Juju itself is parsing the LXD version and failing?
>
> That's a bit weird as I'd have expected it to instead check for the API
> version (1.0) if even checking anything.
>
>
> I've been using the Juju betas with
I wanted to get any feedback on moving the relation information in Juju
status down to the bottom of the list. While it's one of Juju's highlight
features and important to know what's been wired together, with the
coloring it's obvious that the relation section doesn't have that type of
"is it
tl;dr the Juju RC1 is scheduled to be built and released on Tues, Sept 20th
The team would like to let everyone know that there will not be a beta or
RC1 today as usual. The team has been working very hard to address the
outstanding critical issues that need to be corrected before we claim that
Thanks Menno, this is great stuff.
On Thu, Sep 15, 2016, 10:35 PM Menno Smits
wrote:
> Hi everyone,
>
> This is just a quick heads up about an improvement that will be in Juju
> 2.0 rc1.
>
> The Juju client has never really worked on flavours of Linux which we
>
Correct, the original discussion was the charm behaving differently if the
fingerprint had changed of the resource on the remote end. However, running
resource-get deals with only fetching the new data if the fingerprint
changes and so there wasn't a big draw to the feature to that end.
Now, in
Thanks Andrew, this is great to hear. Can I bug you about details as to how
it works? Does this introduce their pricing API as a blocker to deploying
with Juju? If they introduce a change to the API we miss or their API goes
down is there any sort of cache of the info that users can continue with
On Thu, Oct 6, 2016 at 8:13 PM Adam Stokes
wrote:
> Nice! One question though maybe I'm missing something but I didn't see
> where the conjure-up instructions were shown on the jujucharms.com page?
> https://jujucharms.com/canonical-kubernetes/ It is in the README
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.
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
We need to delay the release of beta16 until next week as we've been busy
breaking things and currently don't have a working Azure in our trunk.
We've updated the Azure code we use to talk to their APIs and in the
process uncovered changes in our code that need to happen to help bring
things back
1611514
>
> Thanks!
>
>
> On Thu, Aug 18, 2016 at 9:26 AM Rick Harding <rick.hard...@canonical.com>
> wrote:
>
>> We need to delay the release of beta16 until next week as we've been busy
>> breaking things and currently don't have a working Azure in our
It was caught today in Juju testing that we fail to build with the latest
lxd 2.1 [1]. This initially seems like it's an issue in that the team
checks for lxd versioning much too tightly. We're working to update this as
fast as possible and doing some testing to see what's new in 2.1 that might
Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> <http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
> goal, but you can always help by sponsoring the project
> <http://www.meteorite.bi/products/saiku/s
I think we should truncate it to a reasonable length and folks will be able
to get at the full information once we fix the bug about a missing
show-action command. [1]
It is interesting in that there might be a need to add some basic 'readme'
style support to actions as they grow in complexity to
s
> verified at charm-proof time to be within the limit.
>
> On Tue, 23 Aug 2016 at 13:33 Rick Harding <rick.hard...@canonical.com>
> wrote:
>
>> I think we should truncate it to a reasonable length and folks will be
>> able to get at the full information once we fix t
This is just a miss. The original ability to see the plugins was a subset
of the help command and didn't make our CLI spreadsheet for things to
rework. I agree that list-plugins is the right idea here and that means
that plugins becomes a noun in our language.
What's interesting is that
Thanks Tom, it was a good week and glad you got something out of the time
there. I know it's exciting for us in Engineering to directly chat with
folks using and abusing our tools. It's exciting to see what you all do
with what we've built and to help motivate us to keep at it so that we can
take
On Mon, Nov 14, 2016 at 12:00 PM Jonathan D. Proulx
wrote:
>
> Continuing to try and get a Juju controller in my (14.04/Mitaka)
> OpenStack Cloud. Working with juju 2.0.1 from Xenial client.
>
> My next issue is I need to specify a network for the controller as
>
That's very true on the items that are different. I wonder if we could work
with the CPC team and note the things that are assumed promises when using
cloud images so that it'd be easy to build a "patch" for manually
provisioned machines. If we know specific packages or configuration is
there on
I'm definitely agreeing we need to provide some better tools for the admin
of the controller to track and garden things such as charms and resources
which can be quite large and grows over time.
My main point with Uros was that we have this way due to model migrations
to stick a controller/model
On Sun, Nov 13, 2016 at 6:03 PM James Beedy wrote:
> Do we have access to managing separate versions of a resource
> pragmatically? To give some context, I'm trying to implement rollback
> functionality for resources deployed in our applications. Implementing
> rollback is
Trusty is listed first. Order counts for the series list.
On Thu, Dec 8, 2016, 6:25 PM Merlijn Sebrechts
wrote:
> Hi
>
>
> I'm having trouble upgrading a multiseries charm.
>
>
> merlijn@travers:~$ juju status
> ModelController Cloud/Region Version
>
es manually with
> `upgrade-charm`. The command doesn't recognize the `--series` flag.
>
> 2016-12-08 14:20 GMT-05:00 Rick Harding <rick.hard...@canonical.com>:
>
> Trusty is listed first. Order counts for the series list.
>
> On Thu, Dec 8, 2016, 6:25 PM Merlijn Sebre
No, currently it does not. It's on the 17.04 roadmap to add that support.
The bundle does support resources, but as revisions from the charmstore so
that you can build a bundle that's not just the latest published charm
revision/resource revision set.
On Tue, Dec 13, 2016 at 6:09 PM Kevin Monroe
Come join us as we host the next Juju Show live stream tomorrow. We'll be
going over the latest in community news, demoing the new developments in
tools for charming, and getting a demonstration of the new model migration
feature coming in Juju 2.1.
When: Nov 30th, at 19:00 GMT, 2:00pm EST
Where:
in Juju 2.1.
With the holidays we'll be having our next Juju Show on January 4th and the
one after that will be the 18th. We'll have links and announcements out
after folks get back from the holidays.
On Tue, Dec 13, 2016 at 3:47 PM Rick Harding <rick.hard...@canonical.com>
wrote:
> Com
We'll be hosting a Juju Show live stream tomorrow. Set your reminder to
hear about the latest news in the Juju community.
When: Nov 30th, at 15:30 GMT, 10:30 EST
Where: https://www.youtube.com/watch?v=wo23ZXwa8ZU
How to participate: Hang out in the #juju Freenode IRC channel
Join us in the IRC
You will notice this is beta4 vs the rc1 we had been working toward.
Part of 2.1 is an improvement to juju container networking that corrects
issues that many users are facing. This updates Juju to only create bridges
on a host machine only when a container is placed on the host and only for
the
I'm looking into this. The bundle deploy feature in Juju 2.0 does not allow
referring to existing machines because it breaks the reusability of the
bundle.
However, the manual provider is a bit unique in that it's how you get
machines into the system. The bundle deployment should work to pick up
Hi Vance, you can deploy a bundle that uses existing machines in the model
with the juju-deployer [1] tool.
The built in juju deploy method is the first stage in a generic tool and
does not allow pointing at existing machines because it means the bundles
are not sharable and that you need your
On Thu, Jan 5, 2017 at 8:17 AM Panagiotis Liakos wrote:
>
> Moreover, I have just released the latest version of my charm [2].
Congrats!
> 1) Should I follow some procedure to find someone to review the charm?
>
Definitely, you can submit it to the review queue [1] and
since: 03 Jan 2017 14:53:31Z
> version: 1.25.9
> agent-state: started
> agent-version: 1.25.9
> machine: "9"
> open-ports:
> - 8777/tcp
> public-address: ceilometer.cord.lab
>
>
>
> On Tue, Jan 3, 2017 at 8:
One heads up is that this beta includes a memory improvement from Tim that
cut memory consumption over 75% when you get into the hundreds of models
for a controller. Folks that really iterate on controllers should notice
considerable improvement. If you're hitting this at all make sure to test
the
-science
Rick Harding
@mitechie
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
. I just walked through
setting it up and I missed the relation there. I'll have to test that out
and update the article. Thanks for the heads up!
On Tue, Mar 21, 2017 at 5:01 AM Jacek Nykis <jacek.ny...@canonical.com>
wrote:
> On 20/03/17 18:04, Rick Harding wrote:
> > During The
1 - 100 of 239 matches
Mail list logo