[Openstack] Communication between 2 tenants

Kaustubh Kelkar kaustubh.kelkar at casa-systems.com
Thu Oct 20 16:40:30 UTC 2016


You can find it here: http://docs.openstack.org/cli-reference/neutron.html#neutron-net-create . Hope this helps.

From: Silvia Fichera [mailto:fichera.sil at gmail.com]
Sent: Thursday, October 20, 2016 12:38 PM
To: Kaustubh Kelkar <kaustubh.kelkar at casa-systems.com>
Cc: openstack at lists.openstack.org
Subject: Re: [Openstack] Communication between 2 tenants

Thanks Kaustubh.
There is any guide or wiki?
Thanks

2016-10-20 18:34 GMT+02:00 Kaustubh Kelkar <kaustubh.kelkar at casa-systems.com<mailto:kaustubh.kelkar at casa-systems.com>>:
Similar to a shared public network, you can create a shared tenant network. I would think this will require admin privileges however.


-Kaustubh

From: Silvia Fichera [mailto:fichera.sil at gmail.com<mailto:fichera.sil at gmail.com>]
Sent: Thursday, October 20, 2016 11:45 AM
To: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: [Openstack] Communication between 2 tenants

Hi all,
It is possible to let communicate the instances launched by two different tenants?

I mean:
admin:
net-a 192.168.0.0/24<http://192.168.0.0/24>
router-01 attached to net-a 192.168.0.1 and to the net-public 172.27.0.2
instance p 192.168.0.2 and floating ip 172.27.0.3

demo:
demo-net 192.168.2.0/24<http://192.168.2.0/24>
demo-router attached to demo-net 192.168.2.1 and to net-public 172.27.0.8
instance inst 192.168.2.2 floating ip 172.27.0.7

they share the public network net-public  172.27.0.0./24

Instances can ping google (and also other instances within the same project with a different subnet).
It is possible ping instances belonging to different project?

If it could be useful I'm using the ONOS SONA implementation for the control of the network functionalities.

Thanks
--
Silvia Fichera



--
Silvia Fichera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20161020/67ea0659/attachment.html>


More information about the Openstack mailing list