che.org
> Cc: Edison Su; Anthony Xu; Kelven Yang; Vijayendra Bhamidipati
> Subject: Re: VM router spawning multiple public nics
>
> Great, thanks. I've already got a working implementation of
> adding/removing nics from regular instances that I've been playing
> with, so I
could point me in the
>>> right direction and be available to answer questions.
>>>
>>> On Wed, Aug 29, 2012 at 10:39 AM, Edison Su
>>> wrote:
>>> > Yah, KVM doesn't support VPC yet. Will you help to add VPC support on
>>> KVM?:) Just implement
ge-
>> From: Marcus Sorensen [mailto:shadow...@gmail.com]
>> Sent: Wednesday, August 29, 2012 10:16 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VM router spawning multiple public nics
>>
>> I'd be willing to give it a shot if someone coul
: cloudstack-dev@incubator.apache.org
> Subject: Re: VM router spawning multiple public nics
>
> I'd be willing to give it a shot if someone could point me in the
> right direction and be available to answer questions.
>
> On Wed, Aug 29, 2012 at 10:39 AM, Edison Su
> w
related commands...
>
>> -Original Message-
>> From: Marcus Sorensen [mailto:shadow...@gmail.com]
>> Sent: Wednesday, August 29, 2012 6:49 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VM router spawning multiple public nics
>>
>&g
ubator.apache.org
> Subject: Re: VM router spawning multiple public nics
>
> I can confirm that the patch has fixed my particular issue.
>
> This is likely unrelated and I think it doesn't even use the same
> code, but I began to play with the VPC stuff a bit and noticed that I
&g
:shadow...@gmail.com]
>> Sent: Tuesday, August 28, 2012 2:00 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VM router spawning multiple public nics
>>
>> I thought about this solution myself, but below this portion of code
>> it looks like it us
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Tuesday, August 28, 2012 2:00 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: VM router spawning multiple public nics
>
> I thought about this solution myself, but below
Tuesday, August 28, 2012 1:40 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VM router spawning multiple public nics
>>
>> Yes, that looks like it would work for me, however that's not
>> something that would ever make it into master, right? Essentially
&g
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Tuesday, August 28, 2012 1:40 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: VM router spawning multiple public nics
>
> Yes, that looks like it would work for m
012 12:23 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VM router spawning multiple public nics
>>
>> Thanks for pointing me in the right direction. I've reviewed this code
>> in a bit more detail, and it seems like it's accomplishing the
&g
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Tuesday, August 28, 2012 12:23 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: VM router spawning multiple public nics
>
> Thanks for pointing me in the right direction. I&
Thanks for pointing me in the right direction. I've reviewed this code
in a bit more detail, and it seems like it's accomplishing the
following:
1. get all network interfaces currently connected to the running VM
(a.k.a vnet devices via libvirt)
2. find out which vlans these network interfaces are
...
Integer nicPos = 0;
for (InterfaceDef nic : nics) {
if (nic.getBrName().equalsIgnoreCase(_linkLocalBridgeName)) {
vlanAllocatedToVM.put("LinkLocal", nicPos);
} else {
String vlanId = getVlanIdFromBri
Possible bug in in kvm code: LibvirtComputingResource->execute(IpAssocCommand
cmd)-> VifHotPlug, which is only place adding nic into router vm.
Turn on agent log, then take a look what happened.
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Monday, Augu
15 matches
Mail list logo
