Hello Denis, 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. Consultant Engineering Team: HPCS-Vertica Location: Noida, India On 11/07/2013 03:22 PM, Denis Makogon wrote: > SnowDust, hi, are there any needs of Neutron usage(in trove)? Since > nova supports nova-network i suppose we could keep networking with nova. > > > 2013/11/7 Nilakhya <nilakhya.chatterjee at globallogic.com > <mailto:nilakhya.chatterjee at globallogic.com>> > > Currently my heat template works with AWS resource type: > > DatabaseIPAddress: > Type: AWS::EC2::EIP > DatabaseIPAssoc : > Type: AWS::EC2::EIPAssociation > Properties: > InstanceId: {Ref: BaseInstance} > EIP: {Ref: MyIPAddress} > > Now if i want to change to OpenStack ( OS ) namespace with a > similar implementation : > > MyIPAddress: > Type: OS::Neutron::FloatingIP > Properties: > floating_network_id : String > MyIPAssoc : > Type: OS::Neutron::FloatingIPAssociation > Properties: > floatingip_id : {Ref: MyIPAddress} > > I cannot problem is, > > a) floating_network_id ( is not known ) which is a required property. > b) Even if its available / defaults to, its an overhead from AWS > simplicity. > > > -- > Consultant Engineering > Team: HPCS-Vertica > Location: Noida, India > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > <mailto:OpenStack-dev at lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131107/3f3a5bb8/attachment.html>