15:56:52 #startmeeting hyper-v 15:56:53 Meeting started Tue Mar 19 15:56:52 2013 UTC. The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:56:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:56:56 The meeting name has been set to 'hyper_v' 15:57:14 ok 15:57:29 ociuhandu: you alive? 15:59:06 so couple updates from alessandro who is unavailable to join 15:59:18 Live migration with Volumes is fixed 15:59:56 also pnavarro thanks for the bugfix effort last week 16:00:28 it also seems that the rdp-console proxy/dashboard is well underway and should be available for demo at the summit 16:00:37 er dashboard integration 16:01:04 there were also some other minor bug fixes as well 16:01:22 iben: anything you would like to discuss 16:01:30 iben: i started the process of cleaning my puppet bits 16:01:42 iben: to hopefully add them to the puppetforge 16:02:11 iben hopefully in the next few days I'll make the available for consumption 16:02:26 primeministerp: a lot of work there :) 16:02:26 cern folks are also interested in the hyper-v/windows specific bits 16:02:33 luis_fdez: o perfect 16:02:42 luis_fdez: did you get my last email 16:02:47 yep 16:03:12 luis_fdez: as I mentioned, the windows bits don't really fit into the existing model 16:03:25 luis_fdez: mostly due to the windowsness 16:03:49 I know... but as a long-term goal... i would be ideal to have everything mixed... but I supposed the first steps must be done sepparatlely 16:04:05 hey team - is this list up to date? https://wiki.openstack.org/wiki/HypervisorSupportMatrix 16:04:11 luis_fdez: were you thinking of extending the existing modules to support windows 16:04:13 luis_fdez: yes 16:04:18 luis_fdez: so that being said 16:04:32 iben: yes 16:04:34 iben: from a hyper-v perspective 16:04:39 iben: i updated it a few weeks back 16:04:50 luis_fdez: my goal is put my bits on the forge anyway 16:04:51 nice 16:05:21 primeministerp: thanks, that will be a great contribution... as windows support is quite poor... 16:05:42 luis_fdez: I also have bits to generate custom winpe pxe bits 16:05:44 i think the biggest drawback is always the package manager 16:05:51 luis_fdez: yes 16:05:53 luis_fdez: it sucks 16:06:06 primeministerp: alive and squeezing my brain on c++ and python integration 16:06:08 luis_fdez: now that puppet 3 has support for package = exe 16:06:13 luis_fdez: it'a bit better 16:06:18 luis_fdez: for those of us that don't know - what are you working on? 16:06:19 ociuhandu: i'm going to work on that 16:06:32 iben: luis_fdez works for cern 16:06:38 ahh 16:06:45 luis_fdez: he's in the process of preparing to deploy hyper-v 16:06:46 yeps 16:06:50 er 16:07:10 luis_fdez: I'll try to get those out this week then 16:07:20 luis_fdez: although I started a complete refactor 16:07:25 ok, thanks primeministerp 16:07:33 ociuhandu: had one the first refactor of my original bits 16:07:51 now i'm cleaning up those to conform to puppet 3 16:08:00 ok 16:08:03 luis_fdez: and hopefully get it to completely build from source 16:08:24 I also need to get up to speed with puppet... 16:08:37 luis_fdez: I also have all my unattend.xml generation puppetized 16:08:49 luis_fdez: goal is to release all my provising kungfu 16:08:52 that sounds really interesting 16:09:31 i'm thinking how could I mix it with automated image creation 16:10:11 luis_fdez: all possible 16:10:17 ups sorry 16:10:25 I forgot to go in 16:10:25 hehe, of course primeministerp :) 16:10:27 luis_fdez: i'm using it for all baremetal deployments as well as base image creation 16:10:50 luis_fdez: I'll keep you posted on that 16:11:10 ok primeministerp, thanks 16:11:11 pnavarro: anything you want to add 16:11:22 pnavarro: about the bugfixes last week? 16:11:27 o, re: summit 16:11:29 we have session 16:11:39 not, working on that, contributing a bit to puppet, i'm implementing some missing facts for windows 16:11:39 Alex was also added as a presenter 16:12:00 luis_fdez: i just wrote a bunch of facts as well 16:12:07 luis_fdez: basic ones 16:12:16 not really, primeministerp... 16:12:18 luis_fdez: for system variables 16:12:22 pnavarro: ok 16:12:39 ok primeministerp 16:12:45 luis_fdez: let me know if jan wants to have a call 16:12:53 ok primeministerp 16:12:54 luis_fdez: i'd like to get a bit more organized around this 16:13:04 he will :) 16:13:19 luis_fdez: if i put it out sooner than later we can work together on the rest 16:13:25 luis_fdez: i know iben is also interested 16:13:57 yeah, it think it will make it easier 16:14:06 *I 16:14:11 luis_fdez: that will be my goal for this week 16:14:14 then to try to get those out 16:14:14 luis_fdez: are you going to the summit? 16:14:31 no, Jan and Belmiro, I'll be at Hepix 16:15:36 anything else? 16:15:53 primeministerp: ype 16:15:54 iben: ? 16:16:05 primeministerp: about snapshoting of windows guests 16:16:12 luis_fdez: is there bug? 16:16:59 luis_fdez: what's the issue? 16:17:01 primeministerp: no, but I was wondering what could be the best way of snapshotting windows guests... and notifying them to be generalize or what is the first boot and thinks like that 16:17:16 luis_fdez: you'll have to sysprep them 16:17:34 because now... if I snapshot a windows machine joined to domain with a concrete name... the following instances... will be the same... and I'm not sure about the best way of dealing with that 16:17:41 there is a whole sysprep process to prepare a windows image 16:17:50 yep 16:18:07 primeministerp: I know... I know... but how to trigger it during snapshoting an image? 16:18:21 luis_fdez: you have to run it before snapshotting 16:18:46 luis_fdez: same as if you were generating custom windows images for deployment 16:18:56 so you have a running machine you want to clone into an image for use by others? 16:19:18 normally the machine to be used as a template image is shutdown during the sysprep proecess 16:19:19 luis_fdez: i'm assuming your trying to take existing windows images 16:19:49 luis_fdez: from openstack 16:19:52 not really, i'm thinking in general... because if I want to do it in an automated way I'm not sure how to do it... 16:20:01 luis_fdez: so 16:20:13 luis_fdez: you need to have the domain join 16:20:46 luis_fdez: as part of the sysprep starting process 16:20:55 luis_fdez: you can apply unattend.xml for those parts 16:21:01 during the sysprep 16:21:16 luis_fdez: it can get complicated 16:21:54 luis_fdez: i'm actually using puppet to have them join the domain, etc 16:21:56 no, I know that but ummm.... is it possible for a running vm to detect that he's going to be snapshoted? 16:22:06 luis_fdez: not that i know of 16:22:18 luis_fdez: and you can't really use a snapshot 16:22:22 luis_fdez: you have to down the vm 16:22:25 and take the vhd 16:22:33 luis_fdez: would be the clean way 16:22:40 luis_fdez: if you snapshot 16:22:59 luis_fdez: i.e. run sysprep, with all the necessary bits 16:23:02 then snapshot 16:23:09 however 16:23:18 you still need a restart somewhere in there 16:23:31 so - I know that vmware convertor can snapshot a running windows vm as long as vmware tools is installed 16:23:38 it uses the vss driver 16:23:47 iben: we can snapshot w/ hyper-v too 16:23:58 iben: however don't know if its the best way to create master images 16:24:04 the destination is a vmware vmdk image which can be converted to a ovf or ova 16:24:30 i'm just saying it's technically possible 16:24:44 sure, except we still can't boot those on hyperv 16:24:50 and is commonly done for testing machine conversion 16:25:05 you can even snapshot and convert a running physical machine to virtual 16:25:13 that's a p2v 16:25:25 then there are v2v v2p and p2p 16:25:31 hahaha 16:25:32 dude 16:25:33 x2x 16:25:42 that's so 2010 16:25:51 hehehe 16:25:53 i'm sure depending on the use case there's a way with different tools to get done what you need 16:25:53 it's want I would like to be able to.... use openstack snapshoting to create templates that are automatically syspreped... 16:26:28 luis_fdez: you might be able t o 16:26:30 right - so we should write a story about that and work on the process 16:26:46 peter - where on the openstack interweb would we post this work? 16:26:52 luis_fdez: just going to have to figure out the specific task order before snapshotting i assume 16:27:05 iben: not sure 16:27:09 iben: a wiki page 16:28:17 luis_fdez - if you like I can help you work on this 16:28:31 luis_fdez: i haven't needed to do much w/ sysprep lately however this is a key topic 16:28:39 need to know your environment - can you skype? 16:28:52 luis_fdez: iben we could document the process on the wiki 16:28:58 skype me at: ibenrodriguez 16:29:04 luis_fdez: iben or in the admin guide 16:29:34 i'm sure annegentle might have better suggestions too 16:29:37 no, it's not a priority... I was just thinking about it... sysprep, unattended is not the problem (i'm using it to create the templates automatically) but the process of snapshoting is a bit different 16:30:09 luis_fdez: I'll start to look at it 16:30:12 yup - cool - once it's a proven procedure we can post in the admin guide 16:30:32 anything else anyone? 16:30:50 yeah wiki is great for vetting, then post tested stuff to the admin guide 16:30:57 if the snapshot is to be called from the hypervisor or outside the VM it would call the vss driver of the windows server guest vm 16:30:59 annegentle: awesome 16:31:34 primeministerp: from my side it's all :) 16:31:41 http://msdn.microsoft.com/en-us/library/dd722833(v=bts.10).aspx 16:31:54 iben: vss driver? 16:32:10 the feature name is called: Host side backup support (VSS) 16:32:16 luis_fdez: ok, thx for the input today 16:32:16 luis_fdez: i'll keep you posed on my puppet progress 16:32:32 windows specific features? 16:33:04 iben: not sure how that applies? 16:33:28 let's take it to the hyper-v channel for further discussion 16:33:34 I'm going to close the meetign for now 16:33:41 #endmeeting