Hi,
I repeated all the procedure (created a network offering, created a
shared network, added nic to tenant VMs) and all work.
Before I wasn't able to ping both router and tenant VM. I don't know
what I was wrong.
Now I'll wait for the 4.2 release in order to deny that VMs of different
tenants are reachable among them, but only by monitoring service. PVlan
is the solution, right?
kind regards,
Alex
On 13/09/2013 11:11, murali reddy wrote:
On Fri, Sep 13, 2013 at 1:52 AM, alex
<alessandro.ciancaglini-re5jqeeqqe8avxtiumw...@public.gmane.org>wrote:
Hi,
I would like to setup a machine which can reach all tenant VMs in my
advanced zone. The use case is a centralized monitoring service of tenant
VMs.
So I was thinking to create a VM on a shared network under ROOT and add new
NICs on the same network to the machines of the 3 tenants in order to
monitor them. It doesn't work.
Can you please elaborate what does not work? Is monitoring service VM on
shared network is able to reach out to the tenant VM's in isolated network?
If there are more than one tenant networks, then does CIDR's of the tenants
network overlap?
Doubt :
- are my thoughts correct?
Yes. Its a valid use-case for shared networks to be used for a monitoring.
- this network needs a router?
- if so, which are the router services I need?
Router will be created any way for DHCP and DNS service. That should be
sufficient at the minimum unless you want to make monitoring service make
it available out side the shared network.
thanks a lot,
Alex
