16:02:08 #startmeeting hyper-v 16:02:09 Meeting started Tue Sep 2 16:02:08 2014 UTC and is due to finish in 60 minutes. The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:12 The meeting name has been set to 'hyper_v' 16:02:19 hey everyone 16:02:30 hi all.. 16:02:41 hi there 16:02:42 alexpilotti: hey now 16:03:05 ociuhandu: hi tavi 16:03:08 luis_fdez: hi luis 16:03:16 primeministerp: lazy_prince is interested in how to test the Windows disk image builder 16:03:22 o nice 16:03:34 we can discuss that too 16:04:12 alexpilotti: do we want to start there? 16:04:18 just started the conversation on #openstack-hyper-v and the timing was perfect for bringing it to the attention at the meeting 16:04:22 well.. we can discuss that at the end.. after all formal agenda is done.. 16:04:24 I suggest so 16:04:33 lazy_prince: we can start here 16:04:56 #topic windows-disk-image-builder 16:05:29 alexpilotti: is the discussion still at "where it should ruN" 16:05:37 okay.. so right now, openstack is resisting the tool bcoz we dont have testing framework for wordows related stuff there.. 16:05:52 lazy_prince: understood, it's kinda required 16:06:09 lazy_prince: so you'd like us to pick up those tests in our ci? 16:06:31 so i checked with google and there were some linux alternatives available for DISM, WIM etc.. but could not find anything for powershell... 16:06:56 meaning if you wanted to run the image creation on linux only 16:07:18 lazy_prince: there are a bunch of alternatives, but those won’t have MSFT support, which might be a concern 16:07:22 yes. i guess, then only openstack will agree for its adoption.. 16:07:46 ale: yup. i agree 16:08:33 but i wanted to have minimal tests in openstack CI using linux tools and a full fleged tests using HyperV ci.. 16:09:05 so that it gets adopted as well as tested too.. 16:09:14 does it makes sense..? 16:09:23 yeah thinking 16:10:11 so do you know what will be needed to adquately test it? 16:11:02 lazy_prince: ^ 16:11:11 yup.. we currently plan to put the code on stackforge. I hope that should not be an issue for integrating with HyperV CI.. 16:11:41 and so we just need the tool to create a basic image for now and then test it on a VM.. 16:12:15 later on, we can extend the tests as and when we extend the tool.. 16:13:30 now the question is where do i start.. 16:14:42 lazy_prince: so my only issue here 16:14:58 is that we currently already have a set of tools which create windows images 16:15:04 for anything 16:15:19 which we currently consume 16:15:35 and would ideally need to test w/in our ci first 16:15:54 lazy_prince: would it make sense to discuss combining our efforts there? 16:16:08 aha.. thats okay.. i am not asking to update your tests.. 16:16:21 lazy_prince: it's not a matter of updating our tests 16:16:21 but all i am asking it to test it.. 16:16:33 we already have stuff for creating windows images 16:16:41 i.e. a windows-image-builder 16:17:03 now we create images as virtual 16:17:17 but they can be preped for physical w/ the exact same code we already ahve 16:17:54 ok i get it.. 16:18:07 lazy_prince: I'm looking at it from the perspective it makes sense to collaborate around the one tool which we already use in our ci 16:18:26 lazy_prince: and not duplicate efforts 16:18:38 I can take a look at it if there is a public repo available.. 16:18:55 yes there is 16:19:03 however, my goal was to create a tool to generate Image without standing up a VM.. 16:19:06 lazy_prince: https://github.com/cloudbase/windows-openstack-imaging-tools 16:19:11 alexpilotti: do you mind sending it to them 16:19:13 lazy_prince: how? 16:19:19 primeministerp: ^ 16:19:20 lazy_prince: that's practically impossible 16:19:38 lazy_prince: you'd have to dd it off the hw 16:19:41 using powershell DISM 16:20:13 we can create a vhd and then layoff everything on it using DISM.. 16:20:47 lazy_prince: i'm thinking about the process 16:20:48 we have tested it and it is definately possible... 16:20:53 lazy_prince: would you mind pasting the link to the repo w your tool? 16:21:07 sure.. give me a sec.. 16:21:09 lazy_prince: i'm trying to understand where in the process you are creating an image 16:21:11 lazy_prince: it is possible, it’s using standard DISM tools, so it’s all ok 16:21:31 alexpilotti: on the backside of an unattended install 16:21:32 lazy_prince primeministerp we tested it as well 16:21:39 ^? 16:22:02 https://github.com/slokesh184/windows-diskimage-builder.git 16:22:11 thats great... 16:23:02 lazy_prince: reading now 16:23:42 from testing perspective, it should be fairly simple.. I think, everyone may need time to go through the tool, experiment with it.. 16:24:18 and then probably, we can discuss about it in the next meeting. 16:24:26 is that okay..? 16:25:41 lazy_prince: that's fine too 16:25:55 the future goal is to bring the tool on par with linux diskimage-builder.. 16:25:59 lazy_prince: let's setup a call if possible to discuss 16:26:17 lazy_prince: but we'll need to take a look at it first 16:26:30 that should be fine with me.. 16:26:52 lazy_prince: perfect, if you want send some times which work for you at ppouliot@microsoft.com 16:27:53 ok 16:27:58 let's move on 16:28:03 #topic development updates 16:28:09 sure.. I will check with my team and will send the timings to you.. do you have any prefered time that you want us to consider..? 16:28:18 lazy_prince: EST is best for me 16:28:22 I'm on the east coast 16:28:39 alexpilotti: updates? 16:28:41 okay.. well I am on IST.. 16:29:09 lazy_prince: hmm 16:29:13 lazy_prince: we'll figure something out 16:29:18 lazy_prince: send some options 16:29:38 lazy_prince: are you coming to Paris by any chance? 16:31:35 yup.. will do do.. I cant say now, if I will be coming to paris.. but if I or anyone from my team travels, i will ask them to talk to you 16:32:10 ok tx! 16:32:46 some quick updates, since we started the topic 16:33:19 Nova blueprints are all in 16:33:37 we have one relatively new one, which is the sofy shutdown 16:33:45 *soft shutdown 16:34:13 it merged recently for KVM and we sent the patch for Hyper-V 16:34:22 should hopefully merge today 16:35:24 https://review.openstack.org/#/c/111291/ 16:35:34 waiting for CI votes 16:36:24 on the CInder side, we were blocked by a refactoring patch which merged last Friday 16:36:40 we rebased the patches and today they are under review 16:37:00 https://review.openstack.org/#/c/106046/ 16:37:12 #link https://review.openstack.org/#/c/106057/ 16:37:24 (the latter must be rebased on top of the first one) 16:37:44 for the rest all teh Tempest and Devstack patches merged 16:37:51 alexpilotti: awesome 16:37:56 we have a new one for Tempest (neutron) 16:38:14 https://review.openstack.org/#/c/118167/ 16:38:31 but for Tempest we have no issues with code freeze 16:38:37 #link https://review.openstack.org/#/c/111291/ 16:38:45 so it’s on a lower priority compared to the remaining BPs 16:38:53 #link https://review.openstack.org/#/c/118167/ 16:39:07 alexpilotti: ok 16:39:19 I’ll add a full report on the bug fixes on teh next meeting 16:39:21 alexpilotti: also I'm hoping we can light up the livemigration tests next week 16:39:45 yep, all teh Tempest work can be used right away in the CI since it merged 16:39:52 ociuhandu: anything to add? 16:39:56 luis_fdez: ? 16:40:01 if not I think we're good for now 16:40:32 lazy_prince: thanks for participating I look for forward to our followon 16:40:39 #endmeeting