Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

Did you "juju expose mediawiki" ? That should have Juju update the security group on the mediawiki machines to expose port 80. John =:-> On Sun, Mar 26, 2017 at 10:58 PM, Giuseppe Attardi wrote: > I solved the problem by using Chrome instead of Safari. > > I was able then to deploy a mediawiki

Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

I solved the problem by using Chrome instead of Safari. I was able then to deploy a mediawiki bundle on AWS. It deployed two machines and the mediawiki unit was given these addresses: Public addresses: • 52.55.114.200:80 IP addresses: • 172.31.19.141:80 But none of them is reacha

Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

Hi, sorry about that. When visiting the login page directly it will attempt to open another tab to allow you to log in to your Ubuntu account. Check that you've allowed jujucharms.com to open new tabs. On Sat, Mar 25, 2017 at 6:15 AM, Giuseppe Attardi wrote: > Nice. > But > https://jujucharms.c

Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

On Fri, Mar 24, 2017 at 4:21 PM, Curtis Hovey-Canonical wrote: > ## How do I get it? ... > Windows, CentOS, and MacOS users can get a corresponding Juju > installer at: > >https://launchpad.net/juju/+milestone/2.2-beta1 Juju 2.2-beta1 is now in Homebrew. MacOS users can install it with the

Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

Nice. But https://jujucharms.com/login/ runs into a loop of: Requesting code… Rendering the GUI… Requesting code — Attardi -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juj

Re: A new release of Juju, 2.2-beta1 and conjure-up are here!

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

Re: maas how to add-cloud to a zone

Yes, this will work. I like the idea of being able to add constraints dynamically so you don't have to change the YAML. However, one thing to think about, as John said this way of using is like deploying everything to on Availability Zone on AWS, it would generally be a bad idea. The expected str

Re: Intermittent service interruption on jujucharms.com

The jujucharms.com interruption has been resolved. Thanks for your patience! On Tue, Mar 21, 2017 at 2:13 PM, Jeff Pihach wrote: > Hi everyone, > > We're working on a resolution for those experiencing intermittent service > interruption with jujucharms.com. This only affects jujucharms.com and >

Re: [Review Queue] Elastisys Charmscaler Promulgated!

PS: The in-page links in your README don't work in the charm store because of this bug: https://github.com/juju/juju-gui/issues/2650 If you want' add a :+1: to that bug so they know I'm not the only one using such links ;) PPS: I saw *"By using the Elastisys CharmScaler, you agree to its license a

Re: [Review Queue] Elastisys Charmscaler Promulgated!

The issue I see here is that there is much more momentum behind stuff like Nagios. It would be great if you could just plug this into existing monitoring/metrics solutions. I see the Charm has some Nagios-related config options and relations, is there some documentation about how this charm integr

Re: [Review Queue] Elastisys Charmscaler Promulgated!

On 21 March 2017 at 13:00, Merlijn Sebrechts wrote: > Awesome stuff! > > Would it make sense to expose the autoscaling options over an > interface/relationship? So that you can connect the autoscaler to a charm > and the charm tells the autoscaler how it should be scaled > Yea! It would be r

Re: [Review Queue] Elastisys Charmscaler Promulgated!

The question there is how different businesses will have different rules. I think it makes sense for a relation to describe what the charm author thinks is useful parameters/etc and maybe some default scaling config but I think that different folks will have different tastes to this. Especially as

Re: [Review Queue] Elastisys Charmscaler Promulgated!

Awesome stuff! Would it make sense to expose the autoscaling options over an interface/relationship? So that you can connect the autoscaler to a charm and the charm tells the autoscaler how it should be scaled 2017-03-20 21:54 GMT+01:00 Simon Kollberg : > > > On 20 March 2017 at 18:13, Char

Re: monitoring your production juju controllers

Jacek, let's talk on the mongodb exporter sometime. I tried to get it running but was unable to figure out how to get it to talk to the juju mongodb. All I could get out of it was generic connection errors. The relation thing you note is interesting. There's talk on the roadmap of exposing control

Re: Can't juju deploy p2.xlarge in aws/us-east-1

Preferring a VPC if there is a single one that exists, even if it isn't flagged as "default" for a region would probably be reasonable, and probably not a lot of effort. If there are multiple, I wonder if we could refuse to bootstrap/add-model unless one is specified. John =:-> On Tue, Mar 21, 2

Re: Can't juju deploy p2.xlarge in aws/us-east-1

Preferring a VPC if there is a single one that exists, even if it isn't flagged as "default" for a region would probably be reasonable, and probably not a lot of effort. If there are multiple, I wonder if we could refuse to bootstrap/add-model unless one is specified. John =:-> On Tue, Mar 21, 2

Re: monitoring your production juju controllers

On 20/03/17 18:04, Rick Harding wrote: > During The Juju Show #8 [1] last week we talked about how to setup your > controllers to be provide metrics through Prometheus to Grafana to keep > an eye on those controllers in production. > > I put together a blog post [2] about how to set it up, config

Re: Can't juju deploy p2.xlarge in aws/us-east-1

Isn't this spending time on a problem that will tend to disappear (and is probably already only like 0.1% of the user base)? Not sure it's worth the effort. Just specify Juju requires a VPC in the docs, and explain exactly how to fix it (call AWS...) and there you go. No code, problem solved. ++

Re: Can't juju deploy p2.xlarge in aws/us-east-1

On Mon, Mar 20, 2017 at 10:17 PM Junien Fridrick < junien.fridr...@canonical.com> wrote: > And once/if you have no Classic instance running in a region, you should > file a ticket to AWS Support asking for a default VPC creation. Once > it's done, you don't need to supply the VPC ID anymore. > > C

Re: [Review Queue] Elastisys Charmscaler Promulgated!

On 20 March 2017 at 18:13, Charles Butler wrote: > Greetings, > > I realized last week I had completed a review and failed to send an update > to the mailing list. As some of you may have heard on the Juju Show that > Elastisys released their Charm Scaler to the promulgated channel. > > > This wa

Re: Can't juju deploy p2.xlarge in aws/us-east-1

And once/if you have no Classic instance running in a region, you should file a ticket to AWS Support asking for a default VPC creation. Once it's done, you don't need to supply the VPC ID anymore. Could juju maybe be instructed to use a VPC if and only if a single VPC exist in a region, without s

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

Thanks for the heads up, this is now fixed $ sudo snap refresh conjure-up --beta On Fri, Mar 17, 2017 at 9:49 AM Mark Shuttleworth wrote: > 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: > >

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: Constraints for Additional Units

Correct. Putting the constraints on the machines is equivalent to doing: juju add-machine --constraints mem=4gb juju deploy mysql --to $MACHINE Rather than doing: juju deploy mysql --constraints mem=4gb Constraints on an Application will affect all new units of an application, but constraint

Re: Constraints for Additional Units

I think I see *my* issue here. I have placed the constraints on the machines (to which the charms are mapped) in my bundle, and not on the actual applications themselves. I guess I shouldn't expect the constraints to be associated with the charms in that case. Does this sound correct? On Thu, Mar

Re: Constraints for Additional Units

On 17/03/17 14:23, James Beedy wrote: Currently, if I scale the units of my application, the new units do not have the same constraints as the previously deployed units. Well, I certainly think they should be carrying over the constraints as the constraints are set on the application, not the

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

Please note, that the experience with "juju login jaas" in 2.2-Alpha1 is still quite broken. The login command will add jaas controller to the controllers.yaml, so the next time you'd like to use it, you'll have to do "juju switch jaas" instead of "juju login jaas". We'll improve the experience by

Re: Can't juju deploy p2.xlarge in aws/us-east-1

A. That was it. After passing --config "vpc-id=vpc-924fc7f6" to `juju bootstrap`, I can now deploy p2 instance types. Thanks Andrew! On Thu, Mar 16, 2017 at 4:21 AM, Samuel Cozannet < samuel.cozan...@canonical.com> wrote: > Aaah whaow. I have a default VPC myself, so that may explain the prob

Re: Can't juju deploy p2.xlarge in aws/us-east-1

Aaah whaow. I have a default VPC myself, so that may explain the problem Tim is having. Early adopters problem!! -- Samuel Cozannet Cloud, Big Data and IoT Strategy Team Business Development - Cloud and ISV Ecosystem Changing the Future of Cloud Ubuntu / Canonical UK LTD

Re: Can't juju deploy p2.xlarge in aws/us-east-1

On Thu, Mar 16, 2017 at 3:57 PM Samuel Cozannet < samuel.cozan...@canonical.com> wrote: > I am using the default settings, no change as far as I know to what Juju > would do by default. > What Juju will do depends on what is available in your EC2 account. Not all EC2 accounts were born alike. If

Re: Can't juju deploy p2.xlarge in aws/us-east-1

I am using the default settings, no change as far as I know to what Juju would do by default. -- Samuel Cozannet Cloud, Big Data and IoT Strategy Team Business Development - Cloud and ISV Ecosystem Changing the Future of Cloud Ubuntu / Canonical UK LTD

Re: Can't juju deploy p2.xlarge in aws/us-east-1

On Tue, Mar 14, 2017 at 8:48 PM Tim Van Steenburgh < tim.van.steenbu...@canonical.com> wrote: > 2.1.1 juju client and controller, controller bootstrapped in aws/us-east-1: > > juju deploy ./kubernetes-worker --constraints "instance-type=p2.xlarge" > kubernetes-worker-gpu > Deploying charm "local:

Re: maas how to add-cloud to a zone

For now i found a way to work around this. I group machines now by tags. Then use constraints to deploy the charms to those groups. This works quite well. It would be nice if charm bundles would support constraints without changing the .yaml file which i have to do now.. but it works. so in th

Re: maas how to add-cloud to a zone

Zones are generally meant to be used to provide fault domains such that you should be spreading your applications across zones. I can see how zones could be used differently but it does feel like it would be going against the grain. John =:-> On Mar 15, 2017 13:01, "Menno Smits" wrote: Hi Chris

Re: maas how to add-cloud to a zone

Hi Christian, Someone who knows more about Juju's MAAS support may disagree with me but I just had a quick look through the code I don't see any way to specify the MAAS zone as part of a MAAS cloud definition. - Menno On 14 March 2017 at 13:26, wrote: > Hi > > Is it possible to add-cloud a maa

Re: Can't juju deploy p2.xlarge in aws/us-east-1

TBH I can't remember which juju version I have been using, but I tend to be on the edge of 16.10, so the latest there is what I have. I deployed like 5 times yesterday and 2 this morning, so for me no problemas at all. On Mar 14, 2017 14:31, "Tim Van Steenburgh" < tim.van.steenbu...@canonical.com

Re: Can't juju deploy p2.xlarge in aws/us-east-1

Yeah, and it also doesn't list any p2 types in the list of valid values. I'm not sure why. IIRC, 2.1 introduced a querying-clouds-for-instance-types feature - I wonder if that could be related. I might just drop back to 2.0 and see if it works there. Sam, curious if you've tried a p2 with 2.1? On

Re: Can't juju deploy p2.xlarge in aws/us-east-1

It is weird, it fails because it doesn't recognize the instance type in the constraint. I haven't seen that in the past, though to spin more than one you need to ask to upgrade your quota. ++ Sam On Mar 14, 2017 13:48, "Tim Van Steenburgh" < tim.van.steenbu...@canonical.com> wrote: > 2.1.1 juju

Re: [Resolved] Some API endpoints are currently experiencing unexpected downtime

This issue has been resolved and all API endpoints are back to working as expected. On Mon, Mar 13, 2017 at 8:52 AM, Jeff Pihach wrote: > Hello everyone, > > There are a few API endpoints that are currently experiencing unexpected > downtime. This only affects certain clients, notably conjure-

Re: juju 2.0.2 picking a random ip address from maas

Bindings can be set explicitly in bundles because each piece of the bundle takes different bindings. mysql: ... bindings: "": space telemetry: ... bindings: "": space You can't specify deploy bundle with binding because each application is likely to be bound differently. John =:->

Re: juju 2.0.2 picking a random ip address from maas

Good morning John, I tested it, i destroyed the controller and rebuilt from scratch. after juju bootstrap i got "No packaged binary found, preparing local Juju agent binary" because it could not find 2.1.2 version in the repos, which is great. with $ juju deploy ceph-osd --bind The unit deploy

Re: Juju GUI handling of empty config breaks promulgated charms

Hi All, Just a quick follow-up on this: both the gui and python-libjuju now use the "config-yaml" rather than the "config" parameter when deploying a bundle, which addresses the issue (provided you have an updated GUI or libjuju wherever you're performing the deploy, of course). ~ PeteVG On Thu,

Re: juju 2.0.2 picking a random ip address from maas

Ok! I'll test tomorrow, but i need a xenial build as i'm on 16.04 release Patrizio Il 09/mar/2017 07:29 PM, "John Meinel" ha scritto: > http://data.vapour.ws/juju-ci/products/version-4977/build- > binary-trusty-amd64/build-2159/juju-core_2.1.2-0ubuntu1~ > 14.04.1~juju1_amd64.deb > > Should have

Re: juju 2.0.2 picking a random ip address from maas

http://data.vapour.ws/juju-ci/products/version-4977/build-binary-trusty-amd64/build-2159/juju-core_2.1.2-0ubuntu1~14.04.1~juju1_amd64.deb Should have the fix for empty binding names. John =:-> On Thu, Mar 9, 2017 at 11:43 AM, Ante Karamatić < ante.karama...@canonical.com> wrote: > My snap is p

Re: juju 2.0.2 picking a random ip address from maas

My snap is pending review. In the meantime you can try with: https://launchpad.net/~ivoks/+archive/ubuntu/ppa On Thu, Mar 9, 2017 at 6:38 PM John Meinel wrote: > We should as soon as I have it landed in the 2.1 branch and CI starts to > run we can use it's deb. > > John > =:-> > > On Mar 9, 201

Re: juju 2.0.2 picking a random ip address from maas

We should as soon as I have it landed in the 2.1 branch and CI starts to run we can use it's deb. John =:-> On Mar 9, 2017 09:48, "Patrizio Bassi" wrote: > Fantastic job John! > > do you have a .deb i can already test on my environment? > > Patrizio > > 2017-03-09 16:24 GMT+01:00 John Meinel :

Re: juju 2.0.2 picking a random ip address from maas

Fantastic job John! do you have a .deb i can already test on my environment? Patrizio 2017-03-09 16:24 GMT+01:00 John Meinel : > I do have a fix up for review: > https://github.com/juju/juju/pull/7081 > And I have tested it live against a local maas, though my maas doesn't > have multiple int

Re: juju 2.0.2 picking a random ip address from maas

Hi John I'll give this a shot today. Thank you! On Thu, Mar 9, 2017 at 4:25 PM John Meinel wrote: > I do have a fix up for review: > https://github.com/juju/juju/pull/7081 > And I have tested it live against a local maas, though my maas doesn't > have multiple interfaces, I can see the bindin

Re: juju 2.0.2 picking a random ip address from maas

I do have a fix up for review: https://github.com/juju/juju/pull/7081 And I have tested it live against a local maas, though my maas doesn't have multiple interfaces, I can see the bindings get requested appropriately and not fail with the "empty binding name" failure. I'm pushing to get a 2.1.2

Re: juju 2.0.2 picking a random ip address from maas

@John great. i'm using juju 2.1.1 and maas 2.1.3. Regarding the workaround...it's not a matter of a particular charm, it's a matter of all (i will deploy openstack-telemetry charm with some modifications), because when we allocate a machine with juju i would like it to pick a public (dns) name, th

Re: juju 2.0.2 picking a random ip address from maas

Where do we find which bindings a charm has so they can be specified directly? According to the docs on the metadata ( https://jujucharms.com/docs/stable/authors-charm-metadata) there's a section called extra-bindings but that only seems to be used in some charms. -- Sandor Zeestraten On Thu, Mar

Re: juju 2.0.2 picking a random ip address from maas

In the meantime, you can work around it by specifying the bindings directly: so in the case of mysql that would be: juju deploy mysql --bind "db=db-space monitors=db-space ha=db-space ..." John =:-> On Thu, Mar 9, 2017 at 7:25 AM, John Meinel wrote: > "juju deploy mysql --bind db-space" is ex

Re: juju 2.0.2 picking a random ip address from maas

"juju deploy mysql --bind db-space" is exactly the syntax that should be working, and I'm seeing it failing now. I will work to fix that and make sure we don't regress here. We certainly should have caught that before release. John =:-> On Thu, Mar 9, 2017 at 1:47 AM, Patrizio Bassi wrote: > H

Re: juju 2.0.2 picking a random ip address from maas

What version of MAAS? Just in case the problem is a mismatch with all the tests I've been doing so far. John =:-> On Mar 9, 2017 07:05, wrote: We intentionally use "" to mean the default value for everything else, which is why I need to understand where we are actually getting the error. I'll tr

Re: juju 2.0.2 picking a random ip address from maas

We intentionally use "" to mean the default value for everything else, which is why I need to understand where we are actually getting the error. I'll try to reproduce it today. John =:-> On Mar 9, 2017 01:28, "Patrizio Bassi" wrote: > Hi John, > > i simply would like to do what's written in ht

Re: juju 2.0.2 picking a random ip address from maas

Hi All, after some debugging i found in juju /application /deploy.go func (c *DeployCommand) parseBind() { case

Re: juju 2.0.2 picking a random ip address from maas

Hi Ante, no that is not working, but i think it's by design. That constraint means: pick up a machine that has a leg in the db-space leg. So my machine with 2 eth ports in two different spaces satisfy that constraint, it is picked, but the IP is wrong. Another option i tried is: juju deploy mys

Re: juju 2.0.2 picking a random ip address from maas

Hi Patrizio, this is exactly what I saw yesterday too, unrelated to this thread. What you could do is: juju deploy mysql --constraints spaces=db-space Let me know if the constraints workaround works for you. On Thu, Mar 9, 2017 at 8:28 AM Patrizio Bassi wrote: > Hi John, > > i simply would li

Re: juju 2.0.2 picking a random ip address from maas

Hi John, i simply would like to do what's written in https://jujucharms.com/docs/2.1/charms-deploying "When deploying an application to a target with multiple spaces, the operator must specify which space to use because ambiguous bindings will result in a provisioning failure." This is exactly m

Re: MySQL charm bugs

Looking at the page: https://jujucharms.com/mysql on the right is the link to "submit a bug" which goes to: https://github.com/marcoceppi/charm-mysql/issues You can also get the bug url with the charm command. charm show mysql bugs-url bugs-url: https://github.com/marcoceppi/charm-mysql/issues

Re: juju 2.0.2 picking a random ip address from maas

So without bindings, I would expect the behavior, the question is why you would be seeing: "cannot run instances: cannot run instance: interface bindings cannot have empty names" Can you open a bug on https://bugs.launchpad.net/juju/+filebug and include some more information like the logs from t

Re: Make JaaS better for data scientists

> On 8 Mar 2017, at 09:51, Merlijn Sebrechts > wrote: > > Juju as a Service is incredibly cool. This is a great step towards making > Juju useful for data scientists. However, there are still a number of issues > that block this adoption. This email sheds some light into how, in our > experi

Re: cinder and ceilometer metrics architecture question

Hi Drew On Wed, 8 Mar 2017 at 16:03 Drew Freiberger wrote: [...] > Unfortunately, nothing in ceilometer is picking up the > oslo_message_notifications on the unit where cinder is running. I went > to add the ceilometer-agent-charm to the unit, but found it's only > written to pick up OS and Com

Re: ssh keys

This is definitely on the todo list. It's completely correct that users should be able to manage their own keys. On Wed, Mar 8, 2017 at 11:01 AM James Beedy wrote: > I'm quickly finding myself maintaining users ssh keys. How do people feel > about making ssh keys bound to the user instead of the

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 mailing list Juju@lists.ubuntu.com Modify settings or

Re: juju 2.0.2 picking a random ip address from maas

Is it possible for you to test with Juju 2.1? I haven't seen that particular bug with binding, but I have done a lot more testing with 2.1. I didn't think we changed the particular "empty space" differences. The other possibility is to try and explicitly list the endpoints: juju deploy ceph-osd

Re: juju 2.0.2 picking a random ip address from maas

i just upgraded to 2.1.1-xenial-amd64, same behaviour unfortunately. As i'm going to deploy openstack services (now i'm using ceph-osd just to test, than my binding should be global for a local bundle charm) i would like to say: all juju endpoint (bare metal/lxd containers) just get a 10.xxx addre

Re: juju 2.0.2 picking a random ip address from maas

It looks like it's not working $ juju deploy ceph-osd --bind "management" $ juju show-machine 0 shows "message: 'failed to start instance (cannot run instances: cannot run instance: interface bindings cannot have empty names), retrying in 10s (3 more attempts)' ...than after some seconds i

Re: juju 2.0.2 picking a random ip address from maas

You should be using "juju deploy application --bind space" to declare which set of addresses you want the applications to use. Does that not work? John =:-> On Wed, Mar 8, 2017 at 4:44 AM, Patrizio Bassi wrote: > Hi All, > > I'm quite new the juju and it's charms. On ubuntu 16.04 LTS I have j

Re: Giraf demo

> OK. Are there actions on the charms to kick these off? > The smoke-test in the charm executes PageRank on a very small graph: https://github.com/panagiotisl/bigtop/blob/master/bigtop-packages/src/charm/giraph/layer-giraph/actions/smoke-test#L54 For some reason the giraph-examples.jar (with Page

Re: Giraf demo

On 07/03/17 06:44, Panagiotis Liakos wrote: > In terms of performance, the giraph distribution features examples of > algorithms such as PageRank or ShortestPaths. OK. Are there actions on the charms to kick these off? Also, is the I/O all text based or is there a Giraf GUI? I won't have a lot of

Re: Giraf demo

Hi! One really intriguing and fun example of what you can do with giraph is the algorithm of Backstrom and Kleinberg [1] that uses only network structure to order your friends according to their probability of being in a relationship with you. I have implemented it for Giraph (~50 lines of Java co

Re: Cannot update bugs-url of promulgated charm

You're all set Merlijn. -Kevin On Mon, Mar 6, 2017 at 11:21 AM, Jay Wren wrote: > The charm is promulgated and thus its write permissions are set to only > "charmers". > > Will a member of charmers please set bugs-url for Merlijn? > > Alternatively, you could update a different charm, set its b

Re: Cannot update bugs-url of promulgated charm

The charm is promulgated and thus its write permissions are set to only "charmers". Will a member of charmers please set bugs-url for Merlijn? Alternatively, you could update a different charm, set its bugs-url and ask for it to be promulgated. -- Jay On Mon, Mar 6, 2017 at 10:55 AM, Merlijn Se

Re: giraph charm approved

On 04/03/17 00:01, Antonio Rosales wrote: > On Fri, Mar 3, 2017 at 12:34 PM, Panagiotis Liakos wrote: >> Dear Mark, >> >> Thank you! I agree that deploying Giraph easily can be extremely >> beneficial for researchers and software engineers as it will enable >> them to focus on developing algorithm

Re: giraph charm approved

On Fri, Mar 3, 2017 at 12:34 PM, Panagiotis Liakos wrote: > Dear Mark, > > Thank you! I agree that deploying Giraph easily can be extremely > beneficial for researchers and software engineers as it will enable > them to focus on developing algorithms instead of wasting time to > set-up their infra

Re: giraph charm approved

Dear Mark, Thank you! I agree that deploying Giraph easily can be extremely beneficial for researchers and software engineers as it will enable them to focus on developing algorithms instead of wasting time to set-up their infrastructure. And I believe that Giraph is more capable of handling produ

Re: giraph charm approved

Thank you for your work Panagiotis. Congrats! On Fri, Mar 3, 2017 at 1:53 PM, Mark Shuttleworth wrote: > Hi Panagiotis > > Congratulations on getting giraf into the curated set! I think it's an > exciting new capability for people working with webs of linked data, so > making it really easy to d

Re: Juju Snap Changes

A 'classic' snap is OK in the cases where the tool in question really, really makes sense as part of a classic environment. Things like compilers, editors, file viewers, etc, all make sense. It's also a nice comfortable way to start out making a snap, but for things that can be confined, its best

Re: giraph charm approved

Hi Panagiotis Congratulations on getting giraf into the curated set! I think it's an exciting new capability for people working with webs of linked data, so making it really easy to deploy and operate is a very valuable contribution. It took a long time for giraf to mature but it's now one of thos

Re: Issue with Amulet testing

Seems more like just a python thing, vs anything to do with Amulet. https://github.com/kennethreitz/requests/issues/2214 Says you can do some magic around disabled warnings A better goal might be to have the charm optionally take the config of a cert to use and configure your tests to include tha

Re: Juju Snap Changes

And thanks to Merlijn for bing blunt enough to ask the questions a lot of us were thinking about snaps! :) On Wed, Mar 1, 2017 at 9:27 AM, Merlijn Sebrechts < merlijn.sebrec...@gmail.com> wrote: > Thanks for the thorough explanation! > > 2017-03-01 7:07 GMT+01:00 John Meinel : > >> ... >>> >> >>

Re: Juju Snap Changes

Thanks for the thorough explanation! 2017-03-01 7:07 GMT+01:00 John Meinel : > ... >> > > >> I'm having a hard time wrapping my head around classic mode. Classic mode >> means unconfined, right? >> >> What are the reasons for this switch? Is the snap still cross-distro? >> Will the snap have some

Re: Juju Snap Changes

> > ... > > I'm having a hard time wrapping my head around classic mode. Classic mode > means unconfined, right? > > What are the reasons for this switch? Is the snap still cross-distro? Will > the snap have some expectations about the system outside of the snap? What > are the advantages of an u

Re: Juju Snap Changes

Hi Nicholas I'm having a hard time wrapping my head around classic mode. Classic mode means unconfined, right? What are the reasons for this switch? Is the snap still cross-distro? Will the snap have some expectations about the system outside of the snap? What are the advantages of an unconfined

Re: Juju Snap Changes

Thanks Nicholas, Sounds awesome. Tim On 01/03/17 08:52, Nicholas Skaggs wrote: Those of you subscribed to a snap channel may have noticed some nice changes that happened with 2.1 release. The juju snap package now utilizes classic mode, and all channels (including stable) are now active. You s

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

On Fri, Feb 24, 2017 at 11:14 AM, Andrew Wilkins < andrew.wilk...@canonical.com> wrote: > On Fri, Feb 24, 2017 at 6:51 PM Mark Shuttleworth wrote: > >> On 24/02/17 11:30, Andrew Wilkins wrote: >> >> On Fri, Feb 24, 2017 at 6:15 PM Adam Collard >> wrote: >> >> On Fri, 24 Feb 2017 at 10:07 Adam Is

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

On Fri, Feb 24, 2017 at 6:51 PM Mark Shuttleworth wrote: > On 24/02/17 11:30, Andrew Wilkins wrote: > > On Fri, Feb 24, 2017 at 6:15 PM Adam Collard > wrote: > > On Fri, 24 Feb 2017 at 10:07 Adam Israel > wrote: > > Thanks for calling this out, Simon! We should be shouting this from the > rooft

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: Juju 2.1.0, and Conjure-up, are here!

On Fri, Feb 24, 2017 at 6:15 PM Adam Collard wrote: > On Fri, 24 Feb 2017 at 10:07 Adam Israel > wrote: > > Thanks for calling this out, Simon! We should be shouting this from the > rooftops and celebrating in the streets. > > > Only if you also wave a big WARNING banner! > > I can definitely se

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

On Fri, 24 Feb 2017 at 10:07 Adam Israel wrote: > Thanks for calling this out, Simon! We should be shouting this from the > rooftops and celebrating in the streets. > Only if you also wave a big WARNING banner! I can definitely see value in pre-installing a bunch of things in your LXD images as

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

Thanks for calling this out, Simon! We should be shouting this from the rooftops and celebrating in the streets. On Fri, Feb 24, 2017 at 8:42 AM Stuart Bishop wrote: > On 23 February 2017 at 23:20, Simon Davy wrote: > > > One thing that seems to have landed in 2.1, which is worth noting IMO, is

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

On 23 February 2017 at 23:20, Simon Davy wrote: > One thing that seems to have landed in 2.1, which is worth noting IMO, is > the local juju lxd image aliases. > > tl;dr: juju 2.1 now looks for the lxd image alias juju/$series/$arch in the > local lxd server, and uses that if it finds it. > > Thi

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

On Thu, Feb 23, 2017 at 2:48 AM, Curtis Hovey-Canonical < cur...@canonical.com> wrote: > A new release of Juju, 2.1.0, and Conjure-up, are here! > > > ## What's new in 2.1.0 > > - Model migration > - Interactive `add-cloud` > - Networking changes > - Conjure-up > - LXD credential changes > - Chang

Re: Juju GUI handling of empty config breaks promulgated charms

On Thu, Feb 23, 2017 at 2:31 AM John Meinel wrote: > AFAICT we fixed this in Juju 1.15, but there are 2 places you can pass > config. The old field uses the compatibility of "" means nil, the new field > handles nil vs "" correctly. The Juju CLI should work correctly, it sounds > like the GUI was

Re: PostgreSQL Use Case/Issues

Awesome. Thanks for this! > On Feb 23, 2017, at 4:15 AM, Stuart Bishop > wrote: > >> On 23 February 2017 at 15:46, Stuart Bishop >> wrote: >> On 23 February 2017 at 01:46, James Beedy wrote: >> I think I can fix this, but I'll need to make a corresponding adjustment in the Postgre

Re: PostgreSQL Use Case/Issues

On 23 February 2017 at 15:46, Stuart Bishop wrote: > On 23 February 2017 at 01:46, James Beedy wrote: > >>> I think I can fix this, but I'll need to make a corresponding >>> adjustment in the PostgreSQL charm and the fix will only take effect >>> with updated services. >>> >> +1 for a fix. Thanks

Re: PostgreSQL Use Case/Issues

On 23 February 2017 at 14:22, Mark Shuttleworth wrote: > On 22/02/17 19:46, James Beedy wrote: > > A client can 'accept the defaults' by not setting any properties on >> >> the db relation when it joins (dating back to the original protocol >> with pyjuju). When the PostgreSQL charm runs its relat

Re: PostgreSQL Use Case/Issues

On 23 February 2017 at 01:46, James Beedy wrote: >> I think I can fix this, but I'll need to make a corresponding >> adjustment in the PostgreSQL charm and the fix will only take effect >> with updated services. >> > +1 for a fix. Thanks. >> Its related to the above issue. Your charm connects an

Re: Juju GUI handling of empty config breaks promulgated charms

> > ... > > The ideal solution is of course to fix it in Juju, and have it stop > throwing away perfectly valid configuration data :) > > > AFAICT we fixed this in Juju 1.15, but there are 2 places you can pass config. The old field uses the compatibility of "" means nil, the new field handles nil

<    5   6   7   8   9   10   11   12   13   14   >