<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Raoul Scarazzini <rasca@redhat.com><br>
<b>Sent:</b> Wednesday, August 24, 2016 11:34 AM<br>
<b>To:</b> Boris Derzhavets; Wesley Hayutin; Attila Darazs<br>
<b>Cc:</b> rdo-list<br>
<b>Subject:</b> Re: [rdo-list] Instack-virt-setup vs TripleO QuickStart in regards of managing HA PCS/Corosync cluster via pcs CLI</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 24/08/2016 09:54, Boris Derzhavets wrote:<br>
[...]<br>
> - Which version are you using? The latest? So are you installing from<br>
> master?<br>
>><br>
> No idea. My actions :-<br>
> <br>
> $ rm -fr .ansible .quickstart tripleo-quickstart<br>
> $ git clone <a id="LPlnk593663" href="https://github.com/openstack/tripleo-quickstart">
https://github.com/openstack/tripleo-quickstart</a>
<div style="margin-bottom: 20px; overflow: auto; width: 100%; text-indent: 0px;" id="LPBorder_GT_14720409913870.025559156153063922">
<table style="width: 90%; background-color: rgb(255, 255, 255); position: relative; overflow: auto; padding-top: 20px; padding-bottom: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); border-bottom: 1px dotted rgb(200, 200, 200);" id="LPContainer_14720409913800.6981633271846324" cellspacing="0">
<tbody>
<tr style="border-spacing: 0px;" valign="top">
<td colspan="1" style="width: 250px; position: relative; display: table-cell; padding-right: 20px;" id="ImageCell_14720409913810.6922925452699036">
<div style="background-color: rgb(255, 255, 255); height: 250px; position: relative; margin: auto; display: table; width: 250px;" id="LPImageContainer_14720409913820.6502618736706608">
<a target="_blank" href="https://github.com/openstack/tripleo-quickstart" style="display: table-cell; text-align: center;" id="LPImageAnchor_14720409913830.17373490139315728"><img id="LPThumbnailImageID_14720409913830.49087009163101536" aria-label="Preview image with link selected. Double-tap to open the link." style="display: inline-block; max-width: 250px; max-height: 250px; height: 250px; width: 250px; border-width: 0px; vertical-align: bottom;" width="250" height="250" src="https://avatars0.githubusercontent.com/u/324574?v=3&s=400"></a></div>
</td>
<td colspan="2" style="vertical-align: top; position: relative; padding: 0px; display: table-cell;" id="TextCell_14720409913840.3412332236955842">
<div id="LPRemovePreviewContainer_14720409913840.14363945841627324"></div>
<div style="top: 0px; color: rgb(0, 120, 215); font-weight: 400; font-size: 21px; font-family: "wf_segoe-ui_light","Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; line-height: 21px;" id="LPTitle_14720409913840.5413771112841603">
<a target="_blank" href="https://github.com/openstack/tripleo-quickstart" style="text-decoration: none;" id="LPUrlAnchor_14720409913850.2578844521310333">GitHub - openstack/tripleo-quickstart: Ansible based ...</a></div>
<div style="margin: 10px 0px 16px; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 14px;" id="LPMetadata_14720409913850.891811225751335">
github.com</div>
<div style="display: block; color: rgb(102, 102, 102); font-weight: 400; font-family: "wf_segoe-ui_normal","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: hidden;" id="LPDescription_14720409913860.32895896091063626">
tripleo-quickstart - Ansible based project for setting up TripleO virtual environments</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> $ cd tripleo*<br>
> $ ssh root@$VIRTHOST uname -a<br>
> $ vi /config/general_config/ha.yml ==> to tune && save<br>
> $ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST<br>
<br>
OK, it can be useful to see what's inside ha.yml, but the command you<br>
mentioned does not specify a branc, so it uses "master", so Newton, so<br>
you're using a totally different setup from mitaka, especially from a<br>
cluster perspective.<br>
========================================================================<br>
Addressing your requests<br>
========================================================================<br>
<div>[boris@fedora24wks tripleo-quickstart]$ cat ./config/general_config/ha.yml<br>
# Deploy an HA openstack environment.<br>
#<br>
# This will require (6144 * 4) == approx. 24GB for the overcloud<br>
# nodes, plus another 8GB for the undercloud, for a total of around<br>
# 32GB.<br>
control_memory: 6144<br>
compute_memory: 6144<br>
default_vcpu: 2<br>
<br>
undercloud_memory: 8192<br>
<br>
# Giving the undercloud additional CPUs can greatly improve heat's<br>
# performance (and result in a shorter deploy time).<br>
undercloud_vcpu: 2<br>
<br>
# Create three controller nodes and one compute node.<br>
overcloud_nodes:<br>
- name: control_0<br>
flavor: control<br>
- name: control_1<br>
flavor: control<br>
- name: control_2<br>
flavor: control<br>
<br>
- name: compute_0<br>
flavor: compute<br>
- name: compute_1<br>
flavor: compute<br>
# We don't need introspection in a virtual environment (because we are<br>
# creating all the "hardware" we really know the necessary<br>
# information).<br>
step_introspect: true<br>
<br>
# Tell tripleo about our environment.<br>
network_isolation: true<br>
extra_args: >-<br>
--control-scale 3 --compute-scale 2 --neutron-network-type vxlan<br>
--neutron-tunnel-types vxlan<br>
--ntp-server pool.ntp.org<br>
test_tempest: false<br>
test_ping: true<br>
enable_pacemaker: true<br>
<br>
<font size="2"><span style="font-size:10pt;">$ bash quickstart.sh --config ./config/general_config/ha.yml $VIRTHOST</span></font><br>
<br>
EXIT ( undrecloud has been built )<br>
<br>
##################################<br>
Virtual Environment Setup Complete<br>
##################################<br>
<br>
Access the undercloud by:<br>
<br>
ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud<br>
<br>
There are scripts in the home directory to continue the deploy:<br>
<br>
overcloud-deploy.sh will deploy the overcloud<br>
overcloud-deploy-post.sh will do any post-deploy configuration<br>
overcloud-validate.sh will run post-deploy validation<br>
<br>
Alternatively, you can ignore these scripts and follow the upstream docs,<br>
starting from the overcloud deploy section:<br>
<br>
http://ow.ly/1Vc1301iBlb<br>
<br>
##################################<br>
Virtual Environment Setup Complete<br>
##################################<br>
<br>
[boris@fedora24wks tripleo-quickstart]$ ssh -F /home/boris/.quickstart/ssh.config.ansible undercloud<br>
Warning: Permanently added '192.168.1.74' (ECDSA) to the list of known hosts.<br>
Warning: Permanently added 'undercloud' (ECDSA) to the list of known hosts.<br>
Last login: Wed Aug 24 12:13:16 2016 from gateway<br>
<br>
[stack@undercloud ~]$ sudo su -<br>
<br>
[root@undercloud stack]# cd /etc/yum.repos.d<br>
[root@undercloud yum.repos.d]# ls -l<br>
total 40<br>
-rw-r--r--. 1 root root 1664 Dec 9 2015 CentOS-Base.repo<br>
-rw-r--r--. 1 root root 1057 Aug 24 02:58 CentOS-Ceph-Hammer.repo<br>
-rw-r--r--. 1 root root 1309 Dec 9 2015 CentOS-CR.repo<br>
-rw-r--r--. 1 root root 649 Dec 9 2015 CentOS-Debuginfo.repo<br>
-rw-r--r--. 1 root root 290 Dec 9 2015 CentOS-fasttrack.repo<br>
-rw-r--r--. 1 root root 630 Dec 9 2015 CentOS-Media.repo<br>
-rw-r--r--. 1 root root 1331 Dec 9 2015 CentOS-Sources.repo<br>
-rw-r--r--. 1 root root 1952 Dec 9 2015 CentOS-Vault.repo<br>
-rw-r--r--. 1 root root 162 Aug 24 02:58 delorean-deps.repo<br>
-rw-r--r--. 1 root root 220 Aug 24 02:58 delorean.repo<br>
<br>
[root@undercloud yum.repos.d]# cat delorean-deps.repo<br>
[delorean-mitaka-testing]<br>
name=dlrn-mitaka-testing<br>
baseurl=http://buildlogs.centos.org/centos/7/cloud/$basearch/openstack-mitaka/<br>
enabled=1<br>
gpgcheck=0<br>
priority=2<br>
<br>
[root@undercloud yum.repos.d]# cat delorean.repo<br>
[delorean]<br>
name=delorean-openstack-rally-3909299306233247d547bad265a1adb78adfb3d4<br>
baseurl=http://trunk.rdoproject.org/centos7-mitaka/39/09/3909299306233247d547bad265a1adb78adfb3d4_4e6dfa3c<br>
enabled=1<br>
gpgcheck=0<br>
</div>
<br>
Thanks<br>
Boris.<br>
===================================================================================<br>
> When I get prompt to login to undercloud<br>
> /etc/yum.repos.d/ contains delorean.repo ( on fresh undercloud QS build )<br>
> files pointing to Mitaka Delorean trunks.<br>
> Just check for yourself.<br>
<br>
Where can I check? On the link you posted I cannot find these files from<br>
the quickstart installation...<br>
<br>
> - Are the two versions the same while using quickstart and<br>
> instack-virt-setup?<br>
> No the versions are different ( points in delorean.repos differ )<br>
<br>
This could have a great impact while comparing results.<br>
<br>
> - Do we have some logs to look at?<br>
> Sorry, it was not my concern.<br>
> My primary target was identify sequence of steps<br>
> which brings PCS Cluster to proper state with 100% warranty.<br>
<br>
This is strictly related on all the stuff I've mentioned above. Things<br>
must work without workarounds like cleanup or similar things. If<br>
something breaks and we're using correct setup steps then we're in front<br>
of a bug.<br>
But to analyze a bug we need logs.<br>
<br>
> Again, I think here we're hitting a version issure.<br>
> I tested QuickStart ( obtained just at the same time on different box)<br>
> delorean.repo files in instack-virt-setup build of VENV<br>
> It doesn't change much final overcloud cluster behavior.<br>
> I am aware of this link is outdated ( due to Wesley Hayutin respond )<br>
> <a href="https://bluejeans.com/s/a5ua/">https://bluejeans.com/s/a5ua/</a><br>
> However , my current understanding of QuickStart CI ( not TripleO CI )<br>
> is based on this video<br>
> I believe the core reason is the way how Tripleo QS assembles undercloud<br>
> for VENV build.<br>
> It makes HA Controllers cluster pretty stable and always recoverable<br>
> (VENV case)<br>
<br>
The VENV should not matter at all in terms of cluster configuration on<br>
the overcloud.<br>
<br>
> It is different from official way at least in meantime.<br>
> I've already wrote TripleO QS nowhere issues :-<br>
> $ openstack overcloud images build --all ===> that is supposed to be<br>
> removed<br>
> as far as I understand TripleO Core team intend.<br>
> Boris.<br>
<br>
As I said there's a lot of mix inside the repo and thins makes the debug<br>
really difficult.<br>
<br>
-- <br>
Raoul Scarazzini<br>
rasca@redhat.com<br>
</div>
</span></font></div>
</div>
</body>
</html>