<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" color="#000000" face="Calibri, sans-serif"><b>From:</b> rdo-list-bounces@redhat.com <rdo-list-bounces@redhat.com> on behalf of Karanbir Singh <mail-lists@karan.org><br>
<b>Sent:</b> Friday, August 12, 2016 4:30 PM<br>
<b>To:</b> Xiandong Meng; David Moreau Simard<br>
<b>Cc:</b> rdo-list<br>
<b>Subject:</b> Re: [rdo-list] RDO CI hardware requirements for CentOS altarch</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">note that a key element to the messaging from our side is that the<br>
content is tested the way users use the code, not the way developers<br>
deliver the code - so ideally, we want to get down to baremetal<br>
deployments and validating distro v/s rdo and rdo v/s distro.<br>
<br>
> we typically see hundreds of bare metal deployments per day for rdo /<br>
> cloud SIG, and at the very least we should make an effort to sync<br>
> across the arch's if we can.<br>
<br>
In regards of <b>RDO</b> how much is percentage of TripleO bare metal<br>
deployments per <b>Mitaka</b> ( per Liberty ) ?<br>
If this info is closed by some reasons , sorry for question been asked.<br>
<br>
Thanks.<br>
Boris<br>
<br>
>so, as we work through what needs doing, lets make sure we factor in<br>
>the user story we want to deliver at the other end.<br>
<br>
Regards<br>
<br>
On 11/08/16 09:05, Xiandong Meng wrote:<br>
> OK, so the bottleneck is in "INSTALL / TEST (IMPORT IMAGES)" stage<br>
> with 2 Triple-O scenario, 3 Packstack and 3 OpenStack-Puppet test<br>
> jobs. So we may need up to (4 core, 8 GB memory)*3 to cover<br>
> PackStack and OpenStack-Puppet path as each Triple-O scenario will<br>
> need about 90 minutes. (So the shortest time is limited to 90<br>
> minutes assuming we maximize the parallelism level. )<br>
> <br>
> Now i need some input about the resource requirements for Triple-O<br>
> test scenarios.<br>
> <br>
> <br>
> <br>
> Regards,<br>
> <br>
> Alex Meng<<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>> mengxiandong@gmail.com<br>
> <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>><br>
> <br>
> On Thu, Aug 11, 2016 at 4:11 PM, David Moreau Simard<br>
> <dms@redhat.com <<a href="mailto:dms@redhat.com">mailto:dms@redhat.com</a>>> wrote:<br>
> <br>
> Right now the jobs are sequenced as outlined in the pipeline [1].<br>
> <br>
> First, the job "rdo-promote-get-hash-master" will run. If it is <br>
> successful, it triggers the next "stage" of the pipeline. Then, the<br>
> job "tripleo-quickstart-promote-master-delorean-build-images" will<br>
> run. If it is successfull, it triggers the next "stage" of the <br>
> pipeline. After that you have 8 jobs that, if capacity allows<br>
> (usually the case), will all run simultaneously. Otherwise, builds<br>
> can be queued until a slave can process them. ... and so on.<br>
> <br>
> We can't realistically run all these jobs in a sequence. <br>
> Considering they complete in 45 minutes (or more), we'd be looking<br>
> at a pipeline of over 6 hours of builds.<br>
> <br>
> [1]: <br>
> <a href="https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-promote-master/">
https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-promote-master/</a><br>
><br>
> <br>
<<a href="https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-promote-master/">https://ci.centos.org/view/rdo/view/promotion-pipeline/job/rdo-delorean-promote-master/</a>><br>
> <br>
> David Moreau Simard Senior Software Engineer | Openstack RDO<br>
> <br>
> dmsimard = [irc, github, twitter]<br>
> <br>
> <br>
> On Wed, Aug 10, 2016 at 11:52 PM, Xiandong Meng <br>
> <mengxiandong@gmail.com <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>>> wrote:<br>
>> OK, i mean on the same time, how many concurrent CI jobs may be<br>
> running? For<br>
>> example, at peak load, will<br>
> weirdo-master-promote-packstack-scenario001 ,<br>
>> weirdo-master-promote-packstack-scenario002 , <br>
>> weirdo-master-promote-packstack-scenario003 run at the same<br>
>> time?<br>
> Or they<br>
>> will run in sequence by design?<br>
>> <br>
>> <br>
>> Regards,<br>
>> <br>
>> Alex Meng mengxiandong@gmail.com <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>><br>
>> <br>
>> On Thu, Aug 11, 2016 at 2:50 PM, David Moreau Simard<br>
> <dms@redhat.com <<a href="mailto:dms@redhat.com">mailto:dms@redhat.com</a>>> wrote:<br>
>>> <br>
>>> Alex,<br>
>>> <br>
>>> Can you expand on what you mean by that ? The concurrency (or<br>
>>> lack thereof) of the jobs are more about the design of the job<br>
>>> itself -- or the environment it is run from as well as the<br>
>>> environment it is run on.<br>
>>> <br>
>>> The jobs part of the promotion pipeline [1] run a couple times<br>
> per day.<br>
>>> <br>
>>> [1]: <a href="https://ci.centos.org/view/rdo/view/promotion-pipeline/">https://ci.centos.org/view/rdo/view/promotion-pipeline/</a><br>
> <<a href="https://ci.centos.org/view/rdo/view/promotion-pipeline/">https://ci.centos.org/view/rdo/view/promotion-pipeline/</a>><br>
>>> <br>
>>> David Moreau Simard Senior Software Engineer | Openstack RDO<br>
>>> <br>
>>> dmsimard = [irc, github, twitter]<br>
>>> <br>
>>> <br>
>>> On Wed, Aug 10, 2016 at 9:45 PM, Xiandong Meng<br>
> <mengxiandong@gmail.com <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>>><br>
>>> wrote:<br>
>>>> David, thank you for your response.<br>
>>>> <br>
>>>> For Packstack and Puppet-OpenStack jobs, I noticed that<br>
>>>> usually<br>
> each job<br>
>>>> takes no more than 45 minutes. How many jobs may run in<br>
> parallel and how<br>
>>>> often they are triggered?<br>
>>>> <br>
>>>> Regards,<br>
>>>> <br>
>>>> Alex Meng mengxiandong@gmail.com<br>
>>>> <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>><br>
>>>> <br>
>>>> On Thu, Aug 11, 2016 at 2:24 AM, David Moreau Simard<br>
> <dms@redhat.com <<a href="mailto:dms@redhat.com">mailto:dms@redhat.com</a>>><br>
>>>> wrote:<br>
>>>>> <br>
>>>>> Hi Alex,<br>
>>>>> <br>
>>>>> I don't know the specifics of resource usage for<br>
>>>>> alternative architectures but I can tell about x86_64.<br>
>>>>> <br>
>>>>> Packstack and Puppet-OpenStack jobs are designed to run<br>
>>>>> within<br>
> 8GB of<br>
>>>>> RAM - either on a single virtual machine or on a single<br>
>>>>> bare metal server. I would say 4 cores is the minimum (or<br>
>>>>> otherwise job length is severely affected), 8 is best. Disk<br>
>>>>> space is not generally a concern, easily fitting within<br>
> 50GB of<br>
>>>>> space.<br>
>>>>> <br>
>>>>> I don't have the numbers for TripleO so I'll let someone<br>
>>>>> else<br>
> chime in<br>
>>>>> on that.<br>
>>>>> <br>
>>>>> David Moreau Simard Senior Software Engineer | Openstack<br>
>>>>> RDO<br>
>>>>> <br>
>>>>> dmsimard = [irc, github, twitter]<br>
>>>>> <br>
>>>>> <br>
>>>>> On Wed, Aug 10, 2016 at 6:18 AM, Xiandong Meng<br>
> <mengxiandong@gmail.com <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>>><br>
>>>>> wrote:<br>
>>>>>> We had discussed it a bit in previous RDO meeting on irc.<br>
>>>>>> I<br>
> want to<br>
>>>>>> write a separate mail for more broad and in-depth<br>
>>>>>> discussion here.<br>
>>>>>> <br>
>>>>>> <br>
>>>>>> For a master release (for now it is Newton), i noticed<br>
>>>>>> the<br>
> promotion<br>
>>>>>> pipes fall into three different categories: - Triple-O<br>
>>>>>> based CI test - Packstack based test - OpenStack-Puppet<br>
>>>>>> based test<br>
>>>>>> <br>
>>>>>> So what is the base minimal CI requirements to start<br>
>>>>>> with<br>
> for AltArch<br>
>>>>>> support? Since many of the CI test should work even with<br>
>>>>>> VMs<br>
> instead<br>
>>>>>> of physical nodes, can we start with 1-2 physical<br>
>>>>>> servers?<br>
>>>>>> <br>
>>>>>> Regards,<br>
>>>>>> <br>
>>>>>> Alex Meng mengxiandong@gmail.com<br>
>>>>>> <<a href="mailto:mengxiandong@gmail.com">mailto:mengxiandong@gmail.com</a>><br>
>>>>>> <br>
>>>>>> _______________________________________________ rdo-list<br>
>>>>>> mailing list rdo-list@redhat.com<br>
>>>>>> <<a href="mailto:rdo-list@redhat.com">mailto:rdo-list@redhat.com</a>> <br>
>>>>>> <a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
> <<a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a>><br>
>>>>>> <br>
>>>>>> To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
> <<a href="mailto:rdo-list-unsubscribe@redhat.com">mailto:rdo-list-unsubscribe@redhat.com</a>><br>
>>>> <br>
>>>> <br>
>> <br>
>> <br>
> <br>
> <br>
<br>
<br>
-- <br>
Karanbir Singh, Project Lead, The CentOS Project<br>
+44-207-0999389 | <a href="http://www.centos.org/">http://www.centos.org/</a> | twitter.com/CentOS<br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc">http://www.karan.org/publickey.asc</a><br>
<br>
-- <br>
Karanbir Singh<br>
+44-207-0999389 | <a href="http://www.karan.org/">http://www.karan.org/</a> | twitter.com/kbsingh<br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc">http://www.karan.org/publickey.asc</a><br>
<br>
_______________________________________________<br>
rdo-list mailing list<br>
rdo-list@redhat.com<br>
<a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
<br>
To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
</div>
</span></font></div>
</div>
</body>
</html>