Actually , command
[boris@fedora24wks tripleo-quickstart]$ bash quickstart.sh -p quickstart-extras.yml -r
quickstart-extras-requirements.txt -R newton --config config/general_config/ha.yml
$VIRTHOST
Seems to work nicely in case when correct ansible environment has been setup for
quickstart.sh
prior to start command above. I have not seen for a while all scripts generated and
undercloud been ready for immediate overcloud-deploy.sh run.
Bug filed to upstream
https://bugs.launchpad.net/tripleo-quickstart/+bug/1653344
Thanks
Boris.
________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Saturday, December 31, 2016 2:31 PM
To: rdo-list(a)redhat.com
Subject: Re: [rdo-list] How to work with TripleO QS after commit
6c3cd87a6639b15ad84b798f76e8a1f65877855a ?
When I run with old syntax ( no matter it is already useless ) under $HOME/.quickstart I
can find
[boris@fedora24wks ~]$ find . -name ansible-playbook -print
./.quickstart/bin/ansible-playbook
Than I clean everything up and run :-
[boris@fedora24wks ~]$ rm -fr .ansible .quickstart tripleo-quickstart
[boris@fedora24wks ~]$ git clone
https://github.com/openstack/tripleo-quickstart
Cloning into 'tripleo-quickstart'...
remote: Counting objects: 5741, done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 5741 (delta 20), reused 0 (delta 0), pack-reused 5673
Receiving objects: 100% (5741/5741), 923.94 KiB | 726.00 KiB/s, done.
Resolving deltas: 100% (2962/2962), done.
Checking connectivity... done.
[boris@fedora25wks ~]$ cd tripleo*
[boris@fedora25wks tripleo-quickstart]$ ssh root@$VIRTHOST uname -aLinux
Server73CentOS.localdomain 3.10.0-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
[boris@fedora25wks tripleo-quickstart]$ bash quickstart.sh -p quickstart-extras.yml -r
quickstart-extras-requirements.txt --tags all $VIRTHOST
Command :-
[boris@fedora24wks ~]$ find . -name ansible-playbook -print
been run under /home/boris cannot find "ansible-playbook"
Looks as a bug for myself at least in meantime.
Thanks.
Boris.
________________________________
From: rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on behalf of Boris
Derzhavets <bderzhavets(a)hotmail.com>
Sent: Friday, December 30, 2016 12:58 PM
To: rdo-list(a)redhat.com
Subject: [rdo-list] How to work with TripleO QS after commit
6c3cd87a6639b15ad84b798f76e8a1f65877855a ?
What commit does ?
Author: Wes Hayutin <weshayutin(a)gmail.com>
Date: Tue Dec 13 17:07:54 2016 -0500
move the undercloud deploy role to quickstart-extras for composability
In an effort to make more of the tripleo deployment ci more composable
it has been discussed to break out the undercloud deployment into it's
own role. There are examples where additional configuration is needed
prior to the undercloud installation such as dpdk, and installing in
other ci environments.
This patch moves the undercloud deployment from the quickstart.yml
playbook to the quickstart-extras.yml playbook
-----
So command :-
$ bash quickstart.sh -R newton --config config/general_config/ha.yml $VIRTHOST
still works , but no longer deploys undercloud and create stackrc file
Follow
https://github.com/openstack/tripleo-quickstart
and run as test :-
[boris@fedora25wks ~]$ rm -fr .ansible .quickstart tripleo-quickstart
[boris@fedora25wks ~]$ git clone
https://github.com/openstack/tripleo-quickstart
Cloning into 'tripleo-quickstart'...
remote: Counting objects: 5741, done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 5741 (delta 20), reused 0 (delta 0), pack-reused 5673
Receiving objects: 100% (5741/5741), 923.94 KiB | 726.00 KiB/s, done.
Resolving deltas: 100% (2962/2962), done.
Checking connectivity... done.
[boris@fedora25wks ~]$ cd tripleo*
[boris@fedora25wks tripleo-quickstart]$ ssh root@$VIRTHOST uname -aLinux
Server73CentOS.localdomain 3.10.0-514.2.2.el7.x86_64 #1 SMP Tue Dec 6 23:06:41 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
[boris@fedora25wks tripleo-quickstart]$ bash quickstart.sh -p quickstart-extras.yml -r
quickstart-extras-requirements.txt --tags all $VIRTHOST
. . . . . . . .
Installing OpenStack mitaka on host 192.168.0.74
Using directory /home/boris/.quickstart for a local working directory
+ export ANSIBLE_CONFIG=/home/boris/.quickstart/tripleo-quickstart/ansible.cfg
+ ANSIBLE_CONFIG=/home/boris/.quickstart/tripleo-quickstart/ansible.cfg
+ export ANSIBLE_INVENTORY=/home/boris/.quickstart/hosts
+ ANSIBLE_INVENTORY=/home/boris/.quickstart/hosts
+ source /home/boris/.quickstart/tripleo-quickstart/ansible_ssh_env.sh
++ export OPT_WORKDIR=/home/boris/.quickstart
++ OPT_WORKDIR=/home/boris/.quickstart
++ export SSH_CONFIG=/home/boris/.quickstart/ssh.config.ansible
++ SSH_CONFIG=/home/boris/.quickstart/ssh.config.ansible
++ touch /home/boris/.quickstart/ssh.config.ansible
++ export 'ANSIBLE_SSH_ARGS=-F /home/boris/.quickstart/ssh.config.ansible'
++ ANSIBLE_SSH_ARGS='-F /home/boris/.quickstart/ssh.config.ansible'
+ '[' 0 = 0 ']'
+ rm -f /home/boris/.quickstart/hosts
+ '[' 192.168.0.74 = localhost ']'
+ '[' '' = 1 ']'
+ VERBOSITY=vv
+ ansible-playbook -vv /home/boris/.quickstart/playbooks/quickstart-extras.yml -e
@/home/boris/.quickstart/tripleo-quickstart/config/general_config/minimal.yml -e
ansible_python_interpreter=/usr/bin/python -e
@/home/boris/.quickstart/config/release/mitaka.yml -e
local_working_dir=/home/boris/.quickstart -e virthost=192.168.0.74 -t all,teardown-nodes
quickstart.sh: line 433: ansible-playbook: command not found <=== Error
Please advise. All what I need is deploying undercloud via
$ bash quickstart.sh -R newton --config config/general_config/ha.yml $VIRTHOST
as it happened before 12/13/16 or how manually do it after log into undercloud
Thanks
Boris
[
https://avatars0.githubusercontent.com/u/324574?v=3&s=400]<https:/...
GitHub - openstack/tripleo-quickstart: Ansible based
...<https://github.com/openstack/tripleo-quickstart>
github.com
Now that tripleo-quickstart and tripleo-quickstart-extras are both upstream it makes sense
for quickstart-extras to be a default requirement for the setup via pip.