[Openstack] [Horizon] external network should not be mapped

Heiko Krämer hkraemer at anynines.com
Fri Mar 7 12:47:44 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi guys,

a network with tag external_network:true can be choose by every one by
booting an instance. Each customer can add 'directly' this network type
(not assiciate flaotingIP) on instance setting. This is not a good deal
because some customers have not much experience with this and it is very
confused for such customers if the network name is "public".

So my question, is there a special reason to show this network
(external_network) on instance boot configuration. This networks/IP need
to be associate with the correct funtion.


I would open a blueprint on the wishlist but would like to ask here first :)

There is my question on ask.openstack =>
https://ask.openstack.org/en/question/9563/neutron-external-network-not-visible/?comment=12479#comment-12479


Cheers
Heiko

- -- 
anynines.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTGb/wAAoJELxFogM4ixOFDwMIAKYlMovw8MzgjN8hTAlwIW0J
nBnpMEf0Bx1ieAO+ed0wiVsW5t1U3u3i2JKkFNL1bvcajTqrS0p06teFCISzcJHQ
aZJ7S68PStLpKfp5pWA2BjHgTONZY6Zdhz6CzYBCZ4n3UdQuVBYTdI+ovD61Pi8M
Sao3axMIHYGeFegihYhzkOH6jMPoMYvfJnCdOu4dcPKCNS4pG36Fg+YY3QLtUbM1
9Sy7zi1uuKbHMnWxQ3DFZs75xJcq5WCeNFzz3j5TqMWlVGYfaNj4lP3jCeAn2qak
eMXZ9QKaoYKVbGoqnObGqC3UmLzuXQoIMyrYambcoesF1Gfkv0xso02BZQH8Jus=
=ZcqS
-----END PGP SIGNATURE-----





More information about the Openstack mailing list