According to requirements and comments, now we opened the CI runs with run_validation = True And according to [1] below, for example, [2] need the ssh validation passed the test
And there are a couple of comments need some enhancement on the logs of CI such as format and legacy incorrect links of logs etc the newest logs sample can be found [3] (take n-cpu as example and those logs are with _white.html) Also, the blueprint [4] requested by previous discussion post here again for reference please let us know whether the procedure -2 can be removed in order to proceed . thanks for your help [1] http://extbasicopstackcilog01.podc.sl.edst.ibm.com/test_logs/jenkins-check-nova-master-17455/logs/tempest.log 2018-04-27 08:50:44.852 19582 DEBUG tempest [-] validation.run_validation = True http://extbasicopstackcilog01.podc.sl.edst.ibm.com/test_logs/jenkins-check-nova-master-17455/console.html {0} tempest.scenario.test_server_basic_ops.TestServerBasicOps.test_server_basic_ops [86.788179s] ... ok [2] https://github.com/openstack/tempest/blob/master/tempest/scenario/test_server_basic_ops.py [3] http://extbasicopstackcilog01.podc.sl.edst.ibm.com/test_logs/jenkins-check-nova-master-17455/logs/n-cpu.log_white.html [4] https://review.openstack.org/#/c/562154/ Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: [email protected] Phone: +86-10-82451493 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC From: melanie witt <[email protected]> To: [email protected] Date: 04/18/2018 01:41 AM Subject: Re: [openstack-dev] [Nova] z/VM introducing a new config driveformat On Tue, 17 Apr 2018 16:58:22 +0800, Chen Ch Ji wrote: > For the question on AE documentation, it's open source in [1] and the > documentation for how to build and use is [2] > once our code is upstream, there are a set of documentation change which > will cover this image build process by > adding some links to there [3] Thanks, that is good info. > You are right, we need image to have our Active Engine, I think > different arch and platform might have their unique > requirements and our solution our Active Engine is very like to > cloud-init so no harm to add it from user's perspective > I think later we can upload image to some place so anyone is able to > consume it as test image if they like > because different arch's image (e.g x86 and s390x) can't be shared anyway. > > For the config drive format you mentioned, actually, as previous > explanation and discussion witho Michael and Dan, > We found the iso9660 can be used (previously we made a bad assumption) > and we already changed the patch in [4], > so it's exactly same to other virt drivers you mentioned , we don't need > special format and iso9660 works perfect for our driver That's good news, I'm glad that got resolved. > It make sense to me we are temply moved out from runway, I suppose we > can adjust the CI to enable the run_ssh = true > with config drive functionalities very soon and we will apply for review > after that with the test result requested in our CI log. Okay, sounds good. Since you expect to be up and running with [validation]run_validation = True soon, I'm going to move the z/VM driver blueprint back to the front of the queue and put the next blueprint in line into the runway. Then, when the next blueprint end date arrives (currently 2018-04-30), if the z/VM CI is ready with cleaned up, human readable log files and is running with run_ssh = True with the test_server_basic_ops test to verify config drive operation, we will add the z/VM driver blueprint back to a runway for dedicated review. Let us know when the z/VM CI is ready, in case other runway reviews are completed early. If other runway reviews complete early, a runway space might be available earlier than 2018-04-30. Thanks, -melanie > Thanks > > [1] > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mfcloud_python-2Dzvm-2Dsdk_blob_master_tools_share_zvmguestconfigure&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=CRsbKwMgE5rCqLl8MTo6ZnKA4QkxK3NRmDont5BYcqw&s=RpjRNK6wiUJDNTYKBkou6nSDpaUkNOXdmBJ-SyjkPaw&e= > [2] > https://urldefense.proofpoint.com/v2/url?u=http-3A__cloudlib4zvm.readthedocs.io_en_latest_makeimage.html-23configuration-2Dof-2Dactivation-2Dengine-2Dae-2Din-2Dzlinux&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=CRsbKwMgE5rCqLl8MTo6ZnKA4QkxK3NRmDont5BYcqw&s=CVvkU6HtWW7GArGIpFT4fichM0fuTXXrmWD9zyRo9h0&e= > [3] > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_q_status-3Aopen-2Bproject-3Aopenstack_nova-2Bbranch-3Amaster-2Btopic-3Abp_add-2Dzvm-2Ddriver-2Drocky&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=CRsbKwMgE5rCqLl8MTo6ZnKA4QkxK3NRmDont5BYcqw&s=P_DwKtfQWsNNWz9SmTW2xvArTWIzCh2EKPHRqLDkGeg&e= > [4] > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.openstack.org_-23_c_527658_33_nova_virt_zvm_utils.pyline&d=DwIGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=8sI5aZT88Uetyy_XsOddbPjIiLSGM-sFnua3lLy2Xr0&m=CRsbKwMgE5rCqLl8MTo6ZnKA4QkxK3NRmDont5BYcqw&s=l9eTwoZcQ84k6S2EwQCw3gG8n8g5kLkcFplIMzI1G0I&e= 104 __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?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=CRsbKwMgE5rCqLl8MTo6ZnKA4QkxK3NRmDont5BYcqw&s=eXxXnVzbsK42dW14x1C23QaY4E-TKbCPBLyX05K_bag&e=
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
