Re: Juju 2.0 is here!

[Tim Penhey]

I concur. You only have to use 1.25 for a short while again to see how 
far Juju has come.


Be proud of your work, celebrate the release.

Go team!

Tim

On 14/10/16 17:50, Mark Shuttleworth wrote:


Congrats everyone, this is a release to be proud of. Multi-user
multi-model, great CLI, it's a joy to train people on it. Well done.

Mark

On 14/10/16 06:34, Nicholas Skaggs wrote:

Juju 2.0 is here! This release has been a year in the making. We’d
like to thank everyone for their feedback, testing, and adoption of
juju 2.0 throughout its development process! Juju brings refinements
in ease of use, while adding support for new clouds and features.

## New to juju 2?

https://jujucharms.com/docs/2.0/getting-started

## Need to install it?

If you are running Ubuntu, you can get it from the juju stable ppa:

sudo add-apt-repository ppa:juju/stable
sudo apt update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0.0

## Want to upgrade to GA?

Those of you running an RC version of juju 2 can upgrade to this
release by running:

juju upgrade-juju

## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
juju@lists.ubuntu.com and join us on #juju on freenode. We would love
to hear
your feedback and usage of juju.







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

Re: Juju 2.0 is here!

[Tim Penhey]

I concur. You only have to use 1.25 for a short while again to see how 
far Juju has come.


Be proud of your work, celebrate the release.

Go team!

Tim

On 14/10/16 17:50, Mark Shuttleworth wrote:


Congrats everyone, this is a release to be proud of. Multi-user
multi-model, great CLI, it's a joy to train people on it. Well done.

Mark

On 14/10/16 06:34, Nicholas Skaggs wrote:

Juju 2.0 is here! This release has been a year in the making. We’d
like to thank everyone for their feedback, testing, and adoption of
juju 2.0 throughout its development process! Juju brings refinements
in ease of use, while adding support for new clouds and features.

## New to juju 2?

https://jujucharms.com/docs/2.0/getting-started

## Need to install it?

If you are running Ubuntu, you can get it from the juju stable ppa:

sudo add-apt-repository ppa:juju/stable
sudo apt update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0.0

## Want to upgrade to GA?

Those of you running an RC version of juju 2 can upgrade to this
release by running:

juju upgrade-juju

## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
j...@lists.ubuntu.com and join us on #juju on freenode. We would love
to hear
your feedback and usage of juju.







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

Re: Juju 2.0 is here!

[Mark Shuttleworth]

Congrats everyone, this is a release to be proud of. Multi-user
multi-model, great CLI, it's a joy to train people on it. Well done.

Mark

On 14/10/16 06:34, Nicholas Skaggs wrote:
> Juju 2.0 is here! This release has been a year in the making. We’d
> like to thank everyone for their feedback, testing, and adoption of
> juju 2.0 throughout its development process! Juju brings refinements
> in ease of use, while adding support for new clouds and features.
>
> ## New to juju 2?
>
> https://jujucharms.com/docs/2.0/getting-started
>
> ## Need to install it?
>
> If you are running Ubuntu, you can get it from the juju stable ppa:
>
> sudo add-apt-repository ppa:juju/stable
> sudo apt update; sudo apt install juju-2.0
>
> Or install it from the snap store
>
> snap install juju --beta --devmode
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0.0
>
> ## Want to upgrade to GA?
>
> Those of you running an RC version of juju 2 can upgrade to this
> release by running:
>
> juju upgrade-juju
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju@lists.ubuntu.com and join us on #juju on freenode. We would love
> to hear
> your feedback and usage of juju.
>
>


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

Re: Juju 2.0 is here!

[Mark Shuttleworth]

Congrats everyone, this is a release to be proud of. Multi-user
multi-model, great CLI, it's a joy to train people on it. Well done.

Mark

On 14/10/16 06:34, Nicholas Skaggs wrote:
> Juju 2.0 is here! This release has been a year in the making. We’d
> like to thank everyone for their feedback, testing, and adoption of
> juju 2.0 throughout its development process! Juju brings refinements
> in ease of use, while adding support for new clouds and features.
>
> ## New to juju 2?
>
> https://jujucharms.com/docs/2.0/getting-started
>
> ## Need to install it?
>
> If you are running Ubuntu, you can get it from the juju stable ppa:
>
> sudo add-apt-repository ppa:juju/stable
> sudo apt update; sudo apt install juju-2.0
>
> Or install it from the snap store
>
> snap install juju --beta --devmode
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0.0
>
> ## Want to upgrade to GA?
>
> Those of you running an RC version of juju 2 can upgrade to this
> release by running:
>
> juju upgrade-juju
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> j...@lists.ubuntu.com and join us on #juju on freenode. We would love
> to hear
> your feedback and usage of juju.
>
>


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

Re: Juju 2.0 is here!

[José Antonio Rey]

Congratulations to everyone that has been involved on this release! It's 
very exciting for me to read this email.


Infinite thanks to all of those involved developing this new Juju 
version and refining every bit of it. I know it's been a long and 
tedious process, but it's finally landed.


Thanks to all of those who tested and made sure no bugs were left to squash.

Again, congratulations, you rock :)

On 10/13/2016 11:34 PM, Nicholas Skaggs wrote:

Juju 2.0 is here! This release has been a year in the making. We’d like
to thank everyone for their feedback, testing, and adoption of juju 2.0
throughout its development process! Juju brings refinements in ease of
use, while adding support for new clouds and features.

## New to juju 2?

https://jujucharms.com/docs/2.0/getting-started

## Need to install it?

If you are running Ubuntu, you can get it from the juju stable ppa:

sudo add-apt-repository ppa:juju/stable
sudo apt update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0.0

## Want to upgrade to GA?

Those of you running an RC version of juju 2 can upgrade to this release
by running:

juju upgrade-juju

## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
hear
your feedback and usage of juju.





--
José Antonio Rey

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

Re: Juju 2.0 is here!

[Alexis Bruemmer]

WOOT!

On Thu, Oct 13, 2016 at 9:34 PM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:

> Juju 2.0 is here! This release has been a year in the making. We’d like to
> thank everyone for their feedback, testing, and adoption of juju 2.0
> throughout its development process! Juju brings refinements in ease of use,
> while adding support for new clouds and features.
>
> ## New to juju 2?
>
> https://jujucharms.com/docs/2.0/getting-started
>
> ## Need to install it?
>
> If you are running Ubuntu, you can get it from the juju stable ppa:
>
> sudo add-apt-repository ppa:juju/stable
> sudo apt update; sudo apt install juju-2.0
>
> Or install it from the snap store
>
> snap install juju --beta --devmode
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0.0
>
> ## Want to upgrade to GA?
>
> Those of you running an RC version of juju 2 can upgrade to this release
> by running:
>
> juju upgrade-juju
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> juju@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> --
> Juju-dev mailing list
> juju-...@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
>



-- 
Alexis Bruemmer
Juju Core Manager, Canonical Ltd.
(503) 686-5018
alexis.bruem...@canonical.com
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Juju 2.0 is here!

[Alexis Bruemmer]

WOOT!

On Thu, Oct 13, 2016 at 9:34 PM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:

> Juju 2.0 is here! This release has been a year in the making. We’d like to
> thank everyone for their feedback, testing, and adoption of juju 2.0
> throughout its development process! Juju brings refinements in ease of use,
> while adding support for new clouds and features.
>
> ## New to juju 2?
>
> https://jujucharms.com/docs/2.0/getting-started
>
> ## Need to install it?
>
> If you are running Ubuntu, you can get it from the juju stable ppa:
>
> sudo add-apt-repository ppa:juju/stable
> sudo apt update; sudo apt install juju-2.0
>
> Or install it from the snap store
>
> snap install juju --beta --devmode
>
> Windows, Centos, and MacOS users can get a corresponding installer at:
>
> https://launchpad.net/juju/+milestone/2.0.0
>
> ## Want to upgrade to GA?
>
> Those of you running an RC version of juju 2 can upgrade to this release
> by running:
>
> juju upgrade-juju
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe the mailing list at
> j...@lists.ubuntu.com and join us on #juju on freenode. We would love to
> hear
> your feedback and usage of juju.
>
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju-dev
>



-- 
Alexis Bruemmer
Juju Core Manager, Canonical Ltd.
(503) 686-5018
alexis.bruem...@canonical.com
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Juju 2.0 is here!

[Nicholas Skaggs]

Juju 2.0 is here! This release has been a year in the making. We’d like 
to thank everyone for their feedback, testing, and adoption of juju 2.0 
throughout its development process! Juju brings refinements in ease of 
use, while adding support for new clouds and features.


## New to juju 2?

https://jujucharms.com/docs/2.0/getting-started

## Need to install it?

If you are running Ubuntu, you can get it from the juju stable ppa:

sudo add-apt-repository ppa:juju/stable
sudo apt update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0.0

## Want to upgrade to GA?

Those of you running an RC version of juju 2 can upgrade to this release 
by running:


juju upgrade-juju

## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
juju@lists.ubuntu.com and join us on #juju on freenode. We would love to 
hear

your feedback and usage of juju.


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

Juju 2.0 is here!

[Nicholas Skaggs]

Juju 2.0 is here! This release has been a year in the making. We’d like 
to thank everyone for their feedback, testing, and adoption of juju 2.0 
throughout its development process! Juju brings refinements in ease of 
use, while adding support for new clouds and features.


## New to juju 2?

https://jujucharms.com/docs/2.0/getting-started

## Need to install it?

If you are running Ubuntu, you can get it from the juju stable ppa:

sudo add-apt-repository ppa:juju/stable
sudo apt update; sudo apt install juju-2.0

Or install it from the snap store

snap install juju --beta --devmode

Windows, Centos, and MacOS users can get a corresponding installer at:

https://launchpad.net/juju/+milestone/2.0.0

## Want to upgrade to GA?

Those of you running an RC version of juju 2 can upgrade to this release 
by running:


juju upgrade-juju

## Feedback Appreciated!

We encourage everyone to subscribe the mailing list at
j...@lists.ubuntu.com and join us on #juju on freenode. We would love to 
hear

your feedback and usage of juju.


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

Re: Github Reviews vs Reviewboard

[Tim Penhey]

-1, like Menno I was initially quite hopeful for the github reviews.

My main concerns are around easily having a list to pull from, and being 
able to see status, comments on a single dashboard.


Tim

On 14/10/16 11:44, Menno Smits wrote:

We've been trialling Github Reviews for some time now and it's time to
decide whether we stick with it or go back to Reviewboard.

We're going to have a vote. If you have an opinion on the issue please
reply to this email with a +1, 0 or -1, optionally followed by any
further thoughts.

  * +1 means you prefer Github Reviews
  * -1 means you prefer Reviewboard
  * 0 means you don't mind.

If you don't mind which review system we use there's no need to reply
unless you want to voice some opinions.

The voting period starts *now* and ends my*EOD next Friday (October 21)*.

As a refresher, here are the concerns raised for each option.

*Github Reviews*

  * Comments disrupt the flow of the code and can't be minimised,
hindering readability.
  * Comments can't be marked as done making it hard to see what's still
to be taken care of.
  * There's no way to distinguish between a problem and a comment.
  * There's no summary of issues raised. You need to scroll through the
often busy discussion page.
  * There's no indication of which PRs have been reviewed from the pull
request index page nor is it possible to see which PRs have been
approved or otherwise.
  * It's hard to see when a review has been updated.

*Reviewboard*

  * Another piece of infrastructure for us to maintain
  * Higher barrier to entry for newcomers and outside contributors
  * Occasionally misses Github pull requests (likely a problem with our
integration so is fixable)
  * Poor handling of deleted and renamed files
  * Falls over with very large diffs
  * 1990's looks :)
  * May make future integration of tools which work with Github into our
process more difficult (e.g. static analysis or automated review tools)

There has been talk of evaluating other review tools such as Gerrit and
that may still happen. For now, let's decide between the two options we
have recent experience with.

- Menno




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

Re: Github Reviews vs Reviewboard

[Menno Smits]

-1

I was really excited by Github Reviews initially but after using it for a
while I've switched my position.

On 14 October 2016 at 11:44, Menno Smits  wrote:

> We've been trialling Github Reviews for some time now and it's time to
> decide whether we stick with it or go back to Reviewboard.
>
> We're going to have a vote. If you have an opinion on the issue please
> reply to this email with a +1, 0 or -1, optionally followed by any further
> thoughts.
>
>- +1 means you prefer Github Reviews
>- -1 means you prefer Reviewboard
>- 0 means you don't mind.
>
> If you don't mind which review system we use there's no need to reply
> unless you want to voice some opinions.
>
> The voting period starts *now* and ends my* EOD next Friday (October 21)*.
>
> As a refresher, here are the concerns raised for each option.
>
> *Github Reviews*
>
>- Comments disrupt the flow of the code and can't be minimised,
>hindering readability.
>- Comments can't be marked as done making it hard to see what's still
>to be taken care of.
>- There's no way to distinguish between a problem and a comment.
>- There's no summary of issues raised. You need to scroll through the
>often busy discussion page.
>- There's no indication of which PRs have been reviewed from the pull
>request index page nor is it possible to see which PRs have been approved
>or otherwise.
>- It's hard to see when a review has been updated.
>
> *Reviewboard*
>
>- Another piece of infrastructure for us to maintain
>- Higher barrier to entry for newcomers and outside contributors
>- Occasionally misses Github pull requests (likely a problem with our
>integration so is fixable)
>- Poor handling of deleted and renamed files
>- Falls over with very large diffs
>- 1990's looks :)
>- May make future integration of tools which work with Github into our
>process more difficult (e.g. static analysis or automated review tools)
>
> There has been talk of evaluating other review tools such as Gerrit and
> that may still happen. For now, let's decide between the two options we
> have recent experience with.
>
> - Menno
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Github Reviews vs Reviewboard

[Ian Booth]

-1000 :-)

On 14/10/16 08:44, Menno Smits wrote:
> We've been trialling Github Reviews for some time now and it's time to
> decide whether we stick with it or go back to Reviewboard.
> 
> We're going to have a vote. If you have an opinion on the issue please
> reply to this email with a +1, 0 or -1, optionally followed by any further
> thoughts.
> 
>- +1 means you prefer Github Reviews
>- -1 means you prefer Reviewboard
>- 0 means you don't mind.
> 
> If you don't mind which review system we use there's no need to reply
> unless you want to voice some opinions.
> 
> The voting period starts *now* and ends my* EOD next Friday (October 21)*.
> 
> As a refresher, here are the concerns raised for each option.
> 
> *Github Reviews*
> 
>- Comments disrupt the flow of the code and can't be minimised,
>hindering readability.
>- Comments can't be marked as done making it hard to see what's still to
>be taken care of.
>- There's no way to distinguish between a problem and a comment.
>- There's no summary of issues raised. You need to scroll through the
>often busy discussion page.
>- There's no indication of which PRs have been reviewed from the pull
>request index page nor is it possible to see which PRs have been approved
>or otherwise.
>- It's hard to see when a review has been updated.
> 
> *Reviewboard*
> 
>- Another piece of infrastructure for us to maintain
>- Higher barrier to entry for newcomers and outside contributors
>- Occasionally misses Github pull requests (likely a problem with our
>integration so is fixable)
>- Poor handling of deleted and renamed files
>- Falls over with very large diffs
>- 1990's looks :)
>- May make future integration of tools which work with Github into our
>process more difficult (e.g. static analysis or automated review tools)
> 
> There has been talk of evaluating other review tools such as Gerrit and
> that may still happen. For now, let's decide between the two options we
> have recent experience with.
> 
> - Menno
> 
> 
> 

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

Github Reviews vs Reviewboard

[Menno Smits]

We've been trialling Github Reviews for some time now and it's time to
decide whether we stick with it or go back to Reviewboard.

We're going to have a vote. If you have an opinion on the issue please
reply to this email with a +1, 0 or -1, optionally followed by any further
thoughts.

   - +1 means you prefer Github Reviews
   - -1 means you prefer Reviewboard
   - 0 means you don't mind.

If you don't mind which review system we use there's no need to reply
unless you want to voice some opinions.

The voting period starts *now* and ends my* EOD next Friday (October 21)*.

As a refresher, here are the concerns raised for each option.

*Github Reviews*

   - Comments disrupt the flow of the code and can't be minimised,
   hindering readability.
   - Comments can't be marked as done making it hard to see what's still to
   be taken care of.
   - There's no way to distinguish between a problem and a comment.
   - There's no summary of issues raised. You need to scroll through the
   often busy discussion page.
   - There's no indication of which PRs have been reviewed from the pull
   request index page nor is it possible to see which PRs have been approved
   or otherwise.
   - It's hard to see when a review has been updated.

*Reviewboard*

   - Another piece of infrastructure for us to maintain
   - Higher barrier to entry for newcomers and outside contributors
   - Occasionally misses Github pull requests (likely a problem with our
   integration so is fixable)
   - Poor handling of deleted and renamed files
   - Falls over with very large diffs
   - 1990's looks :)
   - May make future integration of tools which work with Github into our
   process more difficult (e.g. static analysis or automated review tools)

There has been talk of evaluating other review tools such as Gerrit and
that may still happen. For now, let's decide between the two options we
have recent experience with.

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

[ANN] Canonical Distribution of Kubernetes Release Notes [week of 10/13]

[Charles Butler]

10/13 Release Notes

Greetings everyone! It's been a short but busy week for us.  We've landed a
lot more bugfixes and some new features for you all to kick the tires.
We're excited to push this week’s rollup as it contains the early work
(alpha?) in consuming Ceph RBD volumes for persistent volume storage in
your kubernetes workloads.

It’s missing from the readme, so here is a quick rundown below the release
notes.  As always, bugs/comments/questions are all welcome.
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues

Or you can find us on irc in #juju on irc.freenode.net


Layer-docker


   -

   Added DOCKER_OPTS passthrough config option. This enables end users to
   configure the runtime of their docker-engine (Such as insecure registries)
   without having to add python code to the layers and/or re-build a fork.


   -

   Corrected an immutable config when attempting to switch between archive
   docker package and the docker-engine package from upstream.


Thanks @brianlbaird and @simonklb for driving this feature during
dev/testing.

Flannel


   -

   Corrected the directory glob pattern on flannel which was failing and
   causing some false positives in the cloud weather report testing tool.


Kubernetes Master

   -

   Added a create-rbd-pv action to enlist persistent storage from Ceph.
   -

  This requires the use of the ceph-mon charm from the
  openstack-charmers-next branch.
  -

   Closed a bug where running microbots would yield an EOF error due to
   proxy settings. Consult the README for limited egress environments. (Thanks
   @ryebot and @cynerva)


Kubernetes Worker

   -

   Added a kubectl wrapper for context with manifests, and a kubectl
   wrapper for arbitrary keyword args.
   -

   Various lint fixes.
   -

   Worker nodes now cleanly remove themselves from the cluster during the
   stop hook. (Thanks to @ryebot and @cynerva)
   -

   The ingress controller now scales to the number of deployed worker
   units. 1 ingress controller per 1 worker unit. (Thanks to @ryebot and
   @cynerva)


Canonical Distribution of Kubernetes Bundle


   -

   Added documentation for proxy settings in network limited environments
   to the bundle README. (Thanks to @ryebot and @cynerva)
   -

   Updated the README with additional limitation notes about which charms
   are not compatible enough to run in LXD at this time.
   -

   Bumped each charm to their latest revision.


Kubernetes Core Bundle

A minimalist bundle, only deploying the bare minimum required to evaluate
kubernetes. Useful when doing laptop development or resource constrained
environments. (Thanks @cynerva and @ryebot)



   -

   The kubernetes core bundle has been updated with our latest release of
   the Canonical Distribution of Kubernetes (CDK) charms.
   -

   Brand new README imported from the CDK bundle.


https://github.com/juju-solutions/bundle-kubernetes-core  - we’re still
testing this minimal bundle, and it will be published in the charm store as
early as next week. Thanks for your early interest!

Etcd

   -

   Refactored the test to gate on the status messages before reading the
   deployment as ready and proceeding with executing tests.



Quick Rundown on how to enlist RBD PV’s

You’ll need to be running at bare-minimum the ceph-mon charm from the
~openstack-charmers-next namespace.

juju deploy cs:~openstack-charmers-next/xenial/ceph-mon -n 3

juju deploy cs:ceph-osd -n 3

>From here you will need to enlist the OSD storage devices:

For example on GCE you would fulfill this request with GCE Persistent Disks:

juju add-storage ceph-osd/0 osd-devices=gce,10gb

juju add-storage ceph-osd/1 osd-devices=gce,10gb

juju add-storage ceph-osd/2 osd-devices=gce,10gb

This will allocate 30gb of storage, across the 3 OSD device nodes, and
begin your ceph replicated file storage cluster.

Next is to relate the storage cluster with the kubernetes master:

juju add-relation kubernetes-master ceph-mon

We’re now ready to enlist Persistent Volumes in Kubernetes which our
workloads can consume via PersistentVolumeClaims

juju run-action kubernetes-master/0 create-rbd-pv name=test size=50

Tailing a watch on your kubernetes cluster like the following, you should
see the PV become enlisted and be marked as available:

watch kubectl get pv --all-namespaces

NAME CAPACITY   ACCESSMODES   STATUSCLAIM  REASONAGE

test   50M  RWO   Available  10s


To consume these Persistent Volumes, your pods will need an associated PVC
with them, and is outside the scope of this tutorial. See:
http://kubernetes.io/docs/user-guide/persistent-volumes/  for more
information.

This work is early so please let us know if you using storage and remember
to open issues at:
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues

-- 
Juju Charmer
Canonical Group Ltd.
Ubuntu - Linux for human beings | www.ubuntu.com
Juju - The fastest way to model your 

Re: Issue deploying a juju controller on openstack private cloud

[Ian Booth]

Hi Sergio

Courtesy of Rick Harding, here's the information you need.

The openstack provider has a network configuration attribute which needs to be
set to specify the network label or UUID to bring machines up on when multiple
networks exist.

You pass it as an argument to bootstrap. eg

$ juju bootstrap openstack-controller openstack-mitaka
--config image-metadata-url=http://10.2.1.109/simplestream/images/
--config network=

On 13/10/16 06:29, sergio gonzalez wrote:
> Hello
> 
> I am trying to deploy a juju controller, but I get the following error:
> 
> juju --debug bootstrap openstack-controller openstack-mitaka --config
> image-metadata-url=http://10.2.1.109/simplestream/images/
> 
> 2016-10-12 20:19:00 INFO juju.cmd supercommand.go:63 running juju
> [2.0-beta15 gc go1.6.2]
> 
> 2016-10-12 20:19:00 INFO cmd cmd.go:141 Adding contents of
> "/home/ubuntu/.local/share/juju/ssh/juju_id_rsa.pub" to
> authorized-keys
> 
> 2016-10-12 20:19:00 DEBUG juju.cmd.juju.commands bootstrap.go:499
> preparing controller with config: map[name:controller
> uuid:71e55928-2c38-407b-897f-94e83c60890b
> image-metadata-url:http://10.2.1.109/simplestream/images/
> authorized-keys:ssh-rsa
> B3NzaC1yc2EDAQABAAABAQDBoDbcBms7z/ChSG5hQyqZQYhkH6V5uA7HcINuFJH2AC9ygej6TdJ6eCdsPU77x+CgdRVLINE1PhtWsXdYFEZ11e7OV2Y4Jlt/SkMqGJK4enHNXcofIBUntbuVh90hww/yiApLxxi4/cMgHTigu4YZbkZz+QVBqCn5zZMgqPbSR55uHGsT9cbF1S+XRj/OqMpuwOkbgZ/vR880wz6lq1rUwdBOIAIblhuwXHLTT7A5y6Vck69xuqkeyjI67SUdHhxXeCDbjUkOkCqKHY9dU3LNHIH0xYsWGTB7z+FpCn8f7URfMviLQ2QX30Uda/h0KQ91/raGjYE5SHU3E/P/VWtj
> juju-client-key
> 
>  type:openstack]
> 
> 2016-10-12 20:19:00 INFO juju.provider.openstack provider.go:75
> opening model "controller"
> 
> 2016-10-12 20:19:00 INFO cmd cmd.go:129 Creating Juju controller
> "openstack-controller" on openstack-mitaka/RegionOne
> 
> 2016-10-12 20:19:00 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "image-metadata-url"
> 
> 2016-10-12 20:19:00 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "default cloud images"
> 
> 2016-10-12 20:19:00 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "default ubuntu cloud images"
> 
> 2016-10-12 20:19:01 INFO juju.cmd.juju.commands bootstrap.go:641
> combined bootstrap constraints:
> 
> 2016-10-12 20:19:01 INFO cmd cmd.go:129 Bootstrapping model "controller"
> 
> 2016-10-12 20:19:01 DEBUG juju.environs.bootstrap bootstrap.go:214
> model "controller" supports service/machine networks: false
> 
> 2016-10-12 20:19:01 DEBUG juju.environs.bootstrap bootstrap.go:216
> network management by juju enabled: true
> 
> 2016-10-12 20:19:01 INFO juju.environs.bootstrap tools.go:95 looking
> for bootstrap tools: version=2.0-beta15
> 
> 2016-10-12 20:19:01 INFO juju.environs.tools tools.go:106 finding
> tools in stream "devel"
> 
> 2016-10-12 20:19:01 INFO juju.environs.tools tools.go:108 reading
> tools with major.minor version 2.0
> 
> 2016-10-12 20:19:01 INFO juju.environs.tools tools.go:116 filtering
> tools by version: 2.0-beta15
> 
> 2016-10-12 20:19:01 DEBUG juju.environs.tools urls.go:109 trying
> datasource "keystone catalog"
> 
> 2016-10-12 20:19:02 DEBUG juju.environs.simplestreams
> simplestreams.go:680 using default candidate for content id
> "com.ubuntu.juju:devel:tools" are {20161007 mirrors:1.0
> content-download streams/v1/cpc-mirrors.sjson []}
> 
> 2016-10-12 20:19:03 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "image-metadata-url"
> 
> 2016-10-12 20:19:03 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "default cloud images"
> 
> 2016-10-12 20:19:03 DEBUG juju.environs imagemetadata.go:112 obtained
> image datasource "default ubuntu cloud images"
> 
> 2016-10-12 20:19:03 DEBUG juju.environs.bootstrap bootstrap.go:489
> constraints for image metadata lookup &{{{RegionOne
> http://10.2.1.111:35357/v3} [centos7 precise trusty win10 win2012
> win2012hv win2012hvr2 win2012r2 win2016 win2016nano win7 win8 win81
> xenial yakkety] [amd64 arm64 ppc64el s390x] released}}
> 
> 2016-10-12 20:19:03 DEBUG juju.environs.bootstrap bootstrap.go:501
> found 1 image metadata in image-metadata-url
> 
> 2016-10-12 20:19:04 DEBUG juju.environs.simplestreams
> simplestreams.go:458 index has no matching records
> 
> 2016-10-12 20:19:04 DEBUG juju.environs.bootstrap bootstrap.go:501
> found 0 image metadata in default cloud images
> 
> 2016-10-12 20:19:05 DEBUG juju.environs.simplestreams
> simplestreams.go:454 skipping index
> "http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson;
> because of missing information: index file has no data for cloud
> {RegionOne http://10.2.1.111:35357/v3} not found
> 
> 2016-10-12 20:19:05 DEBUG juju.environs.bootstrap bootstrap.go:497
> ignoring image metadata in default ubuntu cloud images: index file has
> no data for cloud {RegionOne http://10.2.1.111:35357/v3} not found
> 
> 2016-10-12 20:19:05 DEBUG juju.environs.bootstrap bootstrap.go:505
> found 1 image 

Re: upcoming change in Juju 2.0 to bootstrap arguments

[Jason Hobbs]

Thanks for the heads up Ian - we will adjust our scripts to accomodate.

Jason

On Thu, Oct 13, 2016 at 12:36 AM, Ian Booth  wrote:

> See https://bugs.launchpad.net/juju/+bug/1632919
>
> The order of the cloud/region and controller name arguments will be
> swapped.
>
> Old:
>
> $ juju bootstrap mycontroller aws/us-east-1
>
> New:
>
> $ juju bootstrap aws/us-east-1 mycontroller
> or now
> $ juju bootstrap aws/us-east-1
>
> Notice how controller name is optional. It will default to cloud-region.
> eg
>
> $ juju bootstrap aws
> Creating Juju controller "aws-us-east-1" on aws/us-east-1
> ...
>
> The only fallout I expect will be for folks like OIL who use scripts will
> have
> to tweak their scripts to swap the arguments. The bootstrap API itself is
> unaffected so Python client and other API users will see no difference.
> It's
> just a CLI change.
>
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Fwd: Big memory usage improvements

[Christian Muirhead]

Oops, meant to reply-all.

-- Forwarded message -
From: Christian Muirhead 
Date: Thu, 13 Oct 2016, 09:26
Subject: Re: Big memory usage improvements
To: Katherine Cox-Buday 




On Wed, 12 Oct 2016, 22:36 Katherine Cox-Buday, <
katherine.cox-bu...@canonical.com> wrote:

Awesome, good work, Christian!


:)
Thanks for your help with the StatePool!


Not to detract from this fantastic news, but it's still worrisome that an
idle Juju seems to have a memory which is growing linearly (before picture
looked like the beginning of an exponential curve?). Do we feel this is
memory which will at some point be GCed?


No, I think there's still a leak there. The other ones I fixed were
goroutine leaks which were a bit easier to track down. There aren't any
goroutines escaping now so I'll need to switch back to looking at heap
dumps to find more.

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

Re: Big memory usage improvements

[Christian Muirhead]

On Wed, 12 Oct 2016, 21:39 Menno Smits,  wrote:

> Interestingly the MongoDB memory usage profile is quite different as well.
> I'm not sure if this is due to Christian's improvements or something else.
>

Thanks Menno! One of the fixes was a state.State instance being leaked when
the model was destroyed, and that held a Mongo session open which would've
held memory in the mongod process as well.

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

Re: Big memory usage improvements

[Danilo Šegan]

Indeed, this is amazing stuff: good job, it's great to see so
significant improvements!
I can't help but wonder about the bootstrap time: it goes up by 75s
(from 114s to 189s, or ~66% increase)? Do you perhaps have multiple
runs comparing just the bootstrap times to ensure it's related more to
the environment state (hardware, network, load) than changes in the
code? Is there any explanation for the difference in the number of
deployments done and models created in roughly the same time (46/946 vs
52/1092, 13/15% decrease)?
It might still be a trade-off worth accepting, and even if it'd be even
better with no trade-offs, it's fine as long as we know about it and
make sure that we evaluate the value/cost proposition for each case.
Cheers,
Danilo
У чет, 13. 10 2016. у 09:39 +1300, Menno Smits пише:
> Christian (babbageclunk) has been busy fixing various memory leaks in
> the Juju controllers and has made some significant improvements.
> Chris (veebers) has been tracking resource usage for a long running
> test which adds and removes a bunch of models and he noticed the
> difference.
> 
> Take a look at the memory usage graphs here:
> 
> Before: http://people.canonical.com/~leecj2/perfscalemem/
> After: http://people.canonical.com/~leecj2/perfscalemem2/
> 
> Interestingly the MongoDB memory usage profile is quite different as
> well. I'm not sure if this is due to Christian's improvements or
> something else.
> 
> There's possibly still some more small leaks somewhere but this is
> fantastic regardless. Thanks to Christian for tackling this and Chris
> for tracking the numbers.
> 
> - Menno
> 
> 
> -- 
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/l
> istinfo/juju-dev-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev