Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2015-04-13

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

All times shown according to UTC.

Time Nick Message
00:18 ericpeterson joined #puppet-openstack
00:35 openstackgerrit Merged stackforge/puppet-horizon: Add support for Neutron DVR and L3 HA options  https://review.openstack.org/170091
00:40 gildub joined #puppet-openstack
00:55 ericpeterson joined #puppet-openstack
02:08 ericpeterson joined #puppet-openstack
03:12 subscope_ joined #puppet-openstack
03:24 ericpeterson joined #puppet-openstack
05:13 ericpeterson joined #puppet-openstack
05:14 britthouser joined #puppet-openstack
05:16 britthou_ joined #puppet-openstack
06:15 stamak joined #puppet-openstack
06:34 rwsu joined #puppet-openstack
06:53 saneax joined #puppet-openstack
07:01 ericpeterson joined #puppet-openstack
07:06 asilenkov joined #puppet-openstack
07:08 igajsin joined #puppet-openstack
07:20 gchamoul morning!
07:24 jistr joined #puppet-openstack
07:24 openstackgerrit Yanis Guenane proposed stackforge/puppet-tripleo: Enable access to HAProxy stats page  https://review.openstack.org/171957
07:25 tfz joined #puppet-openstack
07:29 dgurtner joined #puppet-openstack
07:29 dgurtner joined #puppet-openstack
07:32 dgurtner joined #puppet-openstack
07:32 dgurtner joined #puppet-openstack
07:37 gfidente joined #puppet-openstack
07:49 tfz joined #puppet-openstack
07:50 jpena joined #puppet-openstack
08:03 stamak joined #puppet-openstack
08:05 mmagr joined #puppet-openstack
08:32 derekh joined #puppet-openstack
08:36 openstackgerrit Benedikt Trefzer proposed stackforge/puppet-vswitch: make dkms on Debian/Ubuntu optional, add tests  https://review.openstack.org/151629
08:43 IBerezovskiy joined #puppet-openstack
08:50 ericpeterson joined #puppet-openstack
09:05 igajsin left #puppet-openstack
09:08 openstackgerrit Lukas Bezdicka proposed stackforge/puppet-trove: Sync amqp support with other openstack modules  https://review.openstack.org/169808
09:23 ddmitriev joined #puppet-openstack
09:41 mmagr joined #puppet-openstack
09:42 beddari spredzy: how do you relate puppeels to the cloud module? would it make sense for puppeels to use that? and have them interface each other. just an idea :)
09:45 danieru joined #puppet-openstack
09:46 spredzy beddari, hey, By cloud you refer to https://github.com/stackforge/puppet-openstack-cloud ?
09:53 beddari spredzy: yep
09:53 beddari spredzy: I think so :) at least hehe
09:54 spredzy Initally, the intent in pupeels/openstack was to backport puppet-openstack-cloud (the hierarachy), but just using includes, removing all the logic that was in puppet-openstack-cloud so it could be hiera driven
09:54 beddari yes sounds like me
09:55 beddari like something I want ;)
09:55 spredzy so per-se, puppeels doesn't rely/use puppet-openstack-cloud, but it provide the exact same hierarchy
09:55 beddari yeah that was what I noticed now that I actually cared to look at your latest commits
09:56 beddari :-)
09:56 spredzy interfaces are different since we don't want to provide parameters (actually the least possible)
09:56 beddari yes I realize, need more people to understand why hehe
09:57 beddari to provide more value we could argue that puppeels needs possibly data-in-modules or a tree to go with it
09:57 beddari more reuse value I mean
09:58 spredzy agree for puppet-module-data use
09:59 beddari that was what you were doing with the examples I remember
09:59 markvoelker joined #puppet-openstack
10:00 spredzy well the example were strictly using hiera, since my target is only EL7 it wasn't a big deal (for my examples)
10:01 _nick joined #puppet-openstack
10:01 spredzy IF you have a scenario/need of puppet-module-data, could you do a quick PR (doesn't have to be working) just so I can grasp the idea of what is it you'd expect
10:01 beddari yes, I've been using Hiera quite extensively for a long time now, to the point where I think parameters are mostly annoying in the composition layer
10:02 beddari yes, the discussion though is what parameters do you leave at that point :) ?
10:03 spredzy Well the only parameter I'd like to leave, are the one to use in create_resources()
10:04 beddari yes, I think I'll have to show you some code to really discuss this ;)
10:04 beddari I've only done data-in-modules plus explicit hiera (no params) for a composition layer in samller examples, not openstack/larger infra yet
10:05 dgurtner joined #puppet-openstack
10:06 spredzy beddari, I'd be interested in seeing code see what you're doing
10:06 spredzy fire a PR even w/ the current code you have, just so I can grasp where you want to head at
10:08 beddari I'll try
10:08 spredzy Thanks
10:08 beddari one more idea to think about: once going this way, it is possible to think about the param to a class being its schema/interface
10:14 spredzy well, if I get what you're saying yes it will be the schema/interface to the pupeels class. But then it will be up to the deployer to configure the underlying classes params
10:18 cdent joined #puppet-openstack
10:18 markvoelker joined #puppet-openstack
10:33 ferest joined #puppet-openstack
10:39 ericpeterson joined #puppet-openstack
11:14 dgurtner joined #puppet-openstack
11:14 dgurtner joined #puppet-openstack
11:20 nosleep77 joined #puppet-openstack
11:22 openstackgerrit Gael Chamoulaud proposed stackforge/puppet-ceilometer: spec: Add Unit Tests for Ceilometer_config type/provider  https://review.openstack.org/170488
11:40 ericpeterson joined #puppet-openstack
11:56 saneax joined #puppet-openstack
12:09 EmilienM|afk good morning
12:10 ericpeterson joined #puppet-openstack
12:21 morazi joined #puppet-openstack
12:26 dprince joined #puppet-openstack
12:52 markvoelker joined #puppet-openstack
12:54 markvoelker_ joined #puppet-openstack
13:03 openstackgerrit joined #puppet-openstack
13:09 richm joined #puppet-openstack
13:11 tfz joined #puppet-openstack
13:16 ozialien joined #puppet-openstack
13:20 ericpeterson joined #puppet-openstack
13:24 ericpeterson joined #puppet-openstack
13:25 ericpeterson joined #puppet-openstack
13:38 ferest joined #puppet-openstack
13:49 beddari morning :)
13:53 beddari spredzy: so the "problem" with these hash params as opposed to inline hiera calls is that there is no way to do hash or array searches for the data, right? So instead of writing wrapper classes to do that, once hiera is your only concern it is better I think to reserve params/autolookup for returning a value to the class that determines if you want a full hash data search - or only a simple lookup
13:53 beddari spredzy: these in the above are ref https://github.com/Mylezeem/puppeels/blob/master/manifests/database/mariadb.pp#L12-L16
13:54 ferest joined #puppet-openstack
13:59 spredzy beddari, not sure I understand. "inline hiera calls": How can you instantiate define type from hiera ? "to do a hash or array searches for the data": What do you mean by that ?
14:05 britthouser joined #puppet-openstack
14:05 ericpeterson joined #puppet-openstack
14:12 britthouser joined #puppet-openstack
14:25 richm How are keystone admin credentials used on nodes that are not keystone nodes?
14:26 richm For example, on keystone nodes, the puppet code can fall back to using the admin token from keystone.conf
14:26 richm But on a non keystone node, how do you pass in the admin credentials?
14:33 richm Anyone?  Anyone doing multi-node installations?
14:33 vinsh joined #puppet-openstack
14:34 EmilienM richm: that's a well known issue
14:34 EmilienM richm: can you tell me which use case you need the credentials (ie which class)
14:36 richm EmilienM: I'm trying to understand how this works, trying to understand how the user domain and project domain will be passed in as well as the username and password
14:36 EmilienM richm: ok so I think you would have to use ::keystone everywhere you want to manage Keystone resources
14:36 EmilienM except if we change something
14:37 EmilienM there is a change we could do, is to check if an openrc is existing and we could load it if so.
14:38 richm I'm also trying to figure out if there is a way we could have the puppet code use a global, default domain
14:38 richm When using the v3 api, the domain parameter is required for all domain scoped resources - keystone_user, keystone_tenant, keystone_user_role
14:39 richm It's going to be an upgrade/migration nightmare if you have to add a domain parameter to every single resource, and every single class/resource that references keystone resources, and so on, all the way up to the composition layer
14:40 richm Again, on the keystone node, and only on the keystone node, the puppet code can use the default_domain_id parameter from keystone.conf
14:40 richm which is what my latest patch attempts (and fails) to do
14:41 richm Is there some way to set some sort of global variable/parameter?
14:41 richm I know I can use hiera to do that, but I get the impression that hiera is not widely used
14:42 richm Is it possible to add a custom fact with facter, that would be available on all nodes?  But then how would I allow that custom fact to be configurable by the deployer?
14:47 markvoelker joined #puppet-openstack
14:48 markvoelker_ joined #puppet-openstack
14:52 markvoelker joined #puppet-openstack
14:54 rwsu joined #puppet-openstack
15:03 beddari spredzy: ok, I'll need code, it's so much easier :)
15:07 mdorman joined #puppet-openstack
15:07 stevemar joined #puppet-openstack
15:09 openstackgerrit Merged stackforge/puppet-cinder: Adds OracleLinux support  https://review.openstack.org/170879
15:12 openstackgerrit Merged stackforge/puppet-nova: Adds OracleLinux support  https://review.openstack.org/170857
15:23 stamak joined #puppet-openstack
15:30 stevemar joined #puppet-openstack
15:31 aschultz_ joined #puppet-openstack
15:53 markvoelker_ joined #puppet-openstack
16:02 cwolferh joined #puppet-openstack
16:04 stevemar joined #puppet-openstack
16:41 subscope_ joined #puppet-openstack
16:43 mmagr joined #puppet-openstack
16:54 vinsh joined #puppet-openstack
16:56 richm Anyone?  Any ideas?  Is there really no way to do this but to add a domain parameter to all of the composition layers, on down to the calls to keystone resources, and force all puppet code to change at the same time?
16:59 mschmitt joined #puppet-openstack
17:12 ozialien joined #puppet-openstack
17:23 hogepodge joined #puppet-openstack
17:28 aimon joined #puppet-openstack
17:52 ozialien joined #puppet-openstack
17:54 mwhahaha joined #puppet-openstack
17:56 markvoelker joined #puppet-openstack
18:04 britthouser joined #puppet-openstack
18:32 openstackgerrit Adam Vinsh proposed stackforge/puppet-swift: Added rsyslog logging support to object-server  https://review.openstack.org/169071
18:37 openstackgerrit Adam Vinsh proposed stackforge/puppet-swift: Added rsyslog logging support to object-server  https://review.openstack.org/169071
18:37 vinsh gchamoul: ^^ better approach then my first pass.
18:39 openstackgerrit Muhammad Salman Khan proposed stackforge/puppet-neutron: Add PLUMgrid plugin support.  https://review.openstack.org/173033
18:47 openstackgerrit Muhammad Salman Khan proposed stackforge/puppet-neutron: Add PLUMgrid plugin support.  https://review.openstack.org/173033
18:59 dprince joined #puppet-openstack
19:11 openstackgerrit Ryan Hefner proposed stackforge/puppet-manila: Update share driver parameters  https://review.openstack.org/171778
19:48 cdent joined #puppet-openstack
20:14 tlbr joined #puppet-openstack
20:26 vinsh Can anyone comment on the over-all strategy around using templates for config files vs the service specific "<service>_config" provider?
20:37 sanjayu joined #puppet-openstack
20:52 openstackgerrit Ryan Hefner proposed stackforge/puppet-manila: Support network plugin model  https://review.openstack.org/171737
20:58 EmilienM vinsh: for *.conf files, we always use templates (except for puppet-swift)
20:58 EmilienM and there is some discussion around this
20:59 markvoelker joined #puppet-openstack
21:00 vinsh You mean the other way around right?
21:00 vinsh Templates for puppet-swift only and not others
21:01 vinsh EmilienM: ^ ?
21:01 EmilienM yeah
21:01 EmilienM but I think we want to use providers for everything
21:01 vinsh What I am looking at is a bunch of tuneables for swift
21:01 EmilienM tell me if I'm wrong, but it allows more flexibility
21:02 vinsh I'm wondering if its worth it to put up reviews that would add these to puppet-swift
21:02 vinsh OR, since the defaults are usually ok.. if its not worth it.
21:02 EmilienM vinsh: which one?
21:02 vinsh For example, the interval settings for object-updater
21:02 vinsh or any of the services.
21:03 EmilienM I think you can go ahead with a patch, by taking in example how it's done for other params
21:03 EmilienM the migration to providers is not for today
21:04 vinsh Ok cool, there are quite a few to add to puppet-swift.. I was thinking that having the ability to tune them is just a better thing
21:04 vinsh though some would argue simpler is better.
21:04 ozialien joined #puppet-openstack
21:05 vinsh I also wonder if we should be building in the sysctl settings used to tune swift into the module?
21:05 vinsh Or do you just say that folks should do that in their own manifests depending on their needs?
21:09 cdent joined #puppet-openstack
21:23 britthouser joined #puppet-openstack
21:26 openstackgerrit Muhammad Salman Khan proposed stackforge/puppet-neutron: Add PLUMgrid plugin support.  https://review.openstack.org/173033
21:26 xarses joined #puppet-openstack
21:28 fedexo joined #puppet-openstack
21:51 fedexo joined #puppet-openstack
22:00 markvoelker_ joined #puppet-openstack
22:01 salmankh joined #puppet-openstack
22:01 salmankh Hey Guys
22:02 salmankh I am new to the community and made my commit. Please help me to understand few things.
22:14 salmankh joined #puppet-openstack
22:33 nosleep77 joined #puppet-openstack
22:52 aimon joined #puppet-openstack
23:05 gildub joined #puppet-openstack
23:49 markvoelker joined #puppet-openstack
23:50 mschmitt joined #puppet-openstack
23:53 markvoelker_ joined #puppet-openstack

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