[00:50] 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] I haven't looked into it further, it could be the repository doesn't match what the tool assumes [00:53] 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] as long as I deploy all containers to one machine, it's ok :/ [00:58] pragsmike: Looks like it's reported: https://bugs.launchpad.net/juju/+bug/1618948 [00:58] Bug #1618948: Can't bootstrap localhost cloud [01:12] hmm, that doesn't seem to be related, you sure that # is correct? [05:58] Hello Juju World! === frankban|afk is now known as frankban === ant_ is now known as Guest84579 [10:49] 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] bcsaller: oooh.... python3-pip only recommends build-essential (and python3-setuptools, and python3-wheel), so some deploys won't get those === Guest84579 is now known as antdillon [12:02] 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] hi kwmonroe , how to push ibm-im charm for xenial series in to charm store ?(charm push . cs:~ibmcharmers/xenial/ibm-im) [13:49] hello team, how to build a deployable charm under xenial directory? [13:52] 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] ok if we give xenial first the deployable charm will be build under xenial directory is it ? [13:54] 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] 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] oh k thanku [13:56] tp push charm for xenial series in to charm store do we need to use charm push . cs:~ibmcharmers/xenial/ibm-im? [13:57] 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] I think pushing to a specific series works too, although I haven't tried it [13:58] we have IBM-IM charm for trusty in charm store , now i want to push for xenial with same name [13:58] But the charm store is smart enough to look at the series: in metadata.yaml and do the right thing I think. [13:58] 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] Ok. I'd try pushing to xenial/ibm-im as you sugested. [13:59] iam getting that error if i try to push with xenial series [14:00] 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] 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] ohh ok thanku stub` [14:12] 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] 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] stub: Yes. first command I ran. But it ran with out giving any response. [14:24] 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] I don't think 'charm set' says anything on success. [14:26] oh, that bugs url isn't valid [14:29] 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] 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] Is your charm in a branch on Launchpad? What is the branch URL? [14:33] Or maybe the openstack people here know. [14:36] rock__ o/ [14:36] rock__ - i understand you're having some issues publishing to the juju charm store? [14:40] welcome! [14:40] 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] rock__ - charm set cs:~lazypower/foo bugs-url=https://foobar.co [14:42] as an example [14:46] 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] rock__ - you've apparently set bugs-url to https://kaminario-openstack.co/ [14:48] rock__: that url does not resolve for me [14:48] rock__: https://kaminario-openstack.co/ [14:48] 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] 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] 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] rock__: Github or Launchpad are not required . But the URL should resolve or the bug link will not work [14:53] lazypower: I tried a moment later. Then also it was giving the same issue. [14:54] 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] its up to you as the author which system to use. github, launchpad, bitbucket [14:54] rock__: So I would put the url to a community page, or somewhere the user could get some help with this charm. [14:54] are 3 of the popular choices [14:57] 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] Bug #1619577: Review and promulgate telegraf [15:01] 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] stub` - have you seen http://review.jujucharms.com? [15:02] rock__: Where is your layer code? [15:02] Ooh, shiny [15:03] 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] mbruzek: what do mean by layer code? [15:04] rock__: The charm code then [15:04] 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] rock__: The code that you wrote to build this charm, I call that the "layer code" [15:05] stub`: i tried [15:05] mbruzek: Actually, I pushed my charm to store from local machine. [15:09] rock__: We have found it is best practice to use a version control system for the code. [15:26] 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. === frankban is now known as frankban|afk [17:06] 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] 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] Can any one provide me the network architeture of {MAAS+openstack base bundle] setup. === lazyPower changed the topic of #juju to: Welcome to Juju! || Docs: http://jujucharms.com/docs || FAQ: http://goo.gl/MsNu4I || Review Queue: http://review.juju.solutions || Unanswered Questions: http://goo.gl/dNj8CP || Youtube: https://www.youtube.com/c/jujucharms || Charmer Summit Sept 12-14th http://summit.juju.solutions || Juju 2.0 beta-17 release notes: https://jujucharms.com/docs/devel/temp-release-notes [18:48] 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] kjackal ^^ you too, but you should be eod by now :) [18:50] carrot cory_fu: if you +1 my pr, i'll help you with the ODSC CFP [18:56] lazyPower: i'm having trouble getting to http://ci.containers.juju.solutions:8080/. is it up for you? [18:56] kwmonroe - i ran bundletester in that environment and didnt juju lock it, so i learned some hard lessons lastnight [18:56] jcastro: Hi [18:56] lol lazyPower [18:56] reset: false ftw [18:57] kwmonroe https://jujucharms.com/u/lazypower/container-ci [18:57] its all charmed up however, and i have 2 instances of it deployed and purring atm [18:57] i'll get the DNS back online before i EOD with its final resting place and send you new credentials [18:57] it'll be in teh same model i shared with you, but new user login/pass [18:58] ack lazyPower... would you mind kicking a new charmbox devel build? i'd like to beat on beta 17 this afternoon [18:58] kwmonroe - i have jujubox build and pushed at beta17 [18:58] do you mind cloning locally and building a beta17 charmbox until we verify the test tooling updates still work for b17? [18:58] roger that lazyPower [18:59] 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] i dont know why did beta16 break it? :) [19:00] so pretty good [19:00] i was make joke [19:00] oh! [19:00] * lazyPower is dense on the interwebs [19:01] beta is the new alpha. [19:01] ha! [19:01] * lazyPower clicks the "like" button on jrwren's last post [19:02] * lazyPower assigns a thumbs up emojii [19:04] 😇 👍🏾 [19:17] kwmonroe - let me know what you find out with charmbox, i just kicked off a build here too [19:17] if its thumbs up in both places we'll cut a release [19:25] 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] 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] 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] 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] 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] plars: no worries, let me find you an example [19:35] 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] plars: here's what I wrote the uwsgi layer for https://github.com/marcoceppi/layer-charmsvg [19:37] plars: it's an example of uwsgi & nginx for a flask app [19:37] lazyPower: have you tested this with bundletester? [19:37] marcoceppi - running now [19:37] lazyPower: LGTM pending tests [19:38] marcoceppi - should i add this to build-cloud? [19:38] its kind of a cornerstone thing that a lot of people look for [19:38] marcoceppi: awesome I'll take a look, thanks! [19:38] lazyPower: sure :) [19:38] rgr [19:38] magicaltrout - is ELK good enough or do you *really need greylog*? [19:38] 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] plars: feel free to reach out if things don't make sense, because it's probably me not you :) [19:50] 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] kwmonroe: Easy fix for the tests: http://www.voidspace.org.uk/python/mock/magicmock.html#magic-mock [19:50] +1 [19:56] thx for the feedback cory_fu petevg! i'll remove the unit tests and merge away. [19:56] lol, +1 [19:56] (kidding) === rmcall_ is now known as rmcall [22:02] kwmonroe - testing tools were +1 LGTM on b17 [22:02] were your findings ~ the same? [22:08] 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] that said, b17 was good to me [22:08] kwmonroe - you were a big help today :) [22:09] lol