ad2f2e00e8
Various options are available when formatting the different file systems we support. This change implements a hash to capture many of the different options we use throughout a test deployment. * BTRFS: set metadata for test volumes to single. the metadata on our loopback devices was defaulting the the file-system default of DUP (duplicate) which is reasonable on a production deployment however on a loopback device it makes more sense to set the data and metadata options to "single". This will help eliminate the issues were seeing with intermittently full file-systems. * XFS: set block sizes, placement groups, and do not issue discards at create. This will speed up the time it takes to format an XFS partition as well as ensure things remain speedy under load. * EXT4: speed up directory lookups Use hashed b-trees to speed up name lookups in large directories. Change-Id: I004768d98da194cc90b36cdf72dbf75b24a661a2 Signed-off-by: Kevin Carter <kevin.carter@rackspace.com> |
||
---|---|---|
deploy-guide/source | ||
doc | ||
etc | ||
inventory | ||
osa_toolkit | ||
playbooks | ||
releasenotes | ||
scripts | ||
tests | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
ansible-role-requirements.yml | ||
ansible-role-requirements.yml.example | ||
bindep.txt | ||
global-requirement-pins.txt | ||
LICENSE.txt | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
Vagrantfile |
Team and repository tags
OpenStack-Ansible
OpenStack-Ansible is an official OpenStack project which aims to deploy production environments from source in a way that makes it scalable while also being simple to operate, upgrade, and grow.
For an overview of the mission, repositories and related Wiki home page, please see the formal Home Page for the project.
For those looking to test OpenStack-Ansible using an All-In-One (AIO) build, please see the Quick Start guide.
For more detailed Installation and Operator documentation, please see the Deployment Guide.
If OpenStack-Ansible is missing something you'd like to see included, then we encourage you to see the Developer Documentation for more details on how you can get involved.
Developers wishing to work on the OpenStack-Ansible project should always base their work on the latest code, available from the master GIT repository at Source.
If you have some questions, or would like some assistance with
achieving your goals, then please feel free to reach out to us on the OpenStack Mailing Lists
(particularly openstack-operators or openstack-dev) or on IRC in
#openstack-ansible
on the freenode network.
OpenStack-Ansible Roles
OpenStack-Ansible offers separate role repositories for each individual role that OpenStack-Ansible supports. For individual role configuration options, see the Role Documentation.
An individual role's source code can be found at: https://git.openstack.org/cgit/openstack/openstack-ansible-<ROLENAME>.