Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2015-01-09

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

All times shown according to UTC.

Time Nick Message
00:14 markvoelker joined #puppet-openstack
00:43 markvoelker joined #puppet-openstack
00:51 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Test keystone_user password with curl  https://review.openstack.org/145986
00:52 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Add timeout to API requests  https://review.openstack.org/145987
00:52 crinkle EmilienM|afk: richm ^
00:53 crinkle the second one resolves an issue I was running into while debugging the first one >.<
01:18 mfisch crinkle: reviewed your keystone stuff, thanks for the service wait stuff thats really super annoying to have happen in the middle of a > 100 machine deployment
01:29 badiane_ka joined #puppet-openstack
01:33 rmoe joined #puppet-openstack
01:33 richm crinkle: ugh - is there no other command we can use to check the password?
01:35 crinkle richm: not that i could find, non-admin users can't do any keystone-related commands
01:36 richm ok
01:36 crinkle was hoping i could make it try to list tenants or roles or something :(
01:36 richm note that this introduces another dependency on curl
01:37 richm perhaps it would be better to just use the http requests module directly?
01:37 crinkle oh hrm
01:37 richm see https://review.openstack.org/133601
01:37 crinkle okay i can look at that when i get back to a computer
01:42 dprince joined #puppet-openstack
02:14 xarses joined #puppet-openstack
02:32 michchap joined #puppet-openstack
02:34 spyglass joined #puppet-openstack
02:36 spyglass is there an easy way of running horizon with https using the openstack module?
02:51 michchap This isn't exactly what you asked for, but I use the haproxy module in front of the horizon module and do SSL termination there.
02:52 michchap You can turn on SSL in apache via options in the horizon module if that's more what you're looking for: https://github.com/stackforge/puppet-hor​izon/blob/master/manifests/init.pp#L131
04:26 EmilienM|afk crinkle: ack
04:27 markvoelker joined #puppet-openstack
04:29 saju_m joined #puppet-openstack
04:35 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Test keystone_user password with Net::HTTP  https://review.openstack.org/145986
04:36 openstackgerrit Colleen Murphy proposed stackforge/puppet-keystone: Add timeout to API requests  https://review.openstack.org/145987
05:06 sanjayu joined #puppet-openstack
05:08 fedexo joined #puppet-openstack
05:08 fedexo_ joined #puppet-openstack
05:16 saju_m joined #puppet-openstack
05:27 markvoelker joined #puppet-openstack
06:32 michchap joined #puppet-openstack
07:08 markvoelker joined #puppet-openstack
07:27 berendt joined #puppet-openstack
07:48 stamak joined #puppet-openstack
08:10 markvoelker joined #puppet-openstack
08:37 michchap joined #puppet-openstack
08:39 dgurtner joined #puppet-openstack
08:39 dgurtner joined #puppet-openstack
08:47 jpena joined #puppet-openstack
08:57 dalgaaf joined #puppet-openstack
08:58 arnaud_orange joined #puppet-openstack
08:59 tfz joined #puppet-openstack
09:05 jistr joined #puppet-openstack
09:10 markvoelker joined #puppet-openstack
09:15 berendt joined #puppet-openstack
09:22 derekh joined #puppet-openstack
09:28 qba73 joined #puppet-openstack
09:33 spyglass joined #puppet-openstack
09:34 spyglass when installing the puppetlabs-openstack "network" role I'm getting an error - Error: Could not prefetch neutron_network provider 'neutron': Execution of '/usr/bin/neutron net-list --format=csv --column=id --quote=none' returned 1: Connection to neutron failed: Maximum attempts reached
09:36 spyglass it doesn't seem like authentication params are used.  are these supposed to be grabbed from the ENV?
09:37 michchap joined #puppet-openstack
09:40 berendt joined #puppet-openstack
09:41 mmagr joined #puppet-openstack
11:02 rcallawa_ joined #puppet-openstack
11:12 markvoelker joined #puppet-openstack
11:18 rcallawa joined #puppet-openstack
11:37 michchap joined #puppet-openstack
12:07 EmilienM Good morning!
12:10 social moin
12:14 markvoelker joined #puppet-openstack
12:38 michchap joined #puppet-openstack
12:54 kbyrne joined #puppet-openstack
13:14 markvoelker joined #puppet-openstack
13:21 dprince joined #puppet-openstack
13:23 djm68 joined #puppet-openstack
13:30 rcallawa joined #puppet-openstack
13:38 michchap joined #puppet-openstack
14:11 morazi joined #puppet-openstack
14:19 openstackgerrit Lukas Bezdicka proposed stackforge/puppet-nova: Add support for nova Pci passthrough  https://review.openstack.org/145787
14:19 richm joined #puppet-openstack
14:20 social EmilienM: ^^
14:24 EmilienM social: will look !
14:35 beddari spredzy: https://github.com/Mylezeem/puppeels/issues/5
14:38 EmilienM social: why having  pci_alias_entry.pp and pci_passthrough_whitelist_entry.pp ? Also, why aren't they consistent? Why do you have physical_network for API and not used in the define?
14:39 michchap joined #puppet-openstack
14:42 spredzy beddari, answered :)
14:52 pcaruana|afk| joined #puppet-openstack
14:52 djm68 joined #puppet-openstack
14:59 rickerc joined #puppet-openstack
15:02 rcallawa_ joined #puppet-openstack
15:04 beddari spredzy: updated with arguments ...
15:04 spredzy beddari, I read it, and after giving some though you might be right. Not everybody will have the same requirement for the base class, so making it plugable make it a safe bet
15:05 beddari :)
15:06 beddari spredzy: I'll add that to the cleanup PR ...
15:07 pradk joined #puppet-openstack
15:26 djm68 joined #puppet-openstack
15:28 social EmilienM: hmm puppet lint hates me, will look
15:29 social EmilienM: because I want pci_passthrough hash to be same for compute and api
15:29 social so you have to generate/set it only once
15:40 michchap joined #puppet-openstack
15:51 djm68 joined #puppet-openstack
15:52 rcallawa joined #puppet-openstack
16:06 openstackgerrit joined #puppet-openstack
16:07 mdorman joined #puppet-openstack
16:13 openstackgerrit Tri Hoang Vo proposed stackforge/puppet-keystone: Fix service keystone conflict when running in apache  https://review.openstack.org/127939
16:17 tfz joined #puppet-openstack
16:18 ericpeterson joined #puppet-openstack
16:20 EmilienM /qusp
16:20 EmilienM oops
16:21 vinsh joined #puppet-openstack
16:30 arnaud_orange1 joined #puppet-openstack
16:41 michchap joined #puppet-openstack
16:44 mschmitt joined #puppet-openstack
16:52 dprince EmilienM: I just pushed the latest TripleO puppet-swift patches... all of which rely on the new seed parameter patch in puppet-swift
16:53 dprince EmilienM: It is used here: https://review.openstack.org/#​/c/145809/2/puppet/ringbuilder.pp,cm
16:53 EmilienM dprince: ok, will look
16:53 dprince EmilienM: also, the storage role is finished now as well: https://review.openstack.org/#/c/146129/
16:53 rwsu joined #puppet-openstack
16:54 dprince EmilienM: for the storage role we have a Heat parameter for the 'controller ip'. I'm not sure we need that do we?
16:54 dprince EmilienM: is there some reason a storage node needs the IP of a controller?
16:54 * dprince isn't aware of any
16:55 EmilienM mhh
16:55 EmilienM good question! let me dig
16:55 EmilienM I'm not a swift expert
16:55 dprince EmilienM: me neither. I can bring this up in TripleO too. Just thought I'd ask
16:56 EmilienM dprince: where is controller_ip?
16:56 dprince EmilienM: https://review.openstack.org/#/​c/146129/1/swift-storage-puppet.yaml,cm
16:56 EmilienM ok
16:56 dprince EmilienM: see the first FIXME at the top there
16:57 dprince EmilienM: this is an interface so I have to adhere to it for now... but I'm questioning it, along with serveral other parameters as well
16:57 EmilienM where do you use it?
16:58 dprince EmilienM: I am not. That is why I was asking. I'm almost positive we don't need it
16:58 EmilienM +1
16:59 EmilienM dprince: have you read the comment of Swift PTL?
17:00 dprince EmilienM: yep. It sounds like everyone agrees that so long as you use the same seed, creating the ring on separate nodes is totally fine
17:00 dprince EmilienM: arguably not the most efficient way to do this. But until we have Heat breakpoints I think it is reasonable
17:00 EmilienM will see
17:01 dprince EmilienM: we won't regenerate rings that often... so I think it is an acceptable solution for now
17:01 * EmilienM very curious about how heat breakpoints will work
17:01 EmilienM dprince: we never you mean!
17:01 dprince EmilienM: it works. I setup a multi-node swift cluster and replication is working with these changes. (I saw .data files getting replicated)
17:01 dprince EmilienM: for now, yes. Me
17:02 EmilienM dprince: +2 on https://review.openstack.org/#/c/145941/
17:03 EmilienM dprince: off for lunch and I move to the office, ttyl
17:04 dprince EmilienM|afk: thanks
17:12 richm Can we get some more reviews for https://review.openstack.org/145986 ?  This is holding up moving to openstackclient
17:22 EmilienM|afk sbadia: can you review/approve?
17:29 rmoe joined #puppet-openstack
17:31 jistr_ joined #puppet-openstack
17:31 fvollero_ joined #puppet-openstack
17:39 fvollero joined #puppet-openstack
17:41 michchap joined #puppet-openstack
18:01 mschmitt joined #puppet-openstack
18:12 ericpete_ joined #puppet-openstack
18:18 vinsh joined #puppet-openstack
18:31 richm puppet/ruby question - how do I print the file+line of the current puppet manifest from within the ruby code of a custom type provider?  I'm trying to figure out where keystone_user and keystone_tenant are being called
18:34 crinkle I don't know of any way to do that, I wouldn't think it would be possible
18:34 crinkle richm: btw thanks for the suggestion to use Net::HTTP, makes way more sense than what I was doing
18:37 richm I can get a ruby traceback, but I'm not sure how to map that to the current puppet execution environment
18:37 richm crinkle: It just so happened that I had recently ran across some heat puppet code that did the same thing :-)
18:38 ericpeterson joined #puppet-openstack
18:42 michchap joined #puppet-openstack
18:55 markvoelker joined #puppet-openstack
18:59 xarses joined #puppet-openstack
19:10 imcsk8 joined #puppet-openstack
19:13 vinsh_ joined #puppet-openstack
19:19 mmagr joined #puppet-openstack
19:33 mschmitt joined #puppet-openstack
19:43 michchap joined #puppet-openstack
19:45 f10d4 joined #puppet-openstack
20:16 kbyrne joined #puppet-openstack
20:38 openstackgerrit Nathan Kinder proposed stackforge/puppet-keystone: Set WSGI process display-name  https://review.openstack.org/146197
20:44 michchap joined #puppet-openstack
20:49 richm with respect to ^^^ - does anyone know the bottom line earliest version of mod_wsgi we have to support?  display-name was added in mod_wsgi 2.0 - do we have to suppport mod_wsgi 1.x?
20:50 nkinder joined #puppet-openstack
20:58 djm68 joined #puppet-openstack
20:59 djm68 joined #puppet-openstack
21:18 ericpete_ joined #puppet-openstack
21:29 ericpeterson joined #puppet-openstack
21:38 vinsh joined #puppet-openstack
21:39 ericpete_ joined #puppet-openstack
21:42 badiane_ka joined #puppet-openstack
21:44 ericpeterson joined #puppet-openstack
21:44 michchap joined #puppet-openstack
21:50 ericpete_ joined #puppet-openstack
21:56 ericpeterson joined #puppet-openstack
22:02 djm68 joined #puppet-openstack
22:25 rcallawa_ joined #puppet-openstack
22:27 mdorman anybody know if there’s a fact i can reference to determine if the future parser is enabled or not?
22:29 xarses joined #puppet-openstack
22:45 michchap joined #puppet-openstack
22:55 mmagr joined #puppet-openstack
23:21 c0m0 joined #puppet-openstack
23:46 michchap joined #puppet-openstack
23:50 vinsh joined #puppet-openstack

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