RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-10-18 Thread Donal Lafferty
r the confusion. > -Original Message- > From: Donal Lafferty [mailto:donal.laffe...@citrix.com] > Sent: 20 September 2013 19:05 > To: dev@cloudstack.apache.org > Subject: RE: [Proposal] Userdata Support for Hyper-V with KVP Data > Exchange > > Let me put this on hol

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-20 Thread Donal Lafferty
> To: dev@cloudstack.apache.org > Subject: RE: [Proposal] Userdata Support for Hyper-V with KVP Data > Exchange > > Yep. I'll recirculate the proposal next week. > > DL > > > -Original Message- > > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Rajesh Battala
Message- From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] Sent: Saturday, September 14, 2013 1:46 AM To: dev@cloudstack.apache.org Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange I believe DL is actually referring to boot args, not user/metadata On 9/13/13

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Donal Lafferty
Yep. I'll recirculate the proposal next week. DL > -Original Message- > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] > Sent: 13 September 2013 21:16 > To: dev@cloudstack.apache.org > Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Da

Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Chiradeep Vittal
I believe DL is actually referring to boot args, not user/metadata On 9/13/13 12:41 PM, "Darren Shepherd" wrote: >On 09/13/2013 11:56 AM, Donal Lafferty wrote: > >> Ah, okay, so you're talking about this: >>http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Admi >>n_Guide/user-

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Donal Lafferty
> -Original Message- > From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] > Sent: 13 September 2013 18:35 > To: dev@cloudstack.apache.org > Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Data > Exchange > > On 09/13/2013 10:25 AM, Rajesh B

Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Darren Shepherd
On 09/13/2013 11:56 AM, Donal Lafferty wrote: Ah, okay, so you're talking about this: http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.1/html/Admin_Guide/user-data-and-meta-data.html Okay, that leads me back to my original question. Why is that hypervisor specific? That data

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Donal Lafferty
> -Original Message- > From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com] > Sent: 13 September 2013 17:40 > To: dev@cloudstack.apache.org > Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Data > Exchange > > On 09/13/2013 08:51 AM, Donal

Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Darren Shepherd
On 09/13/2013 10:25 AM, Rajesh Battala wrote: To bring up the system vm's on the hyperv host we need to pass the boot args from host to the systemvm's. To pass the data from hyperv host to systemvm guest we need this method. Oh maybe I'm getting terminology mixed up. When you say userdata I

RE: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Rajesh Battala
en.s.sheph...@gmail.com] Sent: Friday, September 13, 2013 10:10 PM To: dev@cloudstack.apache.org Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange On 09/13/2013 08:51 AM, Donal Lafferty wrote: > IIRC, OpenStack puts userdata for Hyper-V guest VMs on a separate volume. > The

Re: [Proposal] Userdata Support for Hyper-V with KVP Data Exchange

2013-09-13 Thread Darren Shepherd
On 09/13/2013 08:51 AM, Donal Lafferty wrote: IIRC, OpenStack puts userdata for Hyper-V guest VMs on a separate volume. The guest can mount the volume and extract the data. However, I suggest we use Hyper-V's KVP Data Exchange mechanism instead. Doing so keeps volume management and passing u