Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/initial-sriov-support. Description: Summary ======= The goal of this blueprint is to allow SRIOV configuration within Horizon. Motivation ======== Currently, SRIOV is supported in Neutron but only by CLI. The aim is to get basic feature parity, so that users are not forced to use CLI. This blueprint is not designed to address Nova support. Description ========= The first stage is to expose SRIOV availability/capabilities on the Network Details > Ports pages. This will show the Port type. Ports could also be made a separate tab to the Network overview. The second stage is to enable creation, configuration and removal of port capabilities through Horizon. This will be done through the existing Admin section. It may be worth considering breaking Ports into its own section as it is currently only possible to create ports by following Admin > Networks > Network Details. UX === Extend the Network Details page, under the Ports section. Potentially make Ports a separate tab due to volume of information, needs discussion Ports can currently be created via Admin > Networks. The creation needs to have fields made available for binding:vnic_type. We could extend port creation capabilities to regular users, but this may be making the default appearance over complicated. Need input from UX folks. Wireframes, Mocks, Videos and UI Markup --------------------------------------------------------- Will post these up as code is developed. Testing ====== This bp will be testable easily through standard devstack deployments with Neutron enabled. Outside Dependencies ================== This functionality is already supported in Neutron, so requires no external project changes: https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking The Horizon neutron api already has a port_create function available. Requirements Update Required ======================== No requirements changes to the Dashboard as far as I am aware. Doc Impact ========= No changes to default behaviours, settings, or depracation of previous code. However, it would be worth documenting new options where appropriate; for example, if we change where/how Ports are created. Specification URL (additional information): None
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1548