<div dir="ltr">Hm, you are right. I suppose we need backward compability with nova network, without Neutron.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/11/7 Nilakhya <span dir="ltr"><<a href="mailto:nilakhya.chatterjee@globallogic.com" target="_blank">nilakhya.chatterjee@globallogic.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello Denis,<br>
<br>
I asked in icehouse design session about the Floating IP support
in heat templates ( so that we can migrate from AWS to OS) and was
guided to OS::neutron resource even i was thinking if neutron
becomes a dependancy then (and not just a simple nova-network)
even using OS::Neutron there the asked usecase is a problem so
opening it to community.<div class="im"><br>
<pre cols="72">Consultant Engineering
Team: HPCS-Vertica
Location: Noida, India</pre></div><div><div class="h5">
On 11/07/2013 03:22 PM, Denis Makogon wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div dir="ltr">SnowDust, hi, are there any needs of Neutron
usage(in trove)? Since nova supports nova-network i suppose we
could keep networking with nova.<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
2013/11/7 Nilakhya <span dir="ltr"><<a href="mailto:nilakhya.chatterjee@globallogic.com" target="_blank">nilakhya.chatterjee@globallogic.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Currently my heat
template works with AWS resource type:<br>
<br>
DatabaseIPAddress:<br>
Type: AWS::EC2::EIP<br>
DatabaseIPAssoc :<br>
Type: AWS::EC2::EIPAssociation<br>
Properties:<br>
InstanceId: {Ref: BaseInstance}<br>
EIP: {Ref: MyIPAddress}<br>
<br>
Now if i want to change to OpenStack ( OS ) namespace with
a similar implementation : <br>
<br>
MyIPAddress:<br>
Type: OS::Neutron::FloatingIP<br>
<font color="#ff0000">Properties:</font><br>
<font color="#ff0000">floating_network_id : <span>String</span></font><br>
MyIPAssoc :<br>
Type: OS::Neutron::FloatingIPAssociation<br>
Properties:<br>
floatingip_id : {Ref: MyIPAddress}<br>
<br>
I cannot problem is,<br>
<br>
a) floating_network_id ( is not known ) which is a
required property.<br>
b) Even if its available / defaults to, its an overhead
from AWS simplicity.<span><font color="#888888"><br>
<br>
<br>
<pre cols="72">--
Consultant Engineering
Team: HPCS-Vertica
Location: Noida, India
</pre>
</font></span></div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>