Bug 1601112 - glance backend file configuration looks as if it was required for NFV
Summary: glance backend file configuration looks as if it was required for NFV
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: All
OS: All
high
high
Target Milestone: ---
: ---
Assignee: Roger Heslop
QA Contact: Yariv
URL:
Whiteboard:
Depends On:
Blocks: 1601039 1754502 1754525 1754559
TreeView+ depends on / blocked
 
Reported: 2018-07-13 22:39 UTC by Andreas Karis
Modified: 2020-11-25 08:23 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1601039
: 1754502 1754525 1754559 (view as bug list)
Environment:
Last Closed: 2019-09-24 10:56:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andreas Karis 2018-07-13 22:39:30 UTC
+++ This bug was initially created as a clone of Bug #1601039 +++

This has nothing to do with NFV. We shouldn't provide this in the template here - Andreas

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/network_functions_virtualization_configuration_guide/appe-sample-ovsdpdk-files#annotations:e6a345f6-865f-4abc-9fba-9c628d8fcc64

--- Additional comment from Sandra McCann on 2018-07-13 13:18:39 EDT ---

Andreas -

The yaml files are a direct import from QE. We can not hand edit. Please open an internal bug against an engineering component (I suggest director) to have this removed from the QE source. We can then import the files again.

+++++++++++++++++++++++++++++++++++++++++++

Hi,

Can we change the QE templates or add a comment indicating that the glance file backend is not needed for NFV deployments? The same with the SSH configuration. Otherwise, the example file makes users configure these parameters, it simply looks as if the params were needed when in reality they have nothing to do with the NFV configuration.

Thanks,

Andreas

Comment 2 Andreas Karis 2018-08-01 14:43:24 UTC
Hi,

Please have a look at:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/network_functions_virtualization_configuration_guide/appe-sample-ovsdpdk-files#annotations:e6a345f6-865f-4abc-9fba-9c628d8fcc64

Section:
B.1.3. network.environment.yaml

The example environment file contains:
 GlanceBackend: 'file'

It also contains:
  SshServerOptions:
    UseDns: 'no'

These should not be there in the examples for NFV deployments. Customers will copy this file and will insert the above two options in their templates, or will at least ask support why these parameters are there. The network-environment.yaml file for our examples should be minimal. 

Sandra McCann from the docs team told me that:
~~~

The yaml files are a direct import from QE. We can not hand edit. Please open an internal bug against an engineering component (I suggest director) to have this removed from the QE source. We can then import the files again.
~~~

Perhaps, we need to change our QE templates and "outsource" these parameters (such as GlanceBackend: 'file' and SshServerOptions into a different .yaml file.

Thanks,

Andreas

Thanks,

Andreas

Comment 3 Andreas Karis 2018-08-01 14:46:33 UTC
Additionally:
'
  # Configure the classname of the firewall driver to use for implementing security groups.
  NeutronOVSFirewallDriver: openvswitch


The openvswitch OVS firewall driver is only tech preview, so we should not include that in our NFV documentation (which should only refer to fully supported components).

- Andreas

Comment 5 Alan Bishop 2018-08-01 18:17:29 UTC
This seems specific to NFV, so updating the DFG assignment.

Comment 14 Roger Heslop 2019-09-23 19:47:00 UTC
Introductory paragraph has been modified; admonition added at top of appendix and published: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/network_functions_virtualization_configuration_guide/appe-sample-dpdk-sriov-2-port-files


Note You need to log in before you can comment on or make changes to this bug.