Expose "get me a network" in instance creation

[Armando Migliaccio]

It would be nice to expose get-me-a-network via horizon. Right now it only works with the nova CLI. This came up for discussion during Boston summit [2]

[1] https://blueprints.launchpad.net/nova/+spec/get-me-a-network
[2] https://etherpad.openstack.org/p/pike-neutron-gman

[Pierre Riteau (priteau)]

It would be very nice indeed. Get Me A Network is intended to improve the user-friendliness of OpenStack, but it should really be leveraged by the most user-friendly interface (Horizon) for maximum usefulness.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/521266
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=4c8a294aee4caff9f1bb764686bd6f4b47d62b41
Submitter: Zuul
Branch: master

commit 4c8a294aee4caff9f1bb764686bd6f4b47d62b41
Author: Akihiro Motoki <email address hidden>
Date: Sun Oct 22 18:17:03 2017 +0000

    API micro-version support for multiple features

    Previously horizon micro-version support only supports one feature,
    but there is a case where we need to support more than one feature
    using micro-versioning. For example, "instance_description" and
    "auto_allocated_network" in the server create operation both require
    micro-version. This case was not supported previously.

    This commit changes get_microversion() function to take a feature list
    and looks up a micro-version which supports all requested features.

    A known limitation is that we need to re-call get_microversion() with
    different feature(s) if no micro-version which satisfies all requested
    features is found and we would like to look up a micro-version which
    supports a subset of the requested features. Most features are expected
    in recent API versions, so I believe this would be a minor limitation.

    Change-Id: I46f1c7fa1ddcf1dfac93d921cffaf3aa5ac011a7
    Related-Bug: #1690433

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/514084
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d16ed45e0615d54d983da43b1d0a2070c7edc814
Submitter: Zuul
Branch: master

commit d16ed45e0615d54d983da43b1d0a2070c7edc814
Author: Akihiro Motoki <email address hidden>
Date: Sat Nov 18 17:36:39 2017 +0000

    Support "Get me a network" in launch instance

    "Get-me-a-network" feature is supported in Nova API 2.37 or later.
    To support this in horizon, a dummy "auto_allocated_network" is shown
    in the launch instance form. I believe this approach fits the current
    way of the launch instance form. The dummy network is a special network ID
    and if specified the nova API wrapper converts 'nics' parameter properly.

    In addition, a dummy "auto_allocated_network" is now shown in the network
    table. This is because Neutron creates an actual auto allocated network
    once a server is created specifying nics=="auto".
    I believe this fake behavior brings consistency in the network table
    to some extent, while this is just a compromise.

    Note that this patch does not cover the network topology integration.
    "auto_allocated_network" is not shown until the actual auto allocated
    network is created. The network topology integration requires more work.
    For example, the link for the fake auto allocated network should be
    disabled in the flat view. The pop-up for the fake auto allocated network
    should be disabled in the graph view.

    Change-Id: I062fc1b7ed75dc771ddc7f13c8324ed4ffab6808
    Closes-Bug: #1690433

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/horizon 14.0.0.0b2 development milestone.