[Openstack] [neutron] attach network to multiple tenants without being "shared" / or ec2 solution?

Sebastian Porombka porombka at uni-paderborn.de
Tue Oct 29 14:40:47 UTC 2013


I'm sorry for reposting this mail in this list, but I hope i'm here at the
correct list to get helped.

I have at our on-premise installation of (grizzly-) openstack multiple
"shared" networks which can be used from all tenants.
For example "Public External" and "Public Internal" Networks which are uses
by multiple tenatsŠ

Now I have the problem, that when I launch an instance via the ec2-interface
it gets connected to *all* shared networks.

Is there any possibility to map quantum-networks to tenants ­ so that I can
avoid the multiple shares networks in all tenants.
Or ­ can I set the network via the ec2-interface which a new instance have
to connect to?

Thanks in advance

Sebastian Porombka, M.Sc.
Zentrum für Informations- und Medientechnologien (IMT)
Universität Paderborn

E-Mail: porombka at uni-paderborn.de
Tel.: 05251/60-5999
Fax: 05251/60-48-5999
Raum: N5.314 

Q: Why is this email five sentences or less?
A: http://five.sentenc.es <http://five.sentenc.es/>

Please consider the environment before printing this email.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131029/9cfadf01/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5443 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131029/9cfadf01/attachment.bin>

More information about the Openstack mailing list