[openstack-dev] [tripleo] scenario006 conflict

Derek Higgins derekh at redhat.com
Wed Aug 16 13:46:35 UTC 2017


On 19 July 2017 at 17:02, Derek Higgins <derekh at redhat.com> wrote:
> On 17 July 2017 at 15:56, Derek Higgins <derekh at redhat.com> wrote:
>> On 17 July 2017 at 15:37, Emilien Macchi <emilien at redhat.com> wrote:
>>> On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi <emilien at redhat.com> wrote:
>>>> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins <derekh at redhat.com> wrote:
>>>>> On 12 July 2017 at 22:33, Emilien Macchi <emilien at redhat.com> wrote:
>>>>>> On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi <emilien at redhat.com> wrote:
>>>>>> [...]
>>>>>>> Derek, it seems like you want to deploy Ironic on scenario006
>>>>>>> (https://review.openstack.org/#/c/474802). I was wondering how it
>>>>>>> would work with multinode jobs.
>>>>>>
>>>>>> Derek, I also would like to point out that
>>>>>> https://review.openstack.org/#/c/474802 is missing the environment
>>>>>> file for non-containerized deployments & and also the pingtest file.
>>>>>> Just for the record, if we can have it before the job moves in gate.
>>>>>
>>>>> I knew I had left out the ping test file, this is the next step but I
>>>>> can create a noop one for now if you'd like?
>>>>
>>>> Please create a basic pingtest with common things we have in other scenarios.
>>>>
>>>>> Is the non-containerized deployments a requirement?
>>>>
>>>> Until we stop supporting non-containerized deployments, I would say yes.
>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> --
>>>>>> Emilien Macchi
>>>>
>>>> So if you create a libvirt domain, would it be possible to do it on
>>>> scenario004 for example and keep coverage for other services that are
>>>> already on scenario004? It would avoid to consume a scenario just for
>>>> Ironic. If not possible, then talk with Flavio and one of you will
>>>> have to prepare scenario007 or 0008, depending where Numans is in his
>>>> progress to have OVN coverage as well.
>>>
>>> I haven't seen much resolution / answers about it. We still have the
>>> conflict right now and open questions.
>>>
>>> Derek, Flavio - let's solve this one this week if we can.
>> Yes, I'll be looking into using scenario004 this week. I was traveling
>> last week so wasn't looking at it.
>
> I'm not sure if this is what you had intended but I believe to do
> this(i.e. test the nova ironic driver) we we'll
> need to swap out the nova libvirt driver for the ironic one. I think
> this is ok as the libvirt driver has coverage
> in other scenarios.
>
> Because there are no virtual BMC's setup yet on the controller I also
> have to remove the instance creation,
> but if merged I'll next work on adding these now. So I'm think
> something like this
> https://review.openstack.org/#/c/485261/

Quick update here, after talking to Emilien about this, I'll add to
this patch to set up VirtualBMC instances and not remove instance
creation. So it continues to test a ceph backed glance.

>
>>
>>>
>>> Thanks,
>>> --
>>> Emilien Macchi



More information about the OpenStack-dev mailing list