Virtual router and vm on different hosts

[Girish Shilamkar <gi...@clogeny.com>]

Hello,

I was under the assumption that virtual router (VR) and vm spawned for an account would always be on the same host. Therefore in
egress rule automation tests we were ssh'ing VR via host on which the vm was created. But recently we saw failures in egress rule tests 
as VR was not reachable from host on which vm was created. While debugging this issue I found that VR and vm for an account can be on different host. 
It would be great if someone could confirm this.

Thanks !

Regards,
Girish

Re: Virtual router and vm on different hosts

[Girish Shilamkar <gi...@clogeny.com>]

Hello Marty, Marcus,

Thanks for the explanation, I have updated the test accordingly.

Regards,
Girish

On 14-Sep-2013, at 9:37 PM, Marcus Sorensen <sh...@gmail.com> wrote:

> Yes, as Marty mentions they can be on any host, with tagged vlans linking
> everything together.If you prefer them on the same host you can write a
> custom allocator. The user concentrated algorithm packs VMS together when
> possible, and random allocator is self explanatory, but I don't think
> either pay attention to the router/guest relationships.
> On Sep 14, 2013 1:22 AM, "Girish Shilamkar" <gi...@clogeny.com> wrote:
> 
>> Hello,
>> 
>> I was under the assumption that virtual router (VR) and vm spawned for an
>> account would always be on the same host. Therefore in
>> egress rule automation tests we were ssh'ing VR via host on which the vm
>> was created. But recently we saw failures in egress rule tests
>> as VR was not reachable from host on which vm was created. While debugging
>> this issue I found that VR and vm for an account can be on different host.
>> It would be great if someone could confirm this.
>> 
>> Thanks !
>> 
>> Regards,
>> Girish
>> 
>> 

Re: Virtual router and vm on different hosts

[Marcus Sorensen <sh...@gmail.com>]

Yes, as Marty mentions they can be on any host, with tagged vlans linking
everything together.If you prefer them on the same host you can write a
custom allocator. The user concentrated algorithm packs VMS together when
possible, and random allocator is self explanatory, but I don't think
either pay attention to the router/guest relationships.
On Sep 14, 2013 1:22 AM, "Girish Shilamkar" <gi...@clogeny.com> wrote:

> Hello,
>
> I was under the assumption that virtual router (VR) and vm spawned for an
> account would always be on the same host. Therefore in
> egress rule automation tests we were ssh'ing VR via host on which the vm
> was created. But recently we saw failures in egress rule tests
> as VR was not reachable from host on which vm was created. While debugging
> this issue I found that VR and vm for an account can be on different host.
> It would be great if someone could confirm this.
>
> Thanks !
>
> Regards,
> Girish
>
>

Re: Virtual router and vm on different hosts

[Marty Sweet <ms...@gmail.com>]

Hi Girish,

Virtual routers can be on different hosts to user vms as it is assumed the
VLAN used for the private user network is tagged to all the hypervisors.

Marty

On Saturday, September 14, 2013, Girish Shilamkar wrote:

> Hello,
>
> I was under the assumption that virtual router (VR) and vm spawned for an
> account would always be on the same host. Therefore in
> egress rule automation tests we were ssh'ing VR via host on which the vm
> was created. But recently we saw failures in egress rule tests
> as VR was not reachable from host on which vm was created. While debugging
> this issue I found that VR and vm for an account can be on different host.
> It would be great if someone could confirm this.
>
> Thanks !
>
> Regards,
> Girish
>
>