magnum/magnum/tests
Mohammed Naser 26e36485d6 [fedora atomic k8s] Add boot from volume support
Support boot from volume for Kubernetes all nodes (master and worker)
so that user can create a big size root volume, which could be more
flexible than using docker_volume_size. And user can specify the
volume type so that user can leverage high performance storage, e.g.
NVMe etc.

And a new label etcd_volme_type is added as well so that user can
set volume type for etcd volume.

If the boot_volume_type or etcd_volume_type are not passed by labels,
Magnum will try to read them from config option
default_boot_volume_type and default_etcd_volume_type. A random
volume type from Cinder will be used if those options are not set.

Task: 30374
Story: 2005386

Co-Authored-By: Lingxian Kong <anlin.kong@gmail.com>
Co-Authored-By: Feilong Wang<flwang@catalyst.net.nz>

Change-Id: I39dd456bfa285bf06dd948d11c86867fc03d5afb
2019-09-12 09:38:33 +00:00
..
contrib Using Fedora Atomic 29 as default image 2019-08-24 09:37:35 +12:00
functional Use oslo_serialization instead of the json module directly 2019-01-21 16:28:03 -08:00
unit [fedora atomic k8s] Add boot from volume support 2019-09-12 09:38:33 +00:00
__init__.py Remove redundant FunctionalTest class 2015-07-15 03:39:11 +08:00
base.py Set is_admin flag correctly in RequestContext 2017-03-03 03:37:08 +00:00
conf_fixture.py Centralize config option: trust section 2016-09-22 05:57:46 +00:00
fake_notifier.py Emit notifications when bay operations get executed 2016-05-19 15:29:56 +08:00
fakes.py FakeLoopingCall raises IOError 2019-02-28 10:01:17 +00:00
policy_fixture.py Register default magnum service and stat policies in code 2017-10-23 02:57:29 +00:00
utils.py Remove redundant code from magnum.test.utils 2015-07-20 21:53:12 +08:00