commit | 23e5d1953c38e4b7f0e91691c27d697de7d35715 | [log] [tgz] |
---|---|---|
author | Dennis Dmitriev <ddmitriev@mirantis.com> | Mon Oct 31 11:27:10 2016 +0200 |
committer | Dennis Dmitriev <ddmitriev@mirantis.com> | Mon Oct 31 11:27:10 2016 +0200 |
tree | 858e26a507871630c3787a7217d2a9f04853407e | |
parent | 3bf410eac9b4d1a9b066a6d249d02b0e0704d5d1 [diff] |
Working deploy for controller and compute nodes - use 'dash' branch for mk-lab-salt-model repo (it has a lot of improvements and fixes) - use less number of nodes to match the 'mk22-lab-advanced' model - force update packages before configuring salt.minions - use saltstack repo for latest salt.minions on trusty * Note if the deploy starts from an 'underlay' snapshot, keepalived can lose VIP after update DHCP leases on nodes. It's better to start deploy from clean environment.
Default template used here requires 20 vCPU and 52Gb host RAM.
git clone https://github.com/Mirantis/tcp-qa
cd ./tcp-qa
pip install -r ./tcp_tests/requirements.txt
dos-manage.py migrate
wget https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img -O ./trusty-server-cloudimg-amd64.qcow2
wget https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img -O ./xenial-server-cloudimg-amd64.qcow2
export ENV_NAME=tcpcloud-mk22 # Optional
export IMAGE_PATH1404=./trusty-server-cloudimg-amd64.qcow2
export IMAGE_PATH1604=./xenial-server-cloudimg-amd64.qcow2
export SHUTDOWN_ENV_ON_TEARDOWN=false # Optional
py.test -vvv -s -k test_tcp_install_default
dos.py create-env ./tcp_tests/templates/tcpcloud-default.yaml
dos.py start "${ENV_NAME}"
Then, wait until cloud-init is finished and port 22 is open (~3-4 minutes), and login with root:r00tme