In meantime indercloud gets created with swift container "overcloud" already been built.

It results  failure to start Mistral Work-flow by script :-

#!/bin/bash -x
source /home/stack/stackrc   
openstack overcloud deploy  \
 --control-scale 3 --compute-scale 1 \
 --libvirt-type qemu \
 --ntp-server pool.ntp.org  \
 --templates  /usr/share/openstack-tripleo-heat-templates \
 -e  /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml \
 -e  /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
 -e  /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \
 -e  $HOME/network_env.yaml

 Attempt  `swift delete overcloud`  and restart deployment fails to start Mistral work-flow either way.  Changes seems to be done a bit latter 10/13/16 (GMT+4) due to 10/12-10/13 old schema still worked experiencing   some delay during updating plan and starting mistral work flow.

However, command `bash quickstart.sh   -R newton --config ./config/general_config/ha.yml  $VIRTHOST`   still completes with old instructions

##################################
Virtual Environment Setup Complete
##################################

Access the undercloud by:
    ssh -F /home/jon/.quickstart/ssh.config.ansible undercloud
Follow the documentation in the link below to complete your deployment.
    http://ow.ly/c44w304begR   <== standard instructions from
                                   tripleo.org

which seems to be outdated at the moment .
I cannot proceed with script above when swift container 
"overcloud" already exists. 

Thanks.

Boris.