[rdo-dev] [ppc64le] Spinning up Triple O container jobs

[Michael Turek]

Hey David,

I'm not entirely sure. My understanding is that OVB and heat are used 
for testing tripleo deployment, but are not  used in the container 
builds. If this is correct, we wouldn't need OVB or heat initially.

So could we leverage the cico cloud? What would we need to do?

Thanks!
Mike Turek <mjturek>


On 5/11/18 2:21 PM, David Moreau Simard wrote:
> What are the requirements for those jobs other than ppc64le ?
>
> Do you need OVB ? Do you need heat ?
> If you don't need either and duffy won't work, we can consider asking
> the CentOS infrastructure team if we can upload custom images to the
> cico cloud.
>
> They have some amount of ppc64le capacity available [1].
>
> [1]: https://wiki.centos.org/QaWiki/CI/Multiarch#head-02310f99181bff98c506d96637895e982c799226
>
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]
>
>
> On Fri, May 11, 2018 at 1:36 PM, Michael Turek
> <mjturek at linux.vnet.ibm.com> wrote:
>> Hey David,
>>
>> Replies inline
>>
>>
>> On 5/11/18 12:57 PM, David Moreau Simard wrote:
>>> Michael,
>>>
>>> The cloud from which Duffy provides virtual machines is not publicly
>>> available, this means we cannot leverage it with Nodepool or Zuul.
>> Fair enough! I guess the alternative is to get Power nodes into the RDO
>> cloud? Any other ideas?
>>>
>>> We have some tooling to request [1][2] and destroy [3][4] Duffy nodes.
>>> Do you really need a custom image or would requesting a "vanilla"
>>> ppc64le node from Duffy be enough ?
>> Not sure about this. The image used for container builds on x86_64
>> (upstream-centos-7) seems to use quite a few elements [0]. I'm not clear on
>> why each of them are required, but I would assume a power node would need an
>> image built with these elements as well.
>>
>>> [1]:
>>> https://github.com/rdo-infra/ci-config/blob/master/jenkins/jobs/scripts/cico-node-get-to-ansible.sh
>>> [2]:
>>> https://github.com/rdo-infra/ci-config/blob/516411b57b378c1bf7374bcf32774e2f5dd1b2fb/jenkins/jobs/weirdo-builders.yml#L1-L6
>>> [3]:
>>> https://github.com/rdo-infra/ci-config/blob/master/jenkins/jobs/scripts/cico-node-done-from-ansible.sh
>>> [4]:
>>> https://github.com/rdo-infra/ci-config/blob/516411b57b378c1bf7374bcf32774e2f5dd1b2fb/jenkins/jobs/weirdo-defaults.yml#L68-L78
>>>
>>> David Moreau Simard
>>> Senior Software Engineer | OpenStack RDO
>>>
>>> dmsimard = [irc, github, twitter]
>>>
>>>
>>> On Fri, May 11, 2018 at 12:49 PM, Michael Turek
>>> <mjturek at linux.vnet.ibm.com> wrote:
>>>> Hey all,
>>>>
>>>> Last week I threw up a patch to add tripleo container build jobs for
>>>> ppc64le
>>>> [0]. I would really appreciate getting some eyes on it. I'm not sure how
>>>> complete it is, but I do know that we'll need:
>>>>
>>>> a) A provider for ppc64le in nodepool [1]
>>>> b) A ppc64le image in nodepool. [2]
>>>>
>>>> There's been some discussion around (a) which led to me being linked to
>>>> https://wiki.centos.org/QaWiki/CI/Multiarch but I don't think Duffy can
>>>> work
>>>> with nodepool. If I'm wrong about this, please let me know.
>>>>
>>>> As for (b), we would need a node running DIB on a ppc64le node/guest
>>>> providing a ppc64le image .
>>>>
>>>> Thanks,
>>>> Mike Turek <mjturek on freenode>
>>>>
>>>> [0] https://review.rdoproject.org/r/#/c/13606/
>>>> [1]
>>>> https://review.rdoproject.org/r/#/c/13606/4/nodepool/nodepool.yaml@134
>>>> [2]
>>>> https://review.rdoproject.org/r/#/c/13606/3/nodepool/nodepool.yaml@145
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev at lists.rdoproject.org
>>>> http://lists.rdoproject.org/mailman/listinfo/dev
>>>>
>>>> To unsubscribe: dev-unsubscribe at lists.rdoproject.org
>> Thanks,
>> Mike Turek <mjturek on freenode>
>>
>> [0]
>> https://github.com/rdo-infra/review.rdoproject.org-config/blob/master/nodepool/nodepool.yaml#L15-L27
>>