Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of msweet.dev@gmail.com designates
 209.85.223.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4308CB64-E717-4856-A2DE-A9470AA1577B@clogeny.com>
References: <4308CB64-E717-4856-A2DE-A9470AA1577B@clogeny.com>
Date: Sat, 14 Sep 2013 15:29:16 +0100
Message-ID: 
 <CALoaWF5u49JnoiCSMjfMvgRh9fgvE0qZSDMpwKJSi29wSuz40A@mail.gmail.com>
Subject: Re: Virtual router and vm on different hosts
From: Marty Sweet <msweet.dev@gmail.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Content-Type: multipart/alternative; boundary=047d7b3a9c08b9898104e658cb54

--047d7b3a9c08b9898104e658cb54
Content-Type: text/plain; charset=ISO-8859-1

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
>
>

--047d7b3a9c08b9898104e658cb54--