Commit Graph

2 Commits

Author SHA1 Message Date
Akihiro Motoki 6294494163 i18n: Fix untranslated messages
trunk-subports.help.html: The <p translate> tag was not closed
appropriately. This confused angular-gettext and as a result
translations are not used properly.

launch-instance/networkports/ports.html:
"on subnet" was marked as translation string in bug 1745873,
but one "on subnet" is forgot to mark. This commit fixes it.

Related-Bug: #1745873
Change-Id: I01c653161c9a91d499bf493590bb5f511901f31a
2018-01-31 13:35:36 +00:00
Bence Romsics 1ab4b498f2 Trunks panel: create button
Trunk creation is a 3-step workflow:
  * Basic trunk attributes
  * Parent port selector transfertable:
      Selects a single port (mandatory)
  * Subports selector transfertable:
      Selects many ports with segmentation details (optional)

In the port selector steps reused and built on port allocator
transfertable from launch instance.

The easiest way to test is to take the whole change series by taking the
last change in it, then build devstack with neutron trunk support. Eg:

  local.conf:
  enable_plugin neutron https://git.openstack.org/openstack/neutron
  enable_service q-trunk

If you want to test this change in isolation you also need the following
Horizon config:

  openstack_dashboard/enabled/_1500_project_trunks_panel.py:
  DISABLED = False  # or just remove this line

As long as the 'trunk' API extension is available (openstack
extension show trunk) the panel should automatically appear under
Project/Network/Trunks.

To try the 'inherit' segmentation type the subports must be ports of
vlan type provider networks.

Co-Authored-By: Lajos Katona <lajos.katona@ericsson.com>
Co-Authored-By: Elod Illes <elod.illes@ericsson.com>
Change-Id: I663a7e0158335155fe11f0fc40d9fa86bf984ae0
Partially-Implements: blueprint neutron-trunk-ui
2017-11-27 14:05:43 +01:00