Re: kvm on lxd guidance?

[Reed O'Brien]

I'm sorted. Thanks to those that replied.

On Thu, Dec 15, 2016, 18:33 Reed O'Brien  wrote:

> Is there anyone around tomorrow North American time or sometime (any
> timezone) next week who can guide me through getting kvm running on lxd
> locally on my system?
>
> To be clear, that would be juju bootstrapped on lxd deploying kvm onto an
> lxd container:)
>
> I know Andy said it isn't too difficult, but I'm not sure if he's around.
>
> Cheers,
> Reed
>
>
> --
> Reed O'Brien
> ✉ reed.obr...@canonical.com
> ✆ 415-562-6797
>
> --

Reed O'Brien
reed.obr...@canonical.com
202-656-5501
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Canonical Distribution of Kubernetes 1.5.1 is here

[Adam Stokes]

At least on the mobile site the install instructions are not properly
formatted (under getting started)

On Fri, Dec 16, 2016, 6:14 PM Jorge O. Castro  wrote:

> Hello everyone,
>
> I'm happy to announce that 1.5.1 is here, all charms have been pushed and
> it's ready to go. Please refer to this blog post for the lengthy changelog,
> enjoy!
>
>
> http://insights.ubuntu.com/2016/12/16/announcing-canonical-kubernetes-1-5-1/
>
> --
> Jorge Castro
> Canonical Ltd.
> http://ubuntu.com/cloud/kubernetes  - Pure
> upstream Kubernetes
> --
> 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

Canonical Distribution of Kubernetes 1.5.1 is here

[Jorge O. Castro]

Hello everyone,

I'm happy to announce that 1.5.1 is here, all charms have been pushed and
it's ready to go. Please refer to this blog post for the lengthy changelog,
enjoy!

http://insights.ubuntu.com/2016/12/16/announcing-canonical-kubernetes-1-5-1/

-- 
Jorge Castro
Canonical Ltd.
http://ubuntu.com/cloud/kubernetes  - Pure upstream
Kubernetes
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: A (Very) Minimal Charm

[Stuart Bishop]

On 16 December 2016 at 22:33, Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:

> Tim Penhey  writes:
>
> > Make sure you also run on LXD with a decent delay to the APT archive.
>
> Open question: is there any reason we shouldn't expect charm authors to
> take a hard-right towards charms with snaps embedded as resources? I know
> one of our long-standing conceptual problems is consistency across units
> which snaps solves nicely.
>

https://github.com/stub42/layer-snap is how I'm expecting things to go.
There is already one charm in the ~charmers review queue using it and I'm
aware of several more in various stages of development.

More work is needed though. In particular, Juju storage is inaccessible to
snaps, because there is no way to reach it from inside the containment.

(But none of this is a reason to not optimize Juju unit provisioning times,
since we will still need an environment setup capable of running the charms
so they can install the snaps for some time yet).

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

Re: A (Very) Minimal Charm

[Stuart Bishop]

On 16 December 2016 at 22:33, Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:

> Tim Penhey  writes:
>
> > Make sure you also run on LXD with a decent delay to the APT archive.
>
> Open question: is there any reason we shouldn't expect charm authors to
> take a hard-right towards charms with snaps embedded as resources? I know
> one of our long-standing conceptual problems is consistency across units
> which snaps solves nicely.
>

https://github.com/stub42/layer-snap is how I'm expecting things to go.
There is already one charm in the ~charmers review queue using it and I'm
aware of several more in various stages of development.

More work is needed though. In particular, Juju storage is inaccessible to
snaps, because there is no way to reach it from inside the containment.

(But none of this is a reason to not optimize Juju unit provisioning times,
since we will still need an environment setup capable of running the charms
so they can install the snaps for some time yet).

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

Re: A (Very) Minimal Charm

[David Britton]

On Fri, Dec 16, 2016 at 09:33:18AM -0600, Katherine Cox-Buday wrote:
> Tim Penhey  writes:
> 
> > Make sure you also run on LXD with a decent delay to the APT
> > archive.
> 
> Open question: is there any reason we shouldn't expect charm authors
> to take a hard-right towards charms with snaps embedded as resources?
> I know one of our long-standing conceptual problems is consistency
> across units which snaps solves nicely.

For new projects we are working this way.  We have not used resources
yet, but instead are using "fat" charms and sideloading the snap.

But, resources are the next logical progression.

-- 
David Britton 

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

Re: A (Very) Minimal Charm

[David Britton]

On Fri, Dec 16, 2016 at 09:33:18AM -0600, Katherine Cox-Buday wrote:
> Tim Penhey  writes:
> 
> > Make sure you also run on LXD with a decent delay to the APT
> > archive.
> 
> Open question: is there any reason we shouldn't expect charm authors
> to take a hard-right towards charms with snaps embedded as resources?
> I know one of our long-standing conceptual problems is consistency
> across units which snaps solves nicely.

For new projects we are working this way.  We have not used resources
yet, but instead are using "fat" charms and sideloading the snap.

But, resources are the next logical progression.

-- 
David Britton 

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

[Review Queue]: ghost, znc, IBM-*

[Kevin Monroe]

Hi Juju,

Cory, Kostas, Pete, and I waded through https://review.jujucharms.com/ this
week.  Here's what we found:


   -

   ghost
   -

  https://review.jujucharms.com/reviews/62
  -

  Ghost is a simple, powerful publishing platform.
  -

  The charm is in a good shape (24th revision).
  -

  There are a few more points that require the author’s attention,
  mainly in the tests.
  -

  We will have to wait the authors input for now.
  -

   znc
   -

  https://review.jujucharms.com/reviews/24
  -

  Refactored to use Ruby instead of Perl as the charm language, but has
  a test failure
  -

   Ibm-platform-lsf-server
   -

  https://review.jujucharms.com/reviews/18
  -

  Left some comments after code review, requesting improvements to
  error handling (currently, the charm can behave unpredictably,
and does not
  check for several error conditions)
  -

   Ibm-im
   -

  https://review.jujucharms.com/reviews/47?revision=106
  -

  We noticed an unhandled exception when deploying without a proper
  resource and committed a minor fix.  With this and previous +2,
this looks
  good.
  -

  Promulgated: https://jujucharms.com/ibm-im/
  -

   Ibm-was-base
   -

  https://review.jujucharms.com/reviews/74?revision=164
  -

  Our previous review was accidentally against the xenial version
  (under development).  We opened this one to review updates to the stable
  trusty revision.
  -

  We added a repo key and cleaned up minor readme/test issues.
  -

  Rebuilt to pull in recent ibm-im changes.  Deployed / functioned as
  documented in the readme.  +1.
  -

  Promulgated: https://jujucharms.com/ibm-was-base/trusty


Find us on Freenode in #juju with any questions/concerns.

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

Re: A (Very) Minimal Charm

[Katherine Cox-Buday]

Tim Penhey  writes:

> Make sure you also run on LXD with a decent delay to the APT archive.

Open question: is there any reason we shouldn't expect charm authors to take a 
hard-right towards charms with snaps embedded as resources? I know one of our 
long-standing conceptual problems is consistency across units which snaps 
solves nicely.

-- 
Katherine

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

Re: A (Very) Minimal Charm

[Katherine Cox-Buday]

Tim Penhey  writes:

> Make sure you also run on LXD with a decent delay to the APT archive.

Open question: is there any reason we shouldn't expect charm authors to take a 
hard-right towards charms with snaps embedded as resources? I know one of our 
long-standing conceptual problems is consistency across units which snaps 
solves nicely.

-- 
Katherine

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

Re: AZs and placement

[Martin Packman]

On 16/12/2016, Brent Clements  wrote:
> This is great info.
>
> I apologize for my ignorance but what would that, as placement for each
> unit, look like in a bundle?

For each application, it can look something like this:

  an-application:
charm: ./a-charm
num_units: 3
to:
  - zone=zone-a
  - zone=zone-a
  - zone=zone-a

Martin

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

A new development release of Juju, 2.1-beta3, is here!

[Curtis Hovey-Canonical]

A new development release of Juju, 2.1-beta3, is here!


## What's new?

* Deployments to LXD containers on Xenial use the more performant
  directory backend https://bugs.launchpad.net/juju/+bug/1648513
* Constraints placed on KVM containers in bundles are honoured
* Juju SSH improvements for the Windows platform
* Memory usage improvements
* Other Bug fixes https://launchpad.net/juju/+milestone/2.1-beta3


## Known Issues:

* Model Migrations does not migrate back to the original controller


## How do I get it?

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

sudo add-apt-repository ppa:juju/devel
sudo apt-get update; sudo apt-get 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.1-beta3


## 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.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

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

A new development release of Juju, 2.1-beta3, is here!

[Curtis Hovey-Canonical]

A new development release of Juju, 2.1-beta3, is here!


## What's new?

* Deployments to LXD containers on Xenial use the more performant
  directory backend https://bugs.launchpad.net/juju/+bug/1648513
* Constraints placed on KVM containers in bundles are honoured
* Juju SSH improvements for the Windows platform
* Memory usage improvements
* Other Bug fixes https://launchpad.net/juju/+milestone/2.1-beta3


## Known Issues:

* Model Migrations does not migrate back to the original controller


## How do I get it?

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

sudo add-apt-repository ppa:juju/devel
sudo apt-get update; sudo apt-get 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.1-beta3


## 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.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

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

AZs and placement

[Martin Packman]

There have been a couple of reports of Juju struggling with
availability zones recently. This isn't new code, it was introduced in
1.20, but with 2.0 it appears that we're not surfacing errors from
improper zone selection[1], which is a particular issue when we also
seem to not be selecting a valid zone[2]. This is seen with both
Openstack (datacenterd) and vSphere.

We don't have a global option to say only use a particular AZ, so the
only way at present to do this right is specify a zone placement for
every unit. I did find how to do that spelled out in the
documentation, though it's not completely intuitive:



$ juju deploy an-application -n 3 --to zone=$ZONE,zone=$ZONE,zone=$ZONE

Note that a placement directive is needed per unit.

Also, of note, we have only just fixed a bug[3] that prevented
combining constraints and placement directives in bundles. So,
currently care is required if creating a bundle that needs to specify
a zone for everything.

Martin


[1] "Openstack provider error not surfaced on bootstrap"

[2] "inconsistent results when fetching availability zones while
bootstrapping with vsphere as provider"

[3] "Juju ignores constraints set in the bundle and deploys KVMs with
default values"


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