From build.starlingx at gmail.com Wed Jan 1 04:35:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 31 Dec 2019 23:35:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 570 - Failure! Message-ID: <2015026148.456.1577853305302.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 570 Status: Failure Timestamp: 20200101T025644Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200101T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200101T023000Z DOCKER_BUILD_ID: jenkins-master-20200101T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200101T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200101T023000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Jan 1 04:35:07 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 31 Dec 2019 23:35:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 368 - Failure! Message-ID: <562408427.459.1577853308684.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 368 Status: Failure Timestamp: 20200101T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200101T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Don.Penney at windriver.com Wed Jan 1 21:42:09 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 1 Jan 2020 21:42:09 +0000 Subject: [Starlingx-discuss] Build failure in python-keystoneclient Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15D7A8F@ALA-MBD.corp.ad.wrs.com> Hi folks, We're hitting a build failure in python-keystoneclient in test code: https://opendev.org/openstack/python-keystoneclient/src/branch/stable/stein/keystoneclient/tests/unit/v3/test_auth.py#L31 The test token expiry is set to "2020-01-01T00:00:10.000123Z", and the test then fails. As a workaround, we could just comment out the %check in the spec, which runs the unit tests: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-keystoneclient/centos/python-keystoneclient.spec#L217 That would probably allow the builds to succeed. Here are the errors seen in python-keystoneclient: {15} keystoneclient.tests.unit.v2_0.test_auth.AuthenticateAgainstKeystoneTests.test_authenticate_success_token_unscoped [0.009347s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/v2_0/test_auth.py", line 226, in test_authenticate_success_token_unscoped self.assertRequestBodyIs(json=self.TEST_REQUEST_BODY) File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/utils.py", line 72, in assertRequestBodyIs self.assertEqual(json, val) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = {'auth': {'token': {'id': '7497a5a479a041178c8988e973ea24f5'}}} actual = {u'auth': {u'tenantId': u'83f086cee02d4234a909590e68ca00da', u'token': {u'id': u'7497a5a479a041178c8988e973ea24f5'}}} Captured pythonlogging: ~~~~~~~~~~~~~~~~~~~~~~~ Making authentication request to http://127.0.0.1:5000/v2.0/tokens Failed to find endpoint for management url The service catalog is empty. Making authentication request to http://127.0.0.1:5000/v2.0/tokens Failed to find endpoint for management url The service catalog is empty. {3} keystoneclient.tests.unit.v3.test_auth.AuthenticateAgainstKeystoneTests.test_authenticate_success_token_unscoped [0.011026s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/v3/test_auth.py", line 329, in test_authenticate_success_token_unscoped self.assertRequestBodyIs(json=self.TEST_REQUEST_BODY) File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/utils.py", line 72, in assertRequestBodyIs self.assertEqual(json, val) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = {'auth': {'identity': {'methods': ['token'], 'token': {'id': '960c83d28fa14046a3a1c8967ae19da2'}}}} actual = {u'auth': {u'identity': {u'methods': [u'token'], u'token': {u'id': u'960c83d28fa14046a3a1c8967ae19da2'}}, u'scope': {u'project': {u'id': u'f110ab7629924d18b0466aacbd6a148f'}}}} Captured pythonlogging: ~~~~~~~~~~~~~~~~~~~~~~~ Making authentication request to http://127.0.0.1:5000/v3/auth/tokens {"token": {"project": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "f110ab7629924d18b0466aacbd6a148f", "name": "4a827c43830e4247b8bc968d3082ff6a"}, "issued_at": "2013-05-29T16:55:21.468960Z", "methods": ["token", "password"], "expires_at": "2020-01-01T00:00:10.000123Z", "user": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "5c57c4d19e4942918293e8617abe2912", "name": "5c57c4d19e4942918293e8617abe2912"}}} Failed to find endpoint for management url The service catalog is empty. Making authentication request to http://127.0.0.1:5000/v3/auth/tokens {"token": {"project": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "f110ab7629924d18b0466aacbd6a148f", "name": "4a827c43830e4247b8bc968d3082ff6a"}, "issued_at": "2013-05-29T16:55:21.468960Z", "methods": ["token", "password"], "expires_at": "2020-01-01T00:00:10.000123Z", "user": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "5c57c4d19e4942918293e8617abe2912", "name": "5c57c4d19e4942918293e8617abe2912"}}} Failed to find endpoint for management url The service catalog is empty. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Jan 1 23:42:41 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 1 Jan 2020 23:42:41 +0000 Subject: [Starlingx-discuss] Build failure in python-keystoneclient In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15D7A8F@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15D7A8F@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15D7B09@ALA-MBD.corp.ad.wrs.com> I've created a review in starlingx/upstream to skip running the unit tests during the build: https://review.opendev.org/700852 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, January 01, 2020 4:42 PM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] Build failure in python-keystoneclient Hi folks, We're hitting a build failure in python-keystoneclient in test code: https://opendev.org/openstack/python-keystoneclient/src/branch/stable/stein/keystoneclient/tests/unit/v3/test_auth.py#L31 The test token expiry is set to "2020-01-01T00:00:10.000123Z", and the test then fails. As a workaround, we could just comment out the %check in the spec, which runs the unit tests: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-keystoneclient/centos/python-keystoneclient.spec#L217 That would probably allow the builds to succeed. Here are the errors seen in python-keystoneclient: {15} keystoneclient.tests.unit.v2_0.test_auth.AuthenticateAgainstKeystoneTests.test_authenticate_success_token_unscoped [0.009347s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/v2_0/test_auth.py", line 226, in test_authenticate_success_token_unscoped self.assertRequestBodyIs(json=self.TEST_REQUEST_BODY) File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/utils.py", line 72, in assertRequestBodyIs self.assertEqual(json, val) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = {'auth': {'token': {'id': '7497a5a479a041178c8988e973ea24f5'}}} actual = {u'auth': {u'tenantId': u'83f086cee02d4234a909590e68ca00da', u'token': {u'id': u'7497a5a479a041178c8988e973ea24f5'}}} Captured pythonlogging: ~~~~~~~~~~~~~~~~~~~~~~~ Making authentication request to http://127.0.0.1:5000/v2.0/tokens Failed to find endpoint for management url The service catalog is empty. Making authentication request to http://127.0.0.1:5000/v2.0/tokens Failed to find endpoint for management url The service catalog is empty. {3} keystoneclient.tests.unit.v3.test_auth.AuthenticateAgainstKeystoneTests.test_authenticate_success_token_unscoped [0.011026s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/v3/test_auth.py", line 329, in test_authenticate_success_token_unscoped self.assertRequestBodyIs(json=self.TEST_REQUEST_BODY) File "/builddir/build/BUILD/python-keystoneclient-3.19.0/keystoneclient/tests/unit/utils.py", line 72, in assertRequestBodyIs self.assertEqual(json, val) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual self.assertThat(observed, matcher, message) File "/usr/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: !=: reference = {'auth': {'identity': {'methods': ['token'], 'token': {'id': '960c83d28fa14046a3a1c8967ae19da2'}}}} actual = {u'auth': {u'identity': {u'methods': [u'token'], u'token': {u'id': u'960c83d28fa14046a3a1c8967ae19da2'}}, u'scope': {u'project': {u'id': u'f110ab7629924d18b0466aacbd6a148f'}}}} Captured pythonlogging: ~~~~~~~~~~~~~~~~~~~~~~~ Making authentication request to http://127.0.0.1:5000/v3/auth/tokens {"token": {"project": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "f110ab7629924d18b0466aacbd6a148f", "name": "4a827c43830e4247b8bc968d3082ff6a"}, "issued_at": "2013-05-29T16:55:21.468960Z", "methods": ["token", "password"], "expires_at": "2020-01-01T00:00:10.000123Z", "user": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "5c57c4d19e4942918293e8617abe2912", "name": "5c57c4d19e4942918293e8617abe2912"}}} Failed to find endpoint for management url The service catalog is empty. Making authentication request to http://127.0.0.1:5000/v3/auth/tokens {"token": {"project": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "f110ab7629924d18b0466aacbd6a148f", "name": "4a827c43830e4247b8bc968d3082ff6a"}, "issued_at": "2013-05-29T16:55:21.468960Z", "methods": ["token", "password"], "expires_at": "2020-01-01T00:00:10.000123Z", "user": {"domain": {"id": "02c36756715a499cbed4a4807fbd5dca", "name": "93439078538f4d06aea85038a0124fbd"}, "id": "5c57c4d19e4942918293e8617abe2912", "name": "5c57c4d19e4942918293e8617abe2912"}}} Failed to find endpoint for management url The service catalog is empty. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Jan 2 00:07:17 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 2 Jan 2020 00:07:17 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608F9C96@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F54CC@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F6268@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F668B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F9C96@SHSMSX105.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7660908B1F@SHSMSX105.ccr.corp.intel.com> Hi Frank, Happy New Year! How is the testing going for kata? Is there any issue I need check? Thanks. Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 19, 2019 8:56 AM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Here is the test list I did. 1. Pass daily sanity test by Ada's team for AIO-SX/AIO-DX/Multi/Multi+Storage. 2. Verify container's regression test cases in link: https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit#gid=1448647783 3. Verify no private registry/private insecure registry/private secure registry/multi private registry case. 4. Verify no docker proxy/with docker proxy case. 5. Verify IPv6 deployment. 6. Verify backup&restore for platform. Best Regards Shuicheng From: Miller, Frank > Sent: Wednesday, December 18, 2019 10:16 PM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: We took out your commits and did some basic testing so thanks for providing the list. One final question: where can we review the list of the tests you have done? Or can you summarize the test cases please. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, December 06, 2019 3:34 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, 1 more patch [0] is uploaded today. So there are 8 patches in total. With this patch, token server supports POST method for token fetch, so the WA in containerd is removed. [0]: https://review.opendev.org/697601 Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 5, 2019 4:11 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Glad to hear that. I have rebased all my patches to latest. And your link is correct. Feel free to contact me if you have any question with it. Thanks. Best Regards Shuicheng From: Miller, Frank > Sent: Thursday, December 5, 2019 6:07 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the updates. We would like to take out your changes for KATA containers for a test. Can you rebase your commits and let me know if these are all of the commits: https://review.opendev.org/#/q/topic:kata+(status:open) Once you have rebased we'll create a designer build and run a few tests and let you know if we find anything that needs to be addressed. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Sunday, December 01, 2019 9:15 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I try to run busybox with kata containers by k8s, and it could run successfully in IPv6 environment. Best Regards Shuicheng From: Miller, Frank > Sent: Saturday, November 30, 2019 4:03 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the update. It looks like stx-openstack has not yet been tested with IPv6. But we have been testing IPv6 with kubernetes platform only and simple k8s apps. Can you confirm kata containers is working with IPv6 when stx-openstack is not applied/not used? Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, November 29, 2019 12:48 AM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jan 2 04:34:40 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 1 Jan 2020 23:34:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 571 - Still Failing! In-Reply-To: <1541443498.454.1577853302148.JavaMail.javamailuser@localhost> References: <1541443498.454.1577853302148.JavaMail.javamailuser@localhost> Message-ID: <344151759.463.1577939681209.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 571 Status: Still Failing Timestamp: 20200102T025702Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200102T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200102T023000Z DOCKER_BUILD_ID: jenkins-master-20200102T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200102T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200102T023000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Thu Jan 2 04:34:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 1 Jan 2020 23:34:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 369 - Still Failing! In-Reply-To: <602950500.457.1577853306302.JavaMail.javamailuser@localhost> References: <602950500.457.1577853306302.JavaMail.javamailuser@localhost> Message-ID: <1729619430.466.1577939684206.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 369 Status: Still Failing Timestamp: 20200102T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200102T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Brent.Rowsell at windriver.com Thu Jan 2 13:42:03 2020 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Thu, 2 Jan 2020 13:42:03 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C7660908B1F@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F54CC@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F6268@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F668B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F9C96@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C7660908B1F@SHSMSX105.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC283E903@ALA-MBD.corp.ad.wrs.com> Shuicheng, What testing has been done with kata-runtime ? Thanks, Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, January 1, 2020 7:07 PM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Hi Frank, Happy New Year! How is the testing going for kata? Is there any issue I need check? Thanks. Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 19, 2019 8:56 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Here is the test list I did. 1. Pass daily sanity test by Ada's team for AIO-SX/AIO-DX/Multi/Multi+Storage. 2. Verify container's regression test cases in link: https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit#gid=1448647783 3. Verify no private registry/private insecure registry/private secure registry/multi private registry case. 4. Verify no docker proxy/with docker proxy case. 5. Verify IPv6 deployment. 6. Verify backup&restore for platform. Best Regards Shuicheng From: Miller, Frank > Sent: Wednesday, December 18, 2019 10:16 PM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: We took out your commits and did some basic testing so thanks for providing the list. One final question: where can we review the list of the tests you have done? Or can you summarize the test cases please. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, December 06, 2019 3:34 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, 1 more patch [0] is uploaded today. So there are 8 patches in total. With this patch, token server supports POST method for token fetch, so the WA in containerd is removed. [0]: https://review.opendev.org/697601 Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 5, 2019 4:11 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Glad to hear that. I have rebased all my patches to latest. And your link is correct. Feel free to contact me if you have any question with it. Thanks. Best Regards Shuicheng From: Miller, Frank > Sent: Thursday, December 5, 2019 6:07 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the updates. We would like to take out your changes for KATA containers for a test. Can you rebase your commits and let me know if these are all of the commits: https://review.opendev.org/#/q/topic:kata+(status:open) Once you have rebased we'll create a designer build and run a few tests and let you know if we find anything that needs to be addressed. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Sunday, December 01, 2019 9:15 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I try to run busybox with kata containers by k8s, and it could run successfully in IPv6 environment. Best Regards Shuicheng From: Miller, Frank > Sent: Saturday, November 30, 2019 4:03 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the update. It looks like stx-openstack has not yet been tested with IPv6. But we have been testing IPv6 with kubernetes platform only and simple k8s apps. Can you confirm kata containers is working with IPv6 when stx-openstack is not applied/not used? Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, November 29, 2019 12:48 AM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jan 2 21:24:43 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 16:24:43 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 1 - Failure! Message-ID: <940491541.470.1578000284536.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 1 Status: Failure Timestamp: 20200102T212436Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T212431Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T212431Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200102T212431Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Thu Jan 2 21:28:55 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 16:28:55 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 2 - Still Failing! In-Reply-To: <1522468034.468.1578000281459.JavaMail.javamailuser@localhost> References: <1522468034.468.1578000281459.JavaMail.javamailuser@localhost> Message-ID: <1900051259.475.1578000536203.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 2 Status: Still Failing Timestamp: 20200102T212852Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T212846Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T212846Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200102T212846Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From shuicheng.lin at intel.com Fri Jan 3 00:17:01 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 3 Jan 2020 00:17:01 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC283E903@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F54CC@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F6268@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F668B@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C76608F9C96@SHSMSX105.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C7660908B1F@SHSMSX105.ccr.corp.intel.com> <2588653EBDFFA34B982FAF00F1B4844EC283E903@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C7660909DD8@SHSMSX105.ccr.corp.intel.com> Hi Brent, For kata-runtime, I tested kata container could be launched by both annotation and Runtime Class methods. Best Regards Shuicheng From: Rowsell, Brent Sent: Thursday, January 2, 2020 9:42 PM To: Lin, Shuicheng ; Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng, What testing has been done with kata-runtime ? Thanks, Brent From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, January 1, 2020 7:07 PM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: Re: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Hi Frank, Happy New Year! How is the testing going for kata? Is there any issue I need check? Thanks. Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 19, 2019 8:56 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Here is the test list I did. 1. Pass daily sanity test by Ada's team for AIO-SX/AIO-DX/Multi/Multi+Storage. 2. Verify container's regression test cases in link: https://docs.google.com/spreadsheets/d/1dwcBwY4Yq1Lo9Der4RylzQ6KYp0BsMHohhEmhwpauDo/edit#gid=1448647783 3. Verify no private registry/private insecure registry/private secure registry/multi private registry case. 4. Verify no docker proxy/with docker proxy case. 5. Verify IPv6 deployment. 6. Verify backup&restore for platform. Best Regards Shuicheng From: Miller, Frank > Sent: Wednesday, December 18, 2019 10:16 PM To: Lin, Shuicheng >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: We took out your commits and did some basic testing so thanks for providing the list. One final question: where can we review the list of the tests you have done? Or can you summarize the test cases please. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, December 06, 2019 3:34 AM To: Miller, Frank >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, 1 more patch [0] is uploaded today. So there are 8 patches in total. With this patch, token server supports POST method for token fetch, so the WA in containerd is removed. [0]: https://review.opendev.org/697601 Best Regards Shuicheng From: Lin, Shuicheng Sent: Thursday, December 5, 2019 4:11 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, Glad to hear that. I have rebased all my patches to latest. And your link is correct. Feel free to contact me if you have any question with it. Thanks. Best Regards Shuicheng From: Miller, Frank > Sent: Thursday, December 5, 2019 6:07 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the updates. We would like to take out your changes for KATA containers for a test. Can you rebase your commits and let me know if these are all of the commits: https://review.opendev.org/#/q/topic:kata+(status:open) Once you have rebased we'll create a designer build and run a few tests and let you know if we find anything that needs to be addressed. Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Sunday, December 01, 2019 9:15 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I try to run busybox with kata containers by k8s, and it could run successfully in IPv6 environment. Best Regards Shuicheng From: Miller, Frank > Sent: Saturday, November 30, 2019 4:03 AM To: Lin, Shuicheng >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Shuicheng: Thanks for the update. It looks like stx-openstack has not yet been tested with IPv6. But we have been testing IPv6 with kubernetes platform only and simple k8s apps. Can you confirm kata containers is working with IPv6 when stx-openstack is not applied/not used? Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, November 29, 2019 12:48 AM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 3 01:23:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 20:23:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1 - Failure! Message-ID: <806195884.481.1578014628676.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 1 Status: Failure Timestamp: 20200103T012344Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200102T213645Z DOCKER_BUILD_ID: jenkins-master-compiler-20200102T213645Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Fri Jan 3 01:24:21 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 20:24:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 255 - Failure! Message-ID: <384714625.485.1578014662638.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 255 Status: Failure Timestamp: 20200103T012349Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200102T213645Z DOCKER_BUILD_ID: jenkins-master-compiler-20200102T213645Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200102T213645Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From build.starlingx at gmail.com Fri Jan 3 02:55:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 21:55:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 2 - Still Failing! In-Reply-To: <945336217.479.1578014625590.JavaMail.javamailuser@localhost> References: <945336217.479.1578014625590.JavaMail.javamailuser@localhost> Message-ID: <1487470471.488.1578020148788.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 2 Status: Still Failing Timestamp: 20200103T025544Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200103T023000Z DOCKER_BUILD_ID: jenkins-master-compiler-20200103T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From build.starlingx at gmail.com Fri Jan 3 02:56:11 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 2 Jan 2020 21:56:11 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 256 - Still Failing! In-Reply-To: <1513539014.483.1578014660283.JavaMail.javamailuser@localhost> References: <1513539014.483.1578014660283.JavaMail.javamailuser@localhost> Message-ID: <2057984890.492.1578020172947.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 256 Status: Still Failing Timestamp: 20200103T025549Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200103T023000Z DOCKER_BUILD_ID: jenkins-master-compiler-20200103T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200103T023000Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From cristopher.j.lemus.contreras at intel.com Fri Jan 3 09:09:51 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 03 Jan 2020 03:09:51 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191231T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From build.starlingx at gmail.com Fri Jan 3 17:14:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 3 Jan 2020 12:14:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 9 - Failure! Message-ID: <1910042416.504.1578071680638.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 9 Status: Failure Timestamp: 20200103T171433Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200103T171428Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: distro.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200103T171428Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200103T171428Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro From maria.g.perez.ibarra at intel.com Fri Jan 3 20:49:00 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 3 Jan 2020 20:49:00 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200103 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-03 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 3 21:34:08 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 3 Jan 2020 16:34:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 3 - Still Failing! In-Reply-To: <617335214.486.1578020145764.JavaMail.javamailuser@localhost> References: <617335214.486.1578020145764.JavaMail.javamailuser@localhost> Message-ID: <1938205178.516.1578087249319.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 3 Status: Still Failing Timestamp: 20200103T205818Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T203220Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200103T203220Z DOCKER_BUILD_ID: jenkins-master-compiler-20200103T203220Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200103T203220Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200103T203220Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From cristopher.j.lemus.contreras at intel.com Sat Jan 4 09:05:16 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 04 Jan 2020 03:05:16 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$6cnsgg@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200103T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Sun Jan 5 09:08:30 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 05 Jan 2020 03:08:30 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <03957c$6jn206@orsmga006.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200104T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Mon Jan 6 09:09:34 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 06 Jan 2020 03:09:34 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <86d0ec$6mva5q@fmsmga001.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200106T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From build.starlingx at gmail.com Mon Jan 6 17:10:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Jan 2020 12:10:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 4 - Still Failing! In-Reply-To: <129247911.514.1578087246276.JavaMail.javamailuser@localhost> References: <129247911.514.1578087246276.JavaMail.javamailuser@localhost> Message-ID: <1020292071.522.1578330631739.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 4 Status: Still Failing Timestamp: 20200106T165905Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200106T162956Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200106T162956Z DOCKER_BUILD_ID: jenkins-master-compiler-20200106T162956Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200106T162956Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200106T162956Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From maria.g.perez.ibarra at intel.com Mon Jan 6 17:44:24 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 6 Jan 2020 17:44:24 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200106 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-06 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] List of docker images http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007401.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Jan 6 18:00:28 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 6 Jan 2020 18:00:28 +0000 Subject: [Starlingx-discuss] Reference material for StarlingX flock components Message-ID: StarlingX Community: A number of developers have created training material for some of the flock components as well as networking & containers used in StarlingX and we would like to share this with the community. For any developers who are interested in this material please see the following: https://drive.google.com/drive/folders/1AvUCq3ojuhNZV6XE8YdRhp9PVxixRIeE Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Jan 6 18:28:21 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 6 Jan 2020 18:28:21 +0000 Subject: [Starlingx-discuss] Question about distributed openstack In-Reply-To: <1577773690103.64126@chinaunicom.cn> References: <1577772988426.88956@chinaunicom.cn> <1577773690103.64126@chinaunicom.cn> Message-ID: <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> Hello Wei. Distributed Cloud support is available in StarlingX 3.0 which was just recently released. You can find the ISO image here [1]. You can find documentation on how to setup a StarlingX distributed cloud at this link [2]. Once you have your cloud and its subclouds set up, you should be able to share images between them. brucej [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, December 30, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question about distributed openstack ​ Dear Sir/Madam, I'm an engineer that use the starlingx in our product. I setup a central cloud and an edge. Now I hit an issue about how to share the image from center to the edge. What I thought is, write one application on the edge, get the image list from center, then pull by demand. It's said that in the near future like starlingx 4.0, the distributed openstack will be leveraged and there's something about image process. So, could you share any idea/material about it? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Jan 6 18:33:40 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 6 Jan 2020 18:33:40 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Bi-weekly Meeting Message-ID: The next meeting for containerization will occur next week on Tuesday Jan 14. Agenda will be updated before the meeting but will include: Agenda for January 14 meeting: 1. Review status on 2006145: Kata container support [Shuicheng Lin] (should be merged by time of this meeting) 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC (every 2 weeks) Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2627 bytes Desc: not available URL: From bruce.e.jones at intel.com Mon Jan 6 20:21:06 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 6 Jan 2020 20:21:06 +0000 Subject: [Starlingx-discuss] Reference material for StarlingX flock components In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BED397294@fmsmsx123.amr.corp.intel.com> Frank, thank you and everyone who built all of this. This is a wonderful gift for the community! brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, January 6, 2020 10:00 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Reference material for StarlingX flock components StarlingX Community: A number of developers have created training material for some of the flock components as well as networking & containers used in StarlingX and we would like to share this with the community. For any developers who are interested in this material please see the following: https://drive.google.com/drive/folders/1AvUCq3ojuhNZV6XE8YdRhp9PVxixRIeE Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Jan 6 21:28:24 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Jan 2020 16:28:24 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 18 - Failure! Message-ID: <1019440276.533.1578346105461.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 18 Status: Failure Timestamp: 20200106T212818Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200106T212812Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: flock.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200106T212812Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200106T212812Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From build.starlingx at gmail.com Mon Jan 6 22:25:45 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Jan 2020 17:25:45 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 7 - Failure! Message-ID: <424815490.539.1578349546310.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 7 Status: Failure Timestamp: 20200106T221415Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200106T193141Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200106T193141Z DOCKER_BUILD_ID: jenkins-master-distro-20200106T193141Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200106T193141Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200106T193141Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From chenw66 at chinaunicom.cn Tue Jan 7 02:26:19 2020 From: chenw66 at chinaunicom.cn (=?gb2312?B?V2VpIENoZW4owarNqLyvzcXBqs2o1MbK/b7d09DP3rmry76xvrK/KQ==?=) Date: Tue, 7 Jan 2020 02:26:19 +0000 Subject: [Starlingx-discuss] =?gb2312?b?tPC4tDogUXVlc3Rpb24gYWJvdXQgZGlz?= =?gb2312?b?dHJpYnV0ZWQgb3BlbnN0YWNr?= In-Reply-To: <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> References: <1577772988426.88956@chinaunicom.cn> <1577773690103.64126@chinaunicom.cn>, <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> Message-ID: <1578363962363.7501@chinaunicom.cn> Hi Bruce, Many thanks for your reply. I'm using the starlingx 3.0. Maybe I didn't describe my question clearly. I want to setup the openstack on both central and edge. The main VM image storage will be on the central. When we deploy VM instance on edge, there's no image locally. So either get the image from central by demands, or save the image on both sides. It's heard from other that openstack couldn't be deployed on central cloud for version 3.0. And some more stratage for image sharing will be in version 4.0. Because version 4.0 would be a little late for us, it will be good to know some details and maybe we could do some simplified process. Thanks & Regards, Wei ________________________________ 发件人: Jones, Bruce E 发送时间: 2020年1月7日 2:28 收件人: Wei Chen(联通集团联通云数据有限公司本部); starlingx-discuss at lists.starlingx.io 主题: RE: Question about distributed openstack Hello Wei. Distributed Cloud support is available in StarlingX 3.0 which was just recently released. You can find the ISO image here [1]. You can find documentation on how to setup a StarlingX distributed cloud at this link [2]. Once you have your cloud and its subclouds set up, you should be able to share images between them. brucej [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, December 30, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question about distributed openstack ? Dear Sir/Madam, I'm an engineer that use the starlingx in our product. I setup a central cloud and an edge. Now I hit an issue about how to share the image from center to the edge. What I thought is, write one application on the edge, get the image list from center, then pull by demand. It's said that in the near future like starlingx 4.0, the distributed openstack will be leveraged and there's something about image process. So, could you share any idea/material about it? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 7 08:32:41 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 7 Jan 2020 08:32:41 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Message-ID: Hi All: Happy New Year. Agenda for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) - Standardize Flock Package Versioning (JITStack-Daniels) - Kata Container (Shuicheng) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: Tarball: container builder and iso status : openstack rpm from centos8 ??? rt kernel rpm package from centos8 ??? * CVE issue tracking (Shuicheng) * Open Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From cristopher.j.lemus.contreras at intel.com Tue Jan 7 09:11:47 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 07 Jan 2020 03:11:47 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$6dg3g7@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200107T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From km.giuseppesannino at gmail.com Tue Jan 7 09:42:29 2020 From: km.giuseppesannino at gmail.com (Giuseppe Sannino) Date: Tue, 7 Jan 2020 10:42:29 +0100 Subject: [Starlingx-discuss] Baremetal installation problem Message-ID: Hi all, I have an HP ProLiant DL380 Gen10 and the idea is to install STX 3.0 Baremetal All-In-One Controller Configuration". I downloaded the ISO from here: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso I linked as Virtual Drive through the HP iLo and then booted from it. I'm able to see the "Select kernel options and boot kernel". Here I picked the "UEFI All-in-Hone Controller Configuratation" option. Then "Serial console". After that, basically I can just see a black screen with nothing going on. I can't see the installation going through. I tried with the 3.0.0 iso also on Virtualbox and on an Openstack data center, same result. Furthermore, the same happens using the 2.0 image. What am i doing wrong ? Thanks for your help /Giuseppe -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 7 13:16:35 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 7 Jan 2020 13:16:35 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 In-Reply-To: References: Message-ID: Hi Austin - happy new year :) I suggest the kata containers topic be moved to the containers meeting (next meeting planned for Jan 14). I'm on the fence about which meeting should cover ceph containerization - it overlaps with both the non-openstack mandate due to this being ceph but also with the containerization mandate. There are more containers SMEs at the containerization meeting so I would suggest Tingie attend the containerization meeting as well as the non-Openstack meeting. Does that work? Frank -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, January 07, 2020 3:33 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi All: Happy New Year. Agenda for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) - Standardize Flock Package Versioning (JITStack-Daniels) - Kata Container (Shuicheng) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: Tarball: container builder and iso status : openstack rpm from centos8 ??? rt kernel rpm package from centos8 ??? * CVE issue tracking (Shuicheng) * Open Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Tue Jan 7 15:06:21 2020 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 7 Jan 2020 15:06:21 +0000 Subject: [Starlingx-discuss] Weekly Testing Meeting Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A3778EF26@FMSMSX105.amr.corp.intel.com> When: Tuesday, January 07, 2020 11:00 AM-12:00 PM. (UTC-06:00) Guadalajara, Mexico City, Monterrey *~*~*~*~*~*~*~*~*~* Please forward this meeting if I’m missing someone. Weekly meetings on Tuesdays at 9am Pacific • Zoom link: https://zoom.us/j/342730236 • Dialing in from phone: • Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 • Meeting ID: 342 730 236 • International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2089 bytes Desc: not available URL: From Chris.Winnicki at windriver.com Tue Jan 7 15:13:43 2020 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Tue, 7 Jan 2020 15:13:43 +0000 Subject: [Starlingx-discuss] Baremetal installation problem In-Reply-To: References: Message-ID: <7E4792BA14B1DE4BAB354DF77FE0233AC432F6B2@ALA-MBD.corp.ad.wrs.com> Hi Giuseppe Some questions. Do you have the serial port enabled in the bios? Do you have a telnet session/connection your DL380 machine? Have you tried to select "Graphical install" ? Note: If you select "Serial console" install and are monitoring the graphical terminal then you will indeed see a "black screen" because the output goes to the serial console. Chris Winnicki chris.winnicki at windriver.com 613-963-1329 ________________________________ From: Giuseppe Sannino [km.giuseppesannino at gmail.com] Sent: Tuesday, January 07, 2020 4:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Baremetal installation problem Hi all, I have an HP ProLiant DL380 Gen10 and the idea is to install STX 3.0 Baremetal All-In-One Controller Configuration". I downloaded the ISO from here: http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso I linked as Virtual Drive through the HP iLo and then booted from it. I'm able to see the "Select kernel options and boot kernel". Here I picked the "UEFI All-in-Hone Controller Configuratation" option. Then "Serial console". After that, basically I can just see a black screen with nothing going on. I can't see the installation going through. I tried with the 3.0.0 iso also on Virtualbox and on an Openstack data center, same result. Furthermore, the same happens using the 2.0 image. What am i doing wrong ? Thanks for your help /Giuseppe -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.friesen at windriver.com Tue Jan 7 15:49:07 2020 From: chris.friesen at windriver.com (Chris Friesen) Date: Tue, 7 Jan 2020 09:49:07 -0600 Subject: [Starlingx-discuss] CNCF K8s conformance - Error found In-Reply-To: <3177D746-58C3-4BE7-8E19-2AAA6A0036A0@intel.com> References: <3177D746-58C3-4BE7-8E19-2AAA6A0036A0@intel.com> Message-ID: There are some notes in the bug below, but for anyone looking at the list this was due to a mismatch between the x509 front-proxy-ca certificates/keys on the two controller nodes.  It was fixed by https://bugs.launchpad.net/starlingx/+bug/1855915 Chris On 12/27/2019 2:40 PM, Lemus Contreras, Cristopher J wrote: > > Hello All, > > I created a launchpad to track an error found during the CNCF K8s > conformance procedure: https://bugs.launchpad.net/starlingx/+bug/1857716 > > Conformance was executed using sonobuoy tool, instructions here: > https://github.com/cncf/k8s-conformance/blob/master/instructions.md > > This is the summary: > > Ran 276 of 4897 Specs in 9316.930 seconds > > FAIL! -- 275 Passed | 1 Failed | 0 Pending | 4621 Skipped > > --- FAIL: TestE2E (9316.96s) > > FAIL > > It looks like there’s an issue with the self-signed certificate that > might have caused the failures and skips. > > E1226 13:31:14.402186       1 authentication.go:63] Unable to > authenticate the request due to an error: [x509: certificate signed by > unknown authority (possibly because of "crypto/rsa: verification > error" while trying to verify candidate authority certificate > "front-proxy-ca"), x509: certificate signed by unknown authority] > > Some additional details can be found on launchpad, including the full > tar.gz file created by sonobuoy. Hopefully somebody can take a look at it. > > Regards, > > Cristopher > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Jan 7 15:54:13 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 7 Jan 2020 15:54:13 +0000 Subject: [Starlingx-discuss] Question about distributed openstack In-Reply-To: <1578363962363.7501@chinaunicom.cn> References: <1577772988426.88956@chinaunicom.cn> <1577773690103.64126@chinaunicom.cn>, <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> <1578363962363.7501@chinaunicom.cn> Message-ID: <9A85D2917C58154C960D95352B22818BED397C06@fmsmsx123.amr.corp.intel.com> Hi Wei. You are correct that the Dist Cloud architecture doesn’t currently support OpenStack on the edge nodes, and thus the image caching features in OpenStack aren’t available. Sadly your questions take me beyond the limits of my knowledge, so I need other folks in the community to join this thread and help you. brucej From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, January 6, 2020 6:26 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: 答复: Question about distributed openstack Hi Bruce, Many thanks for your reply. I'm using the starlingx 3.0. Maybe I didn't describe my question clearly. I want to setup the openstack on both central and edge. The main VM image storage will be on the central. When we deploy VM instance on edge, there's no image locally. So either get the image from central by demands, or save the image on both sides. It's heard from other that openstack couldn't be deployed on central cloud for version 3.0. And some more stratage for image sharing will be in version 4.0. Because version 4.0 would be a little late for us, it will be good to know some details and maybe we could do some simplified process. Thanks & Regards, Wei ________________________________ 发件人: Jones, Bruce E > 发送时间: 2020年1月7日 2:28 收件人: Wei Chen(联通集团联通云数据有限公司本部); starlingx-discuss at lists.starlingx.io 主题: RE: Question about distributed openstack Hello Wei. Distributed Cloud support is available in StarlingX 3.0 which was just recently released. You can find the ISO image here [1]. You can find documentation on how to setup a StarlingX distributed cloud at this link [2]. Once you have your cloud and its subclouds set up, you should be able to share images between them. brucej [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, December 30, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question about distributed openstack ​ Dear Sir/Madam, I'm an engineer that use the starlingx in our product. I setup a central cloud and an edge. Now I hit an issue about how to share the image from center to the edge. What I thought is, write one application on the edge, get the image list from center, then pull by demand. It's said that in the near future like starlingx 4.0, the distributed openstack will be leveraged and there's something about image process. So, could you share any idea/material about it? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 7 16:22:29 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jan 2020 11:22:29 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 8 - Still Failing! In-Reply-To: <879223458.537.1578349543220.JavaMail.javamailuser@localhost> References: <879223458.537.1578349543220.JavaMail.javamailuser@localhost> Message-ID: <2012430974.546.1578414150659.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 8 Status: Still Failing Timestamp: 20200107T162226Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T155448Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200107T155448Z DOCKER_BUILD_ID: jenkins-master-distro-20200107T155448Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T155448Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200107T155448Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From build.starlingx at gmail.com Tue Jan 7 16:22:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jan 2020 11:22:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 267 - Failure! Message-ID: <1843634480.550.1578414171304.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 267 Status: Failure Timestamp: 20200107T162232Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T155448Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200107T155448Z DOCKER_BUILD_ID: jenkins-master-distro-20200107T155448Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T155448Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200107T155448Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro From Tao.Liu at windriver.com Tue Jan 7 18:32:19 2020 From: Tao.Liu at windriver.com (Liu, Tao) Date: Tue, 7 Jan 2020 18:32:19 +0000 Subject: [Starlingx-discuss] Question about distributed openstack In-Reply-To: <9A85D2917C58154C960D95352B22818BED397C06@fmsmsx123.amr.corp.intel.com> References: <1577772988426.88956@chinaunicom.cn> <1577773690103.64126@chinaunicom.cn>, <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> <1578363962363.7501@chinaunicom.cn> <9A85D2917C58154C960D95352B22818BED397C06@fmsmsx123.amr.corp.intel.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4EDCD4F@ALA-MBD.corp.ad.wrs.com> Hi Wei, As far as I know, there are no current plans to support the shared openstack services such as Image service (glance). Regards. Tao From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, January 7, 2020 10:54 AM To: chenw66 at chinaunicom.cn; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Question about distributed openstack Hi Wei. You are correct that the Dist Cloud architecture doesn’t currently support OpenStack on the edge nodes, and thus the image caching features in OpenStack aren’t available. Sadly your questions take me beyond the limits of my knowledge, so I need other folks in the community to join this thread and help you. brucej From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, January 6, 2020 6:26 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: 答复: Question about distributed openstack Hi Bruce, Many thanks for your reply. I'm using the starlingx 3.0. Maybe I didn't describe my question clearly. I want to setup the openstack on both central and edge. The main VM image storage will be on the central. When we deploy VM instance on edge, there's no image locally. So either get the image from central by demands, or save the image on both sides. It's heard from other that openstack couldn't be deployed on central cloud for version 3.0. And some more stratage for image sharing will be in version 4.0. Because version 4.0 would be a little late for us, it will be good to know some details and maybe we could do some simplified process. Thanks & Regards, Wei ________________________________ 发件人: Jones, Bruce E > 发送时间: 2020年1月7日 2:28 收件人: Wei Chen(联通集团联通云数据有限公司本部); starlingx-discuss at lists.starlingx.io 主题: RE: Question about distributed openstack Hello Wei. Distributed Cloud support is available in StarlingX 3.0 which was just recently released. You can find the ISO image here [1]. You can find documentation on how to setup a StarlingX distributed cloud at this link [2]. Once you have your cloud and its subclouds set up, you should be able to share images between them. brucej [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, December 30, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question about distributed openstack ​ Dear Sir/Madam, I'm an engineer that use the starlingx in our product. I setup a central cloud and an edge. Now I hit an issue about how to share the image from center to the edge. What I thought is, write one application on the edge, get the image list from center, then pull by demand. It's said that in the near future like starlingx 4.0, the distributed openstack will be leveraged and there's something about image process. So, could you share any idea/material about it? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 7 18:37:33 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jan 2020 13:37:33 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 9 - Still Failing! In-Reply-To: <863076579.544.1578414147808.JavaMail.javamailuser@localhost> References: <863076579.544.1578414147808.JavaMail.javamailuser@localhost> Message-ID: <1981517336.554.1578422254141.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 9 Status: Still Failing Timestamp: 20200107T170105Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200107T163607Z DOCKER_BUILD_ID: jenkins-master-distro-20200107T163607Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200107T163607Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From build.starlingx at gmail.com Tue Jan 7 20:46:46 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jan 2020 15:46:46 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 10 - Still Failing! In-Reply-To: <1201316322.552.1578422251444.JavaMail.javamailuser@localhost> References: <1201316322.552.1578422251444.JavaMail.javamailuser@localhost> Message-ID: <1959623627.559.1578430007546.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 10 Status: Still Failing Timestamp: 20200107T203842Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200107T163607Z DOCKER_BUILD_ID: jenkins-master-distro-20200107T163607Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200107T163607Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false From maria.g.perez.ibarra at intel.com Tue Jan 7 21:08:31 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 7 Jan 2020 21:08:31 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200107 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-07 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] List of docker images http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007412.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Jan 7 21:25:27 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 7 Jan 2020 21:25:27 +0000 Subject: [Starlingx-discuss] Mid-cycle meetup in Chandler AZ Message-ID: <9A85D2917C58154C960D95352B22818BED39806A@fmsmsx123.amr.corp.intel.com> Last year we held a mid-cycle community meetup in sunny Chandler Arizona, and of course it rained. But perhaps this year will be different. The Intel team is able & willing to host the mid-cycle meetup again this year, at our Chandler campus, sometime soon. Let's try to set a date at the community call this week. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 7 21:49:54 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Jan 2020 16:49:54 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_post_installer - Build # 507 - Failure! Message-ID: <1626166219.563.1578433795264.JavaMail.javamailuser@localhost> Project: STX_build_post_installer Build #: 507 Status: Failure Timestamp: 20200107T214759Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200107T163607Z DOCKER_BUILD_ID: jenkins-master-distro-20200107T163607Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200107T163607Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200107T163607Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro From chenw66 at chinaunicom.cn Wed Jan 8 01:27:00 2020 From: chenw66 at chinaunicom.cn (=?gb2312?B?V2VpIENoZW4owarNqLyvzcXBqs2o1MbK/b7d09DP3rmry76xvrK/KQ==?=) Date: Wed, 8 Jan 2020 01:27:00 +0000 Subject: [Starlingx-discuss] =?gb2312?b?tPC4tDogUXVlc3Rpb24gYWJvdXQgZGlz?= =?gb2312?b?dHJpYnV0ZWQgb3BlbnN0YWNr?= In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4EDCD4F@ALA-MBD.corp.ad.wrs.com> References: <1577772988426.88956@chinaunicom.cn> <1577773690103.64126@chinaunicom.cn>, <9A85D2917C58154C960D95352B22818BED3970B5@fmsmsx123.amr.corp.intel.com> <1578363962363.7501@chinaunicom.cn> <9A85D2917C58154C960D95352B22818BED397C06@fmsmsx123.amr.corp.intel.com>, <7242A3DC72E453498E3D783BBB134C3EA4EDCD4F@ALA-MBD.corp.ad.wrs.com> Message-ID: <1578446804828.55672@chinaunicom.cn> Hi Tao & Bruce, Thank you for the confirmation. It's a big help for me to confirm what I should do later. Thanks again, Wei ________________________________ 发件人: Liu, Tao 发送时间: 2020年1月8日 2:32 收件人: Jones, Bruce E; Wei Chen(联通集团联通云数据有限公司本部); starlingx-discuss at lists.starlingx.io 主题: RE: Question about distributed openstack Hi Wei, As far as I know, there are no current plans to support the shared openstack services such as Image service (glance). Regards. Tao From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, January 7, 2020 10:54 AM To: chenw66 at chinaunicom.cn; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Question about distributed openstack Hi Wei. You are correct that the Dist Cloud architecture doesn’t currently support OpenStack on the edge nodes, and thus the image caching features in OpenStack aren’t available. Sadly your questions take me beyond the limits of my knowledge, so I need other folks in the community to join this thread and help you. brucej From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, January 6, 2020 6:26 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: 答复: Question about distributed openstack Hi Bruce, Many thanks for your reply. I'm using the starlingx 3.0. Maybe I didn't describe my question clearly. I want to setup the openstack on both central and edge. The main VM image storage will be on the central. When we deploy VM instance on edge, there's no image locally. So either get the image from central by demands, or save the image on both sides. It's heard from other that openstack couldn't be deployed on central cloud for version 3.0. And some more stratage for image sharing will be in version 4.0. Because version 4.0 would be a little late for us, it will be good to know some details and maybe we could do some simplified process. Thanks & Regards, Wei ________________________________ 发件人: Jones, Bruce E > 发送时间: 2020年1月7日 2:28 收件人: Wei Chen(联通集团联通云数据有限公司本部); starlingx-discuss at lists.starlingx.io 主题: RE: Question about distributed openstack Hello Wei. Distributed Cloud support is available in StarlingX 3.0 which was just recently released. You can find the ISO image here [1]. You can find documentation on how to setup a StarlingX distributed cloud at this link [2]. Once you have your cloud and its subclouds set up, you should be able to share images between them. brucej [1] http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html From: Wei Chen(联通集团联通云数据有限公司本部) [mailto:chenw66 at chinaunicom.cn] Sent: Monday, December 30, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Question about distributed openstack ? Dear Sir/Madam, I'm an engineer that use the starlingx in our product. I setup a central cloud and an edge. Now I hit an issue about how to share the image from center to the edge. What I thought is, write one application on the edge, get the image list from center, then pull by demand. It's said that in the near future like starlingx 4.0, the distributed openstack will be leveraged and there's something about image process. So, could you share any idea/material about it? Thanks & Regards, Wei 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. 如果您错误接收了该邮件,请通过电子邮件立即通知我们。请回复邮件到 hqs-spmc at chinaunicom.cn,即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to hqs-spmc at chinaunicom.cn ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Jan 8 01:34:33 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 8 Jan 2020 01:34:33 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 In-Reply-To: References: Message-ID: Hi Frank: Thanks your suggestion . Kata container and Ceph containerization topic feature were initialized and be tracking on non-openstack distro meeting since end of Jun last year. it is most for integration work for kata container , so it was being track in non-openstack distro meeting. It is welcome container expert joining non-openstack distro meeting. For your suggestion about Tingjie attending containerization meeting , I'm fine with it personally , it mostly depends on Tingjie's plan and schedule. Thanks. BR Austin Sun. -----Original Message----- From: Miller, Frank Sent: Tuesday, January 7, 2020 9:17 PM To: Sun, Austin ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi Austin - happy new year :) I suggest the kata containers topic be moved to the containers meeting (next meeting planned for Jan 14). I'm on the fence about which meeting should cover ceph containerization - it overlaps with both the non-openstack mandate due to this being ceph but also with the containerization mandate. There are more containers SMEs at the containerization meeting so I would suggest Tingie attend the containerization meeting as well as the non-Openstack meeting. Does that work? Frank -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, January 07, 2020 3:33 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi All: Happy New Year. Agenda for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) - Standardize Flock Package Versioning (JITStack-Daniels) - Kata Container (Shuicheng) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: Tarball: container builder and iso status : openstack rpm from centos8 ??? rt kernel rpm package from centos8 ??? * CVE issue tracking (Shuicheng) * Open Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Brent.Rowsell at windriver.com Wed Jan 8 01:49:27 2020 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 8 Jan 2020 01:49:27 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC2847D55@ALA-MBD.corp.ad.wrs.com> Austin, Kata container introduction is making fundamental changes to the container platform including changing the default runtime. Seems pretty logical this falls under the container sub-project. Brent -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, January 7, 2020 8:35 PM To: Miller, Frank ; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi Frank: Thanks your suggestion . Kata container and Ceph containerization topic feature were initialized and be tracking on non-openstack distro meeting since end of Jun last year. it is most for integration work for kata container , so it was being track in non-openstack distro meeting. It is welcome container expert joining non-openstack distro meeting. For your suggestion about Tingjie attending containerization meeting , I'm fine with it personally , it mostly depends on Tingjie's plan and schedule. Thanks. BR Austin Sun. -----Original Message----- From: Miller, Frank Sent: Tuesday, January 7, 2020 9:17 PM To: Sun, Austin ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi Austin - happy new year :) I suggest the kata containers topic be moved to the containers meeting (next meeting planned for Jan 14). I'm on the fence about which meeting should cover ceph containerization - it overlaps with both the non-openstack mandate due to this being ceph but also with the containerization mandate. There are more containers SMEs at the containerization meeting so I would suggest Tingie attend the containerization meeting as well as the non-Openstack meeting. Does that work? Frank -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, January 07, 2020 3:33 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi All: Happy New Year. Agenda for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) - Standardize Flock Package Versioning (JITStack-Daniels) - Kata Container (Shuicheng) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: Tarball: container builder and iso status : openstack rpm from centos8 ??? rt kernel rpm package from centos8 ??? * CVE issue tracking (Shuicheng) * Open Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Wed Jan 8 09:10:10 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 08 Jan 2020 03:10:10 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <4417ee$cj8n5h@fmsmga006.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200108T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From saichandu.behara at calsoftinc.com Wed Jan 8 09:21:27 2020 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Wed, 8 Jan 2020 14:51:27 +0530 Subject: [Starlingx-discuss] Any update on Calsoft's Images/ Doc Message-ID: <4a7a0920-8966-a5d0-ef58-a09e2d440b70@calsoftinc.com> Hi We have shared the StarlingX_all-in-one_Edgex_with_Openstack Images and doc. Any update on this. link: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html Please let us know, If you have any doubt regarding the same. -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From km.giuseppesannino at gmail.com Wed Jan 8 09:27:58 2020 From: km.giuseppesannino at gmail.com (Giuseppe Sannino) Date: Wed, 8 Jan 2020 10:27:58 +0100 Subject: [Starlingx-discuss] Baremetal installation problem In-Reply-To: <7E4792BA14B1DE4BAB354DF77FE0233AC432F6B2@ALA-MBD.corp.ad.wrs.com> References: <7E4792BA14B1DE4BAB354DF77FE0233AC432F6B2@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Chris, thanks a lot for your fast reply. I tried the "Graphical install" with the same result in the past. Consider that if I use an Ubuntu or CentOS ISO everything is visible on the console. I will double check the BiOS settings in case something is missing there. Further info, I triggered the installation by setting the Serial console and left the "black screen " there. I connected through the iLO console after a couple of hours and the installation was successful. At the moment, it seems only a problem of visualizing installation/bootstrap logs on the console. In case of any further suggestion I will be more than happy to explore alternatives. Thanks again /Giuseppe On Tue, 7 Jan 2020 at 16:13, Winnicki, Chris wrote: > Hi Giuseppe > > Some questions. > > Do you have the serial port enabled in the bios? > Do you have a telnet session/connection your DL380 machine? > Have you tried to select "Graphical install" ? > > Note: > If you select "Serial console" install and are monitoring the graphical > terminal then you will indeed see a "black screen" because the output goes > to the serial console. > > Chris Winnicki > chris.winnicki at windriver.com > 613-963-1329 > ------------------------------ > *From:* Giuseppe Sannino [km.giuseppesannino at gmail.com] > *Sent:* Tuesday, January 07, 2020 4:42 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Baremetal installation problem > > Hi all, > I have an HP ProLiant DL380 Gen10 and the idea is to install STX 3.0 > Baremetal All-In-One Controller Configuration". > > I downloaded the ISO from here: > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/iso/bootimage.iso > > I linked as Virtual Drive through the HP iLo and then booted from it. > > I'm able to see the "Select kernel options and boot kernel". > Here I picked the "UEFI All-in-Hone Controller Configuratation" option. > Then "Serial console". > > After that, basically I can just see a black screen with nothing going on. > I can't see the installation going through. > > I tried with the 3.0.0 iso also on Virtualbox and on an Openstack data > center, same result. > > Furthermore, the same happens using the 2.0 image. > > What am i doing wrong ? > > Thanks for your help > > /Giuseppe > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Wed Jan 8 11:44:13 2020 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Wed, 8 Jan 2020 17:14:13 +0530 Subject: [Starlingx-discuss] Any update on Calsoft's Images/ Doc In-Reply-To: <4a7a0920-8966-a5d0-ef58-a09e2d440b70@calsoftinc.com> References: <4a7a0920-8966-a5d0-ef58-a09e2d440b70@calsoftinc.com> Message-ID: <55978302-2474-202b-9523-48b0687e0b19@calsoftinc.com> ++ Kristal On 08-01-2020 14:51, Saichandu Behara wrote: > > Hi > > We have shared the StarlingX_all-in-one_Edgex_with_Openstack Images > and doc. can you please provide any latest update on this. > > link: > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html > > > Please let us know, If you have any doubt regarding the same. > > > -- > Thanks & Regards > Sai Chandu Behara -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 8 12:47:35 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Jan 2020 12:47:35 +0000 Subject: [Starlingx-discuss] Community Call (Jan 8, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B42D1E@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call coming up later today. We'll devote the first half of today's call to planning for the Test Hack-a-thon next week, as per Ian's email [3]. Please feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200108T1500 [3] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007353.html From austin.sun at intel.com Wed Jan 8 14:38:04 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 8 Jan 2020 14:38:04 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Message-ID: Hi All: Thanks join the call. MoM for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) Track the status on: https://etherpad.openstack.org/p/Ceph-Containerization-Task Finished Rook-plugin coding, and integrating sysinv modules with conductor/coommon modules. Bootstrap Rook-Ceph cluster with STX system configuration by helm-overriding, and also remove native puppet deployment scripts. - Standardize Flock Package Versioning (JITStack-Daniels) commit patches for example: https://review.opendev.org/#/c/698005/ fm contains some non-python code. Saul will sync-up w/ Bart and other reviewers to get an alignment. will continue to work on python packages firstly. - Kata Container (Shuicheng) Still new comments is coming, and perform some more tests. - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: most srpms , and ntp package is not uploaded yet . tarball: all tarball changes are uploaded . container builder and iso status: iso installation , man-db-cache-update services can not be found when installation. openstack rpm from centos8 rt kernel rpm package from centos8 plan to rebase master for centos8 branches in this week or next week. * CVE issue tracking (Shuicheng) all patches are merged in master. cherry-pick for stx.3.0 and stx 2.0 maintain branch( still on-going) * Open WW05 is CNY holiday , plan to cancel meeting in WW05. -----Original Message----- From: Sun, Austin Sent: Tuesday, January 7, 2020 4:33 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/8/2020 Hi All: Happy New Year. Agenda for 1/8 meeting: * stx.4.0 feature - Ceph Containerization (Tingjie/Martin) - Standardize Flock Package Versioning (JITStack-Daniels) - Kata Container (Shuicheng) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: Tarball: container builder and iso status : openstack rpm from centos8 ??? rt kernel rpm package from centos8 ??? * CVE issue tracking (Shuicheng) * Open Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From Brent.Rowsell at windriver.com Wed Jan 8 14:43:15 2020 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 8 Jan 2020 14:43:15 +0000 Subject: [Starlingx-discuss] Ceph Containerization feature discuss In-Reply-To: References: <2588653EBDFFA34B982FAF00F1B4844EC281C525@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC28484B8@ALA-MBD.corp.ad.wrs.com> Hi Austin, Is there any update on this ? Thanks, Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, December 18, 2019 9:47 AM To: Rowsell, Brent ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Ceph Containerization feature discuss Hi Brent : Thanks your mention this. We just discussed in non-distro meeting. Tingjie and Martin will think a way for ceph upgrade from stx.3.0 to stx.4.0 Thanks. BR Austin Sun. From: Rowsell, Brent > Sent: Wednesday, December 18, 2019 8:30 PM To: Sun, Austin >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Ceph Containerization feature discuss One significant item that seems to be missing here is the migration for users on stx3 to to stx4 with rook/ceph. We simply just can’t rip out the existing code and tell users to re-deploy. Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Monday, December 16, 2019 12:45 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] Ceph Containerization feature discuss Hi All: There was a good discuss about Ceph Containerization task and schedule during the 10th china open source hackathon. open questions/risk: 1.Ceph Images will be pull directly from upstream or built from stx 2. Sysinv integration with Ceph. 3. Ceph feature branch ? needed branch ha / stx-puppet / config / platform-armada-app / ansible-playbooks / integ / utilities 4.rook -client code repo like ceph-client 5. librados / rgw provide 6. Test case/Test Strategy. Schedule/Plan: 1)Python Rook Plugin for Sysinv and Command Tingjie / 2020-1-1 2)Bootstrap and Helm-Override Mapping Martin / 2020-1-4 3)CSI Provider Replace Rbd Provider for Sysinv KubeApp Martin / 2020-1-20 4)SysInv Openstack Interface support provisioning (Cinder/Swift) Tingjie / 2020-1-20 5)Integration/System command/Patch upload ??? Wait for the 4th task finish and Plan 6)Old code cleanup The Detail info was put in etherpad [1], but it was changed simple Chinese characters in some section. Thanks Tingjie, Martin and Yong. [1] https://etherpad.openstack.org/p/OpenSource-Hackathon-Ceph-Containerization Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 8 16:30:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Jan 2020 16:30:27 +0000 Subject: [Starlingx-discuss] Community Call (Jan 8, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B42EB3@ALA-MBD.corp.ad.wrs.com> Notes from today's meeting... - Test Hack-a-thon - planning for next week - per email from Ian: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007353.html - communication - devote the IRC channel to the hack-a-thon - other ideas? open a Zoom channel? - generally, how to stay in synch globally so our work doesn't collide - consensus seems to be a combination of... - IRC: for detailed communication - Etherpad: to capture the backlog, work item list - Mailing List: daily summary, for all to see, of the progress - proposed areas - starlingx/config (sysinv) - armada application life cycle management (kube_app) - api semantic validation (corner cases) - host system data generation (puppet/helm) - rpc callback interfaces - target as many varied system configurations (AIO-SX/DX+, Standard, Storage, IPv4, IPv6, etc) - agent auto inventory and host state management ** target conductor logic - starlingx/ansible-playbooks - fix Ansible lint errors so that it can be fully enabled - target as many varied system configurations - test non-default configurations - backup/restore - upgrades - next steps - create new etherpad for the Hack-a-thon - organize it... - decompose each item into discrete items that folks can work on - make it clear who's working on what - also note who is the prime for each area - checkpoint on next week's Community call to see how things are going - Intel internal changes (brucej) - most of the Intel folks have moved to the IOTG group - several of them will *not* be moving to IOTG, so will moving away from StarlingX - this is effective as of yesterday - sanity will continue for a little while (just the automated stuff) - Intel will work on moving the test activity to another group, no definitive timeline for this now - AR: Bruce to determine what the timeline is for having the new group in place - AR: Ada/Yang to assess the immediate-term impact - Reference material for StarlingX flock components (Frank): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007404.html - per Bruce, where is the long term home for this content? - there's a link to this from the developer resources page on the wiki - Yong has shared with the folks in China - Kris will potentially look at adding stuff like this in an appropriate place in the docs - Mid-Cycle meetup for the community @ Intel's Chandler (Phoenix AZ) campus. When can/do we want to do this? (brucej) - late Feb, early March? - Bruce will propose March 3/4 to the mailing list - we'll set up some kind of registration form for this, maybe an etherpad - Standing Topics - time permitting - Sanity: all green recently - Reviews needing input - Saul: CentOS 8 continuing effort - keep reviewing - discussion about test coverage on the feature branch before we bring it into master - etherpad to track the testing - make sure we've got a comprehensive list of tests that we need to run/pass before merging to master - make this a standing topic for this meeting, review the Etherpad (assuming there's a summary on the Etherpad) - Saul: pbr versioning reviews - some discussion ensued, Bart to take a 2nd look - Unanswered Requests for Help on Mailing List - didn't get to this this week - AR review - calsoft/saichandu- Any update on the image/Doc for StarlingX AIO openstack-- http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html - didn't get to this this week -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 8, 2020 7:48 AM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (Jan 8, 2020) Hi all, reminder of the Community call coming up later today. We'll devote the first half of today's call to planning for the Test Hack-a-thon next week, as per Ian's email [3]. Please feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200108T1500 [3] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007353.html From ada.cabrales at intel.com Wed Jan 8 16:51:35 2020 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 8 Jan 2020 16:51:35 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 01/07/2020 Message-ID: Agenda for 01/7/2020 Attendees: JoseP, Elio, Ada, Cristopher, JC, Maria P, Jessica, Fernando, Yang 1. Sanity Status: - Cristopher : close to EOY something broke the build system, but it's fixed now. Nothing remarkable to report. OpenStack is in bad state after controller forced reboot - https://bugs.launchpad.net/starlingx/+bug/1855474 2. Upcoming Activities stx.4.0 - proposed dates MS1 - 1/24 MS2 (specs proposal) - 3/27 MS3 (feature development) - 5/15 Feature testing - 5/29 Regression testing - 4/27 - 6/12 RC1 - 6/12 Final regression - 6/15 - 6/26 Release - 7/3 CNCF certification - we're looking for containers compliance certification. CNCF provides a tool for running certain test and the results have to be verified by the foundation. 3. Opens Ada : what has happened with the unified sanity? Cristopher - changes have been introduced to the infrastructure. We will give it another try. Yang - make sure the jump servers and the external VM network are not in the same vlan. Yang to bring the diagram sent by email a while back. -- Regards Ada From bruce.e.jones at intel.com Wed Jan 8 19:09:13 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 8 Jan 2020 19:09:13 +0000 Subject: [Starlingx-discuss] Mid-cycle Meetup Message-ID: <9A85D2917C58154C960D95352B22818BED398915@fmsmsx123.amr.corp.intel.com> As discussed in the community meeting today, we are planning a mid-cycle meetup at Intel's Chandler AZ location. We have tentatively set the dates as March 3rd-4th. If you would like to attend but cannot make those dates, please respond to this email with dates that would work for you. This meeting is open to all members of the StarlingX community and is expected to cover both issues related to the project's current work and planning for future releases. There is an etherpad for the event [1]. Please feel free to add agenda topics to the list, and your name to the Attendee list if you plan to attend. Thank you and see you all in Arizona! Brucej [1] https://etherpad.openstack.org/p/starlingX-winter-2020-meetup -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Jan 8 19:37:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 8 Jan 2020 14:37:06 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 626 - Failure! Message-ID: <1567658619.573.1578512226841.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 626 Status: Failure Timestamp: 20200108T193704Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200108T193653Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master-flock MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200108T193653Z DOCKER_BUILD_ID: jenkins-master-flock-20200108T193653Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200108T193653Z/logs DOCKER_BUILD_TAG: master-flock-20200108T193653Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200108T193653Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From maria.g.perez.ibarra at intel.com Wed Jan 8 22:04:46 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 8 Jan 2020 22:04:46 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200108 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-08 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] List of docker images http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007430.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Jan 8 22:19:14 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 8 Jan 2020 22:19:14 +0000 Subject: [Starlingx-discuss] Any update on Calsoft's Images/ Doc In-Reply-To: <55978302-2474-202b-9523-48b0687e0b19@calsoftinc.com> References: <4a7a0920-8966-a5d0-ef58-a09e2d440b70@calsoftinc.com> <55978302-2474-202b-9523-48b0687e0b19@calsoftinc.com> Message-ID: <43F963BD1517044B90CF82FB2F3CA7162348395F@fmsmsx120.amr.corp.intel.com> Hi Sai – thanks for following up on this in the new year and for all your ongoing efforts on this! I have the content staged to be added to the documentation (https://review.opendev.org/#/c/692202/). Final review and merging of the content is pending resolution of image hosting/being able to build the qcow2 image from scratch on our servers. We still have some open questions about building the qcow2 image from scratch. In order for us to move this ahead as quickly as possible, I suggest we meet (via a call) and discuss real-time the specific steps to create the image and any remaining questions from our side. I’ll email you directly to set up a time to meet. Cheers, Kris From: Saichandu Behara Sent: Wednesday, January 8, 2020 3:44 AM To: Bill.Zvonar at windriver.com; starlingx-discuss at lists.starlingx.io; Dale, Kristal Subject: Re: Any update on Calsoft's Images/ Doc ++ Kristal On 08-01-2020 14:51, Saichandu Behara wrote: Hi We have shared the StarlingX_all-in-one_Edgex_with_Openstack Images and doc. can you please provide any latest update on this. link: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html Please let us know, If you have any doubt regarding the same. -- Thanks & Regards Sai Chandu Behara -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison at openstack.org Wed Jan 8 22:59:43 2020 From: allison at openstack.org (Allison Price) Date: Wed, 8 Jan 2020 16:59:43 -0600 Subject: [Starlingx-discuss] StarlingX 3.0 Promotion Update Message-ID: Hi everyone, I wanted to provide an update on the timing of the StarlingX 3.0 promotion after today’s Marketing meeting. In order to give a little more time to finalize materials, we are going to schedule the go live date for next Tuesday, January 14 at 9am CT. We are planning to: Distribute a press release Post a blog on the StarlingX website from Glenn Seiler Promote on social media If you organization is interested in collaborating on promotion of the release, please reach out to me and I can share content that we are planning to use next week. Let me know if there are any questions or concerns. Thanks! Allison Allison Price OpenStack Foundation allison at openstack.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Jan 8 23:01:29 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 8 Jan 2020 15:01:29 -0800 Subject: [Starlingx-discuss] Community Call (Jan 8, 2020) In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B42EB3@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B42EB3@ALA-MBD.corp.ad.wrs.com> Message-ID: <6d871bf7-d759-f036-b98b-bc8021e95586@linux.intel.com> Following up on the CentOS-8 Item, I have created an etherpad for creating notes about functional areas that need to be tested: https://etherpad.openstack.org/p/centos8-testing I will send an additional email with this link. Sau! On 1/8/20 8:30 AM, Zvonar, Bill wrote: > Notes from today's meeting... > > - Test Hack-a-thon - planning for next week > - per email from Ian: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007353.html > - communication > - devote the IRC channel to the hack-a-thon > - other ideas? open a Zoom channel? > - generally, how to stay in synch globally so our work doesn't collide > - consensus seems to be a combination of... > - IRC: for detailed communication > - Etherpad: to capture the backlog, work item list > - Mailing List: daily summary, for all to see, of the progress > - proposed areas > - starlingx/config (sysinv) > - armada application life cycle management (kube_app) > - api semantic validation (corner cases) > - host system data generation (puppet/helm) > - rpc callback interfaces > - target as many varied system configurations (AIO-SX/DX+, Standard, Storage, IPv4, IPv6, etc) > - agent auto inventory and host state management ** target conductor logic > - starlingx/ansible-playbooks > - fix Ansible lint errors so that it can be fully enabled > - target as many varied system configurations > - test non-default configurations > - backup/restore > - upgrades > - next steps > - create new etherpad for the Hack-a-thon > - organize it... > - decompose each item into discrete items that folks can work on > - make it clear who's working on what > - also note who is the prime for each area > - checkpoint on next week's Community call to see how things are going > > - Intel internal changes (brucej) > - most of the Intel folks have moved to the IOTG group > - several of them will *not* be moving to IOTG, so will moving away from StarlingX > - this is effective as of yesterday - sanity will continue for a little while (just the automated stuff) > - Intel will work on moving the test activity to another group, no definitive timeline for this now > - AR: Bruce to determine what the timeline is for having the new group in place > - AR: Ada/Yang to assess the immediate-term impact > > - Reference material for StarlingX flock components (Frank): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007404.html > - per Bruce, where is the long term home for this content? > - there's a link to this from the developer resources page on the wiki > - Yong has shared with the folks in China > - Kris will potentially look at adding stuff like this in an appropriate place in the docs > > - Mid-Cycle meetup for the community @ Intel's Chandler (Phoenix AZ) campus. When can/do we want to do this? (brucej) > - late Feb, early March? > - Bruce will propose March 3/4 to the mailing list > - we'll set up some kind of registration form for this, maybe an etherpad > > - Standing Topics - time permitting > - Sanity: all green recently > - Reviews needing input > - Saul: CentOS 8 continuing effort - keep reviewing > - discussion about test coverage on the feature branch before we bring it into master > - etherpad to track the testing - make sure we've got a comprehensive list of tests that we need to run/pass before merging to master > - make this a standing topic for this meeting, review the Etherpad (assuming there's a summary on the Etherpad) > - Saul: pbr versioning reviews - some discussion ensued, Bart to take a 2nd look > - Unanswered Requests for Help on Mailing List > - didn't get to this this week > - AR review > - calsoft/saichandu- Any update on the image/Doc for StarlingX AIO openstack-- http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007064.html > - didn't get to this this week > > > -----Original Message----- > From: Zvonar, Bill > Sent: Wednesday, January 8, 2020 7:48 AM > To: starlingx-discuss at lists.starlingx.io > Subject: Community Call (Jan 8, 2020) > > Hi all, reminder of the Community call coming up later today. > > We'll devote the first half of today's call to planning for the Test Hack-a-thon next week, as per Ian's email [3]. > > Please feel free to add new topics to the agenda at [0]. > > Bill... > > [0] etherpad: https://etherpad.openstack.org/p/stx-status > [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call > [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200108T1500 > [3] http://lists.starlingx.io/pipermail/starlingx-discuss/2019-December/007353.html > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From sgw at linux.intel.com Wed Jan 8 23:14:00 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 8 Jan 2020 15:14:00 -0800 Subject: [Starlingx-discuss] CentOS-8 Tracking functional testing requirements. Message-ID: <704b1afe-46ac-a3a5-0029-f14e7175b775@linux.intel.com> Cores & Reviewers: There was an ask during the community call today to create an tracking etherpad [0] to track any additional functional testing requirements for the CentOS-8 branch to ensure that certain changes get tracked with testing beyond the Sanity and Regression testing that the CentOS-8 branch will go through before getting merged. Changes that folks want to see additional testing should be called out in both the Gerrit review and in the etherpad. This can allow reviews to get merged now so the branch can be used to create the ISO that can the be tested. We will need to address the testing prior to the time the various repo will merge to master. [0] https://etherpad.openstack.org/p/centos8-testing Thanks for your understanding. Sau! From build.starlingx at gmail.com Thu Jan 9 02:42:39 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 8 Jan 2020 21:42:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_info_file - Build # 536 - Failure! Message-ID: <60100328.580.1578537760663.JavaMail.javamailuser@localhost> Project: STX_build_info_file Build #: 536 Status: Failure Timestamp: 20200109T024237Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200109T023000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200109T023000Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200109T023000Z/logs MASTER_BUILD_NUMBER: 376 TIMESTAMP: 20200109T023000Z PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200109T023000Z/logs MASTER_JOB_NAME: STX_build_master_master LAYER: From build.starlingx at gmail.com Thu Jan 9 02:42:42 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 8 Jan 2020 21:42:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 376 - Failure! Message-ID: <379485075.583.1578537763779.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 376 Status: Failure Timestamp: 20200109T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200109T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From austin.sun at intel.com Thu Jan 9 07:52:45 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 9 Jan 2020 07:52:45 +0000 Subject: [Starlingx-discuss] Ceph Containerization feature discuss In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC28484B8@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EC281C525@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EC28484B8@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent: Tingjie , Marin and I have synced about migration of ceph upgrade from 3.0 to 4.0 offline. 1) it should be impossible to support live migration. 2) Tingjie and Marin will work migration tools/script to support ceph migration from 3.0 to 4.0. This is immature thought currently , Once ceph container is working, they will work to prove the concept and develop this tools. Thanks. BR Austin Sun. From: Rowsell, Brent Sent: Wednesday, January 8, 2020 10:43 PM To: Sun, Austin ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: [Starlingx-discuss] Ceph Containerization feature discuss Hi Austin, Is there any update on this ? Thanks, Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, December 18, 2019 9:47 AM To: Rowsell, Brent >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Ceph Containerization feature discuss Hi Brent : Thanks your mention this. We just discussed in non-distro meeting. Tingjie and Martin will think a way for ceph upgrade from stx.3.0 to stx.4.0 Thanks. BR Austin Sun. From: Rowsell, Brent > Sent: Wednesday, December 18, 2019 8:30 PM To: Sun, Austin >; 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [Starlingx-discuss] Ceph Containerization feature discuss One significant item that seems to be missing here is the migration for users on stx3 to to stx4 with rook/ceph. We simply just can’t rip out the existing code and tell users to re-deploy. Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Monday, December 16, 2019 12:45 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] Ceph Containerization feature discuss Hi All: There was a good discuss about Ceph Containerization task and schedule during the 10th china open source hackathon. open questions/risk: 1.Ceph Images will be pull directly from upstream or built from stx 2. Sysinv integration with Ceph. 3. Ceph feature branch ? needed branch ha / stx-puppet / config / platform-armada-app / ansible-playbooks / integ / utilities 4.rook -client code repo like ceph-client 5. librados / rgw provide 6. Test case/Test Strategy. Schedule/Plan: 1)Python Rook Plugin for Sysinv and Command Tingjie / 2020-1-1 2)Bootstrap and Helm-Override Mapping Martin / 2020-1-4 3)CSI Provider Replace Rbd Provider for Sysinv KubeApp Martin / 2020-1-20 4)SysInv Openstack Interface support provisioning (Cinder/Swift) Tingjie / 2020-1-20 5)Integration/System command/Patch upload ??? Wait for the 4th task finish and Plan 6)Old code cleanup The Detail info was put in etherpad [1], but it was changed simple Chinese characters in some section. Thanks Tingjie, Martin and Yong. [1] https://etherpad.openstack.org/p/OpenSource-Hackathon-Ceph-Containerization Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Thu Jan 9 12:31:04 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 9 Jan 2020 12:31:04 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 12/2019 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C16045DC@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C16045DC@ALA-MBD.corp.ad.wrs.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B432E5@ALA-MBD.corp.ad.wrs.com> Hi all - I'll host the release team meeting today as Ghada is unavailable. It'll be 30 minutes today - please let me know if you'd like to add anything in particular to the agenda. Bill... -----Original Message----- From: Khalil, Ghada Sent: Thursday, December 12, 2019 9:06 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Dec 12/2019 Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.3.0 - No build yet as per Scott's email. Current ETA is 7:30pm Eastern - Test team is waiting for the new build (monitored by Jenkins job) to start sanity - Once sanity is green, will mark the build as released and declare the release milestone - Need to keep an eye on the sanity issue that was reported in master: https://bugs.launchpad.net/starlingx/+bug/1856078 - Currently this was not seen on the rc 3.0 build - Will monitor to see if this appears in the next sanity on master or on the next 3.0 load Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ada.cabrales at intel.com Thu Jan 9 23:25:54 2020 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Thu, 9 Jan 2020 23:25:54 +0000 Subject: [Starlingx-discuss] Ada Cabrales resigning to the testing team Message-ID: Hello StarlingX Community Due to organizational changes happening internally at my company, I must resign my position as PL and member of the stx-test team. This was previously announced in the past community meeting (on 01/08/2020). Bruce Jones will be able to provide more information on who will be taking the testing responsibilities soon. Stay tuned. It has been an honor to work with all of you. Thanks for the learnings. Ada From zhipengs.liu at intel.com Fri Jan 10 02:23:00 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 10 Jan 2020 02:23:00 +0000 Subject: [Starlingx-discuss] Discuss about one VM evacuation failure issue Message-ID: <93814834B4855241994F290E959305C753123878@SHSMSX104.ccr.corp.intel.com> Hi Bart, I have been working on one OpenStack related LP below. https://bugs.launchpad.net/starlingx/+bug/1857462 You can get detail information in LP comments. Root cause was found after analyzed related log, it seems need a fix in NFV side. As you are NFV expert, I'd like to get your comment before I can work out the solution. Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Jan 10 05:33:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Jan 2020 00:33:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 578 - Failure! Message-ID: <362135625.587.1578634382762.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 578 Status: Failure Timestamp: 20200110T024241Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200110T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200110T023000Z DOCKER_BUILD_ID: jenkins-master-20200110T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200110T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200110T023000Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Jan 10 05:33:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 10 Jan 2020 00:33:05 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 377 - Still Failing! In-Reply-To: <354357945.581.1578537761449.JavaMail.javamailuser@localhost> References: <354357945.581.1578537761449.JavaMail.javamailuser@localhost> Message-ID: <1162508679.590.1578634385958.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 377 Status: Still Failing Timestamp: 20200110T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200110T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From dejan.muhamedagic at tttech-industrial.com Fri Jan 10 09:15:05 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Fri, 10 Jan 2020 09:15:05 +0000 Subject: [Starlingx-discuss] modify the amount of available memory Message-ID: Hi, I'm running starlingx in a VM and noticed that modifying the amount of memory of the VM has no effect in Starlingx. Is there a way to modify it? Or is reinstall the only remedy? Thanks! Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Bill.Zvonar at windriver.com Fri Jan 10 14:15:03 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Fri, 10 Jan 2020 14:15:03 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B4385A@ALA-MBD.corp.ad.wrs.com> Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... From Barton.Wensley at windriver.com Fri Jan 10 17:29:26 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 10 Jan 2020 17:29:26 +0000 Subject: [Starlingx-discuss] Discuss about one VM evacuation failure issue In-Reply-To: <93814834B4855241994F290E959305C753123878@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C753123878@SHSMSX104.ccr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBCB2C@ALA-MBD.corp.ad.wrs.com> Zhipeng, I took a look through the logs and the VIM is behaving correctly in this case - I added my analysis to the LP. Bart From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: January 9, 2020 9:23 PM To: Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Discuss about one VM evacuation failure issue Hi Bart, I have been working on one OpenStack related LP below. https://bugs.launchpad.net/starlingx/+bug/1857462 You can get detail information in LP comments. Root cause was found after analyzed related log, it seems need a fix in NFV side. As you are NFV expert, I'd like to get your comment before I can work out the solution. Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sun Jan 12 02:32:44 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Jan 2020 21:32:44 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 632 - Failure! Message-ID: <1760659519.595.1578796365164.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 632 Status: Failure Timestamp: 20200112T023127Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200112T023000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200112T023000Z DOCKER_BUILD_ID: jenkins-master-20200112T023000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200112T023000Z/logs DOCKER_BUILD_TAG: master-20200112T023000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200112T023000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Jan 12 02:32:47 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 11 Jan 2020 21:32:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 379 - Failure! Message-ID: <276321889.598.1578796368188.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 379 Status: Failure Timestamp: 20200112T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200112T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From build.starlingx at gmail.com Mon Jan 13 00:02:25 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Jan 2020 19:02:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 633 - Still Failing! In-Reply-To: <1098573137.593.1578796361880.JavaMail.javamailuser@localhost> References: <1098573137.593.1578796361880.JavaMail.javamailuser@localhost> Message-ID: <2113400017.601.1578873746027.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 633 Status: Still Failing Timestamp: 20200113T000124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200113T000000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200113T000000Z DOCKER_BUILD_ID: jenkins-master-20200113T000000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200113T000000Z/logs DOCKER_BUILD_TAG: master-20200113T000000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200113T000000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Jan 13 00:02:28 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 12 Jan 2020 19:02:28 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 380 - Still Failing! In-Reply-To: <1790644706.596.1578796365933.JavaMail.javamailuser@localhost> References: <1790644706.596.1578796365933.JavaMail.javamailuser@localhost> Message-ID: <2004741188.604.1578873749315.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 380 Status: Still Failing Timestamp: 20200113T000000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200113T000000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From zhipengs.liu at intel.com Mon Jan 13 02:31:29 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Mon, 13 Jan 2020 02:31:29 +0000 Subject: [Starlingx-discuss] Discuss about one VM evacuation failure issue In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBCB2C@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C753123878@SHSMSX104.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBCB2C@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C7531243E7@SHSMSX104.ccr.corp.intel.com> Hi Barton, Thanks for your clarification for current VIM design! Hi Peng, Could you retest and double check it again? Need to wait for enough time as mentioned in Barton’s comment. >From current log, there are 2 VMs already resumed on ctrl-1 after it reboot. The VIM is behaving correctly in this case. When a host with instances on it goes offline, the behaviour is as follows: - As long as the host is disabled, attempt to evacuate the instances from the host (one at a time). - When the host goes enabled (e.g. after it reboots) do not do any further evacuations (this could lead to an instance running on multiple hosts). - Once the hypervisor on the host goes enabled, recover any failed instances by rebooting (or rebuilding if the reboot fails). Thanks! Zhipeng From: Wensley, Barton Sent: 2020年1月11日 1:29 To: Liu, ZhipengS Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Discuss about one VM evacuation failure issue Zhipeng, I took a look through the logs and the VIM is behaving correctly in this case - I added my analysis to the LP. Bart From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: January 9, 2020 9:23 PM To: Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Discuss about one VM evacuation failure issue Hi Bart, I have been working on one OpenStack related LP below. https://bugs.launchpad.net/starlingx/+bug/1857462 You can get detail information in LP comments. Root cause was found after analyzed related log, it seems need a fix in NFV side. As you are NFV expert, I’d like to get your comment before I can work out the solution. Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Mon Jan 13 03:22:38 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Mon, 13 Jan 2020 03:22:38 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B4385A@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B4385A@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Bart, The statement in task AppOperator of sysinv SB prefers adding tests for one method in each commit, while the etherpad shows "use a single commit for each Storyboard Task". Does it mean each test for each method in AppOperator class needs a task created in SB 2007082 respectively? What's the best practice of this operation? (or create tasks in a separate SB?) Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Matt.Peters at windriver.com Mon Jan 13 12:23:51 2020 From: Matt.Peters at windriver.com (Peters, Matt) Date: Mon, 13 Jan 2020 12:23:51 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Message-ID: Hi Mingyuan, Additional tasks can be added if individual commits will be used for each of the public methods. -Matt On 2020-01-12, 10:24 PM, "Qi, Mingyuan" wrote: Hi Bart, The statement in task AppOperator of sysinv SB prefers adding tests for one method in each commit, while the etherpad shows "use a single commit for each Storyboard Task". Does it mean each test for each method in AppOperator class needs a task created in SB 2007082 respectively? What's the best practice of this operation? (or create tasks in a separate SB?) Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Mon Jan 13 18:42:17 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 13 Jan 2020 18:42:17 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200111 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-11 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] These results were tested in the last iso 01-11-2020 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Jan 13 21:03:29 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 13 Jan 2020 13:03:29 -0800 Subject: [Starlingx-discuss] Using NVME Disks instead of SD Message-ID: <39f925b1-064f-4def-dd8a-99e2e2bad0e3@linux.intel.com> Folks, I have been trying to get a NUC based deployment work, with Erich's help we managed to start with a pair of Skull Canyon NUCs running Duplex controllers. This NUC has a pair of Ethernet ports and can be configured with 2 NVME-based disks. I was able to get the devices booted initially with changes to the ISO first by hardcoding /dev/nvme0n1 in metal/bsp-files, later Don's tool helped address alternative boot_device and rootfs_device setting, but I am not sure it went far enough. Erich figured out that we needed to patch the sysinv sqlDB (by hand) in order to unlock and make the second controller usable. I went a little further and tried to hook up both work and storage nodes to create a 2+2+2 Standard lab, I had to hand edit the PXE boot cmdline and also do the sysinv SQL magic to unlock the compute and storage nodes, but the Storage configuration still failed. I am thinking there is still some hardcode "sda" and/or "sdb" in places. Any thoughts on how to enable the Storage nodes properly? I can provide logs, configs, ... I realize this is a problem at initial ISO boot/install to select the drive type, but from there is should be automagically detected on the target, so it would require setting the drive type of the host at the same time as setting the personality so that the anaconda at least knows where to start installing. It may be possible for anaconda to determine the drive time also. Should this be a story, launchpad bug or a Spec to allow use to properly use NVME devices with StarlingX. Or is this a solved problem that lacks proper documentation? Yes, we discussed some of this last March, but I guess it's still a problem and I think it's only going to become more common. Thoughts, direction welcome. Thanks Sau! From build.starlingx at gmail.com Mon Jan 13 21:25:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Jan 2020 16:25:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 29 - Failure! Message-ID: <1939116871.612.1578950702193.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 29 Status: Failure Timestamp: 20200113T212454Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200113T212356Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: flock.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200113T212356Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200113T212356Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From marcela.a.rosales.jimenez at intel.com Mon Jan 13 22:03:34 2020 From: marcela.a.rosales.jimenez at intel.com (Rosales Jimenez, Marcela A) Date: Mon, 13 Jan 2020 22:03:34 +0000 Subject: [Starlingx-discuss] Marcela Rosales resigning MultiOS team Message-ID: <2781C163-D62A-4818-B4DF-C82B213E6B1B@intel.com> Hi team, I am resigning my position as PL and member for MultiOS team due to organizational changes within Intel. MultiOS team or TSC should nominate a replacement if required. It was a pleasure working with you! Marcela -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 14 00:02:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Jan 2020 19:02:19 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! Message-ID: <1247400319.616.1578960139935.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 636 Status: Failure Timestamp: 20200114T000124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200114T000000Z DOCKER_BUILD_ID: jenkins-master-20200114T000000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs DOCKER_BUILD_TAG: master-20200114T000000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200114T000000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Tue Jan 14 00:02:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 13 Jan 2020 19:02:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 381 - Still Failing! In-Reply-To: <1112140363.602.1578873746954.JavaMail.javamailuser@localhost> References: <1112140363.602.1578873746954.JavaMail.javamailuser@localhost> Message-ID: <125790308.619.1578960143187.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 381 Status: Still Failing Timestamp: 20200114T000000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Frank.Miller at windriver.com Tue Jan 14 01:41:44 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 01:41:44 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Bi-weekly Meeting In-Reply-To: References: Message-ID: A reminder that there will be a meeting this week on Tuesday Jan 14. The 2 main topics will be: 1. Review status on 2006145: Kata container support [Shuicheng Lin] 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] If you have additional topics please add them to the etherpad: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank Sent: Monday, January 06, 2020 1:34 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: StarlingX Containerization Bi-weekly Meeting When: Tuesday, January 14, 2020 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 The next meeting for containerization will occur next week on Tuesday Jan 14. Agenda will be updated before the meeting but will include: Agenda for January 14 meeting: 1. Review status on 2006145: Kata container support [Shuicheng Lin] (should be merged by time of this meeting) 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC (every 2 weeks) Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Jan 14 05:13:01 2020 From: yong.hu at intel.com (Yong Hu) Date: Mon, 13 Jan 2020 22:13:01 -0700 Subject: [Starlingx-discuss] StarlingX Distro.OpenStack Bi-weekly Meeting - WW03'2020 Message-ID: <074b12fd-4f22-1370-f5e1-069a47bfc8e0@intel.com> A reminder that there will be a meeting this week on Tuesday Jan 14. The 2 main topics will be: 1. Discuss a PR [0] for Stx.2.0 CVE fix on stx-nava staging. @Dean, @Brent and @Shuicheng please join this topic. 2. Review OpenStack Service Upgrade from "Train" to "Ussuri" for stx.4.0 release. @Kunpeng and @Chant from 99Cloud and @Zhipeng, please update on this task. 3. Review LPs on distro.openstack [1] if we still have time 4. Open If you have additional topics please add them to the etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings [0] https://github.com/starlingx-staging/stx-nova/pull/27 [1] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Thanks, Yong From dorian_lau at 126.com Tue Jan 14 05:43:48 2020 From: dorian_lau at 126.com (Daolin Liu) Date: Tue, 14 Jan 2020 13:43:48 +0800 (CST) Subject: [Starlingx-discuss] Ansible bootstrap playbook error Message-ID: <1ebc2d11.669a.16fa2945691.Coremail.dorian_lau@126.com> Hi, I'm a rookie and this is the first time I study and install Starlingx (I have never used K8S and Openstack before). I am following the steps from: https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html I encountered an issue when I run "Ansible bootstrap playbook". After I copy /usr/share/ansible/stx-ansible/playbooks/bootstrap/host_vars/default.yml to $HOME/localhost.yml, and change some values in it, especially the registry k8s.gcr.io url to aliyun (since it can not pull image in China), I got below errors for kubelet init: [kubelet-check] Initial timeout of 40s passed. [kubelet-check] It seems like the kubelet isn't running or healthy. [kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp [::1]:10248: connect: connection refused. and some more information like this: Unfortunately, an error has occurred: timed out waiting for the condition This error is likely caused by: - The kubelet is not running - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled) If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet' Can someone give me any clues? Thanks, Daolin -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 14 08:40:54 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 14 Jan 2020 08:40:54 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/15/2020 Message-ID: Hi All: Agenda for 1/15 meeting: * stx.4.0 feature - Standardize Flock Package Versioning (JITStack-Daniels) - CentOS 8.0 upgrade planning (Shuai Zhao) Srpms: tarball: container builder and iso status: openstack rpm for centos8: * Unit Test for non-openstack project (Brainstorming) * Open Thanks. BR Austin Sun. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yi.c.wang at intel.com Tue Jan 14 08:44:07 2020 From: yi.c.wang at intel.com (Wang, Yi C) Date: Tue, 14 Jan 2020 08:44:07 +0000 Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon Message-ID: Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Tue Jan 14 09:02:42 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Tue, 14 Jan 2020 09:02:42 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Message-ID: Test Hack-a-thon Kube_app status: Jan 14th Mingyuan, Austin, Shuicheng is now working on kube_app test cases. 1. For kube_app AppOperator class, 5 commits out for review: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit out for review: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Team will continue working on adding test cases/mock for public methods of underlining 2 classes. Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Tue Jan 14 09:04:19 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 14 Jan 2020 10:04:19 +0100 Subject: [Starlingx-discuss] New project overview diagram for review Message-ID: Hi StarlingX Community, A few of us have been working on an update to the overview diagram we are using on the website and a couple more places to reflect better the new architecture of the project. You can find the new diagram on GitHub as the last entry on this issue: https://github.com/StarlingXWeb/starlingx-website/issues/39 Direct link to the diagram: https://user-images.githubusercontent.com/6662817/72329198-9c267280-36b4-11ea-9be8-d8d17a5d4f2b.jpg Please let us know if you have any feedback to the diagram. Thanks and Best Regards, Ildikó From tingjie.chen at intel.com Tue Jan 14 10:47:15 2020 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Tue, 14 Jan 2020 10:47:15 +0000 Subject: [Starlingx-discuss] About execute bash command in sysinv conductor Message-ID: Hi, I have met an issue when add a new plugin which called by sysinv, The plugin is to execute some bash commands, such as kubectl to get information, but it seems I have tried by using: Subprocess.Popen() and subprocess.check_output() it return failed with non-zero exit status 1. But I tried on my local Ubuntu environment, the result is OK. Is there any audit or privilege or some audit in Sysinv Service? Piece of code: execute_process = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=sys.stderr) objects = yaml.safe_load(execute_process.stdout) if execute_process.wait() != 0: raise ApiError return objects Following is the output: ----------------------------------------------------- sysinv 2020-01-14 10:31:20.038 1172858 INFO sysinv.common.ceph [-] ceph osd crush rule ls sysinv 2020-01-14 10:31:20.038 1172858 ERROR rook_client_kubeapi [-] ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:20.038 1172858 INFO rook_client_kubeapi [-] Get pod command: ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:45.026 1172858 ERROR sysinv.common.ceph [-] Exception in ls crush rule: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1: CalledProcessError: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 sysinv 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: CephFailure: OSD crush rule ls failed. Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last): 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp **args) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 4405, in iplatform_update_by_ihost 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp cceph.fix_crushmap(self.dbapi) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 947, in fix_crushmap 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp rule_is_present, __, __ = _operator._crush_rule_status(default_ceph_tier_name) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 67, in _crush_rule_status 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp raise exception.CephFailure("OSD crush rule ls failed. %s" %str(e)) Thanks, Tingjie SSP NST Storage Tel: +86(21)88216699 Mobile: 15901876439 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Jan 14 12:57:59 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 14 Jan 2020 12:57:59 +0000 Subject: [Starlingx-discuss] About execute bash command in sysinv conductor In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE1D5@ALA-MBD.corp.ad.wrs.com> Tingjie, It looks like you are missing the --kubeconfig parameter for kubectl, which should point to the /etc/kubernetes/admin.conf file which contains the authentication credentials. However, it is better to use the python-kubernetes API instead of kubectl - take a look at the KubeOperator class in sysinv/common/kubernetes.py - that is our preferred way to communicate with the kubernetes API. Bart From: Chen, Tingjie [mailto:tingjie.chen at intel.com] Sent: January 14, 2020 5:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] About execute bash command in sysinv conductor Hi, I have met an issue when add a new plugin which called by sysinv, The plugin is to execute some bash commands, such as kubectl to get information, but it seems I have tried by using: Subprocess.Popen() and subprocess.check_output() it return failed with non-zero exit status 1. But I tried on my local Ubuntu environment, the result is OK. Is there any audit or privilege or some audit in Sysinv Service? Piece of code: execute_process = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=sys.stderr) objects = yaml.safe_load(execute_process.stdout) if execute_process.wait() != 0: raise ApiError return objects Following is the output: ----------------------------------------------------- sysinv 2020-01-14 10:31:20.038 1172858 INFO sysinv.common.ceph [-] ceph osd crush rule ls sysinv 2020-01-14 10:31:20.038 1172858 ERROR rook_client_kubeapi [-] ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:20.038 1172858 INFO rook_client_kubeapi [-] Get pod command: ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:45.026 1172858 ERROR sysinv.common.ceph [-] Exception in ls crush rule: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1: CalledProcessError: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 sysinv 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: CephFailure: OSD crush rule ls failed. Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last): 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp **args) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 4405, in iplatform_update_by_ihost 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp cceph.fix_crushmap(self.dbapi) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 947, in fix_crushmap 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp rule_is_present, __, __ = _operator._crush_rule_status(default_ceph_tier_name) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 67, in _crush_rule_status 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp raise exception.CephFailure("OSD crush rule ls failed. %s" %str(e)) Thanks, Tingjie SSP NST Storage Tel: +86(21)88216699 Mobile: 15901876439 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Jan 14 13:09:07 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 14 Jan 2020 13:09:07 +0000 Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon Message-ID: <93814834B4855241994F290E959305C7531247D1@SHSMSX104.ccr.corp.intel.com> Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on fault project: 1. Created 7 tasks, https://storyboard.openstack.org/#!/story/2007082 2. Submitted 6 patches for review https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP Welcome more people join in this task force. We have 100+ RPC EP need to be done for unit test. Thanks. Zhipeng From: Wang, Yi C Sent: 2020年1月14日 16:44 To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan ; An, Ran1 Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From tingjie.chen at intel.com Tue Jan 14 13:26:59 2020 From: tingjie.chen at intel.com (Chen, Tingjie) Date: Tue, 14 Jan 2020 13:26:59 +0000 Subject: [Starlingx-discuss] About execute bash command in sysinv conductor In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE1D5@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE1D5@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Barton, I think it is the reason for the failure :) Yes, It is a better way to use Kubernetes.client API to communicate with Kubernetes cluster, but the interface in sysinv/common/Kubernetes.py is not enough to support the Ceph plugin, so I have made a simple kube Api to verify the functionality and it will be better to extend the interface in Kubernetes.py to support Ceph plugin further, for example: https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md#connect_get_namespaced_pod_exec Thanks, Tingjie From: Wensley, Barton Sent: Tuesday, January 14, 2020 8:58 PM To: Chen, Tingjie ; starlingx-discuss at lists.starlingx.io Subject: RE: About execute bash command in sysinv conductor Tingjie, It looks like you are missing the --kubeconfig parameter for kubectl, which should point to the /etc/kubernetes/admin.conf file which contains the authentication credentials. However, it is better to use the python-kubernetes API instead of kubectl - take a look at the KubeOperator class in sysinv/common/kubernetes.py - that is our preferred way to communicate with the kubernetes API. Bart From: Chen, Tingjie [mailto:tingjie.chen at intel.com] Sent: January 14, 2020 5:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] About execute bash command in sysinv conductor Hi, I have met an issue when add a new plugin which called by sysinv, The plugin is to execute some bash commands, such as kubectl to get information, but it seems I have tried by using: Subprocess.Popen() and subprocess.check_output() it return failed with non-zero exit status 1. But I tried on my local Ubuntu environment, the result is OK. Is there any audit or privilege or some audit in Sysinv Service? Piece of code: execute_process = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=sys.stderr) objects = yaml.safe_load(execute_process.stdout) if execute_process.wait() != 0: raise ApiError return objects Following is the output: ----------------------------------------------------- sysinv 2020-01-14 10:31:20.038 1172858 INFO sysinv.common.ceph [-] ceph osd crush rule ls sysinv 2020-01-14 10:31:20.038 1172858 ERROR rook_client_kubeapi [-] ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:20.038 1172858 INFO rook_client_kubeapi [-] Get pod command: ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:45.026 1172858 ERROR sysinv.common.ceph [-] Exception in ls crush rule: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1: CalledProcessError: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 sysinv 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: CephFailure: OSD crush rule ls failed. Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last): 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp **args) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 4405, in iplatform_update_by_ihost 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp cceph.fix_crushmap(self.dbapi) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 947, in fix_crushmap 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp rule_is_present, __, __ = _operator._crush_rule_status(default_ceph_tier_name) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 67, in _crush_rule_status 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp raise exception.CephFailure("OSD crush rule ls failed. %s" %str(e)) Thanks, Tingjie SSP NST Storage Tel: +86(21)88216699 Mobile: 15901876439 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 14 13:47:39 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 14 Jan 2020 13:47:39 +0000 Subject: [Starlingx-discuss] New project overview diagram for review In-Reply-To: References: Message-ID: Hi Ildikó: This diagram looks fancy and clear. One Small suggestion , we should add Redfish in diagram , which is same function as IPMI using for Host Manager. Thanks. BR Austin Sun. -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, January 14, 2020 5:04 PM To: starlingx Subject: [Starlingx-discuss] New project overview diagram for review Hi StarlingX Community, A few of us have been working on an update to the overview diagram we are using on the website and a couple more places to reflect better the new architecture of the project. You can find the new diagram on GitHub as the last entry on this issue: https://github.com/StarlingXWeb/starlingx-website/issues/39 Direct link to the diagram: https://user-images.githubusercontent.com/6662817/72329198-9c267280-36b4-11ea-9be8-d8d17a5d4f2b.jpg Please let us know if you have any feedback to the diagram. Thanks and Best Regards, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Barton.Wensley at windriver.com Tue Jan 14 13:57:36 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 14 Jan 2020 13:57:36 +0000 Subject: [Starlingx-discuss] About execute bash command in sysinv conductor In-Reply-To: References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE1D5@ALA-MBD.corp.ad.wrs.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE2FA@ALA-MBD.corp.ad.wrs.com> Thanks Tingjie. Using kubectl for prototyping is OK, but when you are submitting code for review, please extend the KubeOperator to support the APIs you require. Bart From: Chen, Tingjie [mailto:tingjie.chen at intel.com] Sent: January 14, 2020 8:27 AM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io Subject: RE: About execute bash command in sysinv conductor Thanks Barton, I think it is the reason for the failure :) Yes, It is a better way to use Kubernetes.client API to communicate with Kubernetes cluster, but the interface in sysinv/common/Kubernetes.py is not enough to support the Ceph plugin, so I have made a simple kube Api to verify the functionality and it will be better to extend the interface in Kubernetes.py to support Ceph plugin further, for example: https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md#connect_get_namespaced_pod_exec Thanks, Tingjie From: Wensley, Barton Sent: Tuesday, January 14, 2020 8:58 PM To: Chen, Tingjie ; starlingx-discuss at lists.starlingx.io Subject: RE: About execute bash command in sysinv conductor Tingjie, It looks like you are missing the --kubeconfig parameter for kubectl, which should point to the /etc/kubernetes/admin.conf file which contains the authentication credentials. However, it is better to use the python-kubernetes API instead of kubectl - take a look at the KubeOperator class in sysinv/common/kubernetes.py - that is our preferred way to communicate with the kubernetes API. Bart From: Chen, Tingjie [mailto:tingjie.chen at intel.com] Sent: January 14, 2020 5:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] About execute bash command in sysinv conductor Hi, I have met an issue when add a new plugin which called by sysinv, The plugin is to execute some bash commands, such as kubectl to get information, but it seems I have tried by using: Subprocess.Popen() and subprocess.check_output() it return failed with non-zero exit status 1. But I tried on my local Ubuntu environment, the result is OK. Is there any audit or privilege or some audit in Sysinv Service? Piece of code: execute_process = subprocess.Popen(command, stdout=subprocess.PIPE, stderr=sys.stderr) objects = yaml.safe_load(execute_process.stdout) if execute_process.wait() != 0: raise ApiError return objects Following is the output: ----------------------------------------------------- sysinv 2020-01-14 10:31:20.038 1172858 INFO sysinv.common.ceph [-] ceph osd crush rule ls sysinv 2020-01-14 10:31:20.038 1172858 ERROR rook_client_kubeapi [-] ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:20.038 1172858 INFO rook_client_kubeapi [-] Get pod command: ['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"'] sysinv 2020-01-14 10:31:45.026 1172858 ERROR sysinv.common.ceph [-] Exception in ls crush rule: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1: CalledProcessError: Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 sysinv 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp [-] Exception during message handling: CephFailure: OSD crush rule ls failed. Command '['/usr/bin/kubectl', 'get', '--namespace', 'kube-system', 'pod', '-l', 'app=rook-ceph-tools', '-o', 'jsonpath="{.items[0].metadata.name}"']' returned non-zero exit status 1 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp Traceback (most recent call last): 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/amqp.py", line 437, in _process_data 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp **args) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/openstack/common/rpc/dispatcher.py", line 172, in dispatch 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp result = getattr(proxyobj, method)(ctxt, **kwargs) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/conductor/manager.py", line 4405, in iplatform_update_by_ihost 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp cceph.fix_crushmap(self.dbapi) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 947, in fix_crushmap 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp rule_is_present, __, __ = _operator._crush_rule_status(default_ceph_tier_name) 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp File "/usr/lib64/python2.7/site-packages/sysinv/common/ceph.py", line 67, in _crush_rule_status 2020-01-14 10:31:45.027 1172858 ERROR sysinv.openstack.common.rpc.amqp raise exception.CephFailure("OSD crush rule ls failed. %s" %str(e)) Thanks, Tingjie SSP NST Storage Tel: +86(21)88216699 Mobile: 15901876439 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 14:22:07 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 14:22:07 +0000 Subject: [Starlingx-discuss] Using NVME Disks instead of SD In-Reply-To: <39f925b1-064f-4def-dd8a-99e2e2bad0e3@linux.intel.com> References: <39f925b1-064f-4def-dd8a-99e2e2bad0e3@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DAE67@ALA-MBD.corp.ad.wrs.com> For the second controller and other nodes installing from the active controller, you can set the rootfs_device and boot_device installation parameters via sysinv, either with horizon or the "system host-update" command, such as: system host-update 2 personality=controller rootfs_device=/dev/nvme0n1 boot_device=/dev/nvme0n1 You can see these settings via host-show: system host-show controller-1 -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, January 13, 2020 4:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Using NVME Disks instead of SD Folks, I have been trying to get a NUC based deployment work, with Erich's help we managed to start with a pair of Skull Canyon NUCs running Duplex controllers. This NUC has a pair of Ethernet ports and can be configured with 2 NVME-based disks. I was able to get the devices booted initially with changes to the ISO first by hardcoding /dev/nvme0n1 in metal/bsp-files, later Don's tool helped address alternative boot_device and rootfs_device setting, but I am not sure it went far enough. Erich figured out that we needed to patch the sysinv sqlDB (by hand) in order to unlock and make the second controller usable. I went a little further and tried to hook up both work and storage nodes to create a 2+2+2 Standard lab, I had to hand edit the PXE boot cmdline and also do the sysinv SQL magic to unlock the compute and storage nodes, but the Storage configuration still failed. I am thinking there is still some hardcode "sda" and/or "sdb" in places. Any thoughts on how to enable the Storage nodes properly? I can provide logs, configs, ... I realize this is a problem at initial ISO boot/install to select the drive type, but from there is should be automagically detected on the target, so it would require setting the drive type of the host at the same time as setting the personality so that the anaconda at least knows where to start installing. It may be possible for anaconda to determine the drive time also. Should this be a story, launchpad bug or a Spec to allow use to properly use NVME devices with StarlingX. Or is this a solved problem that lacks proper documentation? Yes, we discussed some of this last March, but I guess it's still a problem and I think it's only going to become more common. Thoughts, direction welcome. Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Tue Jan 14 15:05:33 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 14 Jan 2020 10:05:33 -0500 Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! In-Reply-To: <1247400319.616.1578960139935.JavaMail.javamailuser@localhost> References: <1247400319.616.1578960139935.JavaMail.javamailuser@localhost> Message-ID: Container setup failed on this command. stx-tools/Dockerfile ... RUN pip install python-subunit junitxml --upgrade && \     pip install tox --upgrade resulting in ... *00:00:52.319* Downloadinghttps://files.pythonhosted.org/packages/df/8c/c278395367a46c00d28036143fdc6583db8f98622b83875403f16473509b/more-itertools-8.1.0.tar.gz (78kB) *00:00:52.485* Complete output from command python setup.py egg_info: *00:00:52.485* Traceback (most recent call last): *00:00:52.485* File "", line 1, in *00:00:52.485* File "/tmp/pip-build-ixeFen/more-itertools/setup.py", line 5, in *00:00:52.485* from more_itertools import __version__ *00:00:52.485* File "more_itertools/__init__.py", line 1, in *00:00:52.485* from .more import * # noqa *00:00:52.485* File "more_itertools/more.py", line 480 *00:00:52.485* yield from iterable *00:00:52.485* ^ *00:00:52.485* SyntaxError: invalid syntax *00:00:52.485* *00:00:52.485* ---------------------------------------- *00:00:52.517* Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-ixeFen/more-itertools/ *00:00:52.517* You are using pip version 8.1.2, however version 19.3.1 is available. We haven't changed the dockerfile. Something has changed upstream at pypi.  Has anyone else observed this? Scott On 2020-01-13 7:02 p.m., build.starlingx at gmail.com wrote: > Project: STX_BUILD_container_setup > Build #: 636 > Status: Failure > Timestamp: 20200114T000124Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs > -------------------------------------------------------------------------------- > Parameters > > PROJECT: master > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200114T000000Z > DOCKER_BUILD_ID: jenkins-master-20200114T000000Z-builder > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs > DOCKER_BUILD_TAG: master-20200114T000000Z-builder-image > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200114T000000Z/logs > MY_REPO_ROOT: /localdisk/designer/jenkins/master > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 14 15:20:47 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 15:20:47 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Bi-weekly Meeting References: Message-ID: Thank-you to all for participating in today's meeting - here are the minutes: Note: the next meeting will be Tuesday Feb 4 Minutes for January 14 meeting: 1. Review status on 2006145: Kata container support [Shuicheng Lin] (should be merged by time of this meeting) - Shuicheng's main commits are now merged - Remaining work items include: - remove dockerd after all containers switch to containerd - update "Rotate k8s certificate" code in patch 692276 to use containerd - Open issue: - Shuicheng cannot remove dockerd as the containerd crictl command does not support image push function ACTIONs: i) Brent to have a look offline about the crictl limitation for pushing images; ideally we want to remove dockerd so would be good to identify a solution ii) Shuicheng to hold a brief demo at the next containerization meeting on Feb 4; Greg/Frank to provide suggestions of what we would like to see 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] - Tingie gave an update of the tasks for this feature (Reference: https://etherpad.openstack.org/p/Ceph-Containerization-Task) - Some discussion held on 2 option design questions: a) Why is sysinv involved in configuring CEPH with Rook - how can we have Rook do all the configuration and not have sysinv involved? b) How will an existing customer with a mimc ceph cluster migrate to a Rook ceph cluster? - Plan is for the feature primes to continue to flush out these 2 design questions and we'll continue the discussion at the next containerization meeting on Feb 4 3. Other topics? - [Mingyuan] Please review https://review.opendev.org/#/c/698619/ , addressing Ironic LP https://bugs.launchpad.net/starlingx/+bug/1855319 --> Bob will review this week; will also need another core to review - [Mingyuan] Need inputs from container cores for user application gen tool https://review.opendev.org/#/c/697013/ --> Bob will review this week; Frank will also ask Angie to review as well _____________________________________________ From: Miller, Frank Sent: Monday, January 13, 2020 8:42 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: RE: StarlingX Containerization Bi-weekly Meeting A reminder that there will be a meeting this week on Tuesday Jan 14. The 2 main topics will be: 1. Review status on 2006145: Kata container support [Shuicheng Lin] 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] If you have additional topics please add them to the etherpad: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank Sent: Monday, January 06, 2020 1:34 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: StarlingX Containerization Bi-weekly Meeting When: Tuesday, January 14, 2020 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 The next meeting for containerization will occur next week on Tuesday Jan 14. Agenda will be updated before the meeting but will include: Agenda for January 14 meeting: 1. Review status on 2006145: Kata container support [Shuicheng Lin] (should be merged by time of this meeting) 2. Review status on 2005527: CEPH Containerization in StarlingX [Tingjie Chen] 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC (every 2 weeks) Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 14 15:27:03 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 15:27:03 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Adding this invite into our calendars for the next containerization meeting which will be held on Feb 4th. Agenda will be updated before the meeting but will include: 1. KATA containers demo [Shuicheng] 2. Continued discussion for 2005527: CEPH Containerization in StarlingX [Tingjie Chen] - Update/discussion on how Rook will configure ceph (and not have sysinv involved) - Update/discussion on approach for an existing user with ceph mimic to migrate to a rook ceph cluster 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2679 bytes Desc: not available URL: From Don.Penney at windriver.com Tue Jan 14 16:33:10 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 16:33:10 +0000 Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! In-Reply-To: References: <1247400319.616.1578960139935.JavaMail.javamailuser@localhost> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DAFBD@ALA-MBD.corp.ad.wrs.com> I've posted https://review.opendev.org/702471 to resolve the build failure, constraining more-itertools to the last version that officially supports python 2.7. From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 10:06 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! Container setup failed on this command. stx-tools/Dockerfile ... RUN pip install python-subunit junitxml --upgrade && \ pip install tox --upgrade resulting in ... 00:00:52.319 Downloading https://files.pythonhosted.org/packages/df/8c/c278395367a46c00d28036143fdc6583db8f98622b83875403f16473509b/more-itertools-8.1.0.tar.gz (78kB) 00:00:52.485 Complete output from command python setup.py egg_info: 00:00:52.485 Traceback (most recent call last): 00:00:52.485 File "", line 1, in 00:00:52.485 File "/tmp/pip-build-ixeFen/more-itertools/setup.py", line 5, in 00:00:52.485 from more_itertools import __version__ 00:00:52.485 File "more_itertools/__init__.py", line 1, in 00:00:52.485 from .more import * # noqa 00:00:52.485 File "more_itertools/more.py", line 480 00:00:52.485 yield from iterable 00:00:52.485 ^ 00:00:52.485 SyntaxError: invalid syntax 00:00:52.485 00:00:52.485 ---------------------------------------- 00:00:52.517 [91mCommand "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-ixeFen/more-itertools/ 00:00:52.517 [0m[91mYou are using pip version 8.1.2, however version 19.3.1 is available. We haven't changed the dockerfile. Something has changed upstream at pypi. Has anyone else observed this? Scott On 2020-01-13 7:02 p.m., build.starlingx at gmail.com wrote: Project: STX_BUILD_container_setup Build #: 636 Status: Failure Timestamp: 20200114T000124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200114T000000Z DOCKER_BUILD_ID: jenkins-master-20200114T000000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs DOCKER_BUILD_TAG: master-20200114T000000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200114T000000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 17:25:07 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 17:25:07 +0000 Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DAFBD@ALA-MBD.corp.ad.wrs.com> References: <1247400319.616.1578960139935.JavaMail.javamailuser@localhost> <6703202FD9FDFF4A8DA9ACF104AE129FC15DAFBD@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB034@ALA-MBD.corp.ad.wrs.com> Update has been merged and a new CENGN build has been launched. From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 11:33 AM To: Little, Scott; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! I've posted https://review.opendev.org/702471 to resolve the build failure, constraining more-itertools to the last version that officially supports python 2.7. From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 10:06 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 636 - Failure! Container setup failed on this command. stx-tools/Dockerfile ... RUN pip install python-subunit junitxml --upgrade && \ pip install tox --upgrade resulting in ... 00:00:52.319 Downloading https://files.pythonhosted.org/packages/df/8c/c278395367a46c00d28036143fdc6583db8f98622b83875403f16473509b/more-itertools-8.1.0.tar.gz (78kB) 00:00:52.485 Complete output from command python setup.py egg_info: 00:00:52.485 Traceback (most recent call last): 00:00:52.485 File "", line 1, in 00:00:52.485 File "/tmp/pip-build-ixeFen/more-itertools/setup.py", line 5, in 00:00:52.485 from more_itertools import __version__ 00:00:52.485 File "more_itertools/__init__.py", line 1, in 00:00:52.485 from .more import * # noqa 00:00:52.485 File "more_itertools/more.py", line 480 00:00:52.485 yield from iterable 00:00:52.485 ^ 00:00:52.485 SyntaxError: invalid syntax 00:00:52.485 00:00:52.485 ---------------------------------------- 00:00:52.517 [91mCommand "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-ixeFen/more-itertools/ 00:00:52.517 [0m[91mYou are using pip version 8.1.2, however version 19.3.1 is available. We haven't changed the dockerfile. Something has changed upstream at pypi. Has anyone else observed this? Scott On 2020-01-13 7:02 p.m., build.starlingx at gmail.com wrote: Project: STX_BUILD_container_setup Build #: 636 Status: Failure Timestamp: 20200114T000124Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200114T000000Z DOCKER_BUILD_ID: jenkins-master-20200114T000000Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T000000Z/logs DOCKER_BUILD_TAG: master-20200114T000000Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200114T000000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Jan 14 17:40:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 14 Jan 2020 12:40:22 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! In-Reply-To: <1965855460.617.1578960140747.JavaMail.javamailuser@localhost> References: <1965855460.617.1578960140747.JavaMail.javamailuser@localhost> Message-ID: <1410052238.624.1579023623166.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Don.Penney at windriver.com Tue Jan 14 17:47:19 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 17:47:19 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From Barton.Wensley at windriver.com Tue Jan 14 18:19:36 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 14 Jan 2020 18:19:36 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1BBE5A8@ALA-MBD.corp.ad.wrs.com> Good progress - thanks for the update. I have noticed that some of the commits are failing tox tests (e.g. flake8 or py27). Please run the tox tests locally before you create your review in gerrit (and before you upload each patch). You should be able to fix all the errors before the review gets uploaded. We'll wait for you to fix the tox failures before reviewing the commits with the failures. Bart -----Original Message----- From: Qi, Mingyuan [mailto:mingyuan.qi at intel.com] Sent: January 14, 2020 4:03 AM To: Zvonar, Bill; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 14th Mingyuan, Austin, Shuicheng is now working on kube_app test cases. 1. For kube_app AppOperator class, 5 commits out for review: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit out for review: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Team will continue working on adding test cases/mock for public methods of underlining 2 classes. Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Tue Jan 14 19:22:45 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 14 Jan 2020 14:22:45 -0500 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> Message-ID: <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11     36M     Details [ ]    kata-ksm-throttler-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:33     5.9M     Details [ ]    kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22     8.3M     Details [ ]    kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22     335K     Details [ ]    kata-proxy-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11 2.4K     Details [ ]    kata-proxy-bin-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11     1.8M     Details [ ]    kata-runtime-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:39 20M     Details [ ]    kata-shim-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:20 2.4K     Details [ ]    kata-shim-bin-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:20 7.3M     Details [ ]    qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29     2.5K     Details [ ]    qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29     2.6M     Details [ ]    qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29     3.0M     Details [ ]    qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44     2.6K     Details [ ]    qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44     2.5M     Details [ ]    qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44     13M     Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser.  Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools.  IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: > The latest CENGN build attempt fails on the RPM download stage, with the following errors: > > > > Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 > No Match for argument kata-containers-image-1.9.2-7.1 > Nothing to download > Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 > No Match for argument kata-containers-image-1.9.2-7.1 > Nothing to download > Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 > No Match for argument kata-ksm-throttler-1.9.2-7.1 > Nothing to download > Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 > No Match for argument kata-ksm-throttler-1.9.2-7.1 > Nothing to download > Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 > No Match for argument kata-linux-container-4.19.75.54-7.1 > Nothing to download > Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 > No Match for argument kata-linux-container-4.19.75.54-7.1 > Nothing to download > Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 > No Match for argument kata-linux-container-debug-4.19.75.54-7.1 > Nothing to download > Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 > No Match for argument kata-linux-container-debug-4.19.75.54-7.1 > Nothing to download > Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-proxy-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 > No Match for argument kata-proxy-1.9.2-7.1 > Nothing to download > Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found > Looking for kata-proxy-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 > No Match for argument kata-proxy-1.9.2-7.1 > Nothing to download > Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found > Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 > No Match for argument kata-proxy-bin-1.9.2-7.1 > Nothing to download > Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 > No Match for argument kata-proxy-bin-1.9.2-7.1 > Nothing to download > Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-runtime-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 > No Match for argument kata-runtime-1.9.2-7.1 > Nothing to download > Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found > Looking for kata-runtime-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 > No Match for argument kata-runtime-1.9.2-7.1 > Nothing to download > Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found > Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 > No Match for argument kata-shim-1.9.2-7.1 > Nothing to download > Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found > Looking for kata-shim-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 > No Match for argument kata-shim-1.9.2-7.1 > Nothing to download > Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found > Error: kata-shim-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 > No Match for argument kata-shim-bin-1.9.2-7.1 > Nothing to download > Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 > No Match for argument kata-shim-bin-1.9.2-7.1 > Nothing to download > Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > > > > -----Original Message----- > From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] > Sent: Tuesday, January 14, 2020 12:40 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! > > Project: STX_build_master_master > Build #: 382 > Status: Still Failing > Timestamp: 20200114T172515Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: false > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 19:38:36 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 19:38:36 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 14 20:03:15 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 20:03:15 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> Message-ID: Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 20:05:16 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 20:05:16 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB154@ALA-MBD.corp.ad.wrs.com> Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 20:08:34 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 20:08:34 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 14 20:22:29 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 20:22:29 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> Message-ID: I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 20:23:43 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 20:23:43 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> It may not actually cause a build failure, now that I think about it… the download-mirror will see that the file exists and skip it. So it’s only because the file no longer existed the first time it tried to download that we had a failure. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:22 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Jan 14 20:32:27 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 14 Jan 2020 20:32:27 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Don – that takes care of #2 so we won’t see this issue again once Shuicheng updates the kata version and completes #1. Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:24 PM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs It may not actually cause a build failure, now that I think about it… the download-mirror will see that the file exists and skip it. So it’s only because the file no longer existed the first time it tried to download that we had a failure. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:22 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Jan 14 20:40:53 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 14 Jan 2020 20:40:53 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB20B@ALA-MBD.corp.ad.wrs.com> Reviews for reversions: https://review.opendev.org/#/q/status:open+projects:starlingx+branch:master+topic:kata From: Miller, Frank Sent: Tuesday, January 14, 2020 3:32 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thanks Don – that takes care of #2 so we won’t see this issue again once Shuicheng updates the kata version and completes #1. Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:24 PM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs It may not actually cause a build failure, now that I think about it… the download-mirror will see that the file exists and skip it. So it’s only because the file no longer existed the first time it tried to download that we had a failure. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:22 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Tue Jan 14 20:49:23 2020 From: scott.little at windriver.com (Scott Little) Date: Tue, 14 Jan 2020 15:49:23 -0500 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> Message-ID: <7934307f-558d-2f09-10d3-0e8206cef9c8@windriver.com> The new upstream repo should be introduced 24 hours before any lst files that reference content from that repo. That should give CENGN to mirror the new repo.  Once cengn has a copy of the version we want, it no longer matters if upstream changes the version. Scott On 2020-01-14 3:22 p.m., Miller, Frank wrote: > 2)Identify how we can prevent a build failure in the future when kata > puts out a new version and deletes the 1.9.3-8.1 version.  Is there a > way the StarlingX build or CENGN mirror can cache this version so we > can control when we move to a new version? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Jan 14 21:31:15 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 14 Jan 2020 21:31:15 +0000 Subject: [Starlingx-discuss] Test Hackathon Status Message-ID: A review to enable pylint on the unit tests folder has merged. https://review.opendev.org/#/c/702294/ Hopefully this will help make things a little easier for unit test authors finding issues in their code. I have also updated the test_pv API unit test class which is being referenced by the hackathon as a reference when writing new API unit tests. https://review.opendev.org/#/c/702537/ The intention here was to allow alternative configurations to be more easily API unit tested (through mixins) Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Tue Jan 14 23:31:23 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Tue, 14 Jan 2020 23:31:23 +0000 Subject: [Starlingx-discuss] hackathon status update Message-ID: <7B6A2AE64F40F245AE81F245059F0C3672F88932@ALA-MBD.corp.ad.wrs.com> Review to add (50) network api tests is up.. https://review.opendev.org/702300 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Jan 15 01:35:13 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 14 Jan 2020 17:35:13 -0800 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <7934307f-558d-2f09-10d3-0e8206cef9c8@windriver.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <7934307f-558d-2f09-10d3-0e8206cef9c8@windriver.com> Message-ID: <4fba2ff8-8ab9-c189-9009-7cd0ed56824b@linux.intel.com> On 1/14/20 12:49 PM, Scott Little wrote: > The new upstream repo should be introduced 24 hours before any lst files > that reference content from that repo. > What do you think of creating a new Zuul process to fetch or cause Cengn to fetch a current copy when the review is started via the Check gate? Sau! > That should give CENGN to mirror the new repo.  Once cengn has a copy of > the version we want, it no longer matters if upstream changes the version. > > Scott > > > On 2020-01-14 3:22 p.m., Miller, Frank wrote: >> 2)Identify how we can prevent a build failure in the future when kata >> puts out a new version and deletes the 1.9.3-8.1 version.  Is there a >> way the StarlingX build or CENGN mirror can cache this version so we >> can control when we move to a new version? > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From shuicheng.lin at intel.com Wed Jan 15 01:58:36 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 15 Jan 2020 01:58:36 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB20B@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB20B@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C76609137BB@SHSMSX105.ccr.corp.intel.com> Hi all, Really sorry for the trouble caused. I thought I have checked the rpm available last week, but it seems I missed. I will submit new patch later after verified the new kata rpm. Best Regards Shuicheng From: Penney, Don Sent: Wednesday, January 15, 2020 4:41 AM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Reviews for reversions: https://review.opendev.org/#/q/status:open+projects:starlingx+branch:master+topic:kata From: Miller, Frank Sent: Tuesday, January 14, 2020 3:32 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thanks Don – that takes care of #2 so we won’t see this issue again once Shuicheng updates the kata version and completes #1. Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:24 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs It may not actually cause a build failure, now that I think about it… the download-mirror will see that the file exists and skip it. So it’s only because the file no longer existed the first time it tried to download that we had a failure. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:22 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Wed Jan 15 09:06:22 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Wed, 15 Jan 2020 09:06:22 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status In-Reply-To: References: Message-ID: Test Hack-a-thon Kube_app status: Jan 15th Mingyuan, Austin, Shuicheng continue working on kube_app test cases. 1. For kube_app AppOperator class, 2 new commits out for review, 5 updated: New: - Add unit test for perform_app_upload in AppOperator(WIP) https://review.opendev.org/702597 - Add unit test for reapply in AppOperator https://review.opendev.org/702592 Updated: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit updated: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Tuesday, January 14, 2020 17:03 To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 14th Mingyuan, Austin, Shuicheng is now working on kube_app test cases. 1. For kube_app AppOperator class, 5 commits out for review: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit out for review: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Team will continue working on adding test cases/mock for public methods of underlining 2 classes. Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yi.c.wang at intel.com Wed Jan 15 12:05:16 2020 From: yi.c.wang at intel.com (Wang, Yi C) Date: Wed, 15 Jan 2020 12:05:16 +0000 Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon - Day 3 Message-ID: Updates of Day 3, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : Create test framework for python with stestr. * Merged #702327 to avoid py35 failure, added py27/py35 to gating list. 2. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py * Abandoned according to Bart's comment, that fm-rest-api/fm/fm/common/timeutils.py should be replaced by oslo.utils.timeutils. * Submitted https://bugs.launchpad.net/starlingx/+bug/1859737 to track this clean up task. * Submitted a patch https://review.opendev.org/702589 : Remove fm/common/timeutils. 3. https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py * Submitted https://bugs.launchpad.net/starlingx/+bug/1859738 to track the code clean up task to remove fm.common.utils.generate_uuid. * Submitted a patch https://review.opendev.org/702588 : Remove fm.common.utils.generate_uuid. 4. https://review.opendev.org/702362 : Add test cases for fm-rest-api common code * Fixed pep8 errors and rebased Thanks. Yi From: Wang, Yi C Sent: Tuesday, January 14, 2020 4:44 PM To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan ; An, Ran1 Subject: a summary of fault project task force for test hackathon Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Jan 15 12:51:00 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 15 Jan 2020 12:51:00 +0000 Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon In-Reply-To: <93814834B4855241994F290E959305C7531247D1@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7531247D1@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C753124B03@SHSMSX104.ccr.corp.intel.com> Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on fault project: 1. 6 commits updated after review https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP 2. 1 new commit submitted. https://review.opendev.org/#/c/702616/ Add unit tests for pci_device_update_by_host RPC EP Welcome more people join in this task force. We have 100+ RPC EP need to be done for unit test. Thanks. Zhipeng From: Liu, ZhipengS Sent: 2020年1月14日 21:09 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on fault project: 1. Created 7 tasks, https://storyboard.openstack.org/#!/story/2007082 2. Submitted 6 patches for review https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP Welcome more people join in this task force. We have 100+ RPC EP need to be done for unit test. Thanks. Zhipeng From: Wang, Yi C > Sent: 2020年1月14日 16:44 To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan >; An, Ran1 > Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 15 13:44:33 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Jan 2020 13:44:33 +0000 Subject: [Starlingx-discuss] Community Call (Jan 15, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B44FE6@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call coming up later today. We'll get an update on the Test Hack-a-thon that's underway [3], and reminder that we added a new standing topic to talk about CentOS 8. There are a couple of topics on the agenda [0] now, please feel free to add others. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200115T1500 [3] https://etherpad.openstack.org/p/stx-test-hackathon From Don.Penney at windriver.com Wed Jan 15 14:29:03 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 15 Jan 2020 14:29:03 +0000 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <9700A18779F35F49AF027300A49E7C76609137BB@SHSMSX105.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB20B@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76609137BB@SHSMSX105.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB6FE@ALA-MBD.corp.ad.wrs.com> No need to apologize. I think it was an easy thing to miss with a feature/update in development for a while like this. Maybe we should consider allowing merging the starlingx/tools LST file updates earlier in the future, or see if we can tie it to Zuul’s checks (as Saul has suggested in another email). From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, January 14, 2020 8:59 PM To: Penney, Don; Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Hi all, Really sorry for the trouble caused. I thought I have checked the rpm available last week, but it seems I missed. I will submit new patch later after verified the new kata rpm. Best Regards Shuicheng From: Penney, Don Sent: Wednesday, January 15, 2020 4:41 AM To: Miller, Frank ; Little, Scott ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Reviews for reversions: https://review.opendev.org/#/q/status:open+projects:starlingx+branch:master+topic:kata From: Miller, Frank Sent: Tuesday, January 14, 2020 3:32 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thanks Don – that takes care of #2 so we won’t see this issue again once Shuicheng updates the kata version and completes #1. Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:24 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs It may not actually cause a build failure, now that I think about it… the download-mirror will see that the file exists and skip it. So it’s only because the file no longer existed the first time it tried to download that we had a failure. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:22 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs I think the best 2 actions would be: 1) Revert the kata commit(s) and Shuicheng to rebase on the new kata version, run his own testing to ensure the new version did not break anything and then push the kata commits along with the new version of kata. 2) Identify how we can prevent a build failure in the future when kata puts out a new version and deletes the 1.9.3-8.1 version. Is there a way the StarlingX build or CENGN mirror can cache this version so we can control when we move to a new version? Frank From: Penney, Don Sent: Tuesday, January 14, 2020 3:09 PM To: Miller, Frank >; Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Option B here would be to revert the kata updates so the build can proceed, and ask for it to be rebased and retested: https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata From: Penney, Don Sent: Tuesday, January 14, 2020 3:05 PM To: Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Unfortunately, the upstream repo where we get the RPMs deletes the older versions when they release a new one, it seems. So our build will break any time they do so. From: Miller, Frank Sent: Tuesday, January 14, 2020 3:03 PM To: Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs Thank-you Don. Did Shuicheng not use a specific version of kata containers in his commits? Will your commit ensure that we are locked down on the 1.9.3-8.1 version? We need to make sure the next time kata releases a new version that we do not automatically pick up the new version. Going to a new version should be done in a controlled way where the feature owner does testing with the new version in his own environment before posting a commit to upversion to the newer version. Frank From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, January 14, 2020 2:39 PM To: Little, Scott >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs A review is posted to update the versions of the kata RPMs: https://review.opendev.org/702506 From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, January 14, 2020 2:23 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs 1) The rpms listed in the lst files are way out of date relative to what's available from the new kata repo. [ ] kata-containers-image-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 36M Details [ ] kata-ksm-throttler-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:33 5.9M Details [ ] kata-linux-container-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 8.3M Details [ ] kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm 10-Dec-2019 09:22 335K Details [ ] kata-proxy-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 2.4K Details [ ] kata-proxy-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:11 1.8M Details [ ] kata-runtime-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:39 20M Details [ ] kata-shim-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 2.4K Details [ ] kata-shim-bin-1.9.3-8.1.x86_64.rpm 10-Dec-2019 09:20 7.3M Details [ ] qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.5K Details [ ] qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 2.6M Details [ ] qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm 10-Dec-2019 09:29 3.0M Details [ ] qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.6K Details [ ] qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 2.5M Details [ ] qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm 10-Dec-2019 09:44 13M Details 2) The kata repo appears to be for SUSE, not CentOS. 3) The new repos url points to a location with a lot of extra 'stuff' when viewed from a browser. Not sure if yum is being served a cleaner view, but there is certainly the potential of confusing tools. IS there an alternate UR that would be cleaner? I recommend that the update (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted. There is likely other updates dependent on this that also need to be reverted. Scott On 2020-01-14 12:47 p.m., Penney, Don wrote: The latest CENGN build attempt fails on the RPM download stage, with the following errors: Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 No Match for argument kata-containers-image-1.9.2-7.1 Nothing to download Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 No Match for argument kata-ksm-throttler-1.9.2-7.1 Nothing to download Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 No Match for argument kata-linux-container-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 No Match for argument kata-linux-container-debug-4.19.75.54-7.1 Nothing to download Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 No Match for argument kata-proxy-1.9.2-7.1 Nothing to download Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 No Match for argument kata-proxy-bin-1.9.2-7.1 Nothing to download Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-runtime-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 No Match for argument kata-runtime-1.9.2-7.1 Nothing to download Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 No Match for argument kata-shim-1.9.2-7.1 Nothing to download Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 No Match for argument kata-shim-bin-1.9.2-7.1 Nothing to download Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found -----Original Message----- From: build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] Sent: Tuesday, January 14, 2020 12:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! Project: STX_build_master_master Build #: 382 Status: Still Failing Timestamp: 20200114T172515Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Jan 15 16:18:19 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 15 Jan 2020 11:18:19 -0500 Subject: [Starlingx-discuss] Important: stx-tools and build layering Message-ID: I'm having a far bit of trouble getting the build layering feature to lane due to churn in the lst files within the stx-tools.  Every time there is a change to the current monolithis lst files, I get merge conflicts, and have a fair bit of work to determine which layer or layers the changes belong in.  Then I must re-validate all layer builds in several working models.  It take a minimum of 2 days to complete that work. Any new lst change in that period breaks the final build process and invalidates the 2 days of work. I'd like to propose a temporary change to the review process for stx-tools so that lst file changes do not disrupt layered build testing. If an *stx-tool* change applies to the *master* branch, and includes a *changes to an lst* file, please review it but *DO NOT give it a workflow +1*.  I will give it the workflow +1 in the window between the test cycles of layered build. This will likely mean two merge windows per week. We should be able to resume normal reviews within two weeks. If there are no objects, please lets start now. Scott P.S. Please reach out to me if you think your review is being ignored. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 15 16:22:41 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Jan 2020 16:22:41 +0000 Subject: [Starlingx-discuss] Community Call (Jan 15, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B452C3@ALA-MBD.corp.ad.wrs.com> Update from today's call... - Standing Topics - Sanity - recent build failures - new Python module w/ hard dependency on Python 3 - this has been resolved, no follow up req'd - Kata rpm issues - AR: Build team / Saul to look into a good way of avoiding this for all types of builds - Reviews - Kris: https://review.opendev.org/#/c/687400 - per Saul, it's dependent on the layered build stuff - Scott will put a 'freeze' on the tools repo so he can get the layered build stuff in - will send a mail to the mailing list - Request for Help - Ansible bootstrap playbook error - - CentOS 8 - Saul, these are the areas we need to track... - https://etherpad.openstack.org/p/centos8-testing - this tracks the testing, overall status will be tracked here: https://etherpad.openstack.org/p/stx-distro-other - outstanding reviews - general build status - ISO generation, bootability & installation summary - status of dependencies - stuff that's traditionally upstream & not *yet* part of CentOS (e.g. Keystone, Barbican & their dependencies) - Austin - we can build *an* ISO now, there are ~700 rpms, this is bootable in a basic sense, but can't run Ansible yet - need a staged plan to copmlete - AR: Austin will send the view of what the staged plan will be for getting CentOS 8 sufficiently built & tested - AR: Austin will send the list of *missing* rpms - i.e. the list of rpms that are in CentOS 7 but not currently in CentOS 8 - Austin expressed some concern re: building the srpm for kernel-rt (as opposed to just picking it up from somewhere) - AR: Austin will share concerns about building this srpm, seek input from community - Austin also mentioned concerns about drbd - will add this to the staged plan - Test Hack-a-Thon Update - per Matt, there are ~18 open reviews across all the different areas - some have merged already - Al enabled PyLint for the tests folder - https://etherpad.openstack.org/p/stx-test-hackathon - Ceph Bluestore and software upgrade - Bruce - storage team to map out a plan for Ceph upgrade - Mid Cycle Meetup - date and location Mar 3rd Chandler AZ - Confirmed? - poll the TSC about their ability to attend - Flock Service Meetings - Dariush will look to start these soon - QCOW image - this will be added to the agenda for the Build call in 2 weeks time -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 15, 2020 8:45 AM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (Jan 15, 2020) Hi all, reminder of the Community call coming up later today. We'll get an update on the Test Hack-a-thon that's underway [3], and reminder that we added a new standing topic to talk about CentOS 8. There are a couple of topics on the agenda [0] now, please feel free to add others. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200115T1500 [3] https://etherpad.openstack.org/p/stx-test-hackathon From maria.g.perez.ibarra at intel.com Wed Jan 15 20:37:23 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 15 Jan 2020 20:37:23 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200115 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-15 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] AIO Simplex controller degraded https://bugs.launchpad.net/starlingx/+bug/1859859 Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Castelino at windriver.com Wed Jan 15 22:42:46 2020 From: Jessica.Castelino at windriver.com (Castelino, Jessica) Date: Wed, 15 Jan 2020 22:42:46 +0000 Subject: [Starlingx-discuss] Test Hackathon Status Message-ID: Hi, A review to add a py27 test case for NTP API has been posted. https://review.opendev.org/#/c/702759/ Kind Regards, Jessica -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Jan 15 23:25:50 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jan 2020 15:25:50 -0800 Subject: [Starlingx-discuss] Can cgcs-users/ibsh package be removed? Message-ID: <9d5035ef-9ba8-63de-8af6-b585b0f07bfa@linux.intel.com> Folks, As I was reviewing some of the CentOS-8 work, I saw the update to the cgcs-users package and looked into what it was. It seems to be a rename of an older locked down shell (2005). I searched through the repos and could only find it referenced in the integ repo for inclusion on the ISO. I don't see ibsh set as a shell or used any place. Is it time to retire this package? Thanks Sau! From sgw at linux.intel.com Wed Jan 15 23:35:55 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jan 2020 15:35:55 -0800 Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs Message-ID: Scott, Don: I am the following error which indeed seems to be the case, does rvmc belong in the centos_pkg_dirs if it does not have an RPM specfile? ERROR: build_dir (425): Neither srpm_path nor .spec file not found in '/localdisk/designer/swold/stx/cgcs-root/stx/metal/tools/rvmc/centos' $ ls metal/tools/rvmc/centos build_srpm.data docker rvmc.stable_docker_image I can file a launchpad as needed. Sau! From Don.Penney at windriver.com Wed Jan 15 23:39:12 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 15 Jan 2020 23:39:12 +0000 Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DBAB0@ALA-MBD.corp.ad.wrs.com> No, and it wouldn't need the build_srpm.data file, either. This is for a docker image, not on-host package. -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, January 15, 2020 6:36 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs Scott, Don: I am the following error which indeed seems to be the case, does rvmc belong in the centos_pkg_dirs if it does not have an RPM specfile? ERROR: build_dir (425): Neither srpm_path nor .spec file not found in '/localdisk/designer/swold/stx/cgcs-root/stx/metal/tools/rvmc/centos' $ ls metal/tools/rvmc/centos build_srpm.data docker rvmc.stable_docker_image I can file a launchpad as needed. Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Wed Jan 15 23:44:59 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 15 Jan 2020 15:44:59 -0800 Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DBAB0@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DBAB0@ALA-MBD.corp.ad.wrs.com> Message-ID: Don, Great, I will file a LP and deal with cleaning it up. Is there any checks for these kind of errors in the build system? Clearly this has been there for a bit and ignored. Maybe a SB is needed to add somekind of checking if that's possible. Sau! On 1/15/20 3:39 PM, Penney, Don wrote: > No, and it wouldn't need the build_srpm.data file, either. This is for a docker image, not on-host package. > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Wednesday, January 15, 2020 6:36 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs > > > Scott, Don: > > I am the following error which indeed seems to be the case, does rvmc > belong in the centos_pkg_dirs if it does not have an RPM specfile? > > ERROR: build_dir (425): Neither srpm_path nor .spec file not found in > '/localdisk/designer/swold/stx/cgcs-root/stx/metal/tools/rvmc/centos' > > $ ls metal/tools/rvmc/centos > build_srpm.data docker rvmc.stable_docker_image > > I can file a launchpad as needed. > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Don.Penney at windriver.com Thu Jan 16 00:16:11 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 16 Jan 2020 00:16:11 +0000 Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DBAB0@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DBAD0@ALA-MBD.corp.ad.wrs.com> Oddly, it's logged as an "ERROR", but has a "return 0" like it's a warning. So easy enough to make it a fatal error. And there's at least one other warning in the same function that looks like it should be a fatal, right after this one. https://opendev.org/starlingx/root/src/branch/master/build-tools/build-srpms-parallel#L437-L450 -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Wednesday, January 15, 2020 6:45 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs Don, Great, I will file a LP and deal with cleaning it up. Is there any checks for these kind of errors in the build system? Clearly this has been there for a bit and ignored. Maybe a SB is needed to add somekind of checking if that's possible. Sau! On 1/15/20 3:39 PM, Penney, Don wrote: > No, and it wouldn't need the build_srpm.data file, either. This is for a docker image, not on-host package. > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Wednesday, January 15, 2020 6:36 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] RVMC in meta/centos_pkg_dirs > > > Scott, Don: > > I am the following error which indeed seems to be the case, does rvmc > belong in the centos_pkg_dirs if it does not have an RPM specfile? > > ERROR: build_dir (425): Neither srpm_path nor .spec file not found in > '/localdisk/designer/swold/stx/cgcs-root/stx/metal/tools/rvmc/centos' > > $ ls metal/tools/rvmc/centos > build_srpm.data docker rvmc.stable_docker_image > > I can file a launchpad as needed. > > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kristal.dale at intel.com Thu Jan 16 00:42:20 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 16 Jan 2020 00:42:20 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-01-15 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-01-15 * All -- reviews in progress and recent merges -- https://review.opendev.org/#/q/project:starlingx/docs * 4 merged since last week, including bug fixes * Open: https://review.opendev.org/#/q/project:starlingx/docs+status:open * Mergable: https://review.opendev.org/#/q/project:starlingx/docs+status:open+is:mergeable ? Needs +2 and +Workflow: https://review.opendev.org/#/c/608214/ ? Needs +2: https://review.opendev.org/#/c/702565/ - revise this to not use release specific URLs (KRIS - Done) ? Stuck: https://review.opendev.org/#/c/701474/ - email openstack-infra at lists.openstack.org for suport (KRIS) * All -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * All -- Ongoing tasks: * Kris -- misc doc clean up * Kris -- STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Ask author to join build meeting in 2 weeks. If not possible (due to time diff), set up separate meeting with Scott Little/Saul Wold. * Mike/Linja/Huifeng/David -- adding video to StarlingX.io -- Video posted: https://youtu.be/6IhWPaRD7Po ? Final location? Huifeng suggests adding to https://docs.starlingx.io/operations/tsn.html instead of the Wiki (https://wiki.openstack.org/wiki/StarlingX/Networking/TSN , which is supposed to be Outdated) * Final location: Add to TSN page in docs. See if we can embed the vid. If not, use a simple text link. (KRIS) * Mike -- Adding article to StarlingX.io -- In progress https://01.org/blogs/vmrod25/2019/accelerating-ai-workloads-starlingx-edge-servers-using-x86-technology ? Lets do this as a blog post: https://www.starlingx.io/blog/ ? Need to write a summary (Mike), then link to article. Submit as a PR to site (Kris). ? Target - first part of January * Bruce -- Improve www.starlingx.io -- https://storyboard.openstack.org/#!/story/2007029 --- CLOSE this out for now (KRIS - Done) ? Get started link will be an easy change - make PR as soon as ready. ? Note that the marketing call handles larger changes related to website (graphics, design, etc). https://wiki.openstack.org/wiki/Starlingx/Meetings#8am_Pacific_-_Community_Marketing_Planning_Call ? Put together requirements together, then attend the marketing call (coordinate with Ildiko) (Kris will coord requirements) * Planning: * Open stories tagged R2: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.docs&tags=stx.2.0 ? https://storyboard.openstack.org/#!/story/2004877 - 1 open task for stx-ha (Abraham) - status? Check with Abraham, and close out (KRIS - DONE) ? https://storyboard.openstack.org/#!/story/2004737 - 1 open task for stx-clients (Kris) - I found that earlier updates have a bug in them. All should be updated. * Remaining tasks from R3: Suggest we move back into backlog for reprioritization. https://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 * Suggest we ID near term (opportunistic) and R4 release work * Prio 1: Must have for R4 release ? Are these items confirmed? https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 * Prio 2: Should have for R4 release * Prio 3: Nice to have * Opportunistic: ? Actionable items from backlog, pick off the top of list https://etherpad.openstack.org/p/stx-docs-backlog ? Need to review and decide actionable/things to add to Storyboard * Transition plan: https://etherpad.openstack.org/p/docs-transition-plan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jan 16 09:13:55 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Jan 2020 10:13:55 +0100 Subject: [Starlingx-discuss] Ada Cabrales resigning to the testing team In-Reply-To: References: Message-ID: <73572572-3198-4C96-AFE1-93B6975AF3C2@gmail.com> Hi Ada, It was great to have you being part of the community, I’m sorry to hear that you will not have bandwidth to keep on participating. Thank you for all the great work you have been doing on QA and testing and leading the team in these key areas. Without your hard work we couldn’t have put out three releases of the project in the course of one and a half years. I wish you all the best in your new role and I hope you might be able to contribute to StarlingX again in the future. Thanks and Best Regards, Ildikó > On Jan 10, 2020, at 00:25, Cabrales, Ada wrote: > > Hello StarlingX Community > > Due to organizational changes happening internally at my company, I must resign my position as PL and member of the stx-test team. This was previously announced in the past community meeting (on 01/08/2020). > > Bruce Jones will be able to provide more information on who will be taking the testing responsibilities soon. Stay tuned. > > It has been an honor to work with all of you. Thanks for the learnings. > > Ada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu Jan 16 09:17:36 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Jan 2020 10:17:36 +0100 Subject: [Starlingx-discuss] Marcela Rosales resigning MultiOS team In-Reply-To: <2781C163-D62A-4818-B4DF-C82B213E6B1B@intel.com> References: <2781C163-D62A-4818-B4DF-C82B213E6B1B@intel.com> Message-ID: <3D7A53D5-5E5F-4AF3-A4AD-A7820631DCC5@gmail.com> Hi Marcela, It was great to have you in the StarlingX community and I’m sorry to see you depart. Thank you for all the great work you have been doing in the project and for taking on the leadership role in a very important area such as MultiOS. I wish you all the best in your new role and I hope you might be able to contribute to StarlingX again in the future. Thanks and Best Regards, Ildikó > On Jan 13, 2020, at 23:03, Rosales Jimenez, Marcela A wrote: > > Hi team, > > I am resigning my position as PL and member for MultiOS team due to organizational changes within Intel. MultiOS team or TSC should nominate a replacement if required. > > It was a pleasure working with you! > > Marcela > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu Jan 16 09:41:55 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Jan 2020 10:41:55 +0100 Subject: [Starlingx-discuss] Filling in leadership roles that opened up between elections Message-ID: Hi, As we have a few people who don’t have the capacity anymore to contribute to the project and are also holding leadership positions we need to think of how to resolve this case and fill in the open positions. I wanted to bring up the OpenStack project as example to find a viable way forward. As a practice within project teams in OpenStack there are two ways forward they usually take depending on the circumstances: 1. Delegating the departing PTL's responsibilities to a successor for the rest of the term 2. Call for a special election to find a successor The departing PTL is encouraged to choose from options #1 or #2. In case the remaining term is short the usual practice is option #1 while when the remaining time is longer they hold an interim election for the project team that elects a new PTL for the remaining term. When the case remains unresolved by the departing PTL the TC has the responsibility to act where they also choose between options #1 and #2 with taking similar considerations as mentioned above. I think it would be beneficial to consider adopting a similar process for the StarlingX community as well. In the specific cases we have currently I would suggest holding elections for the affected teams as more than half of the terms are still left till the next PL/TL elections. I will bring this topic up with the TSC group and would like to get feedback from the community as well. Thanks and Best Regards, Ildikó From dorian_lau at 126.com Thu Jan 16 10:12:43 2020 From: dorian_lau at 126.com (Daolin Liu) Date: Thu, 16 Jan 2020 18:12:43 +0800 (CST) Subject: [Starlingx-discuss] Rejected: Total allocated memory exceeds the total memory of controller-0 numa node 0 Message-ID: <5899523.f76e.16fadd7432c.Coremail.dorian_lau@126.com> Hi, I'm installing all-in-one environment, and my PC has only 8G memory, so I assign 4G for the simplex-controller-0. After I configure controller-0 and run "system host-unlock controller-0" command, I got below error: Rejected: Total allocated memory exceeds the total memory of controller-0 numa node 0 Probably the controller-0 memory is 4G, but some default parameters in configuration is more than 4G. Can you tell me how to change it, since I don't want to change my physical PC. Thanks, Daolin -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Thu Jan 16 12:38:02 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 16 Jan 2020 12:38:02 +0000 Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon In-Reply-To: <93814834B4855241994F290E959305C753124B03@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7531247D1@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C753124B03@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C753124E03@SHSMSX104.ccr.corp.intel.com> Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on below task: https://storyboard.openstack.org/#!/story/2007082 Task 38039 Add unit tests for all RPC entry points in ConductorManager class in sysinv/conductor/manager.py 1. 7 commits updated after review https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP https://review.opendev.org/#/c/702616/ Add unit tests for pci_device_update_by_host RPC EP 2. 1 new commit submitted. https://review.opendev.org/#/c/702833/ Add unit tests for inumas_update_by_ihost RPC EP. Welcome more people join in this task force. We have 100+ RPC EP need to be done for unit test. Thanks. Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Thu Jan 16 12:40:29 2020 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 16 Jan 2020 12:40:29 +0000 Subject: [Starlingx-discuss] Can cgcs-users/ibsh package be removed? In-Reply-To: <9d5035ef-9ba8-63de-8af6-b585b0f07bfa@linux.intel.com> References: <9d5035ef-9ba8-63de-8af6-b585b0f07bfa@linux.intel.com> Message-ID: I'm not aware of ibsh still being used. It was previously replaced by lshell for restricted shells which has also been removed from the system. Regards, Matt On 2020-01-15, 6:27 PM, "Saul Wold" wrote: Folks, As I was reviewing some of the CentOS-8 work, I saw the update to the cgcs-users package and looked into what it was. It seems to be a rename of an older locked down shell (2005). I searched through the repos and could only find it referenced in the integ repo for inclusion on the ISO. I don't see ibsh set as a shell or used any place. Is it time to retire this package? Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mingyuan.qi at intel.com Thu Jan 16 13:53:35 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 16 Jan 2020 13:53:35 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status In-Reply-To: References: Message-ID: Test Hack-a-thon Kube_app status: Jan 16th Mingyuan, Austin, Shuicheng continue working on kube_app test cases kube_app AppOperator: 4 patches in review(1 WIP), 3 merged: Review: - Add unit test for perform_app_upload in AppOperator(WIP) https://review.opendev.org/702597 - Add unit test for reapply in AppOperator https://review.opendev.org/702592 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 Merged: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 kube_app DockerHelper: 1 in review(WIP) - Add test class for kube_app DockerHelper(WIP) https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Wednesday, January 15, 2020 17:06 To: Qi, Mingyuan ; Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 15th Mingyuan, Austin, Shuicheng continue working on kube_app test cases. 1. For kube_app AppOperator class, 2 new commits out for review, 5 updated: New: - Add unit test for perform_app_upload in AppOperator(WIP) https://review.opendev.org/702597 - Add unit test for reapply in AppOperator https://review.opendev.org/702592 Updated: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit updated: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Tuesday, January 14, 2020 17:03 To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 14th Mingyuan, Austin, Shuicheng is now working on kube_app test cases. 1. For kube_app AppOperator class, 5 commits out for review: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit out for review: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Team will continue working on adding test cases/mock for public methods of underlining 2 classes. Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yi.c.wang at intel.com Thu Jan 16 14:47:46 2020 From: yi.c.wang at intel.com (Wang, Yi C) Date: Thu, 16 Jan 2020 14:47:46 +0000 Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon - Day 4 Message-ID: Updates of Day 4, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : Updated according to Bart's comment. 2. https://review.opendev.org/702347 : Got +2, pending on #702175. 3. https://review.opendev.org/702588 : Updated according to Bart's comment. Under testing. 4. https://review.opendev.org/702589 : Under testing. 5. submitted a new patch https://review.opendev.org/#/c/702823/, fake database Thanks. Yi From: Wang, Yi C Sent: Wednesday, January 15, 2020 8:05 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Chen, Yan ; An, Ran1 Subject: a summary of fault project task force for test hackathon - Day 3 Updates of Day 3, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : Create test framework for python with stestr. * Merged #702327 to avoid py35 failure, added py27/py35 to gating list. 2. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py * Abandoned according to Bart's comment, that fm-rest-api/fm/fm/common/timeutils.py should be replaced by oslo.utils.timeutils. * Submitted https://bugs.launchpad.net/starlingx/+bug/1859737 to track this clean up task. * Submitted a patch https://review.opendev.org/702589 : Remove fm/common/timeutils. 3. https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py * Submitted https://bugs.launchpad.net/starlingx/+bug/1859738 to track the code clean up task to remove fm.common.utils.generate_uuid. * Submitted a patch https://review.opendev.org/702588 : Remove fm.common.utils.generate_uuid. 4. https://review.opendev.org/702362 : Add test cases for fm-rest-api common code * Fixed pep8 errors and rebased Thanks. Yi From: Wang, Yi C Sent: Tuesday, January 14, 2020 4:44 PM To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan >; An, Ran1 > Subject: a summary of fault project task force for test hackathon Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 16 15:22:25 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 16 Jan 2020 15:22:25 +0000 Subject: [Starlingx-discuss] question about ceph or storage In-Reply-To: <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85628DE96@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747683@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85628F3EA@CDSMSX102.ccr.corp.intel.com>, <56829C2A36C2E542B0CCB9854828E4D85628F402@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747C99@ALA-MBD.corp.ad.wrs.com>, <56829C2A36C2E542B0CCB9854828E4D85629833F@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> Hi Ovidiu & Bob Another question. I found starlingx save ceph cluster's client.admin key in kube secret "ceph-pool-kube-rbd". I wonder when starlingx create this secret, read ceph cluster keyring and save to secret. In bootstrap? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Poncea, Ovidiu Sent: Monday, December 30, 2019 11:40 PM To: Chen, Haochuan Z ; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage I don't know if it's out of date :) it may just need to be retested if it wasn't for current release. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 30, 2019 3:51 PM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Thanks Ovidiu! If "-c" is out of date, what about remove it later. Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 4:43 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, It was used in the previous release for connecting a deployment (especially an openstack one) to an external Ceph cluster. I don't know what is the feature testing status for current release. Ovidiu ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 23, 2019 9:18 AM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Sorry to disturb! Merry Christmas to all StarlingX member! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 23, 2019 3:17 PM To: Poncea, Ovidiu >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Ovidiu For "system storage-backend-add -c ", user could deploy another ceph cluster, and add as storage backend, correctly. And this is this command's intention, correct? Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Wednesday, December 18, 2019 7:47 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, see inline. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Tuesday, December 17, 2019 10:46 AM To: Church, Robert; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: question about ceph or storage Hi Bob & Ovidiu Some question about ceph or storage. 1, What's storage tier and storage profile? What's the [Ovi] Storage tiering is equivalent with this: https://ceph.io/planet/deploying-ceph-with-storage-tiering/ . [Ovi] Profiles are managed by system storprofile-* and system host-apply-profile and are used to copy configuration from one node to another, identical node on initial provisioning. These profiles are only in system inventory, there is no Ceph equivalent. 2, why for duplex it request such puppet class dependency in ceph.pp? Is this request make all drbd config before class ceph? [Ovi] ceph-mon in AIO-DX is DRBD managed and it has a single, floating, monitor. On DX, when you swact, the monitor is stopped on the active controller and started on the standby controller. Drbd::Resource <| |> -> Class['::ceph'] And flag file ".node_ceph_configured", to inform drbd make init setup before ceph config? 3, To launch ceph-mon, create a logical volume "ceph-mon-lv" and mount to /var/lib/ceph/mon, not directly mkdir "/var/lib/ceph/mon" for ceph-mon [Ovi] Ceph monitors have their own logical volume. They are managed through "system ceph-mon*" commands. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, December 11, 2019 4:46 PM To: Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu >; Qi, Mingyuan > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob Some question, what's storage tier and storage profile? As you said, we no longer manage pool and pg num, is this also unnecessary and we should remove it? BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Wednesday, December 4, 2019 12:09 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor See inline... From: "Chen, Haochuan Z" > Date: Tuesday, December 3, 2019 at 2:18 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob 1, we could update default pg num in sysinv/helm/rbd_provisioner.py. But when platform-integ-apps applied, maybe user has not add osded, so the default pg num is still for user reference. And for user override, I think it should add in ceph-pool-audit, stx-platform-helm/helm-charts/ceph-pools-audit/templates/job-ceph-pools-audit.yaml. but pg num update will make rebalance which cause management network jam. [RTC] For a more robust solution, consider the following: * We can update _met_app_apply_prerequisites () in sysinv/conductor.py for platform-integ-apps to require OSDs to be provisioned prior to applying the application. This will ensure an accurate OSD view when the application is initially applied. * The provisioner system overrides (in sysinv/helm/rbd_provisioner.py) should have the ability to calculate and set an optimal PG number to avoid generating a warning. * The rbd provisioner chart should also support setting a new chunk size (if greater than the existing size) to update the PG num. This will support user PG updates from the helm-overrides API. * I think it's potentially a good idea for ceph-pool-audit to support adjusting the PG numbers as well but this is tricky as I don't think we can reduce PG_num in Mimic without creating a new pool and copying the contents (pg_autoscaling is added in Nautilis). This audit code would have to be very specific in adjusting the PG num as installing applications that add additional pools will change the PG_num distribution. 2, the above case is only for system application. Any more alarm for PG number, request user should manage. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Tuesday, December 3, 2019 10:34 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor Hi Martin, In STX 1.0, we ran bare-metal openstack services for which we created and managed specific ceph storage pools for glance, cinder, nova, and swift. In this environment, we managed their creation and parameters (PGs and quotas) as the cluster scaled up. With the move to containerizing the openstack services in STX 2.0, pool creation is now driven mostly by helm charts packaged into an application (radosgw pools are the exception). Since we don't know what additional application(s) will be deployed and what pools may be created, we are currently longer managing pools as in STX 1.0. These related functions in sysinv/conductor/ceph.py are remaining from STX 1.0 and need to be removed and/or repurposed to meet any new requirements. I took a look at the LP logs and it looks like we only have a single application applied: platform-integ-apps. This currently results in a single pool for 6 OSDs cluster: id: 6231df84-33be-4aa4-82ea-7408e0f2421c health: HEALTH_WARN too few PGs per OSD (21 < min 30) services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 6 osds: 6 up, 6 in data: pools: 1 pools, 64 pgs objects: 0 objects, 0 B usage: 645 MiB used, 5.4 TiB / 5.4 TiB avail pgs: 64 active+clean Since every installation will install platform-integ-apps, I think we should do the following: 1. Update the chunk_size calculation in sysinv/helm/rbd_provisioner.py to be dynamically calculated based on the number OSDs provisioned in the cluster. As this may be the only pool created, it should meet the minimum size characteristics to avoid a ceph warning. 2. Update the rbd-provisioner helm chart to support explicitly setting the pg_num based on the chunk size. Do this to allow setting a user override for the chunk size so that we can re-apply platform-integ-apps and explicitly set new values. Regards, Bob From: "Chen, Haochuan Z" > Date: Monday, December 2, 2019 at 1:15 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: ceph ops enabling in sysinv-conductor Hi Bob I find some many function in sysinv-conductor/ceph.py, which could manage ceph cluster, such as create/delete/configure pool, audit pg etc. But why these function is not enabled? Or plan to request user to manage ceph cluster, such as create pool and configure pg num? Now I checked this issue, pg too few, as user maybe deploy few osd, which make alarm. So for such issue, request user to decide correct pg num or user could ignore? https://bugs.launchpad.net/starlingx/+bug/1844164 BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Thu Jan 16 15:44:17 2020 From: Robert.Church at windriver.com (Church, Robert) Date: Thu, 16 Jan 2020 15:44:17 +0000 Subject: [Starlingx-discuss] question about ceph or storage In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85628DE96@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747683@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85628F3EA@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85628F402@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747C99@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629833F@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> Message-ID: <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> Hi Martin, The rbd provisioner chart creates the secret along with the pool when it’s first installed in the cluster via platform-integ-apps. Regards, Bob From: "Chen, Haochuan Z" Date: Thursday, January 16, 2020 at 9:22 AM To: Ovidiu Poncea , Robert Church Cc: "'starlingx-discuss at lists.starlingx.io'" Subject: RE: question about ceph or storage Hi Ovidiu & Bob Another question. I found starlingx save ceph cluster’s client.admin key in kube secret “ceph-pool-kube-rbd”. I wonder when starlingx create this secret, read ceph cluster keyring and save to secret. In bootstrap? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Poncea, Ovidiu Sent: Monday, December 30, 2019 11:40 PM To: Chen, Haochuan Z ; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage I don't know if it's out of date :) it may just need to be retested if it wasn't for current release. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 30, 2019 3:51 PM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Thanks Ovidiu! If “-c” is out of date, what about remove it later. Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 4:43 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, It was used in the previous release for connecting a deployment (especially an openstack one) to an external Ceph cluster. I don't know what is the feature testing status for current release. Ovidiu ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 23, 2019 9:18 AM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Sorry to disturb! Merry Christmas to all StarlingX member! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 23, 2019 3:17 PM To: Poncea, Ovidiu >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Ovidiu For “system storage-backend-add -c ”, user could deploy another ceph cluster, and add as storage backend, correctly. And this is this command’s intention, correct? Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Wednesday, December 18, 2019 7:47 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, see inline. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Tuesday, December 17, 2019 10:46 AM To: Church, Robert; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: question about ceph or storage Hi Bob & Ovidiu Some question about ceph or storage. 1, What’s storage tier and storage profile? What’s the [Ovi] Storage tiering is equivalent with this: https://ceph.io/planet/deploying-ceph-with-storage-tiering/ . [Ovi] Profiles are managed by system storprofile-* and system host-apply-profile and are used to copy configuration from one node to another, identical node on initial provisioning. These profiles are only in system inventory, there is no Ceph equivalent. 2, why for duplex it request such puppet class dependency in ceph.pp? Is this request make all drbd config before class ceph? [Ovi] ceph-mon in AIO-DX is DRBD managed and it has a single, floating, monitor. On DX, when you swact, the monitor is stopped on the active controller and started on the standby controller. Drbd::Resource <| |> -> Class['::ceph'] And flag file “.node_ceph_configured”, to inform drbd make init setup before ceph config? 3, To launch ceph-mon, create a logical volume “ceph-mon-lv” and mount to /var/lib/ceph/mon, not directly mkdir “/var/lib/ceph/mon” for ceph-mon [Ovi] Ceph monitors have their own logical volume. They are managed through "system ceph-mon*" commands. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, December 11, 2019 4:46 PM To: Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu >; Qi, Mingyuan > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob Some question, what’s storage tier and storage profile? As you said, we no longer manage pool and pg num, is this also unnecessary and we should remove it? BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Wednesday, December 4, 2019 12:09 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor See inline… From: "Chen, Haochuan Z" > Date: Tuesday, December 3, 2019 at 2:18 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob 1, we could update default pg num in sysinv/helm/rbd_provisioner.py. But when platform-integ-apps applied, maybe user has not add osded, so the default pg num is still for user reference. And for user override, I think it should add in ceph-pool-audit, stx-platform-helm/helm-charts/ceph-pools-audit/templates/job-ceph-pools-audit.yaml. but pg num update will make rebalance which cause management network jam. [RTC] For a more robust solution, consider the following: • We can update _met_app_apply_prerequisites () in sysinv/conductor.py for platform-integ-apps to require OSDs to be provisioned prior to applying the application. This will ensure an accurate OSD view when the application is initially applied. • The provisioner system overrides (in sysinv/helm/rbd_provisioner.py) should have the ability to calculate and set an optimal PG number to avoid generating a warning. • The rbd provisioner chart should also support setting a new chunk size (if greater than the existing size) to update the PG num. This will support user PG updates from the helm-overrides API. • I think it’s potentially a good idea for ceph-pool-audit to support adjusting the PG numbers as well but this is tricky as I don’t think we can reduce PG_num in Mimic without creating a new pool and copying the contents (pg_autoscaling is added in Nautilis). This audit code would have to be very specific in adjusting the PG num as installing applications that add additional pools will change the PG_num distribution. 2, the above case is only for system application. Any more alarm for PG number, request user should manage. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Tuesday, December 3, 2019 10:34 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor Hi Martin, In STX 1.0, we ran bare-metal openstack services for which we created and managed specific ceph storage pools for glance, cinder, nova, and swift. In this environment, we managed their creation and parameters (PGs and quotas) as the cluster scaled up. With the move to containerizing the openstack services in STX 2.0, pool creation is now driven mostly by helm charts packaged into an application (radosgw pools are the exception). Since we don’t know what additional application(s) will be deployed and what pools may be created, we are currently longer managing pools as in STX 1.0. These related functions in sysinv/conductor/ceph.py are remaining from STX 1.0 and need to be removed and/or repurposed to meet any new requirements. I took a look at the LP logs and it looks like we only have a single application applied: platform-integ-apps. This currently results in a single pool for 6 OSDs cluster: id: 6231df84-33be-4aa4-82ea-7408e0f2421c health: HEALTH_WARN too few PGs per OSD (21 < min 30) services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 6 osds: 6 up, 6 in data: pools: 1 pools, 64 pgs objects: 0 objects, 0 B usage: 645 MiB used, 5.4 TiB / 5.4 TiB avail pgs: 64 active+clean Since every installation will install platform-integ-apps, I think we should do the following: 1. Update the chunk_size calculation in sysinv/helm/rbd_provisioner.py to be dynamically calculated based on the number OSDs provisioned in the cluster. As this may be the only pool created, it should meet the minimum size characteristics to avoid a ceph warning. 2. Update the rbd-provisioner helm chart to support explicitly setting the pg_num based on the chunk size. Do this to allow setting a user override for the chunk size so that we can re-apply platform-integ-apps and explicitly set new values. Regards, Bob From: "Chen, Haochuan Z" > Date: Monday, December 2, 2019 at 1:15 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: ceph ops enabling in sysinv-conductor Hi Bob I find some many function in sysinv-conductor/ceph.py, which could manage ceph cluster, such as create/delete/configure pool, audit pg etc. But why these function is not enabled? Or plan to request user to manage ceph cluster, such as create pool and configure pg num? Now I checked this issue, pg too few, as user maybe deploy few osd, which make alarm. So for such issue, request user to decide correct pg num or user could ignore? https://bugs.launchpad.net/starlingx/+bug/1844164 BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Jan 16 15:46:33 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 16 Jan 2020 15:46:33 +0000 Subject: [Starlingx-discuss] question about ceph or storage In-Reply-To: <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D85628DE96@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747683@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85628F3EA@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85628F402@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747C99@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629833F@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85629BBEE@CDSMSX102.ccr.corp.intel.com> Great thanks, Bob! Martin, Chen IOTG, Software Engineer 021-61164330 From: Church, Robert Sent: Thursday, January 16, 2020 11:44 PM To: Chen, Haochuan Z ; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: question about ceph or storage Hi Martin, The rbd provisioner chart creates the secret along with the pool when it’s first installed in the cluster via platform-integ-apps. Regards, Bob From: "Chen, Haochuan Z" > Date: Thursday, January 16, 2020 at 9:22 AM To: Ovidiu Poncea >, Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" > Subject: RE: question about ceph or storage Hi Ovidiu & Bob Another question. I found starlingx save ceph cluster’s client.admin key in kube secret “ceph-pool-kube-rbd”. I wonder when starlingx create this secret, read ceph cluster keyring and save to secret. In bootstrap? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 11:40 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage I don't know if it's out of date :) it may just need to be retested if it wasn't for current release. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 30, 2019 3:51 PM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Thanks Ovidiu! If “-c” is out of date, what about remove it later. Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 4:43 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, It was used in the previous release for connecting a deployment (especially an openstack one) to an external Ceph cluster. I don't know what is the feature testing status for current release. Ovidiu ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 23, 2019 9:18 AM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Sorry to disturb! Merry Christmas to all StarlingX member! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 23, 2019 3:17 PM To: Poncea, Ovidiu >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Ovidiu For “system storage-backend-add -c ”, user could deploy another ceph cluster, and add as storage backend, correctly. And this is this command’s intention, correct? Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Wednesday, December 18, 2019 7:47 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, see inline. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Tuesday, December 17, 2019 10:46 AM To: Church, Robert; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: question about ceph or storage Hi Bob & Ovidiu Some question about ceph or storage. 1, What’s storage tier and storage profile? What’s the [Ovi] Storage tiering is equivalent with this: https://ceph.io/planet/deploying-ceph-with-storage-tiering/ . [Ovi] Profiles are managed by system storprofile-* and system host-apply-profile and are used to copy configuration from one node to another, identical node on initial provisioning. These profiles are only in system inventory, there is no Ceph equivalent. 2, why for duplex it request such puppet class dependency in ceph.pp? Is this request make all drbd config before class ceph? [Ovi] ceph-mon in AIO-DX is DRBD managed and it has a single, floating, monitor. On DX, when you swact, the monitor is stopped on the active controller and started on the standby controller. Drbd::Resource <| |> -> Class['::ceph'] And flag file “.node_ceph_configured”, to inform drbd make init setup before ceph config? 3, To launch ceph-mon, create a logical volume “ceph-mon-lv” and mount to /var/lib/ceph/mon, not directly mkdir “/var/lib/ceph/mon” for ceph-mon [Ovi] Ceph monitors have their own logical volume. They are managed through "system ceph-mon*" commands. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, December 11, 2019 4:46 PM To: Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu >; Qi, Mingyuan > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob Some question, what’s storage tier and storage profile? As you said, we no longer manage pool and pg num, is this also unnecessary and we should remove it? BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Wednesday, December 4, 2019 12:09 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor See inline… From: "Chen, Haochuan Z" > Date: Tuesday, December 3, 2019 at 2:18 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob 1, we could update default pg num in sysinv/helm/rbd_provisioner.py. But when platform-integ-apps applied, maybe user has not add osded, so the default pg num is still for user reference. And for user override, I think it should add in ceph-pool-audit, stx-platform-helm/helm-charts/ceph-pools-audit/templates/job-ceph-pools-audit.yaml. but pg num update will make rebalance which cause management network jam. [RTC] For a more robust solution, consider the following: • We can update _met_app_apply_prerequisites () in sysinv/conductor.py for platform-integ-apps to require OSDs to be provisioned prior to applying the application. This will ensure an accurate OSD view when the application is initially applied. • The provisioner system overrides (in sysinv/helm/rbd_provisioner.py) should have the ability to calculate and set an optimal PG number to avoid generating a warning. • The rbd provisioner chart should also support setting a new chunk size (if greater than the existing size) to update the PG num. This will support user PG updates from the helm-overrides API. • I think it’s potentially a good idea for ceph-pool-audit to support adjusting the PG numbers as well but this is tricky as I don’t think we can reduce PG_num in Mimic without creating a new pool and copying the contents (pg_autoscaling is added in Nautilis). This audit code would have to be very specific in adjusting the PG num as installing applications that add additional pools will change the PG_num distribution. 2, the above case is only for system application. Any more alarm for PG number, request user should manage. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Tuesday, December 3, 2019 10:34 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor Hi Martin, In STX 1.0, we ran bare-metal openstack services for which we created and managed specific ceph storage pools for glance, cinder, nova, and swift. In this environment, we managed their creation and parameters (PGs and quotas) as the cluster scaled up. With the move to containerizing the openstack services in STX 2.0, pool creation is now driven mostly by helm charts packaged into an application (radosgw pools are the exception). Since we don’t know what additional application(s) will be deployed and what pools may be created, we are currently longer managing pools as in STX 1.0. These related functions in sysinv/conductor/ceph.py are remaining from STX 1.0 and need to be removed and/or repurposed to meet any new requirements. I took a look at the LP logs and it looks like we only have a single application applied: platform-integ-apps. This currently results in a single pool for 6 OSDs cluster: id: 6231df84-33be-4aa4-82ea-7408e0f2421c health: HEALTH_WARN too few PGs per OSD (21 < min 30) services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 6 osds: 6 up, 6 in data: pools: 1 pools, 64 pgs objects: 0 objects, 0 B usage: 645 MiB used, 5.4 TiB / 5.4 TiB avail pgs: 64 active+clean Since every installation will install platform-integ-apps, I think we should do the following: 1. Update the chunk_size calculation in sysinv/helm/rbd_provisioner.py to be dynamically calculated based on the number OSDs provisioned in the cluster. As this may be the only pool created, it should meet the minimum size characteristics to avoid a ceph warning. 2. Update the rbd-provisioner helm chart to support explicitly setting the pg_num based on the chunk size. Do this to allow setting a user override for the chunk size so that we can re-apply platform-integ-apps and explicitly set new values. Regards, Bob From: "Chen, Haochuan Z" > Date: Monday, December 2, 2019 at 1:15 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: ceph ops enabling in sysinv-conductor Hi Bob I find some many function in sysinv-conductor/ceph.py, which could manage ceph cluster, such as create/delete/configure pool, audit pg etc. But why these function is not enabled? Or plan to request user to manage ceph cluster, such as create pool and configure pg num? Now I checked this issue, pg too few, as user maybe deploy few osd, which make alarm. So for such issue, request user to decide correct pg num or user could ignore? https://bugs.launchpad.net/starlingx/+bug/1844164 BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tee.Ngo at windriver.com Thu Jan 16 15:50:17 2020 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Thu, 16 Jan 2020 15:50:17 +0000 Subject: [Starlingx-discuss] Rejected: Total allocated memory exceeds the total memory of controller-0 numa node 0 In-Reply-To: <5899523.f76e.16fadd7432c.Coremail.dorian_lau@126.com> References: <5899523.f76e.16fadd7432c.Coremail.dorian_lau@126.com> Message-ID: <80ED4CE81E3D8F4099306648E95DAFE453AFEA2B@ALA-MBD.corp.ad.wrs.com> Minimum and also the default memory for All-in-one is 8GB. You cannot unlock the host with less than this amount. If you plan to launch application pods, you will need 8GB + whatever memory your application(s) requires. Tee From: Daolin Liu [mailto:dorian_lau at 126.com] Sent: January-16-20 5:13 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Rejected: Total allocated memory exceeds the total memory of controller-0 numa node 0 Hi, I'm installing all-in-one environment, and my PC has only 8G memory, so I assign 4G for the simplex-controller-0. After I configure controller-0 and run "system host-unlock controller-0" command, I got below error: Rejected: Total allocated memory exceeds the total memory of controller-0 numa node 0 Probably the controller-0 memory is 4G, but some default parameters in configuration is more than 4G. Can you tell me how to change it, since I don't want to change my physical PC. Thanks, Daolin -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Thu Jan 16 15:58:38 2020 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 16 Jan 2020 09:58:38 -0600 Subject: [Starlingx-discuss] Filling in leadership roles that opened up between elections In-Reply-To: References: Message-ID: On Thu, Jan 16, 2020 at 3:43 AM Ildiko Vancsa wrote: > As a practice within project teams in OpenStack there are two ways forward they usually take depending on the circumstances: > > 1. Delegating the departing PTL's responsibilities to a successor for the rest of the term > 2. Call for a special election to find a successor > > The departing PTL is encouraged to choose from options #1 or #2. In case the remaining term is short the usual practice is option #1 while when the remaining time is longer they hold an interim election for the project team that elects a new PTL for the remaining term. > > When the case remains unresolved by the departing PTL the TC has the responsibility to act where they also choose between options #1 and #2 with taking similar considerations as mentioned above. > > I think it would be beneficial to consider adopting a similar process for the StarlingX community as well. In the specific cases we have currently I would suggest holding elections for the affected teams as more than half of the terms are still left till the next PL/TL elections. I think this is a reasonable approach and like the idea of StarlingX following that precedent from OpenStack. dt -- Dean Troyer dtroyer at gmail.com From stefan at fuhrmann.homedns.org Thu Jan 16 16:47:52 2020 From: stefan at fuhrmann.homedns.org (Stefan Fuhrmann) Date: Thu, 16 Jan 2020 17:47:52 +0100 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available Message-ID: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> Hello all, I want to install "Virtual All-in-one Simplex"  on my proxmox machine. Its kvm-based solution and I run the starlingx vm nested with "host cpu". Starting the installation: bash setup_configuration.sh -c simplex -i ./bootimage.iso gives error: Failed to start domain simplex-controller-0 error: the CPU is incompatible with host CPU: Host CPU does not provide required features: ssse3, sse4.1, sse4.2 the host machine ia a bit older and has this cpu- flags: flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs hw_pstate vmmcall npt lbrv svm_lock Is it possible to run starlingx when only sse2 is available? How can I do it? Can someone help? Tia Stefan From stefan at fuhrmann.homedns.org Thu Jan 16 17:03:04 2020 From: stefan at fuhrmann.homedns.org (Stefan Fuhrmann) Date: Thu, 16 Jan 2020 18:03:04 +0100 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> Message-ID: <6a8d3f4b-1e67-a572-ddcd-aaacd189771d@fuhrmann.homedns.org> Hello all, sorry, I noticed now sse4a. Is startlingx not running on amd? tia Stefan Am 16.01.20 um 17:47 schrieb Stefan Fuhrmann: > Hello all, > > I want to install "Virtual All-in-one Simplex"  on my proxmox machine. > Its kvm-based solution and I run the starlingx vm nested with "host cpu". > > Starting the installation: > > bash setup_configuration.sh -c simplex -i ./bootimage.iso > > gives > > error: Failed to start domain simplex-controller-0 > error: the CPU is incompatible with host CPU: Host CPU does not > provide required features: ssse3, sse4.1, sse4.2 > > the host machine ia a bit older and has this cpu- flags: > > > flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl > nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm > cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch > osvw ibs hw_pstate vmmcall npt lbrv svm_lock > > Is it possible to run starlingx when only sse2 is available? > > How can I do it? > > Can someone help? > > > Tia > > Stefan > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Thu Jan 16 17:05:00 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 16 Jan 2020 09:05:00 -0800 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <9700A18779F35F49AF027300A49E7C76609137BB@SHSMSX105.ccr.corp.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB18F@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB20B@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C76609137BB@SHSMSX105.ccr.corp.intel.com> Message-ID: <0bcaacc8-0223-8cac-5ed8-0dfbc1c9cf0d@linux.intel.com> Folks, I checked with the Kata team and they do maintain a stable branch and repos that will not be removed. There is a different OBS project that they store them in. Note they now have a stable 1.10 version which is even newer than the 1.9 you started with in December. > > Yes is a different repository here it is: > https://build.opensuse.org/project/show/home:katacontainers:releases:x86_64:stable-1.9 > https://build.opensuse.org/project/show/home:katacontainers:releases:x86_64:stable-1.10 > > We maintain the last two stable branches of Kata, in average it is maintained for about 2 months. > After that the packages are not removed and you can keep pointing to it but we encourage to the next > Supported version. You can get details about the repos here: > https://software.opensuse.org//download.html?project=home%3Akatacontainers%3Areleases%3Ax86_64%3Astable-1.10&package=kata-containers-image Sau! On 1/14/20 5:58 PM, Lin, Shuicheng wrote: > Hi all, > > Really sorry for the trouble caused. I thought I have checked the rpm > available last week, but it seems I missed. > > I will submit new patch later after verified the new kata rpm. > > Best Regards > > Shuicheng > > *From:*Penney, Don > *Sent:* Wednesday, January 15, 2020 4:41 AM > *To:* Miller, Frank ; Little, Scott > ; starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > Reviews for reversions: > > https://review.opendev.org/#/q/status:open+projects:starlingx+branch:master+topic:kata > > *From:*Miller, Frank > *Sent:* Tuesday, January 14, 2020 3:32 PM > *To:* Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > Thanks Don – that takes care of #2 so we won’t see this issue again once > Shuicheng updates the kata version and completes #1. > > Frank > > *From:*Penney, Don > *Sent:* Tuesday, January 14, 2020 3:24 PM > *To:* Miller, Frank >; Little, Scott > >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > It may not actually cause a build failure, now that I think about it… > the download-mirror will see that the file exists and skip it. So it’s > only because the file no longer existed the first time it tried to > download that we had a failure. > > *From:*Miller, Frank > *Sent:* Tuesday, January 14, 2020 3:22 PM > *To:* Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > I think the best 2 actions would be: > > 1)Revert the kata commit(s) and Shuicheng to rebase on the new kata > version, run his own testing to ensure the new version did not break > anything and then push the kata commits along with the new version of kata. > > 2)Identify how we can prevent a build failure in the future when kata > puts out a new version and deletes the 1.9.3-8.1 version.  Is there a > way the StarlingX build or CENGN mirror can cache this version so we can > control when we move to a new version? > > Frank > > *From:*Penney, Don > *Sent:* Tuesday, January 14, 2020 3:09 PM > *To:* Miller, Frank >; Little, Scott > >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > Option B here would be to revert the kata updates so the build can > proceed, and ask for it to be rebased and retested: > > https://review.opendev.org/#/q/status:merged+projects:starlingx+branch:master+topic:kata > > *From:*Penney, Don > *Sent:* Tuesday, January 14, 2020 3:05 PM > *To:* Miller, Frank; Little, Scott; starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > Unfortunately, the upstream repo where we get the RPMs deletes the older > versions when they release a new one, it seems. So our build will break > any time they do so. > > *From:*Miller, Frank > *Sent:* Tuesday, January 14, 2020 3:03 PM > *To:* Penney, Don; Little, Scott; starlingx-discuss at lists.starlingx.io > > *Subject:* RE: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > Thank-you Don.  Did Shuicheng not use a specific version of kata > containers in his commits?  Will your commit ensure that we are locked > down on the 1.9.3-8.1 version?  We need to make sure the next time kata > releases a new version that we do not automatically pick up the new > version.  Going to a new version should be done in a controlled way > where the feature owner does testing with the new version in his own > environment before posting a commit to upversion to the newer version. > > Frank > > *From:*Penney, Don [mailto:Don.Penney at windriver.com] > *Sent:* Tuesday, January 14, 2020 2:39 PM > *To:* Little, Scott >; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > A review is posted to update the versions of the kata RPMs: > > https://review.opendev.org/702506 > > *From:*Scott Little [mailto:scott.little at windriver.com] > *Sent:* Tuesday, January 14, 2020 2:23 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Kata containers update breaking build > - failure to download RPMs > > 1) The rpms listed in the lst files are way out of date relative to > what's available from the new kata repo. > > [ ]    kata-containers-image-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11 >     36M     Details > [ ]    kata-ksm-throttler-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:33 > 5.9M     Details > [ ]    kata-linux-container-4.19.75.54-8.1.x86_64.rpm    10-Dec-2019 > 09:22     8.3M     Details > [ ]    kata-linux-container-debug-4.19.75.54-8.1.x86_64.rpm > 10-Dec-2019 09:22     335K     Details > [ ]    kata-proxy-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11     2.4K > Details > [ ]    kata-proxy-bin-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:11     1.8M >     Details > [ ]    kata-runtime-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:39     20M >     Details > [ ]    kata-shim-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:20     2.4K > Details > [ ]    kata-shim-bin-1.9.3-8.1.x86_64.rpm    10-Dec-2019 09:20     7.3M >     Details > [ ]    qemu-lite-2.11.0+git.87517afd72-8.1.x86_64.rpm    10-Dec-2019 > 09:29     2.5K     Details > [ ]    qemu-lite-bin-2.11.0+git.87517afd72-8.1.x86_64.rpm    10-Dec-2019 > 09:29     2.6M     Details > [ ]    qemu-lite-data-2.11.0+git.87517afd72-8.1.x86_64.rpm > 10-Dec-2019 09:29     3.0M     Details > [ ]    qemu-vanilla-4.1.0+git.9e06029aea-8.1.x86_64.rpm    10-Dec-2019 > 09:44     2.6K     Details > [ ]    qemu-vanilla-bin-4.1.0+git.9e06029aea-8.1.x86_64.rpm > 10-Dec-2019 09:44     2.5M     Details > [ ]    qemu-vanilla-data-4.1.0+git.9e06029aea-8.1.x86_64.rpm > 10-Dec-2019 09:44     13M     Details > > 2) The kata repo appears to be for SUSE, not CentOS. > > 3) The new repos url > points > to a location with a lot of extra 'stuff' when viewed from a browser. > Not sure if yum is being served a cleaner view, but there is certainly > the potential of confusing tools.  IS there an alternate UR that would > be cleaner? > > I recommend that the update > (stx-tools:431885231ae41256188a7c32f0f5351c4455707b) be reverted.  There > is likely other updates dependent on this that also need to be reverted. > > Scott > > On 2020-01-14 12:47 p.m., Penney, Don wrote: > > The latest CENGN build attempt fails on the RPM download stage, with the following errors: > > Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 > > No Match for argument kata-containers-image-1.9.2-7.1 > > Nothing to download > > Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-containers-image-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-containers-image-1.9.2-7.1 > > No Match for argument kata-containers-image-1.9.2-7.1 > > Nothing to download > > Warning: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > > Error: kata-containers-image-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 > > No Match for argument kata-ksm-throttler-1.9.2-7.1 > > Nothing to download > > Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-ksm-throttler-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-ksm-throttler-1.9.2-7.1 > > No Match for argument kata-ksm-throttler-1.9.2-7.1 > > Nothing to download > > Warning: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > > Error: kata-ksm-throttler-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 > > No Match for argument kata-linux-container-4.19.75.54-7.1 > > Nothing to download > > Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-linux-container-4.19.75.54-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-4.19.75.54-7.1 > > No Match for argument kata-linux-container-4.19.75.54-7.1 > > Nothing to download > > Warning: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > > Error: kata-linux-container-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 > > No Match for argument kata-linux-container-debug-4.19.75.54-7.1 > > Nothing to download > > Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-linux-container-debug-4.19.75.54-7.1 > > No Match for argument kata-linux-container-debug-4.19.75.54-7.1 > > Nothing to download > > Warning: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > > Error: kata-linux-container-debug-4.19.75.54-7.1.x86_64.rpm not found > > Looking for kata-proxy-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 > > No Match for argument kata-proxy-1.9.2-7.1 > > Nothing to download > > Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-proxy-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-1.9.2-7.1 > > No Match for argument kata-proxy-1.9.2-7.1 > > Nothing to download > > Warning: kata-proxy-1.9.2-7.1.x86_64.rpm not found > > Error: kata-proxy-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 > > No Match for argument kata-proxy-bin-1.9.2-7.1 > > Nothing to download > > Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-proxy-bin-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-proxy-bin-1.9.2-7.1 > > No Match for argument kata-proxy-bin-1.9.2-7.1 > > Nothing to download > > Warning: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > > Error: kata-proxy-bin-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-runtime-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 > > No Match for argument kata-runtime-1.9.2-7.1 > > Nothing to download > > Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-runtime-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-runtime-1.9.2-7.1 > > No Match for argument kata-runtime-1.9.2-7.1 > > Nothing to download > > Warning: kata-runtime-1.9.2-7.1.x86_64.rpm not found > > Error: kata-runtime-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 > > No Match for argument kata-shim-1.9.2-7.1 > > Nothing to download > > Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-1.9.2-7.1 > > No Match for argument kata-shim-1.9.2-7.1 > > Nothing to download > > Warning: kata-shim-1.9.2-7.1.x86_64.rpm not found > > Error: kata-shim-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 > > No Match for argument kata-shim-bin-1.9.2-7.1 > > Nothing to download > > Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > > Looking for kata-shim-bin-1.9.2-7.1.x86_64.rpm > > --> run: sudo -E yumdownloader -q -C -c /tmp/stx_mirror_vHj2Gp/yum.conf --releasever=7 --archlist=noarch,x86_64 kata-shim-bin-1.9.2-7.1 > > No Match for argument kata-shim-bin-1.9.2-7.1 > > Nothing to download > > Warning: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > > Error: kata-shim-bin-1.9.2-7.1.x86_64.rpm not found > > -----Original Message----- > > From:build.starlingx at gmail.com [mailto:build.starlingx at gmail.com] > > Sent: Tuesday, January 14, 2020 12:40 PM > > To:starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 382 - Still Failing! > > Project: STX_build_master_master > > Build #: 382 > > Status: Still Failing > > Timestamp: 20200114T172515Z > > Check logs at: > > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200114T172515Z/logs > > -------------------------------------------------------------------------------- > > Parameters > > BUILD_CONTAINERS_DEV: false > > BUILD_CONTAINERS_STABLE: false > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From vm.rod25 at gmail.com Thu Jan 16 17:12:56 2020 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 16 Jan 2020 11:12:56 -0600 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> Message-ID: On Thu, Jan 16, 2020 at 10:48 AM Stefan Fuhrmann wrote: > > Hello all, > > I want to install "Virtual All-in-one Simplex" on my proxmox machine. > Its kvm-based solution and I run the starlingx vm nested with "host cpu". > > Starting the installation: > > bash setup_configuration.sh -c simplex -i ./bootimage.iso > > gives > > error: Failed to start domain simplex-controller-0 > error: the CPU is incompatible with host CPU: Host CPU does not provide > required features: ssse3, sse4.1, sse4.2 > > the host machine ia a bit older and has this cpu- flags: > > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl > nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy > svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs > hw_pstate vmmcall npt lbrv svm_lock > > Is it possible to run starlingx when only sse2 is available? > Hi Can you help me with cat /proc/cpuinfo of your machine ? I want to know what kind of machine you have, from the GCC compile flags i can remember we didnot set march = something BUt definitly someting before sse2 might be hard to mantain since it was at least 10 yeras ago > How can I do it? > > Can someone help? > > > Tia > > Stefan > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Thu Jan 16 17:16:09 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 16 Jan 2020 17:16:09 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200116 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-16 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] AIO Simplex controller degraded https://bugs.launchpad.net/starlingx/+bug/1859859 Regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefan at fuhrmann.homedns.org Thu Jan 16 17:48:09 2020 From: stefan at fuhrmann.homedns.org (Stefan Fuhrmann) Date: Thu, 16 Jan 2020 18:48:09 +0100 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> Message-ID: <095da1f4-f95a-602a-2314-5a8d241520ba@fuhrmann.homedns.org> Hello Victor, Am 16.01.20 um 18:12 schrieb Victor Rodriguez: > cat /proc/cpuinfo processor       : 7 vendor_id       : AuthenticAMD cpu family      : 16 model           : 2 model name      : Quad-Core AMD Opteron(tm) Processor 2350 stepping        : 3 microcode       : 0x1000083 cpu MHz         : 2000.000 cache size      : 512 KB physical id     : 1 siblings        : 4 core id         : 3 cpu cores       : 4 apicid          : 7 initial apicid  : 7 fpu             : yes fpu_exception   : yes cpuid level     : 5 wp              : yes flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs hw_pstate vmmcall npt lbrv svm_lock bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2 bogomips        : 3990.07 TLB size        : 1024 4K pages clflush size    : 64 cache_alignment : 64 address sizes   : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate tia Stefan From vm.rod25 at gmail.com Thu Jan 16 18:16:19 2020 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 16 Jan 2020 12:16:19 -0600 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: <095da1f4-f95a-602a-2314-5a8d241520ba@fuhrmann.homedns.org> References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> <095da1f4-f95a-602a-2314-5a8d241520ba@fuhrmann.homedns.org> Message-ID: Hi Stefan Saul help me out to find this thread, it might be useful they also have an AMD platform, reviewing the Makefiles i dont see any march=<> that prevent from AMD to run http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002528.html IRC might be a good place to ask this question as well On Thu, Jan 16, 2020 at 11:48 AM Stefan Fuhrmann wrote: > > Hello Victor, > > > Am 16.01.20 um 18:12 schrieb Victor Rodriguez: > > cat /proc/cpuinfo > > processor : 7 > vendor_id : AuthenticAMD > cpu family : 16 > model : 2 > model name : Quad-Core AMD Opteron(tm) Processor 2350 > stepping : 3 > microcode : 0x1000083 > cpu MHz : 2000.000 > cache size : 512 KB > physical id : 1 > siblings : 4 > core id : 3 > cpu cores : 4 > apicid : 7 > initial apicid : 7 > fpu : yes > fpu_exception : yes > cpuid level : 5 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge > mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext > fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl > nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy > svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs > hw_pstate vmmcall npt lbrv svm_lock > bugs : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg > amd_e400 spectre_v1 spectre_v2 > bogomips : 3990.07 > TLB size : 1024 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 48 bits physical, 48 bits virtual > power management: ts ttp tm stc 100mhzsteps hwpstate > > tia > > Stefan > From stefan at fuhrmann.homedns.org Thu Jan 16 18:34:37 2020 From: stefan at fuhrmann.homedns.org (Stefan Fuhrmann) Date: Thu, 16 Jan 2020 19:34:37 +0100 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> <095da1f4-f95a-602a-2314-5a8d241520ba@fuhrmann.homedns.org> Message-ID: <066bca51-2412-d56d-88ab-95052977e873@fuhrmann.homedns.org> Hello Victor, Am 16.01.20 um 19:16 schrieb Victor Rodriguez: > Hi Stefan > > Saul help me out to find this thread, it might be useful they also > have an AMD platform, reviewing the Makefiles i dont see any march=<> > that prevent from AMD to run > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002528.html hmm that doesnt help. I dont have nova or other openstack things > > IRC might be a good place to ask this question as well okay. I will also look there. buying new hardware? tia Stefan From ildiko.vancsa at gmail.com Thu Jan 16 22:37:59 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Jan 2020 23:37:59 +0100 Subject: [Starlingx-discuss] Filling in leadership roles that opened up between elections In-Reply-To: References: Message-ID: Thanks Dean for the feedback and support. We also had a discussion about this on the TSC call today and were in an agreement about holding interim elections to fill in the open positions. The election officials started the preparations, please stay tuned for updates. In the meantime please don’t hesitate to raise further questions or comments if you have any. Thanks and Best Regards, Ildikó > On Jan 16, 2020, at 16:58, Dean Troyer wrote: > > On Thu, Jan 16, 2020 at 3:43 AM Ildiko Vancsa wrote: >> As a practice within project teams in OpenStack there are two ways forward they usually take depending on the circumstances: >> >> 1. Delegating the departing PTL's responsibilities to a successor for the rest of the term >> 2. Call for a special election to find a successor >> >> The departing PTL is encouraged to choose from options #1 or #2. In case the remaining term is short the usual practice is option #1 while when the remaining time is longer they hold an interim election for the project team that elects a new PTL for the remaining term. >> >> When the case remains unresolved by the departing PTL the TC has the responsibility to act where they also choose between options #1 and #2 with taking similar considerations as mentioned above. >> >> I think it would be beneficial to consider adopting a similar process for the StarlingX community as well. In the specific cases we have currently I would suggest holding elections for the affected teams as more than half of the terms are still left till the next PL/TL elections. > > I think this is a reasonable approach and like the idea of StarlingX > following that precedent from OpenStack. > > dt > > -- > Dean Troyer > dtroyer at gmail.com From Jessica.Castelino at windriver.com Thu Jan 16 23:42:05 2020 From: Jessica.Castelino at windriver.com (Castelino, Jessica) Date: Thu, 16 Jan 2020 23:42:05 +0000 Subject: [Starlingx-discuss] Test Hackathon Status Message-ID: Status as of 16th December: 1. https://review.opendev.org/#/c/702759/ Submitted patch set 3 according to Bart, Al and Joseph's comments. 2. https://review.opendev.org/#/c/702999/ Posted a review to add a py27 test case for DNS API. Kind Regards, Jessica From: Castelino, Jessica Sent: Wednesday, January 15, 2020 5:43 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hackathon Status Hi, A review to add a py27 test case for NTP API has been posted. https://review.opendev.org/#/c/702759/ Kind Regards, Jessica -------------- next part -------------- An HTML attachment was scrubbed... URL: From dorian_lau at 126.com Fri Jan 17 08:24:18 2020 From: dorian_lau at 126.com (Daolin Liu) Date: Fri, 17 Jan 2020 16:24:18 +0800 (CST) Subject: [Starlingx-discuss] system application-apply stx-openstack FAILED due to failed to download images Message-ID: <385ac7ca.89d9.16fb29a5c71.Coremail.dorian_lau@126.com> Hi, When I run system application-apply stx-openstack, failed to download one or more images, and I check from sysinv log, it seems that I cannot pull images from gcr.io in China (succeed for docker.io and quay.io) So I pull the image of defaultbackend:1.0 by myself and change the tag to gcr.io/google_containers/defaultbackend:1.0, and then run system application-apply stx-openstack again, but still failed, which seems that it's still tried to download from gcr.io although this image already exists. Probably related to Bug #1859881 Please give me some advice. Thanks, Daolin -------------- next part -------------- An HTML attachment was scrubbed... URL: From hu.tianhao at 99cloud.net Fri Jan 17 08:47:35 2020 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Fri, 17 Jan 2020 16:47:35 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?_Drdb_fails_for_AIO_Simplex_after_u?= =?utf-8?q?nlock_controller-0?= Message-ID: Hi guys, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. It seems that not all lvm are mounted successfully. Can anyone give some advice on this problem? controller-0:~$ drbd-overview 1:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 2:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 5:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 7:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 8:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s controller-0:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 600G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 500M 0 part /boot ├─sda3 8:3 0 19.5G 0 part / ├─sda4 8:4 0 229G 0 part │ ├─cgts--vg-scratch--lv 253:0 0 8G 0 lvm /scratch │ ├─cgts--vg-log--lv 253:1 0 7.8G 0 lvm /var/log │ ├─cgts--vg-extension--lv 253:2 0 1G 0 lvm │ │ └─drbd5 147:5 0 1024M 1 disk │ ├─cgts--vg-pgsql--lv 253:3 0 20G 0 lvm │ ├─cgts--vg-docker--lv 253:4 0 30G 0 lvm /var/lib/docker │ ├─cgts--vg-kubelet--lv 253:5 0 10G 0 lvm /var/lib/kubelet │ ├─cgts--vg-etcd--lv 253:6 0 5G 0 lvm │ │ └─drbd7 147:7 0 5G 1 disk │ ├─cgts--vg-backup--lv 253:7 0 25G 0 lvm /opt/backups │ ├─cgts--vg-dockerdistribution--lv 253:8 0 16G 0 lvm │ │ └─drbd8 147:8 0 16G 1 disk │ ├─cgts--vg-rabbit--lv 253:9 0 2G 0 lvm │ │ └─drbd1 147:1 0 2G 1 disk │ ├─cgts--vg-platform--lv 253:10 0 10G 0 lvm │ │ └─drbd2 147:2 0 10G 1 disk │ └─cgts--vg-ceph--mon--lv 253:11 0 20G 0 lvm /var/lib/ceph/mon └─sda5 8:5 0 34G 0 part sdb 8:16 0 200G 0 disk ├─sdb1 8:17 0 199G 0 part /var/lib/ceph/osd/ceph-0 └─sdb2 8:18 0 1G 0 part sdc 8:32 0 200G 0 disk sr0 11:0 1 1.9G 0 rom Thanks, Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Fri Jan 17 08:54:16 2020 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 17 Jan 2020 08:54:16 +0000 Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status In-Reply-To: References: Message-ID: Test Hack-a-thon Kube_app status: Jan 17th Mingyuan, Austin, Shuicheng continue working on kube_app test cases kube_app AppOperator: 1 new patch submitted, 2 patches in review, 5 merged New: - Add unit test for perform_app_apply in AppOperator (WIP) https://review.opendev.org/#/c/703031 Review: - Add unit test for perform_app_upload in AppOperator https://review.opendev.org/702597 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 Merged: - Add unit test for reapply in AppOperator https://review.opendev.org/702592 - Add unit test in AppOperator https://review.opendev.org/702369 - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 kube_app DockerHelper: 1 in review(WIP) - Add test class for kube_app DockerHelper(WIP) https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Thursday, January 16, 2020 21:54 To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 16th Mingyuan, Austin, Shuicheng continue working on kube_app test cases kube_app AppOperator: 4 patches in review(1 WIP), 3 merged: Review: - Add unit test for perform_app_upload in AppOperator(WIP) https://review.opendev.org/702597 - Add unit test for reapply in AppOperator https://review.opendev.org/702592 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 Merged: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 kube_app DockerHelper: 1 in review(WIP) - Add test class for kube_app DockerHelper(WIP) https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Wednesday, January 15, 2020 17:06 To: Qi, Mingyuan ; Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: RE: Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 15th Mingyuan, Austin, Shuicheng continue working on kube_app test cases. 1. For kube_app AppOperator class, 2 new commits out for review, 5 updated: New: - Add unit test for perform_app_upload in AppOperator(WIP) https://review.opendev.org/702597 - Add unit test for reapply in AppOperator https://review.opendev.org/702592 Updated: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit updated: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Mingyuan -----Original Message----- From: Qi, Mingyuan Sent: Tuesday, January 14, 2020 17:03 To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Kube_app Status Test Hack-a-thon Kube_app status: Jan 14th Mingyuan, Austin, Shuicheng is now working on kube_app test cases. 1. For kube_app AppOperator class, 5 commits out for review: - Add test class for kube_app AppOperator https://review.opendev.org/702341 - Add unit test for activate in AppOperator https://review.opendev.org/702361 - Add unit test for deactivate in AppOperator https://review.opendev.org/702367 - Add unit test for is_app_aborted in AppOperator https://review.opendev.org/702346 - Add unit test in AppOperator https://review.opendev.org/702369 2. For kube_app DockerHelper class, 1 commit out for review: - Add test class for kube_app DockerHelper https://review.opendev.org/#/c/702372/ Team will continue working on adding test cases/mock for public methods of underlining 2 classes. Mingyuan -----Original Message----- From: Zvonar, Bill Sent: Friday, January 10, 2020 22:15 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Test Hack-a-thon Etherpad... Hi folks - the etherpad for the Test Hack-a-thon is open at https://etherpad.openstack.org/p/stx-test-hackathon. More details to be added, but as discussed in the Community Call yesterday, we'll use this to keep track of who's working on what. Please indicate which areas/tasks you will work on in the list on the etherpad. Let's get hacking! Bill... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Fri Jan 17 13:59:41 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 17 Jan 2020 13:59:41 +0000 Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon In-Reply-To: <93814834B4855241994F290E959305C753124E03@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C7531247D1@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C753124B03@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C753124E03@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C753125109@SHSMSX104.ccr.corp.intel.com> Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on below task: https://storyboard.openstack.org/#!/story/2007082 Task 38039 Add unit tests for all RPC entry points in ConductorManager class in sysinv/conductor/manager.py Finish 8 patches. 2 patches merged https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. 3 patches ready for merge https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP https://review.opendev.org/#/c/702616/ Add unit tests for pci_device_update_by_host RPC EP 3 patches still under review. https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702833/ Add unit tests for inumas_update_by_ihost RPC EP. Zhipeng From: Liu, ZhipengS Sent: 2020年1月16日 20:38 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] a summary of RPC EP for ConductorManager task force for test hackathon Task force: Bin Yang & Zhipeng Liu from Intel. Here is a summary of our today's work on below task: https://storyboard.openstack.org/#!/story/2007082 Task 38039 Add unit tests for all RPC entry points in ConductorManager class in sysinv/conductor/manager.py 1. 7 commits updated after review https://review.opendev.org/#/c/702330/ Add unit tests for get_ihost_by_macs RPC EP. https://review.opendev.org/#/c/702359/ Add unit tests for get_ihost_by_hostname RPC EP. https://review.opendev.org/#/c/702360/ Add unit tests for ilvg_get_nova_ilvg_by_ihost RPC EP. https://review.opendev.org/#/c/702355/ Add unit tests for mtc_host_add RPC EP. https://review.opendev.org/#/c/702351/ Add unit tests for vim_host_add RPC EP. https://review.opendev.org/#/c/702377/ Add unit tests for platform_interfaces RPC EP https://review.opendev.org/#/c/702616/ Add unit tests for pci_device_update_by_host RPC EP 2. 1 new commit submitted. https://review.opendev.org/#/c/702833/ Add unit tests for inumas_update_by_ihost RPC EP. Welcome more people join in this task force. We have 100+ RPC EP need to be done for unit test. Thanks. Zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Jan 17 15:00:18 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 17 Jan 2020 15:00:18 +0000 Subject: [Starlingx-discuss] system application-apply stx-openstack FAILED due to failed to download images In-Reply-To: <385ac7ca.89d9.16fb29a5c71.Coremail.dorian_lau@126.com> References: <385ac7ca.89d9.16fb29a5c71.Coremail.dorian_lau@126.com> Message-ID: <20200117150018.uody3d4tu2ncvcp6@yuggoth.org> On 2020-01-17 16:24:18 +0800 (+0800), Daolin Liu wrote: > When I run system application-apply stx-openstack, failed to > download one or more images, and I check from sysinv log, it seems > that I cannot pull images from gcr.io in China (succeed for > docker.io and quay.io) > > So I pull the image of defaultbackend:1.0 by myself and change the > tag to gcr.io/google_containers/defaultbackend:1.0, and then run > system application-apply stx-openstack again, but still failed, > which seems that it's still tried to download from gcr.io although > this image already exists. [...] I gather this is related to the GFW blocking access to Google. What I've heard from Kubernetes users in mainland China is that overriding your image repository setting to registry.cn-hangzhou.aliyuncs.com/google_containers should work around it without needing a VPN. I'm not sure where you'd set this in the apply configuration for StarlingX, but hopefully others will chime in. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From vm.rod25 at gmail.com Fri Jan 17 15:53:28 2020 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Fri, 17 Jan 2020 09:53:28 -0600 Subject: [Starlingx-discuss] Host CPU does not provide required features, install when only sse2 is available In-Reply-To: <066bca51-2412-d56d-88ab-95052977e873@fuhrmann.homedns.org> References: <16120e97-8526-7584-f6b9-cc5d72873983@fuhrmann.homedns.org> <095da1f4-f95a-602a-2314-5a8d241520ba@fuhrmann.homedns.org> <066bca51-2412-d56d-88ab-95052977e873@fuhrmann.homedns.org> Message-ID: On Thu, Jan 16, 2020 at 12:34 PM Stefan Fuhrmann wrote: > > Hello Victor, > > Am 16.01.20 um 19:16 schrieb Victor Rodriguez: > > Hi Stefan > > > > Saul help me out to find this thread, it might be useful they also > > have an AMD platform, reviewing the Makefiles i dont see any march=<> > > that prevent from AMD to run > > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002528.html > hmm that doesnt help. I dont have nova or other openstack things > > > > IRC might be a good place to ask this question as well > > okay. I will also look there. > > buying new hardware? > No, it should be easier to fix the SW Bill can take this topic into the incoming weekly project meeting Thanks > tia > > Stefan > From Don.Penney at windriver.com Fri Jan 17 20:06:54 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 17 Jan 2020 20:06:54 +0000 Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DE951@ALA-MBD.corp.ad.wrs.com> Can you verify you used “system_mode: simplex” in your ansible override? Maybe provide your override file? Can you also do a “cat /etc/platform/platform.conf” and maybe a “system host-show controller-0”? From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Friday, January 17, 2020 3:48 AM To: starlingx-discuss Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi guys, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. It seems that not all lvm are mounted successfully. Can anyone give some advice on this problem? controller-0:~$ drbd-overview 1:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 2:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 5:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 7:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 8:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s controller-0:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 600G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 500M 0 part /boot ├─sda3 8:3 0 19.5G 0 part / ├─sda4 8:4 0 229G 0 part │ ├─cgts--vg-scratch--lv 253:0 0 8G 0 lvm /scratch │ ├─cgts--vg-log--lv 253:1 0 7.8G 0 lvm /var/log │ ├─cgts--vg-extension--lv 253:2 0 1G 0 lvm │ │ └─drbd5 147:5 0 1024M 1 disk │ ├─cgts--vg-pgsql--lv 253:3 0 20G 0 lvm │ ├─cgts--vg-docker--lv 253:4 0 30G 0 lvm /var/lib/docker │ ├─cgts--vg-kubelet--lv 253:5 0 10G 0 lvm /var/lib/kubelet │ ├─cgts--vg-etcd--lv 253:6 0 5G 0 lvm │ │ └─drbd7 147:7 0 5G 1 disk │ ├─cgts--vg-backup--lv 253:7 0 25G 0 lvm /opt/backups │ ├─cgts--vg-dockerdistribution--lv 253:8 0 16G 0 lvm │ │ └─drbd8 147:8 0 16G 1 disk │ ├─cgts--vg-rabbit--lv 253:9 0 2G 0 lvm │ │ └─drbd1 147:1 0 2G 1 disk │ ├─cgts--vg-platform--lv 253:10 0 10G 0 lvm │ │ └─drbd2 147:2 0 10G 1 disk │ └─cgts--vg-ceph--mon--lv 253:11 0 20G 0 lvm /var/lib/ceph/mon └─sda5 8:5 0 34G 0 part sdb 8:16 0 200G 0 disk ├─sdb1 8:17 0 199G 0 part /var/lib/ceph/osd/ceph-0 └─sdb2 8:18 0 1G 0 part sdc 8:32 0 200G 0 disk sr0 11:0 1 1.9G 0 rom Thanks, Tianhao [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Jan 17 21:24:37 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 17 Jan 2020 16:24:37 -0500 Subject: [Starlingx-discuss] Kata containers update breaking build - failure to download RPMs In-Reply-To: <4fba2ff8-8ab9-c189-9009-7cd0ed56824b@linux.intel.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DB04F@ALA-MBD.corp.ad.wrs.com> <9e85ac86-0d04-ba93-47eb-11797ca4e428@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB0FB@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DB165@ALA-MBD.corp.ad.wrs.com> <7934307f-558d-2f09-10d3-0e8206cef9c8@windriver.com> <4fba2ff8-8ab9-c189-9009-7cd0ed56824b@linux.intel.com> Message-ID: <4e614208-c25d-be6b-d9d4-cfded23a2078@windriver.com> Looks like the current serial mirror sync job is taking aprox 24 hours to sync all our repos. In the short term, the zul trigger won't help much. Need to look into a parallel implementation!!! Scott On 2020-01-14 8:35 p.m., Saul Wold wrote: > > > On 1/14/20 12:49 PM, Scott Little wrote: >> The new upstream repo should be introduced 24 hours before any lst >> files that reference content from that repo. >> > What do you think of creating a new Zuul process to fetch or cause > Cengn to fetch a current copy when the review is started via the Check > gate? > > Sau! >> That should give CENGN to mirror the new repo.  Once cengn has a copy >> of the version we want, it no longer matters if upstream changes the >> version. >> >> Scott >> >> >> On 2020-01-14 3:22 p.m., Miller, Frank wrote: >>> 2)Identify how we can prevent a build failure in the future when >>> kata puts out a new version and deletes the 1.9.3-8.1 version.  Is >>> there a way the StarlingX build or CENGN mirror can cache this >>> version so we can control when we move to a new version? >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> From maria.g.perez.ibarra at intel.com Fri Jan 17 22:10:14 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 17 Jan 2020 22:10:14 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200117 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-17 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Jan 17 22:56:15 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 17 Jan 2020 22:56:15 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 9/2020 & Jan 16/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1611C04@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Jan 9/2020: - Happy New Year! - stx.4.0 - Feature Plans: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Milestone-1 is planned for Jan 24 - Based on the milestone checklist, we look to be in good shape. - https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Release Concerns / Risks: - StarlingX Intel test team being diverted. Will need to determine a replacement plan. - This is a risk to MS-1 (criteria: High level resources secured) as well as the overall release - Some discussions happening, we'll revisit this in next week's release meeting. - CentOS-8 -- continue discussion from the community meeting on risk and how to mitigate them - stx.2.0.2 - Making progress on cherrypicking CVE fixes. OVMF & kernel in progress. See updates in Dec 19 meeting minutes below. - Also waiting for k8s certificate rotation: https://bugs.launchpad.net/starlingx/+bug/1838659 - Note sent to Mingyan thru the LP - Any others? - Branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Current Count: 7 - stx.3.0.1 - Branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 - Not much content merged since Release Date (Dec) - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 - Current Count: 17 Jan 16/2020: - Resourcing - Intel is re-org'ing. Some existing teams are ceasing their involvement in StarlingX and others will be joining the project. - New test team in Romania (Galati) - Right now, the focus is on transitioning sanity from GDC to Galati - There is currently no StarlingX lab in Galati. New manager is working on acquiring hardware. - New dev teams in Bangalore. One dev team remains in Shanghai, - Impacted Areas - Storage - Networking - Test Coverage - stx.4.0 - Expect release content to be reduced due to Intel resourcing shuffle. - Target is to deliver ceph containerization without BlueStore - The upgrades impact of BlueStore is technically complex due to the migration to a new filestore - This needs to be discussed in the next F2F meeting - Other features are TBD - TSC discussed today the lack of commitment/resourcing for stx.3 to stx.4 upgrades - This is not staffed and there hasn't been any uptake from the community to take on this work - Need to bring focus to the upgrades area in the next F2F meeting and discuss how we make it a priority - This may mean reducing investment in all other features - Need to continue to assess test impact on release activities - stx.2.0.2 - OVMF is still waiting on the stx-nova staging change. - Also waiting for https://bugs.launchpad.net/starlingx/+bug/1838659 -- k8s certificate rotation - stx.3.0.1 - Not discussed From Joseph.Richard at windriver.com Sat Jan 18 00:20:03 2020 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Sat, 18 Jan 2020 00:20:03 +0000 Subject: [Starlingx-discuss] hackathon status report Message-ID: <7B6A2AE64F40F245AE81F245059F0C3672F890B2@ALA-MBD.corp.ad.wrs.com> Merged: https://review.opendev.org/#/c/702300/ Introduces 62 new unit tests to cover sysinv network api In Review: https://review.opendev.org/#/c/702975/ Introduces 20 new unit tests to cover sysinv oam network api https://review.opendev.org/#/c/703212/ Introduces 14 new unit tests to cover sysinv address api Issues uncovered: https://bugs.launchpad.net/starlingx/+bug/1859855 https://bugs.launchpad.net/starlingx/+bug/1860176 https://bugs.launchpad.net/starlingx/+bug/1860186 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yi.c.wang at intel.com Sat Jan 18 03:00:24 2020 From: yi.c.wang at intel.com (Wang, Yi C) Date: Sat, 18 Jan 2020 03:00:24 +0000 Subject: [Starlingx-discuss] a summary of fault project task force for test hackathon - Day 5 Message-ID: Updates of Day 5, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : merged. 2. https://review.opendev.org/702347 : merged. 3. https://review.opendev.org/702588 : test passed. 4. https://review.opendev.org/702589 : test passed. 5. https://review.opendev.org/702823 : updated Submitted two more patches 6. https://review.opendev.org/703010 : add test case for migration sync and version 7. Submitted a new patch https://review.opendev.org/702823 : add test framework for rest api tests Thanks. Yi From: Wang, Yi C Sent: Thursday, January 16, 2020 10:48 PM To: 'starlingx-discuss at lists.starlingx.io' Cc: Chen, Yan ; An, Ran1 Subject: a summary of fault project task force for test hackathon - Day 4 Updates of Day 4, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : Updated according to Bart's comment. 2. https://review.opendev.org/702347 : Got +2, pending on #702175. 3. https://review.opendev.org/702588 : Updated according to Bart's comment. Under testing. 4. https://review.opendev.org/702589 : Under testing. 5. submitted a new patch https://review.opendev.org/#/c/702823/, fake database Thanks. Yi From: Wang, Yi C Sent: Wednesday, January 15, 2020 8:05 PM To: 'starlingx-discuss at lists.starlingx.io' > Cc: Chen, Yan >; An, Ran1 > Subject: a summary of fault project task force for test hackathon - Day 3 Updates of Day 3, Task force: Yan Chen, An Ran, Yi Wang 1. https://review.opendev.org/702175 : Create test framework for python with stestr. * Merged #702327 to avoid py35 failure, added py27/py35 to gating list. 2. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py * Abandoned according to Bart's comment, that fm-rest-api/fm/fm/common/timeutils.py should be replaced by oslo.utils.timeutils. * Submitted https://bugs.launchpad.net/starlingx/+bug/1859737 to track this clean up task. * Submitted a patch https://review.opendev.org/702589 : Remove fm/common/timeutils. 3. https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py * Submitted https://bugs.launchpad.net/starlingx/+bug/1859738 to track the code clean up task to remove fm.common.utils.generate_uuid. * Submitted a patch https://review.opendev.org/702588 : Remove fm.common.utils.generate_uuid. 4. https://review.opendev.org/702362 : Add test cases for fm-rest-api common code * Fixed pep8 errors and rebased Thanks. Yi From: Wang, Yi C Sent: Tuesday, January 14, 2020 4:44 PM To: starlingx-discuss at lists.starlingx.io Cc: Chen, Yan >; An, Ran1 > Subject: a summary of fault project task force for test hackathon Task force: Yan Chen, An Ran, Yi Wang Here is a summary of our today's work on fault project: 1. Created more tasks 10+, https://storyboard.openstack.org/#!/story/2007082 2. Submitted four patches for review https://review.opendev.org/702175 : Create test framework for python with stestr. https://review.opendev.org/702327 : Fix py3 exception error in fm-rest-api/fm/fm/common/timeutils.py https://review.opendev.org/702347 : Add unit test case for fm-rest-api/fm/fm/common/utils.py https://review.opendev.org/702362 : Add test cases for fm-rest-api common code 3. On-going work includes database faking, and more test cases Welcome more people join in this task force. Thanks. Yi -------------- next part -------------- An HTML attachment was scrubbed... URL: From hu.tianhao at 99cloud.net Sun Jan 19 02:16:51 2020 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Sun, 19 Jan 2020 10:16:51 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?Drdb_fails_for_AIO_Simplex_after_un?= =?utf-8?q?lock_controller-0?= In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DE951@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Don, Thank you for your reply, this is my override file. system_mode: simplex timezone: UTC dns_servers: - 114.114.114.114 - 8.8.8.8 admin_username: admin admin_password: 99cloud at SH ansible_become_pass: 99cloud at SH external_oam_subnet: 172.16.140.0/24 external_oam_gateway_address: 172.16.140.1 external_oam_floating_address: 172.16.140.188 management_subnet: 192.168.2.0/24 management_start_address: 192.168.2.2 management_end_address: 192.168.2.20 cluster_host_subnet: 192.168.68.0/24 # cluster_host_start_address: # cluster_host_end_address: docker_registries: k8s.gcr.io: url: gcr.azk8s.cn/google-containers gcr.io: url: gcr.azk8s.cn quay.io: url: quay.azk8s.cn And I'm sure I install StarlingX AIO Simplex, but after unlock controller-0, some pods fails to be up because of drab failed. controller-0:~$ cat /etc/platform/platform.conf nodetype=controller subfunction=controller,worker system_type=All-in-one security_profile=standard management_interface=lo http_port=8080 INSTALL_UUID=7edaf118-e70b-41f9-bfab-562c3219578c UUID=aef8f074-3bf9-4dea-8e77-9df1d82a1ae0 sdn_enabled=no region_config=no system_mode=simplex sw_version=19.09 security_feature="nopti nospectre_v2" vswitch_type=none region_config=False oam_interface=enp2s1 cluster_host_interface=lo 发件人:"Penney, Don" 发送日期:2020-01-18 04:06:54 收件人:"胡天昊" ,starlingx-discuss 主题:RE: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Can you verify you used “system_mode: simplex” in your ansible override? Maybe provide your override file? Can you also do a “cat /etc/platform/platform.conf” and maybe a “system host-show controller-0”? From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Friday, January 17, 2020 3:48 AM To: starlingx-discuss Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi guys, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. It seems that not all lvm are mounted successfully. Can anyone give some advice on this problem? controller-0:~$ drbd-overview 1:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 2:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 5:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 7:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 8:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s controller-0:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 600G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 500M 0 part /boot ├─sda3 8:3 0 19.5G 0 part / ├─sda4 8:4 0 229G 0 part │ ├─cgts--vg-scratch--lv 253:0 0 8G 0 lvm /scratch │ ├─cgts--vg-log--lv 253:1 0 7.8G 0 lvm /var/log │ ├─cgts--vg-extension--lv 253:2 0 1G 0 lvm │ │ └─drbd5 147:5 0 1024M 1 disk │ ├─cgts--vg-pgsql--lv 253:3 0 20G 0 lvm │ ├─cgts--vg-docker--lv 253:4 0 30G 0 lvm /var/lib/docker │ ├─cgts--vg-kubelet--lv 253:5 0 10G 0 lvm /var/lib/kubelet │ ├─cgts--vg-etcd--lv 253:6 0 5G 0 lvm │ │ └─drbd7 147:7 0 5G 1 disk │ ├─cgts--vg-backup--lv 253:7 0 25G 0 lvm /opt/backups │ ├─cgts--vg-dockerdistribution--lv 253:8 0 16G 0 lvm │ │ └─drbd8 147:8 0 16G 1 disk │ ├─cgts--vg-rabbit--lv 253:9 0 2G 0 lvm │ │ └─drbd1 147:1 0 2G 1 disk │ ├─cgts--vg-platform--lv 253:10 0 10G 0 lvm │ │ └─drbd2 147:2 0 10G 1 disk │ └─cgts--vg-ceph--mon--lv 253:11 0 20G 0 lvm /var/lib/ceph/mon └─sda5 8:5 0 34G 0 part sdb 8:16 0 200G 0 disk ├─sdb1 8:17 0 199G 0 part /var/lib/ceph/osd/ceph-0 └─sdb2 8:18 0 1G 0 part sdc 8:32 0 200G 0 disk sr0 11:0 1 1.9G 0 rom Thanks, Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Mon Jan 20 12:00:28 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Mon, 20 Jan 2020 12:00:28 +0000 Subject: [Starlingx-discuss] ValueError: typeURI failed validation Message-ID: hi, i have some errors in my container output, maybe someone is interest in? {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit [req-0fdd0943-a8f1-41ce-bce1-fe7d996c5989 - - - - -] An exception occurred processing the API call: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e : ValueError: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e\n","stream":"stdout","time":"2020-01-20T11:56:55.379405394Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit Traceback (most recent call last):\n","stream":"stdout","time":"2020-01-20T11:56:55.379435801Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 75, in wrapper\n","stream":"stdout","time":"2020-01-20T11:56:55.379442749Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit return fn(*args, **kwargs)\n","stream":"stdout","time":"2020-01-20T11:56:55.379454201Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 116, in _process_request\n","stream":"stdout","time":"2020-01-20T11:56:55.379459425Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit self._create_event(request).as_dict())\n","stream":"stdout","time":"2020-01-20T11:56:55.379464653Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 107, in _create_event\n","stream":"stdout","time":"2020-01-20T11:56:55.379469347Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit event = self._cadf_audit._create_event(req)\n","stream":"stdout","time":"2020-01-20T11:56:55.379474396Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 309, in _create_event\n","stream":"stdout","time":"2020-01-20T11:56:55.379486027Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit target = self.get_target_resource(req)\n","stream":"stdout","time":"2020-01-20T11:56:55.379491561Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 290, in get_target_resource\n","stream":"stdout","time":"2020-01-20T11:56:55.379496109Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit return self._build_target(req, service_info)\n","stream":"stdout","time":"2020-01-20T11:56:55.379501005Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 234, in _build_target\n","stream":"stdout","time":"2020-01-20T11:56:55.37950566Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit id=service.id, name=service.name)\n","stream":"stdout","time":"2020-01-20T11:56:55.379511641Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/pycadf/resource.py\", line 105, in __init__\n","stream":"stdout","time":"2020-01-20T11:56:55.379516714Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit setattr(self, RESOURCE_KEYNAME_TYPEURI, typeURI)\n","stream":"stdout","time":"2020-01-20T11:56:55.379521608Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/pycadf/cadftype.py\", line 66, in __set__\n","stream":"stdout","time":"2020-01-20T11:56:55.379526909Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit (self.name, self.func))\n","stream":"stdout","time":"2020-01-20T11:56:55.379531749Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit ValueError: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e\n","stream":"stdout","time":"2020-01-20T11:56:55.379536069Z"} {"log":"2020-01-20 11:56:55.378 18 ERROR keystonemiddleware.audit \n","stream":"stdout","time":"2020-01-20T11:56:55.379541045Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit [req-b872e320-8812-4662-bdb3-c7def9427909 0f653115099144a6909cbde1dedc83e5 3bd7feb370b24bf3a50e81b0af01c681 - default default] An exception occurred processing the API call: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e : ValueError: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e\n","stream":"stdout","time":"2020-01-20T11:56:55.418607081Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit Traceback (most recent call last):\n","stream":"stdout","time":"2020-01-20T11:56:55.41863818Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 75, in wrapper\n","stream":"stdout","time":"2020-01-20T11:56:55.418644225Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit return fn(*args, **kwargs)\n","stream":"stdout","time":"2020-01-20T11:56:55.418649354Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 122, in _process_response\n","stream":"stdout","time":"2020-01-20T11:56:55.418654119Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit self._create_event(request)\n","stream":"stdout","time":"2020-01-20T11:56:55.418659017Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/__init__.py\", line 107, in _create_event\n","stream":"stdout","time":"2020-01-20T11:56:55.418663354Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit event = self._cadf_audit._create_event(req)\n","stream":"stdout","time":"2020-01-20T11:56:55.418675457Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 309, in _create_event\n","stream":"stdout","time":"2020-01-20T11:56:55.418680509Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit target = self.get_target_resource(req)\n","stream":"stdout","time":"2020-01-20T11:56:55.418685274Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 290, in get_target_resource\n","stream":"stdout","time":"2020-01-20T11:56:55.418689622Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit return self._build_target(req, service_info)\n","stream":"stdout","time":"2020-01-20T11:56:55.418694389Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/keystonemiddleware/audit/_api.py\", line 234, in _build_target\n","stream":"stdout","time":"2020-01-20T11:56:55.418698711Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit id=service.id, name=service.name)\n","stream":"stdout","time":"2020-01-20T11:56:55.418704551Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/pycadf/resource.py\", line 105, in __init__\n","stream":"stdout","time":"2020-01-20T11:56:55.418709034Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit setattr(self, RESOURCE_KEYNAME_TYPEURI, typeURI)\n","stream":"stdout","time":"2020-01-20T11:56:55.41871373Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit File \"/var/lib/openstack/lib/python2.7/site-packages/pycadf/cadftype.py\", line 66, in __set__\n","stream":"stdout","time":"2020-01-20T11:56:55.41871813Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit (self.name, self.func))\n","stream":"stdout","time":"2020-01-20T11:56:55.418722777Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit ValueError: typeURI failed validation: \u003cfunction \u003clambda\u003e at 0x7fb078bd3398\u003e\n","stream":"stdout","time":"2020-01-20T11:56:55.418727024Z"} {"log":"2020-01-20 11:56:55.417 18 ERROR keystonemiddleware.audit \n","stream":"stdout","time":"2020-01-20T11:56:55.418731753Z"} greez, volker. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Jan 20 12:15:11 2020 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 20 Jan 2020 12:15:11 +0000 Subject: [Starlingx-discuss] centos8 upgrade status and plan Message-ID: CentOS 8 including python2to3: 1. Current Status: *build partial iso including 783 RPMs *ISO could be installed and boot successfully *pxe sever function has been verified individually *the detail rpm status https://drive.google.com/file/d/1HI3SuzXwT4pCirLSxgB46sxIPhIR8iuc/view?usp=sharing summary: SRPM: 55 is still not uploaded, most are puppet and openstack srpm. Tallball: 36 is not uploaded, most we can keep , some are depends on ceph. noarch rpm : 561 is not found, python2 pkgs should change to python3 , and openstack and its depends x86 rpm: 204 is not found. 2.staged plan: 1.Ansible ,Docker and Kubernetes pkgs rpm and install into iso,(verify individual function per ) ---Feb 14th 2.Flock Services (including platform openstack such as keystone, horizons and barbican) , assuming use RDO non-official release build into iso ---- March 13th 3.RT build ---- March 27th 4.ansible bootstrap ---- March 27th 5.all platform service running successfully. ---- April 17th 6.platform application and openstack application --- April 30th (assume using ceph containerization ) 7.feature test and function test , issue fix ---- End of May 3.issues, risk and concern *Ceph tarball (mimic is not support centos8) , Currently Strategy waiting rook /ceph containerization work *Openstack official RPMs are not released yet , just some middle repos , and those are for openstack train(most likely ,not official release, directly plan to release ussuri) https://trunk.rdoproject.org/centos8-train/26/c9/26c97d910a135d1ab1bd8ecd47f5bd80355b5624_190d169b/ https://trunk.rdoproject.org/centos8-master/deps/latest/noarch/ https://trunk.rdoproject.org/centos8-master/deps/latest/x86_64/ need upgrade platform openstack to train puppet version upgrade? Openstack Train is using puppet5, but platform puppet version is 4.8 if upgrade openstack to train, potential compatible issue. any potential quality issue using "pre-release" official train rpms. *RT kernel no official rpm or srpm Spec and config can be found in below https://git.centos.org/rpms/kernel-rt/branches?branchname=c8 tarball matching std kernel location. any potential quality issues built by ourselves *some packages version are big changes , such as drbd upgrade from 8 to 9 , any function or compatible issue. for example, currently drbd 8 cannot be built in kernel 4.10. so upgrade to 9, but is there campatible issues etc. another example, dnf which replacing yum, dnf does not support multi-paremeters in centos8, it cause build iso very slow, ~30mins. suggestions from expert in certain areas are welecome and needed. *Kubeadm install , the statement from k8s official site. "if your system's iptables tooling uses the nftables backend, you will need to switch the iptables tooling to 'legacy' mode to avoid these problems. This is the case on at least Debian 10 (Buster), Ubuntu 19.04, Fedora 29 and newer releases of these distributions by default. RHEL 8 does not support switching to legacy mode, and is therefore incompatible with current kubeadm packages." assume CentOS8 is same as RHEL8, it might be risk enabling kubeadm. *rebasing master to centos8 feature branch for example k8s upgrade in master, it will cause 2nd upgrade work when rebaseing master to centos8 feature branch. *verification and quality since this is major version upgrade, need test plan and test support. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Mon Jan 20 14:41:12 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 20 Jan 2020 14:41:12 +0000 Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15DE951@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DF1B2@ALA-MBD.corp.ad.wrs.com> Next thing to check will be if the puppet manifest application failed. I expect if you run “sudo sm-dump”, you’re seeing everything in an “initial” state - if the initial configuration failed, SM is unable to allocate IP addresses and bring up services, which would be why DRBD is not up. You can look at the logs in /var/log/puppet to see what the failure was, if that’s what’s happening (“grep -e Error -e Warning /var/log/puppet/latest/puppet.log”). From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Saturday, January 18, 2020 9:17 PM To: Penney, Don Cc: starlingx-discuss Subject: Re:RE: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi Don, Thank you for your reply, this is my override file. system_mode: simplex timezone: UTC dns_servers: - 114.114.114.114 - 8.8.8.8 admin_username: admin admin_password: 99cloud at SH ansible_become_pass: 99cloud at SH external_oam_subnet: 172.16.140.0/24 external_oam_gateway_address: 172.16.140.1 external_oam_floating_address: 172.16.140.188 management_subnet: 192.168.2.0/24 management_start_address: 192.168.2.2 management_end_address: 192.168.2.20 cluster_host_subnet: 192.168.68.0/24 # cluster_host_start_address: # cluster_host_end_address: docker_registries: k8s.gcr.io: url: gcr.azk8s.cn/google-containers gcr.io: url: gcr.azk8s.cn quay.io: url: quay.azk8s.cn And I'm sure I install StarlingX AIO Simplex, but after unlock controller-0, some pods fails to be up because of drab failed. controller-0:~$ cat /etc/platform/platform.conf nodetype=controller subfunction=controller,worker system_type=All-in-one security_profile=standard management_interface=lo http_port=8080 INSTALL_UUID=7edaf118-e70b-41f9-bfab-562c3219578c UUID=aef8f074-3bf9-4dea-8e77-9df1d82a1ae0 sdn_enabled=no region_config=no system_mode=simplex sw_version=19.09 security_feature="nopti nospectre_v2" vswitch_type=none region_config=False oam_interface=enp2s1 cluster_host_interface=lo [Image removed by sender.] 发件人:"Penney, Don" 发送日期:2020-01-18 04:06:54 收件人:"胡天昊" ,starlingx-discuss 主题:RE: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Can you verify you used “system_mode: simplex” in your ansible override? Maybe provide your override file? Can you also do a “cat /etc/platform/platform.conf” and maybe a “system host-show controller-0”? From: 胡天昊 [mailto:hu.tianhao at 99cloud.net] Sent: Friday, January 17, 2020 3:48 AM To: starlingx-discuss Subject: [Starlingx-discuss] Drdb fails for AIO Simplex after unlock controller-0 Hi guys, When I install AIO Simplex following this guide(https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex_install_kubernetes.html), drdb fails after unlock controller-0. It seems that not all lvm are mounted successfully. Can anyone give some advice on this problem? controller-0:~$ drbd-overview 1:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 2:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 5:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 7:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s 8:??not-found?? WFConnection Secondary/Unknown UpToDate/DUnknown C r----s controller-0:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 600G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 500M 0 part /boot ├─sda3 8:3 0 19.5G 0 part / ├─sda4 8:4 0 229G 0 part │ ├─cgts--vg-scratch--lv 253:0 0 8G 0 lvm /scratch │ ├─cgts--vg-log--lv 253:1 0 7.8G 0 lvm /var/log │ ├─cgts--vg-extension--lv 253:2 0 1G 0 lvm │ │ └─drbd5 147:5 0 1024M 1 disk │ ├─cgts--vg-pgsql--lv 253:3 0 20G 0 lvm │ ├─cgts--vg-docker--lv 253:4 0 30G 0 lvm /var/lib/docker │ ├─cgts--vg-kubelet--lv 253:5 0 10G 0 lvm /var/lib/kubelet │ ├─cgts--vg-etcd--lv 253:6 0 5G 0 lvm │ │ └─drbd7 147:7 0 5G 1 disk │ ├─cgts--vg-backup--lv 253:7 0 25G 0 lvm /opt/backups │ ├─cgts--vg-dockerdistribution--lv 253:8 0 16G 0 lvm │ │ └─drbd8 147:8 0 16G 1 disk │ ├─cgts--vg-rabbit--lv 253:9 0 2G 0 lvm │ │ └─drbd1 147:1 0 2G 1 disk │ ├─cgts--vg-platform--lv 253:10 0 10G 0 lvm │ │ └─drbd2 147:2 0 10G 1 disk │ └─cgts--vg-ceph--mon--lv 253:11 0 20G 0 lvm /var/lib/ceph/mon └─sda5 8:5 0 34G 0 part sdb 8:16 0 200G 0 disk ├─sdb1 8:17 0 199G 0 part /var/lib/ceph/osd/ceph-0 └─sdb2 8:18 0 1G 0 part sdc 8:32 0 200G 0 disk sr0 11:0 1 1.9G 0 rom Thanks, Tianhao [Image removed by sender.] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg URL: From maria.g.perez.ibarra at intel.com Mon Jan 20 22:41:37 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 20 Jan 2020 22:41:37 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200120 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-20 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Jan 21 08:45:45 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 21 Jan 2020 08:45:45 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/22/2020 Message-ID: Hi All: Agenda for 1/22 meeting: - Standardize Flock Package Versioning (JITStack Daniels) : AR from last meeting , performance impact ? build ,time ? - CentOS 8.0 upgrade planning (Austin) deep discuss on CentOS8 plan and risk Opens : - Cancel 1/29 meeting due to Chinese New Year. - Thanks. BR Austin Sun. From haochuan.z.chen at intel.com Tue Jan 21 13:42:04 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 21 Jan 2020 13:42:04 +0000 Subject: [Starlingx-discuss] question about ceph or storage In-Reply-To: <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> References: <56829C2A36C2E542B0CCB9854828E4D85628DE96@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747683@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85628F3EA@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85628F402@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747C99@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629833F@CDSMSX102.ccr.corp.intel.com> <4C60D9C5C8176C47874FFF36647AA19EA4747D45@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85629BBB7@CDSMSX102.ccr.corp.intel.com> <2239DBED-5ECC-4A11-9426-6B905CBD8348@windriver.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85629C5E4@CDSMSX102.ccr.corp.intel.com> Hi Bob Why sysinv send “admin_keyring” to glance helm chart, but for nova and cinder, send “user_secret_name” in ceph_client config. Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Church, Robert Sent: Thursday, January 16, 2020 11:44 PM To: Chen, Haochuan Z ; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: question about ceph or storage Hi Martin, The rbd provisioner chart creates the secret along with the pool when it’s first installed in the cluster via platform-integ-apps. Regards, Bob From: "Chen, Haochuan Z" > Date: Thursday, January 16, 2020 at 9:22 AM To: Ovidiu Poncea >, Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" > Subject: RE: question about ceph or storage Hi Ovidiu & Bob Another question. I found starlingx save ceph cluster’s client.admin key in kube secret “ceph-pool-kube-rbd”. I wonder when starlingx create this secret, read ceph cluster keyring and save to secret. In bootstrap? Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 11:40 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage I don't know if it's out of date :) it may just need to be retested if it wasn't for current release. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 30, 2019 3:51 PM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Thanks Ovidiu! If “-c” is out of date, what about remove it later. Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Monday, December 30, 2019 4:43 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, It was used in the previous release for connecting a deployment (especially an openstack one) to an external Ceph cluster. I don't know what is the feature testing status for current release. Ovidiu ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Monday, December 23, 2019 9:18 AM To: Poncea, Ovidiu; Church, Robert Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: question about ceph or storage Sorry to disturb! Merry Christmas to all StarlingX member! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Monday, December 23, 2019 3:17 PM To: Poncea, Ovidiu >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Ovidiu For “system storage-backend-add -c ”, user could deploy another ceph cluster, and add as storage backend, correctly. And this is this command’s intention, correct? Martin, Chen SSP, Software Engineer 021-61164330 From: Poncea, Ovidiu > Sent: Wednesday, December 18, 2019 7:47 PM To: Chen, Haochuan Z >; Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: question about ceph or storage Hi Chen, see inline. ________________________________ From: Chen, Haochuan Z [haochuan.z.chen at intel.com] Sent: Tuesday, December 17, 2019 10:46 AM To: Church, Robert; Poncea, Ovidiu Cc: 'starlingx-discuss at lists.starlingx.io' Subject: question about ceph or storage Hi Bob & Ovidiu Some question about ceph or storage. 1, What’s storage tier and storage profile? What’s the [Ovi] Storage tiering is equivalent with this: https://ceph.io/planet/deploying-ceph-with-storage-tiering/ . [Ovi] Profiles are managed by system storprofile-* and system host-apply-profile and are used to copy configuration from one node to another, identical node on initial provisioning. These profiles are only in system inventory, there is no Ceph equivalent. 2, why for duplex it request such puppet class dependency in ceph.pp? Is this request make all drbd config before class ceph? [Ovi] ceph-mon in AIO-DX is DRBD managed and it has a single, floating, monitor. On DX, when you swact, the monitor is stopped on the active controller and started on the standby controller. Drbd::Resource <| |> -> Class['::ceph'] And flag file “.node_ceph_configured”, to inform drbd make init setup before ceph config? 3, To launch ceph-mon, create a logical volume “ceph-mon-lv” and mount to /var/lib/ceph/mon, not directly mkdir “/var/lib/ceph/mon” for ceph-mon [Ovi] Ceph monitors have their own logical volume. They are managed through "system ceph-mon*" commands. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Wednesday, December 11, 2019 4:46 PM To: Church, Robert > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu >; Qi, Mingyuan > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob Some question, what’s storage tier and storage profile? As you said, we no longer manage pool and pg num, is this also unnecessary and we should remove it? BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Wednesday, December 4, 2019 12:09 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor See inline… From: "Chen, Haochuan Z" > Date: Tuesday, December 3, 2019 at 2:18 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: RE: ceph ops enabling in sysinv-conductor Hi Bob 1, we could update default pg num in sysinv/helm/rbd_provisioner.py. But when platform-integ-apps applied, maybe user has not add osded, so the default pg num is still for user reference. And for user override, I think it should add in ceph-pool-audit, stx-platform-helm/helm-charts/ceph-pools-audit/templates/job-ceph-pools-audit.yaml. but pg num update will make rebalance which cause management network jam. [RTC] For a more robust solution, consider the following: • We can update _met_app_apply_prerequisites () in sysinv/conductor.py for platform-integ-apps to require OSDs to be provisioned prior to applying the application. This will ensure an accurate OSD view when the application is initially applied. • The provisioner system overrides (in sysinv/helm/rbd_provisioner.py) should have the ability to calculate and set an optimal PG number to avoid generating a warning. • The rbd provisioner chart should also support setting a new chunk size (if greater than the existing size) to update the PG num. This will support user PG updates from the helm-overrides API. • I think it’s potentially a good idea for ceph-pool-audit to support adjusting the PG numbers as well but this is tricky as I don’t think we can reduce PG_num in Mimic without creating a new pool and copying the contents (pg_autoscaling is added in Nautilis). This audit code would have to be very specific in adjusting the PG num as installing applications that add additional pools will change the PG_num distribution. 2, the above case is only for system application. Any more alarm for PG number, request user should manage. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Church, Robert > Sent: Tuesday, December 3, 2019 10:34 AM To: Chen, Haochuan Z > Cc: 'starlingx-discuss at lists.starlingx.io' >; Poncea, Ovidiu > Subject: Re: ceph ops enabling in sysinv-conductor Hi Martin, In STX 1.0, we ran bare-metal openstack services for which we created and managed specific ceph storage pools for glance, cinder, nova, and swift. In this environment, we managed their creation and parameters (PGs and quotas) as the cluster scaled up. With the move to containerizing the openstack services in STX 2.0, pool creation is now driven mostly by helm charts packaged into an application (radosgw pools are the exception). Since we don’t know what additional application(s) will be deployed and what pools may be created, we are currently longer managing pools as in STX 1.0. These related functions in sysinv/conductor/ceph.py are remaining from STX 1.0 and need to be removed and/or repurposed to meet any new requirements. I took a look at the LP logs and it looks like we only have a single application applied: platform-integ-apps. This currently results in a single pool for 6 OSDs cluster: id: 6231df84-33be-4aa4-82ea-7408e0f2421c health: HEALTH_WARN too few PGs per OSD (21 < min 30) services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 6 osds: 6 up, 6 in data: pools: 1 pools, 64 pgs objects: 0 objects, 0 B usage: 645 MiB used, 5.4 TiB / 5.4 TiB avail pgs: 64 active+clean Since every installation will install platform-integ-apps, I think we should do the following: 1. Update the chunk_size calculation in sysinv/helm/rbd_provisioner.py to be dynamically calculated based on the number OSDs provisioned in the cluster. As this may be the only pool created, it should meet the minimum size characteristics to avoid a ceph warning. 2. Update the rbd-provisioner helm chart to support explicitly setting the pg_num based on the chunk size. Do this to allow setting a user override for the chunk size so that we can re-apply platform-integ-apps and explicitly set new values. Regards, Bob From: "Chen, Haochuan Z" > Date: Monday, December 2, 2019 at 1:15 AM To: Robert Church > Cc: "'starlingx-discuss at lists.starlingx.io'" >, Ovidiu Poncea > Subject: ceph ops enabling in sysinv-conductor Hi Bob I find some many function in sysinv-conductor/ceph.py, which could manage ceph cluster, such as create/delete/configure pool, audit pg etc. But why these function is not enabled? Or plan to request user to manage ceph cluster, such as create pool and configure pg num? Now I checked this issue, pg too few, as user maybe deploy few osd, which make alarm. So for such issue, request user to decide correct pg num or user could ignore? https://bugs.launchpad.net/starlingx/+bug/1844164 BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Jan 9 02:33:40 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 9 Jan 2020 02:33:40 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-01-08 Message-ID: <43F963BD1517044B90CF82FB2F3CA71623483CDE@fmsmsx120.amr.corp.intel.com> Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris Current agenda and notes 2020-01-08 * All -- reviews in progress and recent merges -- https://review.opendev.org/#/q/project:starlingx/docs * Active: ? https://review.opendev.org/#/c/701474/ - bug fix - Who can help me clarify dist cloud instructions for AIO Simplex on a subcloud? (Greg, Dariush) ? https://review.opendev.org/#/c/701470/ - bug fix ? https://review.opendev.org/#/c/695627/ - Move to new OpenStack - pending tech review ? https://review.opendev.org/#/c/699517/ - R2.0.2 release notes - staged for release ? https://review.opendev.org/#/c/693761/ - Still pending dependency, merge conflict fixed ? https://review.opendev.org/#/c/692202/ - STX in a box - pending * Stale: ? https://review.opendev.org/#/c/660154/ - Containers FAQ (move from wiki) - Q's re criteria for moving content from wiki to docs. Lets define this criteria! * Kris - look back in notes for list of wiki topics to be migrated. ? https://review.opendev.org/#/c/608214/ - python tox update from Jan 2019. Need to review to see if still relevant. ? https://review.opendev.org/#/c/617965/2 - Still relevant? * Stale (Marked abandoned to reset for 2020) - suggest followup review to confirm minor edits/typos covered in current version of pages. ? https://review.opendev.org/#/c/626414/ - Abandoned ? https://review.opendev.org/#/c/629643/ - Abandoned ? https://review.opendev.org/#/c/625118/ - Abandoned ? https://review.opendev.org/#/c/626042/ - Abandoned ? https://review.opendev.org/#/c/626040/ - Abandoned * All -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * Kris -- Releases * R3.0 - remaining items flagged for R3: https://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 * R2.0.2 Early Q1'20 - Release notes prepped. https://review.opendev.org/#/c/699517/1 * R3.0.1 - Early Q1'20 (likely w/ R2.0.2). Will require release notes. * R4.0 - planning - Engage with engineering teams once planning is finalized. ID features/updates requiring docs, and people on teams to contribute. ? Docs are included as a priorty 1 for R4 release. ? R4 planned features: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 (KRIS) * Kris -- Ongoing tasks: * Kris -- STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Updated image/build instructions provided. Instructions still inadequate. Need to meet with author. * Greg/Kris -- semi urgent docs update -- Need to update R3 docs to provide caution re updating Kubernetes secrets (untill long term approach is implemented) ? We don't yet know where this landed. * Mike/Linja/Huifeng/David -- adding video to StarlingX.io -- Video posted: https://youtu.be/6IhWPaRD7Po ? Final location? Huifeng suggests adding to https://docs.starlingx.io/operations/tsn.html instead of the Wiki (https://wiki.openstack.org/wiki/StarlingX/Networking/TSN , which is supposed to be Outdated) * Final location: Add to TSN page in docs. See if we can embed the vid. If not, use a simple text link. * Mike -- Adding article to StarlingX.io -- In progress https://01.org/blogs/vmrod25/2019/accelerating-ai-workloads-starlingx-edge-servers-using-x86-technology ? Lets do this as a blog post: https://www.starlingx.io/blog/ ? Need to write a summary (Mike), then link to article. Submit as a PR to site (Kris). ? Target - first part of January * Bruce -- Improve www.starlingx.io -- https://storyboard.openstack.org/#!/story/2007029 ? Get started link will be an easy change - make PR as soon as ready. ? Note that the marketing call handles larger changes related to website (graphics, design, etc). https://wiki.openstack.org/wiki/Starlingx/Meetings#8am_Pacific_-_Community_Marketing_Planning_Call ? Put together requirements together, then attend the marketing call (coordinate with Ildiko) (Kris will coord requirements) * Kris -- Planning -- Will be consolidating potential content/tasks, as well as existing stories, to use as basis for planning leading up to R4 release. * Documentation backlog: https://etherpad.openstack.org/p/stx-docs-backlog * Bruce/Mike -- Intel reorg - impact to docs? Looking into new structure/org. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sat Jan 11 09:08:39 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 11 Jan 2020 03:08:39 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$6aku8h@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200111T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Wed Jan 15 09:08:57 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 15 Jan 2020 03:08:57 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$6bnq83@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200115T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From huifeng.le at intel.com Thu Jan 9 15:00:40 2020 From: huifeng.le at intel.com (Le, Huifeng) Date: Thu, 9 Jan 2020 15:00:40 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 01/09 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D67650C@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Jan 09/2020 * stx.3.0 Bugs: All open issues should try with latest daily build with train patch (ISO 20191115: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006973.html) * stx.3.0 final compile candidate build: Dec.11 * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * High: ? https://bugs.launchpad.net/starlingx/+bug/1841189 ping to vm fails in live migration test - Gongjun Can't be reproduced this bug (Instances were migrated 640 times by using automated scripts) and suggest WR to take the bug. Reassign this issue to Wendy to reproduce, if it can be reproduced, WR team will help to do debug first ? https://bugs.launchpad.net/starlingx/+bug/1821026 Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - Marvin Some test-case are tested for Matt`s comment, need Matt to confirm these are effective or not Matt will help to provide more test steps to verify the fix ? https://bugs.launchpad.net/starlingx/+bug/1858390 vSwitch socket memory with numa node issue - Process issue, Kris has created the patch (https://review.opendev.org/701470) to update installation guide * stx 2.0 Bugs * High: ? https://bugs.launchpad.net/starlingx/+bug/1849655 StarlingX R2 duplex: VM not getting IP assigned to the vlan network when re-spawned on controller-0 after shutting down controller-1 - Marvin * Tried to deploy cirros VM with IPv6 on stx-openstack, but the VM didn`t get correct IPv6 address inside. The ubuntu cloud image also have same question. How can I create a image with IPv6 enable? - need some special ubuntu cloud image, Matt will help to put the comment later. * stx.4.0 Feature Proposals: https://etherpad.openstack.org/p/stx.4.0-feature-candidates * Milestones: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 ? Milestone-1 1/24/2020 ? Milestone-2 3/27/2020 ? Milestone-3 5/15/2020 ? Feature Test 5/29/2020 ? Regression Test TBD ? RC1 6/12/2020 ? Final Regression TBD ? Release 7/3/2020 * Unit Test Initiative: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006710.html ? to align with community strategy: wait for the Hack-a-thon notification and track the story and task * TSN support in Kata: ? Depend on Kata container support * Kata integration feature will be merged soon, will start this task after kata merged: https://review.opendev.org/#/q/topic:kata+(status:open) * Containerize OVS-DPDK (cheng): propose for 4.0 ? openstack-helm-infra project to support ovs chart per-host overrides * https://storyboard.openstack.org/#!/story/2006965 * https://review.opendev.org/#/c/701676/ ? https://review.opendev.org/#/c/694188 , ovs chart patch, this patch is in progress. Depends on per-host overrides feature - to be worked first ? https://review.opendev.org/#/c/696437/, import OVS-DPDK patches, cherry-pick latest ovs-dpdk feature patch from openstack-helm-infra into STX, Can we consider to upgrade the openstack-helm version in 4.0? - Check with Frank on the 4.0 plan, Copy Bob, Church (TL for container team) * IPv6 PXE boot network support: https://storyboard.openstack.org/#!/story/2006442 - Huang, XiangDong - Plan to start from Feb. * OVS collectd resource monitoring: Chenjie ? https://storyboard.openstack.org/#!/story/2002948 - Monitor other features besides interface/port * Monitor datanetwork for non openstack worker node by link monitor Marvin o Patch submitted: https://review.opendev.org/#/c/695390/ +2 +1 +1: Need Don to review * https://review.opendev.org/#/c/695391/ +1: Need Matt and core reviewer to check * https://review.opendev.org/#/c/694940/ +2: Need Eric to review * https://review.opendev.org/#/c/694927/ : merged, Due to config file path change to /etc/lmon/lmon.conf, the link monitor is invalid now we have to merge these patches ( 695390, 695391, 694940 ) as quickly as possible. ? WIP to add test cases and fix puppet issues _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Thu Jan 16 09:03:48 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 16 Jan 2020 03:03:48 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$7lb4oh@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200116T023002Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Fri Jan 17 09:07:28 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 17 Jan 2020 03:07:28 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$6gmnq5@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200117T023005Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Sat Jan 18 09:06:58 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 18 Jan 2020 03:06:58 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20200118T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Sun Jan 19 09:07:19 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 19 Jan 2020 03:07:19 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$7mcskf@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200119T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Mon Jan 20 09:02:08 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 20 Jan 2020 03:02:08 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <86d0ec$85qugu@fmsmga001.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200120T000004Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Tue Jan 21 09:07:07 2020 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 21 Jan 2020 03:07:07 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$7mvldc@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20200121T000002Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Bill.Zvonar at windriver.com Tue Jan 21 18:51:37 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 21 Jan 2020 18:51:37 +0000 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images In-Reply-To: <412985$6bnq83@orsmga007.jf.intel.com> References: <412985$6bnq83@orsmga007.jf.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B4DFAD@ALA-MBD.corp.ad.wrs.com> Make it stop! : ) -----Original Message----- From: cristopher.j.lemus.contreras at intel.com Sent: Wednesday, January 15, 2020 4:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images List of docker images required for "platform-integ-apps": BUILD_ID="20200115T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Tue Jan 21 18:56:39 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 21 Jan 2020 18:56:39 +0000 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B4DFAD@ALA-MBD.corp.ad.wrs.com> References: <412985$6bnq83@orsmga007.jf.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC007B4DFAD@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15DF9AD@ALA-MBD.corp.ad.wrs.com> These are all different loads and different origination dates. I'm guessing they were blocked for some reason by the mailing list, and unblocked by a moderator just now? -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, January 21, 2020 1:52 PM To: cristopher.j.lemus.contreras at intel.com; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX platform-integ-apps docker images Make it stop! : ) -----Original Message----- From: cristopher.j.lemus.contreras at intel.com Sent: Wednesday, January 15, 2020 4:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images List of docker images required for "platform-integ-apps": BUILD_ID="20200115T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Tue Jan 21 18:58:20 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 21 Jan 2020 18:58:20 +0000 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DF9AD@ALA-MBD.corp.ad.wrs.com> References: <412985$6bnq83@orsmga007.jf.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC007B4DFAD@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DF9AD@ALA-MBD.corp.ad.wrs.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B4E01C@ALA-MBD.corp.ad.wrs.com> Yup, makes sense - I withdraw my request to make it stop. -----Original Message----- From: Penney, Don Sent: Tuesday, January 21, 2020 1:57 PM To: Zvonar, Bill ; cristopher.j.lemus.contreras at intel.com; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX platform-integ-apps docker images These are all different loads and different origination dates. I'm guessing they were blocked for some reason by the mailing list, and unblocked by a moderator just now? -----Original Message----- From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, January 21, 2020 1:52 PM To: cristopher.j.lemus.contreras at intel.com; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX platform-integ-apps docker images Make it stop! : ) -----Original Message----- From: cristopher.j.lemus.contreras at intel.com Sent: Wednesday, January 15, 2020 4:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images List of docker images required for "platform-integ-apps": BUILD_ID="20200115T023003Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From huifeng.le at intel.com Wed Jan 22 02:01:28 2020 From: huifeng.le at intel.com (Le, Huifeng) Date: Wed, 22 Jan 2020 02:01:28 +0000 Subject: [Starlingx-discuss] Huifeng Le resigning to the stx-networking team Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D6798FC@SHSMSX104.ccr.corp.intel.com> StarlingX Community, Due to Internal organizational changes, I have to resign my position as PL and member of the stx-networking team. Community TSC will determine the process on who will be taking the responsibilities soon. It has been an honor and great working experience to work in the community. Thanks much for all the learnings! Best Regards, Le, Huifeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Wed Jan 22 05:14:19 2020 From: huifeng.le at intel.com (Le, Huifeng) Date: Wed, 22 Jan 2020 05:14:19 +0000 Subject: [Starlingx-discuss] StarlingX bi-weekly networking sub-project meeting Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D679968@SHSMSX104.ccr.corp.intel.com> Due to Chinese New Year holiday, networking sub-project meeting on Jan.23 will be canceled. Thanks! Best Regards, Le, Huifeng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Jan 22 12:35:42 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Jan 2020 12:35:42 +0000 Subject: [Starlingx-discuss] Community Call (Jan 22, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B4E4BF@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call coming up later today. Besides the usual standing topics (incl. CentOS 8 status) & and update on last week's Test Hack-a-Thon [3], we'll talk about the plan to fill the recently vacated leadership roles. Please feel free to add other topics to the meeting etherpad [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200122T1500 [3] https://etherpad.openstack.org/p/stx-test-hackathon -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Jan 22 14:54:44 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 22 Jan 2020 14:54:44 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 1/22/2020 Message-ID: Hi All: Thanks join the call. MoM for 1/22 meeting: - Standardize Flock Package Versioning (JITStack-Daniels) : 16 repositories changes , have to finish 12 repos before end of March. performance impact ? build ,time ? it is not starting yet. Wesley(Wesley.yang at jitstack.com) will take over Daniel from JITStack. Wesley will follow performance build use pbr for non-python repos. starlingx/nfv, starlingx/openstack-armada-app , starlingx/platform-armada-app and starlingx/utilities can not be finished before end of march. pbr intro https://docs.openstack.org/pbr/latest/user/semver.html and https://docs.openstack.org/pbr/latest/ status: https://drive.google.com/file/d/1FJtAYuHDCDIEmxBl2wxGsbz-boSxQRY5/view?usp=sharing - CentOS 8.0 upgrade planning (Austin) deep discuss on CentOS8 plan and risk Open : - Cancel 1/29 meeting due to Chinese new year. Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Tuesday, January 21, 2020 4:46 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 1/22/2020 Hi All: Agenda for 1/22 meeting: - Standardize Flock Package Versioning (JITStack Daniels) : AR from last meeting , performance impact ? build ,time ? - CentOS 8.0 upgrade planning (Austin) deep discuss on CentOS8 plan and risk Opens : - Cancel 1/29 meeting due to Chinese New Year. - Thanks. BR Austin Sun. From sgw at linux.intel.com Wed Jan 22 15:57:31 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 22 Jan 2020 07:57:31 -0800 Subject: [Starlingx-discuss] Proposal to Merged Community Meeting & TSC meeting Message-ID: StarlingX Folks: We currently have a large overlap of what's discussed in the two meetings and both meeting sometimes are shorter than the full hour. Is there any reason to not combine the two meetings? The benefit would be that it would give the large community better exposure to workings of the TSC, particularly as we advance towards confirmation. If more time is needed for some topic an extraordinary meeting could be added. I have added this as an item in the mid-cycle meetup also. Thanks for your consideration Sau! From austin.sun at intel.com Wed Jan 22 14:55:49 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 22 Jan 2020 14:55:49 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: New Series of non-Openstack disto meeting invitation , Agenda for each will be sent individual email. * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4555 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT40392 1.jpg Type: image/jpeg Size: 8269 bytes Desc: ATT40392 1.jpg URL: From sgw at linux.intel.com Wed Jan 22 18:14:10 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 22 Jan 2020 10:14:10 -0800 Subject: [Starlingx-discuss] PBR Status Check Message-ID: <5f55cb03-5360-3e11-fcc9-46f6dc24d6f8@linux.intel.com> Hi All & Welcome Wesley, We have a new community member from JitStack starting to look at the PBR work, here is some background for him. The PBR work was proposed via the StarlingX Feature Specification process, see the Flock Versioning specification [0], this is based on the OpenStack Python Build Reasonableness [1] and Semantic Versioning (SemVer) [2] definition. One of the issues that we are trying to resolve is the impact of the proposed change from Bin Yang to the time it takes to build a single package with PBR before and after the change. Ideally this would be done multiple times and provide the average along with the deviation. This in an important part of the project in order for us to move forward. Look forward to working with you. Sau! [0] https://docs.starlingx.io/specs/specs/stx-3.0/approved/standardize_flock_versioning.html [1] https://docs.openstack.org/pbr/latest/ [2] https://docs.openstack.org/pbr/latest/user/semver.html From Bill.Zvonar at windriver.com Wed Jan 22 18:46:09 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Jan 2020 18:46:09 +0000 Subject: [Starlingx-discuss] Community Call (Jan 22, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B4EAF0@ALA-MBD.corp.ad.wrs.com> >From today's call... - Standing Topics - Sanity - all Green since the Kata issues last week - per Bart, Duplex will be broken on the next build - a different Kata issue, not related to the one from last week - Shuicheng raised a bug for this https://bugs.launchpad.net/starlingx/+bug/1860529 - Bart offered to go ahead & merge the change as is (the workaround) (https://review.opendev.org/#/c/703783/) - per Yong, Shuicheng will do some more testing based on Bart's comments & update the review tomorrow (Thursday) - if it works, and Sanity passes (on Thursday), then ok for now & Shuicheng will update the fix after he's back from CNY - if it doesn't work, it'll have to be reverted so that we have Green Sanity until he's back - at the end of the meeting, Don noted that Shuicheng's change merged - we agreed to kick off a CENGN build right away - Reviews - nothing raised today - Requests for Help - nothing reviewed today - CentOS 8 - Austin's update: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007558.html - Test Hack-a-Thon - https://etherpad.openstack.org/p/stx-test-hackathon - results (some pending commits to be merged) - stx/config - 20 commits merged - 9 commits pending - ~550 additional lines of code now covered by unit tests - 3 bugs raised thanks to new unit tests addded by Joseph http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007554.html - stx/fault - 3 commits merged - 4 commits pending - Filling Newly Vacant Leadership Roles - Ildiko's email: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007523.html - Mid-Cycle Meetup - We are confirmed for the meeting in Chandler Arizona at Intel's campus. - Agenda & attendee list: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup - sign up on the etherpad (the one just above) - Bitergia - evaluation wrapping up by end of this month still? what's the next step? - per Ildiko, we'll be keeping it - AR Review - Jan 15, 2019 -- Saul/Build -- look into how to avoid build issues like the Kata issue from ~Jan 15 - Jan 22: per Saul, this has already been resolved - Kata has a stable release, so we've got a better SSOT for the Kata build - Nov 30, 2019 -- Kris -- link to developer resource for upversioning from Stein to Train - Jan 22: done! ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- From: Zvonar, Bill Sent: Wednesday, January 22, 2020 7:36 AM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (Jan 22, 2020) Hi all, reminder of the Community call coming up later today. Besides the usual standing topics (incl. CentOS 8 status) & and update on last week's Test Hack-a-Thon [3], we'll talk about the plan to fill the recently vacated leadership roles. Please feel free to add other topics to the meeting etherpad [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200122T1500 [3] https://etherpad.openstack.org/p/stx-test-hackathon From bruce.e.jones at intel.com Wed Jan 22 19:16:51 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 22 Jan 2020 19:16:51 +0000 Subject: [Starlingx-discuss] 4.0 MS-1? Message-ID: <9A85D2917C58154C960D95352B22818BED3AD224@fmsmsx123.amr.corp.intel.com> Are we declaring MS-1 this week as planned? brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Wed Jan 22 23:09:46 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 22 Jan 2020 23:09:46 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200122 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-22 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jan 23 14:35:45 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 23 Jan 2020 15:35:45 +0100 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Message-ID: Hi, As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. I came across three projects where I didn’t see any meetings on the calendar: * Config (Configuration) * Distcloud (Distributed Cloud) * Flock-Services (StarlingX Flock Services) By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. According to my knowledge these projects are all active. Is that an accurate observation? Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? Thanks and Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Starlingx/Meetings [2] https://wiki.openstack.org/wiki/StarlingX/Config [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices [5] https://www.osf.dev/about/four-opens/ From Dariush.Eslimi at windriver.com Thu Jan 23 14:40:49 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 23 Jan 2020 14:40:49 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: References: Message-ID: Hi Ildiko, Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. Thanks, Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-23-20 9:36 AM To: starlingx Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Hi, As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. I came across three projects where I didn’t see any meetings on the calendar: * Config (Configuration) * Distcloud (Distributed Cloud) * Flock-Services (StarlingX Flock Services) By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. According to my knowledge these projects are all active. Is that an accurate observation? Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? Thanks and Best Regards, Ildikó [1] https://wiki.openstack.org/wiki/Starlingx/Meetings [2] https://wiki.openstack.org/wiki/StarlingX/Config [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices [5] https://www.osf.dev/about/four-opens/ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu Jan 23 14:59:02 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 23 Jan 2020 15:59:02 +0100 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: References: Message-ID: Hi Dariush, Thank you for the quick response. Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. Let me know if I can help with anything else. Thanks, Ildikó > On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: > > Hi Ildiko, > > Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:36 AM > To: starlingx > Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi, > > As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. > > I came across three projects where I didn’t see any meetings on the calendar: > * Config (Configuration) > * Distcloud (Distributed Cloud) > * Flock-Services (StarlingX Flock Services) > > By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. > > Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. > > I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. > > According to my knowledge these projects are all active. Is that an accurate observation? > > Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? > > Thanks and Best Regards, > Ildikó > > [1] https://wiki.openstack.org/wiki/Starlingx/Meetings > [2] https://wiki.openstack.org/wiki/StarlingX/Config > [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud > [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices > [5] https://www.osf.dev/about/four-opens/ > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Jan 23 15:07:35 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 23 Jan 2020 15:07:35 +0000 Subject: [Starlingx-discuss] Mid-cycle Meetup In-Reply-To: <9A85D2917C58154C960D95352B22818BED398915@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED398915@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BED3AEA93@fmsmsx123.amr.corp.intel.com> Our mid-cycle meeting is confirmed for Mar 3-4 at Intel's Chandler campus - 5000 W Chandler Blvd in Chandler, Arizona. Just outside Phoenix. Anyone from the StarlingX community is welcome to attend. Please sign up at the etherpad link below if you plan to attend. brucej From: Jones, Bruce E Sent: Wednesday, January 8, 2020 11:09 AM To: starlingx-discuss at lists.starlingx.io Subject: Mid-cycle Meetup As discussed in the community meeting today, we are planning a mid-cycle meetup at Intel's Chandler AZ location. We have tentatively set the dates as March 3rd-4th. If you would like to attend but cannot make those dates, please respond to this email with dates that would work for you. This meeting is open to all members of the StarlingX community and is expected to cover both issues related to the project's current work and planning for future releases. There is an etherpad for the event [1]. Please feel free to add agenda topics to the list, and your name to the Attendee list if you plan to attend. Thank you and see you all in Arizona! Brucej [1] https://etherpad.openstack.org/p/starlingX-winter-2020-meetup -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Thu Jan 23 15:35:17 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 23 Jan 2020 15:35:17 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: References: Message-ID: Community, I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. Is there any objection to this time window? Thanks, Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-23-20 9:59 AM To: Eslimi, Dariush Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Hi Dariush, Thank you for the quick response. Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. Let me know if I can help with anything else. Thanks, Ildikó > On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: > > Hi Ildiko, > > Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:36 AM > To: starlingx > Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi, > > As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. > > I came across three projects where I didn’t see any meetings on the calendar: > * Config (Configuration) > * Distcloud (Distributed Cloud) > * Flock-Services (StarlingX Flock Services) > > By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. > > Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. > > I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. > > According to my knowledge these projects are all active. Is that an accurate observation? > > Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? > > Thanks and Best Regards, > Ildikó > > [1] https://wiki.openstack.org/wiki/Starlingx/Meetings > [2] https://wiki.openstack.org/wiki/StarlingX/Config > [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud > [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices > [5] https://www.osf.dev/about/four-opens/ > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From allison at openstack.org Thu Jan 23 18:08:23 2020 From: allison at openstack.org (Allison Price) Date: Thu, 23 Jan 2020 12:08:23 -0600 Subject: [Starlingx-discuss] Upcoming OSF Event: OpenDev + PTG, June 8-11 in Vancouver Message-ID: Join us this June in Vancouver for OpenDev + PTG, and grab your early bird tickets now ! OpenDev + PTG is a new collaborative event organized by the OpenStack Foundation gathering developers, system architects, and operators to address common open source infrastructure challenges. June 8-11, 2020 Vancouver Convention Centre - East Building OpenDev will include discussion oriented sessions around a particular topic to explore a problem within a topic area, share common architectures, and collaborate around potential solutions. This OpenDev will focus specifically on the following Tracks, spanning open source projects, including Airship, Ansible, Ceph, Kata Containers, Kubernetes, OpenStack, StarlingX, and Zuul: Hardware Automation Large-scale Usage of Open Source Infrastructure Software Containers in Production Key Challenges for Open Source in 2020 The conversations will continue into the afternoon with the Project Teams Gathering (PTG) . This is when the morning’s practices will be explored by project teams, SIGs and other workgroups who will have dedicated space to get work done in a productive setting, maximizing the ability of contributors to work through their project objectives in an environment that is focused towards work and productivity. Interested in Sponsoring? Sponsoring these events will help ensure the continued growth and success of open source infrastructure projects. A sponsorship prospectus will be available soon. If your organization is interested in participating and supporting the open infrastructure community, please contact events at openstack.org . P.S. - Stay tuned for more info on OSF’s Q4 event, the Open Infrastructure Summit you know and love! See you in Vancouver! The OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Jan 23 20:52:34 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 23 Jan 2020 20:52:34 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-01-22 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris StarlingX Docs Storyboard: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.docs StarlingX Docs Backlog: https://etherpad.openstack.org/p/stx-docs-backlog 2020-01-22 * All -- reviews in progress and recent merges -- https://review.opendev.org/#/q/project:starlingx/docs * 4 merged since last week * Open: https://review.opendev.org/#/q/project:starlingx/docs+status:open * Mergable: https://review.opendev.org/#/q/project:starlingx/docs+status:open+is:mergeable ? Please review: https://review.opendev.org/#/c/702565/ * All -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * All -- Ongoing tasks: * Kris -- misc doc clean up - https://storyboard.openstack.org/#!/story/2007193 - All ok with my updates? YES * Kris -- STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Ask author to join build meeting in 2 weeks. Confirmed * Greg (was Abraham) -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * Transition plan: https://etherpad.openstack.org/p/docs-transition-plan * Send announce (Kris) * Kris -- Releases * R4.0 - target release date is July 3, 2020. ? Code freeze end of May * Planning: * Prio 1: Must have for R4 release https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 * (Keep install guides simple - minimum needed) * We have 3 core types: install, config, ops ? Intel FPGA support for K8s - Get doc w/ content for config and usage. (potential ops and config guide). ? Kata Containers - Get doc w/ content for config and usage. ? Active Dir Integ for K8s APIs - Get doc w/ content for config and usage. ? Dist Cloud - Install guide changes, overview of distcloud functionality for OpenStack ? Backup & Restore: How to (ops guide) ? Kubernetes upgrade support: changes to existing (anything new?) ? Redfish virt media support: likely changes to dist cloud bare metal install ? Layered build: Likely changes to build guide. * Prio 2: Should have for R4 release * Prio 3: Nice to have * Opportunistic: Actionable items to do as time is available * Q: How far back to we want to keep release specific install guides? Mechanism to archive a set of old release docs, w/out building in docs? -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Jan 23 21:02:34 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 23 Jan 2020 21:02:34 +0000 Subject: [Starlingx-discuss] Kristal Dale resigning Documentation team Message-ID: Hello StarlingX Community, Due to organizational changes at Intel, I must resign my position as PTL for the stx-docs team. I will be working with Bruce Jones on a transition plan to ensure transfer of knowledge and planning for the upcoming release. It has been a pleasure to work on this project and with everyone involved! Best, Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Jan 23 21:21:51 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 23 Jan 2020 16:21:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 34 - Failure! Message-ID: <379084951.633.1579814512205.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 34 Status: Failure Timestamp: 20200123T212146Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200123T212130Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: compile.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200123T212130Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200123T212130Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler From maria.g.perez.ibarra at intel.com Fri Jan 24 00:12:51 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 24 Jan 2020 00:12:51 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200123 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-23 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From gopalkrishna.bhat at intel.com Thu Jan 23 03:53:22 2020 From: gopalkrishna.bhat at intel.com (Bhat, Gopalkrishna) Date: Thu, 23 Jan 2020 03:53:22 +0000 Subject: [Starlingx-discuss] Signup Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Jan 24 16:20:33 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 24 Jan 2020 16:20:33 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Thursday, January 23, 2020 7:35 AM To: Ildiko Vancsa Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Community, I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. Is there any objection to this time window? Thanks, Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-23-20 9:59 AM To: Eslimi, Dariush Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Hi Dariush, Thank you for the quick response. Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. Let me know if I can help with anything else. Thanks, Ildikó > On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: > > Hi Ildiko, > > Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:36 AM > To: starlingx > Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi, > > As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. > > I came across three projects where I didn’t see any meetings on the calendar: > * Config (Configuration) > * Distcloud (Distributed Cloud) > * Flock-Services (StarlingX Flock Services) > > By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. > > Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. > > I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. > > According to my knowledge these projects are all active. Is that an accurate observation? > > Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? > > Thanks and Best Regards, > Ildikó > > [1] https://wiki.openstack.org/wiki/Starlingx/Meetings > [2] https://wiki.openstack.org/wiki/StarlingX/Config > [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud > [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices > [5] https://www.osf.dev/about/four-opens/ > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Fri Jan 24 16:44:08 2020 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Fri, 24 Jan 2020 16:44:08 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200124 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-24 (link) Status: GREEN =========================================== Sanity Test executed in Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test executed in Virtual Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Jan 24 17:59:48 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 24 Jan 2020 09:59:48 -0800 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> Message-ID: <2e475abc-e9ab-f814-3699-58d7817fe3be@linux.intel.com> I think we need to do a general review of the meetings in light of other changes and based on the possible idea of merging the TSC and Community meetings. Sau! On 1/24/20 8:20 AM, Jones, Bruce E wrote: > 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. > > brucej > > -----Original Message----- > From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] > Sent: Thursday, January 23, 2020 7:35 AM > To: Ildiko Vancsa > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Community, > > I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. > Is there any objection to this time window? > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:59 AM > To: Eslimi, Dariush > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi Dariush, > > Thank you for the quick response. > > Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. > > Let me know if I can help with anything else. > > Thanks, > Ildikó > > >> On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: >> >> Hi Ildiko, >> >> Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. >> >> Thanks, >> Dariush >> >> -----Original Message----- >> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >> Sent: January-23-20 9:36 AM >> To: starlingx >> Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility >> >> Hi, >> >> As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. >> >> I came across three projects where I didn’t see any meetings on the calendar: >> * Config (Configuration) >> * Distcloud (Distributed Cloud) >> * Flock-Services (StarlingX Flock Services) >> >> By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. >> >> Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. >> >> I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. >> >> According to my knowledge these projects are all active. Is that an accurate observation? >> >> Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? >> >> Thanks and Best Regards, >> Ildikó >> >> [1] https://wiki.openstack.org/wiki/Starlingx/Meetings >> [2] https://wiki.openstack.org/wiki/StarlingX/Config >> [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud >> [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices >> [5] https://www.osf.dev/about/four-opens/ >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Dariush.Eslimi at windriver.com Fri Jan 24 17:59:55 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Fri, 24 Jan 2020 17:59:55 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> Message-ID: This is the earliest available slot on Monday, others days of the week also are pretty full. Unless if we want to break the Meeting Free Fridays? Please take a look here : https://wiki.openstack.org/wiki/Starlingx/Meetings What would you suggest? Dariush -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: January-24-20 11:21 AM To: Eslimi, Dariush ; Ildiko Vancsa Cc: starlingx Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Thursday, January 23, 2020 7:35 AM To: Ildiko Vancsa Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Community, I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. Is there any objection to this time window? Thanks, Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-23-20 9:59 AM To: Eslimi, Dariush Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Hi Dariush, Thank you for the quick response. Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. Let me know if I can help with anything else. Thanks, Ildikó > On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: > > Hi Ildiko, > > Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:36 AM > To: starlingx > Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi, > > As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. > > I came across three projects where I didn’t see any meetings on the calendar: > * Config (Configuration) > * Distcloud (Distributed Cloud) > * Flock-Services (StarlingX Flock Services) > > By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. > > Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. > > I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. > > According to my knowledge these projects are all active. Is that an accurate observation? > > Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? > > Thanks and Best Regards, > Ildikó > > [1] https://wiki.openstack.org/wiki/Starlingx/Meetings > [2] https://wiki.openstack.org/wiki/StarlingX/Config > [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud > [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices > [5] https://www.osf.dev/about/four-opens/ > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Fri Jan 24 18:10:58 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 24 Jan 2020 18:10:58 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: References: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BF165827E@fmsmsx121.amr.corp.intel.com> I feel your pain, Dariush. There are very few (if any) open alternatives. Perhaps we should consider consolidating our meetings more aggressively or shortening more of the 60 minute calls to 30 minutes so we can fit more calls into those slots. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Friday, January 24, 2020 10:00 AM To: Jones, Bruce E ; Ildiko Vancsa Cc: starlingx Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility This is the earliest available slot on Monday, others days of the week also are pretty full. Unless if we want to break the Meeting Free Fridays? Please take a look here : https://wiki.openstack.org/wiki/Starlingx/Meetings What would you suggest? Dariush -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: January-24-20 11:21 AM To: Eslimi, Dariush ; Ildiko Vancsa Cc: starlingx Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Thursday, January 23, 2020 7:35 AM To: Ildiko Vancsa Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Community, I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. Is there any objection to this time window? Thanks, Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-23-20 9:59 AM To: Eslimi, Dariush Cc: starlingx Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility Hi Dariush, Thank you for the quick response. Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. Let me know if I can help with anything else. Thanks, Ildikó > On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: > > Hi Ildiko, > > Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:36 AM > To: starlingx > Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi, > > As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. > > I came across three projects where I didn’t see any meetings on the calendar: > * Config (Configuration) > * Distcloud (Distributed Cloud) > * Flock-Services (StarlingX Flock Services) > > By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. > > Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. > > I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. > > According to my knowledge these projects are all active. Is that an accurate observation? > > Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? > > Thanks and Best Regards, > Ildikó > > [1] https://wiki.openstack.org/wiki/Starlingx/Meetings > [2] https://wiki.openstack.org/wiki/StarlingX/Config > [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud > [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices > [5] https://www.osf.dev/about/four-opens/ > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Fri Jan 24 21:34:28 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 24 Jan 2020 13:34:28 -0800 Subject: [Starlingx-discuss] Using NVME Disks instead of SD In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15DAE67@ALA-MBD.corp.ad.wrs.com> References: <39f925b1-064f-4def-dd8a-99e2e2bad0e3@linux.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15DAE67@ALA-MBD.corp.ad.wrs.com> Message-ID: <09be7ef7-6bce-9d07-8b93-aaa3cd694b4e@linux.intel.com> Ok, so I keep trying some different configurations, I went back to basics and tried a simplex setup and tried to run the set 6 from the AIO simplex docs page [0]. Output of that step: > + system host-disk-list controller-0 > +--------------------------------------+--------------+------------+-------------+----------+---------------+-----+------------------+-------------------------------------------+ > | uuid | device_node | device_num | device_type | size_gib | available_gib | rpm | serial_id | device_path | > +--------------------------------------+--------------+------------+-------------+----------+---------------+-----+------------------+-------------------------------------------+ > | 9e5c01a9-d409-4df2-bc37-b88cbb80f403 | /dev/nvme0n1 | 66304 | NVME | 476.939 | 0.0 | N/A | BTNH907202MD512A | /dev/disk/by-path/pci-0000:72:00.0-nvme-1 | > | c34500df-09d2-497c-a90b-dba1f976bfd0 | /dev/nvme1n1 | 66305 | NVME | 476.939 | 476.937 | N/A | BTNH9072074T512A | /dev/disk/by-path/pci-0000:73:00.0-nvme-1 | > +--------------------------------------+--------------+------------+-------------+----------+---------------+-----+------------------+-------------------------------------------+ > + system host-disk-list controller-0 > + awk '/\/dev\/nvme0n1/{print $2}' > + xargs -i system host-stor-add controller-0 '{}' > Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > + system host-stor-list controller-0 So it seems to require a storage-0 or ceph monitor, which is not mentioned in the docs. Is there something I am missing here? [0] https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_install_kubernetes.html Sau! On 1/14/20 6:22 AM, Penney, Don wrote: > For the second controller and other nodes installing from the active controller, you can set the rootfs_device and boot_device installation parameters via sysinv, either with horizon or the "system host-update" command, such as: > > system host-update 2 personality=controller rootfs_device=/dev/nvme0n1 boot_device=/dev/nvme0n1 > > You can see these settings via host-show: > system host-show controller-1 > > > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Monday, January 13, 2020 4:03 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Using NVME Disks instead of SD > > > Folks, > > I have been trying to get a NUC based deployment work, with Erich's help > we managed to start with a pair of Skull Canyon NUCs running Duplex > controllers. This NUC has a pair of Ethernet ports and can be > configured with 2 NVME-based disks. > > I was able to get the devices booted initially with changes to the ISO > first by hardcoding /dev/nvme0n1 in metal/bsp-files, later Don's tool > helped address alternative boot_device and rootfs_device setting, but I > am not sure it went far enough. Erich figured out that we needed to > patch the sysinv sqlDB (by hand) in order to unlock and make the second > controller usable. > > I went a little further and tried to hook up both work and storage nodes > to create a 2+2+2 Standard lab, I had to hand edit the PXE boot cmdline > and also do the sysinv SQL magic to unlock the compute and storage > nodes, but the Storage configuration still failed. I am thinking there > is still some hardcode "sda" and/or "sdb" in places. > > Any thoughts on how to enable the Storage nodes properly? I can provide > logs, configs, ... > > I realize this is a problem at initial ISO boot/install to select the > drive type, but from there is should be automagically detected on the > target, so it would require setting the drive type of the host at the > same time as setting the personality so that the anaconda at least knows > where to start installing. It may be possible for anaconda to determine > the drive time also. > > Should this be a story, launchpad bug or a Spec to allow use to properly > use NVME devices with StarlingX. Or is this a solved problem that lacks > proper documentation? Yes, we discussed some of this last March, but I > guess it's still a problem and I think it's only going to become more > common. > > Thoughts, direction welcome. > > Thanks > Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Sat Jan 25 00:30:29 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 25 Jan 2020 00:30:29 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 23/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1645C7D@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - January 23 2020 stx.4.0 - New features to consider for 4.0 (brucej) - Intel Vista Creek support - customer request - We already have a feature in stx.4.0 for this - We have been waiting for all the required drivers to be made upstream - Need to influence the time-line of getting the dependent code in the open - Secure Device Onboarding support - https://software.intel.com/en-us/secure-device-onboard - Keep on the watch list -- TBD whether this gets delivered in stx.4.0 - Next step is to work on a spec. Yong Hu will be the prime. - Stretch: ACRN integration - Small footprint industrial hypervisor. - Right now, this is in the exploration phase. Just bringing visibility that Intel will be looking into this. - Stretch: TSN for Kata Containers - We already have a feature in stx.4.0 for this. - Yong will take this over as the prime (instead of Huifeng) - OVS DPDK containerization - Intel cannot take on this work for 4.0 - No issues raised. The release team will consider this out of stx.4.0. - Ceph Containerization/Rook with Bluestore for 4.0 - Intel SH team intends to deliver this - We still need to discuss this at the F2F - Feature is continuing - CentOS 8 - Dependencies are coming in very late. Not much available for StarlingX to make progress. - It would be too much work for the StarlingX team to take on the work to meet the required dependencies - Right now, the work is too big -- including CentOS8, python3 & ceph containerization - Can we divide this into smaller pieces? ...and tackle a smaller scope for stx.4.0 and continue in stx.5.0 - perhaps stick w/ python2 - Need to have a deep dive in with the distro.other team to determine options - Milestone-1 - Criteria - https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Release priorities and major features defined. - High level resourcing secured. - Only concern is the test resource ramp - Bruce is visiting Romania in two weeks.to work out a plan. He feels confident we can succeed. - Agreed to declare the milestone From Ghada.Khalil at windriver.com Sat Jan 25 00:45:43 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 25 Jan 2020 00:45:43 +0000 Subject: [Starlingx-discuss] stx.4.0 Milestone-1 Declared Message-ID: <151EE31B9FCCA54397A757BC674650F0C1645C9F@ALA-MBD.corp.ad.wrs.com> Hello all, The StarlingX release team reviewed the status of stx.4.0 on Jan 23 and agreed to declare Milestone-1 Milestone-1 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Release priorities and major features defined. - High level resourcing secured. A list of proposed features is available at: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Only concern is the test resource ramp - Bruce is working on mitigating this risk in the next few weeks Regards, Ghada & the stx release team From yong.hu at intel.com Mon Jan 27 02:16:04 2020 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 27 Jan 2020 02:16:04 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: When: Tuesday, January 28, 2020 10:00 PM-10:30 PM. (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi Where: https://zoom.us/j/342730236 *~*~*~*~*~*~*~*~*~* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2622 bytes Desc: not available URL: From ildiko.vancsa at gmail.com Mon Jan 27 09:48:11 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Jan 2020 10:48:11 +0100 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: <9A85D2917C58154C960D95352B22818BF165827E@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BF165827E@fmsmsx121.amr.corp.intel.com> Message-ID: <18A37BD4-B73B-43E1-9450-7CB93D5CAA2B@gmail.com> You can also try alternating time slots. Not ideal, but helps sharing the burden caused by time zones. Or utilize IRC more for communication including meetings. What do you think? Thanks, Ildikó > On Jan 24, 2020, at 19:10, Jones, Bruce E wrote: > > I feel your pain, Dariush. There are very few (if any) open alternatives. Perhaps we should consider consolidating our meetings more aggressively or shortening more of the 60 minute calls to 30 minutes so we can fit more calls into those slots. > > brucej > > -----Original Message----- > From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] > Sent: Friday, January 24, 2020 10:00 AM > To: Jones, Bruce E ; Ildiko Vancsa > Cc: starlingx > Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > This is the earliest available slot on Monday, others days of the week also are pretty full. > Unless if we want to break the Meeting Free Fridays? > > Please take a look here : https://wiki.openstack.org/wiki/Starlingx/Meetings > What would you suggest? > > Dariush > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: January-24-20 11:21 AM > To: Eslimi, Dariush ; Ildiko Vancsa > Cc: starlingx > Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. > > brucej > > -----Original Message----- > From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] > Sent: Thursday, January 23, 2020 7:35 AM > To: Ildiko Vancsa > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Community, > > I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. > Is there any objection to this time window? > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:59 AM > To: Eslimi, Dariush > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi Dariush, > > Thank you for the quick response. > > Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. > > Let me know if I can help with anything else. > > Thanks, > Ildikó > > >> On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: >> >> Hi Ildiko, >> >> Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. >> >> Thanks, >> Dariush >> >> -----Original Message----- >> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >> Sent: January-23-20 9:36 AM >> To: starlingx >> Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility >> >> Hi, >> >> As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. >> >> I came across three projects where I didn’t see any meetings on the calendar: >> * Config (Configuration) >> * Distcloud (Distributed Cloud) >> * Flock-Services (StarlingX Flock Services) >> >> By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. >> >> Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. >> >> I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. >> >> According to my knowledge these projects are all active. Is that an accurate observation? >> >> Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? >> >> Thanks and Best Regards, >> Ildikó >> >> [1] https://wiki.openstack.org/wiki/Starlingx/Meetings >> [2] https://wiki.openstack.org/wiki/StarlingX/Config >> [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud >> [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices >> [5] https://www.osf.dev/about/four-opens/ >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Mon Jan 27 09:58:25 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Jan 2020 10:58:25 +0100 Subject: [Starlingx-discuss] Huifeng Le resigning to the stx-networking team In-Reply-To: <76647BD697F40748B1FA4F56DA02AA0B4D6798FC@SHSMSX104.ccr.corp.intel.com> References: <76647BD697F40748B1FA4F56DA02AA0B4D6798FC@SHSMSX104.ccr.corp.intel.com> Message-ID: <34524DEC-5308-4D05-95AC-FFCC5C73D34C@gmail.com> Hi Huifeng, It was great to have you in the StarlingX community and I’m sorry to see you depart. Thank you for all the great work you have been doing in the Networking project and for taking on the leadership role as well to guide the team. I wish you all the best in your new role and I hope you might be able to contribute to StarlingX again in the future. Thanks and Best Regards, Ildikó > On Jan 22, 2020, at 03:01, Le, Huifeng wrote: > > StarlingX Community, > > Due to Internal organizational changes, I have to resign my position as PL and member of the stx-networking team. > > Community TSC will determine the process on who will be taking the responsibilities soon. > > It has been an honor and great working experience to work in the community. Thanks much for all the learnings! > > Best Regards, > Le, Huifeng > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Mon Jan 27 10:01:51 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Jan 2020 11:01:51 +0100 Subject: [Starlingx-discuss] Kristal Dale resigning Documentation team In-Reply-To: References: Message-ID: <35289D14-22A8-4B19-AFD2-F5F6778234AF@gmail.com> Hi Kris, It was great to have you in the StarlingX community and I’m sorry to see you depart. Documentation is an area that is very challenging especially in open source. Hereby I would like to thank you all the amazing work you’ve put into building up the documentation for the StarlingX project. You did a great job working with the community as well as leading the Documentation team, we will miss you. I wish you all the best in your new role and I hope you might be able to contribute to StarlingX again in the future. Thanks and Best Regards, Ildikó > On Jan 23, 2020, at 22:02, Dale, Kristal wrote: > > Hello StarlingX Community, > > Due to organizational changes at Intel, I must resign my position as PTL for the stx-docs team. > > I will be working with Bruce Jones on a transition plan to ensure transfer of knowledge and planning for the upcoming release. > > It has been a pleasure to work on this project and with everyone involved! > > Best, > Kris > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Mon Jan 27 10:14:49 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Jan 2020 11:14:49 +0100 Subject: [Starlingx-discuss] Interim PL elections for open positions - DETAILS and TIMELINE Message-ID: Hi StarlingX Community, As you may have seen on the mailing list we unfortunately have a few people who cannot fulfill their PL responsibilities anymore which leaves us with open positions to fill. Following up on my earlier email[1] based on feedback from the community and TSC we will hold interim elections to find people within the affected teams to step up and take these roles. The project teams looking for new PLs are the following: * Docs * MultiOS * Networking * Test The elections will consist of a nomination period and a voting period both being one week long. The timeline is the following: * PL nomination period: February 10, 2100 UTC - February 17, 2100UTC * PL elections period: February 17, 2100 UTC - February 24, 2100 UTC For details about the elections please check out the elections web page[2]. Please reply to this thread or let the election officials[3] know if you have any questions. Thanks and Best Regards, [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007523.html [2] https://docs.starlingx.io/election/#election-officials [3] https://docs.starlingx.io/election/ From Dariush.Eslimi at windriver.com Mon Jan 27 13:45:18 2020 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 27 Jan 2020 13:45:18 +0000 Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility In-Reply-To: <18A37BD4-B73B-43E1-9450-7CB93D5CAA2B@gmail.com> References: <9A85D2917C58154C960D95352B22818BF165808A@fmsmsx121.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BF165827E@fmsmsx121.amr.corp.intel.com> <18A37BD4-B73B-43E1-9450-7CB93D5CAA2B@gmail.com> Message-ID: I like the alternating idea. Dariush -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: January-27-20 4:48 AM To: starlingx Cc: Eslimi, Dariush ; Jones, Bruce E Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility You can also try alternating time slots. Not ideal, but helps sharing the burden caused by time zones. Or utilize IRC more for communication including meetings. What do you think? Thanks, Ildikó > On Jan 24, 2020, at 19:10, Jones, Bruce E wrote: > > I feel your pain, Dariush. There are very few (if any) open alternatives. Perhaps we should consider consolidating our meetings more aggressively or shortening more of the 60 minute calls to 30 minutes so we can fit more calls into those slots. > > brucej > > -----Original Message----- > From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] > Sent: Friday, January 24, 2020 10:00 AM > To: Jones, Bruce E ; Ildiko Vancsa > Cc: starlingx > Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > This is the earliest available slot on Monday, others days of the week also are pretty full. > Unless if we want to break the Meeting Free Fridays? > > Please take a look here : https://wiki.openstack.org/wiki/Starlingx/Meetings > What would you suggest? > > Dariush > > -----Original Message----- > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] > Sent: January-24-20 11:21 AM > To: Eslimi, Dariush ; Ildiko Vancsa > Cc: starlingx > Subject: RE: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > 8AM Pacific is Midnight in Shanghai, which makes it very hard for our team there to join. > > brucej > > -----Original Message----- > From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] > Sent: Thursday, January 23, 2020 7:35 AM > To: Ildiko Vancsa > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Community, > > I have checked the TL calendars and my own and I am proposing to have the meeting for 3 projects at Monday 8AM Pacific (11 Eastern), bi-weekly. > Is there any objection to this time window? > > Thanks, > Dariush > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: January-23-20 9:59 AM > To: Eslimi, Dariush > Cc: starlingx > Subject: Re: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility > > Hi Dariush, > > Thank you for the quick response. > > Please let me know when the teams identified their meeting slot preferences to make sure there is no collision to use the Zoom account. > > Let me know if I can help with anything else. > > Thanks, > Ildikó > > >> On Jan 23, 2020, at 15:40, Eslimi, Dariush wrote: >> >> Hi Ildiko, >> >> Your observation is accurate, this is my fault and i will send you an email by end of the day Friday to setup a team meeting. >> >> Thanks, >> Dariush >> >> -----Original Message----- >> From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] >> Sent: January-23-20 9:36 AM >> To: starlingx >> Subject: [Starlingx-discuss] [config][distcloud][flock services] Areas to improve team communication and visibility >> >> Hi, >> >> As we have been looking into ways to help new contributors to participate in the community I was checking the meeting calendar[1] and some information available about project teams. >> >> I came across three projects where I didn’t see any meetings on the calendar: >> * Config (Configuration) >> * Distcloud (Distributed Cloud) >> * Flock-Services (StarlingX Flock Services) >> >> By looking at the projects' wiki pages[2][3][4] I couldn’t find much information about where the teams are discussing work items and activities during the release cycles. With following IRC and the mailing list in my experience it’s also hard to spot team activities. >> >> Visible and open communication is very important in terms of the Four Opens[5] that are the guiding principles of the OpenStack Foundation and the projects it supports. The current state also makes it complicated for newcomers to join and chime in to participate so they could eventually become part of the team. >> >> I would be happy to help making improvements, like setting up meetings, discuss tagging mails on the mailing list, etc. >> >> According to my knowledge these projects are all active. Is that an accurate observation? >> >> Do the above teams plan to setup weekly meetings or other ways to make the team communication more visible? Is there anything that I may have missed on the topic? >> >> Thanks and Best Regards, >> Ildikó >> >> [1] https://wiki.openstack.org/wiki/Starlingx/Meetings >> [2] https://wiki.openstack.org/wiki/StarlingX/Config >> [3] https://wiki.openstack.org/wiki/StarlingX/DistCloud >> [4] https://wiki.openstack.org/wiki/StarlingX/FlockServices >> [5] https://www.osf.dev/about/four-opens/ >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From dejan.muhamedagic at tttech-industrial.com Mon Jan 27 14:38:50 2020 From: dejan.muhamedagic at tttech-industrial.com (Dejan Muhamedagic) Date: Mon, 27 Jan 2020 14:38:50 +0000 Subject: [Starlingx-discuss] exposing instance to the public network in the virtual starlingx installation Message-ID: <3a1d5e66c9ccc6d9522cd1994387043402e53032.camel@tttech-industrial.com> Hi, We have a test virtual starlingx AIO-DX installation. One instance should be reachable over the public network (at layer 2). I tried adding a direct (macvtap) interface to the controller-0 libvirt definition. However, after connecting that macvtap interface to the VM instance, the ingress packets are not getting to the instance, most probably because the instance's MAC address is different from the one of the macvtap interface. There's some openstack macvtap documentation: https://docs.openstack.org/neutron/latest/admin/config-macvtap.html but I'm not sure how to create "physical_interface_mapping" with system helm-override-update. Anyway, not quite sure if that would help. Is there a better way to achieve this? Recommendations and tips welcome. Best regards, Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail at tttech.com immediately. From Ian.Jolliffe at windriver.com Mon Jan 27 20:36:15 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Mon, 27 Jan 2020 20:36:15 +0000 Subject: [Starlingx-discuss] [TSC] Meeting notes from January to date Message-ID: Hi all; Sorry for the delay in getting these notes out. For reference our rough notes are on this Etherpad [0] 1/23/2020: Mid-cycle will be happening in Chandler (near Phoenix, AZ), and hosted by Intel (Thank you) March 3/4 This etherpad captures the start of the agenda - Mid-cycle: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup Please add you name if you are planning to attend to allow for logistics planning. All community members are welcome. Figure out how to combine TSC and community meetings. Are there others we should combine? * Discuss at community call 1/29 * Still need to have a focused section for TSC topics – we are experimenting with ways to reduce the number of meetings needed. PL positions - opening up - week of Feb 10th nomination period opens up for 1 week. 1/16/2020: CNCF compatibility testing passed. Ildiko requested TSC review before submission (Brucej) Ada provided update: applied CNCF test suite downloaded the tools, once positive results are achieved, then the certification can be applied for. Test passed -- tagged release 3.0 - official release 276 tests passed – 100% Project gap – upgrades work is not fully staffed under flock services - needs to be discussed with release team - to discuss trade-offs To clarify the gap is the end to end system upgrade (K8S work underway, gaps in openstack and base ) Discussed at PTG 3.0 is gaining adoption, community adoption could be an issue No spec approved - spec date upcoming We all agreed that this is something that needs to be addressed Storage Projects at risk Staffing changes at Intel - Ceph containerization and Bluestore could be impacted 1/9/2020: Project confirmation: Story outline: Timeline chart - Major inflection points and highlights Maybe dashboard on criteria - see Shanghai update – update the Shanghai deck supporting info for the criteria to back up our assessment Info on contributors - Bitergia - need some help here-total 288 contributors until now(from Bitergia) User adoption stories ...pick the key stories to tell. Reducing friction for adoption - what have we done here. Info on test initiatives - summarize hack-a-thon - 1 chart Leverage Shanghai chart deck - board update chart deck. Review as a team determine what actions fall out Input welcome from the community. [0] - https://etherpad.openstack.org/p/stx-cores -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Jan 27 22:02:37 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 27 Jan 2020 22:02:37 +0000 Subject: [Starlingx-discuss] IPv6 Issue introduced by kata container commits Message-ID: <151EE31B9FCCA54397A757BC674650F0C164F9AE@ALA-MBD.corp.ad.wrs.com> Hello all, If you are using an IPv6 env (w/ proxy) with stx master, you may run into an issue where the docker image pull fails: https://bugs.launchpad.net/starlingx/+bug/1859835 This appears to be an issue exposed by the kata containers commits which got merged on 2020-01-21. Shuicheng has identified the root-cause of the issue and Angie will help with the implementation since he's off for Chinese New Year. We hope to have a fix soon. In the meantime, you can locally revert the kata commits to unblock your env. Revert the commits dated Jan 21: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) Regards, Ghada From jim.somerville at windriver.com Mon Jan 27 22:57:11 2020 From: jim.somerville at windriver.com (Jim Somerville) Date: Mon, 27 Jan 2020 17:57:11 -0500 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: Message-ID: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> Hi Folks, Problem (branch master): - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s is due to libvirt-python needing python 3 instead of 2, is nothing related to my change. Anyone know how to get this fixed? CentOS 8 folks, any ideas? Thanks, -Jim -------- Forwarded Message -------- Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use of kernel page pool functionality Date: Mon, 27 Jan 2020 17:39:36 +0000 From: Zuul (Code Review) To: Jim Somerville CC: Victor Manuel Rodriguez Bahena , Robin Lu , Brent Rowsell , Steven Webster , Scott Little , Ghada Khalil , Wendy Mitchell , Don Penney , Saul Wold Zuul has posted comments on this change. ( https://review.opendev.org/704180 ) Change subject: Mellanox Driver: Disable use of kernel page pool functionality ...................................................................... Patch Set 1: Build failed (check pipeline). For information on how to proceed, see http://docs.openstack.org/infra/manual/developers.html#automated-testing - openstack-tox-docs https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 : SUCCESS in 4m 04s - openstack-tox-pep8 https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa : SUCCESS in 4m 52s - openstack-tox-linters https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e : SUCCESS in 4m 18s - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s -- To view, visit https://review.opendev.org/704180 To unsubscribe, visit https://review.opendev.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If7e7155867d539352fcd0ea3acd5a17dd9d9579f Gerrit-PatchSet: 1 Gerrit-Project: starlingx/integ Gerrit-Branch: master Gerrit-Owner: Jim Somerville Gerrit-Reviewer: Brent Rowsell Gerrit-Reviewer: Don Penney Gerrit-Reviewer: Ghada Khalil Gerrit-Reviewer: Jim Somerville Gerrit-Reviewer: Robin Lu Gerrit-Reviewer: Saul Wold Gerrit-Reviewer: Scott Little Gerrit-Reviewer: Steven Webster Gerrit-Reviewer: Victor Manuel Rodriguez Bahena Gerrit-Reviewer: Wendy Mitchell Gerrit-Reviewer: Zuul Gerrit-HasComments: No From shuicheng.lin at intel.com Tue Jan 28 06:49:45 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 28 Jan 2020 06:49:45 +0000 Subject: [Starlingx-discuss] IPv6 Issue introduced by kata container commits In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C164F9AE@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C164F9AE@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C766091669C@SHSMSX105.ccr.corp.intel.com> Hi Angie & Ghada, Thanks very much for the help. Best Regards Shuicheng -----Original Message----- From: Khalil, Ghada Sent: Tuesday, January 28, 2020 6:03 AM To: starlingx-discuss at lists.starlingx.io Cc: Lin, Shuicheng ; Wang, Jing (Angie) Subject: IPv6 Issue introduced by kata container commits Hello all, If you are using an IPv6 env (w/ proxy) with stx master, you may run into an issue where the docker image pull fails: https://bugs.launchpad.net/starlingx/+bug/1859835 This appears to be an issue exposed by the kata containers commits which got merged on 2020-01-21. Shuicheng has identified the root-cause of the issue and Angie will help with the implementation since he's off for Chinese New Year. We hope to have a fix soon. In the meantime, you can locally revert the kata commits to unblock your env. Revert the commits dated Jan 21: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) Regards, Ghada From ildiko.vancsa at gmail.com Tue Jan 28 09:09:29 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 28 Jan 2020 10:09:29 +0100 Subject: [Starlingx-discuss] OSF 2019 Annual Report Message-ID: <5EE61F8B-CCF2-4F1F-9BFD-372EFA6C9F25@gmail.com> Hi StarlingX Community, I’m reaching out to you to draw your attention to the OSF 2019 Annual Report. The projects supported by OSF had a productive year, merging 58k code changes to produce open source infrastructure software like Airship, Kata Containers, StarlingX, and Zuul, along with the third most active OSS project in the world, OpenStack. With 100,000 members and millions more visiting OSF websites in 2019 to get involved, the community made huge strides in addressing the 7.7B market for OpenStack and more than $12B combined OpenStack & Containers markets in the future. Each individual member, working group, SIG, and contributor was instrumental in continuing to support the OSF mission: helping people build and operate open infrastructure. The OSF 2019 Annual Report[1] was published today highlighting the achievements across the community and the goals for the year ahead. Some of the highlights of last year: • The OSF confirmed three new open infrastructure projects to complement OpenStack in powering the world’s open infrastructure; • OpenStack is one of the top three most active open source projects in number of changes, and is projected to be a $7.7 billion USD market by 2023; • Some of the world’s largest brands—AT&T, Baidu, Blizzard Entertainment, BMW, China UnionPay, Walmart, and Volvo among others—shared their open source infrastructure use cases and learnings; • Upstream contributors continued to prioritize cross-project integration with open source projects including Ceph, Kubernetes, Ansible, and Tungsten Fabric. • New contributors were on-boarded through multiple internship and mentoring programs as well as OpenStack Upstream Institute, which was held in seven countries last year! The OSF would like to extend a huge thanks to the global community for all of the work that went into 2019 and is continuing in 2020 to help people build and operate open source infrastructure. Check out the full OSF 2019 Annual Report[1] on the OpenStack website! Thanks and Best Regards, Ildikó [1] https://www.openstack.org/foundation/2019-openstack-foundation-annual-report From Al.Bailey at windriver.com Tue Jan 28 13:35:27 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 28 Jan 2020 13:35:27 +0000 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> Message-ID: A new libvirt-python (6.0.0) was released on Jan 23rd https://pypi.org/project/libvirt-python/#history and it likely only supports py3 I will look into it. Probably just need an upper constraint. Al -----Original Message----- From: Jim Somerville [mailto:jim.somerville at windriver.com] Sent: Monday, January 27, 2020 5:57 PM To: starlingx Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 Hi Folks, Problem (branch master): - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s is due to libvirt-python needing python 3 instead of 2, is nothing related to my change. Anyone know how to get this fixed? CentOS 8 folks, any ideas? Thanks, -Jim -------- Forwarded Message -------- Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use of kernel page pool functionality Date: Mon, 27 Jan 2020 17:39:36 +0000 From: Zuul (Code Review) To: Jim Somerville CC: Victor Manuel Rodriguez Bahena , Robin Lu , Brent Rowsell , Steven Webster , Scott Little , Ghada Khalil , Wendy Mitchell , Don Penney , Saul Wold Zuul has posted comments on this change. ( https://review.opendev.org/704180 ) Change subject: Mellanox Driver: Disable use of kernel page pool functionality ...................................................................... Patch Set 1: Build failed (check pipeline). For information on how to proceed, see http://docs.openstack.org/infra/manual/developers.html#automated-testing - openstack-tox-docs https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 : SUCCESS in 4m 04s - openstack-tox-pep8 https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa : SUCCESS in 4m 52s - openstack-tox-linters https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e : SUCCESS in 4m 18s - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s -- To view, visit https://review.opendev.org/704180 To unsubscribe, visit https://review.opendev.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If7e7155867d539352fcd0ea3acd5a17dd9d9579f Gerrit-PatchSet: 1 Gerrit-Project: starlingx/integ Gerrit-Branch: master Gerrit-Owner: Jim Somerville Gerrit-Reviewer: Brent Rowsell Gerrit-Reviewer: Don Penney Gerrit-Reviewer: Ghada Khalil Gerrit-Reviewer: Jim Somerville Gerrit-Reviewer: Robin Lu Gerrit-Reviewer: Saul Wold Gerrit-Reviewer: Scott Little Gerrit-Reviewer: Steven Webster Gerrit-Reviewer: Victor Manuel Rodriguez Bahena Gerrit-Reviewer: Wendy Mitchell Gerrit-Reviewer: Zuul Gerrit-HasComments: No _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Tue Jan 28 13:53:12 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 28 Jan 2020 13:53:12 +0000 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> Message-ID: Here you go Jim https://review.opendev.org/#/c/704566/ Al -----Original Message----- From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Tuesday, January 28, 2020 8:35 AM To: Somerville, Jim; starlingx Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 A new libvirt-python (6.0.0) was released on Jan 23rd https://pypi.org/project/libvirt-python/#history and it likely only supports py3 I will look into it. Probably just need an upper constraint. Al -----Original Message----- From: Jim Somerville [mailto:jim.somerville at windriver.com] Sent: Monday, January 27, 2020 5:57 PM To: starlingx Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 Hi Folks, Problem (branch master): - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s is due to libvirt-python needing python 3 instead of 2, is nothing related to my change. Anyone know how to get this fixed? CentOS 8 folks, any ideas? Thanks, -Jim -------- Forwarded Message -------- Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use of kernel page pool functionality Date: Mon, 27 Jan 2020 17:39:36 +0000 From: Zuul (Code Review) To: Jim Somerville CC: Victor Manuel Rodriguez Bahena , Robin Lu , Brent Rowsell , Steven Webster , Scott Little , Ghada Khalil , Wendy Mitchell , Don Penney , Saul Wold Zuul has posted comments on this change. ( https://review.opendev.org/704180 ) Change subject: Mellanox Driver: Disable use of kernel page pool functionality ...................................................................... Patch Set 1: Build failed (check pipeline). For information on how to proceed, see http://docs.openstack.org/infra/manual/developers.html#automated-testing - openstack-tox-docs https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 : SUCCESS in 4m 04s - openstack-tox-pep8 https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa : SUCCESS in 4m 52s - openstack-tox-linters https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e : SUCCESS in 4m 18s - stx-integ-pylint https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 : FAILURE in 3m 24s -- To view, visit https://review.opendev.org/704180 To unsubscribe, visit https://review.opendev.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: If7e7155867d539352fcd0ea3acd5a17dd9d9579f Gerrit-PatchSet: 1 Gerrit-Project: starlingx/integ Gerrit-Branch: master Gerrit-Owner: Jim Somerville Gerrit-Reviewer: Brent Rowsell Gerrit-Reviewer: Don Penney Gerrit-Reviewer: Ghada Khalil Gerrit-Reviewer: Jim Somerville Gerrit-Reviewer: Robin Lu Gerrit-Reviewer: Saul Wold Gerrit-Reviewer: Scott Little Gerrit-Reviewer: Steven Webster Gerrit-Reviewer: Victor Manuel Rodriguez Bahena Gerrit-Reviewer: Wendy Mitchell Gerrit-Reviewer: Zuul Gerrit-HasComments: No _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jim.somerville at windriver.com Tue Jan 28 16:01:58 2020 From: jim.somerville at windriver.com (Jim Somerville) Date: Tue, 28 Jan 2020 11:01:58 -0500 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> Message-ID: <09401598-df44-91b5-8f59-3093a239086d@windriver.com> Thanks Al, problem is now gone. -Jim On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote: > Here you go Jim > https://review.opendev.org/#/c/704566/ > > Al > > -----Original Message----- > From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > Sent: Tuesday, January 28, 2020 8:35 AM > To: Somerville, Jim; starlingx > Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > > A new libvirt-python (6.0.0) was released on Jan 23rd > https://pypi.org/project/libvirt-python/#history > > and it likely only supports py3 > > I will look into it. Probably just need an upper constraint. > > Al > > > -----Original Message----- > From: Jim Somerville [mailto:jim.somerville at windriver.com] > Sent: Monday, January 27, 2020 5:57 PM > To: starlingx > Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > Hi Folks, > > Problem (branch master): > > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > > is due to libvirt-python needing python 3 instead of 2, is nothing > related to my change. > > Anyone know how to get this fixed? CentOS 8 folks, any ideas? > > Thanks, > > -Jim > > > -------- Forwarded Message -------- > Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use > of kernel page pool functionality > Date: Mon, 27 Jan 2020 17:39:36 +0000 > From: Zuul (Code Review) > To: Jim Somerville > CC: Victor Manuel Rodriguez Bahena , Robin Lu > , Brent Rowsell , Steven > Webster , Scott Little > , Ghada Khalil , > Wendy Mitchell , Don Penney > , Saul Wold > > Zuul has posted comments on this change. ( > https://review.opendev.org/704180 ) > > Change subject: Mellanox Driver: Disable use of kernel page pool > functionality > ...................................................................... > > > Patch Set 1: > > Build failed (check pipeline). For information on how to proceed, see > http://docs.openstack.org/infra/manual/developers.html#automated-testing > > > - openstack-tox-docs > https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 > : SUCCESS in 4m 04s > - openstack-tox-pep8 > https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa > : SUCCESS in 4m 52s > - openstack-tox-linters > https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e > : SUCCESS in 4m 18s > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > From maria.g.perez.ibarra at intel.com Wed Jan 29 00:12:20 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 29 Jan 2020 00:12:20 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200128 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-28 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Jan 29 01:00:58 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 29 Jan 2020 01:00:58 +0000 Subject: [Starlingx-discuss] IPv6 Issue introduced by kata container commits In-Reply-To: <9700A18779F35F49AF027300A49E7C766091669C@SHSMSX105.ccr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0C164F9AE@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C766091669C@SHSMSX105.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C165123D@ALA-MBD.corp.ad.wrs.com> All, The fix for this issue was merged a few minutes ago. It should be included in tonight's CENGN build. Thanks Shuicheng for determining the root-cause while on vacation and thanks Angie to implementing the fix. Cheers, Ghada -----Original Message----- From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Tuesday, January 28, 2020 1:50 AM To: Wang, Jing (Angie); Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io Subject: RE: IPv6 Issue introduced by kata container commits Hi Angie & Ghada, Thanks very much for the help. Best Regards Shuicheng -----Original Message----- From: Khalil, Ghada Sent: Tuesday, January 28, 2020 6:03 AM To: starlingx-discuss at lists.starlingx.io Cc: Lin, Shuicheng ; Wang, Jing (Angie) Subject: IPv6 Issue introduced by kata container commits Hello all, If you are using an IPv6 env (w/ proxy) with stx master, you may run into an issue where the docker image pull fails: https://bugs.launchpad.net/starlingx/+bug/1859835 This appears to be an issue exposed by the kata containers commits which got merged on 2020-01-21. Shuicheng has identified the root-cause of the issue and Angie will help with the implementation since he's off for Chinese New Year. We hope to have a fix soon. In the meantime, you can locally revert the kata commits to unblock your env. Revert the commits dated Jan 21: https://review.opendev.org/#/q/topic:kata+(status:open+OR+status:merged) Regards, Ghada From build.starlingx at gmail.com Wed Jan 29 02:43:27 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 28 Jan 2020 21:43:27 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 596 - Failure! Message-ID: <1816668116.651.1580265808217.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 596 Status: Failure Timestamp: 20200129T024323Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200129T023003Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200129T023003Z DOCKER_BUILD_ID: jenkins-master-20200129T023003Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200129T023003Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200129T023003Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Jan 29 02:43:30 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 28 Jan 2020 21:43:30 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 399 - Failure! Message-ID: <1782562109.654.1580265811303.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 399 Status: Failure Timestamp: 20200129T023003Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200129T023003Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From build.starlingx at gmail.com Wed Jan 29 02:43:50 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 28 Jan 2020 21:43:50 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 297 - Failure! Message-ID: <338976928.657.1580265831745.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 297 Status: Failure Timestamp: 20200129T024328Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200129T023003Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200129T023003Z DOCKER_BUILD_ID: jenkins-master-20200129T023003Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200129T023003Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20200129T023003Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos From Bill.Zvonar at windriver.com Wed Jan 29 13:41:05 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 29 Jan 2020 13:41:05 +0000 Subject: [Starlingx-discuss] Community Call (Jan 29, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B85533@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call coming up later today. Besides the usual standing topics, the following items are on the agenda for today - feel free to add more at [0]... - the upcoming election - OSF 2019 Annual Report - Mid-Cycle Meetup reminder - combine Community Call & TSC Call? Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200129T1500 From Bill.Zvonar at windriver.com Wed Jan 29 15:47:53 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 29 Jan 2020 15:47:53 +0000 Subject: [Starlingx-discuss] Community Call (Jan 29, 2020) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B85682@ALA-MBD.corp.ad.wrs.com> Notes from our meeting today... - Standing Topics - Sanity - all Green since last week - one issue around Kata Containers though - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007613.html - https://bugs.launchpad.net/starlingx/+bug/1859835 - was related to a specific config - IPv6/Proxy - wasn't tested in this permutation, but general agreement that this wasn't unreasonable - Don asked: would this be considered an upstream bug in containerd? good question - we should ask Shuicheng to ask - Reviews - Kris: some relatively minor updates went out, Kris will ping folks about them - List of reviews: https://review.opendev.org/#/q/owner:kristal.dale%2540intel.com+status:open - Request for Help - Bill will answer: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007611.html - probably an issue in his virtual environment - CentOS 8 - Saul: lots of reviews pending - working towards getting a number of commits merged so testing can continue including those - currently focused on booting the partial ISO - continue refining the staged plan & get key parties into the Distro non-OpenStack meeting next week to focus on that - Topics for This Week - Election: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007609.html - PL nomination period: February 10, 2100 UTC - February 17, 2100UTC - PL elections period: February 17, 2100 UTC - February 24, 2100 UTC - OSF 2019 Annual Report: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-January/007616.html - check it out! - Mid-Cycle Meetup reminder: https://etherpad.openstack.org/p/starlingX-winter-2020-meetup - more folks added to the list, check for other updates on the etherpad - Combine Community Call & TSC Call?: per TSC update https://etherpad.openstack.org/p/stx-cores - Dariush: combining meetings, generally, would help accomodate more meetings - Saul: time-wise, could likely combine Community & TSC, and there's other benefits re: information sharing - we agreed that we will recommend combining Community & TSC on Wednesdays - subject to overruling! - Dariush will run the Flock meetings alternating w/ the Containers meeting - Upgrade: Yesterday is history,tomorrow is a mystery, and today is a gift... that's why they call it present - Dariush: started defining the platform upgrade work - not much of it is staffed at this point, will need help - AR Review - Sep 25, 2019 -- Bill / Doc -- find a place for Sai Chandu's images/documentation - Jan 29: Kris asked to confirm if this is happening on tomorrow's call - Kris will ping Sai Chandu to confirm the meeting is on - Jan 15: this will be added to the agenda for the Build call in 2 weeks time -----Original Message----- From: Zvonar, Bill Sent: Wednesday, January 29, 2020 8:41 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (Jan 29, 2020) Hi all, reminder of the Community call coming up later today. Besides the usual standing topics, the following items are on the agenda for today - feel free to add more at [0]... - the upcoming election - OSF 2019 Annual Report - Mid-Cycle Meetup reminder - combine Community Call & TSC Call? Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200129T1500 From Don.Penney at windriver.com Wed Jan 29 21:15:25 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 29 Jan 2020 21:15:25 +0000 Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC162F46D@ALA-MBD.corp.ad.wrs.com> Hi folks, https://bugs.launchpad.net/starlingx/+bug/1854869 exposed an issue we have with some of our stx-built images. Certain images are referenced statically in platform-installed charts or files that use the master-centos-stable-latest tag, which is updated every time CENGN builds images, whereas the managed applications are able to use the specific image versions from build information. To address this, I'd like to propose a tag management system to complement the image build setup. Workflow: We decide we want to use new functionality introduced in recent build of image Y: * Create a Launchpad to update the image being used * Determine an appropriate version tag to use for the image. For example, if the main project of the image is based on an upstream repo, check the version associated with the SHA used for building the image. If the upstream commit is tagged as v2.2, the image tag to use could be stx.4.0-v2.2. Include this info in the Launchpad. * Update tag management config file, with Partial-Bug: XXXXXX referencing Launchpad. o Include reference to source build tag from loadbuild, using the versioned tag, such as master-centos-stable-20191203T153530Z.0 o Include reference to upstream commit, if appropriate o Include new requested tag * Once tag management config file update is reviewed and merged, tag management utility can be run - as part of CENGN loadbuild, maybe, or perhaps a separate CENGN job that can be triggered by the merge * Once the new tag has been pushed to the docker hub, a follow-up commit can be posted to update the chart or other reference to move to the new image tag, with Closes-Bug in commit message The only cases where we should see charts/manifests or other references to master-centos-stable-latest tag would be files that are inputs to the application build that would be replacing those tags with the specific versioned tags from the loadbuild and are therefore outside the scope of this procedure. This ensures a load is locked down to a specific version of such images, rather than floating to use latest, avoiding compatibility issues that may arise (as in the case of LP 1854869). Example tag management yaml file for stx-4.0: images: - name: docker.io/starlingx/k8s-cni-sriov src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v2.2 - name: docker.io/starlingx/k8s-plugins-sriov-network-device src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v3.1 - name: docker.io/starlingx/intel-fpga-admissionwebhook src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-initcontainer src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-gpu-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-qat-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/d9d92a6997f939cb1ec41813dbf2d72d0b80d79c # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-109-gc48c502 The image retagging utility checks to see if the new tag already exists in the docker repo. If not, it will pull the image using the src_build_tag, retag it with the new tag, and push it. As noted above, this utility can be called by CENGN to handle the retagging - or called manually by a member of the build team with appropriate access permissions. Feedback is welcome. Please let me know if you have any comments or questions. Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Jan 29 21:17:16 2020 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 29 Jan 2020 21:17:16 +0000 Subject: [Starlingx-discuss] [docs][meeting] docs team meeting minutes 2020-01-29 Message-ID: Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2020-01-29 * All -- reviews merged since last week: 3 * Needs review: https://review.opendev.org/#/q/owner:kristal.dale%2540intel.com+status:open (related to config update on docs projects) * All -- bug status -- 2 open and assigned, 1 resolved since last week. * Kris -- Releases * R4.0 - target release date is July 3, 2020. ? Code freeze end of May * Do we know if there will be R2.0.2? - mark invalid. * All -- Ongoing tasks: * Kris -- misc doc clean up -- reviews made, pending approvals. * Kris -- STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Ask author to join build meeting in 2 weeks. Confirmed. ? Suggest I transfer ownership of this coordination now (See if Scott Little can take this.) * Greg (was Abraham) -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required.(Look for email from Greg. Summary: no action required). ? Possible AR (KRIS): terminology clean up. There are storage, worker, and controller nodes. A worker can be labelled as a 'compute' node (a special case of a worker node). * R4 planning: * R4 target content (P1): https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 ? All agreed? ? Will contact project leads to get assigned. * Do we want to ID P2, P3s? <-- GREG: Is this related to 'existing pre-R4 behaviour' not documented ? ? Can't remember where our candidate list was ? ? Prio 2: Should have for R4 release ? Prio 3: Nice to have * Transition plan: https://etherpad.openstack.org/p/docs-transition-plan * Lets finalize. What is missing? * AR: Kris -- add gerrit/git process notes to Bruce's training review (when training is done) StarlingX Docs Storyboard: https://storyboard.openstack.org/#!/story/list?status=active&project_id=1046 StarlingX Docs potential content/tasks: https://etherpad.openstack.org/p/stx-docs-backlog Reviews in progress and recent merges: https://review.opendev.org/#/q/project:starlingx/docs * Open reviews: https://review.opendev.org/#/q/project:starlingx/docs+status:open * Mergable reviews: https://review.opendev.org/#/q/project:starlingx/docs+status:open+is:mergeable Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Jan 30 02:52:55 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 30 Jan 2020 02:52:55 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch Message-ID: Hi Saul : Because mainline has merged some kernel fix , kata feature and some other fixes . would you like to rebase f/centos8 branch from master now ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Jan 30 04:18:53 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 30 Jan 2020 04:18:53 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> Hi Saul, CentOS 8 feature branch also needs below patch, otherwise all patches in integ repo cannot be merged. https://review.opendev.org/704566 Please help rebase master patches to CentOS 8 feature branch. Thanks. Best Regards Shuicheng From: Sun, Austin Sent: Thursday, January 30, 2020 10:53 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] rebase f/centos8 branch Hi Saul : Because mainline has merged some kernel fix , kata feature and some other fixes . would you like to rebase f/centos8 branch from master now ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Jan 30 04:26:31 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 29 Jan 2020 20:26:31 -0800 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> Message-ID: On 1/29/20 8:18 PM, Lin, Shuicheng wrote: > Hi Saul, > > CentOS 8 feature branch also needs below patch, otherwise all patches in > integ repo cannot be merged. > > https://review.opendev.org/704566 > > Please help rebase master patches to CentOS 8 feature branch. > Yes, I am ware of this, I started the rebase this afternoon this one is more complex and I need to do some build testing before I can merge. Sau! > Thanks. > > Best Regards > > Shuicheng > > *From:* Sun, Austin > *Sent:* Thursday, January 30, 2020 10:53 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] rebase f/centos8 branch > > Hi Saul : > >      Because mainline has merged some kernel fix , kata feature and > some other fixes . would you like to rebase f/centos8 branch from master > now ? > > Thanks. > > BR > Austin Sun. > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From ildiko.vancsa at gmail.com Thu Jan 30 09:56:25 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 30 Jan 2020 10:56:25 +0100 Subject: [Starlingx-discuss] Help Shape the Track Content for OpenDev + PTG, June 8-11 in Vancouver Message-ID: <1181B54D-98A7-43E5-9AA0-00D28EFB565A@gmail.com> Hi everyone, Hopefully by now you’ve heard about our upcoming event, OpenDev + PTG Vancouver[1], June 8-11, 2020. We need your help shaping this event! Our vision is for the content to be programmed by you-- the community. OSF is looking to kick things off by selecting members for OpenDev Programming Committees for each Track. That Program Committee will then select Moderators who will lead interactive discussions on a particular topic within the track. Below you'll have the opportunity to nominate yourself for a position on the Programming Committee, as a Moderator, or both, as well as suggesting specific Topics within each Track. PTG programming will kick off in the coming weeks. If you’re interested in volunteering as an OpenDev Programming Committee member, discussion Moderator, or would like to suggest topics for moderated discussions within a particular Track, please __read the details below__, and then fill out this form[2]. We’re looking for subject matter experts on the following OpenDev Tracks: - Hardware Automation (accelerators, provisioning hardware, networking) - Large-scale Usage of Open Source Infrastructure Software (scale pain points, multi-location, CI/CD) - Containers in Production (isolation, virtualization, telecom containers) - Key Challenges for Open Source in 2020 (beyond licensing, public clouds, ethics) __OpenDev Programming Committee__ members will: • Work with other Committee members, which will include OSF representatives, to curate OpenDev content based on subject expertise, community input, and relevance to open source infrastructure • Promote the individual Tracks within your networks • Review community input and suggestions for Track discussions • Solicit moderators from your network if you know someone who is a subject matter expert • Ensure diversity of speakers and companies represented in your Track • Focus topics around on real-world user stories and technical, in-the-trenches experiences Programming Committee members need to be available during the following dates/time commitments: • 8 - 10 hours from February - May for bi-weekly calls with your Track's Programming Committee (plus a couple of OSF representatives to facilitate the call) • OpenDev, June 8 - 10, 2020 (not required, but preferred) • Programming Committee members will receive a complimentary pass to the event Programming Committees will be comprised of a few people per Track who will work to select a handful of topics and moderators for each Track. The exact topic counts will be determined before Committees begin deciding. __OpenDev Discussion Moderators__ will • Be appointed by the Programming Committees • Facilitate discussions within a particular Track • Have adequate knowledge and experience to lead and moderate discussion around certain topics during the event • Work with Programming Committee to decide focal point of discussion Moderators need to be available to attend OpenDev, June 8 - 10, 2020, and will receive a complimentary pass. Programming Committee nominations are open until __February 11__. Deadlines to volunteer to be a moderator and suggest topics will be in late February. Nominate yourself or suggest discussion topics here: https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer Cheers, The OpenStack Foundation [1] https://opendevptg2020.eventbrite.com/ [2] https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer From Greg.Waines at windriver.com Thu Jan 30 13:45:00 2020 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 30 Jan 2020 13:45:00 +0000 Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) Message-ID: Sounds reasonable to me. Only question on tag convention, would we prefix with ‘stx..’ Or just ‘stx.’, since, I am guessing that the container image may not require re-building from one stx release to another ? Greg. From: "Penney, Don" Date: Wednesday, January 29, 2020 at 4:18 PM To: "'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io)" Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) Hi folks, https://bugs.launchpad.net/starlingx/+bug/1854869 exposed an issue we have with some of our stx-built images. Certain images are referenced statically in platform-installed charts or files that use the master-centos-stable-latest tag, which is updated every time CENGN builds images, whereas the managed applications are able to use the specific image versions from build information. To address this, I’d like to propose a tag management system to complement the image build setup. Workflow: We decide we want to use new functionality introduced in recent build of image Y: * Create a Launchpad to update the image being used * Determine an appropriate version tag to use for the image. For example, if the main project of the image is based on an upstream repo, check the version associated with the SHA used for building the image. If the upstream commit is tagged as v2.2, the image tag to use could be stx.4.0-v2.2. Include this info in the Launchpad. * Update tag management config file, with Partial-Bug: XXXXXX referencing Launchpad. * Include reference to source build tag from loadbuild, using the versioned tag, such as master-centos-stable-20191203T153530Z.0 * Include reference to upstream commit, if appropriate * Include new requested tag * Once tag management config file update is reviewed and merged, tag management utility can be run - as part of CENGN loadbuild, maybe, or perhaps a separate CENGN job that can be triggered by the merge * Once the new tag has been pushed to the docker hub, a follow-up commit can be posted to update the chart or other reference to move to the new image tag, with Closes-Bug in commit message The only cases where we should see charts/manifests or other references to master-centos-stable-latest tag would be files that are inputs to the application build that would be replacing those tags with the specific versioned tags from the loadbuild and are therefore outside the scope of this procedure. This ensures a load is locked down to a specific version of such images, rather than floating to use latest, avoiding compatibility issues that may arise (as in the case of LP 1854869). Example tag management yaml file for stx-4.0: images: - name: docker.io/starlingx/k8s-cni-sriov src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v2.2 - name: docker.io/starlingx/k8s-plugins-sriov-network-device src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v3.1 - name: docker.io/starlingx/intel-fpga-admissionwebhook src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-initcontainer src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-gpu-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-qat-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/d9d92a6997f939cb1ec41813dbf2d72d0b80d79c # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-109-gc48c502 The image retagging utility checks to see if the new tag already exists in the docker repo. If not, it will pull the image using the src_build_tag, retag it with the new tag, and push it. As noted above, this utility can be called by CENGN to handle the retagging - or called manually by a member of the build team with appropriate access permissions. Feedback is welcome. Please let me know if you have any comments or questions. Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Jan 30 14:59:38 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 30 Jan 2020 14:59:38 +0000 Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC162F6D4@ALA-MBD.corp.ad.wrs.com> The main reason I suggested the stx.## is to avoid version conflicts between branches. Otherwise, I’d drop the stx.## altogether and just have a simple version number. For example, an image gets updated post-release in r/stx.3.0 and rebuilt to pull in a fix, and gets tagged as v1.1. The same image gets updated in master for the fix, but also has some underlying differences in an installed package or some other behavioural change, and gets tagged as v1.1. When the second request comes along for the same tag, the tag management utility would just see this as “tag already exists, nothing to do”. This doesn’t mean we’d have to update the image tag on every release, of course. If the stx.3.0 image is still fine in master, we could just keep using the older image and not update the tag. Or we can update the tag, but keep the same original source image. From: Waines, Greg Sent: Thursday, January 30, 2020 8:45 AM To: Penney, Don; 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: Re: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) Sounds reasonable to me. Only question on tag convention, would we prefix with ‘stx..’ Or just ‘stx.’, since, I am guessing that the container image may not require re-building from one stx release to another ? Greg. From: "Penney, Don" Date: Wednesday, January 29, 2020 at 4:18 PM To: "'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io)" Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) Hi folks, https://bugs.launchpad.net/starlingx/+bug/1854869 exposed an issue we have with some of our stx-built images. Certain images are referenced statically in platform-installed charts or files that use the master-centos-stable-latest tag, which is updated every time CENGN builds images, whereas the managed applications are able to use the specific image versions from build information. To address this, I’d like to propose a tag management system to complement the image build setup. Workflow: We decide we want to use new functionality introduced in recent build of image Y: * Create a Launchpad to update the image being used * Determine an appropriate version tag to use for the image. For example, if the main project of the image is based on an upstream repo, check the version associated with the SHA used for building the image. If the upstream commit is tagged as v2.2, the image tag to use could be stx.4.0-v2.2. Include this info in the Launchpad. * Update tag management config file, with Partial-Bug: XXXXXX referencing Launchpad. * Include reference to source build tag from loadbuild, using the versioned tag, such as master-centos-stable-20191203T153530Z.0 * Include reference to upstream commit, if appropriate * Include new requested tag * Once tag management config file update is reviewed and merged, tag management utility can be run - as part of CENGN loadbuild, maybe, or perhaps a separate CENGN job that can be triggered by the merge * Once the new tag has been pushed to the docker hub, a follow-up commit can be posted to update the chart or other reference to move to the new image tag, with Closes-Bug in commit message The only cases where we should see charts/manifests or other references to master-centos-stable-latest tag would be files that are inputs to the application build that would be replacing those tags with the specific versioned tags from the loadbuild and are therefore outside the scope of this procedure. This ensures a load is locked down to a specific version of such images, rather than floating to use latest, avoiding compatibility issues that may arise (as in the case of LP 1854869). Example tag management yaml file for stx-4.0: images: - name: docker.io/starlingx/k8s-cni-sriov src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v2.2 - name: docker.io/starlingx/k8s-plugins-sriov-network-device src_build_tag: master-centos-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 # Tag determined based on release tag associated with upstream commit tag: stx.4.0-v3.1 - name: docker.io/starlingx/intel-fpga-admissionwebhook src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-initcontainer src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-fpga-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-gpu-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-103-g4f28657 - name: docker.io/starlingx/intel-qat-plugin src_build_tag: master-distroless-stable-20191203T153530Z.0 src_ref: https://opendev.org/starlingx/integ/commit/d9d92a6997f939cb1ec41813dbf2d72d0b80d79c # Version determined by running 'git describe --tags' in clone of upstream repo tag: stx.4.0-v0.11.0-109-gc48c502 The image retagging utility checks to see if the new tag already exists in the docker repo. If not, it will pull the image using the src_build_tag, retag it with the new tag, and push it. As noted above, this utility can be called by CENGN to handle the retagging - or called manually by a member of the build team with appropriate access permissions. Feedback is welcome. Please let me know if you have any comments or questions. Thanks, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jan 30 17:05:11 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 30 Jan 2020 18:05:11 +0100 Subject: [Starlingx-discuss] ONS North America CFP is closing soon Message-ID: <9342A8B4-1BC7-41E4-B040-D7853FD92E97@gmail.com> Hi, As ONS North America is adding Edge to the conference theme as well it’s a good place for the project to be represented. I wanted to give a friendly reminder that the CFP[1] is closing next Monday (February 3), at 11:59 PM PST. If you’re considering to submit a talk you still have a few days to put together the proposal. Thanks, Ildikó [1] https://events.linuxfoundation.org/open-networking-edge-summit-north-america/program/cfp/#overview From jim.somerville at windriver.com Thu Jan 30 17:19:25 2020 From: jim.somerville at windriver.com (Jim Somerville) Date: Thu, 30 Jan 2020 12:19:25 -0500 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> Message-ID: <29784e5e-06c4-b8c8-0e70-cf764482c761@windriver.com> On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote: > Here you go Jim > https://review.opendev.org/#/c/704566/ Hi Al, Is it safe to backport that to r/2.0 and r/3.0? -Jim > > Al > > -----Original Message----- > From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > Sent: Tuesday, January 28, 2020 8:35 AM > To: Somerville, Jim; starlingx > Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > > A new libvirt-python (6.0.0) was released on Jan 23rd > https://pypi.org/project/libvirt-python/#history > > and it likely only supports py3 > > I will look into it. Probably just need an upper constraint. > > Al > > > -----Original Message----- > From: Jim Somerville [mailto:jim.somerville at windriver.com] > Sent: Monday, January 27, 2020 5:57 PM > To: starlingx > Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > Hi Folks, > > Problem (branch master): > > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > > is due to libvirt-python needing python 3 instead of 2, is nothing > related to my change. > > Anyone know how to get this fixed? CentOS 8 folks, any ideas? > > Thanks, > > -Jim > > > -------- Forwarded Message -------- > Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use > of kernel page pool functionality > Date: Mon, 27 Jan 2020 17:39:36 +0000 > From: Zuul (Code Review) > To: Jim Somerville > CC: Victor Manuel Rodriguez Bahena , Robin Lu > , Brent Rowsell , Steven > Webster , Scott Little > , Ghada Khalil , > Wendy Mitchell , Don Penney > , Saul Wold > > Zuul has posted comments on this change. ( > https://review.opendev.org/704180 ) > > Change subject: Mellanox Driver: Disable use of kernel page pool > functionality > ...................................................................... > > > Patch Set 1: > > Build failed (check pipeline). For information on how to proceed, see > http://docs.openstack.org/infra/manual/developers.html#automated-testing > > > - openstack-tox-docs > https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 > : SUCCESS in 4m 04s > - openstack-tox-pep8 > https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa > : SUCCESS in 4m 52s > - openstack-tox-linters > https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e > : SUCCESS in 4m 18s > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > From Al.Bailey at windriver.com Thu Jan 30 17:36:40 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 30 Jan 2020 17:36:40 +0000 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: <29784e5e-06c4-b8c8-0e70-cf764482c761@windriver.com> References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> <29784e5e-06c4-b8c8-0e70-cf764482c761@windriver.com> Message-ID: It should be fine to cherry pick to 3.0 I am not sure if 2.0 would be a clean pick (we renamed repos at some point) Al -----Original Message----- From: Jim Somerville [mailto:jim.somerville at windriver.com] Sent: Thursday, January 30, 2020 12:19 PM To: Bailey, Henry Albert (Al); starlingx Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote: > Here you go Jim > https://review.opendev.org/#/c/704566/ Hi Al, Is it safe to backport that to r/2.0 and r/3.0? -Jim > > Al > > -----Original Message----- > From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] > Sent: Tuesday, January 28, 2020 8:35 AM > To: Somerville, Jim; starlingx > Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > > A new libvirt-python (6.0.0) was released on Jan 23rd > https://pypi.org/project/libvirt-python/#history > > and it likely only supports py3 > > I will look into it. Probably just need an upper constraint. > > Al > > > -----Original Message----- > From: Jim Somerville [mailto:jim.somerville at windriver.com] > Sent: Monday, January 27, 2020 5:57 PM > To: starlingx > Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > Hi Folks, > > Problem (branch master): > > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > > is due to libvirt-python needing python 3 instead of 2, is nothing > related to my change. > > Anyone know how to get this fixed? CentOS 8 folks, any ideas? > > Thanks, > > -Jim > > > -------- Forwarded Message -------- > Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use > of kernel page pool functionality > Date: Mon, 27 Jan 2020 17:39:36 +0000 > From: Zuul (Code Review) > To: Jim Somerville > CC: Victor Manuel Rodriguez Bahena , Robin Lu > , Brent Rowsell , Steven > Webster , Scott Little > , Ghada Khalil , > Wendy Mitchell , Don Penney > , Saul Wold > > Zuul has posted comments on this change. ( > https://review.opendev.org/704180 ) > > Change subject: Mellanox Driver: Disable use of kernel page pool > functionality > ...................................................................... > > > Patch Set 1: > > Build failed (check pipeline). For information on how to proceed, see > http://docs.openstack.org/infra/manual/developers.html#automated-testing > > > - openstack-tox-docs > https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 > : SUCCESS in 4m 04s > - openstack-tox-pep8 > https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa > : SUCCESS in 4m 52s > - openstack-tox-linters > https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e > : SUCCESS in 4m 18s > - stx-integ-pylint > https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 > : FAILURE in 3m 24s > From jim.somerville at windriver.com Thu Jan 30 18:42:47 2020 From: jim.somerville at windriver.com (Jim Somerville) Date: Thu, 30 Jan 2020 13:42:47 -0500 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> <29784e5e-06c4-b8c8-0e70-cf764482c761@windriver.com> Message-ID: On 2020-01-30 12:36 p.m., Bailey, Henry Albert (Al) wrote: > It should be fine to cherry pick to 3.0 > I am not sure if 2.0 would be a clean pick (we renamed repos at some point) I attempted the 2.0 cherry pick but it fails with a strange invocation error in the zuul check of stx-integ-pylint https://review.opendev.org/#/c/705077/ Possible chicken and egg issue? -Jim > > Al > > -----Original Message----- > From: Jim Somerville [mailto:jim.somerville at windriver.com] > Sent: Thursday, January 30, 2020 12:19 PM > To: Bailey, Henry Albert (Al); starlingx > Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > > > On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote: >> Here you go Jim >> https://review.opendev.org/#/c/704566/ > > Hi Al, > > Is it safe to backport that to r/2.0 and r/3.0? > > -Jim > >> >> Al >> >> -----Original Message----- >> From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] >> Sent: Tuesday, January 28, 2020 8:35 AM >> To: Somerville, Jim; starlingx >> Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 >> >> >> A new libvirt-python (6.0.0) was released on Jan 23rd >> https://pypi.org/project/libvirt-python/#history >> >> and it likely only supports py3 >> >> I will look into it. Probably just need an upper constraint. >> >> Al >> >> >> -----Original Message----- >> From: Jim Somerville [mailto:jim.somerville at windriver.com] >> Sent: Monday, January 27, 2020 5:57 PM >> To: starlingx >> Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 >> >> Hi Folks, >> >> Problem (branch master): >> >> - stx-integ-pylint >> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 >> : FAILURE in 3m 24s >> >> is due to libvirt-python needing python 3 instead of 2, is nothing >> related to my change. >> >> Anyone know how to get this fixed? CentOS 8 folks, any ideas? >> >> Thanks, >> >> -Jim >> >> >> -------- Forwarded Message -------- >> Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use >> of kernel page pool functionality >> Date: Mon, 27 Jan 2020 17:39:36 +0000 >> From: Zuul (Code Review) >> To: Jim Somerville >> CC: Victor Manuel Rodriguez Bahena , Robin Lu >> , Brent Rowsell , Steven >> Webster , Scott Little >> , Ghada Khalil , >> Wendy Mitchell , Don Penney >> , Saul Wold >> >> Zuul has posted comments on this change. ( >> https://review.opendev.org/704180 ) >> >> Change subject: Mellanox Driver: Disable use of kernel page pool >> functionality >> ...................................................................... >> >> >> Patch Set 1: >> >> Build failed (check pipeline). For information on how to proceed, see >> http://docs.openstack.org/infra/manual/developers.html#automated-testing >> >> >> - openstack-tox-docs >> https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 >> : SUCCESS in 4m 04s >> - openstack-tox-pep8 >> https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa >> : SUCCESS in 4m 52s >> - openstack-tox-linters >> https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e >> : SUCCESS in 4m 18s >> - stx-integ-pylint >> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 >> : FAILURE in 3m 24s >> From Ian.Jolliffe at windriver.com Thu Jan 30 19:08:50 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 30 Jan 2020 19:08:50 +0000 Subject: [Starlingx-discuss] ONS North America CFP is closing soon In-Reply-To: <9342A8B4-1BC7-41E4-B040-D7853FD92E97@gmail.com> References: <9342A8B4-1BC7-41E4-B040-D7853FD92E97@gmail.com> Message-ID: <795D60B5-3246-4CEB-AD3D-2EC46B9E78BB@windriver.com> Hi Ildiko; I am working on a proposal for ONS, and thanks for the reminder. Ian On 2020-01-30, 12:07 PM, "Ildiko Vancsa" wrote: Hi, As ONS North America is adding Edge to the conference theme as well it’s a good place for the project to be represented. I wanted to give a friendly reminder that the CFP[1] is closing next Monday (February 3), at 11:59 PM PST. If you’re considering to submit a talk you still have a few days to put together the proposal. Thanks, Ildikó [1] https://events.linuxfoundation.org/open-networking-edge-summit-north-america/program/cfp/#overview _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Thu Jan 30 19:11:08 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 30 Jan 2020 19:11:08 +0000 Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 In-Reply-To: References: <7107690f-04c3-3d39-0887-c99bbc6fe790@windriver.com> <29784e5e-06c4-b8c8-0e70-cf764482c761@windriver.com> Message-ID: I amended your cherry-pick review for the 2.0 branch. It should pass now. Al -----Original Message----- From: Jim Somerville [mailto:jim.somerville at windriver.com] Sent: Thursday, January 30, 2020 1:43 PM To: Bailey, Henry Albert (Al); starlingx Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 On 2020-01-30 12:36 p.m., Bailey, Henry Albert (Al) wrote: > It should be fine to cherry pick to 3.0 > I am not sure if 2.0 would be a clean pick (we renamed repos at some point) I attempted the 2.0 cherry pick but it fails with a strange invocation error in the zuul check of stx-integ-pylint https://review.opendev.org/#/c/705077/ Possible chicken and egg issue? -Jim > > Al > > -----Original Message----- > From: Jim Somerville [mailto:jim.somerville at windriver.com] > Sent: Thursday, January 30, 2020 12:19 PM > To: Bailey, Henry Albert (Al); starlingx > Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 > > > > On 2020-01-28 8:53 a.m., Bailey, Henry Albert (Al) wrote: >> Here you go Jim >> https://review.opendev.org/#/c/704566/ > > Hi Al, > > Is it safe to backport that to r/2.0 and r/3.0? > > -Jim > >> >> Al >> >> -----Original Message----- >> From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] >> Sent: Tuesday, January 28, 2020 8:35 AM >> To: Somerville, Jim; starlingx >> Subject: Re: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 >> >> >> A new libvirt-python (6.0.0) was released on Jan 23rd >> https://pypi.org/project/libvirt-python/#history >> >> and it likely only supports py3 >> >> I will look into it. Probably just need an upper constraint. >> >> Al >> >> >> -----Original Message----- >> From: Jim Somerville [mailto:jim.somerville at windriver.com] >> Sent: Monday, January 27, 2020 5:57 PM >> To: starlingx >> Subject: [Starlingx-discuss] stx-integ-pylint failure due to python 2 vs. 3 >> >> Hi Folks, >> >> Problem (branch master): >> >> - stx-integ-pylint >> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 >> : FAILURE in 3m 24s >> >> is due to libvirt-python needing python 3 instead of 2, is nothing >> related to my change. >> >> Anyone know how to get this fixed? CentOS 8 folks, any ideas? >> >> Thanks, >> >> -Jim >> >> >> -------- Forwarded Message -------- >> Subject: Change in starlingx/integ[master]: Mellanox Driver: Disable use >> of kernel page pool functionality >> Date: Mon, 27 Jan 2020 17:39:36 +0000 >> From: Zuul (Code Review) >> To: Jim Somerville >> CC: Victor Manuel Rodriguez Bahena , Robin Lu >> , Brent Rowsell , Steven >> Webster , Scott Little >> , Ghada Khalil , >> Wendy Mitchell , Don Penney >> , Saul Wold >> >> Zuul has posted comments on this change. ( >> https://review.opendev.org/704180 ) >> >> Change subject: Mellanox Driver: Disable use of kernel page pool >> functionality >> ...................................................................... >> >> >> Patch Set 1: >> >> Build failed (check pipeline). For information on how to proceed, see >> http://docs.openstack.org/infra/manual/developers.html#automated-testing >> >> >> - openstack-tox-docs >> https://zuul.opendev.org/t/openstack/build/cbee2ab21a7c4cf1b123e5da5299fd74 >> : SUCCESS in 4m 04s >> - openstack-tox-pep8 >> https://zuul.opendev.org/t/openstack/build/11fb173c3490482eb2902a46957e2caa >> : SUCCESS in 4m 52s >> - openstack-tox-linters >> https://zuul.opendev.org/t/openstack/build/1a614a32943143b6bdcbf7a145f05c9e >> : SUCCESS in 4m 18s >> - stx-integ-pylint >> https://zuul.opendev.org/t/openstack/build/c8704619a95443ee8a049985061bfb57 >> : FAILURE in 3m 24s >> From scott.little at windriver.com Thu Jan 30 20:39:32 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 30 Jan 2020 15:39:32 -0500 Subject: [Starlingx-discuss] [important] Build layering Message-ID: The build layering feature is coming soon. *Code reviews* have been posted ... https://review.opendev.org/#/c/700819/2 https://review.opendev.org/#/c/700821/9 https://review.opendev.org/#/c/681821/28 https://review.opendev.org/#/c/705092/ *D**ocumentation* can be found in the fourth review, here .... https://review.opendev.org/gitweb?p=starlingx/docs.git;a=blob;f=doc/source/developer_resources/Layered_Build.rst;h=6f945d8d33f70bd91594033fcfa6abaf6271056d;hb=2a6abc988c9a52321982015831b12819586546df *Want to try it out before it merges? * I've set up a modified manifest that pulls in the required updates .... One of ...    repo init -u https://opendev.org/starlingx/manifest.git -b refs/changes/04/705104/2 -m compile.xml    repo init -u https://opendev.org/starlingx/manifest.git -b refs/changes/04/705104/2 -m distro.xml    repo init -u https://opendev.org/starlingx/manifest.git -b refs/changes/04/705104/2 -m flock.xml followed by:    repo sync Scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Jan 30 20:58:38 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 30 Jan 2020 12:58:38 -0800 Subject: [Starlingx-discuss] [important] Build layering In-Reply-To: References: Message-ID: Thanks very much to Scott, Don, Bin Yang, and others who have been working on this update to the build system. Sau! On 1/30/20 12:39 PM, Scott Little wrote: > The build layering feature is coming soon. > > > *Code reviews* have been posted ... > > https://review.opendev.org/#/c/700819/2 > > https://review.opendev.org/#/c/700821/9 > > https://review.opendev.org/#/c/681821/28 > > https://review.opendev.org/#/c/705092/ > > > *D**ocumentation* can be found in the fourth review, here .... > > https://review.opendev.org/gitweb?p=starlingx/docs.git;a=blob;f=doc/source/developer_resources/Layered_Build.rst;h=6f945d8d33f70bd91594033fcfa6abaf6271056d;hb=2a6abc988c9a52321982015831b12819586546df > > > *Want to try it out before it merges? * > > I've set up a modified manifest that pulls in the required updates .... > > One of ... > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m compile.xml > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m distro.xml > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m flock.xml > > > followed by: > >    repo sync > > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Thu Jan 30 21:15:36 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 30 Jan 2020 21:15:36 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Jan 30/2020 Message-ID: <151EE31B9FCCA54397A757BC674650F0C1653009@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - January 30 2020 stx.4.0 - Milestone-1 declared last week - Feature Plans: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Went through feature list and added updates - Another new feature to consider for 4.0 (brucej) - upgrade the kernel in StarlingX from 4.18 to 4.19 or newer, to enable support of TSN in containers - Added to the Feature Plans spreadsheet stx.2.0.2 - OVMF is still waiting on the stx-nova staging change. Need to follow-up with Yong. - Also waiting for the following LPs: - https://bugs.launchpad.net/starlingx/+bug/1838659 -- k8s certificate rotation - https://bugs.launchpad.net/starlingx/+bug/1860347 -- mellanox driver fix - https://bugs.launchpad.net/starlingx/+bug/1860193 -- nospectre_v1 configuration change - Once the above items are merged, we can proceed with a mtce RC build, but need to discuss the test team availability to run sanity/regression on the mtce release stx.3.0.1 - TBD -- no plan yet - Items to be cherrypicked: - https://bugs.launchpad.net/starlingx/+bug/1838659 -- k8s certificate rotation - https://bugs.launchpad.net/starlingx/+bug/1860347 -- mellanox driver fix - https://bugs.launchpad.net/starlingx/+bug/1860193 -- nospectre_v1 configuration change - Any others? From build.starlingx at gmail.com Thu Jan 30 21:48:13 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Jan 2020 16:48:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 26 - Failure! Message-ID: <104220859.663.1580420894593.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 26 Status: Failure Timestamp: 20200130T214809Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200130T213619Z DOCKER_BUILD_ID: jenkins-master-compiler-20200130T213619Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master LAYER: compiler MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler BUILD_ISO: false From build.starlingx at gmail.com Thu Jan 30 21:48:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Jan 2020 16:48:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 300 - Failure! Message-ID: <2042739689.667.1580420917836.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 300 Status: Failure Timestamp: 20200130T214814Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-compiler/20200130T213619Z DOCKER_BUILD_ID: jenkins-master-compiler-20200130T213619Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-compiler/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/compiler/20200130T213619Z/logs MASTER_JOB_NAME: STX_build_layer_compiler_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-compiler PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/compiler From sgw at linux.intel.com Thu Jan 30 22:21:22 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 30 Jan 2020 14:21:22 -0800 Subject: [Starlingx-discuss] Proposal: Tag management for statically referenced container images (LP: 1854869) In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC162F46D@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC162F46D@ALA-MBD.corp.ad.wrs.com> Message-ID: Folks, A quick update, Don and I had a chat on IRC about this, I am still not sure I fully understand the issue yet. One of the questions I had was where we could also leverage PBR somehow rather than introduce a new/different versioning system. While PBR does version on a package level, the version is available at the repo level also since it offsets from a known version followed by number of commit, so a x.y.z- is available to useto help version or tag the images. It seems that this adds additional complexity to an already complex build system. I will continue to study this. Sau! On 1/29/20 1:15 PM, Penney, Don wrote: > Hi folks, > > https://bugs.launchpad.net/starlingx/+bug/1854869 exposed an issue we > have with some of our stx-built images. Certain images are referenced > statically in platform-installed charts or files that use the > master-centos-stable-latest tag, which is updated every time CENGN > builds images, whereas the managed applications are able to use the > specific image versions from build information. > > To address this, I’d like to propose a tag management system to > complement the image build setup. > > Workflow: > > We decide we want to use new functionality introduced in recent build of > image Y: > > ·Create a Launchpad to update the image being used > > ·Determine an appropriate version tag to use for the image. For example, > if the main project of the image is based on an upstream repo, check the > version associated with the SHA used for building the image. If the > upstream commit is tagged as v2.2, the image tag to use could be > stx.4.0-v2.2. Include this info in the Launchpad. > > ·Update tag management config file, with Partial-Bug: XXXXXX referencing > Launchpad. > > oInclude reference to source build tag from loadbuild, using the > versioned tag, such as master-centos-stable-20191203T153530Z.0 > > oInclude reference to upstream commit, if appropriate > > oInclude new requested tag > > ·Once tag management config file update is reviewed and merged, tag > management utility can be run - as part of CENGN loadbuild, maybe, or > perhaps a separate CENGN job that can be triggered by the merge > > ·Once the new tag has been pushed to the docker hub, a follow-up commit > can be posted to update the chart or other reference to move to the new > image tag, with Closes-Bug in commit message > > The only cases where we should see charts/manifests or other references > to master-centos-stable-latest tag would be files that are inputs to the > application build that would be replacing those tags with the specific > versioned tags from the loadbuild and are therefore outside the scope of > this procedure. > > This ensures a load is locked down to a specific version of such images, > rather than floating to use latest, avoiding compatibility issues that > may arise (as in the case of LP 1854869). > > Example tag management yaml file for stx-4.0: > > images: > >   - name: docker.io/starlingx/k8s-cni-sriov > >     src_build_tag: master-centos-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 > >     # Tag determined based on release tag associated with upstream commit > >     tag: stx.4.0-v2.2 > >   - name: docker.io/starlingx/k8s-plugins-sriov-network-device > >     src_build_tag: master-centos-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/dac417bd31ed36d455e94db4aabe5916367654d4 > >     # Tag determined based on release tag associated with upstream commit > >     tag: stx.4.0-v3.1 > >   - name: docker.io/starlingx/intel-fpga-admissionwebhook > >     src_build_tag: master-distroless-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 > >     # Version determined by running 'git describe --tags' in clone of > upstream repo > >     tag: stx.4.0-v0.11.0-103-g4f28657 > >   - name: docker.io/starlingx/intel-fpga-initcontainer > >     src_build_tag: master-distroless-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 > >     # Version determined by running 'git describe --tags' in clone of > upstream repo > >     tag: stx.4.0-v0.11.0-103-g4f28657 > >   - name: docker.io/starlingx/intel-fpga-plugin > >     src_build_tag: master-distroless-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 > >     # Version determined by running 'git describe --tags' in clone of > upstream repo > >     tag: stx.4.0-v0.11.0-103-g4f28657 > >   - name: docker.io/starlingx/intel-gpu-plugin > >     src_build_tag: master-distroless-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/5f72ddb26a38d41fef919060585daaafae677433 > >     # Version determined by running 'git describe --tags' in clone of > upstream repo > >     tag: stx.4.0-v0.11.0-103-g4f28657 > >   - name: docker.io/starlingx/intel-qat-plugin > >     src_build_tag: master-distroless-stable-20191203T153530Z.0 > >     src_ref: > https://opendev.org/starlingx/integ/commit/d9d92a6997f939cb1ec41813dbf2d72d0b80d79c > >     # Version determined by running 'git describe --tags' in clone of > upstream repo > >     tag: stx.4.0-v0.11.0-109-gc48c502 > > The image retagging utility checks to see if the new tag already exists > in the docker repo. If not, it will pull the image using the > src_build_tag, retag it with the new tag, and push it. As noted above, > this utility can be called by CENGN to handle the retagging - or called > manually by a member of the build team with appropriate access permissions. > > Feedback is welcome. Please let me know if you have any comments or > questions. > > Thanks, > > Don. > > *Don Penney*, Developer, *Wind River* > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From maria.g.perez.ibarra at intel.com Thu Jan 30 23:34:26 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 30 Jan 2020 23:34:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200130 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-30 (link) Status: GREEN Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] ---------------------------------------------- We do not have the BareMetal results due to internal problems. regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Jan 30 23:43:53 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 30 Jan 2020 15:43:53 -0800 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> Message-ID: <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> A quick update. Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. Sau! On 1/29/20 8:26 PM, Saul Wold wrote: > > > On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >> Hi Saul, >> >> CentOS 8 feature branch also needs below patch, otherwise all patches >> in integ repo cannot be merged. >> >> https://review.opendev.org/704566 >> >> Please help rebase master patches to CentOS 8 feature branch. >> > Yes, I am ware of this, I started the rebase this afternoon this one is > more complex and I need to do some build testing before I can merge. > > Sau! > >> Thanks. >> >> Best Regards >> >> Shuicheng >> >> *From:* Sun, Austin >> *Sent:* Thursday, January 30, 2020 10:53 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >> >> Hi Saul : >> >>       Because mainline has merged some kernel fix , kata feature and >> some other fixes . would you like to rebase f/centos8 branch from >> master now ? >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ji at sibyl.li Fri Jan 31 04:33:49 2020 From: ji at sibyl.li (Austin Gillmann) Date: Thu, 30 Jan 2020 22:33:49 -0600 Subject: [Starlingx-discuss] stx-openstack neutron failing to applyu Message-ID: Hi all, been trying to deploy starlingx on another cluster, but I am running into a weird error when trying to apply the application. It is `ConfigMap "osh-openstack-neutron.v2" is invalid: []: Too long: must have at most 1048576 characters` I have also attached the log here: http://paste.debian.net/1128435/ I think whatever is at line 484 near the traceback may be of interest. Let me know if you need any other information for troubleshooting, thank you! From austin.sun at intel.com Fri Jan 31 08:48:59 2020 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 31 Jan 2020 08:48:59 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> Message-ID: Thanks Saul. From my opinion , we can cherry-pick pylint change to f/centos8 . Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? Thank. BR Austin Sun. -----Original Message----- From: Saul Wold Sent: Friday, January 31, 2020 7:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch A quick update. Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. Sau! On 1/29/20 8:26 PM, Saul Wold wrote: > > > On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >> Hi Saul, >> >> CentOS 8 feature branch also needs below patch, otherwise all patches >> in integ repo cannot be merged. >> >> https://review.opendev.org/704566 >> >> Please help rebase master patches to CentOS 8 feature branch. >> > Yes, I am ware of this, I started the rebase this afternoon this one > is more complex and I need to do some build testing before I can merge. > > Sau! > >> Thanks. >> >> Best Regards >> >> Shuicheng >> >> *From:* Sun, Austin >> *Sent:* Thursday, January 30, 2020 10:53 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >> >> Hi Saul : >> >>       Because mainline has merged some kernel fix , kata feature and >> some other fixes . would you like to rebase f/centos8 branch from >> master now ? >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mward at akamai.com Fri Jan 31 10:21:11 2020 From: mward at akamai.com (Ward, Martin) Date: Fri, 31 Jan 2020 10:21:11 +0000 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation Message-ID: Good day all, I’m trying to install a Simplex server following the instructions provided in https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex - The base system is CentOS 7.7. I’ve got the basic Simplex VM created, up and running, it’s when I run the Ansible scripts that it fails and logs the error: 2020-01-30T16:19:48.122 Error: 2020-01-30 16:19:48 +0000 ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:19:48.258 Error: 2020-01-30 16:19:48 +0000 /Stage[main]/Platform::Ldap::Bootstrap/Exec[populate initial ldap configuration]/returns: change from notrun to 0 failed: ldapadd -D cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f /etc/openldap/initial_config.ldif returned 49 instead of one of [0] 2020-01-30T16:21:54.301 Error: 2020-01-30 16:21:54 +0000 /Stage[main]/Platform::Drbd::Etcd::Bootstrap/Platform::Drbd::Filesystem[drbd-etcd]/Drbd::Resource[drbd-etcd]/Drbd::Resource::Enable[drbd-etcd]/Drbd::Resource::Up[drbd-etcd]/Mount[/opt/etcd]: Could not evaluate: Execution of '/usr/bin/mount /opt/etcd' returned 32: mount: /dev/drbd7 is write-protected, mounting read-only When I run the ldapadd command myself it fails with: ldap_bind: Invalid credentials (49) I’ve not configured any ldap password anywhere so I guess that the ldapadmin password is auto-generated, but the fact that it’s not working is cause for concern. I’ve looked through the log file for any clues but everything prior to the above command has worked fine no errors or warnings. I am at a loss, any pointers would be appreciated. |\\/|artin -- Martin Ward Technical Support Engineer.Senior Group: Carrier Support Ext: 29745 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Jan 31 14:50:33 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 31 Jan 2020 14:50:33 +0000 Subject: [Starlingx-discuss] rebase f/centos8 branch In-Reply-To: References: <9700A18779F35F49AF027300A49E7C7660916D83@SHSMSX105.ccr.corp.intel.com> <77bd7f99-b769-68a4-9206-2fd8138cc13e@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC1631D0C@ALA-MBD.corp.ad.wrs.com> The cherry-pick of Al's fix has merged in f/centos8: https://review.opendev.org/704862 -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, January 31, 2020 3:49 AM To: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch Thanks Saul. From my opinion , we can cherry-pick pylint change to f/centos8 . Which master base are you using ? shall we wait layer builder change be merged on mainline if layer builder changes will be merged soon ? , or it is already in baseline ? Thank. BR Austin Sun. -----Original Message----- From: Saul Wold Sent: Friday, January 31, 2020 7:44 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] rebase f/centos8 branch A quick update. Due to stx-tools downloads lst files merging before the upgrades merged, I have more work to download the older versions first in order to do some testing of the kernel changes. Another option would be to cherry-pick the pylint change to f/centos8, I think that might be a better option at this point to unblock us. Sau! On 1/29/20 8:26 PM, Saul Wold wrote: > > > On 1/29/20 8:18 PM, Lin, Shuicheng wrote: >> Hi Saul, >> >> CentOS 8 feature branch also needs below patch, otherwise all patches >> in integ repo cannot be merged. >> >> https://review.opendev.org/704566 >> >> Please help rebase master patches to CentOS 8 feature branch. >> > Yes, I am ware of this, I started the rebase this afternoon this one > is more complex and I need to do some build testing before I can merge. > > Sau! > >> Thanks. >> >> Best Regards >> >> Shuicheng >> >> *From:* Sun, Austin >> *Sent:* Thursday, January 30, 2020 10:53 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] rebase f/centos8 branch >> >> Hi Saul : >> >>       Because mainline has merged some kernel fix , kata feature and >> some other fixes . would you like to rebase f/centos8 branch from >> master now ? >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From andy.ning at windriver.com Fri Jan 31 18:12:34 2020 From: andy.ning at windriver.com (Andy Ning) Date: Fri, 31 Jan 2020 13:12:34 -0500 Subject: [Starlingx-discuss] Invalid password for ldapadmin user during simplex installation In-Reply-To: References: Message-ID: On 2020-01-31 05:21 AM, Ward, Martin wrote: > > Good day all, > > I’m trying to install a Simplex server following the instructions > provided in > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_Environment/Simplex > - The base system is CentOS 7.7. > > I’ve got the basic Simplex VM created, up and running, it’s when I run > the Ansible scripts that it fails and logs the error: > > 2020-01-30T16:19:48.122 Error: 2020-01-30 16:19:48 +0000 ldapadd -D > cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f > /etc/openldap/initial_config.ldif returned 49 instead of one of [0] > > 2020-01-30T16:19:48.258 Error: 2020-01-30 16:19:48 +0000 > /Stage[main]/Platform::Ldap::Bootstrap/Exec[populate initial ldap > configuration]/returns: change from notrun to 0 failed: ldapadd -D > cn=ldapadmin,dc=cgcs,dc=local -w f62083c68b43Ti0* -f > /etc/openldap/initial_config.ldif returned 49 instead of one of [0] > > 2020-01-30T16:21:54.301 Error: 2020-01-30 16:21:54 +0000 > /Stage[main]/Platform::Drbd::Etcd::Bootstrap/Platform::Drbd::Filesystem[drbd-etcd]/Drbd::Resource[drbd-etcd]/Drbd::Resource::Enable[drbd-etcd]/Drbd::Resource::Up[drbd-etcd]/Mount[/opt/etcd]: > Could not evaluate: Execution of '/usr/bin/mount /opt/etcd' returned > 32: mount: /dev/drbd7 is write-protected, mounting read-only > > When I run the ldapadd command myself it fails with: > > ldap_bind: Invalid credentials (49) > Looks like ldap is not properly configured before the ldapadd command, ldap doesn't know this binding password. Andy > > I’ve not configured any ldap password anywhere so I guess that the > ldapadmin password is auto-generated, but the fact that it’s not > working is cause for concern. > > I’ve looked through the log file for any clues but everything prior to > the above command has worked fine no errors or warnings. > > I am at a loss, any pointers would be appreciated. > > |\\/|artin > > -- > > Martin Ward > > Technical Support Engineer.Senior > > Group: Carrier Support > > Ext: 29745 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Fri Jan 31 19:25:55 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 31 Jan 2020 19:25:55 +0000 Subject: [Starlingx-discuss] Unit tests first!!! Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C00206@ALA-MBD.corp.ad.wrs.com> Hey everyone. Following on the success of our recent StarlingX test hack-a-thon, I'd like to remind everyone about our goal to submit unit tests along with new (or changed) code. As a core reviewer for many of our projects, I often see new code being put up for review with no unit tests. At that point, you have working code and it feels like going back to write unit tests is a lot of effort (and it can be). To avoid this, I would highly recommend that you write (and execute) your unit tests BEFORE doing any testing on hardware (or virtual) labs. This has big advantages: * The unit tests catch many errors in the code and the test cycle (running tox) is extremely short. This saves time when you do get to the point of testing on hardware because you will be dealing with far fewer bugs. * Many error conditions are very easy to catch with unit tests and either very time consuming (or impossible) to test on hardware. In this case, the unit tests are a big time saver and result in better quality code. So... my advice is to write your unit tests up front whenever possible. This saves time vs. writing them after you have already done your hardware testing (or worse - after your review has been given a -1 due to missing unit tests). If you have questions about what unit tests would be expected for a particular change or how to write them, contact one of the cores for the project you are working on - they will be happy to help. Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Jan 31 21:26:31 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 31 Jan 2020 21:26:31 +0000 Subject: [Starlingx-discuss] Unit tests first!!! In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C00206@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1C00206@ALA-MBD.corp.ad.wrs.com> Message-ID: <20200131212631.5icjcadcbmdobxo3@yuggoth.org> On 2020-01-31 19:25:55 +0000 (+0000), Wensley, Barton wrote: [...] > So... my advice is to write your unit tests up front whenever > possible. This saves time vs. writing them after you have already > done your hardware testing (or worse - after your review has been > given a -1 due to missing unit tests). If you have questions about > what unit tests would be expected for a particular change or how > to write them, contact one of the cores for the project you are > working on - they will be happy to help. Speaking from personal experience, making changes to untested code paths is harrowing. I have no idea whether the already existing code even works, much less whether my change will make it better or worse. I find it especially comforting to first submit tests for the code I'm planning to alter. That way when I submit the code changes I have proof that they either don't alter the tested behavior (if they aren't supposed to, for example a refactoring), or I'm forced to also include changes to the tests which reflect the tested behaviors being altered. This is a huge help to reviewers as well, since they can see immediately what behaviors are changing and confirm those are expected. So I second your advice to incorporate tests when proposing changes which add new features/behaviors, but also strongly recommend adding tests for previously untested code *in advance of* modifying it. Including new tests in the same change as your behavior modifications is too late to get full benefit from them. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From sgw at linux.intel.com Fri Jan 31 21:28:30 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 31 Jan 2020 13:28:30 -0800 Subject: [Starlingx-discuss] [important] Build layering In-Reply-To: References: Message-ID: <830ce6d4-06ec-e409-8536-1540ba46ff3f@linux.intel.com> There seems to be an issue with the download mirror, I attempted to do a "distro" layer build, I started with the download mirror step and it failed to completely download all the RPMs. These did not download correctly: bash-4.2.46-31.el7.tis.4.x86_64.rpm golang-1.12.10-3.tis.1.x86_64.rpm golang-shared-1.12.10-3.tis.1.x86_64.rpm python-2.7.5-76.el7.tis.4.x86_64.rpm python-debug-2.7.5-76.el7.tis.4.x86_64.rpm python-debuginfo-2.7.5-76.el7.tis.4.x86_64.rpm python-devel-2.7.5-76.el7.tis.4.x86_64.rpm These seem to all be part of the compile layer. When I check on the cengn mirror, these RPMs are present in the /mirror/starlingx/master/centos/compiler/latest_build/outputs/RPMS/std/ directory. There is a note in the log about the package not matching: http://mirror.starlingx.cengn.ca:80/mirror/centos/mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/latest_build/outputs/RPMS/std/golang-shared-1.12.10-3.tis.1.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=CENGN_Starlingx-cengn_compiler_std_layer clean metadata I tried to run the --enablerpo, but that did not seem to help. I will work on testing another configuration. Thanks Sau! On 1/30/20 12:39 PM, Scott Little wrote: > The build layering feature is coming soon. > > > *Code reviews* have been posted ... > > https://review.opendev.org/#/c/700819/2 > > https://review.opendev.org/#/c/700821/9 > > https://review.opendev.org/#/c/681821/28 > > https://review.opendev.org/#/c/705092/ > > > *D**ocumentation* can be found in the fourth review, here .... > > https://review.opendev.org/gitweb?p=starlingx/docs.git;a=blob;f=doc/source/developer_resources/Layered_Build.rst;h=6f945d8d33f70bd91594033fcfa6abaf6271056d;hb=2a6abc988c9a52321982015831b12819586546df > > > *Want to try it out before it merges? * > > I've set up a modified manifest that pulls in the required updates .... > > One of ... > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m compile.xml > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m distro.xml > >    repo init -u https://opendev.org/starlingx/manifest.git -b > refs/changes/04/705104/2 -m flock.xml > > > followed by: > >    repo sync > > > Scott > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From maria.g.perez.ibarra at intel.com Fri Jan 31 23:48:36 2020 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 31 Jan 2020 23:48:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test - ISO 20200131 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2020-January-31 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] Standard - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 66 TCs ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: