[00:50] <Brochacho> pragsmike: Thanks! Figured it was an image name issue, do you know if there's an open issue for this? Every search I made turned up nothing
[00:51] <pragsmike> I haven't looked into it further, it could be the repository doesn't match what the tool assumes
[00:53] <pragsmike> I'm still exploring the list of bugs, but the lxd support seems spotty.  I can't get containers on different machines to talk to each other, for instance.
[00:54] <pragsmike> as long as I deploy all containers to one machine, it's ok :/
[00:58] <Brochacho> pragsmike: Looks like it's reported: https://bugs.launchpad.net/juju/+bug/1618948
[00:58] <mup> Bug #1618948: Can't bootstrap localhost cloud <juju:Incomplete> <https://launchpad.net/bugs/1618948>
[01:12] <pragsmike> hmm, that doesn't seem to be related, you sure that # is correct?
[05:58] <kjackal> Hello Juju World!
[10:49] <stub`> bcsaller: Do you know what is going on here? http://pastebin.ubuntu.com/23123739/ It seems I'm missing build tools on a bare metal trusty deploy. Testing locally works no probs.
[10:54] <stub`> bcsaller: oooh.... python3-pip only recommends build-essential (and python3-setuptools, and python3-wheel), so some deploys won't get those
[12:02] <rock__> Hi. I want to deploy openstack using [MAAS+openstack-base-bundle]. Can anyone please give me the detailed hardware requirements. and refrence links for doing that.
[13:35] <shruthima> hi kwmonroe , how to push ibm-im charm for xenial series in to charm store ?(charm push . cs:~ibmcharmers/xenial/ibm-im)
[13:49] <shruthima> hello team, how to build a deployable charm under xenial directory?
[13:52] <stub`> shruthima: metadata.yaml defines the supported series, so if you have "series: [xenial]" or "series: [xenial, trusty]" you should be good. The default series is the first one listed there.
[13:53] <shruthima> ok if we give xenial first the deployable charm will be build under xenial directory is it ?
[13:54] <stub`> If you list a single series, the charm will be built in a directory with the series name. If you list multiple series, it will be build under a 'builds' directory.
[13:55] <stub`> Since Juju 1.25, it doesn't matter where it gets built to as 'juju deploy ~/tmp/builds/mycharm' works. You don't need a $JUJU_REPOSITORY setup with magic subdirectories.
[13:55] <shruthima> oh k thanku
[13:56] <shruthima> tp push charm for xenial series in to charm store do we need to use charm push . cs:~ibmcharmers/xenial/ibm-im?
[13:57] <stub`> If you have a multiseries charm, 'charm push . cs:~ibmcharmers/ibm-im' is fine, and all three URLs will have your new charm (ibm-im, trusty/ibm-im and xenial/ibm-im)
[13:58] <stub`> I think pushing to a specific series works too, although I haven't tried it
[13:58] <shruthima> we have IBM-IM charm for trusty in charm store , now i want to push for xenial with same name
[13:58] <stub`> But the charm store is smart enough to look at the series: in metadata.yaml and do the right thing I think.
[13:58] <shruthima> root@z10lnx04:~/charms/xenial/ibm-im# charm push . cs:~ibmcharmers/xenial/ibm-im --resource ibm_im_installer=/root/placeholder.zip --resource ibm_im_fixpack=/root/placeholder.zip ERROR cannot post archive: charm name duplicates multi-series charm name cs:~ibmcharmers/ibm-im-7
[13:58] <stub`> Ok. I'd try pushing to xenial/ibm-im as you sugested.
[13:59] <shruthima> iam getting that error if i try to push with xenial series
[14:00] <stub`> Someone has already pushed a multiseries charm to cs:~ibmcharmers/ibm-im then. I don't know how to override only the xenial charm.
[14:01] <stub`> I think pushing to cs:~ibmcharmers/ibm-im will do the right thing and only change the series listed in your metadata.yaml, but I'm not sure.
[14:03] <shruthima> ohh ok thanku stub`
[14:12] <rock__> Hi. I pused my charm to charm store. I am trying to set BUG URL. Here I am facing issue. pasted issue info : http://paste.openstack.org/show/566078/
[14:15] <stub`> rock__: Did that first command work? I've used the cs: url to set bugs-url (so charm set cs:~siva9296/kaminario-openstack bugs-url="https://bugs.launchpad...")
[14:21] <rock__> stub: Yes. first command I ran. But it ran with out giving any response.
[14:24] <stub`> rock__: When I go to https://jujucharms.com/u/siva9296/kaminario-openstack , I see a submit a bug link pointing to https://bugs.launchpad.net/charms/+source/kaminario-openstack/+filebug , so something worked even if it didn't look like it.
[14:25] <stub`> I don't think 'charm set' says anything on success.
[14:26] <stub`> oh, that bugs url isn't valid
[14:29] <rock__> stub:  So please tell me what I need to do now?  I tried with charm set cs:~siva9296/kaminario-openstack bugs-url="https://bugs.launchpad...". But it was giving This site can’t be reached  bugs.launchpad...’s server DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
[14:31] <stub`> The command you are running is fine, but the bugs-url you are trying to set is incorrect. It should point to your bug tracker, but I don't know where that is.
[14:32] <stub`> Is your charm in a branch on Launchpad? What is the branch URL?
[14:33] <stub`> Or maybe the openstack people here know.
[14:36] <lazyPower> rock__ o/
[14:36] <lazyPower> rock__ - i understand you're having some issues publishing to the juju charm store?
[14:40] <jcastro> welcome!
[14:40] <rock__> lazypower: To populate charm to charm store i used for pushing charm we used https://jujucharms.com/docs/2.0/authors-charm-store. And Used https://github.com/openstack-charmers/release-tools/blob/master/push-and-publish#L138 to set bug URL. Can you please tell me how to set a bug URL?
[14:41] <lazyPower> rock__ - charm set cs:~lazypower/foo bugs-url=https://foobar.co
[14:42] <lazyPower> as an example
[14:46] <rock__> lazypower: I tried as $ charm set cs:~siva9296/kaminario-openstack-2  bugs-url=https://kaminario-openstack.co.  And from UI when i click on "submit a bug" for charm it was giving  bugs.launchpad...’s server DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
[14:47] <lazyPower> rock__ - you've apparently set bugs-url to https://kaminario-openstack.co/
[14:48] <mbruzek> rock__: that url does not resolve for me
[14:48] <mbruzek> rock__: https://kaminario-openstack.co/
[14:48] <lazyPower> rock__ - additionally it may take the display a moment to update. you can use charm show cs:~siva9296/kaminario-openstack to see the information about your charm
[14:49] <mbruzek> rock__: Most of the time the bugs url is a github issue tracker URL, something like this https://github.com/mbruzek/jenkins-jobs/issues
[14:52] <rock__> mbruzek:So my source have to on github (or) launchpad? required any bug tracker? I don't have any bug tracker as of now. How can I do that?
[14:53] <mbruzek> rock__: Github or Launchpad are not required . But the URL should resolve or the bug link will not work
[14:53] <rock__> lazypower: I tried a moment later. Then also it was giving the same issue.
[14:54] <lazyPower> rock__ - well, lets start from step 1. Where do you want to manage bugs for your charm? This typically resides with the charm/layer source
[14:54] <lazyPower> its up to you as the author which system to use. github, launchpad, bitbucket
[14:54] <mbruzek> rock__: So I would put the url to a community page, or somewhere the user could get some help with this charm.
[14:54] <lazyPower> are 3 of the popular choices
[14:57] <stub`> I've put a promulgation request up at https://bugs.launchpad.net/charms/+bug/1619577 , which is I hope somewhere that gets it onto the right track?
[14:57] <mup> Bug #1619577: Review and promulgate telegraf <Juju Charms Collection:New> <https://launchpad.net/bugs/1619577>
[15:01] <rock__> mbruzek/lazypower: do I need to do any extra work with launchpad/github/bitbucket to manage bugs? Please tell me what I need to do right now w.r.t user perspective.
[15:01] <lazyPower> stub` - have you seen http://review.jujucharms.com?
[15:02] <mbruzek> rock__: Where is your layer code?
[15:02] <stub`> Ooh, shiny
[15:03] <mbruzek> rock__: You are building out of a version control system of some kind right? Any version control system should have a bug/issue/problem link. Unless it is internal, in that case you should make a page that tells users of your charms how to get a hold of you.
[15:03] <rock__> mbruzek: what do mean by layer code?
[15:04] <mbruzek> rock__: The charm code then
[15:04] <stub`> tvansteenburgh1: You should set the defaults of 'share email' and whatever else you need with the SSO login. I can't remember if you do that at your end, or if it is configuration in the SSO.
[15:04] <mbruzek> rock__: The code that you wrote to build this charm, I call that the "layer code"
[15:05] <tvansteenburgh1> stub`: i tried
[15:05] <rock__> mbruzek: Actually, I pushed my charm to store from local machine.
[15:09] <mbruzek> rock__: We have found it is best practice to use a version control system for the code.
[15:26] <rock__> mbruzek:  Thank you. I understood that If we have a version controll system for my code and if we set bug url link to that then that will be good.
[17:06] <rock__> marcoceppi: As we discussed before. This issue was not solved. Series miss match issue between mycharm and cinder while adding relation from JUJU GUI. pasted info  http://paste.openstack.org/show/566123/
[17:25] <rock__> Hi.  I have a question. For suppose acc. to openstack-base bundle requirements I have taken machines. Which node I have to take as main node to deploy bundle? Once I deployed bundle how that bundle distribute service charms to all hardware machines that we have taken?
[17:26] <rock__> Can any one provide me the network architeture of {MAAS+openstack base bundle] setup.
[18:48] <kwmonroe> petevg: cory_fu, any beef with my repo pr?  i'd like to get this in before i update ~bigdata-dev with xenial charms: https://github.com/juju-solutions/layer-apache-bigtop-base/pull/46/files
[18:49] <kwmonroe> kjackal ^^ you too, but you should be eod by now :)
[18:50] <kwmonroe> carrot cory_fu:  if you +1 my pr, i'll help you with the ODSC CFP
[18:56] <kwmonroe> lazyPower: i'm having trouble getting to http://ci.containers.juju.solutions:8080/.  is it up for you?
[18:56] <lazyPower> kwmonroe - i ran bundletester in that environment and didnt juju lock it, so i learned some hard lessons lastnight
[18:56] <davecore> jcastro: Hi
[18:56] <kwmonroe> lol lazyPower
[18:56] <kwmonroe> reset: false ftw
[18:57] <lazyPower> kwmonroe https://jujucharms.com/u/lazypower/container-ci
[18:57] <lazyPower> its all charmed up however, and i have 2 instances of it deployed and purring atm
[18:57] <lazyPower> i'll get the DNS back online before i EOD with its final resting place and send you new credentials
[18:57] <lazyPower> it'll be in teh same model i shared with you, but new user login/pass
[18:58] <kwmonroe> ack lazyPower... would you mind kicking a new charmbox devel build?  i'd like to beat on beta 17 this afternoon
[18:58] <lazyPower> kwmonroe - i have jujubox build and pushed at beta17
[18:58] <lazyPower> do you mind cloning locally and building a beta17 charmbox until we verify the test tooling updates still work for b17?
[18:58] <kwmonroe> roger that lazyPower
[18:59] <kwmonroe> but what are the chances test tooling and juju would be incompatible at this stage in the game?  i mean, we're in double digit betas dude.
[19:00] <lazyPower> i dont know why did beta16 break it? :)
[19:00] <lazyPower> so pretty good
[19:00] <kwmonroe> i was make joke
[19:00] <lazyPower> oh!
[19:00]  * lazyPower is dense on the interwebs
[19:01] <jrwren> beta is the new alpha.
[19:01] <kwmonroe> ha!
[19:01]  * lazyPower clicks the "like" button on jrwren's last post
[19:02]  * lazyPower assigns a thumbs up emojii 
[19:04] <jrwren> 😇 👍🏾
[19:17] <lazyPower> kwmonroe - let me know what you find out with charmbox, i just kicked off a build here too
[19:17] <lazyPower> if its thumbs up in both places we'll cut a release
[19:25] <cory_fu> kwmonroe: Added a comment and replied to petevg's comment.  Other than the tests and verifying the requiredness of the layer options, I think it's good
[19:27] <cory_fu> kwmonroe, petevg: Just checked; those options are *not* marked as required, but they do have default values.  I'm not sure if it's possible to actually remove the default for those
[19:28] <petevg> kwmonroe, cory_fu: the .get for those values just happens to make unit testing a lot easier. I don't mind moving away from it, but it will require a lot of fixing in the tests ...
[19:33] <plars> marcoceppi: Hey, I'm just starting to try to figure out reactive charms, and I saw you have a uwsgi layer. I have a really simple flask app that I'd like to make a charm for and deploy, so I thought this might be a good starting place
[19:33] <plars> marcoceppi: it's not clear to me how to define the config for it using the uwsgi layer though, or maybe I'm completely on the wrong track? Not really sure... having trouble finding a lot of good examples of reactive charms, especially ones using different layers
[19:34] <marcoceppi> plars: no worries, let me find you an example
[19:35] <lazyPower> https://github.com/juju-solutions/bundle-elk-stack/pull/4 -- could use some community eyes on this one, low hanging fruit, charm revision bumps
[19:36] <marcoceppi> plars: here's what I wrote the uwsgi layer for https://github.com/marcoceppi/layer-charmsvg
[19:37] <marcoceppi> plars: it's an example of uwsgi & nginx for a flask app
[19:37] <marcoceppi> lazyPower: have you tested this with bundletester?
[19:37] <lazyPower> marcoceppi - running now
[19:37] <marcoceppi> lazyPower: LGTM pending tests
[19:38] <lazyPower> marcoceppi - should i add this to build-cloud?
[19:38] <lazyPower> its kind of a cornerstone thing that a lot of people look for
[19:38] <plars> marcoceppi: awesome I'll take a look, thanks!
[19:38] <marcoceppi> lazyPower: sure :)
[19:38] <lazyPower> rgr
[19:38] <lazyPower> magicaltrout - is ELK good enough or do you *really need greylog*?
[19:38] <marcoceppi> plars: no worries, I wrote uswgi a little while ago, I'm sure I could improve it. With that it only really has one use case, my charmsvg layer
[19:38] <marcoceppi> plars: feel free to reach out if things don't make sense, because it's probably me not you :)
[19:50] <cory_fu> petevg: Yeah, I agree.  Though, we could actually just switch from using Mock() to MagicMock(), as it supports being used like a dict out of the box
[19:50] <cory_fu> kwmonroe: Easy fix for the tests: http://www.voidspace.org.uk/python/mock/magicmock.html#magic-mock
[19:50] <petevg> +1
[19:56] <kwmonroe> thx for the feedback cory_fu petevg!  i'll remove the unit tests and merge away.
[19:56] <cory_fu> lol, +1
[19:56] <kwmonroe> (kidding)
[22:02] <lazyPower> kwmonroe - testing tools were +1 LGTM on b17
[22:02] <lazyPower> were your findings ~ the same?
[22:08] <kwmonroe> lazyPower: i cheated and apt updated to b17.. didn't actually rebuild charmbox.  and i didn't exercise the test tools -- just your normal boostrap, deploy, add, destroy.
[22:08] <kwmonroe> that said, b17 was good to me
[22:08] <lazyPower> kwmonroe - you were a big help today :)
[22:09] <kwmonroe> lol