On 8/7/12 1:59 AM, "Tomoe Sugihara" wrote:
>On Tue, Aug 7, 2012 at 4:30 PM, Murali Reddy
>wrote:
>> On 07/08/12 12:11 PM, "Tomoe Sugihara" wrote:
>>
>>>On Tue, Aug 7, 2012 at 3:34 PM, Alex Huang
>>>wrote:
> I have looked at the code more in detail and found a bit tricky
>thing.
>
On Tue, Aug 7, 2012 at 4:30 PM, Murali Reddy wrote:
> On 07/08/12 12:11 PM, "Tomoe Sugihara" wrote:
>
>>On Tue, Aug 7, 2012 at 3:34 PM, Alex Huang wrote:
I have looked at the code more in detail and found a bit tricky thing.
Inside the createVif() method, it calls getNetwork(conn,
On 07/08/12 12:11 PM, "Tomoe Sugihara" wrote:
>On Tue, Aug 7, 2012 at 3:34 PM, Alex Huang wrote:
>>> I have looked at the code more in detail and found a bit tricky thing.
>>>
>>> Inside the createVif() method, it calls getNetwork(conn, nic) to set
>>> vifr.network record. And inside getNetwork(
On Tue, Aug 7, 2012 at 3:34 PM, Alex Huang wrote:
>> I have looked at the code more in detail and found a bit tricky thing.
>>
>> Inside the createVif() method, it calls getNetwork(conn, nic) to set
>> vifr.network record. And inside getNetwork(), it differentiates by
>> BroadcastDomainType.
>>
>>
> I have looked at the code more in detail and found a bit tricky thing.
>
> Inside the createVif() method, it calls getNetwork(conn, nic) to set
> vifr.network record. And inside getNetwork(), it differentiates by
> BroadcastDomainType.
>
> Now I'm wondering if the method getNetwork() to be insi
On Mon, Aug 6, 2012 at 6:18 PM, Tomoe Sugihara wrote:
> On Fri, Jul 27, 2012 at 10:13 AM, Chiradeep Vittal
> wrote:
>>
>>
>> On 7/25/12 10:52 PM, "Ishimoto, Ryu" wrote:
>>
>>>On Mon, Jun 4, 2012 at 3:02 PM, Chiradeep Vittal <
>>>chiradeep.vit...@citrix.com> wrote:
>>>
Also note that in
On Fri, Jul 27, 2012 at 10:13 AM, Chiradeep Vittal
wrote:
>
>
> On 7/25/12 10:52 PM, "Ishimoto, Ryu" wrote:
>
>>On Mon, Jun 4, 2012 at 3:02 PM, Chiradeep Vittal <
>>chiradeep.vit...@citrix.com> wrote:
>>
>>>
>>> Also note that in order to support hotplug and hot-detach of nics, we
>>>need
>>> com
On Fri, Jul 27, 2012 at 10:13 AM, Chiradeep Vittal
wrote:
>
>
> On 7/25/12 10:52 PM, "Ishimoto, Ryu" wrote:
>
>>On Mon, Jun 4, 2012 at 3:02 PM, Chiradeep Vittal <
>>chiradeep.vit...@citrix.com> wrote:
>>
>>>
>>> Also note that in order to support hotplug and hot-detach of nics, we
>>>need
>>> com
On Fri, Jul 27, 2012 at 10:13 AM, Chiradeep Vittal
wrote:
>
>
> On 7/25/12 10:52 PM, "Ishimoto, Ryu" wrote:
>
>>On Mon, Jun 4, 2012 at 3:02 PM, Chiradeep Vittal <
>>chiradeep.vit...@citrix.com> wrote:
>>
>>>
>>> Also note that in order to support hotplug and hot-detach of nics, we
>>>need
>>> com
On 7/25/12 10:52 PM, "Ishimoto, Ryu" wrote:
>On Mon, Jun 4, 2012 at 3:02 PM, Chiradeep Vittal <
>chiradeep.vit...@citrix.com> wrote:
>
>>
>> Also note that in order to support hotplug and hot-detach of nics, we
>>need
>> commands like CreateNic and AttachNic.
>>
>>
>This is a great point. I fe
itself to implement that
> >feature. I think XenServer team actually mentioned that they're willing
> >to put in script callouts around vif being brought up and down and that
> >might be one approach but we'll have to investigate what version it has
> >been put int
> -Original Message-
> From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
> Sent: Monday, June 04, 2012 11:11 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: making VM startup more fine-grained
>
> Heya,
>
> What would be the best way
: Monday, June 04, 2012 3:10 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: making VM startup more fine-grained
Volumes can outlive VMs but nics cannot.
I like your idea in the other email. Break the StartCommand into two commands,
a ConstructCommand and a StartCommand. That makes
capabilities. Something we should develop for each hypervisor.
--Alex
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Sunday, June 03, 2012 11:05 PM
> To: CloudStack DeveloperList
> Subject: Re: making VM startup more fine-grained
>
&g
udStack DeveloperList
> Subject: Re: making VM startup more fine-grained
>
> This could work as well.
> If volumes are prepared as part of CreateVm, is there a reason why nics
> cannot be as well? Is it because the volumes are prepared before the
> destination host is chosen
This could work as well.
If volumes are prepared as part of CreateVm, is there a reason why nics
cannot be as well? Is it because the volumes are prepared before the
destination host is chosen?
On 6/1/12 5:38 AM, "Murali Reddy" wrote:
>On 01/06/12 10:46 AM, "Chiradeep Vittal"
>wrote:
>
>>A thir
ut we'll have to investigate what version it has
>been put into.
>
>--Alex
>
>> -Original Message-
>> From: Kelven Yang [mailto:kelven.y...@citrix.com]
>> Sent: Thursday, May 31, 2012 11:30 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject:
Thursday, May 31, 2012 11:30 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: making VM startup more fine-grained
>
> Another way to state my point - don't let CloudStack orchestrators do micro-
> management. It is impossible to handle every case cleanly if we do
On 01/06/12 10:46 AM, "Chiradeep Vittal"
wrote:
>A third way is to split the agent api into 2 commands: CreateVm and
>StartVm.
CloudStack already has two separate agent api commands for
creating(CreateCommand) and starting (StartCommand) VM operations. Not
sure if any optimization influenced thi
Sent: Thursday, May 31, 2012 11:07 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: making VM startup more fine-grained
>
> > Another way is to modify the specific hypervisor resource to do
> something
> > just after creating the vifs but prior to starting the vm.
&
day, May 31, 2012 10:17 PM
> To: CloudStack DeveloperList
> Subject: making VM startup more fine-grained
>
> I was helping someone with their integration of an SDN controller with
> CloudStack. The requirement was that the SDN controller needed the uuid
> of
> the virtual inter
I was helping someone with their integration of an SDN controller with
CloudStack. The requirement was that the SDN controller needed the uuid of
the virtual interface (vif) of the virtual machine so that it could plug
it into the right softswitch, manage the vif etc. This vif uuid is
generated by
22 matches
Mail list logo
