Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2014-11-24

| Channels | #puppet-openstack index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:01 mmaglana joined #puppet-openstack
00:02 imcsk8 gildub: one question
00:04 imcsk8 gildub: by any chance do you know what's the difference between nova-manage network create and nova network-create ?
00:05 imcsk8 gildub: BTW i'm ichavero
00:11 gildub imcsk8, I know it's you :)
00:13 gildub imcsk8, no I don't, well I know some nova-manage commands are piggy backing to others commands, so my understanding is it's the same thing because the same command is ran down anyway, but not sure it's always the case. Probably not really helpful :(
00:16 ToMiles joined #puppet-openstack
00:18 imcsk8 gildub: my problem is that i added the --allowed-start and --allowed-end parms to the nova puppet module but it uses nova-manage network  create  which currently does not have those params
00:19 gildub imcsk8, darn!
00:26 imcsk8 gildub: so  i'm not sure if y should change the nova command? http://paste.fedoraproject.org/153370/78878014/
00:32 gildub imcsk8, I think that's better to use the specific command, more flexible. The nova-manage is nice cli short but not sure how it keeps up to date with the specific ones
00:33 imcsk8 gildub: i just use the nova command for the create stuff because i don't want to introduce any unstabilities
00:35 gildub imcsk8, yeah I see
00:40 imcsk8 gildub: hahaha i only changed the comman for the create stuff and i got unstabilities
00:44 gildub imcsk8, when I see that I can't stop thinking using the API would be better
00:58 vinsh joined #puppet-openstack
01:08 imcsk8 gildub: yeah sounds like it but i think i should keep it with commands because that's how the module is
01:22 topshare joined #puppet-openstack
01:32 gildub imcsk8, yeah, of course, just a thought!
01:37 gildub imcsk8, btw, there is a current openstackclient vs Aviator discussion, have you seen it (on the mailing list)?
01:50 xingchao joined #puppet-openstack
02:05 ToMiles joined #puppet-openstack
02:33 badiane_ka joined #puppet-openstack
02:59 xingchao_ joined #puppet-openstack
03:01 gildub joined #puppet-openstack
03:08 gildub joined #puppet-openstack
03:30 xingchao joined #puppet-openstack
03:42 vinsh joined #puppet-openstack
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-ceilometer: Release 5.0.0 - Juno  https://review.openstack.org/136663
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-cinder: Release 5.0.0 - Juno  https://review.openstack.org/136664
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-glance: Release 5.0.0 - Juno  https://review.openstack.org/136665
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-heat: Release 5.0.0 - Juno  https://review.openstack.org/136666
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-horizon: Release 5.0.0 - Juno  https://review.openstack.org/136667
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Release 5.0.0 - Juno  https://review.openstack.org/136668
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-neutron: Release 5.0.0 - Juno  https://review.openstack.org/136669
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-nova: Release 5.0.0 - Juno  https://review.openstack.org/136670
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-swift: Release 5.0.0 - Juno  https://review.openstack.org/136671
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-tempest: Release 5.0.0 - Juno  https://review.openstack.org/136672
03:43 openstackgerrit Colleen Murphy proposed stackforge/puppet-vswitch: Release 1.0.0 - Juno  https://review.openstack.org/136673
03:44 openstackgerrit Colleen Murphy proposed stackforge/puppet-openstacklib: Release 5.0.0 - Juno  https://review.openstack.org/136674
03:45 openstackgerrit Colleen Murphy proposed stackforge/puppet-openstack_extras: Release 5.0.0 - Juno  https://review.openstack.org/136675
04:06 ToMiles joined #puppet-openstack
05:55 ToMiles joined #puppet-openstack
05:58 fedexo joined #puppet-openstack
06:08 sanjayu joined #puppet-openstack
06:24 sanjayu joined #puppet-openstack
06:52 michchap joined #puppet-openstack
07:05 stamak joined #puppet-openstack
07:12 sanjayu joined #puppet-openstack
07:18 ddmitriev joined #puppet-openstack
07:21 sanjayu joined #puppet-openstack
07:44 ToMiles joined #puppet-openstack
07:49 francois1 joined #puppet-openstack
07:55 beddari michchap: what are your current feeling about pupeeels? I'm thinking about combining data-in-modules with it to make it even more flexible (with hiera_include in there) and thus only keep a basic common flow/skeleton ...
07:55 beddari michchap: not sure if my team is ready for that though ...
07:55 michchap beddari: I am rewriting all our tools to use it right now, actually.
07:56 beddari michchap: with the intent of supporting upstream?
07:56 michchap beddari: yep. I have a large PR open that I'm not going to merge until I have more idea what I need to change.
07:57 beddari michchap: great, I'm in, or we are. I think I'll hold off with data-in-modules then even if my head wants it ;)
07:57 michchap beddari: I'm keeping the data and test harness in puppet_openstack_builder and consuming puppeels from there with a complete rewrite of the hierarchy
07:57 beddari <3 :)
07:57 michchap beddari: cool. I haven't pushed anything on the builder side back up yet.
07:58 beddari so your branch is the one I can see on GH?
07:58 michchap beddari: I'm including things like repo mirrors and image builders whatnot in the roles to try to make it a bit more complete.
07:59 michchap beddari: most of it is still local - I started on the plane back from Paris and did a bit more over the weekend.
07:59 beddari okay
08:00 michchap beddari: but it's my expectation I can get almost everything from my tooling into either puppeels, openstack_extras or a revamped builder, so I don't have to carry a module with random stuff in it.
08:00 beddari that would be best yes
08:00 michchap beddari: like firewall rules for openstack services, and that kind of thing.
08:01 beddari yup
08:02 beddari puppeels might need some written intent then, at some stage?
08:02 beddari or is Spredzy taking on the world? :P
08:02 michchap afaik puppeels is not in prod anywhere, and it's just spredzy so you can ask him what he's got in mind. I've talked to him and we agreed on about 90% of things.
08:03 beddari okay, I'm interested in e.g how/if the Foreman profiles are totally separated from the openstack stuff
08:04 beddari as they are not ... or was not, about 6 months ago, even close to being the same module set
08:04 beddari but who is he? I've only seen the github handle
08:04 beddari ah enovance :)
08:04 michchap he is on here.
08:06 michchap I don't really know that much about the foreman stuff. Totally separate from the enovance tooling afaik.
08:06 beddari yes
08:06 beddari exiting times ahead haha
08:07 beddari RDO meetup kind of summed it up in Paris, x tools, y people, 1 plan? :)
08:07 beddari z plans really
08:07 michchap I don't think I was there.
08:07 michchap actually I'm certain I wasn't there. My memory of Paris is hazy, but not that hazy
08:08 beddari no, you weren't but it was interesting
08:08 beddari a lot of the same things came up, e.g around packaging
08:08 beddari and I as a Red Hat customer and Foreman longtime user asked some hard questions hehe
08:09 dgurtner joined #puppet-openstack
08:09 dgurtner joined #puppet-openstack
08:12 gildub joined #puppet-openstack
08:13 beddari michchap: well thanks, now we're at least a small group committed to it!
08:14 arnaud_orange joined #puppet-openstack
08:14 michchap beddari: my main goal for this is actually not a prod system - I need a little virtual openstack environment builder that I can use for training and for messing up and getting people to fix in interviews.
08:14 michchap beddari: but hopefully I get time to make it more useful beyond my immediate need.
08:16 beddari sure, we got 10 monhts before anything prod-like but I want to start at the right place, which is this, as long as I'm allowed the definition ;)
08:27 beddari spredzy: you closed your upstream PR on multiple_accounts ...?
08:27 ToMiles joined #puppet-openstack
08:28 beddari spredzy: https://github.com/torranc​ew/puppet-account/pull/33 <- this, due to lack of input? something else?
08:30 badiane_ka joined #puppet-openstack
08:40 ToMiles joined #puppet-openstack
08:49 berendt joined #puppet-openstack
08:50 openstackgerrit Bogdan Dobrelya proposed stackforge/puppet-neutron: Add 'state_path' and 'lock_path' for Neutron::Server  https://review.openstack.org/136333
09:10 derekh joined #puppet-openstack
09:28 openstackgerrit Bogdan Dobrelya proposed stackforge/puppet-openstack_extras: Add pacemaker provider for HA services  https://review.openstack.org/136708
09:41 openstackgerrit Bogdan Dobrelya proposed stackforge/puppet-openstack_extras: Add pacemaker provider for HA services  https://review.openstack.org/136708
10:21 sanjayu joined #puppet-openstack
10:25 openstackgerrit Bogdan Dobrelya proposed stackforge/puppet-neutron: Add 'state_path' and 'lock_path' for Neutron::Server  https://review.openstack.org/136333
11:03 xingchao_ joined #puppet-openstack
11:04 ikke-t hello, is anyone familiar using librarian to collect openstack puppet modules?
11:04 ikke-t it fails with my list, due stackforge-keystone dependancy
11:04 ikke-t Unable to find module 'stackforge-keystone' on https://forgeapi.puppetlabs.com
11:05 ikke-t can I make it not to hunt for it, since I get all modules from github anyway?
11:06 ikke-t other openstack modules have dependency on puppetlabs/keystone, but stackforge one declares itself as stackforge-keystone
11:47 TorLaedre joined #puppet-openstack
11:51 michchap ikke-t: I think there are a few people here (myself included) that use librarian-puppet-simple precisely to avoid the dependency management
11:52 michchap ikke-t: Here's a starting point for you: https://github.com/michaeltchapman/​byopenstack/blob/master/Puppetfile
12:41 ToMiles joined #puppet-openstack
12:42 ToMiles joined #puppet-openstack
12:43 ikke-t michchap, thanks, sounds like it suits my purpose.
13:00 ikke-t michchap, that worked perfect for me, thanks for the tip :)
13:00 topshare joined #puppet-openstack
13:01 topshare joined #puppet-openstack
13:04 spredzy beddari, hmmm possible I cleaned some PR that was on for more than 6 months and didn
13:04 spredzy t get any feedback. let me make it point to my current branch on my own fork. Where did you hit this bug ?
13:05 spredzy PS. I am using pupeels w/ foreman on my set up. Parameter handling is not optimal yet, but it's actually working fine once you find your way out
13:09 spredzy michchap, I submitted a PR on beaker to support vagrant-libvirt as a backend, I'll try to CI every puppeels profile as soon as I find the time
13:10 michchap spredzy: hey I have a quick qn for you. gimme 1 sec I'll push my current crap up so you can take a look...
13:10 beddari spredzy: ok thanks, didn't 'find' any bug was just curious if you got that PR in
13:12 michchap spredzy: https://github.com/michaeltchapman/puppet_op​enstack_builder/tree/r7/hiera/data/profiles
13:13 michchap spredzy: make the data hierarchy match the profile directory structure?
13:13 michchap spredzy: like/dislike?
13:14 beddari so for me, more confusing than useful hehe, as I'd use different semantics for the data
13:14 michchap spredzy: still need a shared area for common data across profiles, but it might remove a bit of the 'where is this thing being set?
13:14 badiane_ka joined #puppet-openstack
13:14 michchap beddari: how do you mean?
13:15 EmilienM michchap: hey
13:15 beddari this -> https://gist.github.com/be​ddari/5449cd3a52c695752e07
13:15 spredzy michchap, I do like it, if you look at puppeels-example the data file can quickly become messy
13:16 spredzy with a layer of data that matches the layer of code, I think it is mentally easier to know where to go look for those data
13:16 michchap beddari: so you're doing data by role, location, and hostname?
13:16 beddari for me, there is value in keeping the hierarchy as simple as possible
13:16 beddari michchap: yes ... and only that ...
13:17 beddari michchap: by embedding that data into $trusted certname
13:17 michchap beddari: I used to think that, but having now seen the hierarchy for an 8 Datacentre openstack cluster I'm not so sure. The amount of data getting passed is unweildy and eg. the database team doesn't know which things they are allowed to change.
13:18 beddari michchap: in my opinion, if you get to that, you would be better off to start looking at alternative backends
13:18 michchap spredzy: ok. I will continue the experiment and see if I still like it at the end of the week.
13:18 beddari michchap: like consul, or the Foreman db, as sources
13:19 michchap beddari: it will be the same problem: how do I partition the data so that people can touch it and know they wont' break things elsewhere
13:19 morazi joined #puppet-openstack
13:20 beddari michchap: the same problem, but ... again, I think Hiera is not the right tool once you start having data classification needs
13:21 beddari michchap: I've seen people split up hieradata into different repos for that use case, it might work ...
13:21 beddari for me a simple host, then role, then defaults for that role, then common ... is the best compromise
13:23 openstackgerrit Mike Dorman proposed stackforge/puppet-horizon: Matching ip parameter on ::apache and apache::vhost classes  https://review.openstack.org/123344
13:23 michchap beddari: right.
13:23 michchap beddari: btw have you been following the packaging convo on openstack-operators?
13:23 beddari location could be abstract if needed, to map teams etc
13:24 beddari not recently, should have :>
13:25 beddari I'll read up on it
13:26 patcable joined #puppet-openstack
13:26 tchaypo joined #puppet-openstack
13:28 simonmcc_ joined #puppet-openstack
13:28 mattymo joined #puppet-openstack
13:31 EmilienM sbadia: I'll let you +A the release patches from crinkle
13:34 mdorman joined #puppet-openstack
13:34 beddari michchap: nice discussion, I'm hoping we can _not_ create something openstack-specific, as you know ...
13:35 michchap beddari: I like the look of delorean, and the specs being under openstack-packages.
13:36 michchap beddari: giftwrap and anvil are clearly more mature, though
13:36 beddari michchap: at this point mature is ... not ;)
13:37 sbadia hi!
13:37 sbadia dmsimard_away: oups sorry for the delay…
13:37 * sbadia backlog
13:37 beddari michchap: for me still the point is, this is what I do already, I don't mind switching tools but hey it is a general problem
13:38 beddari michchap: e.g puppetlabs now building packages for 4.0 the same way  ... and releasing whatever tooling they created
13:39 sbadia dmsimard_away: designate is still a bit young I think :) (especialy for bind9 support, pdns is ok)
13:39 beddari michchap: I'll try adding some thoughts to the thread later :)
13:39 sbadia dmsimard_away: and about puppet-designate, debian now works (I've pushed a couple of patches :p)
13:39 michchap beddari: please do.
13:39 sbadia dmsimard_away: so yes it's usable on debian
13:39 francois joined #puppet-openstack
13:39 michchap EmilienM: morning :)
13:40 sbadia EmilienM: ah fine! thanks, ack for the +A
13:42 francois joined #puppet-openstack
13:46 beddari michchap: I think craig_tracey might disagree with us mildly on "I do not think that any tool(s) that we converge around should be dealing with third party/system packaging. This would almost certainly introduce a slew of new items to support as well as incompatibilities/edge cases between distros."
13:46 michchap beddari: quite possible.
13:46 beddari I for one need and depend on being able to do both ...
13:47 beddari for me the new thing you did was to pull in external source packages
13:47 beddari as opposed to "just tarballs" from upstream
13:47 beddari I think that too can and should be generalized though :)
13:48 ericpeterson joined #puppet-openstack
13:48 beddari I do see why you want yaml definitions for simplicity, I think maybe my new dream is yaml -> DSL -> consumption :)
13:49 michchap beddari: I kind of agree. I think derekh's ideas in delorean are pretty close to what I want. Something that spins up a container to build me packages, but isn't a configuration nightmare like koji
13:49 beddari which is what I was getting at with using hiera as the input mechanism for yaml defined 'content'
13:50 michchap beddari: ah
13:50 beddari yes I was going to look at it, he mentioned it at the RDO meetup where as I said all the different packaging apporaches inside just Red Hat became a topic
13:54 beddari " A number of operators have expressed confusion
13:54 beddari and concern about updating an app with whole image updates"
13:54 beddari ? :)
13:54 beddari mostly confusion I hope
13:54 michchap it works in devstack
13:55 bogdando hi. guysm where is an agenda for meetings?
13:56 michchap hey bogdando get someone from mirantis to reply to the packaging thread :)
13:56 nibalizer on the wiki i think
13:56 crinkle morning
13:56 beddari michchap: did you look at the fuel tooling yet?
13:56 nibalizer https://wiki.openstack.org/w​iki/Meetings/PuppetOpenStack
13:57 michchap beddari: Not yet.
13:57 beddari me neither :) I will now though, thanks for pushing this
13:57 beddari I got a blog post halfwritten too ...
13:58 bogdando nibalizer, thanks. Is https://wiki.openstack.org/wiki/​Puppet-openstack#Weekly_meetings an obsolete?..
13:58 bogdando nibalizer, they look detached
13:59 crinkle it's just pointing to the /Meetings/PuppetOpenStack one
14:00 bogdando ok thanks, how do you add items on agenda?
14:01 crinkle log in on the top right and then edit it
14:01 nibalizer bogdando: can you add an 'Integration tests (nibalizer)' bullet point while you are at it
14:04 openstackgerrit Christian Berendt proposed stackforge/puppet-horizon: Add support for the configuration of OPENSTACK_CINDER_FEATURES  https://review.openstack.org/136762
14:04 bogdando nibalizer, done
14:05 nibalizer woo
14:06 mattymo are there any resource tools for creating a nova instance flavor? I don't see anything in puppet-nova
14:09 mdorman mattymo:  there’s a review i submitted a while back that implements that (https://review.openstack.org/#/c/119997/ ), but I don’t think it will be merged because it relies on the ‘nova-manage flavor’ command, which are deprecated
14:11 mattymo so it needs to be refactored to use nova client
14:11 beddari I guess it depends on what scope you are talking about? openstack common client ... ?
14:11 mdorman yeah, or better yet hte openstack cli client.  i think i originaly did it this way so i didn’t have to deal with auth’ing to the cli clients
14:11 mdorman yeah
14:12 beddari I'm doing stuff in my profiles with http://aviator.github.io/www/2~
14:13 beddari minus that 2~  ...
14:13 mattymo ok so it seems that it's an impasse and we won't see flavor management in puppet until a new management system is in place
14:13 mdorman there was an efffort to move all the stackforge puppet stuff to aviator, but now i think the consensus is to use the openstack common client instead
14:14 mattymo either way, it means months before a real solution
14:14 beddari it was a topic in Paris and yeah, that was the outcome
14:14 mdorman i think that’s probably a realistic statement, yeah
14:14 mdorman i don’t know that it’s months…  just needs somebody to work on it.
14:14 dgurtner joined #puppet-openstack
14:14 dgurtner joined #puppet-openstack
14:14 mattymo just trying to squash a tiny bug: https://bugs.launchpad.net/fuel/+bug/1318512
14:14 mattymo but it's easier to do it with an exec than to accept a mammoth system
14:15 mdorman agreed
14:15 richm joined #puppet-openstack
14:15 mdorman i had a similar situation ,which is where the above review came from.  i just run that locally on an openstack-nova fork
14:15 mdorman until there is a real solution for it upstrea
14:15 mdorman *upstream
14:23 EmilienM bogdando: do you know when you will push the first PoC of code for Pacemaker?
14:24 bogdando EmilienM, by the several next days
14:24 bogdando I cannot guarantee it will work with generic OCF scripts, from https://github.com/madkiss​/openstack-resource-agents
14:25 EmilienM bogdando: ok
14:28 beddari michchap: I
14:29 beddari michchap: I'd be interested in seeing that hieradata if possible, to think about modelling
14:29 beddari michchap: if it is possible to share somehow :]
14:29 EmilienM bogdando: do you have an example of code somewhere?
14:34 bogdando EmilienM, yes, https://github.com/stackforge/fuel-library/blob/ma​ster/deployment/puppet/heat_ha/manifests/engine.pp
14:34 bogdando (EmilienM, it is supposed to be moved to extras,eventually...)
14:35 bogdando EmilienM, and pacemaker_wrappers::service actually should be openstack_extras::pacemaker::service
14:35 EmilienM bogdando: I would like to see the pacemaker_wrappers code also
14:35 EmilienM yeah, awesome
14:36 bogdando EmilienM, yes, the code is here: https://review.openstack.org/#/c/13​6708/2/manifests/pacemaker/service.pp
14:36 bogdando EmilienM, we just use another module for now, so it is a bit confusing )
14:36 EmilienM bogdando: will review later
14:39 patcable joined #puppet-openstack
14:40 bogdando EmilienM, looks like I forget to move https://blueprints.launchpad.net/puppet-no​va/+spec/pacemaker-provider-for-openstack to puppet-openstack (it was in puppet-nova initially)
14:40 EmilienM bogdando: I did a very first review so far
14:40 bogdando have an idea how to fix the location?
14:40 EmilienM not sure you can move blueprints.
14:41 bogdando oh
14:41 bogdando will copy paste then
14:44 rcallawa joined #puppet-openstack
14:45 bogdando EmilienM, should I use https://blueprints.launchpad.net/openstack ?.. I'm confused with name spaces :/
14:46 EmilienM mgagne knows better
14:46 bogdando mgagne, ^^ please some help
14:47 bogdando I created another one https://blueprints.launchpad.net/puppet-open​stack/+spec/pacemaker-provider-for-openstack. But looks like it should be 'openstack' path instead
14:47 EmilienM bogdando: to me, https://blueprints.launchpad.net/puppet-openstack is the right place.
14:49 morazi joined #puppet-openstack
14:59 rharrison joined #puppet-openstack
15:07 dgurtner joined #puppet-openstack
15:07 dgurtner joined #puppet-openstack
15:13 prad joined #puppet-openstack
15:31 vinsh joined #puppet-openstack
15:33 openstackgerrit Colleen Murphy proposed stackforge/puppet-heat: Release 5.0.0 - Juno  https://review.openstack.org/136666
15:41 openstackgerrit Merged stackforge/puppet-glance: Release 5.0.0 - Juno  https://review.openstack.org/136665
15:48 mdorman looking for folks to take a look at https://review.openstack.org/#/c/70344/ for nova aggregate support, please
15:49 EmilienM mdorman: oh that one...
15:49 EmilienM mdorman: the code is good, I think people here can't test it easily
15:57 openstackgerrit Merged stackforge/puppet-cinder: Release 5.0.0 - Juno  https://review.openstack.org/136664
16:00 ericpeterson joined #puppet-openstack
16:03 mdorman EmilienM:   ok.  suggestions on how to proceed?  Find people who can test it?
16:05 EmilienM mdorman: if you tested it and if the code looks good, I would +2 it
16:15 mdorman joined #puppet-openstack
16:30 mdorman joined #puppet-openstack
16:41 cwolferh joined #puppet-openstack
16:54 JayJ joined #puppet-openstack
16:56 JayJ Can somebody enlighten me with a very basic question? Where is ephemeral disk of the instance stored on the physical disk? I assumed it should be under /var/... qemu/images, default location. I cannot find it there!
16:58 guimaluf JayJ, ephemeral disk is under /var/lib/nova/instances/00700e6​c-db99-4087-b0ad-9d690f0aedea/
17:00 JayJ guimaluf: Ah! Thanks
17:03 crinkle someone else want to push https://review.openstack.org/#/c/136650/ and https://review.openstack.org/#/c/136651/ through for me?
17:19 mschmitt joined #puppet-openstack
17:20 ericpeterson joined #puppet-openstack
17:25 rmoe joined #puppet-openstack
17:32 sbadia re
17:32 sbadia crinkle: for https://review.openstack.org/#/c/136650/
17:32 sbadia apache module was pinned to 1.1.2 because 1.1.1 doesn't include the fix for https://bugs.launchpad.net/​puppet-horizon/+bug/1374634
17:32 sbadia refs https://tickets.puppetlabs.com/browse/MODULES-1332
17:33 sbadia so we should modify to >=1.2.0 <2.0.0 or =1.2.0 :)
17:55 crinkle sbadia: the problem with 1.2.0 is that this pull request breaks our usage of the apache module https://github.com/puppetlab​s/puppetlabs-apache/pull/881
17:55 crinkle but i can dedicate time today to fixing that rather than pinning it
17:56 sbadia arf, ok I see :/
18:00 ericpeterson joined #puppet-openstack
18:01 openstackgerrit Merged stackforge/puppet-openstacklib: Drop rabbitmq dependency to <4.0.0  https://review.openstack.org/136651
18:08 openstackgerrit Merged stackforge/puppet-nova: Release 5.0.0 - Juno  https://review.openstack.org/136670
18:23 openstackgerrit Sebastien Badia proposed stackforge/puppet-designate: backend/bind9 Added allow-new-zones configuration option.  https://review.openstack.org/132479
18:25 openstackgerrit Colleen Murphy proposed stackforge/puppet-horizon: Update horzion::wsgi::apache for new apache module  https://review.openstack.org/136852
18:25 crinkle sbadia: ^
18:25 openstackgerrit Merged stackforge/puppet-ceilometer: Release 5.0.0 - Juno  https://review.openstack.org/136663
18:25 openstackgerrit Merged stackforge/puppet-swift: Release 5.0.0 - Juno  https://review.openstack.org/136671
18:27 richm joined #puppet-openstack
18:29 openstackgerrit Merged stackforge/puppet-keystone: Release 5.0.0 - Juno  https://review.openstack.org/136668
18:34 openstackgerrit Merged stackforge/puppet-neutron: Release 5.0.0 - Juno  https://review.openstack.org/136669
18:44 openstackgerrit Merged stackforge/puppet-tempest: Release 5.0.0 - Juno  https://review.openstack.org/136672
18:44 openstackgerrit Sebastien Badia proposed stackforge/puppet-designate: spec: Added designate::* unit tests  https://review.openstack.org/132480
18:45 sbadia crinkle: thanks! /me take a look
18:53 aimon joined #puppet-openstack
19:01 ericpeterson joined #puppet-openstack
19:05 xarses joined #puppet-openstack
19:20 prad joined #puppet-openstack
19:30 ericpeterson joined #puppet-openstack
19:37 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Use openstackclient for keystone_tenant  https://review.openstack.org/134844
19:52 mmaglana joined #puppet-openstack
20:05 ericpeterson joined #puppet-openstack
20:08 openstackgerrit Merged stackforge/puppet-vswitch: Release 1.0.0 - Juno  https://review.openstack.org/136673
20:11 openstackgerrit Merged stackforge/puppet-openstack_extras: Release 5.0.0 - Juno  https://review.openstack.org/136675
20:20 openstackgerrit Merged stackforge/puppet-heat: Release 5.0.0 - Juno  https://review.openstack.org/136666
20:26 EmilienM crinkle: release day \o/
20:35 openstackgerrit Richard Megginson proposed stackforge/puppet-keystone: setup keystone using apache mod_wsgi  https://review.openstack.org/136885
20:39 EmilienM richm: what do you think about https://review.openstack.org/#/c/136442/ ?
20:40 openstackgerrit Richard Megginson proposed stackforge/puppet-keystone: fix apache::vhost concat test breakage  https://review.openstack.org/136887
20:40 richm EmilienM: looking . . .
20:42 EmilienM dmsimard_away: mgagne: did I miss something or our puppet-swift miss the WSGI process support like we have in p-key ?
20:43 mgagne EmilienM: AFAIK, keystone is one of the only ones with apache wsgi support
20:43 mgagne EmilienM: in our puppet modules
20:46 crinkle EmilienM: want to look at https://review.openstack.org/#/c/136852/ for me?
20:48 EmilienM crinkle: looking right now.
20:50 EmilienM crinkle: lgtm, but wait for jenkins. Don't we need to update unit tests?
20:51 crinkle oh i didn't notice jenkins hadn't reported yet
20:51 crinkle maybe need to update, let me look
20:52 crinkle yep good call
20:54 morazi joined #puppet-openstack
20:55 openstackgerrit Colleen Murphy proposed stackforge/puppet-horizon: Update horzion::wsgi::apache for new apache module  https://review.openstack.org/136852
21:00 richm barbican is planning to use wsgi too
21:05 mdorman joined #puppet-openstack
21:12 EmilienM richm: my first concern is openstack core services that have issues at scale (nova-api & neutron-server)
21:12 richm EmilienM: ok
21:22 patcable hmm. i just noticed that if $rabbit_hosts you need to ensure "rabbit_host" is absent
21:22 patcable since apparently many config files have *both* values
21:22 patcable is there a good guide to submitting a PR to the stackforge modules?
21:25 mgagne patcable: we follow the same contribution process as OpenStack
21:25 patcable yeah, i dont know what that is
21:26 mgagne https://wiki.openstack.org/wiki/Gerrit_Workflow
21:26 patcable ill dig around for it
21:26 mgagne patcable: we use gerrit to manage reviews
21:26 patcable that link helps, thanks :)
21:26 EmilienM patcable: each patch is made of doc & unit test update FYI
21:27 patcable that makes sense
21:28 patcable eh. i think the CLA may prove problematic for my workplace though
21:29 patcable also cant use ssh externally
21:30 gildub joined #puppet-openstack
21:32 mmaglana joined #puppet-openstack
21:34 EmilienM patcable: oops, can you use tunnel or VPN?
21:35 patcable super not allowed
21:35 EmilienM \o/
21:35 patcable i'm gonna try and get a CCLA signed and such
21:35 EmilienM patcable: I don't know I can help
21:35 patcable its okay, just frustrated at $work
21:35 EmilienM patcable: you can give me your code otherwise
21:36 patcable yeah i need to figure out exactly where it is -- basically if $rabbit_hosts is defined, rabbit_host needs to be absent with the config thing. I'm gonna try and see if I can't get a CCLA signed somehow :)
21:52 mdorman joined #puppet-openstack
22:02 francois1 joined #puppet-openstack
22:11 imcsk8 joined #puppet-openstack
22:19 sputnik13 joined #puppet-openstack
22:48 JayJ joined #puppet-openstack
22:57 richm I'm trying to do a packstack install with the latest openstackclient and puppet-keystone changes to use openstack - the latest python-openstackclient requires stevedore > 1.1.0 - so I install this version in my vm - however, somewhere during the packstack puppet run, stevedore is reset to version 1.0.0
22:57 richm I'm not sure where this is coming from - grepping for stevedore in packstack and opm shows nothing
22:57 richm it must be some sort of dependency of a dependency of a dependency

| Channels | #puppet-openstack index | Today | | Search | Google Search | Plain-Text | summary