I'm not comfortable with the instructions going into the user guide. Setup and deployment will be heavy touch. A developer's page has an implicit warning and the ability to evolve through contribution.
I'll get cracking on a patch. Better to be on the release train half-dressed than waiting four months for the next departure. DL > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: 28 January 2013 20:12 > To: cloudstack-dev@incubator.apache.org > Subject: Re: [DISCUSS] HyperV feature (WAS: Re: [ACS41] Weekly schedule > reminder...) > > On Mon, Jan 28, 2013 at 3:01 PM, Donal Lafferty <donal.laffe...@citrix.com> > wrote: > > AFAIK, the plugin does not need Windows to compile. Dependencies not > captured by Java are encapsulated in Python scripts that are not checked by > the build. > > > > My fault, thanks for clarifying! > > > Instead, the unit tests are skipped by default. These tests rely on Hyper-V > 2012, which is not on either Linux or Windows by default. > > > > Did you want Hyper-V to be a default off build option? It does not seem > like there is a need, but I can do that. > > Optional's great for me. No need to change it. I was actually confirming > that > it *would be* optional. > > > To make the plug-in more useful, the VHDX image type was added to the > set of formats accepted by cloud-api. The agent has to be deployed on the > Hyper-V server along with Java, Python, and some support Python modules. > > > > Install steps and list of available options (network / secondary storage) > needs to be captured somewhere. I was going to follow the Windows > Development environment example, but I'm open to suggestions. > > > > Installation should probably go into the CloudStack advanced installation > guide. You could consider doing a HyperV-specific one first, and we can > advertise this as "tech-preview" for now (or not, depending on the level of > QA we think we can get done). > > > Finally, should I try to merge sooner rather than later? I'd like to up > > the unit > tests, but I'm conscious that there's not much time left. > > > > I'd love if we could get the patch sooner rather than later. That will let > us get > a first round of feedback! > > > > > DL > > > > > >> -----Original Message----- > >> From: Chip Childers [mailto:chip.child...@sungard.com] > >> Sent: 28 January 2013 16:27 > >> To: cloudstack-dev@incubator.apache.org > >> Subject: [DISCUSS] HyperV feature (WAS: Re: [ACS41] Weekly schedule > >> reminder...) > >> > >> Donal, > >> > >> A couple of questions. First, awesome to see that there are good > >> unit tests in there. I seem to remember you mentioning that the > >> HyperV plugin has to be compiled on Windows. Can you confirm this? > >> If this is the case, can you confirm that the plugin is being setup as an > optional build target? > >> > >> Also, what new dependencies are required for this feature to work? > >> > >> Last, do you need any help / direction on how add build / install > >> documentation to the docs? > >> > >> Thanks for the update! > >> > >> -chip > >> > >> On Mon, Jan 28, 2013 at 10:44 AM, Donal Lafferty > >> <donal.laffe...@citrix.com> > >> wrote: > >> > WRT to Hyper-V Plugin, > >> > > >> > The public repo at https://github.com/lafferty/cshv3.git contains > >> > Phase 1 > >> source that passes unit tests a basic integration test involving > >> template and VM creation. The repo was synced to Master yesterday. > >> > > >> > So, I need to prepare a review and merge request. > >> > > >> > Other items: > >> > > >> > -Test and document ability to deploy from scratch. > >> > -Remove Hyper-V systemVM entry in existing deployments. Is this an > >> > db > >> upgrade step? > >> > -Fill in the QA test plan. > >
