On Wed, Mar 27, 2013 at 05:24:39PM +0000, Donal Lafferty wrote: > > > > -----Original Message----- > > From: Chip Childers [mailto:chip.child...@sungard.com] > > Sent: 27 March 2013 1:49 PM > > To: dev@cloudstack.apache.org > > Subject: Re: [DISCUSS] Hyper-V Plugin & Microsoft Compiler & IP Clearance > > > > On Wed, Mar 27, 2013 at 10:27:44AM +0000, Donal Lafferty wrote: > > > Let me bring the conversation back to the subject line... > > > > > > WRT to ServerResource implementation, I'd suggested using a RESTful > > > API to hide ServerComponent and ServerResource implementations from > > > each other [1] > > > > +1 > > > > > > > > This left the ServerResource open for implementation in any 'native' > > language. In contrast, the ServerComponent conformed to Management > > Server (Java/Spring/whatever our ORM is/etc), and it is meant to be > > 'generic' > > to simplify reuse. > > > > > > I reason that the difficulty device access for test and build, and not > > language choice. Integration testing requires device access, and some tools > > will only run on a particular platform, e.g. libvirt, MSFT compiler. The > > language choice is secondary to this problem. > > > > > > > It's both language and build tool/platform, but I get your point. > > Testing and building is my biggest concern. I'm +1 to David's suggestion > > that > > the ServerResource code bits are a separate git repo, which we can publish > > as a different release artifact. > > > [Donal Lafferty] > > https://github.com/cloudstack-extras ?
No, just a second Apache CloudStack *project* git repo that contains the HyperV ServerResource implementation only. > > > > This doesn't address general build / testing though. Anyone have thoughts > > on this? > > > [Donal Lafferty] > > There will be a second email thread on this list when I follow up with > Pradeep for build and Prasanna for BVT (build validation test) as AlexH > suggested. > > Any additional considerations are very welcome. > >
