Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI

Looking at quickstart.sh I see :- : ${OPT_BOOTSTRAP:=0} : ${OPT_CLEAN:=0} : ${OPT_PLAYBOOK:=quickstart.yml} : ${OPT_RELEASE:=mitaka} : ${OPT_RETAIN_INVENTORY_FILE:=0} : ${OPT_SYSTEM_PACKAGES:=0} : ${OPT_TAGS:=$DEFAULT_OPT_TAGS} : ${OPT_TEARDOWN:=nodes} : ${OPT_WORKDIR:=$HOME/.quickstart} . . . . . echo " -R, --release OpenStack release to deploy (default=$OPT_RELEASE)" <== line 147 It clearly shows that default release is Mitaka Would you like to test Newton then command line should look like :- $ bash quickstart.sh --config ./ha.yml --release newton $VIRTHOST Boris. ________________________________ From: Raoul Scarazzini <rasca(a)redhat.com&gt; Sent: Wednesday, August 24, 2016 5:25 PM To: Boris Derzhavets; Wesley Hayutin; Attila Darazs Cc: rdo-list Subject: Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI On 24/08/2016 14:21, Boris Derzhavets wrote: [...] [...] Not only. At this point everything should be built. [...] This sounds really strange, since you should get master repo (so Newton, not Mitaka) while using quickstart without specifying --release. How long ago did you downloaded the quickstart git repo? Can you redeploy everything from scratch with the latest pull from quickstart's git repo? -- Raoul Scarazzini rasca(a)redhat.com