| *** andrey-mp has quit IRC | 06:45 | |
| *** andrey-mp has joined #openstack-ec2api | 07:02 | |
| *** andrey-mp has quit IRC | 07:23 | |
| *** andrey-mp has joined #openstack-ec2api | 08:03 | |
| ansiwen | andrey-mp: stable/ocata | 11:42 |
|---|---|---|
| ansiwen | andrey-mp: so, how do the tempest tests that are image related succeed now? don't they need glance? | 11:43 |
| ansiwen | we are trying to run tempest agains our puppet deployment, and wonder how to run the tests that need an image | 11:44 |
| andrey-mp | ansiwen: image related tests in tempest are fine - they know about differencies in glance v1/v2 | 12:27 |
| andrey-mp | you are talking about ec2 tests that need an image? | 12:27 |
| ansiwen | so, what are the requirements to run all the tempest tests like in ec2-api CI, but against our puppet deployed service? | 12:28 |
| ansiwen | yes, the tests that require an image | 12:28 |
| andrey-mp | ec2 tests requires several images: image_id must be of 'instance-store' type (this is the simple cirros image in openstack) and ebs_image_id must be an 'ebs' image (in ec2-api repo we have devstack/create_config script with steps to create ebs-like image) | 12:41 |
| ansiwen | andrey-mp: but no further requirements regarding how glance is set up? | 13:00 |
| ansiwen | andrey-mp: or am I mistaken, and the tests with images are not dealing with glance? | 13:00 |
| ansiwen | I'm just confused, because it looks like ec2-api doesn't work with glance at the moment, because of the bug you just sent the link for, but the tempest tests in CI that work with images still work. | 13:01 |
| ansiwen | so I guess there is a misunderstanding on my side | 13:02 |
| andrey-mp | ec2-api in master doesn't work with deployments where glance has only version 2. this is related to communication between ec2-api and glance. | 13:05 |
| andrey-mp | images tests against ec2-api will not work if ec2-api is not work due to absence of glance v1 in deployments | 13:06 |
| andrey-mp | but general images tests in tempest should work in any case. | 13:07 |
| andrey-mp | (current code of ec2-api uses glance v1 to work with images. now we are switching it to glance v2) | 13:08 |
| ansiwen | what's the difference between "images tests against ec2-api" and "general images tests"? | 13:09 |
| ansiwen | of course I'm only talking about the ec2-api tests in tempest, not any other tempest tests (if you are referring to them) | 13:10 |
| ansiwen | for example "ec2api.tests.functional.api.test_images.ImageTest.test_describe_image_with_filters" is ok in http://logs.openstack.org/93/443793/1/check/gate-functional-neutron-dsvm-ec2api-ubuntu-xenial/03daf26/console.html, so why doesn't this fail if glance is not deployed in v1? | 13:12 |
| andrey-mp | i mean that tempest project doesn't have ec2-api tests. it has only images tests for glance project itself. | 13:13 |
| andrey-mp | all tests in ec2-api for images will fail because of hard-coded version of glance - https://github.com/openstack/ec2-api/blob/master/ec2api/clients.py#L120 | 13:16 |
| andrey-mp | and it is not so simple to switch this version to '2' | 13:16 |
| andrey-mp | due to many changes in glanceclient | 13:17 |
| ansiwen | why doesn't ec2api.tests.functional.api.test_images.ImageTest.test_describe_image_with_filters feil then for example? or is that from a time when glance v1 was still deployed? | 13:18 |
| andrey-mp | yeah, it was a month ago - glance v1 was removed about 3 weeks ago | 13:20 |
| ansiwen | hmm... I wonder how our glance is deployed... I let everything in default | 13:25 |
| ansiwen | andrey-mp: thanks a lot for that info! | 13:25 |
| ansiwen | so, if I correctly enable v1 glance, everything _should_ work? | 13:25 |
| andrey-mp | yes ) | 13:30 |
| ansiwen | andrey-mp: the S3 service is part of ec2-api? I remember I removed S3 from the puppet ec2-api module, because S3 support is experimental only. so but it seems to be required to upload the image to? so without an S3 service you can't do these tests either? | 14:35 |
| andrey-mp | s3 is needed only register_image function from ec2. this function is needed if you want to upload your own image to the cloud via ec2-api. but ec2-api can work well with existing images in the cloud. | 14:39 |
| ansiwen | andrey-mp: yees, but in the context of the ec2-api tempest tests I would need to upload my own images, which only works with S3, right? (I'm just looking at the create_config of your CI) | 14:45 |
| andrey-mp | ansiwen: in the create-config script there is a code that creates images in the cloud via openstack cli tool. it downloads cirros image and then uploads it to the cloud with 'openstack image create ...' | 14:50 |
| andrey-mp | also script has some steps to create image in S3 to check register_image functionality later. but it's an optional test. | 14:51 |
| andrey-mp | anyway - you can use S3 implementation from swift team. if your deployment has swift installed then you can switch on swifts3 service as well. | 14:52 |
| ansiwen | I just want to have the simplest way to also run the ec2-api tempest tests that use images. if I don't need S3 for that, I'm happy | 15:05 |
| ansiwen | andrey-mp: here it seems to be assumed that there is already a cirros image in glance? https://github.com/openstack/ec2-api/blob/master/devstack/create_config#L70 | 15:05 |
| andrey-mp | yeah | 15:26 |
| andrey-mp | you are right. existing cirros image is used as 'instance-store' image | 15:26 |
| andrey-mp | downloaded cirros image is used to create ebs-like image | 15:27 |
| *** andrey-mp has quit IRC | 15:31 | |
| *** andrey-mp has joined #openstack-ec2api | 17:29 | |
| ansiwen | andrey-mp: any estimate, when the V2 fix will be ready? are you close to merge? | 18:20 |
| ansiwen | we can't deploy glance with v1 anymore :-/ | 18:23 |
| ansiwen | so, is ec2-api still useful without the glance functionality? I'm not sure about the usual usecases, is that critical, or are most people not using it? | 18:25 |
| andrey-mp | ansiwen: I hope we will do it in two-three days | 19:10 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!