OpenStack Heat

Allow Heat to understand what networking service is available

Registered by Pavlo Shchelokovskyy on 2014-08-21

Successful validation and creation of several resources in Heat (like AWS::EC2::SecurityGroup) depend on whether the OpenStack cloud networking is provided by Neutron or Nova-network. It is proposed to add a heat.conf option to set the networking service in use, and for backward compatibility heat-engine on start-up can auto-discover the presence/absence of Neutron in the cloud if such option is not set.

Blueprint information

Status:: Complete

Approver:: None

Priority:: Low

Drafter:: Pavlo Shchelokovskyy

Direction:: Approved

Assignee:: Pavlo Shchelokovskyy

Definition:: Approved

Series goal:: Accepted for juno

Implementation:: Implemented

Milestone target:: 2014.2

Started by: Pavlo Shchelokovskyy on 2014-08-27

Completed by: Steve Baker on 2014-09-02

Related branches

Related bugs

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:is-using-neutron,n,z

Addressed by: https://review.openstack.org/115968
Allow to decide between Nova-network and Neutron

Gerrit topic: https://review.openstack.org/#q,topic:bp/discover-networking-service,n,z

Addressed by: https://review.openstack.org/115969
AWS SecurityGroup use is_using_neutron()

Gerrit topic: https://review.openstack.org/#q,topic:bp/sahara-as-heat-resource,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bp/handle-update-for-security-groups,n,z

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information

Everyone can see this information.

Subscribers

No subscribers.