Open Stack

On Tue, 17 Apr 2018 06:40:35 -0700, Dan Smith wrote:
>> I propose that we remove the z/VM driver blueprint from the runway at
>> this time and place it back into the queue while work on the driver
>> continues. At a minimum, we need to see z/VM CI running with
>> [validation]run_validation = True in tempest.conf before we add the
>> z/VM driver blueprint back into a runway in the future.
> 
> Agreed. I also want to see the CI reporting cleaned up so that it's
> readable and consistent. Yesterday I pointed out some issues with the
> fact that the actual config files being used are not the ones being
> uploaded. There are also duplicate (but not actually identical) logs
> from all services being uploaded, including things like a full compute
> log from starting with the libvirt driver.

Yes, we definitely need to see all of these issues fixed.

> I'm also pretty troubled by the total lack of support for the metadata
> service. I know it's technically optional on our matrix, but it's a
> pretty important feature for a lot of scenarios, and it's also a
> dependency for other features that we'd like to have wider support for
> (like attached device metadata).
> 
> Going back to the spec, I see very little detail on some of the things
> raised here, and very (very) little review back when it was first
> approved. I'd also like to see more detail be added to the spec about
> all of these things, especially around required special changes like
> this extra AE agent.

Agreed, can someone from the z/VM team please propose an update to the 
driver spec to document these details?

Thanks,
-melanie