Juju devel 2.0-beta6 is released

[Curtis Hovey-Canonical]

# juju 2.0-beta6

A new development release of Juju, juju 2.0-beta6, is now available.
This release replaces version 2.0-beta5.


## Getting Juju

Juju 2.0-beta6 is available for Xenial and backported to earlier
series in the following PPA:

https://launchpad.net/~juju/+archive/devel

Windows, Centos, and OS X users will find installers at:

https://launchpad.net/juju-core/+milestone/2.0-beta6

Upgrading environments to 2.0-beta6 is not supported.


## The complete release notes available on the Web

The release notes for Juju 2.0 beta6 are very long. They are too large
to post to a list. The complete release notes are published at

https://jujucharms.com/docs/devel/temp-release-notes


## Getting started with Juju 2.0

Juju 2.0 allows you to get started creating models without modifying any
definition files.  Just provide your credentials and go!  (*Note: to
fully understand the new bootstrap experience please see the "New
Bootstrap and Cloud Management Experience" section below)

* LXD provider (requires lxd 2.0.0~rc9 or later):
  The LXD provider requires no credentials, so you can create a
  controller by just specifying its name:

juju bootstrap  lxd

Note that the lxdbr0 bridge needs to be properly configured for the lxd
provider to work, for details see:
http://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/

* Public Clouds:
  Known public clouds can be listed with juju list-clouds:

juju list-clouds

CLOUD  TYPEREGIONS
awsec2 us-east-1, us-west-1, us-west-2, ...
aws-china  ec2 cn-north-1
aws-govec2 us-gov-west-1
azure  azure   japanwest, centralindia, eastus2, ...
azure-chinaazure   chinaeast, chinanorth
cloudsigma cloudsigma  mia, sjc, wdc, zrh, hnl
google gce us-east1, us-central1, ...
joyent joyent  us-east-1, us-east-2, us-east-3, …
lxdlxd
maas   maas
manual manual
rackspace  rackspace   lon, syd, hkg, dfw, ord, iad

Add your credentials using either:

juju add-credential 
or
juju add-credential  -f creds.yaml
or
juju autoload-credentials

When specifying just the cloud, juju add-credential will allow a new
credential to be added interactively. You will be prompted type the
required credential attributes. Example:

juju add-credential maas
  credential name: hmaas
  replace existing credential? [y/N]: y
  auth-type: oauth1
  maas-oauth:
credentials added for cloud maas

The new credentials.yaml file at: ~/.local/share/juju/credentials.yaml

The autoload tool will search for existing credentials for AWS,
OpenStack/Rackspace, and Google clouds. You will then be prompted for
which ones you'd like to save.

If you have an existing credential.yaml file, you can also import a
named credential, eg for MAAS

cat credentials.yaml

  credentials:
 maas:
   my-credentials:
 auth-type: oauth1
 maas-oauth: 

or, for AWS

cat credentials.yaml

  credentials:
aws:
  default-credential: my-credentials
  my-credentials:
auth-type: access-key
access-key: 
secret-key: 

Bootstrap using your default credentials:

 juju bootstrap  [/region]

Examples:

 juju bootstrap aws-controller aws

 juju bootstrap mass-controller maas/192.168.0.1

In the MAAS example above, you specify the host address of the MAAS
controller. So to use Juju on MAAS out of the box, you set up a
credentials file (either interactively, or based on the example above)
and then bootstrap. This avoids the need for any cloud configuration.
But it's also possible to set up a named MAAS cloud definition as
explained later.

More details on the new bootstrap experience, including defining private
clouds can be found in the New Bootstrap and Cloud Management Experience
section.


## Notable Changes

This releases addresses stability and performance issues.


## Resolved issues

  * Juju rc1 loses agents during a lxd deploy
Lp 1572237

  * Tools info mismatch on arch with lxd containers
Lp 1572781

  * 'failed to ensure lxd image' creating lxd container
Lp 1573149

  * Non-admin users unable to share models
Lp 1573259

  * Only one user can create local users
Lp 1573382

  * Maas provider bridge script deletes /etc/network/if-up.d/ntpdate
during bootstrap
Lp 1564397

  * Awaiting error resolution for "install" hook
Lp 1566130

  * Model uuids shown in some "romulus" command output
Lp 1571055

  * Panic in when bootstrapping maas 2.0
Lp 1573659

  * [lxd provider] trusty container is used by default on xenial host
Lp 1557747

  * Juju terms language confusing for locally-deployed charms
Lp 1573148


Finally

We encourage everyone to 

Re: LXC/LXD profiles through Juju

[Samuel Cozannet]

Hi Tom,

I've been doing what James says recently, it's fully operational.

Alternatively, when you use lxd, the output of juju status will tell you
the names of the containers, which you can then map to "lxc list"
==> you can apply different profiles individually to different units, even
post deployment.
The drawback is that you may need to restart some services inside the
containers when you do so, so some logic must be applied in this context.

++
Sam


--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of Cloud
Ubuntu   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]


On Sat, Apr 23, 2016 at 10:14 PM, Tom Barber 
wrote:

> Thanks chaps!
>
> I figured the worst comes to the worst I must be able to compile juju with
> the flag in there, but if there is a way like James suggests that means I
> don't have to, all the better :)
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> On 23 April 2016 at 21:12, Marco Ceppi  wrote:
>
>> While not a fix, you may be interested in this
>> https://bugs.launchpad.net/juju-core/+bug/1565872
>>
>> On Sat, Apr 23, 2016, 4:08 PM James Page  wrote:
>>
>>> Hi Tom
>>>
>>> On Sat, 23 Apr 2016 at 15:38 Tom Barber  wrote:
>>>
 Hello folks

 Working on my presentation for ApacheCon and trying to leverage some of
 the great new stuff available.

 I've not tested it yet, so this is a slightly lazy question but as I'm
 a way off of being at this stage I might as well ask in anticipation

 I want to run Docker inside LXD Local, which I can do manually by
 passing the docker profile. Does/Can you do the same inside Juju?

>>>
>>> I do something like that for some OpenStack on LXD stuff I've been
>>> working on:
>>>
>>>   https://github.com/openstack-charmers/openstack-on-lxd
>>>
>>> You can update the juju- profiles prior to  deploying any
>>> services to them which is a little coarse (model, not service level), but
>>> would let you use the docker profile for Juju managed LXD machines.
>>>
>>> Cheers
>>>
>>> James
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: DCOS on Juju

[Samuel Cozannet]

Hi Tom,

Adding also Artyom from DataArt as initial writers of the Mesos charms.
Artyom, it looks like we have a PoC for DC/OS charms. Let's coordinate also
with your team to see how we can get that further.

@Tom: No worries. Whenever you're ready send us links to the layers, and
we'll have a look.

So I have created this repo : https://github.com/SaMnCo/layers-dcos.git
so we can have all the code for all layers involved in one place. Empty for
now.

I've added a gitter here : https://gitter.im/SaMnCo/layers-dcos

Everyone interested please join this channel and let's move the
conversation there.

++
Sam






--
Samuel Cozannet
Cloud, Big Data and IoT Strategy Team
Business Development - Cloud and ISV Ecosystem
Changing the Future of Cloud
Ubuntu   / Canonical UK LTD  / Juju

samuel.cozan...@canonical.com
mob: +33 616 702 389
skype: samnco
Twitter: @SaMnCo_23
[image: View Samuel Cozannet's profile on LinkedIn]


On Mon, Apr 25, 2016 at 2:31 PM, Tom Barber  wrote:

> Hi smart people!
>
> I'll tidy up my initial DCOS dump and publish is over the next day or so.
> As a disclaimer, I'm no MESOS/DCOS expert so I'll defer to you guys on
> pretty much everything! ;)
>
> Tom
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> On 25 April 2016 at 12:31, Andy Petrella 
> wrote:
>
>> awesome, my turn to add Rad, who had created a terraform dcos integration
>> to be open sourced soon.
>> in combination with François you'll have all the information necessary
>>
>> On Mon, 25 Apr 2016 13:20 Samuel Cozannet, 
>> wrote:
>>
>>> Adding some smart people working with us on the Mesos stack.
>>>
>>> Andy, Adam, François, have a look at this DCOS charms.
>>> Tom, look at the project in my github (samnco/ods-dl)
>>>
>>> Let's open a gutter room later this week and see how we can collaborate
>>> on this
>>> On Apr 25, 2016 03:03, "Tom Barber"  wrote:
>>>
 GPU Mesos on Power, that sounds cool!

 I did originally just stand up Mesos again, but DCOS is in the news so
 I figured, why not.

 Okay sounds like a plan. Tomorrow is a bit rubbish, I'm around today
 and Wednesday though, just ping me off list with a time.

 Tom

 --

 Director Meteorite.bi - Saiku Analytics Founder
 Tel: +44(0)5603641316

 (Thanks to the Saiku community we reached our Kickstart
 
 goal, but you can always help by sponsoring the project
 )

 On 25 April 2016 at 01:06, Samuel Cozannet <
 samuel.cozan...@canonical.com> wrote:

> Tom,
>
> I've been working with a bunch of people on this as well for GPU
> enabled Mesos on Power. We're also doing more regarding DCOS Open Source.
>
> Let's connect and optimize who works on what. I am at OpenStack summit
> in Austin this week, but can do a call early in my mornings. Pick your 
> time
> and day.
>
> ++
> Sam
> On Apr 24, 2016 5:00 PM, "Tom Barber"  wrote:
>
>> Figured this was worth distributing to try and prevent duplicated
>> effort etc:
>>
>>
>> ​
>> Not ready for distribution yet, but I've stood up DCOS orchestration
>> as part of my ApacheCon demo (as its based on MESOS). Deploys master and
>> slave nodes to EC2 and works a treat(from a novice perspective).
>>
>> If anyone is interested in collaboration as my bandwidth is pretty
>> much maxed at the mo, let me know and we'll sort this stuff out.
>>
>> Tom
>> --
>>
>> Director Meteorite.bi - Saiku Analytics Founder
>> Tel: +44(0)5603641316
>>
>> (Thanks to the Saiku community we reached our Kickstart
>> 
>> goal, but you can always help by sponsoring the project
>> )
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: juju2: how to edit a maas "cloud"?

[Andreas Hasenack]

Forgot to include the list
On Apr 25, 2016 12:55, "Andreas Hasenack"  wrote:

> Uh, so in essence there are now three "files"? Cloud definition, config
> for that cloud and credentials? And the config has to be passed each time,
> whereas the other two are " imported"?
> On Apr 25, 2016 12:44, "Cheryl Jennings" 
> wrote:
>
>> Hi Andreas,
>>
>> The config is now separate from the cloud definition and can be passed in
>> when bootstrapping using --config:
>>
>> juju bootstrap scapestack scapestack --config bootstrap-timeout=1800
>>
>> You can also pass in a yaml file with config options if you don't want to
>> type them all out on the command line:
>>
>> $ cat scapestack-config.yaml
>> default-series: "trusty"
>> logging-config: "=DEBUG"
>> bootstrap-timeout: 1800
>>
>> $ juju bootstrap scapestack scapestack --config=scapestack-config.yaml
>>
>> Thanks!
>> -Cheryl
>>
>> On Mon, Apr 25, 2016 at 10:26 AM, Andreas Hasenack > > wrote:
>>
>>> On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack <
>>> andr...@canonical.com> wrote:
>>>
 Hi,

 I added a couple of maas servers to my cloud list:
 $ juju list-clouds
 CLOUD TYPEREGIONS
 aws   ec2 us-east-1, us-west-1, us-west-2,
 eu-west-1, eu-central-1, ap-southeast-1, ap-southeast-2 ...
 ...
 local:beretstack  maas
 local:scapestack  maas

 I now want to add a bootstrap-timeout parameter to each.

 How do I do that? Do I need to recreate the yaml definition for each
 maas "cloud", add the parameter, and add-cloud --replace it?

>>>
>>>
>>> That didn't work, btw:
>>>
>>> andreas@nsn7:~$ cat foo
>>> clouds:
>>> scapestack:
>>> type: maas
>>> auth-types: [oauth1]
>>> endpoint: http://10.96.0.10/MAAS/
>>> bootstrap-timeout: 1800
>>>
>>> andreas@nsn7:~$ juju add-cloud --replace scapestack foo
>>>
>>> andreas@nsn7:~$ juju show-cloud local:scapestack
>>> defined: local
>>> type: maas
>>> auth-types: [oauth1]
>>> endpoint: http://10.96.0.10/MAAS/
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: juju2: how to edit a maas "cloud"?

[Cheryl Jennings]

Hi Andreas,

The config is now separate from the cloud definition and can be passed in
when bootstrapping using --config:

juju bootstrap scapestack scapestack --config bootstrap-timeout=1800

You can also pass in a yaml file with config options if you don't want to
type them all out on the command line:

$ cat scapestack-config.yaml
default-series: "trusty"
logging-config: "=DEBUG"
bootstrap-timeout: 1800

$ juju bootstrap scapestack scapestack --config=scapestack-config.yaml

Thanks!
-Cheryl

On Mon, Apr 25, 2016 at 10:26 AM, Andreas Hasenack 
wrote:

> On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack 
> wrote:
>
>> Hi,
>>
>> I added a couple of maas servers to my cloud list:
>> $ juju list-clouds
>> CLOUD TYPEREGIONS
>> aws   ec2 us-east-1, us-west-1, us-west-2, eu-west-1,
>> eu-central-1, ap-southeast-1, ap-southeast-2 ...
>> ...
>> local:beretstack  maas
>> local:scapestack  maas
>>
>> I now want to add a bootstrap-timeout parameter to each.
>>
>> How do I do that? Do I need to recreate the yaml definition for each maas
>> "cloud", add the parameter, and add-cloud --replace it?
>>
>
>
> That didn't work, btw:
>
> andreas@nsn7:~$ cat foo
> clouds:
> scapestack:
> type: maas
> auth-types: [oauth1]
> endpoint: http://10.96.0.10/MAAS/
> bootstrap-timeout: 1800
>
> andreas@nsn7:~$ juju add-cloud --replace scapestack foo
>
> andreas@nsn7:~$ juju show-cloud local:scapestack
> defined: local
> type: maas
> auth-types: [oauth1]
> endpoint: http://10.96.0.10/MAAS/
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: juju2: how to edit a maas "cloud"?

[Andreas Hasenack]

On Mon, Apr 25, 2016 at 12:10 PM, Andreas Hasenack 
wrote:

> Hi,
>
> I added a couple of maas servers to my cloud list:
> $ juju list-clouds
> CLOUD TYPEREGIONS
> aws   ec2 us-east-1, us-west-1, us-west-2, eu-west-1,
> eu-central-1, ap-southeast-1, ap-southeast-2 ...
> ...
> local:beretstack  maas
> local:scapestack  maas
>
> I now want to add a bootstrap-timeout parameter to each.
>
> How do I do that? Do I need to recreate the yaml definition for each maas
> "cloud", add the parameter, and add-cloud --replace it?
>


That didn't work, btw:

andreas@nsn7:~$ cat foo
clouds:
scapestack:
type: maas
auth-types: [oauth1]
endpoint: http://10.96.0.10/MAAS/
bootstrap-timeout: 1800

andreas@nsn7:~$ juju add-cloud --replace scapestack foo

andreas@nsn7:~$ juju show-cloud local:scapestack
defined: local
type: maas
auth-types: [oauth1]
endpoint: http://10.96.0.10/MAAS/
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

juju2: how to edit a maas "cloud"?

[Andreas Hasenack]

Hi,

I added a couple of maas servers to my cloud list:
$ juju list-clouds
CLOUD TYPEREGIONS
aws   ec2 us-east-1, us-west-1, us-west-2, eu-west-1,
eu-central-1, ap-southeast-1, ap-southeast-2 ...
...
local:beretstack  maas
local:scapestack  maas

I now want to add a bootstrap-timeout parameter to each.

How do I do that? Do I need to recreate the yaml definition for each maas
"cloud", add the parameter, and add-cloud --replace it?
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: DCOS on Juju

[Tom Barber]

Hi smart people!

I'll tidy up my initial DCOS dump and publish is over the next day or so.
As a disclaimer, I'm no MESOS/DCOS expert so I'll defer to you guys on
pretty much everything! ;)

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 25 April 2016 at 12:31, Andy Petrella  wrote:

> awesome, my turn to add Rad, who had created a terraform dcos integration
> to be open sourced soon.
> in combination with François you'll have all the information necessary
>
> On Mon, 25 Apr 2016 13:20 Samuel Cozannet, 
> wrote:
>
>> Adding some smart people working with us on the Mesos stack.
>>
>> Andy, Adam, François, have a look at this DCOS charms.
>> Tom, look at the project in my github (samnco/ods-dl)
>>
>> Let's open a gutter room later this week and see how we can collaborate
>> on this
>> On Apr 25, 2016 03:03, "Tom Barber"  wrote:
>>
>>> GPU Mesos on Power, that sounds cool!
>>>
>>> I did originally just stand up Mesos again, but DCOS is in the news so I
>>> figured, why not.
>>>
>>> Okay sounds like a plan. Tomorrow is a bit rubbish, I'm around today and
>>> Wednesday though, just ping me off list with a time.
>>>
>>> Tom
>>>
>>> --
>>>
>>> Director Meteorite.bi - Saiku Analytics Founder
>>> Tel: +44(0)5603641316
>>>
>>> (Thanks to the Saiku community we reached our Kickstart
>>> 
>>> goal, but you can always help by sponsoring the project
>>> )
>>>
>>> On 25 April 2016 at 01:06, Samuel Cozannet <
>>> samuel.cozan...@canonical.com> wrote:
>>>
 Tom,

 I've been working with a bunch of people on this as well for GPU
 enabled Mesos on Power. We're also doing more regarding DCOS Open Source.

 Let's connect and optimize who works on what. I am at OpenStack summit
 in Austin this week, but can do a call early in my mornings. Pick your time
 and day.

 ++
 Sam
 On Apr 24, 2016 5:00 PM, "Tom Barber"  wrote:

> Figured this was worth distributing to try and prevent duplicated
> effort etc:
>
>
> ​
> Not ready for distribution yet, but I've stood up DCOS orchestration
> as part of my ApacheCon demo (as its based on MESOS). Deploys master and
> slave nodes to EC2 and works a treat(from a novice perspective).
>
> If anyone is interested in collaboration as my bandwidth is pretty
> much maxed at the mo, let me know and we'll sort this stuff out.
>
> Tom
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Xenial images on EC2

[Tom Barber]

Ta

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 25 April 2016 at 13:01, Mark Shuttleworth  wrote:

> On 25/04/16 03:05, Tom Barber wrote:
> > Morning all,
> >
> > I don't know what the process is for this, but someone here will surely
> > know. Whats the roadmap/timeline to getting Xenial images in EC2?
>
> Just squaring away some details with AWS then they will be up, I think
> this week.
>
> Mark
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Xenial images on EC2

[Mark Shuttleworth]

On 25/04/16 03:05, Tom Barber wrote:
> Morning all,
>
> I don't know what the process is for this, but someone here will surely
> know. Whats the roadmap/timeline to getting Xenial images in EC2?

Just squaring away some details with AWS then they will be up, I think
this week.

Mark

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Backwards incompatible change to config.changed states

[Mark Shuttleworth]

I'd ask Cory to explore Merlijn's suggestions more deeply before we add
another state.

Mark

On 25/04/16 02:11, James Beedy wrote:
> I think this is an excellent idea! The the initial setting of the
> config.changed hook has caused contention in charm design and
> implementation for me. Not having to account for the config.changed hooks
> firing, when logically it seems that one shouldn't have to (e.g. no configs
> have changed yet), would probably ease uptake for new-comers who aren't
> familiar with the intrinsics of why a config.changed hook fires without
> configs changing. I think Cory's implementation is a non-intrusive way of
> handling this issue whilst also providing backwards compatibility for the
> legacy functionality.
>
>> I have proposed https://github.com/juju-solutions/layer-basic/pull/61 as a
>> slight change to how the config.changed states from the basic layer work.
>> Currently, the changed states are set during the first hook invocation,
>> under the assumption that the values were "changed" from "nothing" (not
>> being set at all).  However, this is slightly problematic in a case like
>> the following, where we expect install() to  only be called once, unless
>> the value has changed after the fact:
>>
>> @when_not('installed')def install():
>> # do install
>> set_state('installed')
>> @when('config.changed.install_source')def reinstall():
>> install()
>>
>>
>> The proposal adds new states, config.new, and changes config.changed to
> not
>> be set the first time.  You could get the old behavior by saying
>> @when_any('config.new.foo', 'config.changed.foo').
>>
>> Is anyone depending on the current behavior?  Are there any objections to
>> this change?
>>
>>
>>
>
>

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: 16.04 OpenStack charm release

[John Meinel]

I'm curious if we've looked into throttling to improve things. I've done
some parallel testing in the past, and I've seen a few times where just
adding units sequentially was actually faster than parallel because of
contention.

I wonder if we might want to introduce some sort of rate limiting across
containers, so when you change something you don't have all 10 containers
wake up at the same time and try to apply that change. Though figuring out
a reasonable number that doesn't slow down results when you have enough
hardware can be tricky.

John
=:->


On Sat, Apr 23, 2016 at 6:50 PM, Daniel Westervelt <
daniel.westerv...@canonical.com> wrote:

> With a mixture of LVM and LXC it used to be 12 GB and 8 cores. With pure
> LXD+NCLXD we can do it with less, just not sure how much less yet. I will
> say you start to hit disk IO contention on install as there are a lot of
> units installing all at the same time. We plan on doing an optimization
> review once all the major kinks are out.
>
> - Daniel
>
> Sent from my iPhone
>
> On Apr 23, 2016, at 10:35 AM, Adam Stokes 
> wrote:
>
> I don't think it's a hard rule it is just the hardware I have at the time.
> I'm fixing a few things today and will test on my laptop's once I upgrade
> them to xenial. I can update that section of the site once I figure out the
> minimal requirements
>
> On Sat, Apr 23, 2016, 10:31 AM Mark Baker 
> wrote:
>
>> In the "Get Started" section it states:
>>
>> "For localhost deployments utilizing Juju's LXD provider you will need at
>> least a system with 8 CPUs and 8G RAM."
>>
>> Is this really 8 processors or is it cores? Even 8 cores seems excessive
>> and will rule out many developer laptops.
>>
>>
>>
>> Best Regards
>>
>>
>>
>> Mark Baker
>> On Sat, Apr 23, 2016 at 9:17 AM, Mark Shuttleworth 
>> wrote:
>>
>>> On 23/04/16 09:10, Adam Stokes wrote:
>>>
>>> Also we have conjure-up.io up and running as well.
>>>
>>>
>>> Love it! This makes it really easy to add a deb package to Ubuntu that
>>> wraps any Juju bundle.
>>>
>>> Mark
>>>
>>> --
>>> Cloud mailing list
>>> cl...@lists.canonical.com
>>> Modify settings or unsubscribe at:
>>> https://lists.canonical.com/mailman/listinfo/cloud
>>>
>>> --
> Cloud mailing list
> cl...@lists.canonical.com
> Modify settings or unsubscribe at:
> https://lists.canonical.com/mailman/listinfo/cloud
>
>
> --
> Cloud mailing list
> cl...@lists.canonical.com
> Modify settings or unsubscribe at:
> https://lists.canonical.com/mailman/listinfo/cloud
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: DCOS on Juju

[Samuel Cozannet]

Adding some smart people working with us on the Mesos stack.

Andy, Adam, François, have a look at this DCOS charms.
Tom, look at the project in my github (samnco/ods-dl)

Let's open a gutter room later this week and see how we can collaborate on
this
On Apr 25, 2016 03:03, "Tom Barber"  wrote:

> GPU Mesos on Power, that sounds cool!
>
> I did originally just stand up Mesos again, but DCOS is in the news so I
> figured, why not.
>
> Okay sounds like a plan. Tomorrow is a bit rubbish, I'm around today and
> Wednesday though, just ping me off list with a time.
>
> Tom
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> On 25 April 2016 at 01:06, Samuel Cozannet 
> wrote:
>
>> Tom,
>>
>> I've been working with a bunch of people on this as well for GPU enabled
>> Mesos on Power. We're also doing more regarding DCOS Open Source.
>>
>> Let's connect and optimize who works on what. I am at OpenStack summit in
>> Austin this week, but can do a call early in my mornings. Pick your time
>> and day.
>>
>> ++
>> Sam
>> On Apr 24, 2016 5:00 PM, "Tom Barber"  wrote:
>>
>>> Figured this was worth distributing to try and prevent duplicated effort
>>> etc:
>>>
>>>
>>> ​
>>> Not ready for distribution yet, but I've stood up DCOS orchestration as
>>> part of my ApacheCon demo (as its based on MESOS). Deploys master and slave
>>> nodes to EC2 and works a treat(from a novice perspective).
>>>
>>> If anyone is interested in collaboration as my bandwidth is pretty much
>>> maxed at the mo, let me know and we'll sort this stuff out.
>>>
>>> Tom
>>> --
>>>
>>> Director Meteorite.bi - Saiku Analytics Founder
>>> Tel: +44(0)5603641316
>>>
>>> (Thanks to the Saiku community we reached our Kickstart
>>> 
>>> goal, but you can always help by sponsoring the project
>>> )
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Xenial images on EC2

[Tom Barber]

Morning all,

I don't know what the process is for this, but someone here will surely
know. Whats the roadmap/timeline to getting Xenial images in EC2?

Cheers

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: DCOS on Juju

[Tom Barber]

As people may have noticed I did try and stand it up in LXD Local as well,
sadly currently that (unsurprisingly) doesn't work ;(

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 25 April 2016 at 09:02, Tom Barber  wrote:

> GPU Mesos on Power, that sounds cool!
>
> I did originally just stand up Mesos again, but DCOS is in the news so I
> figured, why not.
>
> Okay sounds like a plan. Tomorrow is a bit rubbish, I'm around today and
> Wednesday though, just ping me off list with a time.
>
> Tom
>
> --
>
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
>
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )
>
> On 25 April 2016 at 01:06, Samuel Cozannet 
> wrote:
>
>> Tom,
>>
>> I've been working with a bunch of people on this as well for GPU enabled
>> Mesos on Power. We're also doing more regarding DCOS Open Source.
>>
>> Let's connect and optimize who works on what. I am at OpenStack summit in
>> Austin this week, but can do a call early in my mornings. Pick your time
>> and day.
>>
>> ++
>> Sam
>> On Apr 24, 2016 5:00 PM, "Tom Barber"  wrote:
>>
>>> Figured this was worth distributing to try and prevent duplicated effort
>>> etc:
>>>
>>>
>>> ​
>>> Not ready for distribution yet, but I've stood up DCOS orchestration as
>>> part of my ApacheCon demo (as its based on MESOS). Deploys master and slave
>>> nodes to EC2 and works a treat(from a novice perspective).
>>>
>>> If anyone is interested in collaboration as my bandwidth is pretty much
>>> maxed at the mo, let me know and we'll sort this stuff out.
>>>
>>> Tom
>>> --
>>>
>>> Director Meteorite.bi - Saiku Analytics Founder
>>> Tel: +44(0)5603641316
>>>
>>> (Thanks to the Saiku community we reached our Kickstart
>>> 
>>> goal, but you can always help by sponsoring the project
>>> )
>>>
>>> --
>>> Juju mailing list
>>> Juju@lists.ubuntu.com
>>> Modify settings or unsubscribe at:
>>> https://lists.ubuntu.com/mailman/listinfo/juju
>>>
>>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: DCOS on Juju

[Tom Barber]

GPU Mesos on Power, that sounds cool!

I did originally just stand up Mesos again, but DCOS is in the news so I
figured, why not.

Okay sounds like a plan. Tomorrow is a bit rubbish, I'm around today and
Wednesday though, just ping me off list with a time.

Tom

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 25 April 2016 at 01:06, Samuel Cozannet 
wrote:

> Tom,
>
> I've been working with a bunch of people on this as well for GPU enabled
> Mesos on Power. We're also doing more regarding DCOS Open Source.
>
> Let's connect and optimize who works on what. I am at OpenStack summit in
> Austin this week, but can do a call early in my mornings. Pick your time
> and day.
>
> ++
> Sam
> On Apr 24, 2016 5:00 PM, "Tom Barber"  wrote:
>
>> Figured this was worth distributing to try and prevent duplicated effort
>> etc:
>>
>>
>> ​
>> Not ready for distribution yet, but I've stood up DCOS orchestration as
>> part of my ApacheCon demo (as its based on MESOS). Deploys master and slave
>> nodes to EC2 and works a treat(from a novice perspective).
>>
>> If anyone is interested in collaboration as my bandwidth is pretty much
>> maxed at the mo, let me know and we'll sort this stuff out.
>>
>> Tom
>> --
>>
>> Director Meteorite.bi - Saiku Analytics Founder
>> Tel: +44(0)5603641316
>>
>> (Thanks to the Saiku community we reached our Kickstart
>> 
>> goal, but you can always help by sponsoring the project
>> )
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Backwards incompatible change to config.changed states

[Stuart Bishop]

On 23 April 2016 at 04:02, Cory Johns  wrote:

> Is anyone depending on the current behavior?  Are there any objections to
> this change?

I can argue both designs, but think that the most useful one is what
you are proposing (config.changed not being set in the first hook,
which is not necessarily the install hook).

If you are clarifying this, you should also clarify how things work in
the upgrade-charm hook when new config options are added or removed.

Your proposed change does not affect my work, and will allow me to
simplify some things.

-- 
Stuart Bishop 

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Backwards incompatible change to config.changed states

[James Beedy]

I think this is an excellent idea! The the initial setting of the
config.changed hook has caused contention in charm design and
implementation for me. Not having to account for the config.changed hooks
firing, when logically it seems that one shouldn't have to (e.g. no configs
have changed yet), would probably ease uptake for new-comers who aren't
familiar with the intrinsics of why a config.changed hook fires without
configs changing. I think Cory's implementation is a non-intrusive way of
handling this issue whilst also providing backwards compatibility for the
legacy functionality.

> I have proposed https://github.com/juju-solutions/layer-basic/pull/61 as a
> slight change to how the config.changed states from the basic layer work.
> Currently, the changed states are set during the first hook invocation,
> under the assumption that the values were "changed" from "nothing" (not
> being set at all).  However, this is slightly problematic in a case like
> the following, where we expect install() to  only be called once, unless
> the value has changed after the fact:
>
> @when_not('installed')def install():
> # do install
> set_state('installed')
> @when('config.changed.install_source')def reinstall():
> install()
>
>
> The proposal adds new states, config.new, and changes config.changed to
not
> be set the first time.  You could get the old behavior by saying
> @when_any('config.new.foo', 'config.changed.foo').
>
> Is anyone depending on the current behavior?  Are there any objections to
> this change?
>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju