Perl 6 - the future is here, just unevenly distributed

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

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

All times shown according to UTC.

Time Nick Message
00:21 digicloseup joined #puppet-openstack
01:19 rongze joined #puppet-openstack
01:50 xingchao joined #puppet-openstack
01:56 rongze joined #puppet-openstack
01:57 rongze joined #puppet-openstack
01:59 rongze_ joined #puppet-openstack
02:05 e1mer joined #puppet-openstack
03:23 rongze joined #puppet-openstack
03:31 tnoor1 joined #puppet-openstack
03:54 e1mer joined #puppet-openstack
04:32 e1mer joined #puppet-openstack
04:34 tnoor2 joined #puppet-openstack
04:35 j8kster joined #puppet-openstack
04:52 j8kster left #puppet-openstack
04:53 rongze joined #puppet-openstack
05:25 xingchao joined #puppet-openstack
06:04 e1mer joined #puppet-openstack
06:26 e1mer joined #puppet-openstack
07:03 EmilienM good morning here
07:53 michchap joined #puppet-openstack
08:02 dvanders joined #puppet-openstack
08:10 mattymo joined #puppet-openstack
08:47 bogdando joined #puppet-openstack
08:58 derekh joined #puppet-openstack
09:08 EmilienM fc__: i have a doubt about https://review.openstack.org/#/c/57790/
09:08 EmilienM and if you could also review https://review.openstack.org/#/c/58134/
09:08 fc__ morning in there
09:08 EmilienM thank you :)
09:09 fc__ EmilienM: what kind of doubt ? Did you write it inebriated ?
09:09 EmilienM fc__: \o/, no but i just want to be sure going on the right way
09:11 mattymo EmilienM, our cinder module has an option to create LVM if you specify a physical volume
09:12 mattymo but this adds an extra dependency
09:12 EmilienM mattymo: could be great to have it maybe
09:14 mattymo okay great. it looks like we use a common stackforge module
09:15 mattymo puppetlabs-lvm
09:15 mattymo oops puppetforge
09:42 dvanders_ joined #puppet-openstack
10:00 marun joined #puppet-openstack
10:51 mattymo dvanders, ping
11:13 rongze joined #puppet-openstack
11:54 mattymo I'm looking at puppet-cinder and I see you don't set DEFAULT/bind_host value
12:14 rongze joined #puppet-openstack
12:20 michchap joined #puppet-openstack
12:24 rongze joined #puppet-openstack
13:27 bcrochet joined #puppet-openstack
13:29 bauzas joined #puppet-openstack
14:01 dprince joined #puppet-openstack
14:04 rongze joined #puppet-openstack
14:07 morazi joined #puppet-openstack
14:15 rharrison joined #puppet-openstack
14:18 bauzas1 joined #puppet-openstack
14:31 rongze_ joined #puppet-openstack
14:50 mjblack joined #puppet-openstack
14:52 mjblack joined #puppet-openstack
15:21 dmsimard joined #puppet-openstack
15:48 thumpba joined #puppet-openstack
16:06 otherwiseguy joined #puppet-openstack
16:28 tnoor1 joined #puppet-openstack
16:29 dwt2 joined #puppet-openstack
16:31 tnoor2 joined #puppet-openstack
16:33 rharrison joined #puppet-openstack
17:02 xarses joined #puppet-openstack
17:06 angdraug joined #puppet-openstack
17:06 piliman974 joined #puppet-openstack
17:36 rmoe joined #puppet-openstack
17:45 brdude joined #puppet-openstack
18:22 xarses good morning stackers
18:23 dmsimard xarses: What timezone are you in!? :P
18:23 xarses dmsimard: the best one =)
18:23 xarses dmsimard: sunny silicon valley, GMT -8
18:23 dmsimard xarses: Eh, -5 here. Where it's cold right now.
18:26 xarses GMT -5 or -5 degrees?
18:26 * xarses grins
18:31 dmsimard both !
18:31 dmsimard Actually -18 C with wind factor
18:32 xarses 13 C here now
18:40 snuffop left #puppet-openstack
19:11 rongze joined #puppet-openstack
19:21 odyi joined #puppet-openstack
19:36 rmoe joined #puppet-openstack
19:44 rongze joined #puppet-openstack
19:50 dachary :-)
19:54 xarses dachary: ping ...
19:54 xarses =)
19:55 xarses I've poked around for some rspec-system examples
19:55 xarses most that i have been able to find are incredibly simple
19:56 xarses they mostly avoid doing distro centric tests
19:57 xarses so to me that raises, should we bother testing the repo's? or test that we can install packages from them?
20:03 dachary xarses: pong
20:04 otherwiseguy joined #puppet-openstack
20:04 toMeloos joined #puppet-openstack
20:04 dachary xarses: because if you make a typo in the repo it won't work ?
20:05 xarses yes, but then it will fail to install the package from said repo yes?
20:05 dachary yes
20:05 dachary and only integration tests can pick this
20:05 dachary I admit that for repo the value added is not very high
20:05 dachary but as we move to mon + osd it will become increasingly important
20:08 xarses ya, but i think package {'ceph': ensure => present } and testing 'puppet resource package ceph' would be better and avoid coding for each distro
20:09 dmsimard xarses: I think the point is that we'll eventually need to test different things on different distros anyway
20:10 dmsimard xarses: We'll hit this problem one day or another
20:20 dmsimard dachary: Not saying it's preferable but I did some reading on https://github.com/puppetlabs/rspec-system
20:20 dmsimard dachary: We could always override prefabs to include an up-to-date Wheezy box
20:20 dmsimard dachary: Not entirely sure I want to rely on a box made available through dropbox, though :) http://www.vagrantbox.es/
20:21 dmsimard dachary: I would had liked to poke hoge about what we could do to get things moving at puppetlabs for updating the prefabs but he's not around
20:21 xarses dmsimard: the problem i have currently is that I don't see a reasonable method to do distro specific tests, I'd like to see a method like "use set 'centos6-4-x64' do ..."
20:22 openstackgerrit Doug Schaapveld proposed a change to stackforge/puppet-horizon: Adding endpoint type parameters  https://review.openstack.org/58374
20:22 xarses dmsimard: otherwise, i dont see how we know if that set is even used in the tests
20:22 xarses or, I'm still confused on how this works
20:24 dmsimard xarses: Wouldn't be able to tell you either, I haven't worked much with it - maybe it runs the tests under every set ?
20:27 xarses according to https://review.openstack.org/#/c/56427/1/README.md L74, Loric had to loop through them
20:27 dmsimard xarses: Here: http://www.rubydoc.org/github/​puppetlabs/rspec-system/frames
20:27 dmsimard "So if you wanted to run an alternate nodeset you could use: RSPEC_SET=nodeset2 rake spec:system"
20:28 dmsimard Oh, I guess I'm late to the party, he already wrote that :p
20:29 dmsimard Hmm, I don't know. The tests probably don't need to be distro specific since the specificity is handled by puppet ?
20:29 xarses thats what i was trying to get at
20:29 xarses we could mostly avoid the problem
20:29 dmsimard I mean, the tests could and should be run on different distributions
20:30 xarses unless one of the commands is distro centric and puppet cant do it
20:30 dmsimard But the tests themselves probably should be agnostic
20:31 xarses thats what i've been able to come up with, the tests need to be made as os generic as possible
20:31 xarses using as many puppet methods as possible
20:31 dmsimard Can you try and see what you can come up with ?
20:31 xarses and hopefully we can avoid if redhat everywhere
20:32 xarses Ya, it probably wont look like much yet
20:32 xarses need a monitor or something to be more constructive
20:33 dmsimard We need to build incrementally :)
20:34 mjblack joined #puppet-openstack
20:35 mjblack joined #puppet-openstack
20:36 xarses dmsimard: i know, I'm just saying it wont look like much
20:37 dmsimard xarses: I'm okay with that. If it sets up the apt repo on debian and the yum repo on redhat i'll be happy :)
20:42 toMeloos hi guys, small question: what is the current status of puppet-ceph on stackforge? is it in development or (partially) ready for use?
20:42 dmsimard toMeloos: It's not ready for use, it's in early development
20:42 dalgaaf_ not ready for use yet
20:42 toMeloos okay
20:43 dmsimard toMeloos: There's other resources, listed here: https://wiki.openstack.org/wiki/Puppet-openstack/​ceph-blueprint#Related_tools_and_implementations
20:43 xarses toMeloos: there is a list of other projects
20:43 toMeloos so stick to the enovance code for now?
20:43 xarses toMeloos: what dmsimard said
20:44 dmsimard toMeloos: I personally use and contribute to https://github.com/TelekomCloud​/puppet-ceph/tree/rc/eisbrecher right now.
20:45 xarses toMeloos: i use https://github.com/Mirantis/fuel/t​ree/master/deployment/puppet/ceph
20:45 dmsimard toMeloos: The plan is to take all the good parts of various puppet-ceph implementations and centralize them in the stackforge initiative, and then to maintain it as upstream
20:45 toMeloos aha okay yes i looked at that one too. liked it had RadosGW support, but what is the status of that branch?
20:46 toMeloos the TelekomCloud RC tree I mean
20:46 rongze joined #puppet-openstack
20:46 dmsimard toMeloos: It's able to setup radosgw and radosgw users right now, I recently pushed keystone integration as well
20:47 xarses ditto or mirantis, but uses ceph-deploy for the osd / mon deployment
20:47 toMeloos nice
20:48 xarses s/or/for
20:48 toMeloos so both the Eisbrechter and the Fuel modules are mature/stable and just a different way to the same result?
20:50 dmsimard They're probably the most up-to-date and maintained branches
20:50 xarses Fuel's module is stable, I think we closed the open bugs on it two weeks ago week
20:50 xarses we will have live openstack migrations using ceph soon, probably in fuel 4.0
20:53 toMeloos sorry, hate to say it but we abandoned fuel...
20:57 toMeloos the fuel ceph code looks really good. I'll give you that!
20:57 xarses toMeloos: I'm sorry to hear that, would you mind discussing why PM preferred since it's off topic for this channel
20:59 toMeloos sure
21:09 marun joined #puppet-openstack
21:19 SabrinaVernalde joined #puppet-openstack
21:46 rongze joined #puppet-openstack
22:11 mjblack joined #puppet-openstack
22:26 pabelanger Why does puppetlabs-keystone 2.2.0 tags not exist in git? https://github.com/stackfor​ge/puppet-keystone/releases
22:26 pabelanger but it lives on the forge https://forge.puppetlabs.co​m/puppetlabs/keystone/2.2.0 ?
22:27 pabelanger What is the diff between the releases?
22:31 xarses pabelanger: not sure, but that probably makes them seperate repo's
22:32 xarses the puppet openstack group is mostly maintained as puppet-<package> on github.com/stackforge
22:32 pabelanger xarses, do you know what the release process is for puppet-openstack and publishing to puppet forge?
22:33 pabelanger https://forge.puppetlabs.com/puppetlabs/keystone references stackforge as the repo location
22:33 xarses i know nada about any forge publishing we may do. As to our releases, they should be stable/grizzly, stable/havana
22:34 pabelanger I suspect it is a manually process somebody does to release them to puppetforge
22:34 xarses version numbers are marked on occasion, but each module is probably on it's own version
22:35 xarses you're probably best dropping a line on the puppet-opestack list
22:36 xarses puppet-openstack@puppetlabs.com
22:37 pabelanger Yup, on the list
22:38 pabelanger figured I ask here first
22:38 pabelanger Also moving the discussion into -infra to get there opinions on a release processes.
22:42 michchap EmilienM: stackforge/puppet_openstack_builder was added yesterday, which is the new version of CiscoSystems/openstack-installer
22:42 sputnik13 joined #puppet-openstack
22:42 EmilienM michchap: that's awesome
22:42 sputnik13 sweeeeet
22:42 michchap EmilienM: I've removed some of the Cisco-centric defaults, but there's a bit more work to do to make it more neutral
22:43 michchap I have a jenkins job using it that's now passing, but that's based on scenariobuilder - I haven't tested the vagrant scripts yet.
22:43 sputnik13 I'm confused, is the puppet-openstack module going to be deprecated or not?
22:43 sputnik13 https://forge.puppetlabs.com/puppetlabs/openstack
22:43 sputnik13 that says it is
22:43 sputnik13 https://github.com/stackforge/puppet-openstack
22:43 sputnik13 that has no mention of it
22:43 EmilienM michchap: it's a bit late here, i'll have a look tomorrow for sure, we are really interested by this.
22:44 sputnik13 anyone know?
22:45 michchap sputnik13: puppet-openstack in its current form will certainly be deprecated
22:45 sputnik13 michchap: what does that mean?  is there somewhere I can read about the future?
22:46 michchap sputnik13: There was a fairly long session at the design summit. https://etherpad.openstack.or​g/p/icehouse-puppet-openstack
22:48 michchap sputnik13: Chris Hoge from Puppetlabs is I think going to replace it with a simple version that could be used as an introduction to the puppet openstack modules, while we're looking at using Dan Bode's work on puppet_openstack_builder (formerly openstack-installer) for more complex deployments.
22:50 rongze joined #puppet-openstack
22:50 sputnik13 michchap: I see...  so puppet-openstack becomes a beginner's interface to openstack and puppet_openstack_builder becomes the power user's interface to openstack?
22:52 michchap sputnik13: That's a good way of putting it.
22:53 sputnik13 https://github.com/stackfor​ge/puppet_openstack_builder
22:53 sputnik13 is this the puppet_openstack_builder you're referring to?
22:54 michchap yep, but it only went upstream yesterday and had to go through a rename, so I'm cleaning up the doc and scripts to reflect that now.
22:55 sputnik13 oh wait, I just made the connection, this is your repo :-D
22:56 michchap It was formerly CiscoSystems/openstack-installer, which I think was formerly my repo.
23:00 sputnik13 michchap: is the module ready for general use or is it under development
23:04 antar joined #puppet-openstack
23:04 antar hello everyone -
23:05 michchap sputnik13: I guess it depends how comfortable you are with Puppet, and whether you have time to learn it. I would say wait at least a few days while I focus on testing the user experience and fixing docs now that I have the testing part working.
23:05 antar got a problem hoping someone can help - can't seem to find an answer on it.  I installed RDO openstack, got everything running started an instance I get error, ran nova list then nova show and i get this error {u'message': u'Invalid console type spice-html5', u'code': 400
23:05 michchap sputnik13: I'm also going to send out a mail to the list when I think it's ready for more general use, possibly with a screencast or longer tutorial on how to get started.
23:06 sputnik13 michchap: I see, thanks for the warning, I guess I'll download to my machine and experiment with it a bit...
23:06 sputnik13 michchap: which list?
23:06 michchap the puppet-openstack mailing list
23:06 sputnik13 michchap: I'm not on that list, I need to subscribe :)
23:07 antar any ideas?
23:08 michchap antar: I've never seen that error before, sorry
23:09 antar michchap: never a good sign :) - install went flawless too, hm..
23:11 antar by default does it use spice-html5? anyway to force the VNC?
23:14 antar you won't believe what it was
23:14 antar simply put - yum install spice-html5
23:15 antar and sometimes its just that simple - so much for that.
23:20 michchap a missing dependency on the compute node?
23:22 antar yeah
23:23 antar okay now i have the next error - {u'message': u'No valid host was found. '
23:23 antar I am not on a bare metal install - so far everything in find is on the baremetal
23:23 antar both nodes are up the master and the compute- all services are running, how do i debug that one?
23:23 michchap do a nova service-list
23:23 antar yep - all are up
23:24 michchap did you try to boot ubuntu with a tiny size VM?
23:24 antar i got the consoleauth, scheduler, conductor and cert all on one server up
23:24 antar and the nova-compute node on another.
23:24 dtalton2 joined #puppet-openstack
23:24 antar i am actually doing a centos image - i gave it 20gb
23:24 michchap or anything that isn't cirros?
23:25 michchap so you're using m1.small or m1.medium?
23:25 antar m1.small | 2GB RAM | 1 VCPU | 20.0GB Disk
23:25 michchap ok
23:25 michchap That error means the scheduler couldn't fit the flavor you asked for onto a compute host
23:26 michchap it can also mean that the image/flavor combination wasn't right, which is why I asked
23:26 antar hm.. let me try another image
23:28 michchap I may be a bit underequipped to help you - I've never used RDO
23:32 antar its pretty much a openstack install just out of their repo
23:32 antar nothing fancy is done to it
23:32 antar short of configurations for a rh base
23:36 antar tried a different image - used fedora no go
23:36 antar same issue
23:46 michchap what does the log say for nova-scheduler
23:51 rongze joined #puppet-openstack
23:52 antar let me check
23:53 antar i actually don't see any log for nova-scheduler
23:53 michchap That's very strange
23:53 antar there is no nova-scheduler.log
23:53 antar yeah
23:56 antar I went to RDO because i couldn't get openstack to work on ubuntu - it would not pick up the MAAS server just kept crashing... now stuck at another point -

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