14 Commits

Author SHA1 Message Date
Giulio Fidente
c7ec726276 Use container_file_t for Cinder*NfsMountOptions by default
This is so that share content is usable by cinder-volume and other
containers mounting the same share.

Closes-Bug: 1890291
Change-Id: Iacf7c9c368b26106e9921b35996c134aacb9acd7
2020-08-26 13:04:10 +02:00
Martin Schuppert
1c241362ff fix storage.yaml to write environments/storage/nova-nfs.yaml
753a3504184d966c63121ca95bc0135afbc83a75 removed ceph entries
from sample-env-generator/storage.yaml which resulted in nova-nfs
and cinder-netapp-config to be in the same section. Therefore
environment_generator.py did not update the nova-nfs.yaml .

Also add quotes to the nfs version as they are required in
the resulting nova-nfs.yaml .

Closes-Bug: #1825374

Change-Id: I209480f209e3a8841362ea619b1c9b073c89f338
2019-04-18 15:03:19 +00:00
Martin Schuppert
393e89bfb6 Make nfs version for nova ephemeral storage configurable
New parameter ``NovaNfsVersion`` allow configuring the NFS version
used for nova storage (when NovaNfsEnabled is true). Since NFSv3
does not support full locking a NFSv4 version need to be used. To
not break current installations the default is the previous hard
coded version 4.

Change-Id: I810478ed82ee6dc056d9652be91dc45b123e78cf
2019-03-19 11:42:32 +00:00
Jill Rouleau
98ecf97609 step2: flatten nova service configuration
This change combines the previous puppet and docker files
into a single file that performs the docker service installation
and configuration. With this patch the baremetal version of
nova has been removed.

Change-Id: Ia41a6adf9fda2d6be8f1b5ac57854381b7f92ce7
2019-02-13 06:20:55 +00:00
Alan Bishop
639285f091 Update parameters for cinder's Netapp backend
Update THT to align with puppet-tripleo changes made in [1]
- Add new CinderNetappPoolNameSearchPattern parameter
- Deprecate CinderNetappStoragePools parameter
- Remove previously deprecated CinderNetappEseriesHostType parameter

[1] https://review.openstack.org/570406

Fix relative path in file the sample-env-generator uses to generate
environments/storage/cinder-netapp-config.yaml.

Change-Id: I813ca60eb5ce9e008e1b72e88d83709d3125676f
2019-01-24 15:39:00 -05:00
David J Peacock
123f40a565 flatten cinder service configuration
This change combines the previous puppet and docker files into a single
file that performs the docker service installation and configuration.

With this patch the baremetal version of cinder services has been removed.

Change-Id: I88f047a8ee9c3eed80e4c48ed9cabdb3035d518b
Related-Blueprint: services-yaml-flattening
2019-01-18 08:55:26 -05:00
Cédric Jeanneret
7fbc4b098f Flatten Glance service configuration
This change combines the previous puppet and docker files into a single file
that performs the docker service installation and configuration.

With this patch the baremetal version of glance services has been removed.

Change-Id: Ie2ac2072f0742ec5e521fc6e3734e89f8a007077
Related-Blueprint: services-yaml-flattening
2018-12-14 08:23:32 +01:00
Alan Bishop
d989c01ce4 Clean up env files for Cinder's Netapp backend
Remove the misleading comment from the cinder-netapp-config.yaml file in
the environments directory that claimed the file is deprecated in favor
of the 'sample-env-generator' file in the environments/storage directory.
The sample-env-generator has not been widely adopted, and the Netapp
file in the environments directory is still being maintained.

Update the sample-env-generator files so they specify the
OS::TripleO::Services::CinderBackendNetApp composable service.

Closes-Bug: 1779397
Change-Id: If0343e96700bf13c0d49c3ae3c311ada1c26a0c0
2018-06-29 13:58:57 -04:00
Pranali Deore
a089310bf3 Add support of shared staging location for glance-direct
In the case of an HA setup (ie with 3 controller nodes) if image
import method is 'glance-direct', it would require a shared
consistent staging location on the controller nodes otherwise it
might happen that the image is uploaded to one node and triggering
the import is executed on a different node - where the image does not
exist.

Hence when import method 'glance-direct' is needed, operators need to
enable it explicitly with enabling NFS across the controller nodes
to share the staging.

Change-Id: I9a5bff5e5d0c3e109b73d691cc9088904a0401ac
Closes-Bug: #1765439
2018-05-22 21:40:13 +05:30
Giulio Fidente
753a350418 Remove support for puppet-ceph
Deployment of a managed Ceph cluster using puppet-ceph
is not supported from the Pike release. From Queens it
is not supported use of puppet-ceph when using an
external Ceph cluster either.

This change removes the old templates necessary to
support deployment of Ceph via puppet-ceph.

Implements: blueprint remove-puppet-ceph
Change-Id: I17b94e8023873f3129a55e69efd751be0674dfcb
2018-05-18 14:00:30 +02:00
Rajesh Tailor
6b6ae966ba Allow configuration of NFS backend for Nova
Allow NFS configuration of storage backend for Nova.
This way the instances files will be stored on a shared
NFS storage.

Implements: bp tripleo-nova-nfs

Depends-On: Id15aec6324814a871e87f19f24999b0e3b8a8f05

Change-Id: Ie4fe217bd119b638f42c682d21572547f02f17b2
2018-05-16 11:18:48 +05:30
Pranali Deore
5f7fdb1656 Add support of netapp configuration for glance in THT
This change adds all the required netapp environment configuartion
for glance in heat template.

Change-Id: Ib44796f77cbc50c3b3c37dcdd37a59f48a7baa1a
Closes-Bug: #1740456
2018-03-01 17:07:34 +05:30
Ben Nemec
56bf9cfb78 Fix enable-ceph sample environment
The necessary resource registry entries were missing from this env
and the old environment was not deprecated.

Change-Id: I6a9b148514fc5da1f96b9fd7fe09f564c2f82419
2017-07-26 13:36:52 +00:00
Ben Nemec
8d086b1710 Add storage sample environments
Starts converting storage-related sample environments to the tool,
and adds a few new ones for demonstration purposes.

This has required the addition of a new category of parameter
overrides in the tool.  There are some parameters that are part of
the public API of roles that should not normally be included in a
sample environment for that role.  Examples are EndpointMap and
ServiceNetMap.  Those are both passed into most (all?) roles, but
their template defaults are not useful (both default to {}).
Unless we are explicitly creating a sample environment that
overrides those defaults we don't want them included.

Parameters such as RoleName and RoleParameters are similar.  We
can't change them because they are part of the composable roles
interface and that would break any existing custom roles, but we
don't really want them included normally either.  It's possible
these could be made completely private, but there have been some
very preliminary discussions about generating role samples that
might actually want to set them.

In order to avoid issues with editing the unit test file in editors
that strip trailing whitespace, the minor formatting bug where
params like EndpointMap had a trailing space after the name has
also been fixed.

Change-Id: If11f30c734bfbc17d463a9890c736d7477186fb9
2017-06-12 15:02:50 -05:00