<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Akihiro,<br>
<br>
yes you'r absolutely right but i needed to shared this network for
visibility for all. This is a requirement for such clients to
communicate with the API because they need a network ID for public
net. <br>
Such clients checks if the id exists but doesn't if the pub net
isn't shared. <br>
<br>
In addition if my external network is no marked as shared, sometimes
(i think if the cache of horizon will refreshed) a Cloud member
can't associate via Horizon new floating ip's because there is no
public network present.<br>
<br>
<br>
So i think some operators have other examples if they have
production systems and the question still exists, why should we not
filter all external_network:True of the instance launch form ? <br>
<br>
<br>
Cheers and thanks<br>
Heiko<br>
<br>
Am 07.03.2014 18:55, schrieb Akihiro Motoki:<br>
<span style="white-space: pre;">> Hi Heiko,<br>
><br>
> I would like to clarify the condition this happens.<br>
> This is the first time I heard that external networks (whose<br>
> router:external_network flag is True)<br>
> can be selected in the "Instance Launch" form.<br>
><br>
> External networks are usually created and owned by admin, so
if you<br>
> logged in as admin<br>
> it is an expected behavior that external network is listed in<br>
> "Instance Launch" form,<br>
> but if it is listed for non-admin users it is not an intended
behavior.<br>
><br>
> Thanks,<br>
> Akihiro<br>
><br>
> On Fri, Mar 7, 2014 at 9:47 PM, Heiko Krämer
<a class="moz-txt-link-rfc2396E" href="mailto:hkraemer@anynines.com"><hkraemer@anynines.com></a> wrote:<br>
>></span><br>
<blockquote type="cite">Hi guys,<br>
<br>
a network with tag external_network:true can be choose by every
one by<br>
booting an instance. Each customer can add 'directly' this network
type<br>
(not assiciate flaotingIP) on instance setting. This is not a good
deal<br>
because some customers have not much experience with this and it
is very<br>
confused for such customers if the network name is "public".<br>
<br>
So my question, is there a special reason to show this network<br>
(external_network) on instance boot configuration. This
networks/IP need<br>
to be associate with the correct funtion.<br>
<br>
<br>
I would open a blueprint on the wishlist but would like to ask
here first :)<br>
<br>
There is my question on ask.openstack =><br>
<a class="moz-txt-link-freetext" href="https://ask.openstack.org/en/question/9563/neutron-external-network-not-visible/?comment=12479#comment-12479">https://ask.openstack.org/en/question/9563/neutron-external-network-not-visible/?comment=12479#comment-12479</a><br>
<br>
<br>
Cheers<br>
Heiko<br>
<br>
--<br>
anynines.com<br>
</blockquote>
<span style="white-space: pre;">>><br>
>><br>
>> _______________________________________________<br>
>> Mailing list:
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
>> Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
>> Unsubscribe :
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
></span><br>
<br>
-- <br>
anynines.com<br>
<br>
</body>
</html>