We didn't do an original 0byte resource because that's almost promised to
fail. The thought was, in order to publish the charm into the store then
you need some minimal resource that the charm will accept. If it's a django
charm, a hello world application; if a file server, a demo image; etc. Just
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 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 add/remove
hey wrote:
> 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 c
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 it'
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
wrote:
> Where can I get fresh RC
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.
Typically you'd be able to tell the source for charms set via
charm show ubuntu homepage
charm show ubuntu bugs-url
In this case they're both set to https://ubuntu.com so not helpful in
getting to the source.
On Fri, Sep 16, 2016 at 2:37 PM Ryan Beisner
wrote:
> Was there a merge proposal or p
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
> hadn't explicitly added support f
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
Ju
I do think that making it a release blocker might be interesting to help
users that find those charms. You can use/develop just fine without making
it a blocker to getting started, but at release time you're already doing
charm command work there.
On Wed, Sep 14, 2016 at 10:28 AM Jorge O. Castro
Ales, can we look into catching that error in the client and perhaps
providing a more pointed message to the user?
On Fri, Sep 2, 2016 at 5:15 AM Anita Nayak1 wrote:
> Hi,
>
> I am able to deploy the charms now.
> Please ignore the previous mail.
>
> Thanks & Regards,
> Anita.
>
> [image: Inacti
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 good
tl;dr Juju 2.0 has moved to lp:juju vs lp:juju-core, please make sure to
file bugs and track blueprints there.
The Juju team is getting ready for Juju 2.0 and as part of that work, we’ve
moved the Juju 2.0 project in launchpad to the launchpad.net/juju
namespace. All 2.0 bugs, blueprints, and futu
anks 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/sponsorship>)
>
> On 23
That looks like something interesting. :)
Yes, the engineering team is working on adapting the Fan to public clouds
as a first go at making sure containers can be routable ootb when using
Juju. We'll just recently had a sprint scoping it out and see this as the
solution to the problem your running
charm-proof time to be within the limit.
>
> On Tue, 23 Aug 2016 at 13:33 Rick Harding
> 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 the bug about a missing
>> show-action command
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
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
To be clear, lxd 2.1 is new in yakkety today and does not currently effect
xenial and previous releases.
On Thu, Aug 18, 2016 at 12:52 PM Rick Harding
wrote:
> 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
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
cau
!
>
>
> On Thu, Aug 18, 2016 at 9:26 AM Rick Harding
> 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 trunk.
>>
>> We've updated the Azur
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
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
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 at
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"
https://maas.ubuntu.com/docs/api.html#logged-i
You can get juju 1 from the default repositories on xenial with the package
juju-1.25. Right now 1.25.6 is working its way into xenial to update that.
That'll give you a juju-1 command that can live alongside juju (which is
juju 2.0).
On Mon, Aug 1, 2016 at 4:14 AM Adam Collard
wrote:
> On Mon,
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 scaling your High Availabil
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 then I got the same error as u
Daniel, sorry for the trouble there. As we work on things in the beta there
are times when the upgrade from one beta to another might cause issues like
this. You're hitting an incompatibility between the beta you were on and
the latest. The only fix is to tear down and redeploy with the latest beta
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
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
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 A
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
wrote:
> On Fri,
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 no
; wrote:
>
>> 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?
&
That's exactly the plan we had in mind by breaking up charm push and
publish. Glad it's working for you.
On Wed, Jun 15, 2016, 8:34 AM Merlijn Sebrechts
wrote:
> FYI: I found a better way to do the CI pipeline. Now I'm pushing the
> Charms to the store before testing and publishing them after te
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:
2016-
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 "
Thanks Merlijn, I'd not come across this yet. I think the best summary is
here:
https://wiki.openstack.org/wiki/App-Catalog#Horizon_Plugin_for_Native_Access
It looks like it's the start of a hub for images, heat templates, and
murano packages. At this time there's no integration with Juju. It's
in
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 through
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
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:
> https://puppet.com/support-services, you guys do
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
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
application.
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 10:59 AM, John Meinel
>>> wrote:
>>>
...
>
>> A
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 Tue, Apr 26, 2016 at 3:11 P
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 op
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
be
ve
>> > 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:
>> > "/home/ubuntu/charms/trusty/ap
+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 <
>> andrew.wilk...@canonical.
n 22 March 2016 at 11:42, Rick Harding
> 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
> >> separate charms that work on older clients. If you hit i
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
wrote:
> On
the charm proof tool is updated to
help with this. It should validate folks don't have the field if the
min-juju-version is < 2.0.
On Mon, Mar 21, 2016 at 10:26 AM Ryan Beisner
wrote:
> On Mon, Mar 21, 2016 at 9:18 AM, Rick Harding
> wrote:
>
>> Checked with the team and o
something that would
have been nicer if we had that version info all the time.
On Mon, Mar 21, 2016 at 10:08 AM Rick Harding
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 so
&g
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
1.2
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 the
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 handful of current features and
adding to the backlog while getting that beta release out, the decision was
made to focus on getting the
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 charm will be deployed nor
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 s
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
wrote:
> Hi!
>
> Could I get this bug added to the list too?
>
> https://bugs.launchpad.net/juju-core/+bug/1554721
>
> On Thu, Mar 17, 2016 at
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
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
define
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
>
>
Awesome, appreciate it.
On Tue, Mar 1, 2016, 8:48 AM Adam Stokes 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
> wrote:
>
>> Thank Adam. That's good feedback. With tabu
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` versus
> reading the controll
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 are both forward an
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 openstack
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
> wrote:
>
>> The lxd cloud works on Juju 2
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
Adam, charm revisions turn into a tuple of the charm revision and the
revision of each resource provided. This means that if you update the
revision of the charm, or any resource, that tuple has been 'upgraded'. So
uploading the resource after the fact would trigger upgrade-charm hook and
it'll be
I wanted to add that the reason we're curious about this is because we're
working on how Juju can help provide insights into things that could be
off/wrong between units. If we expect the units to be the same, then things
like warning users that a unit hasn't yet gotten a resource that the others
h
I just want to say that I ran GSoC for my side open source project a couple
of years ago and it was really awesome. I worked to setup standup meetings,
a kanban board, and did things like code reviews and such. So this is
something, that if folks are interested, can be really useful as far as
mento
ect
> <http://www.meteorite.bi/products/saiku/sponsorship>)
>
> On 14 February 2016 at 20:46, Rick Harding
> wrote:
>
>> It looks like the m4 type is available but seems to not be listed in all
>> regions that it should be. We'll get it looked at and updated.
&g
It looks like the m4 type is available but seems to not be listed in all
regions that it should be. We'll get it looked at and updated.
On Sun, Feb 14, 2016 at 3:24 PM Marco Ceppi
wrote:
> This was a bug that popped up earlier for me, it was fixed in a 1.X
> version of Juju I'm surprised to see
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 again purely so I can hack
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, 20
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 midonet-review
>> > juju switch midonet-revi
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
> wrote:
>
>> Sorry dimiter, I know Andrew is out. Can you investigat p
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 <
> andrew.mcderm...@canonical.com>:
>
>> Hi Patrik,
On Wed, Dec 23, 2015 at 10:17 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:
> This looks great! Nice work!
>
>
> I love the new store interface! Are there any plans to revamp the unit
> configuration sidebar? It would be great if this could also be shown in the
> middle like the charm
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 AM
On Fri, Nov 27, 2015 at 11:35 AM Mark Shuttleworth wrote:
> On 27/11/15 16:21, Aaron Bentley wrote:
>
> It's dependent on what compiler was used to create the jujud binary.
> AIUI, the Ubuntu policy is that nothing goes into a distroseries which
> cannot be compiled with the tools in that distros
Not yet, that work is still going on in the feature branch here:
https://github.com/juju/juju/commits/maas-spaces
I'm not sure on the current timeline for it to reach an alpha release.
Andrew, can you please fill in how it goes?
Thanks
On Fri, Nov 27, 2015 at 1:27 PM Pshem Kowalczyk wrote:
> H
On Wed, Nov 25, 2015 at 4:08 PM Simon Davy
> I don't know where we are at with the resources work, but maybe that
> could have a part to play here?
>
This is exactly what I wanted to bring up for discussion. This work is
about to start at the end of this month/start of next. It sounds like
there'
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 AM
t would
take to support this. I'll make sure the team adds you in 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
nments 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
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 bo
.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
> wrote:
>
>> Thanks for the details Andres.
>>
>> On Mon, Nov 2, 2015, 9:52 AM Andres Rodrigue
Thanks for the details Andres.
On Mon, Nov 2, 2015, 9:52 AM Andres Rodriguez wrote:
> Re-sending my response inline below
>
> On Mon, Nov 2, 2015 at 9:16 AM, Andres Rodriguez
> wrote:
>
>>
>>> > ### Support "devices" on MAAS 1.8+
>>> >
>>> > MAAS 1.8 introduced a new feature called "devices". T
Howdy Merlijn. The team will look into it. I note you filed the bug here:
https://bugs.launchpad.net/juju-gui/+bug/1509443
The read-only isn't used much so we'll have test that out. The console
enabled is for the javascript console and debugging support. Were you
looking for that for some reason o
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
> framew
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 wor
-- Forwarded message --
From: "Jeff Pihach"
Date: May 27, 2015 7:45 PM
Subject: [Juju-gui-peeps] Upcoming GUI release qa request
To: "juju-gui-pe...@lists.launchpad.net"
Cc:
Hello peeps,
Tomorrow we're going to be cutting a new GUI release which includes the
uncommitted bundle f
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
wrote:
> Today I red
-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
the same thought a couple of times. 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@list
Heads up that a new release has hit jujucharms.com. This contains several
smaller things but you might be interested. Please check it out and let us
know if you hit any issues.
http://jujugui.wordpress.com/2014/12/10/new-jujucharms-com-release-dec-10th/
- Add blog support. https://jujucharms.
101 - 200 of 202 matches
Mail list logo
