Go 1.8

Folks, We have moved to Go 1.8 as a requirement for building juju core. I'm just about to land a change that brings in a more recent golang.org/x/crypto version, which means we'll be using the standard library's "context", which isn't available in Go 1.6 and earlier. Please update your toolchain.

Re: Proposing Alex Kavanagh for ~charmers

Strong +1 here. On Wed, Apr 26, 2017 at 12:45 PM, Konstantinos Tsakalozos < kos.tsakalo...@canonical.com> wrote: > +1 from me too! > > On Wed, Apr 26, 2017 at 5:07 PM, Tom Barber wrote: > >> Unofficial +1 from the other half of Norwich... >> >> On Wed, Apr 26, 2017 at 3:06

Re: Proposing Alex Kavanagh for ~charmers

+1 from me too! On Wed, Apr 26, 2017 at 5:07 PM, Tom Barber wrote: > Unofficial +1 from the other half of Norwich... > > On Wed, Apr 26, 2017 at 3:06 PM, Pete Vander Giessen < > pete.vandergies...@canonical.com> wrote: > >> +1 from me :-) >> >> On Wed, Apr 26, 2017 at 9:43

Re: How to add openstack cloud to juju 2.1.2-xenial

Hi, TL;DR: . novarc openstack network list juju bootstrap --config network= --config external-network= --config use-floating-ip=true No need for simplestreams stuff: Juju deploy this: https://jujucharms.com/glance-simplestreams-sync/ Then juju add-relation keystone

Re: How to add openstack cloud to juju 2.1.2-xenial

Still facing issues, but have gotten past the simplestreams issue, I think. I am running "juju bootstrap acauits --metadata-source /home/bidwell/simplestreams --debug" Among everything else, it returns: caused by: request (http://10.20.9.142:8774/v2.1/e69c1091bf744509a8853e a8e336ae26/servers)

Re: Gitlab & SSL

Yeah thats the place, hadn't pushed it. Still got some more work to clean up the config setting a bit, and me and Chuck were mulling over exposing the CI and Docker Repo which I currently don't do. One thing we'd like is Gitlab <-> EasyRSA connectivity and then to K8S so you can setup a private

Re: Proposing Alex Kavanagh for ~charmers

+1 from me :-) On Wed, Apr 26, 2017 at 9:43 AM Charles Butler wrote: > I for one, cast my +1 vote > > It's been great working with tinwood regarding charms, layers, and > reactive 2.0. His reviews have been on point and his helpful hand with the > community has

Re: Proposing Alex Kavanagh for ~charmers

I for one, cast my +1 vote It's been great working with tinwood regarding charms, layers, and reactive 2.0. His reviews have been on point and his helpful hand with the community has been a pleasure to witness. All the best, Charles On Wed, Apr 26, 2017 at 4:52 AM James Page

Re: [ANN] Bigtop-1.2 charms/bundles have been released

On 26/04/17 03:37, Merlijn Sebrechts wrote: > Awesome! > > Some visibility improvements. > > * If you search for Hadoop in the > Charm Store, the first results you get are the old non-bigtop > charms. Can we do something about this? This is the same for

Gitlab & SSL

Hey folks After some prodding from Rick I updated my Gitlab charm and ensured it worked with Tengu's fantastic new SSL termination proxy charm to provide SSL encrypted Gitlab OOTB. The new charm now runs on Xenial and Trusty and provides Gitlab via the omnibus repo. I have some more stuff down

Re: Proposing Alex Kavanagh for ~charmers

Hi, I definitely give my (unofficial) +1 here. Alex's work on the reactive framework is very important as we need to make progress with it and improve our tooling. It would be great to have Alex on the core team as he knows a great deal about juju charms - if there are any questions about the

Proposing Alex Kavanagh for ~charmers

Hi Charmers I'd like to propose Alex (tinwood) for membership of charmers; he's worked extensively across the OpenStack charms, providing valuable reviews to the rest of the team, has been reviewing charm-helpers updates and has been instrumental in the OpenStack charms use of reactive and layers

Re: [ANN] Bigtop-1.2 charms/bundles have been released

Awesome! Some visibility improvements. - If you search for Hadoop in the Charm Store, the first results you get are the old non-bigtop charms. Can we do something about this? This is the same for Spark, Pig, etc.. - The ancient "hadoop"