Bug 1466117
| Summary: | There is no option to set "physical_network_mtus = provider2:4000,provider3:1500" parameter via OSPD | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eran Kuris <ekuris> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Kamil Sambor <ksambor> |
| Status: | CLOSED ERRATA | QA Contact: | Arik Chernetsky <achernet> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 11.0 (Ocata) | CC: | amuller, beagles, ihrachys, jschluet, ksambor, lmarsh, mburns, mflusche, oblaut, rhel-osp-director-maint |
| Target Milestone: | z3 | Keywords: | Triaged, Upstream, ZStream |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-8.0.7-3.el7ost | Doc Type: | Enhancement |
| Doc Text: |
To set MTU as a part of OSPD, this release adds `neutron::plugins::ml2::physical_network_mtus` as a NeutronML2PhysicalNetworkMtus in the heat template to enable MTU in the ml2 plugin. Neutron::plugins::ml2::physical_network_mtus is set based on values from the TripleO heat template.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-13 22:26:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eran Kuris
2017-06-29 06:00:12 UTC
Is that option something we want to support in TripleO? Yes, that's something we should support. I think Brent is a better person to give the timeline on that one. We discussed it a bunch of times in the past that we need it exposed. At the moment this can be set with hiera data in ExtraConfig, example:
parameter_defaults:
ExtraConfig:
neutron::plugins::ml2::physical_network_mtus: ["external:1500"]
Because there is easy workaround, this task is more clean-up than a bug. So there is no reason to backport this changes (changes was released in stable Rocky) 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/RHBA-2018:3587 |