Zun

Support create container with existing neutron port

Bug #1702581 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
Fix Released
High
hongbin

Bug Description

Allow user to pre-create neutron port(s) and use those existing port(s) to create container

hongbin (hongbin034)
Changed in zun:
status: New → Triaged
assignee: nobody → hongbin (hongbin034)
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to zun (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/483113

Changed in zun:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to zun (master)

Reviewed: https://review.openstack.org/483113
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=019055e56b27f596593d34547750d73b72609a56
Submitter: Jenkins
Branch: master

commit 019055e56b27f596593d34547750d73b72609a56
Author: Hongbin Lu <email address hidden>
Date: Wed Jul 12 22:08:16 2017 +0000

    Move get_available_network to API layer

    In before, if there is no network available, users don't know what is
    wrong until the container is scheduled to a compute node and fail.
    This commit moves the searching of neutron net to zun-api so that
    users will receive an error response earlier if the request is
    invalid.

    Change-Id: Ic9fd47c6e4aff4131ebaad73a3bed0f51eeb118c
    Related-Bug: #1702581

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to zun (master)

Reviewed: https://review.openstack.org/481861
Committed: https://git.openstack.org/cgit/openstack/zun/commit/?id=648a9cdaaa9ae0461e2f4072d68f6bad3a232d43
Submitter: Jenkins
Branch: master

commit 648a9cdaaa9ae0461e2f4072d68f6bad3a232d43
Author: Hongbin Lu <email address hidden>
Date: Sat Jul 8 22:25:20 2017 +0000

    Implement create with existing neutron port

    Support creating container with existing neutron port. Users
    can pass the uuid/name of an existing neutron port via the 'nets'
    parameter. If port is specified, Zun will use the existing port
    instead of creating a new port.

    If a container is deleted, its neutron port will be deleted regardless
    of existing or not. A future work is to determine if the port is
    pre-existing and avoid deleting existing port.

    Closes-Bug: #1702581
    Change-Id: I204b4bbe3de9e275690c4a64acdfe557f134b7ee

Changed in zun:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/zun 0.2.0

This issue was fixed in the openstack/zun 0.2.0 release.

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.