Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2014-06-16

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

All times shown according to UTC.

Time Nick Message
00:14 ikke-t joined #puppet-openstack
00:26 ianw joined #puppet-openstack
01:34 kkirkpatrick joined #puppet-openstack
01:46 gildub joined #puppet-openstack
02:26 gildub joined #puppet-openstack
05:00 EmilienM good morning
05:16 saneax_-_ joined #puppet-openstack
05:37 dachary1 joined #puppet-openstack
05:38 dachary1 left #puppet-openstack
05:38 dachary1 joined #puppet-openstack
05:43 dachary1 joined #puppet-openstack
06:18 dachary1 joined #puppet-openstack
06:22 dachary1 joined #puppet-openstack
06:38 aldavud joined #puppet-openstack
06:38 aldavud__ joined #puppet-openstack
06:38 aldavud_ joined #puppet-openstack
07:18 Waao joined #puppet-openstack
07:21 tfz joined #puppet-openstack
07:48 Ours_ joined #puppet-openstack
07:49 Trax joined #puppet-openstack
07:49 Schin joined #puppet-openstack
07:49 Waao Hi there
07:49 Ours Hi
07:50 Schin Hi
07:50 Trax Hi!
07:50 Niyaven joined #puppet-openstack
07:50 airliquide joined #puppet-openstack
07:50 Grus joined #puppet-openstack
07:50 airliquide Hi there !
07:50 Niyaven Hello everyone !
07:51 MathieuP joined #puppet-openstack
07:51 S219_ joined #puppet-openstack
07:52 S219 joined #puppet-openstack
07:53 JayJay_972 joined #puppet-openstack
07:54 JayJay_972 Hi Everyone!
07:55 Waao Oh genre l'autre, comment il nous dit bonjour
07:55 mlumeau joined #puppet-openstack
07:55 mlumeau hello this is patrick
07:55 MathieuP hello patrick
07:56 AlexisD joined #puppet-openstack
07:56 Guest44256 left #puppet-openstack
07:56 NicolasMAZEN joined #puppet-openstack
07:57 AlexisDEVISE joined #puppet-openstack
07:57 lrocher joined #puppet-openstack
07:59 GuillaumeS31 joined #puppet-openstack
07:59 Romain__ joined #puppet-openstack
07:59 GuillaumeS31 Helllo
07:59 Romain__ Hello guillaume
07:59 th0rnspear Hello this is dog!
07:59 Thierno_ joined #puppet-openstack
07:59 AlexisDEVISE where is bryan ?
08:00 Trax In your...
08:00 th0rnspear apartment
08:01 pernotjln joined #puppet-openstack
08:01 pernotjln hi guys
08:01 th0rnspear hello this is sparta
08:02 PhaFTa joined #puppet-openstack
08:02 S219_ joined #puppet-openstack
08:02 th0rnspear hello S219
08:03 PhaFTa hello
08:03 lrocher_ joined #puppet-openstack
08:03 Florian_ joined #puppet-openstack
08:03 Florian_ Hey everyone :)
08:03 pernotjln omelette du fromage
08:03 S219YannD joined #puppet-openstack
08:03 GuillaumeS31 hi omelette
08:03 Zoshonel joined #puppet-openstack
08:04 GuillaumeS31 hello Florian
08:04 Zoshonel hello
08:04 pernotjln how are you ?
08:04 S219YannD Salut
08:04 pernotjln from all ?
08:04 Romain__ hello
08:04 th0rnspear US
08:04 Zoshonel this is a public chanel, please respect other people :)
08:04 S219YannD soory
08:04 SylvainTim Hello all
08:04 S219YannD sorry*
08:05 Fabien_ joined #puppet-openstack
08:05 Romain__ hello Fabien
08:05 Fabien_ Bonjour
08:06 aldavud joined #puppet-openstack
08:06 aldavud_ joined #puppet-openstack
08:06 dachary1 aldavud hi
08:06 dachary1 lots of puppet-ceph new contributors today ;-)
08:07 pernotjln xD
08:07 GuillaumeS31 we're happy to be there to contribute !
08:09 EmilienM guys, please respect this channel and don't pollute. Your IP is tracked and we all know you are students in IUT Toulouse 2 Blagnac.
08:09 GuillaumeS31 whois powa
08:19 aldavud_ dachary1: hi
08:20 aldavud_ dachary1: so the class started?
08:20 th0rnspear yes
08:20 Waao oh yes.
08:27 artem_panchenko joined #puppet-openstack
08:34 dachary1 aldavud: yes ;-) coffee time !
08:36 dachary1 EmilienM: thanks for your patience :-)
08:47 EmilienM GuillaumeS31: th0rnspear : just to let you know, this is not a playground here and if you want to talk, it's about Puppet/OpenStack/Ceph tools, otherwise, please go to another channel to have fun ;-)
08:55 th0rnspear my apologies.
08:55 S219 joined #puppet-openstack
09:04 lrocher__ joined #puppet-openstack
09:10 starmer joined #puppet-openstack
09:17 mmagr joined #puppet-openstack
09:33 SylvainTim joined #puppet-openstack
09:39 gcha joined #puppet-openstack
09:43 mathieuP joined #puppet-openstack
09:46 S219 joined #puppet-openstack
09:49 Schin Is it necessary to install "git-review" ?
09:51 EmilienM Schin: to contribute, yes.
09:51 EmilienM Schin: https://wiki.openstack.org/wiki/Gerrit_Workflow
10:06 Schin EmilienM: Thank you, we are discussing this point with our teacher (dachary1).
10:07 openstackgerrit joined #puppet-openstack
10:08 EmilienM Schin: you're lucky to have Loic as a teacher ;-)
10:22 EmilienM I wonder if michchap will be around for our puppet meeting
10:30 Waao Bybye have a nice day :)
10:31 NicolasMAZEN good bye
10:36 openstackgerrit joined #puppet-openstack
11:50 markvoelker joined #puppet-openstack
11:58 dachary1 joined #puppet-openstack
12:03 flebeau joined #puppet-openstack
12:15 csschwe joined #puppet-openstack
12:24 flebeau left #puppet-openstack
12:27 dprince joined #puppet-openstack
12:47 michchap EmilienM: I might stay up and watch germany vs portugal so I'll be around.
12:47 EmilienM \o/
13:32 openstackgerrit Loic Dachary proposed a change to stackforge/puppet-ceph: test  https://review.openstack.org/100251
13:51 kkirkpatrick joined #puppet-openstack
13:54 mjblack joined #puppet-openstack
13:59 mjblack joined #puppet-openstack
14:03 aldavud joined #puppet-openstack
14:08 kevin joined #puppet-openstack
14:13 openstackgerrit Lukas Bezdicka proposed a change to stackforge/puppet-swift: Fix path for restorecon  https://review.openstack.org/100259
14:29 rwsu joined #puppet-openstack
14:30 doo joined #puppet-openstack
14:47 doo joined #puppet-openstack
14:47 xingchao joined #puppet-openstack
14:50 prad_ joined #puppet-openstack
14:51 brandon_mi joined #puppet-openstack
15:02 xingchao joined #puppet-openstack
15:02 hogepodge joined #puppet-openstack
15:02 hogepodge Good morning
15:03 Hunner 'lo
15:03 hogepodge Let me get the etherpad set up
15:03 Hunner driving in there in 16 minutes
15:04 hogepodge #begin meeting
15:04 hogepodge Etherpad for notes
15:04 hogepodge https://etherpad.openstack.org/p/puppet-openstack-2014-06-16
15:04 EmilienM hello
15:05 Guest25708 joined #puppet-openstack
15:05 michchap Morning
15:06 xingchao hello
15:06 spredzy hi all
15:06 hogepodge So I’ve been gone for a week, and haven’t kept up on much of anything. I have a bit of catching up to do.
15:07 EmilienM hogepodge: there is not much actually
15:07 hogepodge #topic puppet-openstacklib
15:07 xarses joined #puppet-openstack
15:07 hogepodge Have we made much progress on that? Were Dan’s changes accepted to core yet?
15:08 hogepodge s/core/infra/
15:08 hogepodge (hm, I don’t see the project)
15:08 Guest8031 hogepodge: AFAIK, no
15:08 Guest8031 https://review.openstack.org/#/c/97357/
15:08 Guest8031 https://review.openstack.org/#/c/97647/
15:08 mgagne joined #puppet-openstack
15:09 mgagne that was me ^
15:09 EmilienM in progress
15:09 hogepodge Thanks for dropping those.
15:09 EmilienM all got +2 by fungi
15:09 mdorman joined #puppet-openstack
15:10 EmilienM https://review.openstack.org/#/q/owner:bodepd%2540gmail.com+project:openstack-infra/config+status:open,n,z
15:10 hogepodge So apparently infra doesn’t like to merge new projects until Friday
15:10 mgagne hogepodge: we can poke them and ask an ETA
15:10 hogepodge Yeah, that’s a good idea. They’re usually pretty responsive
15:11 morazi joined #puppet-openstack
15:13 hogepodge I’ll try to have both projects created this week.
15:14 hogepodge We’re going to be bringing an intern who will help out the the lib project.
15:14 hogepodge Any other comments on the libraries?
15:15 spredzy Nop
15:15 hogepodge #topic specs
15:16 hogepodge It’s been a couple of weeks now, still not being used. Is this something that we should abandon? Or are we just slow getting started on it since it’s early in the cycle?
15:17 spredzy hogepodge, I've use it last week, I know the template is a template and doesn
15:17 EmilienM hogepodge: I think it's not much used because there is not much features currently. Except the lib stuff
15:17 spredzy 't need to be fully followed. But the process of feeling a blueprint takes quite some time
15:17 mgagne hogepodge: people are busy doing their day job, well, that's my case. And I don't expect 35 specs to be created during this cycle.
15:17 EmilienM I don't want to abandon this process.
15:17 EmilienM mgagne: yes, they only should been used for real design
15:18 mgagne EmilienM: ^
15:18 EmilienM like the one you created
15:18 hogepodge Ok, just wanted to check in with it. Leave it in place and encourage use based on the criteria from a few weeks ago?
15:18 mgagne for reference: https://review.openstack.org/#/q/status:open+project:stackforge/puppet-openstack-specs,n,z
15:20 hogepodge Happy to move on if there isn’t more comment.
15:20 hogepodge #topic rspec
15:21 hogepodge I think that Clayton has a good point about rspec in the mailing list.
15:21 mgagne hogepodge: care to link or summarize?
15:22 hogepodge on master we should pin to <= 2.99 until puppet-rspec-helper is fully compatible with 3
15:22 dvorak mgagne: short version is puppet-rspec works w/rspec 3, but doesn't support it, so it generates hundreds's of deprecation warnings
15:22 hogepodge https://groups.google.com/a/puppetlabs.com/d/msg/puppet-openstack/rYNeH-eemXA/BWAs2t2iJlUJ
15:22 Hunner rspec-puppet*
15:22 dvorak so I proposed we pin to <2.99
15:22 Hunner rspec-puppet implements matchers that are not rspec 3 compliant, so raises deprecation warnings when they're used on a module
15:22 hogepodge stable/icehouse should be pinned permanently, since it’s a stable branch
15:23 sbadia +1
15:23 dvorak at least until rspec-puppet moves to using the new matchers
15:23 Hunner The problem is that rspec-puppet would then become *only* rspec 3 compatible when they're fixed, but such is forward movement
15:23 sbadia (already the case for puppet-neutron)
15:23 sbadia (hi, sorry)
15:23 dvorak this will require reverting some changes for puppet-neutron
15:23 hogepodge The changes are pretty minor. Just a few truthy/falsey statements
15:23 Hunner rspec 2.99 should work with any rspec 3.0 syntax, so it may not actually need reverting, no?
15:24 mgagne when will rspec-puppet be 100% rspec 3 compatible?
15:24 dvorak Hunner: I was suggesting moving to < 2.99, to avoid the deprecation warnings
15:24 Hunner ah, so not even <=
15:24 dvorak yes.
15:25 Hunner Do dep warnings fail gates? And is that on stable, or masterand stable?
15:25 dvorak I'm all for moving to rspec 3, since it looks fairly easy, but I don't think it makes sense until rspec-puppet is updated
15:25 mgagne Hunner: afaik, 2.99 introduced a bunch of deprecation warnings to ease migration to 3
15:25 sbadia dvorak: for stable and living branch?
15:25 dvorak Hunner: it doesn't fail, it's just super spammy
15:25 dvorak yes
15:25 hogepodge deprecations will eventually turn into failures
15:25 Hunner I can see pinning stable to <2.99, but master probably shouldn't
15:26 mgagne Hunner: why not?
15:26 dvorak hogepodge: yes, but when that happens rspec-puppet won't work either.
15:26 dvorak Hunner: my concern is that it generates lots of output and it's much more difficult to find real errors in the output than it should be.
15:26 hogepodge +1 on stable < 2.99
15:27 Hunner If we pin master to ~>2.99, people can write rspec 3 specs and then we'll be ready to unpin (or pin ~> 3.0) when rspec-puppet is fixed
15:27 mgagne we should pin until upstream fully support 3
15:27 Hunner spammy warnings aside
15:27 mgagne no time to waste trying to support 3 until then
15:28 Hunner (just in case anyone is wondering, PL doesn't own rspec-puppet so can't hurry this along)
15:28 Hunner We could probably ask rodjek what his plans are :)
15:28 Hunner mgagne: Is puppet-neutron already rspec 3? (asking because of dvorak's comment above)
15:29 mgagne Hunner: there was only 1 error, rest is a handful of deprecation warnings
15:29 dvorak Hunner: a handful boolean checks have been changed from "be_false" to "be_falsey"
15:29 hogepodge neutron was patched to use 3 syntax. I think nova was also.
15:29 Hunner so meh, either way for master, but +1 <2.99 for stable
15:29 sbadia i've changed that yep
15:30 sbadia the only review missing is on puppet-openstack
15:30 Hunner Maybe nova/neutron could be ~>2.99, and the other masters be <2.99?
15:30 sbadia ( https://review.openstack.org/97567 )
15:30 mgagne Hunner: we shouldn't add inconsistency across our modules
15:31 hogepodge I prefer consistency.
15:31 Hunner I don't mind spammy, then :)
15:31 hogepodge I do mind potentially breaky
15:31 dvorak I think you either leave it, or change master to <2.99.  if you do <~ 2.99 then you have to make a change, still get spammy results and have to make another chnage to go to 3
15:32 dvorak and the 3 compatibility issues have been pretty much resolved
15:32 Hunner <2.99 and revert nova/neutron, then?
15:32 mgagne rspec-puppet does not officially support rspec 3. rspec-puppet is wrong in assuming 3 would be ok to install.
15:32 dvorak I'd say someone should talk to rodjek and put if he's not planning to update to rspec 3 soonish then we do that.
15:33 dvorak I'm fine with moving to rspec 3, but I don't think we should until rspec-puppet does.
15:33 mgagne dvorak: ^
15:33 Hunner https://github.com/rodjek/rspec-puppet/pull/204 is the r-p rspec 3 PR
15:33 mgagne Unless it merges today or tomorrow, I wouldn't hold my breath
15:34 dvorak i see no comments from rodjek in there :)
15:34 Hunner He's not easy to get a hold of sometimes. Should we just do <2.99 reviews and see if he responds before they get merged?
15:34 dvorak works for me
15:34 xingchao +1 for <2.99
15:34 hogepodge My gut feeling is to pin to < 2.99 to keep the noise down, and move ahead when we have a fully supported toolchain.
15:34 mgagne we should pin to < 2.99 like rspec-puppet should have done
15:35 mgagne allowing any major versions to be installed is a recipe for disaster
15:35 mgagne we praise ourselves with symver but people don't care when creating Gemfile
15:35 hogepodge Any objections to that?
15:35 Hunner nope, +1
15:36 mgagne +1
15:36 sbadia +1 also
15:36 xingchao +1
15:36 EmilienM +1
15:36 dvorak hogepodge: related, I've already submitte (and had merged) a change to lock all the major gems we use on stable/icehouse for neutron
15:36 xarses +1
15:36 daneyon joined #puppet-openstack
15:36 hogepodge great, thanks dvorak. Want to do the others too?
15:37 sbadia https://github.com/stackforge/puppet-neutron/commit/55ef5b5d8f9e53149c0551e96a53beae615ccac3
15:37 dvorak that was the plan, I just thought we should agree that's what we wanted to do with everything.  I also have a review open to do the same for havana.  I didn't see much point going back further than havana
15:37 hogepodge +1 on that dvorak
15:38 dvorak I did it for neutron because it was breaking a review I had submitted
15:38 hogepodge move on now?
15:38 dvorak wfm
15:39 hogepodge #topic namespace
15:39 hogepodge I can write something up for the mailing list for larger discussion.
15:39 hogepodge After reading over some IRC logs, I think that having puppetlabs release the modules under our namespace is confusing to people. It also doesn’t reflect the proportional contributions.
15:40 hogepodge I grabbed the stackforge name on Puppet Forge.
15:40 hogepodge I’m happy to continue doing the release management, but wonder if we want to keep having Puppet Labs release the modules or release them as Stackforge modules.
15:41 hogepodge No decision needs to be made, just throwing an idea out there.
15:42 mgagne hogepodge: I would like puppetlabs' plans to be made clear regarding openstack as I see 2 "competing" efforts under the same umbrella
15:42 hogepodge mgagne My intention has been to replace puppet-openstack with the module I’ve been working on, but others are still depending on the original so I haven’t pulled that rug out yet
15:43 hogepodge I also don’t want to do the replacement if it isn’t supported by the community.
15:43 xingchao hogepodge: do you mean puppetlabs-openstack ?
15:43 mgagne hogepodge: what I found unfortunate is that this replacement has been developed "in a corner" outside the puppet-openstack group and used to replace the "old" solution
15:43 Hunner People always have questions and problems with puppet-openstack... someone should rewrite it, and hogepodge basically did that with puppetlabs-openstack (or stackforge-openstack, as it may be called)
15:44 hogepodge mgagne yes, I’m not insensitive to that.
15:44 mgagne Hunner: now this would confuse me more
15:45 Hunner :PU
15:45 mgagne Hunner: if hogepodge's module was renamed to stackforge-openstack
15:45 Hunner s/U//
15:45 Hunner Ignore me about that... I'm not as clueful
15:45 mgagne Hunner: we contributed nothing to the module and it's not even hosted on stackforge
15:45 Hunner Perhaps we're getting off the track of the topic, and puppet-openstack should be the next topic?
15:46 hogepodge I think it’s related to the topic.
15:46 Hunner okay
15:46 hogepodge I recognize the confusion it’s created, and let me be clear about my intentions.
15:46 EmilienM everybody has another setup, I'm not sure a lot of people could really use this module. mgagne has his own, we (eNovance) have ours, etc.
15:47 hogepodge * I needed to understand the modules
15:47 hogepodge * I needed to test the modules
15:47 hogepodge * I also needed a development platform for them
15:47 hogepodge * I also wanted to make somthing others could use and learn from.
15:47 mgagne EmilienM: people reading puppetlabs PR would use it, those people are not all devs, they want a ready-made solution, there is a market for it
15:47 hogepodge * Possibly write documentation from it
15:48 hogepodge Some of those intentions were selfish for me, so I developed it in a corner. However, I’m happy to let this be a public effort and move that into the public realm. I don’t want to force it out there, though
15:48 mgagne hogepodge: in fact, I'm glad this module is made available, I'm just confused around the intention around it and how puppet-openstack group fits into the plan.
15:49 Hunner Does puppet-openstack need a rewrite? If so, should we start with a blueprint?
15:49 michchap there is no way I can move to it without it being roughly comparable feature wise with what emilien and myself have built.
15:49 hogepodge Now, I think the module meets a need and has potential to be a robust installer along the lines of what others are working on (HA, etc).
15:49 Hunner michchap: I think it's for new people who want it to "just work" is what he's saying
15:49 michchap and that means it needs to be both easy to understand and compose/decompose, and able to deploy a real cloud.
15:50 EmilienM michchap: because our module is not for dev, but for production
15:50 michchap I don't see why there should be two separate modules for dev and for prod.
15:51 xarses michchap: +1
15:51 EmilienM michchap: there is not, but I'm saying that's the case for now for these modules
15:51 hogepodge Internally we’re going to use my module for prod.
15:51 michchap right
15:51 EmilienM some of them are not for prod
15:51 hogepodge But I review patches against my module too.
15:51 michchap hogepodge: but it doesn't have any HA capabilities does it? That's pretty much a non-starter for everyone I've spoken to.
15:52 mgagne EmilienM: which one isn't for prod?
15:52 hogepodge No, it doesn’t. By November it will.
15:52 EmilienM mgagne: puppet-openstack, & co
15:52 EmilienM mgagne: and also the one from Chris
15:52 mgagne EmilienM: I don't see why Chris' one couldn't be used in production in a private cloud
15:52 EmilienM I'm not saying it's not a good module, he looks very nice, but it miss features for prod
15:53 EmilienM mgagne: ok maybe it's off-topic
15:53 mgagne right, lets move on
15:53 francois_ hi there, sorry for jumping in the discussion
15:53 hogepodge This is why I’m talking about making it clear that the modules are a Stackforge project, not a Puppet Labs project. We’re invested and committed, but also want to be clear and resepectful about the work that’s going on.
15:53 francois_ as a deployer, I would love to see this community moving towards a common composition layer
15:53 mgagne hogepodge: how about stackforge namespace? would there be a trademark issue or it it ok to use that name?
15:54 francois_ hosted on stackforge and developped just like all the other modules
15:54 dvorak it seems like if it's going to replace the stackforge one, it should at least use the extras module where it can
15:54 hogepodge mgagne I don’t have an answer for that. I’ll investigate.
15:54 mgagne hogepodge: one thing is sure, reserving puppetlabs namespace for actual modules "supported" by puppetlabs would be a better idea and reduce confusion
15:54 hogepodge mgagne yes.
15:55 mgagne hogepodge: because
15:55 mgagne hogepodge: I could see openstack-infra wanting to use that name too for their modules
15:55 hogepodge Releasing under our namespace is a committment we’ve made. We’ll continue to do it regardless of namespace, but most of the work on those modules happens outside of PL. No one entity really controls it.
15:56 hogepodge I didn’t take the name openstack because that would be much more fraught.
15:56 mgagne hehe
15:56 mgagne how about hp for HogePodge ? :D
15:56 xingchao mgagne: :)
15:56 EmilienM ahah
15:56 sbadia ^^
15:57 hogepodge :-)
15:57 hogepodge I don’t think it’s been taken yet. You could grab it.
15:58 mgagne soon noon, what's left to be talked about?
15:58 EmilienM integration testing
15:58 hogepodge #topic integration tests
15:58 EmilienM dachary: ^
15:59 anode joined #puppet-openstack
16:00 mgagne it's noon, lunch time for me :D
16:00 EmilienM heh
16:01 michchap football time!
16:02 hogepodge Sounds like time is up.
16:02 xarses goal!??
16:02 hogepodge #topic next week
16:02 xingchao hurry up, mgagne is hungry :D
16:02 EmilienM michchap: I did not know you had a team :P
16:02 JayJ joined #puppet-openstack
16:02 hogepodge Short, I’d like to allow for time for new people to ask questions next wek.
16:02 hogepodge We talked about it at the summit, and I just wanted to promote it as such.
16:03 rmoe joined #puppet-openstack
16:03 xarses I had two items, should poke them into the ml then
16:03 hogepodge Ok, please do that. Add them to the etherpad and I’ll make sure they wind up on the agenda too.
16:03 EmilienM xarses: you can still poke them here also
16:03 terryw joined #puppet-openstack
16:03 xarses 1) HA mixins such as corosync/pacemaker OCF scripts and cs_resource definitions for services, where should they live? They appear to be out of scope for living in the modules, is there an existing project where they would belong?
16:03 xarses 2) puppet-neutron: fuel has a function to create predefined networks, this appears to be useful to put back upstream, although I'm not sure about it being a ruby resource. Thoughts? (https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/neutron/lib/puppet/parser/functions/create_predefined_networks_and_routers.rb)
16:04 dvorak extras?
16:04 EmilienM xarses: 2) puppet-neutron already does it. Look at providers
16:04 EmilienM 1) IMO they should live in library or something
16:04 hogepodge I would think extras
16:05 xarses EmilienM: from what i could see is that If I wanted to consume the providers this way, I'd still need something to send in the data from our yaml
16:06 xingchao xarses:   1) it would be in extras module
16:06 EmilienM xingchao: +1
16:06 xarses 2) would be passed data like http://paste.openstack.org/show/84187/
16:06 marun joined #puppet-openstack
16:08 hogepodge I need to step out.
16:09 hogepodge Thanks everyone.
16:09 hogepodge #end
16:09 xingchao hogepodge: byebye
16:10 sbadia thanks!
16:18 csschwe joined #puppet-openstack
16:23 dachary1 joined #puppet-openstack
16:28 photocyte joined #puppet-openstack
16:41 mfisch anyone had an issue with keystone user-roles?
16:41 mfisch It creates my user and my tenant, but fails on the user-role
16:41 mfisch In the failure it's trying to pass in a blank user-id
16:43 mfisch I bet this is a default tenant issue
16:45 mdorman this sounds familiar
16:45 mfisch yeah, I know it does, but I can't remember what the issue was
16:45 mfisch I think I had this 6 months ago
16:45 mdorman i had/have a problem like that where it won’t create the user-role unles the user was already assigned to at least one role on that tenant
16:45 mfisch It looks like the ruby is doing a user-list and specifcying the tenant
16:46 mdorman sounds like the same thing
16:46 mfisch mdorman: yes!
16:46 mfisch mdorman: because user-list --tenant-id foo is blank
16:46 mdorman i think i got around it by just manually creating one.  always meant to go backand fix it for real and PR
16:46 mdorman yeah taht sounds right
16:46 mfisch maybe I'll do that and file a bug
16:46 guimaluf joined #puppet-openstack
16:47 mdorman pretty soon here i’m gonna pull in all the latest stuff when we got to icehouse.  what we hvae now is mostly several months ol,d too
16:47 mfisch we're on I for this issue
16:47 mfisch I mean this issue is still in I
16:47 mdorman i see
16:50 mdorman in any case, would be good to fix that
16:50 mfisch mdorman: I'll have an update in the bug, I have a work around'
16:51 mdorman cool
16:55 mfisch dvorak & mdorman: https://bugs.launchpad.net/puppet-keystone/+bug/1330550
16:59 aimon_ joined #puppet-openstack
17:00 mfisch that default tenant thing was a huge pain when we did AD for service accounts
17:04 mdorman iirc that’s where it came up for us, too, b/c we have service accounts in AD also
17:19 sputnik13 joined #puppet-openstack
17:29 bitblt joined #puppet-openstack
17:30 openstackgerrit A change was merged to stackforge/puppet-neutron: stop puppet from breaking neutron  https://review.openstack.org/100042
17:34 mmaglana joined #puppet-openstack
17:54 anode joined #puppet-openstack
18:11 StarBeast joined #puppet-openstack
18:20 hogepodge “stop puppet from breaking neutron” seems a bit hyperbolic as a commit message.
18:27 EmilienM yes :)
18:28 JayJ__ joined #puppet-openstack
18:29 mgagne michchap: sleeping?
18:30 EmilienM football watching I would say :)
18:31 mgagne he should be careful to not die =) https://uk.eurosport.yahoo.com/blogs/the-rio-report/chinese-fan-dies-staying-watch-world-cup-095517534.html
18:33 EmilienM mgagne: wow, weird :(
18:41 mgagne I found out that I'm still using this patch in production: https://review.openstack.org/#/c/78333
18:42 mgagne it's abandoned and I'm not sure if it got fixed somewhere else instead
18:48 exed_ joined #puppet-openstack
18:48 EmilienM mgagne: yes
18:48 EmilienM mgagne: 9f7fe1827348d69a6d8b62c0a334612064cca554
18:49 EmilienM mgagne: https://github.com/enovance/puppet-keystone/commit/9f7fe1827348d69a6d8b62c0a334612064cca554
18:54 mgagne EmilienM: wow, didn't find it
18:55 EmilienM mgagne: git log <file>
18:57 mgagne EmilienM: in gerrit
18:57 mgagne EmilienM: it's not the same change
18:58 mgagne EmilienM: michchap is about tenant, mine is about user
18:58 EmilienM mgagne: oops, my bad
18:58 EmilienM mgagne: so it's abandoned
18:58 mgagne EmilienM: yep
18:58 EmilienM mgagne: is it working for you?
18:58 EmilienM (I guess if it's running in prod)
18:58 mgagne EmilienM: yep, been in prod since
18:58 EmilienM cool
19:03 tfz joined #puppet-openstack
19:22 JayJ___ joined #puppet-openstack
19:27 starmer joined #puppet-openstack
19:27 larsks joined #puppet-openstack
19:42 EmilienM mgagne: have you already face the bug in puppet-keystone with "secret" parameter?
19:42 EmilienM like Invalid parameter secret at /etc/puppet/modules/keystone/manifests/init.pp:353
19:59 anode joined #puppet-openstack
20:12 aldavud joined #puppet-openstack
20:12 aldavud_ joined #puppet-openstack
20:21 StarBeast joined #puppet-openstack
20:21 mgagne EmilienM: no
20:22 mgagne EmilienM: make sure you restart the puppetmaster
20:22 EmilienM mgagne: new version of the module, running passenger, I had to restart paache2
20:22 EmilienM yeah
20:22 EmilienM weird
20:22 mgagne EmilienM: same problem as the change I proposed and got abandonned
20:22 mgagne EmilienM: you need to restart the puppetmaster or something so the new type/provider is detected
20:22 EmilienM ok
20:23 EmilienM i see thanks
20:26 mjblack joined #puppet-openstack
20:37 xarses any one good with corosync?
20:39 xarses i have cs_shadow -> cs_resource -> cs_commit -> service and cs_resource -> cs_colocation - > cs_order -> Service. Does it matter that colocation and order may possibly run before the commit?
20:54 EmilienM xarses: you should try manually but I think that's ok
21:01 dachary1 mgagne: ping ?
21:03 mgagne dachary: hi
21:04 dachary1 sorry to bother you, I was wondering if you had a chance to consider our request regarding David G. ?
22:03 daneyon joined #puppet-openstack
22:08 anode joined #puppet-openstack
22:13 sputnik13 joined #puppet-openstack
22:38 mgagne dachary: oh, I thought you were an admin of the admin already
22:42 mgagne dachary: I think I'm no longer admin of the puppet-ceph-core group on gerrit
22:43 mgagne dachary: you should be able to add him yourself
22:43 mgagne dachary: https://review.openstack.org/#/admin/groups/uuid-40a09ba10a57b052db58d1afe9b174d684f609b2,members
22:43 mgagne dachary: I made you an admin of the launchpad project too
22:45 mgagne anyone having ordering issues with nova group and user creation?
22:46 mgagne http://paste.openstack.org/show/84229/
22:54 openstackgerrit Ivan Chavero proposed a change to stackforge/puppet-vswitch: Fixes bridge interface name check  https://review.openstack.org/100377
23:05 mgagne I'm not sure how people are installing nova with puppet-nova in icehouse :-/
23:11 aldavud joined #puppet-openstack
23:12 mmaglana joined #puppet-openstack
23:12 aldavud_ joined #puppet-openstack
23:16 sputnik13 joined #puppet-openstack
23:23 mgagne ok, my issue got fixed in puppet 3.2.0: https://github.com/puppetlabs/puppet/commit/d0cd32bac64fe1efbe902e20cc07eac9f3b919b8#diff-f5b9cc80dd02278d845d220721ac0217
23:23 mgagne this goes to show that although unit tests are passing fine, integration tests would have caught this puppet bug
23:33 mgagne michchap: ping
23:47 xarses joined #puppet-openstack
23:53 sputnik13 joined #puppet-openstack

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