On 24/08/2016 14:21, Boris Derzhavets wrote:
[...]
> ========================================================================
> Addressing your requests
> ========================================================================
> [boris@fedora24wks tripleo-quickstart]$ cat ./config/general_config/ha.yml
[...]
> $ bash quickstart.sh --config ./config/general_config/ha.yml   $VIRTHOST
> EXIT ( undrecloud has been built )

Not only. At this point everything should be built.
>
Overcloud is not built at this moment. I log into
undercloud and run overcloud-deploy.sh
>
[...]
> [root@undercloud stack]# cd /etc/yum.repos.d
> [root@undercloud yum.repos.d]# cat delorean-deps.repo
> [delorean-mitaka-testing]
> name=dlrn-mitaka-testing
> baseurl=http://buildlogs.centos.org/centos/7/cloud/$basearch/openstack-mitaka/
> enabled=1
> gpgcheck=0
> priority=2
> [root@undercloud yum.repos.d]# cat delorean.repo
> [delorean]
> name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4
> baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c
> enabled=1
> gpgcheck=0

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?
>
5 min
>
Can you
redeploy everything from scratch with the latest pull from quickstart's
git repo?

>
   That is what I have  been doing for you since 10 a.m. this morning (MSK)
Everything has been built from scratch during current business day.
Check time && date of `ls -l` output
_undercloud.qcow2  takes 3.5 hr for download 2.9 GB. What causes
all deployment procedure to take at least 5-6 hr.

Usually via my fiber channel I get 5 GB in 15 min from any location in US or Europe.
Site http://artifacts.ci.centos.org/artifacts/rdo/images/mitaka/delorean/stable/
is extremely slow .  This issue has pretty long story.

  $ git clone https://github.com/openstack/tripleo-quickstart takes about 5 min.

Rich Bowen stated a while ago that default release ( no spec on command line)
works  with Mitaka. Please, resolve this issue , because it is obviously not on my side.

Boris.
>

--
Raoul Scarazzini
rasca@redhat.com