15:00:43 #startmeeting 15:00:44 Meeting started Tue Aug 7 15:00:43 2012 UTC. The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:59 #topic Openstack Compute for Hyper-V 15:01:23 morning everyone 15:01:46 we'll start the meeting today by discussing the current status of the integration work for folsom 15:02:43 man 15:02:49 alessandro isn't on the channel yet 15:02:58 hmm 15:03:07 alexpilotti: there you are 15:03:16 hi everybody 15:03:16 alexpilotti: is pedro going to join? 15:03:21 I guess so! 15:03:24 1s 15:03:31 alexpilotti: thx 15:04:25 alexpilotti: actually I wanted to have dan bode on the channel as well 15:04:33 primeministerp: pedro says that he's going to be a bit late due to corporate policies w IRC firewalling 15:04:44 alexpilotti: ok 15:04:53 primeministerp: do u know of any HTTP based client? 15:05:05 alexpilotti: actually i did 15:05:08 one sec 15:05:35 http://webchat.freenode.net/ 15:06:19 ociuhandu: morning 15:06:31 morning all 15:06:36 guess we'll wait a couple for pedro as well 15:06:46 primeministerp: great news live migration ported to Folsom :-) 15:06:55 primeministerp: finished now 15:06:59 alexpilotti: awesome! 15:07:01 alexpilotti: ok 15:07:10 while we have some folks on 15:07:23 pnavarro: pedro! 15:07:27 perfect 15:07:28 hi all ! 15:07:31 primeministerp: we have to verify / port volumeops only, for the rest all the features have been ported 15:07:31 wish jordan was here 15:07:32 sorry for the delay 15:07:38 pinged him but no love 15:07:41 ok let's finally begin 15:07:51 #topic Statuc of Folsom integration 15:07:57 #topic Status of Folsom integration 15:08:16 So there's been a lot of activity from alexpilotti recently 15:08:38 alexpilotti: stop me if i'm incorrect 15:08:38 and from pnavarro ! 15:08:43 and from pnavarro ! 15:08:59 ;-) 15:09:00 so the current status of hyper-v is as follows 15:09:10 the code has been refactored 15:09:17 the moc driver is complete 15:09:34 the following functions have been ported to folsom 15:09:37 start 15:09:39 stop 15:09:42 pause/unpause 15:09:45 suspend/resume 15:09:56 live-migration 15:10:03 primeministerp: snapshot 15:10:07 snapshot as well 15:10:14 actually all of them, we have to test only volumes 15:10:22 o execelent 15:10:44 pnavarro: have you tested it at all? 15:10:46 pnavarro: do you think you could have time to test the volume stuff on Folsom? 15:11:00 pnavarro: I will setup a folsom env today 15:11:03 it's on my list 15:11:07 test as in "verify" 15:11:16 alexpilotti: I should be able to verify 15:11:24 alexpilotti: can you get me a pip freeze? 15:11:25 that'd be nice, if I have a setup to tested it as fast as possible 15:11:35 pnavarro: if you have devstack vm 15:11:42 you can have a vhd for your iscsi volume 15:12:00 i have small one i use just to verify 15:12:06 however that was essex 15:12:11 pnavarro: you can keep all your existing environment, you only need a devstack controller 15:12:21 ok, that'd be easy then 15:12:27 so volume is the last key piece to verify 15:12:52 alexpilotti: do we have any other bugs that aren't currently addressed? 15:13:12 primeministerp: no, we are set 15:13:16 perfect 15:13:22 alexpilotti: and what's the status on the unit tests? 15:13:46 primeministerp: it's the next (and last step) that I can start now 15:13:53 alexpilotti: perfect 15:14:05 primeministerp: I was actually discussing w Pedro about some technical stuff 15:14:12 alexpilotti: perfect 15:14:15 let's discuss then 15:14:22 one funny thing. I don't see vmware tests in Folsom 15:14:41 maybe they'll be pulled from the project as well 15:14:59 coming to the techical things, unit tests require some fake classes to emulate dependencies 15:15:11 we call them stubs, fakes or mocks 15:15:19 vishy: any response to the lack of vmware tests in Folsom? 15:15:23 depending on how complex tthey are 15:15:56 alexpilotti: ok 15:16:24 so what I don't get is how they inject those fakes in teh xen tests for example 15:16:25 alexpilotti: so that will be the formal naming convention? 15:16:45 how are they currently doing it in kvm? 15:16:49 primeministerp: for what? 15:16:56 unit tests 15:17:01 injecting fakes 15:17:26 primeministerp: false alarm. I just found the vmware tests 15:17:33 alexpilotti: perfect 15:17:44 vishy: nevermind they've been found 15:17:55 who knows in what directory I looked 10' ago! 15:18:04 alexpilotti: hehe 15:18:14 so you are set there now/ 15:18:16 now/ 15:18:29 pnavarro_: pedro's back 15:18:33 ok 15:18:38 alexpilotti: let's continue then 15:18:51 alexpilotti: is there enough info there to help you? 15:18:53 my connection is not very stable 15:19:08 pnavarro_: i see 15:19:20 wo from what I see, they just set up the entire connection against the real hypervisor! 15:19:35 or, I just miss something 15:20:11 that's why I'm going to shoot a nosetest against them right now and see :-) 15:20:17 alexpilotti: hehe 15:20:20 alexpilotti: perfect 15:20:38 in Essex I had the issue that tests were based on a custom runner.py 15:20:48 which had a dependency on Unix 15:21:03 you are shooting your tests from Windows them? 15:21:09 yep 15:21:32 I mean, if they are completely mocked, it's just plain python code 15:21:45 that's true 15:21:48 if not, I'll get a storm of errors :-) 15:22:37 ok 15:22:46 should we move on to the next topic? 15:22:55 alexpilotti: keep me on the threads 15:23:28 ok then, moving on 15:23:39 #topic Status of the Hyper-V ci 15:23:52 so lots have happend in a week 15:24:13 I have secured a dedicated network connection and firewall resources 15:24:18 those are now active 15:24:53 zuul has been setup and configured however is currently not actively ruunning 15:24:55 ERROR: Failure: ImportError (No module named lxml) 15:25:09 alexpilotti: sounds like another dep issue 15:25:16 no? 15:25:20 yep, that's it 15:25:30 so continuing 15:26:00 the implicit question was: do you guys remember where to get a binary lxml? 15:26:04 the hyper-v jenkins keys have been supplied to mtaylor and I have succesfully tested the zuul connectivity 15:26:22 alexpilotti: no 15:26:35 alexpilotti: what's it asking for specifically 15:27:07 lxml 15:27:14 pip install lxml 15:27:19 p and configured however is currently not actively ruunning 15:27:22 just waiting for the result 15:27:34 i see the egg for 2.2 15:27:51 http://pypi.python.org/pypi/lxml/2.2 15:27:59 it tries to compile it and it fails 15:28:08 on what 15:28:16 I remembered correctly that we need a precompiled Win32 copy 15:28:51 even 2.3: http://pypi.python.org/pypi/lxml/2.3/ 15:28:57 http://www.lfd.uci.edu/~gohlke/pythonlibs/ 15:29:00 found it 15:29:37 perfect 15:29:44 ok 15:29:49 so 15:29:55 on w/ ci discussion 15:30:47 I have made the decision to put the hyper-v chef on hold to focus on puppet for the ci infrastructure to keep in line with core project 15:31:02 ERROR: Failure: ImportError (No module named crypt) 15:31:29 Mcrypt? 15:31:33 that makes sense 15:31:55 anyone have any issues with that 15:32:12 on the puppet note, i have discussed with dan bode of puppet labs 15:32:30 we will hopefully engaging cern to assist in the effort 15:32:58 i was hoping jose would be on the meeting today, hopefully he sees the minutes 15:34:36 additionally the current ci controller infrastructure will be moved to devstack with my goal of using the same ci setup as core for the hyper-v 15:34:39 bits 15:34:45 pnavarro: alexpilotti any objections? 15:34:56 primeministerp: it's ok for me 15:35:00 ok perfect 15:35:02 from primeministerp bootstrap: http://stackoverflow.com/questions/6158125/is-there-an-m2crypto-installer-for-windows-7-64-bit 15:35:11 ops: http://chandlerproject.org/pub/Projects/MeTooCrypto/M2Crypto-0.21.1.win32-py2.7.msi 15:35:29 alexpilotti: i'll need your pip freeze so i create a new bootstrap 15:35:40 oki 15:35:53 alexpilotti: also I've created a openstack-puppet-hyper-v public repo 15:36:04 alexpilotti: i'm going to start putting things like that there 15:36:24 cool 15:36:31 https://github.com/ppouliot/openstack-puppet-hyper-v 15:36:33 i believe 15:36:58 #link https://github.com/ppouliot/openstack-puppet-hyper-v.git 15:37:07 that will be the starting point 15:37:22 pnavarro: alexpilotti anything else to add 15:37:37 keep me on the dialog between you to 15:37:49 pnavarro: i'll email you as soon as i'm able to test volume 15:38:01 alexpilotti: keep plugging on the unit tests 15:38:04 ok 15:38:09 last topic 15:38:18 #topic folsom submission 15:38:37 alexpilotti: what's a good estimate for the push of the code upstream? 15:38:43 primeministerp: pnavarro got disconnected 15:38:56 alexpilotti: ok 15:38:58 pnavarro: he asks: what about docs integration on Folsom 15:39:16 pnavarro_: back w/ us 15:39:20 do docs 15:39:23 er 15:39:23 yes, primeministerp we should do doockbookize 15:39:30 we need to do docks 15:39:33 pnavarro_: ok 15:39:45 pnavarro_: do you know how to do that or where to begin? 15:39:54 pnavarro_: i'm new to it 15:40:01 there are the official integration docs from openstack 15:40:12 pnavarro_: do you have link 15:40:14 Oxygen is an XML editor where the company supports work on open source projects, so we can get you a license. 15:40:17 * primeministerp adds to his reading list 15:40:25 #link http://wiki.openstack.org/Documentation/HowTo 15:40:27 annegentle: perfect! 15:40:32 thanks annegentle ! 15:40:52 Oxygen is really cool, I've used it in the past 15:40:56 we never did delete the hyper v chapter, so it's still in the openstack-manuals GitHub repo. You can update that with the latest and then do an xi:include to put it in the Compute Admin manual 15:41:07 pnavarro_: good, I find it really comfortable for authoring 15:41:22 annegentle: on that note 15:41:34 annegentle: what about restoring the hyper-v column on the wiki 15:41:44 ouch: crypt is Unix only 15:41:47 annegentle: is it possible to get some help w/ that 15:41:53 primeministerp: on the first page? it's sort of too detailed for the first page 15:42:05 primeministerp: or do you mean the hypervisor page? 15:42:10 annegentle: the supported hypervisors matrix 15:42:42 primeministerp: got it. you should be able to go to a previous edit of it and pick up the changes? 15:42:59 still learning, just don't want to break it 15:43:11 primeministerp: yeah try the GUI editor for the table 15:43:16 primeministerp: but yes it's touchy 15:43:33 annegentle: perfect, ok to ping you if I have issues? 15:44:17 annegentle: who to address to have the oxygen license? 15:45:29 pnavarro_: i figure docs will be a big part of our f4 push 15:46:00 ok, after F3 then 15:46:02 annegentle: if you could get us that info re: the oxygen license, that would be great, feel free to email to directly to me and I can share w/ the team. ppouliot@microsoft.com 15:46:13 pnavarro_: we need to get what we have in first 15:46:36 alexpilotti: pnavarro_ ok on that note then, i'm going to end it 15:46:43 anything else to add before i do? 15:46:54 alexpilotti: pnavarro_ ? 15:47:02 nothing to add... 15:47:12 ok great work guys 15:47:18 i appreciate all the effort 15:47:23 on that note 15:47:31 #endmeeting