Perl 6 - the future is here, just unevenly distributed

IRC log for #puppet-openstack, 2014-05-30

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

All times shown according to UTC.

Time Nick Message
00:08 kkirkpatrick joined #puppet-openstack
00:09 starmer joined #puppet-openstack
00:29 aimon joined #puppet-openstack
00:42 rmoe joined #puppet-openstack
01:15 imcsk8 hello guys i have a i'm stuck with a problem with the spec file to this patch: https://review.openstack.org/#/c/95519/ can somebody give me a hint in how to fix the spec file? thanks!
01:17 kitp joined #puppet-openstack
01:19 dvorak I'd guess you need to change the service name on line 49
01:22 michchap imcsk8: see review
01:25 longguang how to build a module?
01:25 starmer joined #puppet-openstack
01:26 aldavud joined #puppet-openstack
01:39 michchap http://docs.puppetlabs.com/pe/latest/quick_writing_nix.html
01:39 michchap longguang: these questions might be better off in #puppet
01:41 longguang michchap:all files belong to openstack-puppet-modules-2013.2-9.1.el6.noarch.rpm  are in /usr/share/puppet.  if those modules need to be build ?
01:44 michchap longguang: you mean compiled? No, puppet modules are not compiled. A catalog is compiled when you run puppet apply but it reads the modules in plain text.
01:44 longguang yes
01:44 longguang ok
02:00 mgagne longguang: openstack-puppet-modules-2013.2-9.1.el6.noarch.rpm is not maintained by our team. It is maintained by redhat-openstack.
02:05 longguang michchap, mgagne: please take a look at the link  , it describes my steps.  https://dpaste.de/iPBE . thanks very much
02:10 longguang or could you give me a step by step instruction
02:12 ozialien joined #puppet-openstack
02:14 fandi joined #puppet-openstack
02:39 longguang hi
02:59 bodepd mgagne: wrong channel :)
03:00 bodepd mgagne: who did that? That code seems terrible and wrong
03:00 mgagne bodepd: me =)
03:00 bodepd mgagne: why not just upgrade?
03:01 bodepd mgagne: or why not just vendor the dependent modules as a part of this project?
03:01 mgagne bodepd: it's just a solution I came up with when I thought I needed to get the version of a module in a manifest
03:02 mgagne bodepd: I'm sure you can come up with 100s of reasons why this could be useful =)
03:02 bodepd mgagne: I can think of 1000 more why I don't want that code in there :)
03:02 mgagne bodepd: haha
03:02 bodepd mgagne: it's funny to be back. I won't be doing as much Puppet stuff, but I'm def doing openstack for a while
03:03 bodepd mgagne: thanks for commenting on the specs
03:03 mgagne bodepd: np
03:03 mgagne bodepd: I'm currently having "fun" with wafflehaus
03:03 mgagne bodepd: https://github.com/roaet/wafflehaus
03:05 kitp joined #puppet-openstack
03:06 bodepd mgagne: wow, what a crazy project
03:06 bodepd mgagne: damn, I want specs to kill blueprints
03:06 bodepd mgagne: I don't see the use for them when all of the info can be in the spec
03:06 mgagne bodepd: specs have no status, you can't track progress.
03:07 bodepd mgagne: maybe move them to a completed directory when finished?
03:07 mgagne bodepd: why bother when you have a tool already?
03:07 bodepd mgagne: b/c I hate process
03:08 bodepd mgagne: I would rather have one tool for one job
03:08 bodepd mgagne: hold on, I can update the stuff I agree/concede to
03:08 mgagne bodepd: you have to understand why the tool was created in the first place
03:16 bodepd mgagne: b/c blueprints suck :)
03:16 bodepd mgagne: it's like trying to manage requirements in a wiki
03:17 dvorak where did the specs review get posted?
03:17 mgagne bodepd: I don't understand your example
03:17 bodepd https://review.openstack.org/#/c/96627
03:18 bodepd mgagne: the lack of a place to discuss things, and to have contextual discussions
03:18 bodepd mgagne: essentailly the thing that moving it to gerrit solves
03:18 mgagne bodepd: https://wiki.openstack.org/wiki/Blueprints
03:18 dvorak bodepd: thanks
03:19 bodepd mgagne: I conceded on all of your recomendations except the one to have the title before the guideline stuff
03:19 bodepd mgagne: I straignt up disagree :)
03:19 bodepd mgagne: I'm hesisitant on testing, but I conceded, it will at least be good to talk about how to test things
03:20 mgagne bodepd: without proper testing, you end up with ML2 in puppet
03:20 bodepd mgagne: I haven't been following.
03:20 bodepd mgagne: what happened?
03:20 mgagne bodepd: it doesn't work according to people opening bugs and posting fixes
03:20 bodepd mgagne: I guess that dan and I were the only ones doing integration testing, and we stopped
03:21 dvorak mgagne: you mean the OVS agent for ML2?
03:21 michchap mgagne: That requires integration testing to fix, which we don't have. There's no point talking about things that don't exist in a spec.
03:21 mgagne dvorak: I guess so =)
03:21 dvorak mgagne: it's not so much that it was broken, but that there was no code at all.
03:21 bodepd michchap: that was my point, but I conceded for now
03:22 bodepd mgagne: can you conceded on your ordering concerns, and let someone else hammer on the spec stuff?
03:22 mgagne michchap: we should mention integration tests (or the lack of) somewhere to warm people about the risk of merging untested stuff
03:22 dvorak not sure if other people have noticed, the puppet-ceph guys appear to actually be doing some
03:23 mgagne bodepd: that's what other specs use why bother changing? further more, ====\nwhatever\n==== is used as the document title, you can't have 2 document title.
03:23 michchap mgagne: Isn't every single spec just going to say, 'there's no public automated integration testing for this feature'
03:23 bodepd mgagne: I can fix that
03:23 bodepd michchap: yeah, someone needs to build out the framework for that and maintain it
03:24 mgagne michchap: if you don't mention it, people won't pay attention to it
03:24 michchap bodepd: you're at least partially on that this cycle aren't you?
03:24 bodepd potentially I'll do it, but it'll take 1-2 months before I can get it into a form where anyone can submit to it
03:24 bodepd michchap: I'm totally on it right now. Should I open a spec about the lack of integration testing :_
03:25 bodepd michchap: I'm close to splitting out the components I care about from openstack-infra/config
03:25 bodepd michchap: next step is probably ansible code so that I can deploy it in ec2
03:25 michchap mgagne: Awesome.
03:25 bodepd michchap: I'd love some friggen hardware though
03:25 michchap bodepd: I am also short of kit
03:26 bodepd michchap: with jenkins/zuul/vagrant, I could be testing in 2-3 weeks, but I need kit
03:26 michchap mgagne: sorry, I don't mean awesome. I'm not sure who the target audience is here. Who are we telling that there is no testing?
03:26 bodepd michchap: ourselves :)
03:27 sputnik13 joined #puppet-openstack
03:28 mgagne michchap: "Please discuss how the change will be tested." looks to be straight forward no? "I'm gonna write unit tests and hope it works in production" isn't a good answer.
03:28 dvorak mgagne: no, but might as well be honest about the state of things
03:29 mgagne dvorak: by hiding it?
03:29 dvorak no, I'm in favor of putting that in the spec.  perhaps reworded :)
03:29 mgagne dvorak: providing details on how it can be tested or a test scenario is a good start imo
03:30 mgagne dvorak: if there is nothing to say about tests in the spec, just say it: None
03:31 mgagne dvorak: the sections are there to force yourself to ask the question and think about it.
03:32 bodepd mgagne: what if I move these guidelines to their own doc?
03:33 mgagne bodepd: it's a template, you copy it somewhere and you have everything you need to fill it. Why split?
03:33 mgagne bodepd: why bother changing it? Just remove what does not apply to us, reword to our reality and be done.
03:37 bodepd mgagne: b/c that part is not part of the template
03:38 bodepd mgagne: and it was mixed in with the template, which I found to be counter-intuitive
03:38 mgagne bodepd: so see all hints and description on how to fill the template
03:38 bodepd mgagne: I tried removing it from the template part, but that does mess up the template format
03:38 bodepd mgagne: so I moved it to the README
03:38 bodepd mgagne: why are you so against that change?
03:38 mgagne bodepd: why changing it?
03:39 bodepd mgagne: b/c it's wrong, it mixes info that explains about something in with it's template
03:39 bodepd mgagne: so everytime I want to create a template, I have to remove that text
03:39 bodepd mgagne: b/c it's not part of the template
03:39 mgagne bodepd: jesus, so everything else in the template
03:40 bodepd mgagne: have a look at the latest revision
03:40 bodepd mgagne: README explains about the process, tempalte is just the tempalte
03:40 mgagne bodepd: I did, my emails are hooked to my brain
03:42 mgagne bodepd: the issue I see is that people filling up the template might not read the README or just glance over it
03:42 mgagne bodepd: having it in the template makes it self-contained and the user can't say he didn't read it because it was somewhere else
03:43 bodepd mgagne: what happens when people just disagree?
03:43 mgagne bodepd: they go home =) it's 11:45pm here
03:44 bodepd mgagne: good idea, we can resuem tomorrow
03:49 bodepd joined #puppet-openstack
03:51 sputnik13 joined #puppet-openstack
03:52 kkirkpatrick joined #puppet-openstack
03:52 sputnik13 joined #puppet-openstack
04:07 kitp joined #puppet-openstack
04:20 mmaglana joined #puppet-openstack
04:30 rickerc_ joined #puppet-openstack
04:40 ricardorocha joined #puppet-openstack
04:43 kitp joined #puppet-openstack
05:18 thumpba joined #puppet-openstack
05:34 rickerc joined #puppet-openstack
05:35 sputnik13 joined #puppet-openstack
06:16 kitp joined #puppet-openstack
06:27 tfz joined #puppet-openstack
06:38 gcha joined #puppet-openstack
06:42 bogdando joined #puppet-openstack
06:58 artem_panchenko joined #puppet-openstack
07:00 aldavud joined #puppet-openstack
07:02 rickerc joined #puppet-openstack
07:04 longguang joined #puppet-openstack
07:04 longguang Error: Could not set 'present' on ensure: Undefined boot protocol at 77:/etc/puppet/modules/openstack/manifests/profile/neutron/router.pp
07:04 longguang hi
07:05 longguang Execution of '/usr/bin/glance -T services -I glance -K na-mu-va -N http://192.168.18.129:35357/v2.0/ index' returned 1: Request returned failure status
07:05 longguang i encounter the 2 problems  when install network and storage.
07:17 qba73 joined #puppet-openstack
07:17 kitp joined #puppet-openstack
07:21 EmilienM good morning
07:57 saneax_-_ joined #puppet-openstack
08:03 snk joined #puppet-openstack
08:16 derekh_ joined #puppet-openstack
08:18 kitp joined #puppet-openstack
08:20 admin0 joined #puppet-openstack
08:21 aldavud joined #puppet-openstack
08:25 michchap EmilienM: morning :)
08:25 aldavud good morning!
08:25 EmilienM michchap: please tell me you will be able to attend the meeting on monday
08:31 michchap EmilienM: lol it's at 1am I might fall asleep
08:32 michchap EmilienM: I started going through the config-tools today to understand how they work
08:33 EmilienM michchap: next time, it could be very late for me I don't mind
08:34 EmilienM michchap: this post could help: http://techs.enovance.com/6838/deploying-openstack-the-enovance-way
08:34 michchap EmilienM: yeah I am following that, but I need to understand how the templating is being used
08:34 michchap EmilienM: like...understand how it works, not just the commands to run.
08:35 EmilienM michchap: the key stuff is the infra yaml repo
08:35 sanjayu joined #puppet-openstack
08:35 EmilienM which is not static at all
08:35 EmilienM i even think about creating a new one, more flexible
08:36 michchap EmilienM: so hopefully you can speak for me if I don't make the meeting. I explained what I'm trying to do to spredzy as well.
08:36 michchap infra yaml repo...like this? https://github.com/michaeltchapman/openstack-yaml-infra-3nodes-fullha
08:36 EmilienM michchap: well, I would prefer you around during the meeting
08:36 EmilienM michchap: yeah this one
08:36 EmilienM michchap: it's the one I use for my CI
08:37 michchap I think these are the equivalent of 'scenarios' in the data model, but they are controlling more than just puppet. I need to think about how we can compromise on that so we can both use the same format
08:38 michchap EmilienM: I'm going to keep working on it next week and hopefully it makes sense to me at some point.
08:39 EmilienM michchap: ok cool
08:40 michchap EmilienM: so the idea is your repo with your scenario is an 'input' to your deployment model. The builder contains the scenarios in it, which is nice in some ways because we collaborate on the scenarios, but it does make it so that we have to agree on what is in each scenario
08:40 michchap EmilienM: so I'm not sure which model is best. Maybe we can do both - have some default scenarios and the ability to load more from a downstream like enovance or aptira
08:41 EmilienM michchap: i'm very open to change my way to use tools
08:42 michchap EmilienM: I think we will have to change both of our tools to get this to work :)
08:42 michchap EmilienM: Have you tried using the builder before?
08:48 EmilienM michchap: no
08:48 EmilienM shame on me I know
08:49 michchap EmilienM: if you have time, try it out and then you can decide which bits you like and which bits you don't
08:49 michchap EmilienM: http://stacktira.aptira.com/docs/installation/environment.html
08:49 EmilienM ok
08:58 berendt joined #puppet-openstack
09:13 aldavud dachary: I feel I'm getting my personal edition of your class on upstream training :)
09:14 dachary aldavud: ahahah :-)
09:14 dachary you're the best contributor an upstream could dream of
09:16 aldavud thank you
09:17 aldavud but jokes aside - please continue to let me know where I should improve
09:19 kitp joined #puppet-openstack
09:24 toabctl joined #puppet-openstack
09:59 dgollub joined #puppet-openstack
10:07 hxgqh1987 joined #puppet-openstack
10:19 kitp joined #puppet-openstack
10:34 mmagr joined #puppet-openstack
10:45 aldavud_ joined #puppet-openstack
11:20 kitp joined #puppet-openstack
11:26 openstackgerrit joined #puppet-openstack
11:51 sanjayu joined #puppet-openstack
11:59 aldavud__ joined #puppet-openstack
12:01 dprince joined #puppet-openstack
12:09 aldavud joined #puppet-openstack
12:21 kitp joined #puppet-openstack
12:23 openstackgerrit joined #puppet-openstack
12:24 spredzy mornin' everyone. Could I get some reviews on https://review.openstack.org/#/c/96505/ ?
12:29 openstackgerrit David Gurtner proposed a change to stackforge/puppet-ceph: Initial classes/tests for a roles/profiles pattern  https://review.openstack.org/94195
12:34 aldavud ^ and thwarted by puppet 2.7 gate again :/
12:34 openstackgerrit Yanis Guenane proposed a change to stackforge/puppet-swift: Avoid duplication error when ringserver and storage are on the same node  https://review.openstack.org/96505
12:36 openstackgerrit Yanis Guenane proposed a change to stackforge/puppet-swift: Avoid duplication error when ringserver and storage are on the same node  https://review.openstack.org/96505
12:36 openstackgerrit David Gurtner proposed a change to stackforge/puppet-ceph: Initial classes/tests for a roles/profiles pattern  https://review.openstack.org/94195
12:36 dmsimard spredzy: I'll look later today
12:37 spredzy dmsimard, tanks
12:37 spredzy s/tanks/thanks
12:41 badiane_ka joined #puppet-openstack
12:45 aldavud dmsimard: finally params the way it should be https://review.openstack.org/#/c/94195/9
12:45 dmsimard aldavud: Yeah I saw when jenkins -1'd :p
12:46 dmsimard aldavud: I'll take a look later today
12:46 dmsimard aldavud: Discussed a few interesting solutions with dachary for the integration tests, we'll work something out :)
12:46 aldavud dmsimard: awesome :)
12:47 dvorak what are you guys using for integration tests?  beaker?
12:47 aldavud dmsimard: well yes. jenkins puppet 2.7 gate didn't like them :P
12:47 dmsimard dvorak: rspec-system for the time being, it's deprecated but we were already very involved into it when puppetlabs axe it
12:47 dmsimard axed*
12:47 dmsimard dvorak: We'll need to switch to beaker eventually I guess...
12:47 dachary dvorak: rspec::system . last I checked beaker does not have the ability to provision disks
12:47 dvorak where do those end up running at?
12:48 dvorak ah
12:48 dachary dvorak: on a machine I own. I've been looking for a generous sponsor willing to lend a server but no luck so far.
12:48 dvorak I've got some internal modules I'd like to do some integration testing on, and I just listened to the PL beaker podcast the other day, sounds interesting
12:48 dmsimard I think we can poke Hunner or hogepodge if anything is missing from beaker :)
12:48 prad joined #puppet-openstack
12:49 dachary dvorak: heat is another option, if your openstack provider has an icehouse version of it
12:49 dachary aldavud: the idea to speed up integration is to run ubuntu tests in parallel of centos tests
12:50 dachary the primary reason why centos tests take so long (1h) is because the default package repository is slow (45 minutes worth of download time)
12:51 aldavud dachary: so if we plug a mirror or a proxy we had a huge speedup?
12:51 aldavud s/had/could have/
12:52 rickerc joined #puppet-openstack
12:52 dmsimard dachary: It was in my plans to get in touch with Inktank to mirror the ceph repos eventually. Remember that CephFS use case I talked about? :)
12:53 dachary dmsimard: https://github.com/puppetlabs/beaker/issues/155 is the issue request to support disk provisioning
12:53 dachary dmsimard: yes :-)
12:53 dachary aldavud: yes, it will speed things up considerably.
12:54 aldavud_ joined #puppet-openstack
13:03 morazi joined #puppet-openstack
13:14 cbaesema joined #puppet-openstack
13:18 dgollub joined #puppet-openstack
13:22 kitp joined #puppet-openstack
13:54 aldavud_ joined #puppet-openstack
13:57 kitp joined #puppet-openstack
14:12 rwsu joined #puppet-openstack
14:22 shakamunyi joined #puppet-openstack
14:34 kkirkpatrick joined #puppet-openstack
14:34 rickerc joined #puppet-openstack
14:37 openstackgerrit joined #puppet-openstack
14:42 berendt joined #puppet-openstack
15:04 sputnik13 joined #puppet-openstack
15:11 mdorman joined #puppet-openstack
15:21 badiane_ka joined #puppet-openstack
15:47 ozialien joined #puppet-openstack
15:51 openstackgerrit Mike Dorman proposed a change to stackforge/puppet-keystone: Explicitly setting of PKI token signing cert  https://review.openstack.org/93598
16:00 dtalton joined #puppet-openstack
16:02 openstackgerrit David Gurtner proposed a change to stackforge/puppet-ceph: Support single node CS tests on CentOS 6.4  https://review.openstack.org/96215
16:02 openstackgerrit David Gurtner proposed a change to stackforge/puppet-ceph: Initial classes/tests for a roles/profiles pattern  https://review.openstack.org/94195
16:02 openstackgerrit David Gurtner proposed a change to stackforge/puppet-ceph: Checking for support of CentOS 6.4 in CI pool test  https://review.openstack.org/96217
16:05 cwolferh joined #puppet-openstack
16:17 yocum joined #puppet-openstack
16:20 starmer joined #puppet-openstack
16:22 rmoe joined #puppet-openstack
16:31 daneyon joined #puppet-openstack
16:36 dgollub joined #puppet-openstack
16:45 mmaglana joined #puppet-openstack
16:53 thumpba joined #puppet-openstack
16:58 thumpba joined #puppet-openstack
17:00 openstackgerrit Mike Dorman proposed a change to stackforge/puppet-keystone: Explicitly setting of PKI token signing cert  https://review.openstack.org/93598
17:04 ozialien joined #puppet-openstack
17:16 thumpba joined #puppet-openstack
17:17 openstackgerrit Chris Hoge proposed a change to stackforge/puppet-openstack-specs: Moving template for review.  https://review.openstack.org/96875
17:17 openstackgerrit A change was merged to stackforge/puppet-openstack-specs: Moving template for review.  https://review.openstack.org/96875
17:18 openstackgerrit Chris Hoge proposed a change to stackforge/puppet-openstack-specs: Template submitted for code review.  https://review.openstack.org/96876
17:22 aldavud puppet apply --report /etc/puppet/modules/ceph/tests/allinone.pp
17:22 aldavud puppet apply --report /etc/puppet/modules/ceph/tests/allinone.pp
17:22 aldavud puppet apply --report /etc/puppet/modules/ceph/tests/allinone.pp
17:22 aldavud sorry! that went to the wrong place
17:23 jkt joined #puppet-openstack
17:23 jkt hi there
17:24 jkt I'm already using the various stackforge modules along with the generic openstack wrapper for deployment, and it's really cool
17:24 jkt now there's another requirement, I'm supposed to switch to a "central Keystone" which is managed and run by somebody else
17:24 jkt what would be the easiest way of preventing these modules from realizing the various keystone_* resources?
17:25 dvorak keystone_user <| ensure => absent |>, etc
17:25 xarses joined #puppet-openstack
17:26 jkt I actually don't want to remove them from Keystone; the keystone is not even reachable anymore over that admin endpoint
17:26 dvorak sorry, that's wrong, keystone_user <||> { ensure => absent }
17:26 jkt I just want these manifests to stop caring about keystone_whatever resources altogether
17:26 dvorak oh, I suppose that's a good point, you just don't want them to do anything
17:26 jkt exactly
17:26 jkt not even executing service-list etc
17:27 dvorak can't you just not include nova::keystone::auth and the like?
17:27 jkt that's wrapped by a couple of layers of role/profile/resource boilerplate
17:28 jkt so yeah, I could just sed them away, but I was hoping for some well-contained overload switch
17:28 jkt originally I go that idea of using the enable parameter though hiera now that I know that I can override class params through that
17:29 jkt but it's just on a couple of places anyway, so I can do that as well, sure
17:31 aldavud there's always forking and removing/changing whatever you don't like. It's what we do
17:33 Mr_D joined #puppet-openstack
17:36 thumpba joined #puppet-openstack
18:07 hogepodge joined #puppet-openstack
18:11 sputnik13 joined #puppet-openstack
18:14 dgollub joined #puppet-openstack
18:56 aldavud joined #puppet-openstack
18:59 mjblack joined #puppet-openstack
19:01 mtl1 Hi, trying to install openstack module from github. On the step to do puppet-librarian, it gives me the following error: "Conflict between puppetlabs/apache/0.11.0 <git://github.com/puppetlabs/puppetlabs-apache#origin/0.x> and puppetlabs/apache (>= 1.0.0, < 2.0.0) <http://forge.puppetlabs.com>". To me that looks like it's trying to install apache modules from 2 different locations?
19:08 sputnik13 joined #puppet-openstack
19:12 sputnik13 joined #puppet-openstack
19:13 sputnik13 joined #puppet-openstack
19:15 admin0 joined #puppet-openstack
19:18 meylor joined #puppet-openstack
19:20 meylor left #puppet-openstack
19:26 guimaluf joined #puppet-openstack
19:31 Hunner Huh. mtl1 Is this puppetlabs-openstack 3.x?
19:36 mtl1 Hunner: https://github.com/stackforge/puppet-openstack
19:38 mtl1 I do the git clone, cd to openstack, do the gem install, and then get that when I do "librarian-puppet install --path ../" with —verbose tacked on.
19:43 starmer joined #puppet-openstack
19:54 kkirkpatrick joined #puppet-openstack
20:00 kkirkpatrick joined #puppet-openstack
20:17 francois joined #puppet-openstack
20:20 social__ joined #puppet-openstack
20:20 tdb_ joined #puppet-openstack
20:23 aldavud joined #puppet-openstack
20:23 aldavud_ joined #puppet-openstack
20:24 aldavud mtl1: i would recommend using librarian-puppet-simple instead of librarian-puppet
20:24 aldavud_ mtl1: and then do the following:
20:25 aldavud cp Puppetfile ../ && cd .. && librarian-puppet install
20:25 aldavud_ left #puppet-openstack
20:39 admin0 joined #puppet-openstack
20:44 admin0 joined #puppet-openstack
20:56 kkirkpatrick joined #puppet-openstack
20:58 rstarmer joined #puppet-openstack
21:01 hogepodge joined #puppet-openstack
21:18 cwolferh_ joined #puppet-openstack
21:19 aldavud_ joined #puppet-openstack
21:51 sputnik13 joined #puppet-openstack
21:55 dgollub joined #puppet-openstack
22:00 meylor joined #puppet-openstack
22:05 aldavud_ joined #puppet-openstack
22:23 xarses joined #puppet-openstack
22:32 openstackgerrit joined #puppet-openstack
22:36 openstackgerrit joined #puppet-openstack
22:42 mmaglana joined #puppet-openstack
22:45 mmaglana joined #puppet-openstack
22:51 admin0 joined #puppet-openstack
23:38 ozialien joined #puppet-openstack
23:39 rstarmer joined #puppet-openstack
23:52 mmaglana joined #puppet-openstack

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