Added a update to the spec to the issues that requested https://review.openstack.org/#/c/562154/ , including:
1) How the config drive (Metadata) defined 2) Special AE reason and why it's needed, also ,some documentation and source code links 3) neutron agent for z/VM Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82451493 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC From: melanie witt <melwi...@gmail.com> To: Dan Smith <d...@danplanet.com> Cc: openstack-dev@lists.openstack.org Date: 04/18/2018 01:47 AM Subject: Re: [openstack-dev] [Nova] z/VM introducing a new config driveformat 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 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=CCtWdN4OOlqKzrLg4ctuY1D_fHo8wvps59hVs35J8ys&s=wHuQV89_dwXLe15VAkg8_UOBPfjD72vB0_47W6BgRVk&e=
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev