Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2014-07-02

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

All times shown according to UTC.

Time Nick Message
00:39 daneyon joined #puppet-openstack
01:01 openstackgerrit Spencer Krum proposed a change to stackforge/puppet-nova: Initial rspec-beaker testing scaffolding  https://review.openstack.org/102020
01:03 nibalizer Hunner: thanks for the 2cents
01:04 gildub joined #puppet-openstack
01:28 xarses joined #puppet-openstack
01:47 gildub joined #puppet-openstack
01:57 StarBeas_ joined #puppet-openstack
02:11 djm68 joined #puppet-openstack
02:49 openstackgerrit A change was merged to stackforge/puppet-neutron: Configure OVS Agent when using ML2 plugin  https://review.openstack.org/102054
05:49 tfz joined #puppet-openstack
06:02 EmilienM good morning
06:12 ddmitriev joined #puppet-openstack
06:41 aldavud joined #puppet-openstack
07:02 gcha joined #puppet-openstack
07:03 artem_panchenko joined #puppet-openstack
07:14 imcsk8 joined #puppet-openstack
07:51 EmilienM sbadia: https://etherpad.openstack.org/p/sprint-juno-paris-puppet
07:53 sbadia morning
07:53 sbadia EmilienM: thx
07:56 aldavud joined #puppet-openstack
08:11 gcha joined #puppet-openstack
08:25 mmagr joined #puppet-openstack
08:39 qba73 joined #puppet-openstack
08:41 derekh_ joined #puppet-openstack
09:54 qba73 joined #puppet-openstack
10:20 qba73_ joined #puppet-openstack
11:36 arnaud_orange joined #puppet-openstack
11:40 mkoderer joined #puppet-openstack
11:48 arnaud_orange left #puppet-openstack
11:58 morazi joined #puppet-openstack
12:27 djm68 joined #puppet-openstack
12:44 dprince joined #puppet-openstack
13:15 morazi joined #puppet-openstack
13:35 prad joined #puppet-openstack
13:41 saju_m joined #puppet-openstack
13:42 saju_m Hi friends,
13:42 saju_m How to invoke the classes of puppet module "heat" ? What is the order ?  I tried this http://dpaste.com/1V4YN00   , but not working .
13:42 saju_m i invoked the class "heat" in the init.pp,  https://github.com/stackforge/puppet-heat/blob/master/manifests/init.pp
13:43 saju_m but that did't install any heat services
13:43 EmilienM saju_m: you should not specify order, it's up to puppet-heat to manage it
13:45 saju_m EmilienM, I need to call the calls "heat:engine" defined in the https://github.com/stackforge/puppet-heat/blob/master/manifests/engine.pp  to install heat engine, right ?
13:46 EmilienM saju_m: yes
13:46 saju_m EmilienM, I removed the order http://dpaste.com/2N9JB9W
13:47 saju_m EmilienM, again getting same error Error: Could not find dependency Exec[heat-dbsync] for Service[heat-engine] at /var/puppet/modules/heat/manifests/engine.pp:72
13:47 EmilienM saju_m: look at how we do: https://github.com/enovance/puppet-openstack-cloud/tree/master/manifests/orchestration
13:51 saju_m EmilienM,  that github code using "puppetlabs/heat" module, right ?
13:52 EmilienM saju_m: yes
13:53 saju_m EmilienM,  starting point is https://github.com/enovance/puppet-openstack-cloud/blob/master/manifests/orchestration.pp
13:53 saju_m EmilienM, right ?
13:54 EmilienM right
14:10 rwsu joined #puppet-openstack
14:10 arnaud_orange joined #puppet-openstack
14:19 saju_m EmilienM, I am not getting why the class "heat::engine" defined in the https://github.com/stackforge/puppet-heat/blob/master/manifests/engine.pp can't find the exec resource "heat-dbsync" defined in the https://github.com/stackforge/puppet-heat/blob/master/manifests/init.pp
14:20 saju_m EmilienM, Iam invoking the class 'heat::engine'  only after '::heat'
14:26 saju_m EmilienM, I am using Puppet 3.6.2, that is ok , right ?
14:34 prad joined #puppet-openstack
14:47 daneyon joined #puppet-openstack
14:48 daneyon joined #puppet-openstack
15:01 saju_m joined #puppet-openstack
15:15 djm68 joined #puppet-openstack
15:44 aimon joined #puppet-openstack
15:44 EmilienM sbadia: I'm preparing the patch to move the module into stackforge
15:45 boblebauce joined #puppet-openstack
15:45 sbadia EmilienM: humm not yet, no?
15:45 sbadia the module isn't ready
15:45 EmilienM sbadia: yeah, but it takes time to have eyes on it
15:46 sbadia oki =)
15:50 giorgiodinapoli joined #puppet-openstack
15:51 xrsa joined #puppet-openstack
15:51 hogepodge giorgiodinapoli which system are you running on? RH-like or Ubuntu?
15:51 giorgiodinapoli hogepodge, hi!
15:51 giorgiodinapoli i try atm ubunt 12.04
15:52 giorgiodinapoli hogepodge, i prepared everything and created a snapshot. i wanted to try the allinone. but always when it comes to: Notice: /Stage[main]/Neutron::Agents::Ovs/Vs_bridge[br-int]/ensure: created , network breaks
15:52 aldavud joined #puppet-openstack
15:52 hogepodge Hi, ok. That’s not surprising. The vswitch code is not very robust, and in general 12.04 is not a good platform for Icehouse.
15:53 giorgiodinapoli hogepodge, ok! thats a good info :) so what do you suggest? RTH?
15:53 hogepodge It requires a backported kernel to work, and I haven’t managed to get Icehouse deployed on 12.04. I have on 14.04, though.
15:54 giorgiodinapoli hogepodge, okay! so tell me shall i go for 14.04 or RH. Since i come from debian world, i was choosing with a littl bit dying ubuntu
15:54 hogepodge What’s your development environment? Are you using Vagrant? If so, with which hypervisor?
15:54 hogepodge I’m always happy to have more eyes on 14.04, I really need to make sure the vswitch code is robust enough for it.
15:55 giorgiodinapoli hogepodge, i have a plain i7 machine with  enought 32GB Ram, 3 TB HD and 2 NIC, im tryied already a lot KVM QEM, XEN (Before testing the puppet module)
15:56 giorgiodinapoli hogepodge, i even had it running once but only more or less. my goal was now to get a puppet configuration where i can automatically get it done for our testsystem
15:56 giorgiodinapoli hogepodge, to me more specific:
15:57 giorgiodinapoli hogepodge, i will install now 14.04 server. then i will install puppet (latest with hiera)
15:57 giorgiodinapoli hogepodge, can i use only 1 nic and set all ips to the same subnet?
15:57 hogepodge Ok. Let me know how it goes.
15:58 giorgiodinapoli hogepodge, shall i use this specific version: http://www.ubuntu.com/download/cloud
15:58 hogepodge It’s pretty strongly opinionated about having an internal and external network. I haven’t tested with only one. It should work, but could run into some firewall versions.
15:58 hogepodge That will probably work. I just use a stock 14.04 and connect it to the UCS repository.
15:59 giorgiodinapoli hogepodge, okay i use a stock too then and use the UCS. if i wanna setup allinone, how would it be with 2 nics then?
15:59 daneyon_ joined #puppet-openstack
16:00 hogepodge api and external are on the same network, data and admin are also on the same network.
16:01 giorgiodinapoli hogepodge, if i remove the "hard firewall rule" that diseables all traffic, will it be good then?
16:01 giorgiodinapoli hogepodge, what is about the Vs_bridge[br-int]/ensure: created <-- will this problem be solved in 14.04
16:01 hogepodge Probably.
16:02 giorgiodinapoli since this breaks my complete network configration
16:02 giorgiodinapoli even ssh will be dead after this
16:02 hogepodge In my test run the bridge problem was fixed, and was created without trouble. One of the issues is if puppet is running over the network that gets moved to the bridge, it breaks the run
16:02 hogepodge Right, and you’ll lose ssh
16:03 mtl1 Hi, quick question about https://github.com/stackforge/puppet-ceilometer  Does anyone have any info on what needs to be in place on the controller nodes and on the compute nodes for that to work? I'm having trouble figuring that out by digging through the module.
16:03 hogepodge It might be worthwhile to set the bridge up manually. It’s a problem I need to work on, and see if it can be resolved. That external bridge needs to be there, but changing networking out from underneath yourself can always lead to problems.
16:04 hogepodge mtl1 I think you need the ceilometer configuration and the agents
16:05 giorgiodinapoli hogepodge, i will install it from local "master" via puppet apply site.pp. can i remove the bridge and add it manually afterwards?
16:05 giorgiodinapoli or what do you suggest to get arround this issue
16:06 hogepodge I don’t know. I need to investigate. If the bridge is set up properly with the ip address even if you lose ssh you should be able to log back in.
16:07 giorgiodinapoli so i will configure my second nic even not connected to anything with a diffrent subnet. so the bridge can be connected, will this be the solution you suggest me?
16:08 mtl1 hogepodge: Thanks. I think I already have the controller part right. When I try to include ceilometer::agent::compute on a compute node though, it's still trying to install everything like it's a controller node.
16:10 hogepodge I don’t know. 14.04 and network is not my strength. It works differenlty than from RH, so my suggestions for setting it up may be wrong.
16:10 giorgiodinapoli hogepodge, but how do you do it, so it works without breaking the connection?
16:11 hogepodge I do the puppet run through a different network.
16:11 giorgiodinapoli i can do it from local console
16:11 giorgiodinapoli so ssl wont be needed
16:12 giorgiodinapoli ssh sorry
16:13 hogepodge yeah. I don’t have a better answer yet. working on vswitch ubuntu is on my task list for this week, so I’ll be getting a better grip on it.
16:17 sputnik13 joined #puppet-openstack
16:18 sputnik13 joined #puppet-openstack
16:27 daneyon joined #puppet-openstack
16:28 hogepodge EmilienM https://review.openstack.org/#/c/103676/
16:28 hogepodge I don’t want to +2/merge myself (since I have a bit of bias)
16:29 EmilienM hogepodge: done
16:29 hogepodge Thanks. I’ve been helping out with the work, so I want to make sure there’s a variety of eyes on it.
16:39 openstackgerrit A change was merged to stackforge/puppet-openstacklib: Create basic module structure with required files  https://review.openstack.org/103676
16:42 djm68 joined #puppet-openstack
16:43 djm68_ joined #puppet-openstack
16:50 aimon joined #puppet-openstack
16:51 daneyon joined #puppet-openstack
16:58 mgagne hogepodge: guess I was too late for this one but
16:58 mgagne hogepodge: https://review.openstack.org/#/c/103676/
17:00 hogepodge We can submit updates.
17:00 hogepodge mgagne ^^
17:00 guimaluf joined #puppet-openstack
17:00 mgagne hogepodge: but it looks like the other modules have the same issue, just didn't see them since the import
17:02 mgagne hogepodge: can StackForge be used for the author or should we use something else? Authorship and copyright have always been fuzzy (to me) around the puppet modules for OpenStack
17:03 AaronGr left #puppet-openstack
17:03 hogepodge It’s been a complete mess. I’ve screwed it up a bunch of times. I want to recognize the contributions of the authors and their sponsors.
17:03 hogepodge I usually say “and authors”, then point to the github contributor list. Feels a bit cheap to me, though.
17:04 xarses joined #puppet-openstack
17:05 hogepodge I have no problem with another patch going through that makes that better, though. If we can come up with something that we can all agree upon (especially where there have been multiple companies contributing original code) I want to recognize that, and the next time I do a release or module update it can just be swept through with that.
17:05 mgagne how about "StackeForge Puppet Team"
17:05 mgagne trying to dig through stackforge projects for ideas
17:06 mmaglana joined #puppet-openstack
17:06 mgagne some people are using "OpenStack" but I feel it isn't right neither
17:06 qba73 joined #puppet-openstack
17:09 mgagne don't forget to watch puppet-openstack-specs =) https://review.openstack.org/#/q/status:open+project:stackforge/puppet-openstack-specs,n,z
17:13 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-openstacklib: Fail rspec tests on warnings  https://review.openstack.org/104260
17:14 qba73 joined #puppet-openstack
17:14 openstackgerrit A change was merged to stackforge/puppet-openstack-specs: Template submitted for code review.  https://review.openstack.org/96876
17:17 qba73 joined #puppet-openstack
17:20 mgagne hogepodge: I would like to update all summaries and descriptions to make them consistant
17:20 hogepodge mgagne +1
17:21 mgagne hogepodge: yes, sometimes I wake up and wish to update the world for trivial reasons =)
17:21 mgagne hogepodge: here is the template I suggest:
17:21 mgagne summary 'Puppet module for OpenStack <program-code-name>'
17:21 mgagne description  'Install and configure <program-name> service for OpenStack (<program-code-name>).'
17:21 mgagne program-code-name: Cinder  | program-name: Block Storage
17:21 mgagne something along those lines
17:22 mgagne might add the word "the" before the program-name
17:23 hogepodge For copyright, based on previous feedback, I think it’s best to have Copyright <company who made first contribution> and Contributing Authors, then link to github contributors page.
17:24 hogepodge or Contributing Authors to the StackForge Puppet OpenStack Modules Team.
17:24 mgagne I'll leave that one for later, it isN't an easy subject
17:24 hogepodge No, definitely not easy.
17:25 mgagne hogepodge: "Install and configure the" or "Installs and configures the" ?
17:27 hogepodge The first is an imperative, “you install”, the second is a descriptive, “it installs”
17:27 mgagne the later then?
17:27 mgagne looks like the wording used to be "Puppet module to install and configure ..."
17:27 mfa298 joined #puppet-openstack
17:29 hogepodge Yeah, the ‘to’ changes it to a description.
17:30 mgagne ok, looks like program names aren't consistent across openstack projects...
17:31 mgagne "Queue service", "Block Storage", "DNS Services", etc.
17:44 djm68 joined #puppet-openstack
17:47 guimaluf joined #puppet-openstack
17:50 openstackgerrit joined #puppet-openstack
17:54 djm68 joined #puppet-openstack
17:56 saju_m joined #puppet-openstack
17:57 guimaluf joined #puppet-openstack
17:57 bodepd so vs_bridge is totally broken since a patch was merged recently
17:59 daneyon_ joined #puppet-openstack
18:00 djm68 joined #puppet-openstack
18:01 openstackgerrit Dan Bode proposed a change to stackforge/puppet-vswitch: Allow non-word characters in vs_bridge external_ids  https://review.openstack.org/104274
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-ceilometer: Make Modulefile summary and description consistent  https://review.openstack.org/104277
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-cinder: Make Modulefile summary and description consistent  https://review.openstack.org/104278
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-designate: Make Modulefile summary and description consistent  https://review.openstack.org/104279
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-glance: Make Modulefile summary and description consistent  https://review.openstack.org/104280
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-heat: Make Modulefile summary and description consistent  https://review.openstack.org/104281
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-horizon: Make Modulefile summary and description consistent  https://review.openstack.org/104282
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-ironic: Make Modulefile summary and description consistent  https://review.openstack.org/104283
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-keystone: Make Modulefile summary and description consistent  https://review.openstack.org/104284
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-neutron: Make Modulefile summary and description consistent  https://review.openstack.org/104285
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-nova: Make Modulefile summary and description consistent  https://review.openstack.org/104286
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-swift: Make Modulefile summary and description consistent  https://review.openstack.org/104287
18:05 openstackgerrit Mathieu Gagné proposed a change to stackforge/puppet-tempest: Make Modulefile summary and description consistent  https://review.openstack.org/104288
18:09 openstackgerrit Colleen Murphy proposed a change to stackforge/puppet-openstack-specs: Common OpenStack Database Resource  https://review.openstack.org/104289
18:11 openstackgerrit Dan Bode proposed a change to stackforge/puppet-vswitch: Allow non-word characters in vs_bridge external_ids  https://review.openstack.org/104274
18:14 djm68 joined #puppet-openstack
18:15 bodepd mgagne: can you take a quick look at that patch?
18:15 bodepd https://review.openstack.org/104274
18:19 bodepd mgagne: thx!
18:28 morazi joined #puppet-openstack
18:37 openstackgerrit Colleen Murphy proposed a change to stackforge/puppet-openstack-specs: Common OpenStack Database Resource  https://review.openstack.org/104289
18:39 djm68 joined #puppet-openstack
18:44 openstackgerrit A change was merged to stackforge/puppet-vswitch: Allow non-word characters in vs_bridge external_ids  https://review.openstack.org/104274
18:56 djm68 joined #puppet-openstack
19:01 blkperl mgagne: you know modulefiles were deprecated in favor of metadata.json right?
19:01 mgagne blkperl: I don't see any metadata.json in our repos =)
19:01 * blkperl can fix that
19:01 blkperl its a PITA to verify its correct though
19:01 mgagne blkperl: metadata.json includes a lot more information related to supported platforms and versions
19:01 blkperl yeah
19:02 mgagne blkperl: we would need to figure out those info first
19:02 mgagne blkperl: tbh, I don't know who though json was a good format for this file :-/
19:03 blkperl mgagne: pretty sure it was it preserve backwards compat with older puppet
19:03 mgagne blkperl: yaml would have been just fine
19:03 blkperl ya
19:04 mgagne blkperl: that didn't have yaml? yaml used to be the serialization format used between the agent and the master
19:04 blkperl the puppet module tool always looked at metadata.json
19:04 blkperl the modulefile was used to generate it
19:04 mgagne =(
19:08 bodepd blkperl: I remember back when even including a metadata.json file caused Puppet to explode
19:08 * bodepd complains about kids today and feeds the ducks
19:09 blkperl bodepd: yep :)
19:10 mgagne get off my lawn!
19:26 tfz joined #puppet-openstack
19:28 tfhartmann joined #puppet-openstack
19:34 mmaglana joined #puppet-openstack
19:39 mtl1 joined #puppet-openstack
19:41 djm68 joined #puppet-openstack
19:46 Heemps joined #puppet-openstack
20:01 djm68 joined #puppet-openstack
20:04 hogepodge mgagne bodepd “youth is wasted on the young!”
20:09 djm68 joined #puppet-openstack
20:36 aldavud joined #puppet-openstack
20:50 djm68 joined #puppet-openstack
20:54 djm68 joined #puppet-openstack
21:04 hogepodge joined #puppet-openstack
21:20 djm68 joined #puppet-openstack
21:21 mmaglana joined #puppet-openstack
21:23 mgagne how hard would it be to move away from direct dependency declarations on resources such as package/service to class based relations?
21:23 mgagne hogepodge: ^ I'm thinking about puppet-neutron use cases
21:24 mgagne hogepodge: where some distro do not provide packages for each plugins but instead wrap everything in the neutron-server package
21:24 mgagne hogepodge: so you end up with weird logic and potential duplicated resources if you are not careful
21:25 hogepodge mgagne So being more generic? using anchors?
21:25 mgagne hogepodge: yes, if needed
21:25 mgagne hogepodge: one example: https://github.com/stackforge/puppet-neutron/blob/master/manifests/agents/ml2/ovs.pp#L203-L207
21:25 hogepodge Can you paste a basic example?
21:25 hogepodge jinx
21:26 mgagne hogepodge: if you install the agent on the server, you could end up with duplicated resources
21:26 hogepodge yes. I’ve hit that for allinone
21:26 mgagne hogepodge: even though the resource title is different, you still end up with 2 resources managing the neutron-ovs-server package
21:26 mgagne hogepodge: in the original patch, the idea was to install the neutron-server too if you were on a redhat platform
21:26 openstackgerrit A change was merged to stackforge/puppet-ceph: incorrect cloudwatt.com email and (C) of Copyright was missing  https://review.openstack.org/102901
21:27 mgagne hogepodge: but people forgot
21:30 mgagne hogepodge: https://review.openstack.org/#/c/27571/ May 10, 2013
21:32 hogepodge I’m in a meeting right now, so it’s hard to give it the attention it deserves.
21:32 daneyon joined #puppet-openstack
21:34 djm68 joined #puppet-openstack
21:36 mgagne hogepodge: ok, we will check tomorrow, I'm leaving soon, have a good one
21:37 hogepodge :-P
21:37 hogepodge I’m booked up until late too. Meetings, trail running race, then party.
22:01 djm68 joined #puppet-openstack
22:05 mmaglana joined #puppet-openstack
22:06 djm68 joined #puppet-openstack
22:09 aldavud joined #puppet-openstack
22:12 Underyx|off joined #puppet-openstack
22:12 djm68 joined #puppet-openstack
22:14 djm68_ joined #puppet-openstack
22:16 dvorak mgagne: another alternative would be to start tagging services and packages.  I think that would be useful for other things also, like easily ensuring that repos were in place before packages were installed, without having an upstream repo be a dependency for *all* packages
22:16 morazi joined #puppet-openstack
23:02 kaiserpathos joined #puppet-openstack
23:04 djm68 joined #puppet-openstack
23:49 mgagne dvorak: that could be a nice idea
23:56 gildub joined #puppet-openstack

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