FloatingIP functionality is missing

Bug #1314193 reported by Alexander Tivelkov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Murano
Fix Released
Critical
Alexander Tivelkov

Bug Description

No FloatingIP functionality in 0.5.

Changed in murano:
milestone: none → 0.5
assignee: nobody → Alexander Tivelkov (ativelkov)
importance: Undecided → Critical
status: New → In Progress
Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to murano-dashboard (master)

Fix proposed to branch: master
Review: https://review.openstack.org/91015

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix proposed to murano-api (master)

Fix proposed to branch: master
Review: https://review.openstack.org/91042

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to murano-dashboard (master)

Reviewed: https://review.openstack.org/91015
Committed: https://git.openstack.org/cgit/stackforge/murano-dashboard/commit/?id=1d29c54ba5e3c6fa16b102a1af3db8528986eb6b
Submitter: Jenkins
Branch: master

commit 1d29c54ba5e3c6fa16b102a1af3db8528986eb6b
Author: Alexander Tivelkov <email address hidden>
Date: Tue Apr 29 17:38:24 2014 +0400

    Cleaned up obsolete network-related stuff

    One of these checks was preventing FloatingIpField from being displayed properly.

    Change-Id: Iaa4c47211717d30bc4c247c92ffed42045942056
    Partial-bug: #1314193

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to murano-api (master)

Reviewed: https://review.openstack.org/91042
Committed: https://git.openstack.org/cgit/stackforge/murano-api/commit/?id=86a3fa3abe8eb16c53dee3549a7e4a039be0ec22
Submitter: Jenkins
Branch: master

commit 86a3fa3abe8eb16c53dee3549a7e4a039be0ec22
Author: Alexander Tivelkov <email address hidden>
Date: Tue Apr 29 18:27:35 2014 +0400

    Added functionality to assign FloatingIP addresses

    The Instance class got an boolean field 'assignFloatingIp', false by default.
    If this is set 'true', the instance will attempt to assign a floating ip in one
    of its networks (starting from default ones)

    NetworkExplorer class got a functionality to dicover the ID of the external network:
    - for newly created networks it will use their specified external router's external_gateway_info
    - for existing networks it will iterate among all their routers

    Change-Id: I754cd41ffacbf2a2ec62ac23c3a5a7883d1e13b5
    Closes-Bug: #1314193

Changed in murano:
status: In Progress → Fix Committed
ruhe (ruhe)
Changed in murano:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.