[07:43] <rts-sander> I've build juju using the github project and ran "./juju switch" on it
[07:43] <rts-sander> now my existing juju environment lost all its configuration
[07:43] <rts-sander> is this recoverable?
[08:06] <kjackal> Hello Juju World!
[11:18] <KpuCko> hello guys, im trying to play with juju, im absolute beginer with this, i have installed juju and juju-quickstrt, and now im running juju-quickstart with -i (interactive) mode trying to setup lxc environment (local) but my juju-quickstart fails with juju-quickstart: error: error: flag provided but not defined: -e
[11:18] <KpuCko> im using juju 2.0
[11:32] <evilnick_> KpuCko, quickstart doesn't work with Juju 2.0. You should follow the documentation here: https://jujucharms.com/docs/stable/getting-started
[11:32] <KpuCko> thanks evilnick_
[13:01] <xnox> are there examples of people using layers/reactive and interface:juju-info ?
[13:52] <ram_____> marcoceppi:  Hi. I have a question. While selecting components from landscape UI for autopilot openstack deployment , can we give set external configuration parameters for a particular component?
[13:53] <ram_____> marcoceppi: any idea?
[13:55] <kjackal> cory_fu: are you there?
[13:56] <cory_fu> Yep
[13:56] <cory_fu> kjackal: What's up?
[13:56] <kjackal> Hey I wanted to ask about boto on cwr
[13:57] <kjackal> should it really be optional?
[13:57] <kjackal> cory_fu: ^
[13:58] <cory_fu> Well, it's optional to use it, so it seems unnecessary to require it, but making it a required dep probably isn't that big of a deal and would save potential headache
[13:59] <kjackal> yeap agreed!
[14:40] <BjornT_> tvansteenburgh: hi. is it possible to have bundletester not destroy and recreate the environment when it runs the tests?
[14:41] <tvansteenburgh> BjornT_: reset: false in tests.yaml
[14:41] <tvansteenburgh> BjornT_: see options here https://github.com/juju-solutions/bundletester#testsyaml
[14:42] <BjornT_> tvansteenburgh: thanks
[14:43] <petevg> bradm: I'm leaving a comment for your on those two outstanding PRs against bip (https://code.launchpad.net/~josvaz/charms/trusty/bip/charmhelpers-cleanup/+merge/301499, https://code.launchpad.net/~josvaz/charms/trusty/bip/client_side_ssl-with_helper-lp1604894/+merge/301802)
[14:43] <petevg> bradm: since you're the maintainer, I think that the correct thing to do is for you to pull all the latest code into your namespace (including merging those PRs), publish the charm, and then get a charmer to promulgate it to the store for you.
[14:44] <petevg> bradm: that should leave you in a place where you can do most of the things that you'd want to do as a maintainer, and it should close the circle for the community member who is trying to get his changes into the charm :-)
[14:48] <cory_fu> cholcombe: Hey, I'm working on the review queue and saw that the gluster charm was +1'd a while back and that you pushed it to the store.  I just wanted to confirm that https://jujucharms.com/u/xfactor973/gluster/xenial/4 is correct and I'll go ahead and finish the promulgation
[14:55] <cholcombe> cory_fu, let me just double check
[14:55] <cholcombe> cory_fu, yeah xenial/4 is the one
[14:55] <cholcombe> cory_fu, or trusty/16
[14:59] <cory_fu> cholcombe: https://jujucharms.com/gluster/
[14:59] <cholcombe> cory_fu, yup
[14:59] <cholcombe> cory_fu, sweet!
[14:59] <cory_fu> Sorry it took so long.  :)
[15:00] <cholcombe> cory_fu, \o/  woo!  thanks :)
[15:52] <ram_____> marcoceppi: Hi. For testing purpose I developed a simple charm using the shell script  to modify the cinder configuration file for the post-deployment of OpenStack. cinder configuration modified. But I am saw some error in charm log. pasted information of my issuehttp://paste.openstack.org/show/563408/
[16:02] <ram_____> marcoceppi: I tried to deploy 'cinder-xtremio " charm in our local Juju openstack environment like $juju deploy cinder-xtremio. I was facing errors. Error log : http://paste.openstack.org/show/563416/
[16:03] <ram_____> Can you please provide me  some solution for this. Thanks.
[16:51] <cmars> hey ram_____ I don't know anything about openstack, but is your install executable and does it have a shebang at the top?
[16:52] <cmars> ^install hook, i mean
[17:11] <ram_____> cmars: Hi. shebang means. sry I did get it. What it mean?
[17:12] <cmars> ram_____, the `#!/bin/bash -e`, i mean
[17:12] <cmars> ram_____, the error in your paste, looked like the kind of thing you'd see if you tried to run a script without it
[17:13] <cmars> (that's usually how i start my scripts... you might prefer `#!/bin/sh` or something
[17:15] <ram_____> cmars: Ok thank you. I will try with that.
[17:54] <ram_____> [22:52] <ram____> Hi. I tried to deploy "cinder-xtremio " charm in our local Juju openstack environment like $juju deploy cinder-xtremio. I was facing errors. pasted error log : http://paste.openstack.org/show/563432/. Please anyone provide me some solution for this.
[18:00] <Guest79992> How to get a FQDN for a juju container?
[18:01] <Guest79992> How to get a FQDN for a juju container?
[18:12] <bjf> how do i set the security group for my AWS instances to use? url pointer to the appropriate juju 2.0 doc appreciated
[18:22] <ram_____>  Hi. I want to develop a cinder-storagedriver  charm. And i want to integrate it with Ubuntu-autopilot . SO can I give input parameters like san IP, san user and san password from landscape autopilot UI. Otherwise everything we have to hardcode into the charm. And different users for the same storage array have different credentials.
[18:23] <ram_____> any idea?
[19:07] <kwmonroe> bjf: not sure if this helps, but i let juju create its own security groups.. i did run into an account limit where i had to go remove old security groups that weren't removed from previous deployments... but i haven't had to do that with recent juju-2 betas.
[19:12] <kwmonroe> ram_____: sounds like you could make the san connection parameters as charm config options.. different users that deployed your charm would "juju set" appropriate credentials.
[19:18] <bjf> kwmonroe, thanks
[23:23] <bradm> petevg: sounds good, will try and look at doing that soon