[09:10] <Muntaner> hello to everyone...I have a problem with a bootstrap, is this the right channel?
[09:23] <Muntaner> marcoceppi, ping
[09:27] <Muntaner> I'm trying to bootstrap juju with two maas machines, that actually are two VM into VMWare...  I installed the Maas controller on another machine, and the bootstrap seems to go well, it installs the OS cloud into the first of the two machines but when it comes to MongoDB replica stuff, it fails. I have under my hands the logs that I see in this situation
[11:12] <wesleymason> Unable to install my charm after rebuilding it this morning: https://github.com/juju-solutions/reactive-base-layer/issues/27
[12:10] <beisner> jamespage - can you review/land these liberty, xenial amulet test enablements?:  tia
[12:10] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/glance/next-amulet-mitaka-1601/+merge/282496
[12:10] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/keystone/next-amulet-mitaka-1601/+merge/282493
[12:10] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/rabbitmq-server/next-amulet-mitaka-1601/+merge/282497
[12:12] <beisner> jamespage, +this one:
[12:12] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/neutron-api/next-mitaka-amulet-1601/+merge/282835
[12:19] <beisner> uno mas, jamespage.  it's raining test extensions...
[12:19] <beisner> https://code.launchpad.net/~1chb1n/charms/trusty/cinder/next-amulet-mitaka-1601/+merge/282519
[13:30] <wesleymason> marcoceppi: is the base layer not pinning the wheels it vendors?
[13:30] <wesleymason> specifically pip in this case
[13:31] <marcoceppi> wesleymason: I tried to pin it in the base layer
[13:31] <marcoceppi> wesleymason: but it's still getting pulled in by charms.reactive which does not have it pinned
[13:31] <marcoceppi> wesleymason: I'm going to try to patch there
[13:31] <marcoceppi> but I'd really like cory_fu_ to weigh in on the MP there
[13:32]  * wesleymason nods
[13:32] <wesleymason> marcoceppi: for the record there's 2 of us sat here with different charm layers stuck on it 😃
[13:32] <marcoceppi> wesleymason: there's more than two, that's for sure
[13:32] <marcoceppi> wesleymason: everyone is blocked which makes it a priority patch
[13:35] <wesleymason> 👍
[13:38] <marcoceppi> wesleymason: would you be willing to try a patched layer?
[13:38] <wesleymason> marcoceppi: sure
[13:43] <marcoceppi> wesleymason: okay, so this actually needs changes in charm-tools
[13:46]  * wesleymason gets popcorn
[14:21] <marcoceppi> wesleymason cmars kjackal I've updated https://github.com/juju-solutions/reactive-base-layer/pull/26 when tested, only pip-7.1.0 was included in the wheelhouse which shouldn't present these problems
[14:23] <wesleymason> 🙌
[14:23] <marcoceppi> once I have cory_fu_ or bcsaller feedback I'll push a 1.11.1 release almost immediately after
[14:25] <kjackal> thank you marcoceppi
[14:37] <icey> gah bundletester is failing because of uncommitted changes in charms that it is checking out!
[17:46] <geetha> @mbruzek: Hi, I have got comment for WebSphere Base product where its mentioned that we should add configuration options for profile options like profile name, path, and admin username and password. But once user installs Websphere product and if he changes any of those values using juju set, It will not create profile again with new values. So what is the benifit of giving config options for these profile options?
[18:20] <icey> I'm seeing a strange issue in bundletester; I'm using `bundletester -e amazon -l DEBUG -vF` to run tests and it looks like bundletester is pulling down other charms from launchpad and then failing because the machine I'm running bundletester on has no ssh key to access LP?
[18:26] <icey> all tests give me this error: bzrlib.errors.ConnectionReset: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[19:45] <D4RKS1D3> Hi
[19:45] <D4RKS1D3> Someone has problemas installing odl-controller within juju?
[19:46] <D4RKS1D3> problems*
[20:17] <lazypower> cmars - the issue with pyyaml
[20:17] <lazypower> did you find a work around? i just ran into it
[20:18] <lazypower> nvm i see in the scrollback this is being triaged already - https://github.com/juju-solutions/reactive-base-layer/issues/27
[21:12] <bdx> charmers: Has storage support for openstack provider been considered? .. or possibly already exist?
[21:13] <bdx>  core^
[21:24] <narindergupta> D4RKS1D3: no one has issues with odl-controller make sure you provide the url and profile correctly based on which ODL r u targetinh
[21:43] <arosales> tych0: I am not sure what you'll need to test exactly but I think I have a way for you to bootstrap xenial on AWS, may also work on GCE
[21:43] <arosales> and to deploy Xenial workloads
[21:44] <tych0> arosales: oh, sweet
[21:44] <arosales> tych0: how was the ride?
[21:44] <tych0> arosales: good. unusually fast, actually, must have slept well last night :)
[21:45] <arosales> bdx: re storage provider, definitely something considered and may already be on the roadmap
[21:45] <arosales> bdx: may need to ping in #juju-dev on free node to get a more exact answer though
[21:45] <arosales> tych0: and solid weather :-)
[21:46] <tych0> arosales: yeah, for sure
[21:46] <arosales> well and the whoosh of carbon wheels, right
[21:46] <tych0> arosales: ha yeah. you have to be better than me to actually get an advantage from them. but they sure sound cool :)
[21:46] <arosales> I am sure you take advantage of them
[21:47] <arosales> tych0: so you need xenial on a cloud?
[21:47] <tych0> arosales: yeah, if you have a way. that would save me from having to ssh to the node and add a lxd ppa
[21:47] <arosales> I currently have a bootstrap and deploying the ubuntu charm on AWS onto of xenial with 1.26 alpha juju
[21:48] <tych0> sweet
[21:48] <tych0> what's the magic sauce?
[21:48] <arosales> tych0: I can add you ssh keys if you would like, but the sauce was as follows
[21:48] <arosales> for AWS, I have to check GCE
[21:48] <arosales> installed the -devel version of juju (for 1.26)
[21:49] <arosales> confirmed the daily stream has xenial
[21:49] <arosales> https://cloud-images.ubuntu.com/daily/streams/v1/com.ubuntu.cloud:daily:aws.json
[21:50] <arosales> in my ~/.juju/environment.yaml I updated image-stream: "daily"
[21:50] <arosales> under the AWS stanza
[21:50] <arosales> the then juju bootstrap --upload-tools
[21:50] <arosales> given aws is your default environment
[21:50] <arosales> oh
[21:50] <tych0> ah
[21:51] <tych0> maybe i can't set the image-stream for GCE?
[21:51] <tych0> i don't see it in the code :\
[21:51] <arosales> and I am on a Xenial Ubuntu desktop from which I am running the client
[21:51] <arosales> I think juju looks at the juju version and desktop client to build the appropriate tools, because I couldn't get it to work from my trusty machine
[21:52] <tych0> yeah
[21:52] <tych0> i think you're right
[21:52] <tych0> cool, thanks
[21:52] <tych0> do we happen to have any company AWS accounts? or should i just sign up for my own?
[21:52] <arosales> also for the aws stanza I also set  `default-series: xenial`
[21:53]  * arosales checking GCE for daily stream
[22:02] <arosales> ya looks like no daily stream for GCE
[22:03] <bdx> arosales: great, thanks
[22:05] <arosales> also if others are following the xenial conversation I also set `default-series: xenial` for my amazon/aws stanza and I was able to bootstrap and deploy xenial instances
[22:05] <arosales> I did have to deploy local charms with the directory structure ./xenial/<charm-name>  but seems to be working on AWS
[22:05] <arosales> bdx: ping if you don't get response and I can also digg on that
[22:06] <lazypower> that makes sense that you'd have to do local only
[22:06] <lazypower> i dont think any of the charm store has been ported over to xenial yet
[22:07] <arosales> yup, that was my take lazypower
[22:07] <bdx> arosales: sweet, will do!
[22:08] <arosales> I didn't say, but `default-series: xenial` in the environment.yaml file, in can folks were wondering
[22:27] <lazypower> hey tych0 whats your TZ again?
[22:27] <lazypower> i'm doing some slides for fosdem, and it would be really helpful if i could poke you for some specifics of how LXD is doing things
[22:27] <tych0> lazypower: nominally mountain time
[22:28] <tych0> lazypower: but really any time as long as i'm at the keyboard :)
[22:28] <lazypower> :) Is your schedule tomorrow crazy? i only  need a few irc pokes here and there
[22:28] <tych0> lazypower: not at all, any time should work
[22:28] <lazypower> awesome. thanks tych0, as always you da man :)
[22:28] <tych0> i usually start around 7
[22:28] <tych0> lazypower: well, let's not go that far :)
[22:32] <lazypower> one word
[22:32] <lazypower> "doom"
[22:35] <tych0> :)