Tempest tests missing for mtu and gateway api changes
Bug #1612528 reported by
Marc Koderer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Marc Koderer |
Bug Description
Tempest api tests are not fully covering the 'mtu' and 'gateway' extension of manila api (version 1.18 and 1.20).
Implemented with:
https:/
and
https:/
Changed in manila: | |
assignee: | nobody → Marc Koderer (m-koderer) |
importance: | Undecided → Medium |
milestone: | none → newton-3 |
Changed in manila: | |
milestone: | newton-3 → ocata-1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/349506 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=e3afcd751ff 8e681867e1c7a05 4684277ec2874b
Committed: https:/
Submitter: Jenkins
Branch: master
commit e3afcd751ff8e68 1867e1c7a054684 277ec2874b
Author: Marc Koderer <email address hidden>
Date: Thu Aug 4 15:01:29 2016 +0200
Add MTU information in DB and API
MTU value can be different for each neutron network.
E.g. for high-performance use-cases it's very important to also
support MTU's with jumbo frames.
This patch exposes this information to the drivers. Each driver
should setup its resources accordingly.
The tempest test actually just covers the api change. Better coverage will
be added when the container driver lands.
APIImpact
DocImpact
Change-Id: I9b4efae620ec9f 6790547c8fffc58 872d43277f5
Implements: bp add-network-mtu
Related-Bug: #1612528