David, thank you for your response.
For Packstack and Puppet-OpenStack jobs, I noticed that usually each job
takes no more than 45 minutes. How many jobs may run in parallel and how
often they are triggered?
Regards,
Alex Meng <mengxiandong(a)gmail.com>
mengxiandong(a)gmail.com
On Thu, Aug 11, 2016 at 2:24 AM, David Moreau Simard <dms(a)redhat.com> wrote:
Hi Alex,
I don't know the specifics of resource usage for alternative
architectures but I can tell about x86_64.
Packstack and Puppet-OpenStack jobs are designed to run within 8GB of
RAM - either on a single virtual machine or on a single bare metal
server.
I would say 4 cores is the minimum (or otherwise job length is
severely affected), 8 is best.
Disk space is not generally a concern, easily fitting within 50GB of space.
I don't have the numbers for TripleO so I'll let someone else chime in on
that.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Wed, Aug 10, 2016 at 6:18 AM, Xiandong Meng <mengxiandong(a)gmail.com>
wrote:
> We had discussed it a bit in previous RDO meeting on irc. I want to
write a
> separate mail
> for more broad and in-depth discussion here.
>
>
> For a master release (for now it is Newton), i noticed the promotion
pipes
> fall into three different categories:
> - Triple-O based CI test
> - Packstack based test
> - OpenStack-Puppet based test
>
> So what is the base minimal CI requirements to start with for AltArch
> support? Since many of the CI test should work even with VMs instead of
> physical nodes, can we start
> with 1-2 physical servers?
>
> Regards,
>
> Alex Meng
> mengxiandong(a)gmail.com
>
> _______________________________________________
> rdo-list mailing list
> rdo-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe(a)redhat.com