This website requires JavaScript.
Explore
Get Started
openstack
/
devstack
Code
Issues
Proposed changes
42be2425d8
Branches
Tags
View all branches
devstack
/
roles
/
sync-devstack-data
/
defaults
/
main.yaml
3 lines
80 B
YAML
Raw
Normal View
History
Unescape
Escape
Fix multinode mode for devstack Extend the devstack job so that it can support both single and multinode cases. Multinode mode require extra settings in devstack configuration, some of which as subnode specific, some controller specific. Also keep a simple devstack-multinode job defined for now so we can run a multinode job in devstack gate, until the full tempest multinode job is ready to match the old gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial-nv. Fixing multinode also requires sharing the CA configuration between controller and peers, overlay network configuration for communication between virtual machines and running discover_hosts for nova after the subnode has been setup. The extra orchestration required for multinode is encoded in a dedicated role to allow for jobs in other repos to re-use it. Change-Id: I2dcbd9bdb401860820e655d97aa3c4775af2827f
2018-02-17 22:21:26 +00:00
devstack_base_dir
:
/opt/stack
sync-devstack-data: new argument devstack_data_base_dir When the role is used by grenade, the data directory is shared among different devstack executions, and the base directory is different, for example: /opt/stack/data vs /opt/stack/{old,new}. The new devstack_data_base_dir parameter allows user to specify a base directory for the data/ directory which is unrelated to the devstack directory. The default value is devstack_base_dir, so the default behavior is unchanged. Change-Id: Ie69b7b51947cbf1a8b31d2701783de2fb56a2d33
2019-04-02 12:28:31 +02:00
devstack_data_base_dir
:
"{{ devstack_base_dir }}"
Copy Permalink