Perl 6 - the future is here, just unevenly distributed

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

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

All times shown according to UTC.

Time Nick Message
00:06 gildub joined #puppet-openstack
00:19 aimon_ joined #puppet-openstack
00:21 openstackgerrit joined #puppet-openstack
00:59 markvoelker joined #puppet-openstack
01:05 openstackgerrit joined #puppet-openstack
01:35 rmoe joined #puppet-openstack
01:58 markvoelker joined #puppet-openstack
02:15 xarses joined #puppet-openstack
02:21 openstackgerrit joined #puppet-openstack
02:48 ilbot3 joined #puppet-openstack
02:48 Topic for #puppet-openstack is now Place to collaborate on Puppet/OpenStack tools: logs at http://irclog.perlgeek.de/puppet-openstack/today
03:20 openstackgerrit joined #puppet-openstack
03:51 blkperl joined #puppet-openstack
04:11 badiane_ka joined #puppet-openstack
04:21 markvoelker joined #puppet-openstack
04:47 fc__ joined #puppet-openstack
04:48 ikke-t joined #puppet-openstack
04:48 bogdando joined #puppet-openstack
04:53 markvoelker_ joined #puppet-openstack
04:55 fedexo joined #puppet-openstack
05:01 sanjayu joined #puppet-openstack
05:04 sanjayu_ joined #puppet-openstack
05:06 sanjayu_ joined #puppet-openstack
05:13 timbyr_ joined #puppet-openstack
05:16 markvoelker joined #puppet-openstack
05:47 markvoelker joined #puppet-openstack
05:51 blkperl joined #puppet-openstack
05:52 blkperl joined #puppet-openstack
06:19 timbyr_ joined #puppet-openstack
06:29 sileht joined #puppet-openstack
06:48 markvoelker joined #puppet-openstack
07:05 sanjayu__ joined #puppet-openstack
07:21 markvoelker joined #puppet-openstack
07:39 ebogdanov joined #puppet-openstack
07:47 openstackgerrit GuanYu, lin proposed stackforge/puppet-cinder: Adds ability to override service name for service catalog  https://review.openstack.org/150658
07:49 stamak joined #puppet-openstack
07:51 EmilienM|afk dachary, dmsimard_away: do you have an example of composition layer usage for stackforge/puppet-ceph ?
07:53 dgurtner joined #puppet-openstack
07:53 dgurtner joined #puppet-openstack
07:55 arnaud_orange joined #puppet-openstack
08:15 timbyr_ joined #puppet-openstack
08:19 GrwN left #puppet-openstack
08:22 ByteSore joined #puppet-openstack
08:25 markvoelker joined #puppet-openstack
08:25 e1mer joined #puppet-openstack
08:25 e1mer joined #puppet-openstack
08:33 tfz joined #puppet-openstack
08:46 eglynn-pto joined #puppet-openstack
08:52 stamak joined #puppet-openstack
08:52 jpena joined #puppet-openstack
08:53 mmagr joined #puppet-openstack
09:16 dachary EmilienM|afk: is there something that could be useful to you at https://github.com/stackforge/puppet-ceph/blob/master/USECASES.md ? It has been updated recently but it looks like the review's not complete yet.
09:16 jistr joined #puppet-openstack
09:28 markvoelker joined #puppet-openstack
09:47 derekh joined #puppet-openstack
10:28 mmagr joined #puppet-openstack
10:30 markvoelker joined #puppet-openstack
11:14 dgurtner joined #puppet-openstack
11:14 dgurtner joined #puppet-openstack
11:31 markvoelker joined #puppet-openstack
11:37 mmagr joined #puppet-openstack
11:45 cdent joined #puppet-openstack
12:01 eglynn-pto joined #puppet-openstack
12:31 markvoelker joined #puppet-openstack
12:52 ebogdanov joined #puppet-openstack
12:55 ebogdanov joined #puppet-openstack
13:10 morazi joined #puppet-openstack
13:11 bodepd_ hi
13:12 bodepd_ I'm working with someone who wants to contribute flavor management type/providers
13:12 dprince joined #puppet-openstack
13:12 bodepd_ and I know that part of the code has been changing quite a bit, is there a parent provider that we should be using? Has aviator definitely been chosen over openstackclient?
13:22 EmilienM dachary: thx, will look
13:22 EmilienM dprince: https://github.com/stackforge/puppet-ceph/blob/master/USECASES.md
13:22 EmilienM that may help us :)
13:24 dprince EmilienM: cool, yep
13:27 Madkiss here you mean?
13:27 dachary off_rhoden: is the person you want to talk, I think EmilienM / dprince
13:27 EmilienM Madkiss: yes
13:28 Madkiss i guess rich is not onlnie right now, then :)
13:28 EmilienM dachary: we had talked in the past, but nothing happened - we take actions now
13:28 EmilienM Madkiss: yes, he's UTC-7 AFIK
13:28 Madkiss i see
13:30 dachary EmilienM: I'm not sure what action you're refering to ?
13:31 EmilienM off_rhoden and my folks wanted to compare enovance/puppet-ceph (already in production) and stackforge/puppet-ceph - define the gap, and bring new (eventual missing) features to converge to the stackforge module.
13:33 markvoelker joined #puppet-openstack
13:33 dachary I remember that EmilienM. What action are you taking now ?
13:33 EmilienM dachary: today is our sprint planning, i have no details yet :-)
13:34 dachary oh, I was confused when you wrote : "we take actions now". Please let us know what comes out of it, I'm interested (although not active ;-).
13:35 markvoelker_ joined #puppet-openstack
13:38 spredzy bodepd_, I started a similar work (not upstream), trying to replicate https://forge.puppetlabs.com/puppetlabs/gce_compute but for openstack (nova_instance, nova_flavor, identity_keypair, etc...).
13:38 spredzy bodepd_, do you have anything public I can look at ?
13:47 QuentinM joined #puppet-openstack
13:47 QuentinM Hey there. It seems that something's wrong with Librarian-puppet + stackforge/puppet-ceph but I can't determine what. Can somebody help me figuring out ? http://pastebin.com/SV0MS9ER
13:54 eglynn-pto joined #puppet-openstack
13:55 bodepd_ spredzy: nah, we haven't started yet. I'd be pretty partial to using whatever parent classes crinkle recommends though
13:55 bodepd_ spredzy: for now, we really just care about images
13:57 _nick joined #puppet-openstack
13:57 bodepd_ QuentinM: try using librian-puppet-simple or r10k. librarian-puppet doesn't really work
13:57 QuentinM oh thanks okay
14:00 jistr joined #puppet-openstack
14:04 rcallawa joined #puppet-openstack
14:06 rcallawa joined #puppet-openstack
14:19 eglynn-pto joined #puppet-openstack
14:25 mschmitt joined #puppet-openstack
14:27 flaviof joined #puppet-openstack
14:33 richm joined #puppet-openstack
15:01 ericpeterson joined #puppet-openstack
15:11 jistr joined #puppet-openstack
15:21 dmsimard EmilienM: There's a composition layer built in the module
15:21 dmsimard EmilienM: I have almost nothing for my composition layer aside from specific configs I want and base install tools/config
15:22 dmsimard EmilienM: Look in roles/profiles, they were built by dgurtner - the spec/system tests can give you a good hint at how to use them
15:32 cwolferh joined #puppet-openstack
15:34 EmilienM dmsimard: thanks
15:44 dgurtner EmilienM: ping
15:45 markvoelker joined #puppet-openstack
15:46 dgurtner EmilienM: I saw you referencing the puppet-ceph USECASES.md before
15:47 dgurtner EmilienM: they are heavily out of sync, and you might want to check out https://review.openstack.org/#/c/98730/ instead
15:59 prad joined #puppet-openstack
16:10 mdorman joined #puppet-openstack
16:24 Hunner joined #puppet-openstack
16:39 crinkle bodepd_: we actually switched back to openstackclient, and so far it's been implemented only in the keystone module
16:39 crinkle because we wanted to be able to backport it to stable/juno without breaking dependencies
16:39 crinkle but the parent stuff will go into openstacklib soonish
16:43 EmilienM dgurtner: thanks a lot!
16:44 dgurtner EmilienM: the code inside of the CI tests in spec/system also contain quite a few examples on how to use it
16:44 EmilienM dgurtner: ok
16:44 EmilienM and now the one million dollars question
16:44 EmilienM who is running it in production ?
16:46 dgurtner that's alas a chicken and egg question
16:47 dgurtner only the people actually using it could answer that question
16:48 EmilienM dgurtner: so let me give a bit of background
16:49 EmilienM we (enovance) are running github/enovance/puppet-ceph in production for a while now - and we still maintain it with the feedback we got from the field - so I want to measure the gap between the 2 modules and see what we would need to bring up to stackforge module.
16:49 EmilienM fc__: FYI ^
16:50 EmilienM dgurtner: my goal is to converge to the stackforge one
16:50 EmilienM but I have to ensure I don't break our deployments
16:53 dmsimard EmilienM: I'm using it for our private cloud Ceph
16:53 dgurtner EmilienM: right... so you're looking for people using it in production which could give you feedback on the long-time stability of the module?
16:53 dmsimard EmilienM: I "migrated" from a fork of Enovance's puppet-ceph to the stackforge one
16:54 dmsimard Migrate is a big word, I just started the cluster from scratch :p
16:54 aarefiev joined #puppet-openstack
16:54 dmsimard I was using https://github.com/TelekomCloud/puppet-ceph/tree/rc/eisbrecher
16:55 aarefiev joined #puppet-openstack
16:58 EmilienM dgurtner: yes I need feedback
16:58 EmilienM dmsimard: dgurtner what I see by migration is a way to migrate a cluster and not breaking everything
16:59 EmilienM we have a long therm support for our platforms, so...
17:00 dmsimard EmilienM: That's a tough one. You'll need to do some testing before doing it live in production for sure. I haven't gone that route so I can't help you there :(
17:04 EmilienM dmsimard: yeah I know it's not going to be easy but we like challenges :)
17:04 dmsimard EmilienM: Hyped about you guys working in that direction
17:10 fc__ EmilienM: saw this on trello, I may be able to help you a little bit depending on the bandwidth I'll have in the following weeks
17:13 dgurtner EmilienM: I guess one important step would be to get more reviewers (and ultimately core reviewers) on the stackforge module, because currently many things get stuck for a long time
17:13 EmilienM dgurtner: I'm going to be more involved in the next weeks, we have user stories about it in our backlog
17:14 dgurtner EmilienM: great!
17:14 EmilienM dgurtner: I'm already puppet-openstack core, not on ceph though
17:15 dgurtner yes, currently it's only dachary, xarses, dmsimard and me on the puppet module
17:15 rcallawa joined #puppet-openstack
17:15 dgurtner dmsimard provided a new CI box
17:16 dmsimard dgurtner: One of the large steps is to go in the same direction as the puppet-openstack modules though (beaker)
17:16 dmsimard This is probably going to be a lot of work
17:16 dgurtner and I'm currently trying to iron out the final kinks before CI works again
17:16 dgurtner dmsimard: agreed
17:17 dgurtner dmsimard: but the first step for me is to get the outstanding reviews merged
17:17 * dmsimard nods
17:18 dgurtner but beaker would make many things easier, because set-up and tear-down would become easier
17:18 dmsimard Not only that but I believe puppet-openstack leverages openstack-infra
17:19 rcallawa joined #puppet-openstack
17:23 dachary EmilienM: although I agree that it would be great to be able to transition from the enovance puppet-ceph, it would be a lot of work. Is it a Red Hat requirement ? If it is I'm confident resources will be found ;-) If not, it's likely not to happen ever, unfortunately.
17:29 openstackgerrit Emilien Macchi proposed stackforge/puppet-nova: params: update libvirt  https://review.openstack.org/151324
17:30 markvoelker joined #puppet-openstack
17:34 rcallawa_ joined #puppet-openstack
17:34 rmoe joined #puppet-openstack
17:52 xarses joined #puppet-openstack
18:02 rcallawa joined #puppet-openstack
18:08 timbyr_ joined #puppet-openstack
18:16 tfz joined #puppet-openstack
18:27 arnaud_orange joined #puppet-openstack
18:48 fandi joined #puppet-openstack
18:50 eglynn joined #puppet-openstack
18:51 openstackgerrit joined #puppet-openstack
18:52 openstackgerrit Emilien Macchi proposed stackforge/puppet-nova: params: update libvirt  https://review.openstack.org/151324
18:57 aimon joined #puppet-openstack
19:28 aimon joined #puppet-openstack
19:29 aimon joined #puppet-openstack
19:46 badiane_ka joined #puppet-openstack
19:50 andi- joined #puppet-openstack
19:50 andi- joined #puppet-openstack
19:51 rmoe_ joined #puppet-openstack
19:55 social_ joined #puppet-openstack
19:55 michchap_ joined #puppet-openstack
19:57 aarefiev joined #puppet-openstack
20:05 openstackgerrit joined #puppet-openstack
20:14 xarses joined #puppet-openstack
20:45 aimon joined #puppet-openstack
20:54 britthouser joined #puppet-openstack
20:58 dprince joined #puppet-openstack
21:21 dgurtner joined #puppet-openstack
21:21 dgurtner joined #puppet-openstack
21:24 rcallawa joined #puppet-openstack
21:24 morazi joined #puppet-openstack
22:06 morazi joined #puppet-openstack
22:15 pradk joined #puppet-openstack
22:47 markvoelker_ joined #puppet-openstack
22:51 xarses joined #puppet-openstack
22:52 openstackgerrit joined #puppet-openstack
23:11 EmilienM dachary: quick question
23:11 EmilienM dachary: how do you manage the mount for osds ?
23:11 EmilienM I don't see any exec or provider
23:13 dachary EmilienM: that's a key difference between the stackforge and the enovance module. There is no need to manage the mounts, this is taken care of by Ceph, via udev rules and ceph-disk. The enovance module was created prior to this mechanism and handles it in a different way.
23:14 EmilienM awesome
23:15 gildub joined #puppet-openstack
23:15 dachary yes, except when you have an existing installation already managing disks in a different way. Transitioning to ceph-disk amounts to rewriting the manifests entirely.
23:17 EmilienM dachary: I take note
23:18 dachary You will find a lot more material about this in the discussions (puppet-openstack google group)  and the stackforge/puppet-ceph specifications.
23:32 imcsk8 joined #puppet-openstack
23:36 openstackgerrit Matt Fischer proposed stackforge/puppet-heat: Support region_name for Heat  https://review.openstack.org/150139
23:51 QuentinM left #puppet-openstack
23:57 nosleep77 joined #puppet-openstack

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