Re: My beginners experience of juju charm development

I'm a researcher at Lenovo US. I myself started researching Juju and charms about 4 months ago and can relate to many of Erik's comments. To add to this discussion, here are my experience and thoughts: 1. Design document. Reading official document and tutorials are good but not satisfying to

Re: My beginners experience of juju charm development

Thank you so much for the detailed view into your journey and sharing this feedback Erik. Things like this will go far to help us improve our community resources. I offer no excuses, only empathy that I understand where you're coming from. As a 3 year veteran of the Juju ecosystem, I too felt

My beginners experience of juju charm development

Hello! I've been trying to become friends with juju for the last month or so and was asked in the #juju IRC channel on Freenode to share my experiences from a "beginner perspective on juju charming". Generally, I believe JuJu is a great concept. I makes alot of sense and the architecture and

Re: [ANN] Kubernetes 1.6.3 snaps available in the edge channel for testing

Good work Chuck! We'll take them for a spin over at DARPA. Tom On Thu, May 11, 2017 at 4:34 PM, Charles Butler < charles.but...@canonical.com> wrote: > We’ve just published a new revision of the Kubernetes snaps in edge. > > This includes the latest upstream release of Kubernetes for 1.6. > >

[ANN] Kubernetes 1.6.3 snaps available in the edge channel for testing

We’ve just published a new revision of the Kubernetes snaps in edge. This includes the latest upstream release of Kubernetes for 1.6. For those looking to upgrade from 1.6.2 or an earlier version of the snaps this can be performed with the charms: juju config kubernetes-master

Re: Normalizing output dir for charm build

+1! While you're at it; I think it could be wise to namespace everything with Juju. For example $JUJU_LAYER_PATH and ~/.cache/juju/charm-build/deps or something similar. I think it would make everything more coherent and also eliminate the possibility of naming collisions. This could of course

Re: How to build juju for centOS

Andrew, I tried stock Juju on Ubuntu 16.04, but having the same error: ERROR cannot obtain provisioning script ERROR getting instance config: finding tools: no matching tools available (not found) Here are the steps: 1. juju bootstrap lxd lxd-test 2. juju add-machine ssh:username@ip --series

Re: Normalizing output dir for charm build

Adam, I think the name "charms" is up to the user, it's just whatever they have set $JUJU_REPOSITORY to. It just so happens that Merlijn sets his to JUJU_REPOSITORY=~/charms (or similar). Previously, the build charm would end up in {$JUJU_REPOSITORY,$PWD}/{builds,trusty,xenial,...}/$charm_name.

Re: Normalizing output dir for charm build

To confirm: Builds will be replaced by a charms directory, and deps moved to ~/.cache/charm-build. If so, I'm +1 to that. On Thu, May 11, 2017 at 9:28 AM, Cory Johns wrote: > Yes, that's what I'm proposing. > > On Thu, May 11, 2017 at 4:47 AM, Merlijn Sebrechts < >

Re: Normalizing output dir for charm build

Yes, that's what I'm proposing. On Thu, May 11, 2017 at 4:47 AM, Merlijn Sebrechts < merlijn.sebrec...@gmail.com> wrote: > It seems like deps should go under ~/.cache/charm-build/ > > > +1 > > Now, to be clear, the structure you propose is something like the > following? > > > ├── charms

Re: Normalizing output dir for charm build

> > It seems like deps should go under ~/.cache/charm-build/ +1 Now, to be clear, the structure you propose is something like the following? ├── charms# $JUJU_REPOSITORY │ ├── my-charm │ ├── ... ├── interfaces# $INTERFACE_PATH │ ├── ... ├── layers# $LAYER_PATH │