Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2013-11-19

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

All times shown according to UTC.

Time Nick Message
00:04 dmsimard joined #puppet-openstack
00:18 michchap xarses: yep :)
00:23 dwt1 joined #puppet-openstack
00:27 xarses I'm looking for a method to pull // bundle // test a number of the puppet-openstack modules and some others. I need to be able to pin branches / maybe even commits. Something similar to the way fixtures.yaml works with rspec-system-puppet does. There used to be some hack in stackforge/puppet-openstack that was removed before the stable/grizzly release
00:31 mgagne xarses: you should take a look at smokestack/firestack. it checkout all puppet modules from master except the one tested where the commit is checkout instead. it is only a matter of scripting/automating the process. https://github.com/dprince/firest​ack/blob/master/tasks/puppet.rake
00:35 mgagne xarses: https://github.com/puppetlabs/rspec-system-puppet
00:35 mgagne xarses: "Replace mymodule with your module name"
00:35 mgagne xarses: I guess Rakefile should be able to access env variables to override which versions to checkout
00:35 xarses mgagne: thanks, looking
00:38 mgagne xarses: I however think puppet_module_install expects the module to be locally available first. I'm not sure if rspec-system-puppet expects you to download them beforehand, in that case, librarian-puppet might help you.
00:38 xarses hmm the rspec-system-puppet thing appears to be only geared towards testing. In the end case, I'd need to have 'bundle' of all the modules under a single tree like how they are on a normal puppet modules/ folder
00:39 mgagne xarses: this can be done at runtime using librarian-puppet
00:40 xarses mgagne: pre-package? I can't rely that the end user's system would have Internet access
00:40 openstackgerrit A change was merged to stackforge/puppet-ceph: Add more dashes to match title line length  https://review.openstack.org/56976
00:42 mgagne xarses: the end user's system? are you expecting tests to be able to run on a closed network without internet access?
00:42 xarses tests should be able to run on an open network
00:42 xarses i need to be able to build a complete repo of modules after testing for handing off to a possibly closed network
00:42 openstackgerrit A change was merged to stackforge/puppet-ceph: Change 4 space indent to 2  https://review.openstack.org/57065
00:44 mgagne xarses: librarian-puppet can still help you. I use it to bundle all modules in a tar.gz
00:44 xarses ok
00:44 mjblack joined #puppet-openstack
00:46 mgagne xarses: tbh, if you need to be able to download a bunch of modules from git (for packaging/tests purposes) and pin to specific versions, I only know librarian-puppet(-simple)
00:47 xarses mgagne: sounds good, I'll look it over, thanks for the pointers
00:47 xarses mgagne: https://github.com/rodjek/librarian-puppet ?
00:48 mgagne xarses: yes and https://github.com/bodepd/librarian-puppet-simple
00:49 openstackgerrit A change was merged to stackforge/puppet-cinder: Add Glance support  https://review.openstack.org/56302
00:49 mgagne xarses: the second one is a reimplementation made by bodepd. It tries to fix a known problem of librarian-puppet where it still downloads from forge even if you don't want.
00:53 mjblack joined #puppet-openstack
00:58 xarses mgagne: thanks again, i need to read a bit now =)
00:59 mgagne xarses: yw
01:31 xarses joined #puppet-openstack
01:38 michchap joined #puppet-openstack
01:52 mjblack joined #puppet-openstack
01:57 rmoe joined #puppet-openstack
02:11 rongze joined #puppet-openstack
02:14 mjblack joined #puppet-openstack
02:46 _ilbot joined #puppet-openstack
02:46 Topic for #puppet-openstack is now Place to collaborate on Puppet/OpenStack tools: logs at http://irclog.perlgeek.de/puppet-openstack/today
03:27 Hunner_irssi joined #puppet-openstack
03:27 Hunner_irssi joined #puppet-openstack
03:27 blkperl joined #puppet-openstack
04:24 brdude joined #puppet-openstack
04:36 badiane_ka joined #puppet-openstack
06:04 michchap joined #puppet-openstack
07:04 michchap joined #puppet-openstack
07:08 francois1 joined #puppet-openstack
08:15 EmilienM i love wake up in the morning and see patches merged
08:16 EmilienM michchap: ^
08:16 EmilienM :)
08:24 marun joined #puppet-openstack
08:40 michchap :)
08:55 dachary joined #puppet-openstack
09:01 beddari left #puppet-openstack
09:02 beddari joined #puppet-openstack
09:11 derekh joined #puppet-openstack
09:21 comptona joined #puppet-openstack
09:26 michchap joined #puppet-openstack
09:52 dachary michchap: I'm having what seems to be LVM attachement issues related to apparmor restrictions. Does openstack-installer do apparmor related things ?
09:54 EmilienM dachary: i don't think so, it's for Ubuntu openstack-installer, as far i know
09:55 dachary apparmor is installed on ubuntu
10:08 EmilienM dachary: wow i should have read twice before, sorry
10:08 EmilienM dachary: i have no answer then
10:15 dachary I think it's something misconfigured and no relationship whatsoever with stackforge modules or openstack-installer. Another machine works fine. Sorry for the noise.
10:20 openstackgerrit Flavio Percoco proposed a change to stackforge/puppet-glance: Replace qpid_host with qpid_hostname  https://review.openstack.org/56208
10:23 michchap dachary: I have no idea. Maybe?
10:25 dachary michchap: apparently not, no worries. Not sure what the problem is yet but I'm quite sure it has no relationship with openstack-installer.
10:25 michchap dachary: ok cool.
10:26 mmagr joined #puppet-openstack
10:49 marun joined #puppet-openstack
11:15 dachary michchap: could it be the case that the "build" server ( openstack-installer parlance ) that runs the puppetmaster runs apparmor as a side effect ?
11:31 marun joined #puppet-openstack
12:13 rongze joined #puppet-openstack
12:30 morazi joined #puppet-openstack
12:48 morazi joined #puppet-openstack
13:02 rcrit joined #puppet-openstack
13:18 dprince joined #puppet-openstack
13:29 rmoe joined #puppet-openstack
13:37 michchap dachary: Entirely possible. It looks like the ones I build with sb have it on build
13:38 dachary ah :-) this is reassuring. That's what I get for installing the puppet master as a compute node also ;-)
13:38 michchap dachary: I know nothing about apparmor, but it says that there are 4 profiles and 4 processes in enforce mode, so I assume that means it's on.
13:38 EmilienM michchap: still here ???
13:38 michchap EmilienM: can't sleep :(
13:38 EmilienM wow it's late dude
13:39 michchap dachary: actually I see it on control and compute
13:39 michchap it's about midnight
13:42 hbroyon joined #puppet-openstack
13:45 michchap dachary: Apparmor profiles seem to be loaded silently when particular packages are installed. I'm not sure how to inspect a package to determine whether it's going to add a profile or not without opening the deb.
13:49 marun joined #puppet-openstack
13:51 michchap ./usr.lib.libvirt.virt-aa-helper:  deny /dev/dm-* r,
13:51 michchap dachary: That might be what's causing issues on your compute node. It's on my compute nodes too.
13:59 rongze dachary: ping
14:05 dachary rongze: let me take a look at the blueprint use case
14:05 dachary user story
14:07 dachary rongze: good catch, there cannot be two class by the same name https://wiki.openstack.org/wiki/Puppet​-openstack/ceph-blueprint#User_Stories
14:08 rongze dachary: If we have multiple osds in the same host,   ‘Class’ is not fit with ceph::osd
14:08 rongze dachary: the same as MON/KEY
14:10 rongze dachary: if you want to deploy multiple ceph cluster on the same host,  it may be multiple monitor on the same host...
14:11 dachary I don't know what's the puppet-openstack way of dealing with this.
14:12 dachary rongze: I completely ignored this so far but it must be addressed. And it should be addressed the same way other openstack related modules do it.
14:12 dachary EmilienM: do you have an opinion ?
14:13 dachary rongze: do you have a suggestion ?
14:13 rongze dachary: what about use 'define' ?
14:13 dachary unless I'm mistaken 'define' would break scenario_node_terminus
14:14 dachary michchap: and bodepd know more than I do regarding this
14:15 rongze dachary: it is a example  https://github.com/enovance/puppet-cep​h/blob/master/manifests/osd/device.pp
14:18 dachary rongze: I don't think this module is compatible with scenario_node_terminus
14:19 dachary I may be wrong though
14:20 rongze dachary: shall we must compatible with scenario_node_terminus ?  Today I have just learning scenario_node_terminus :)
14:23 dachary I use it, bodepd does, michchap also. I have no use for a module that do not support scenario_node_terminus. I realize that does not make a majority. But that's definitely something that I care about ;-)
14:27 rongze I also like 'data driven approach to deploy'.. but how to resolve the problem about duplicate declaration class ?
14:27 rongze dachary: may be we need some time to address it
14:32 dachary rongze: it has been resolved, I think, for the existing puppet openstack modules which are all compatible with scenario_node_terminus. But I'm not familiar with their design and don't know how. You raised an excellent question.
14:35 rongze dachary: after I fast read the puppet-openstack source code, I found there is one 'define' , https://github.com/stackforge/puppet-openstack/​blob/master/manifests/swift/device_endpoint.pp
14:37 dachary My understanding is that using define is ok as long as it is *not* the user facing API
14:47 rongze dachary: I'm sorry, I spend time to call my colleague to ask the question, but he have not idea to address it if not use 'define' :(   Could you define the *user facing api* ?
14:47 dachary :-)
14:48 rongze dachary:  Do you mean I cannot write 'define' in the site.pp ?
14:48 dachary rongze: by "user facing API" I mean the set of classes that are documented and that the user of the module is expected to understand. If all these are classes only, then only those will be used by scenario_node_terminus and it does nto matter what's underneath is.
14:49 dachary it's probably not the correct term in the puppet context
14:49 rongze dachary: I see
14:51 dachary in other words, if a functionality of the module can only be accessed via a define, we have a problem
14:51 dachary if a class wraps it, it's good
14:53 rongze dachary: I think I need some time to study scenario_node_terminus and how to use it ..
14:55 dachary rongze: IMO openstack-installer is the easiest way to get familiar with it ( http://dachary.org/?p=2352 for instructions or the README )
14:55 Gwyxx joined #puppet-openstack
14:56 rongze dachary: thank you very much
15:04 dmsimard joined #puppet-openstack
15:27 otherwiseguy joined #puppet-openstack
15:30 SVernalde joined #puppet-openstack
15:31 hbroyon hello
15:32 Jean-Roger Hello hbroyon
15:35 rongze joined #puppet-openstack
15:39 mjblack joined #puppet-openstack
15:47 andi- joined #puppet-openstack
15:51 Jean-Roger joined #puppet-openstack
15:58 dwt2 joined #puppet-openstack
15:59 ianw joined #puppet-openstack
16:03 bcrochet joined #puppet-openstack
16:06 bcrochet joined #puppet-openstack
16:17 mjblack_ joined #puppet-openstack
16:17 rongze joined #puppet-openstack
16:37 piliman974 joined #puppet-openstack
16:43 badiane_ka joined #puppet-openstack
17:06 xarses joined #puppet-openstack
17:07 nibalizer joined #puppet-openstack
17:10 rmoe joined #puppet-openstack
17:41 dprince joined #puppet-openstack
17:49 badiane_ka joined #puppet-openstack
17:50 hogepodge joined #puppet-openstack
17:56 brdude joined #puppet-openstack
17:59 rongze joined #puppet-openstack
18:04 mjblack joined #puppet-openstack
18:08 brdude joined #puppet-openstack
18:15 EmilienM dachary: no
18:33 rongze joined #puppet-openstack
18:36 hogepodge joined #puppet-openstack
18:38 finch left #puppet-openstack
18:58 mjblack joined #puppet-openstack
19:00 angdraug joined #puppet-openstack
19:09 mjblack joined #puppet-openstack
19:27 openstackgerrit A change was merged to stackforge/puppet-neutron: Improve multi DHCP agent support  https://review.openstack.org/55228
19:34 rongze joined #puppet-openstack
19:51 mwoodson joined #puppet-openstack
20:06 mwoodson ianw: hey man
20:07 mwoodson i am looking at using the puppet-heat module.  I had a few questions about it, one of them in particular was the encription line.
20:07 mwoodson it has: command => 'sed -i".bak"
20:08 mwoodson this will never get written out to the file.  I was trying to figure out the reasoning behind this.
20:36 rongze joined #puppet-openstack
20:37 xarses dachary: ping
20:52 tnoor joined #puppet-openstack
20:53 dachary xarses: pong ( back in 30 min or so )
20:54 xarses https://review.openstack.org/#/c/57063
20:56 xarses darchy: I can't implement the rspec-system-tests yet as i don't know how. I'll probably catch up to that in another week or so, do we want to hold the commit hostage for it?
21:06 hogepodge sed -i writes a file in place and backs up the file with the given extension
21:07 hogepodge mwoodson: ^
21:07 mwoodson hogepodge: sorry, let me rephrase my question
21:08 mwoodson hogepodge: i think another bug is getting me, cause it doesn't seem to be writing that file out
21:08 mwoodson probably this one: https://bugs.launchpad.net​/puppet-heat/+bug/1249280
21:10 hogepodge If that exec line is run the file /etc/heat/heat.conf should be modified, and you should see a heat.conf.bak file also.
21:12 tnoor1 joined #puppet-openstack
21:14 mwoodson hogepodge: it is, but it's being run every puppet run.
21:14 hogepodge Yes, that's the bug you referenced.
21:15 hogepodge Thanks for clarifying.
21:15 mwoodson sorry if i wasn't clear :)
21:30 dachary xarses: since we don't yet have a policy for integration tests and you promise to do it later I tend to believe you and +2 although I have not clue if it works  or not. That being said, what's the difference between it not being there and it not being integration tested ? When ceph::mon lands, there will be no way for me to know that it works on redhat and so on. Therefore, for all intent and purposes, redhat won't actually be supported.
21:34 rmoe_ joined #puppet-openstack
21:34 hogepodge xarses dachary: Lacking rspec-system-tests, I would hope that someone is running integration tests manually. Is that the case? I feel a bit odd committing code I haven't tested, but I feel better about it if I know that somebody I trust (like the regular puppet-openstack devs) have. I'm not fond of futures, though. See for example this https://review.openstack.org/#/c/48289/
21:37 rongze joined #puppet-openstack
21:38 dachary hogepodge: yes, that's what it boils down to, best case scenario. Worst case every OS specific modification stays in various forks and not merged upstream. The lack of integration tests play a large role ( although not exclusively ) in such a fragmentation. Another factor is the lack of dedicated upstream : if someone is caring for the module in a very dedicated way and centralizes all the knowledge there is, has the stamina and expertise t
21:38 dachary setup and run semi-manual tests on various OS, it also works.
21:40 dachary It's often not for a lack of good will ( fc__  has plenty of good will ;-) it's most of the time a lack of time and means, because the employer has other plans than to let the employee care for a module that does not generate enough revenus (percieved or real) to justify the salary.
21:49 ianw mwoodson: hi
21:51 xarses joined #puppet-openstack
21:52 hogepodge I just get the feeling that we're a bit doomed on testing these modules regardless. There are way too many combinations of options to make sure everything works even in an automated way. Smokestack ensures that the modules don't break smokestack, but that means new features or configurations slip through the cracks. I don't have a good solution, also having some level of automated system testing helps.
21:54 mjblack joined #puppet-openstack
22:00 mjblack_ joined #puppet-openstack
22:04 hogepodge joined #puppet-openstack
22:16 rmoe joined #puppet-openstack
22:23 rmoe joined #puppet-openstack
22:25 xarses_ joined #puppet-openstack
22:29 xarses dachary hogepodge: sorry network cut out.
22:30 xarses dachary: the main issue i have at the moment, is that i don't see examples of testing two distro's so I'll have to research that some
22:30 dachary xarses: ho, I have one example
22:30 xarses snap
22:30 xarses where?
22:32 dachary xarses: https://review.openstack.org/#/c/56427/ which I abandoned not because it does not work but because the image was too old ( there was no debian wheezy 7.2 images ready ). The patch is good though.
22:33 xarses Ahh, thats where that went
22:34 dachary i'd glad if you find value in it ;-)
22:34 dachary s/glad/be glad/
22:37 rongze joined #puppet-openstack
22:37 xarses yep, thats a start, still need to figure out how to get it to use a seperate set of spec/system tests
22:52 openstackgerrit A change was merged to stackforge/puppet-swift: Add Bulk middleware support  https://review.openstack.org/54366
22:52 openstackgerrit A change was merged to stackforge/puppet-cinder: Add Swift as backup backend support  https://review.openstack.org/56305
23:17 mjblack joined #puppet-openstack
23:25 rmoe joined #puppet-openstack
23:26 hogepodge joined #puppet-openstack
23:38 rongze joined #puppet-openstack
23:55 rmoe joined #puppet-openstack
23:59 tnoor joined #puppet-openstack

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