From ildiko.vancsa at gmail.com Wed Apr 1 09:06:58 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 1 Apr 2020 11:06:58 +0200 Subject: [Starlingx-discuss] Virtual OpenDev Update Message-ID: <816CA2BF-C482-4430-A474-FF2361B5CC2E@gmail.com> Hi everyone, As we continue to gather feedback and discuss what a virtual OpenDev will look like, we wanted to provide you with an update around the event. While we are still attempting to solve some of the riddles of virtual event world, we did come up with some decisions that give us something to build on, which are based on input and experience from members of the Programming Committee. Decisions: - OpenDev will happen after the Virtual PTG (exact format and timing TBD) - Will not be simultaneous/parallel Tracks so everyone has the opportunity to participate in more than one - 3 Tracks, each on different date: - Hardware Automation - Large Scale Ops - Containers in Production We also discussed the original intent and goals of OpenDev to make sure we’re still heading in a direction that’s beneficial for the community, especially since it will no longer directly precede the upcoming PTG. Similar to past OpenDev events, the goal is to identify the questions we don’t have the answers for, and to use that time to dive in and determine the work ahead of us, working together, sharing use cases, and learning from other people asking those same questions. High-level decisions, goals, and some areas we’re looking for feedback are in the etherpad below. As you continue to experience this new amazing world of virtual events, please add any feedback or ideas to the etherpad below. We’re looking forward to creating virtual OpenDev with you all! https://etherpad.openstack.org/p/Virtual_OpenDev_Planning Thanks and Best Regards, Ildikó From allison at openstack.org Wed Apr 1 14:55:09 2020 From: allison at openstack.org (Allison Price) Date: Wed, 1 Apr 2020 09:55:09 -0500 Subject: [Starlingx-discuss] Fwd: OpenStack Foundation Community Meetings References: <1633187D-8928-4671-B126-CB9CAC98377B@openstack.org> Message-ID: <3E20D151-B7D6-4C0E-BA52-3070F9E16BA1@openstack.org> Hi everyone - In case you didn’t see the post on the Foundation mailing list, we have a community meeting tomorrow where we will be talking about updates to OSF events as well as OSF project updates. One meeting will be in English and one in Mandarin. Bring your questions and see you then! Cheers, Allison > Begin forwarded message: > > From: Allison Price > Subject: OpenStack Foundation Community Meetings > Date: March 26, 2020 at 10:21:15 AM CDT > To: foundation at lists.openstack.org > > Hi everyone, > > Next week we are going to have two community meetings to discuss the OpenStack 10th anniversary planning, current community projects, and an update on OSF events. Please join if you would like to hear updates or if you have questions for the OpenStack Foundation team. > > Join us: > Thursday, April 2 at 10am CT / 1500 UTC  > Friday, April 3 in Mandarin at 10am China Standard Time > > If you are unable to join one of the above times, I will share a recording to the mailing list after the meetings. > > Cheers, > Allison > > > Allison Price > OpenStack Foundation > allison at openstack.org > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Apr 1 15:05:55 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 1 Apr 2020 15:05:55 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 1, 2020) In-Reply-To: References: Message-ID: >From this week's meeting... * Community Business * Standing Topics * Sanity * Monolithic: all green since last week * build ID (date) no longer in Sanity email - can we have it back? * used to be: "[Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200325" * now: "[Starlingx-discuss] Sanity Master Test MONOLITHIC" * AR: the sanity guys will add this back to the title * Layered: continuing to work through layered build issues * per Frank, working through some fundamental issues (as per Scott email http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008205.html) * root issue is that some rpms change content without changing version information * will address in next build meeting * Gerrit Review in need of Attention * none this week * CentOS 8 * Integrity/IMA - no longer a priority since stx.3.0 doesn't support the use of extended security - so no concern about testing this before kernel upgrade * Overall Plan - still under construction * Topics for this Week * Customer X Eval (Bruce) - some concerns * Proxy Issues During Installs * could we make it easier to identify issue that are related to proxy? * LDAP Server * used to manage Linux users * per Brent/Greg, it's an internal thing, on the management network - shouldn't be visible on the customer's network * Performance Evaluation * bugs have been opened for the issues seen * * will add some details on the mailing list * WeChat Group * per Austin, it's still active, but has been less active of late, it's ad-hoc * encouraged them to bring unanswered questions to the mailing list, or directly to this meeting * Open Request for Help * Saul pointed out that this request has been open since early last week... * [OpenStack Upgrade] Built the stx-glance for stable/ussuri (YuChengDe) * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008136.html * Don gave some context, relating back to a review that YuChengDe opened, and to this thread * [OpenStack Upgrade]Failed when build StarlingX docker images * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/007955.html * latest request seems from YuChengDe seems to be this: * if stx-glance builds without ceph, what impact will occur * AR: Yong, as OpenStack PL, to comment on this question -----Original Message----- From: Zvonar, Bill Sent: Tuesday, March 31, 2020 4:29 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Apr 1, 2020) Hi all, reminder of tomorrow's TSC/Community call. We'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200401T1400 From alexandru.dimofte at intel.com Wed Apr 1 15:55:57 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Wed, 1 Apr 2020 15:55:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200401 Message-ID: Sanity Test from 2020-April-1 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200401T013010Z/outputs/iso/ ) 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 [PASS] 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] The sanity was blocked because we faced this issue: https://bugs.launchpad.net/starlingx/+bug/1856078 TOTAL: [ 65 TCs ] Standard External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - 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 External - 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, STX Validation Team [cid:image003.png at 01D60857.2A49E0B0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From bruce.e.jones at intel.com Wed Apr 1 17:59:50 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 1 Apr 2020 17:59:50 +0000 Subject: [Starlingx-discuss] performance issues in R3 Message-ID: <9A85D2917C58154C960D95352B22818BFB0783C8@fmsmsx123.amr.corp.intel.com> I'd like to follow up on the comments I made earlier today at the community meeting around performance testing. We are seeing potential users and customers starting to run such tests as they evaluate the software, and there are some known issues. If we could address them, it might help turn potential users into users. The performance tests that Victor and the team developed are partially open sourced. I'm going to ask Nic to finish that work and contribute the tests to the Test project. Meanwhile, our testing showed two issues where the performance of StarlingX is 10X or more worse than the original seed code. One is captured in this bug [1]. The swact command is about 10X slower in R3 than in the seed code. There is some good analysis in the LP. The last comment in the bug is from Frank and says "Changed the priority to low and removed the stx.4.0 tag as this is not a functional issue and the changes required to improve performance require significant work more suited under a SB than a LP." So I'd like to ask - which sub-project should this work land? What needs to be in the SB? How can we move this forward? The other issue is related to the test "time to detect a failed OpenStack VM". This is likely directly related to a patch that we no longer carry in StarlingX. A version of that patch can be found here [2]. I don't believe it's worth our time to try (again) to push that patch. It's been rejected at least once. The direction from the Nova community at the time was to (somehow) implement this functionality outside of Nova. Which means we need a SB for it. Do we know how to solve this problem? What sub-project should that work land in? How can we move this forward? brucej [1] https://bugs.launchpad.net/starlingx/+bug/1838411 [2] https://gist.github.com/VictorRodriguez/e137a8cd87cf821f8076e9acc02ce195 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Wed Apr 1 21:09:49 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 1 Apr 2020 21:09:49 +0000 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Agenda Message-ID: StarlingX Community: This week's Thursday meeting agenda is below - all are welcome to attend: Agenda April 2nd: 1. Moving the kernel from stx-integ into its own repo to enable a layer below the distro layer 2. Review the current build layering challenges and discuss/brainstorm approach to address - Reference: Scott email on March 31st Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Apr 1 22:03:23 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 1 Apr 2020 15:03:23 -0700 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Agenda In-Reply-To: References: Message-ID: <3304a593-d8be-cbd7-908b-cf4f88712efb@linux.intel.com> I would like to also touch base on the PBR version bump methodology, just to confirm our direction. Sau! On 4/1/20 2:09 PM, Miller, Frank wrote: > StarlingX Community: > > This week’s Thursday meeting agenda is below – all are welcome to attend: > > Agenda April 2^nd : > > 1. Moving the kernel from stx-integ into its own repo to enable a layer > below the distro layer > > 2. Review the current build layering challenges and discuss/brainstorm > approach to address > >    - Reference: Scott email on March 31st > > Frank > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From austin.sun at intel.com Thu Apr 2 00:41:29 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 2 Apr 2020 00:41:29 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 4/1/2020 Message-ID: Hi All: Agenda for 4/1 meeting: - Ceph containerization (martin) https://drive.google.com/file/d/1GFO6-72lmVt5av_pX1EfXocibSEcPDJJ/view?usp=sharing 1) lvm solution Bob will discuss with Brent and feedback . 2) Martin will prepare host ceph -> rook ceph migration steps and share. - centos8 upgrade (shuicheng/Austin) kernel upgrade on master: test has been done: Sanity (install, deploy , openstack VM ) on Virtual env and BareMetal have been done. RT cyclictest 12 hours . no degrade HW/drivers: QAT, i210(e1000), ixgbe, i40e, TPM. IMA(integrity) this can not be verified. fpga driver ,small fix for compile issue. MLNX has not been verified yet. test plan for kernel upgrade : https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=1638010416 and have regression test plan. centos8 branch rebase Shuicheng has already rebased to latest master. will be merged by this week. - python3 upgrade status (An Ran) engtools platform-util logmgmt Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Tuesday, March 31, 2020 4:36 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 4/1/2020 Hi All: Agenda for 4/1 meeting: - Ceph containerization (martin) - Kata remaining work (shuicheng) - PBR: (JITStack Wesley) - centos8 upgrade (shuicheng/Austin) kernel upgrade on master centos8 branch rebase - python3 upgrade status (An Ran) -open If have any other topic, feel free to add to https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From scott.little at windriver.com Thu Apr 2 03:18:08 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 1 Apr 2020 23:18:08 -0400 Subject: [Starlingx-discuss] [ Build ] Layered build challenges In-Reply-To: <87354fc1-c64d-7b84-7934-8b5785abf13f@windriver.com> References: <87354fc1-c64d-7b84-7934-8b5785abf13f@windriver.com> Message-ID: <95436777-88be-dcb9-96d4-35866431298f@windriver.com> Some follow up data to give a sense of the diverse types of content changes seen within the rpms of tow consecutive distro layer builds where the only source code delta was in the kernel. The crude format here is '* **'. I add a layer of indent when I further break down a group into sub categories. total rpms 1847    no diff 1445    diff     402        kmod  22        timestamp only 136        other 244            REQUIRES 2    (dropped requires)            add/remove files  37                .build-id    35                date in path   1                other          3            checksum   242                pyc pyo   26                debug     31                bin       62                lib      126                whl       21                object     2                gz        15                html      12                .mo        1                .c .h      4                other     15 I have the lists of rpms falling into each category if that interests folks. And here are a few examples of the categories.  Format is : e.g. add remove other rdma-core-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     /usr/lib/systemd/system/rdma-ndd.service rdma-core-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     /usr/lib/udev/rules.d/60-rdma-ndd.rules rdma-core-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     /usr/sbin/rdma-ndd rdma-core-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     /usr/share/man/man8/rdma-ndd.8.gz e.g. date in path python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/PKG-INFO python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/SOURCES.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/dependency_links.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/entry_points.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/requires.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/top_level.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:added       /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200320-py2.7.egg-info/zip-safe python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/PKG-INFO python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/SOURCES.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/dependency_links.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/entry_points.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/requires.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/top_level.txt python2-setuptools-38.5.1-1.el7.tis.0.noarch.rpm:removed     /usr/lib/python2.7/site-packages/setuptools-38.5.1.post20200321-py2.7.egg-info/zip-safe e.g. REQUIERS ../data/ibacm-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     REQUIRES libsystemd.so.0()(64bit) ../data/ibacm-45mlnx1-1.45101.tis.1.x86_64.rpm:removed     REQUIRES libsystemd.so.0(LIBSYSTEMD_209)(64bit) e.g. pyc pyo ./python2-openvswitch-2.11.0-0.tis.1.noarch.rpm:..5.......T /usr/lib/python2.7/site-packages/ovs/vlog.pyc ./python2-openvswitch-2.11.0-0.tis.1.noarch.rpm:..5.......T /usr/lib/python2.7/site-packages/ovs/vlog.pyo ./python2-openvswitch-2.11.0-0.tis.1.noarch.rpm:..5.......T /usr/lib/python2.7/site-packages/ovs/winutils.pyc ./python2-openvswitch-2.11.0-0.tis.1.noarch.rpm:..5.......T /usr/lib/python2.7/site-packages/ovs/winutils.pyo e.g. debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:..5.......T /usr/lib/debug/usr/bin/ovn-controller-2.11.0-0.tis.1.x86_64.debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:..5.......T /usr/lib/debug/usr/bin/ovn-controller-vtep-2.11.0-0.tis.1.x86_64.debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:..5.......T /usr/lib/debug/usr/bin/ovn-nbctl-2.11.0-0.tis.1.x86_64.debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:..5.......T /usr/lib/debug/usr/bin/ovn-northd-2.11.0-0.tis.1.x86_64.debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:S.5.......T /usr/lib/debug/usr/bin/ovn-sbctl-2.11.0-0.tis.1.x86_64.debug ./openvswitch-debuginfo-2.11.0-0.tis.1.x86_64.rpm:S.5.......T /usr/lib/debug/usr/bin/ovn-trace-2.11.0-0.tis.1.x86_64.debug e.g. bin ntpdate-4.2.6p5-29.el7.centos.tis.1.x86_64.rpm:..5.......T /usr/sbin/ntpdate e.g. lib lighttpd-1.4.54-1.el7.tis.7.x86_64.rpm:..5.......T /usr/lib64/lighttpd/mod_access.so lighttpd-1.4.54-1.el7.tis.7.x86_64.rpm:..5.......T /usr/lib64/lighttpd/mod_accesslog.so lighttpd-1.4.54-1.el7.tis.7.x86_64.rpm:..5.......T /usr/lib64/lighttpd/mod_alias.so lighttpd-1.4.54-1.el7.tis.7.x86_64.rpm:..5.......T /usr/lib64/lighttpd/mod_auth.so e.g. object mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/xz_dec_lzma2.o mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/xz_dec_stream.o mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/xz_dec_syms.o e.g. gz resource-agents-4.1.1-12.el7_6.7.tis.1.x86_64.rpm:S.5.......T /usr/share/man/man7/ocf_heartbeat_symlink.7.gz resource-agents-4.1.1-12.el7_6.7.tis.1.x86_64.rpm:..5.......T /usr/share/man/man7/ocf_heartbeat_tomcat.7.gz resource-agents-4.1.1-12.el7_6.7.tis.1.x86_64.rpm:S.5.......T /usr/share/man/man7/ocf_heartbeat_vdo-vol.7.gz e.g. html grub2-common-2.02-0.76.el7.centos.tis.12.noarch.rpm:..5.......T /usr/share/doc/grub2-common-2.02/grub-dev.html grub2-common-2.02-0.76.el7.centos.tis.12.noarch.rpm:..5.......T /usr/share/doc/grub2-common-2.02/grub.html e.g. .mo libvirt-libs-4.7.0-1.tis.101.x86_64.rpm:..5.......T /usr/share/locale/af/LC_MESSAGES/libvirt.mo libvirt-libs-4.7.0-1.tis.101.x86_64.rpm:..5.......T /usr/share/locale/am/LC_MESSAGES/libvirt.mo libvirt-libs-4.7.0-1.tis.101.x86_64.rpm:..5.......T /usr/share/locale/anp/LC_MESSAGES/libvirt.mo e.g. .c .h shim-unsigned-x64-debuginfo-15-1.el7.tis.2.noarch.rpm:..5.......T /usr/src/debug/shim-15-1.el7.tis.2/shim-15-ia32/version.c shim-unsigned-x64-debuginfo-15-1.el7.tis.2.noarch.rpm:..5.......T /usr/src/debug/shim-15-1.el7.tis.2/shim-15-x64/version.c e.g. other mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:S.5.......T /usr/src/ofa_kernel/default/compat/config.log mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/config.status mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/mlx_compat.ko mlnx-ofa_kernel-rt-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/configure.mk.kernel mlnx-ofa_kernel-rt-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /etc/infiniband/info grub2-efi-x64-2.02-0.76.el7.centos.tis.12.x86_64.rpm:..5.......T /boot/efi/EFI/centos/grubx64.efi shim-x64-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/BOOT/fallback.efi shim-x64-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/BOOT/fbx64.efi shim-x64-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/centos/MokManager.efi shim-x64-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/centos/mmx64.efi grub2-efi-x64-unsigned-2.02-0.76.el7.centos.tis.12.x86_64.rpm:..5.......T /boot/efi/EFI/centos/gcdx64.efi.unsigned grub2-efi-x64-unsigned-2.02-0.76.el7.centos.tis.12.x86_64.rpm:..5.......T /boot/efi/EFI/centos/grubx64.efi.unsigned shim-unsigned-x64-15-1.el7.tis.2.x86_64.rpm:..5.......T /usr/share/shim/x64-15-1.el7.tis.2/shimx64.efi shim-unsigned-x64-15-1.el7.tis.2.x86_64.rpm:..5.......T /usr/share/shim/x64-15-1.el7.tis.2/shimx64.hash python-keystoneauth1-doc-3.13.1-1.tis.0.noarch.rpm:S.5.......T /usr/share/doc/python-keystoneauth1-doc-3.13.1/html/searchindex.js shim-ia32-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/BOOT/fbia32.efi shim-ia32-15-1.tis.2.x86_64.rpm:..5.......T /boot/efi/EFI/centos/mmia32.efi setup-2.8.71-10.el7.tis.16.noarch.rpm:..5.......T /etc/shadow python-gnocchiclient-doc-7.0.4-1.tis.14.noarch.rpm:..5.......T /usr/share/doc/python-gnocchiclient-doc-7.0.4/html/searchindex.js mlnx-ofa_kernel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /etc/infiniband/info shim-unsigned-ia32-15-1.el7.tis.2.x86_64.rpm:..5.......T /usr/share/shim/ia32-15-1.el7.tis.2/shimia32.efi shim-unsigned-ia32-15-1.el7.tis.2.x86_64.rpm:..5.......T /usr/share/shim/ia32-15-1.el7.tis.2/shimia32.hash mlnx-ofa_kernel-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/config.log mlnx-ofa_kernel-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/config.status mlnx-ofa_kernel-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/compat/mlx_compat.ko mlnx-ofa_kernel-devel-4.5-OFED.4.5.1.0.1.1.gb4fdfac.tis.2.x86_64.rpm:..5.......T /usr/src/ofa_kernel/default/configure.mk.kernel grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm:..5.......T /pxeboot/EFI/grubx64.efi grub2-efi-x64-cdboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm:..5.......T /boot/efi/EFI/centos/gcdx64.efi On 2020-03-31 2:21 p.m., Scott Little wrote: > Layered builds relies on an authoritative source (e.g. CENGN) > publishing an RPM repo with all the RPMS produced by a single build, > and an lst file enumerating those RPMS.  There are new config files > describing the url's for those repos that use the latest_build > symlink.  The client, a higher layer we wish to build, must download > the new lst file and repo data, and use those to download all > new/updates rpms. > > Issue identified early on where. > > 1) The outputs of a specific build might not endure on CENGN as long > as a designers build context. > > 2) The latest_build symlink might change in the middle of a download > season.  Packages version may have changes during between builds.  The > old version specified by the pre-update lst file might no longer be > available. > > So the next step is for CENGN to mirror those build outputs in a > cumulative fashion, like any other repo.  It's a default for > download_mirror.sh to look for a CENGN mirror of any url it uses, and > its a default behavior for CENGN to mirror it.  The mirror would > accumulate all the versions from all the builds.  So changing symlinks > and deletion of old builds shouldn't impact the end user. > > All this hinged on two assumptions. > > 1) If a package was not upversioned between builds, there would not be > significant changes to the content of the RPM. > > 2) yum repodata has checksums and timestamps for all packages.  I > expected yum to use that data to flag a changed rpm for re-download. > > Recent experience has proven both assumptions turned out to be wrong. > > 1) Kernel modules were the first example of a violation of this > asumption.  The mkod implicitly changes when the kernel changes. The > most obvious is that the installation path to the kmod change, > embedding the kernel version it was compiled against.  There are > deeper differences not worth enumerating. > > 2) Yum will throw error over inconsistancies between new repodata and > old, our new repodata and rpms already downloaded, but will not > re-download the updated packages.  I have not been able to override > this behavious with command line options, config files, or even > cleaning all yum cache.  It appears to be a defense against mirrors > that are slow to update, and perhaps against malicious hacks of an > upstream repo. > > The broken assumptions affected both the CENGN mirroring process, and > the final download by upper layer builders.  Neither was updating rpms > that have changed if the file name did not also change. > > Is this only an important matter for kmods.  Exploration with rpmdiff > reveals that the majority of RPMS change when rebuilt, even with zero > source code changes to any package.  Excluding the timestamps on files > embedded within the rpms lefts a list greater than 25% of the repo > reporting differences.  Spent some time trying to figure out a way to > filter out paths that embed the build time stamp, but the list > remained stubbornly large. > > So how to fix it. > > Several methods have been explored.  Some solutions only apply if the > downloader retains the file structure of the upstream repo, or if the > download capture the entire repo.   True for the cengn mirror, not for > the output of download_mirror.sh. > > 1) reposync: An rpm repo mirroring tool.  It's built on yum, and has > the same behaviour as yum.  Can't use that. > > 2) verifytree:  This tool validates the checksums in the repodata vs > the current set of rpms.  It's a tool aimed at rpm mirror operators. > It requires that the download directory structure is a faithful > replica of upstream.  So I can manually download the repodata, then > validate it vs the previously downloaded set of rpms.  RPM's that it > flags as having the wrong checksum need to be re-downloaded.  The > actual re-download could be accomplished in two ways. > > 2a) Replicate the current repo in a temporary working directory, > delete the updated rpms, use yum (either reposync or yumdownloader) > with clean cache to re-download the missing files. Finally exchange > the temporary directory with regular one.  This gives an atomic > cutover to the new content.  This is what CENGN mirror is using now. > >   This doesn't entirely solve the problem for downloaders that were > actively updated their local snapshot when such a mirror update goes > live.  Ideally the download_mirror tool has a retry loop.  If the last > pass downloaded files, try again until a pass reports there are no > further files to update. > > 2b) curl:  Use curl rather than yum.  Requires that we somehow know > the URL for the rpm we intend to download.  'yumdownloader --url' can > tell use the upstream url. > > 3) curl:  Use curl rather than yum, but do so directly without > verifytree.  Rely entirely on timestamps.  If we can give curl the > download url for the rpm, it can be given options that compare the > local and remote file timestamps and only downloads if the remote copy > is newer.  Also it preserves the file timestamp on download. We can > use 'yumdownloader --url' to tell us which repo to use, and what the > download url is from that repo. > > This was my solution for the download_mirror.sh users. > > 4) rsync: Requires CENGN to expose an rsync port to the world. Not my > first choice.  File sharing pirates would love to compromise a machine > with an open rsync port. > > > New issues. > > 1) 'yumdownloader --url' is SLOW.  It takes more than a second per > package to produce an answer.  since lower layer rpms are handled by > the same tools as all other rpms, we have over 2000 packages to > check.  This slowness largely persists in batch mode where I query a > large set of packages at once (3/4 sec per package).  It'll take an > hour to process them all, even if the result is 'nothing to update' > > 2) As noted above, most rpms are showing subtle changes between builds > even though the source has not changed.  This is undesirable, > triggering a huge number of needless downloads. > > > New solutions? > > 1) Download rpms from lower layers using a different tool than > 'download_mirror.sh' or at least a different sub-function than > dl-rpms.  First, this mean that we only need to run 'yumdownloader > -url' vs a smaller list of rpms.  Also this would allow us to use > reposync and verify tree for the download functions, removing > 'yumdownloader -url' entirely. > > 2) Use build avoidance.  Copies rpms from previous build into current > build environment and then use an incremental build.  This avoids > needlessly rebuilding rpms. RPMS retain the same checksum and > timestamp if not rebuilt.  Cut the problem off at the source. Concern > with this solution is that I still like to force a non-build avoidance > build from time to time to ensure we haven't diverged from reality in > some new and unexpected way. > > > _______________________________________________ > 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 allison at openstack.org Thu Apr 2 14:40:21 2020 From: allison at openstack.org (Allison Price) Date: Thu, 2 Apr 2020 09:40:21 -0500 Subject: [Starlingx-discuss] OpenStack Foundation Community Meetings In-Reply-To: <3E20D151-B7D6-4C0E-BA52-3070F9E16BA1@openstack.org> References: <1633187D-8928-4671-B126-CB9CAC98377B@openstack.org> <3E20D151-B7D6-4C0E-BA52-3070F9E16BA1@openstack.org> Message-ID: <10020F51-3ADA-4B46-BD03-FCF181020458@openstack.org> Hi everyone, Attached are the slides we will be covering at 10am CT / 1500 UTC today. We will be covering OSF project updates—including StarlingX—as well as updates on OSF events. See you soon! Allison > On Apr 1, 2020, at 9:55 AM, Allison Price wrote: > > Hi everyone - > > In case you didn’t see the post on the Foundation mailing list, we have a community meeting tomorrow where we will be talking about updates to OSF events as well as OSF project updates. > > One meeting will be in English and one in Mandarin. > > Bring your questions and see you then! > > Cheers, > Allison > > > >> Begin forwarded message: >> >> From: Allison Price > >> Subject: OpenStack Foundation Community Meetings >> Date: March 26, 2020 at 10:21:15 AM CDT >> To: foundation at lists.openstack.org >> >> Hi everyone, >> >> Next week we are going to have two community meetings to discuss the OpenStack 10th anniversary planning, current community projects, and an update on OSF events. Please join if you would like to hear updates or if you have questions for the OpenStack Foundation team. >> >> Join us: >> Thursday, April 2 at 10am CT / 1500 UTC  >> Friday, April 3 in Mandarin at 10am China Standard Time >> >> If you are unable to join one of the above times, I will share a recording to the mailing list after the meetings. >> >> Cheers, >> Allison >> >> >> Allison Price >> OpenStack Foundation >> allison at openstack.org >> >> >> >> > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: April 2020 Community Update.pdf Type: application/pdf Size: 1501541 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Thu Apr 2 15:48:54 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Thu, 2 Apr 2020 15:48:54 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200402 Message-ID: Sanity Test from 2020-April-02 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200402T013011Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - 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 External - 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, STX Validation Team [cid:image002.png at 01D6091F.58B52130] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20507 bytes Desc: image002.png URL: From bruce.e.jones at intel.com Thu Apr 2 19:52:56 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 2 Apr 2020 19:52:56 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BFB078F85@fmsmsx123.amr.corp.intel.com> Yang, I'm puzzled by the different Sanity results. Do you and Nic know why the Intel team is seeing Green Sanity runs, and the WR team is seeing multiple issues? Are we running different tests? Different images? Meanwhile, congratulations on pulling the Feature and Regression plan together. It's looking good, thanks to great work by you and the teams! bruej From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: Tuesday, March 31, 2020 9:09 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/31/2020 Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy 1. Sanity Status: * Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation * Sanity issues reported by Intel: * Green * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved * May look into adding ipv6 configs for the long term 2. stx4.0 testing * Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: ? automated and manual test update needed, may be time consuming ? target 06-05 * Layered build is tested daily with issues being found and resolved ? image did not build - fixed ? 03-31 build still failed, but went further * Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing * Targeted regression completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Unified santiy * Intel will bring in robot sanity as is into pytest framework * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment 4. Opens * Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc * Will know more by end of week. * Risk reduced compared to last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Apr 2 22:10:16 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 2 Apr 2020 22:10:16 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meetng - April 2/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - April 2 2020 stx.4.0 - Continue the review of Milestone-2 criteria - Two criteria were already met last week - Spec freexe; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underwa - Focused on reviewing the third criterion - Release tet plan defined - Feature Testing - The majority of features have target dates for test execution with reasonable risk - Key concern/risk is with the Openstack Upversion - Testing currently expected to go into June -- current plan: June 5 - Expect issues and updates to automation test-cases - Regression Testing - Expect to start regression two weeks later and end two weeks later than the orignal plan - This will push the backend of the release by about two weeks as well - New Dates: - Milestone-3: May 29 - Feature Test: Jun 5 - Regression Test: Jun 26 - RC1: Jun 26 - Final Regression: July 10 - Release Date: July 17 - The release team agreed that this is acceptable - Need to monitor that test activities are moving forward as per plan as the team is still working thru a number of h/w dependencies and ramp up - Team agreed to declare MS-2 today -- Congratulations to the whole team! From Ghada.Khalil at windriver.com Thu Apr 2 22:17:04 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 2 Apr 2020 22:17:04 +0000 Subject: [Starlingx-discuss] stx.4.0 Milestone-2 Declared Message-ID: Hello all, The StarlingX release team reviewed the status of stx.4.0 on April 2 and agreed to declare Milestone-2 Milestone-2 Criteria: https://wiki.openstack.org/wiki/StarlingX/Release_Plan#Release_Milestones - Spec freeze; no new specs accepted for the release. The focus is on closing current specs - Feature plans defined and feature development well underway - Release test plan defined - including test automation deliverables The above milestone criteria were met. See detailed minutes from the following release team meetings: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008162.html http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008220.html Please note an update to the release dates as follows (a shift of 2wks): Milestone-3: May 29 Feature Test: Jun 5 Regression Test: Jun 26 RC1: Jun 26 Final Regression: July 10 Release Date: July 17 A list of proposed features/plans is available at: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 Congratulations to the whole team! Regards, Ghada & the stx release team From shuicheng.lin at intel.com Fri Apr 3 08:25:51 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 3 Apr 2020 08:25:51 +0000 Subject: [Starlingx-discuss] [docs] Provide doc input for 2006145 Message-ID: <9700A18779F35F49AF027300A49E7C766397D10B@SHSMSX104.ccr.corp.intel.com> Hi all, Kata Container is supported in StarlingX recently. Here is the doc for how to run kata container in StarlingX. Please help review it, and feel free to notify me if anything is missed or you have question on it. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX Kata container integration.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 28060 bytes Desc: StarlingX Kata container integration.docx URL: From nicolae.jascanu at intel.com Fri Apr 3 11:49:04 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Fri, 3 Apr 2020 11:49:04 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 In-Reply-To: <9A85D2917C58154C960D95352B22818BFB078F85@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BFB078F85@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Bruce, Hi Yang, Looks like the bugs 1863795 and 1859645 are duplicates of 1856078. This was raised by Cristopher and each time we encountered, we've stated this in the report. Seems that we need an upgrade to Helm V3. For the rest of bugs, we need to replicate them after the daily finishes. I guess that Yang is executing also other sanity tests. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Jones, Bruce E Sent: Thursday, April 2, 2020 22:53 To: Liu, Yang (YOW) ; Jascanu, Nicolae Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [ Test ] meeting notes - 03/31/2020 Yang, I'm puzzled by the different Sanity results. Do you and Nic know why the Intel team is seeing Green Sanity runs, and the WR team is seeing multiple issues? Are we running different tests? Different images? Meanwhile, congratulations on pulling the Feature and Regression plan together. It's looking good, thanks to great work by you and the teams! bruej From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: Tuesday, March 31, 2020 9:09 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/31/2020 Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy 1. Sanity Status: * Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation * Sanity issues reported by Intel: * Green * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved * May look into adding ipv6 configs for the long term 2. stx4.0 testing * Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: ? automated and manual test update needed, may be time consuming ? target 06-05 * Layered build is tested daily with issues being found and resolved ? image did not build - fixed ? 03-31 build still failed, but went further * Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing * Targeted regression completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Unified santiy * Intel will bring in robot sanity as is into pytest framework * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment 4. Opens * Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc * Will know more by end of week. * Risk reduced compared to last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From yang.liu at windriver.com Fri Apr 3 13:52:38 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Fri, 3 Apr 2020 13:52:38 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 In-Reply-To: References: <9A85D2917C58154C960D95352B22818BFB078F85@fmsmsx123.amr.corp.intel.com> Message-ID: There was a comparison done by previous Intel test team, and on a high level, sanity test cases were mostly the same between us with 1 extra test in WR sanity suite. The main difference may be our configurations and verifications. There are couple of things I know of that might cause the differences in results: · OpenStack neutron configurations: o In our config, the external traffic goes through neutron routers to reach the vms, and connectivity verification is included in most openstack sanity test we run. Perhaps that is something Nic's team can look into. · Couple of the platform sanity issues we reported were more frequently seen on IPv6 systems (Christopher originally reported in a different LP). This is another item Nic can consider. · 1868567 is a stx-monitor test case we recently added to the sanity suite to test system applications, this test is available in stx-test. Nic could pick up this test if needed. · 1869739 is a configuration alarm issue without obvious system impact, this can only be found if the overall system health including alarms were verified explicitly in every test. Nic could also pick up this one easily because it's already included in pytest framework. Hope that helps. Regards, Yang From: Jascanu, Nicolae [mailto:nicolae.jascanu at intel.com] Sent: April-03-20 7:49 AM To: Jones, Bruce E; Liu, Yang (YOW) Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [ Test ] meeting notes - 03/31/2020 Hi Bruce, Hi Yang, Looks like the bugs 1863795 and 1859645 are duplicates of 1856078. This was raised by Cristopher and each time we encountered, we've stated this in the report. Seems that we need an upgrade to Helm V3. For the rest of bugs, we need to replicate them after the daily finishes. I guess that Yang is executing also other sanity tests. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Jones, Bruce E Sent: Thursday, April 2, 2020 22:53 To: Liu, Yang (YOW) ; Jascanu, Nicolae Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [ Test ] meeting notes - 03/31/2020 Yang, I'm puzzled by the different Sanity results. Do you and Nic know why the Intel team is seeing Green Sanity runs, and the WR team is seeing multiple issues? Are we running different tests? Different images? Meanwhile, congratulations on pulling the Feature and Regression plan together. It's looking good, thanks to great work by you and the teams! bruej From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: Tuesday, March 31, 2020 9:09 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/31/2020 Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy 1. Sanity Status: * Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation * Sanity issues reported by Intel: * Green * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved * May look into adding ipv6 configs for the long term 2. stx4.0 testing * Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: * automated and manual test update needed, may be time consuming * target 06-05 * Layered build is tested daily with issues being found and resolved * image did not build - fixed * 03-31 build still failed, but went further * Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing * Targeted regression completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Unified santiy * Intel will bring in robot sanity as is into pytest framework * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment 4. Opens * Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc * Will know more by end of week. * Risk reduced compared to last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From alfredo.deluca at gmail.com Fri Apr 3 15:02:19 2020 From: alfredo.deluca at gmail.com (Alfredo De Luca) Date: Fri, 3 Apr 2020 17:02:19 +0200 Subject: [Starlingx-discuss] Openstack on the Central Cloud Message-ID: Hi all. We deployed STX 3.0 in 2 baremetal machine as Central Cloud and on 2 other baremetals we deployed 2 edge sub-clouds. All ok and working fine. Now we tried to install Openstack helm as per below.... *wget http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/helm-charts/stx-openstack-1.0-19-centos-stable-latest.tgz system application-upload stx-openstack-1.0-19-centos-stable-latest.tgz* But it's not working. So my questions is: Is it possible to deploy openstack on the Central Cloud? Cheers -- *Alfredo* -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexandru.dimofte at intel.com Fri Apr 3 15:43:24 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Fri, 3 Apr 2020 15:43:24 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200403 Message-ID: Sanity Test from 2020-April-03 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200403T013012Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - 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 External - 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, STX Validation Team [cid:image003.png at 01D609E7.BE9FB000] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 20507 bytes Desc: image003.png URL: From build.starlingx at gmail.com Fri Apr 3 16:03:19 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 3 Apr 2020 12:03:19 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_compiler_master_master - Build # 87 - Failure! Message-ID: <1447079851.1132.1585929801171.JavaMail.javamailuser@localhost> Project: STX_build_layer_compiler_master_master Build #: 87 Status: Failure Timestamp: 20200403T153300Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/compiler/20200403T153300Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true From Barton.Wensley at windriver.com Fri Apr 3 16:18:25 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 3 Apr 2020 16:18:25 +0000 Subject: [Starlingx-discuss] Openstack on the Central Cloud In-Reply-To: References: Message-ID: Alfredo, There is currently no support for OpenStack on distributed cloud systems. This feature has not been implemented yet. Bart From: Alfredo De Luca [mailto:alfredo.deluca at gmail.com] Sent: April 3, 2020 11:02 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Openstack on the Central Cloud Hi all. We deployed STX 3.0 in 2 baremetal machine as Central Cloud and on 2 other baremetals we deployed 2 edge sub-clouds. All ok and working fine. Now we tried to install Openstack helm as per below.... wget http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/helm-charts/stx-openstack-1.0-19-centos-stable-latest.tgz system application-upload stx-openstack-1.0-19-centos-stable-latest.tgz But it's not working. So my questions is: Is it possible to deploy openstack on the Central Cloud? Cheers -- Alfredo -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Apr 3 16:43:52 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 3 Apr 2020 16:43:52 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 In-Reply-To: References: <9A85D2917C58154C960D95352B22818BFB078F85@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BFB079A5B@fmsmsx123.amr.corp.intel.com> Yang, Nic - thank you for the update on this. Can we please work toward one common Sanity test suite and setup? I know Nic's team is working on updating our automation to Pytest which I assume is the long pole - but I'd like to see us take on the goal of fully common test cases and setups for Sanity. Can we do that for 4.0? bruej From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: Friday, April 3, 2020 6:53 AM To: Jascanu, Nicolae ; Jones, Bruce E Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [ Test ] meeting notes - 03/31/2020 There was a comparison done by previous Intel test team, and on a high level, sanity test cases were mostly the same between us with 1 extra test in WR sanity suite. The main difference may be our configurations and verifications. There are couple of things I know of that might cause the differences in results: * OpenStack neutron configurations: o In our config, the external traffic goes through neutron routers to reach the vms, and connectivity verification is included in most openstack sanity test we run. Perhaps that is something Nic's team can look into. * Couple of the platform sanity issues we reported were more frequently seen on IPv6 systems (Christopher originally reported in a different LP). This is another item Nic can consider. * 1868567 is a stx-monitor test case we recently added to the sanity suite to test system applications, this test is available in stx-test. Nic could pick up this test if needed. * 1869739 is a configuration alarm issue without obvious system impact, this can only be found if the overall system health including alarms were verified explicitly in every test. Nic could also pick up this one easily because it's already included in pytest framework. Hope that helps. Regards, Yang From: Jascanu, Nicolae [mailto:nicolae.jascanu at intel.com] Sent: April-03-20 7:49 AM To: Jones, Bruce E; Liu, Yang (YOW) Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: [ Test ] meeting notes - 03/31/2020 Hi Bruce, Hi Yang, Looks like the bugs 1863795 and 1859645 are duplicates of 1856078. This was raised by Cristopher and each time we encountered, we've stated this in the report. Seems that we need an upgrade to Helm V3. For the rest of bugs, we need to replicate them after the daily finishes. I guess that Yang is executing also other sanity tests. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Jones, Bruce E > Sent: Thursday, April 2, 2020 22:53 To: Liu, Yang (YOW) >; Jascanu, Nicolae > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: [ Test ] meeting notes - 03/31/2020 Yang, I'm puzzled by the different Sanity results. Do you and Nic know why the Intel team is seeing Green Sanity runs, and the WR team is seeing multiple issues? Are we running different tests? Different images? Meanwhile, congratulations on pulling the Feature and Regression plan together. It's looking good, thanks to great work by you and the teams! bruej From: Liu, Yang (YOW) [mailto:yang.liu at windriver.com] Sent: Tuesday, March 31, 2020 9:09 AM To: 'starlingx-discuss at lists.starlingx.io' > Subject: [Starlingx-discuss] [ Test ] meeting notes - 03/31/2020 Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 03/31/2020 Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy 1. Sanity Status: * Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation * Sanity issues reported by Intel: * Green * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved * May look into adding ipv6 configs for the long term 2. stx4.0 testing * Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: * automated and manual test update needed, may be time consuming * target 06-05 * Layered build is tested daily with issues being found and resolved * image did not build - fixed * 03-31 build still failed, but went further * Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing * Targeted regression completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Unified santiy * Intel will bring in robot sanity as is into pytest framework * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment 4. Opens * Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc * Will know more by end of week. * Risk reduced compared to last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Steven.Webster at windriver.com Fri Apr 3 18:00:11 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Fri, 3 Apr 2020 18:00:11 +0000 Subject: [Starlingx-discuss] Broken link on starlingx.io Message-ID: Hi All, I noticed that the link to the StarlingX Powerpoint templates at https://www.starlingx.io/faq/ is broken. Does anybody know who takes care of these pages? Cheers, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Apr 3 18:16:28 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 3 Apr 2020 18:16:28 +0000 Subject: [Starlingx-discuss] Broken link on starlingx.io In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BFB079B63@fmsmsx123.amr.corp.intel.com> The web pages are managed in a git repo [1]. We all as a community take care of them, and anyone can submit a PR against them. You can do it, Steven, or we can ask the Docs team to help. Brucej [1] https://github.com/StarlingXWeb/starlingx-website From: Webster, Steven [mailto:Steven.Webster at windriver.com] Sent: Friday, April 3, 2020 11:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Broken link on starlingx.io Hi All, I noticed that the link to the StarlingX Powerpoint templates at https://www.starlingx.io/faq/ is broken. Does anybody know who takes care of these pages? Cheers, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Fri Apr 3 19:08:18 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 3 Apr 2020 19:08:18 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-01 Message-ID: Hello all, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-01 * All -- reviews merged since last week: 2 * All -- bug status -- no change * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Windows Active Dir content -- Review available: https://review.opendev.org/#/c/712111/ ? More changes from Greg. Latest patch set includes updates from Jerry Sun and Teresa Ho. * Upgrade Kubernetes version -- Review available: https://review.opendev.org/#/c/712583/ ? http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007901.html (R4 new content) ? Angie Wang emailed more info about the 3 patches, however offline email thread w/Angie & Bart about making this into wiki content because it could change. We may point to it from the user doc. Check in on Monday if don't hear anything beforehand. * no update: Assignment of R4 doc tasks ? These stories have no assigned person: * https://storyboard.openstack.org/#!/story/2006770 (How to use Backup & Restore) AR Mary ping Frank Miller * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) SME Scott Little but too busy at the moment. Wait a while. * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) AR Mary check discuss archive, may be covered already? If not ask Tao Liu. * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) AR Mary ask Dariush (reference the story) Do we need doc updates? * All -- Opens * new: Docker proxy setup ongoing questions w/Saul: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008189.html and email from Greg. Priority 1 task ? Greg will ask around, try to get with Saul to see the log output, etc. Mary do the un-bury work. ? 2 proxy settings exist (http and https). Anything inside your network must use the "noproxy" setting. 2 customers are having this issue: GE and ABB. ? Failure message says to look at Ansible log - if you dig deep into it, you find that it's a proxy issue. ? 2 areas for improvement: Troubleshooting solution aka "if you get this message, try this". Also, "how you can tell this is working" check after install. * no update: Brucej -- let's discuss Ildiko's email, esp. network documentation (STX feedback): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008088.html ? AR Greg to make a story - ask for help from networking team. We need overview of how to configure networking in STX. ? Mapping between STX networking, how we differ from OpenStack behavior, then point to OpenStack for more details. ? "The way how OpenStack networking was propagated over data networks turned out to be very problematic and caused hitting the wall a few times. In details you have to configure data networks over the platform management components, but then you have to set VLAN's you are going to use over data networks on the OpenStack side. This was not documented anywhere." * no update: All -- Wiki status ? Revisit planned migration of wiki content: lets close this out (see yellow). https://docs.google.com/spreadsheets/d/1UJjUttsWQRyauATrip0wKGIxSO7DvyetDKmPwvEIDaA/edit?usp=sharing ? Virtual Box wiki converted to RST file. Review available: https://review.opendev.org/#/c/711769/ ? Latest patch set includes Bart's comments as separate method in the VB network guide. ? When this gets merged, the old wiki topic will be removed, noted as deprecated. Keep going through to get these last few topics migrated. * Reviews in progress: ? https://review.opendev.org/#/c/714762/ Ritu Raj - adds text and diagrams to improve AIO Simplex installation. AR Mary check latest and fix merge ? https://review.opendev.org/#/c/714821/ Mary - Certificate config and management * no update: New topics for us to document. Both are coming from Intel field teams supporting customers (brucej) ? Mary emailed Ghada on 17Mar20, asking for folks to contact for help on these topics: * High availability and failover mechanisms for applications and for SM. [SM we may have in training in wiki, but HA and failover need more info (for industrial customers) Good idea to document best practices how to build these. ] * Networking - how to bridge / combine K8S and OpenStack networks for applications [Need to capture this info, but unclear who could provide this info. Need diagrams to show how it works externally.] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Apr 3 20:34:59 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 3 Apr 2020 22:34:59 +0200 Subject: [Starlingx-discuss] CNCF conformance review merged Message-ID: Hi, I wanted to quickly update the community that the PR to add StarlingX to the CNCF landscape as a Kubernetes conformant platform got merged: https://github.com/cncf/k8s-conformance/pull/891 You can see the project listed here: https://landscape.cncf.io/format=card-mode&organization=open-stack&selected=starling-x Thanks and Best Regards, Ildikó From bruce.e.jones at intel.com Fri Apr 3 20:45:39 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 3 Apr 2020 20:45:39 +0000 Subject: [Starlingx-discuss] CNCF conformance review merged In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BFB079D6A@fmsmsx123.amr.corp.intel.com> Thank you Ildiko! brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Friday, April 3, 2020 1:35 PM To: starlingx Subject: [Starlingx-discuss] CNCF conformance review merged Hi, I wanted to quickly update the community that the PR to add StarlingX to the CNCF landscape as a Kubernetes conformant platform got merged: https://github.com/cncf/k8s-conformance/pull/891 You can see the project listed here: https://landscape.cncf.io/format=card-mode&organization=open-stack&selected=starling-x 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 glenn.seiler at windriver.com Fri Apr 3 20:45:54 2020 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Fri, 3 Apr 2020 20:45:54 +0000 Subject: [Starlingx-discuss] CNCF conformance review merged In-Reply-To: References: Message-ID: Fantastic. Thank you Ildiko. ________________________________ From: Ildiko Vancsa Sent: Friday, April 3, 2020 1:34:59 PM To: starlingx Subject: [Starlingx-discuss] CNCF conformance review merged Hi, I wanted to quickly update the community that the PR to add StarlingX to the CNCF landscape as a Kubernetes conformant platform got merged: https://github.com/cncf/k8s-conformance/pull/891 You can see the project listed here: https://landscape.cncf.io/format=card-mode&organization=open-stack&selected=starling-x 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Apr 4 01:32:06 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 3 Apr 2020 21:32:06 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 498 - Failure! Message-ID: <1067565720.1139.1585963927948.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 498 Status: Failure Timestamp: 20200404T013012Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200404T013012Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From ildiko.vancsa at gmail.com Sat Apr 4 17:47:27 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Sat, 4 Apr 2020 19:47:27 +0200 Subject: [Starlingx-discuss] Broken link on starlingx.io In-Reply-To: <9A85D2917C58154C960D95352B22818BFB079B63@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BFB079B63@fmsmsx123.amr.corp.intel.com> Message-ID: <361DA179-099E-4C6E-9C19-8330EEBBA913@gmail.com> Hi, I created a PR to fix the issue: https://github.com/StarlingXWeb/starlingx-website/pull/74 There was a recent restructuring under the hood to improve some aspects of the website which I believe is what caused those links to break. Thanks, Ildikó > On Apr 3, 2020, at 20:16, Jones, Bruce E wrote: > > The web pages are managed in a git repo [1]. We all as a community take care of them, and anyone can submit a PR against them. You can do it, Steven, or we can ask the Docs team to help. > > Brucej > > [1] https://github.com/StarlingXWeb/starlingx-website > > From: Webster, Steven [mailto:Steven.Webster at windriver.com] > Sent: Friday, April 3, 2020 11:00 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Broken link on starlingx.io > > Hi All, > > I noticed that the link to the StarlingX Powerpoint templates at https://www.starlingx.io/faq/ is broken. Does anybody know who takes care of these pages? > > Cheers, > > Steve > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From alexandru.dimofte at intel.com Sun Apr 5 16:17:26 2020 From: alexandru.dimofte at intel.com (Dimofte, Alexandru) Date: Sun, 5 Apr 2020 16:17:26 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200405 Message-ID: Sanity Test from 2020-April-05 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200405T013011Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - 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 External - 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, STX Validation Team [cid:image002.png at 01D60B7E.D3C116C0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte at intel.com Intel Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10911 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 20507 bytes Desc: image002.png URL: From abhideodhar at gmail.com Mon Apr 6 06:14:17 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Mon, 6 Apr 2020 11:44:17 +0530 Subject: [Starlingx-discuss] StarlingX install question Message-ID: Hi, I am trying to install StarlingX on virtual standard with controller storage configuration. I am following the steps mentioned in this document: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html I reached the step where 2 controllers and 2 workers are up and running. Now I am confused with "configure controller-1" step. https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 I see an error while doing this step on controller-1: [image: image.png] I tried using sudo to repeat the step: [image: image.png] Can someone please help me with this step to proceed with the installation? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 6768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9305 bytes Desc: not available URL: From abhideodhar at gmail.com Mon Apr 6 06:24:40 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Mon, 6 Apr 2020 11:54:40 +0530 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Forgot to mention that I tried doing this step to enter the admin mode, but the openrc script doesnt seem to exist on controller-1 [image: image.png] So I am not sure how to proceed. Please advise. ~Abhijit On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar wrote: > Hi, > > I am trying to install StarlingX on virtual standard with controller > storage configuration. I am following the steps mentioned in this document: > > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html > > > I reached the step where 2 controllers and 2 workers are up and running. > Now I am confused with "configure controller-1" step. > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 > > > I see an error while doing this step on controller-1: > > [image: image.png] > > I tried using sudo to repeat the step: > [image: image.png] > > Can someone please help me with this step to proceed with the installation? > > Regards > Abhijit > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 6768 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 9305 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 5108 bytes Desc: not available URL: From Shigeru.Yoshida at windriver.com Mon Apr 6 07:00:57 2020 From: Shigeru.Yoshida at windriver.com (Yoshida, Shigeru) Date: Mon, 6 Apr 2020 07:00:57 +0000 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Hi Abhijit, Please try following commands on controller-0: source /etc/platform/openrc OAM_IF=enp2s1 system host-if-modify controller-1 $OAM_IF -c platform system interface-network-assign controller-1 $OAM_IF oam system interface-network-assign controller-1 mgmt0 cluster-host controller-1 is not configured at that point and system command normally be activated on active controller. Thanks, Shigeru From: Abhijit Deodhar Sent: Monday, April 6, 2020 3:25 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX install question Forgot to mention that I tried doing this step to enter the admin mode, but the openrc script doesnt seem to exist on controller-1 So I am not sure how to proceed. Please advise. ~Abhijit On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar wrote: Hi, I am trying to install StarlingX on virtual standard with controller storage configuration. I am following the steps mentioned in this document: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html  I reached the step where 2 controllers and 2 workers are up and running. Now I am confused with "configure controller-1" step.  https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1    I see an error while doing this step on controller-1: I tried using sudo to repeat the step: Can someone please help me with this step to proceed with the installation? Regards Abhijit From abhideodhar at gmail.com Mon Apr 6 07:08:09 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Mon, 6 Apr 2020 12:38:09 +0530 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Ok, I tried that step and it worked. But now I am hitting an issue at the next step: [image: image.png] How to get past this error or debug it? Thanks Abhijit On Mon, Apr 6, 2020 at 12:30 PM Yoshida, Shigeru < Shigeru.Yoshida at windriver.com> wrote: > Hi Abhijit, > > Please try following commands on controller-0: > > source /etc/platform/openrc > OAM_IF=enp2s1 > system host-if-modify controller-1 $OAM_IF -c platform > system interface-network-assign controller-1 $OAM_IF oam > system interface-network-assign controller-1 mgmt0 cluster-host > > controller-1 is not configured at that point and system command normally > be activated on active controller. > > Thanks, > Shigeru > > > From: Abhijit Deodhar > Sent: Monday, April 6, 2020 3:25 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] StarlingX install question > > Forgot to mention that I tried doing this step to enter the admin mode, > but the openrc script doesnt seem to exist on controller-1 > > > > > So I am not sure how to proceed. > > Please advise. > > ~Abhijit > > On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar abhideodhar at gmail.com> wrote: > Hi, > > I am trying to install StarlingX on virtual standard with controller > storage configuration. I am following the steps mentioned in this document: > > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html > > > I reached the step where 2 controllers and 2 workers are up and running. > Now I am confused with "configure controller-1" step. > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 > > > I see an error while doing this step on controller-1: > > > > I tried using sudo to repeat the step: > > > Can someone please help me with this step to proceed with the installation? > > Regards > Abhijit > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 24894 bytes Desc: not available URL: From alfredo.deluca at gmail.com Mon Apr 6 08:09:17 2020 From: alfredo.deluca at gmail.com (Alfredo De Luca) Date: Mon, 6 Apr 2020 10:09:17 +0200 Subject: [Starlingx-discuss] Openstack on the Central Cloud In-Reply-To: References: Message-ID: Thanks Bart. Appreciated /Alfredo On Fri., 3 Apr. 2020, 6:18 pm Wensley, Barton, wrote: > Alfredo, > > > > There is currently no support for OpenStack on distributed cloud systems. > This feature has not been implemented yet. > > > > Bart > > > > *From:* Alfredo De Luca [mailto:alfredo.deluca at gmail.com] > *Sent:* April 3, 2020 11:02 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Openstack on the Central Cloud > > > > Hi all. > > We deployed STX 3.0 in 2 baremetal machine as Central Cloud and on 2 other > baremetals we deployed 2 edge sub-clouds. > > All ok and working fine. Now we tried to install Openstack helm as per > below.... > > > *wget http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos/outputs/helm-charts/stx-openstack-1.0-19-centos-stable-latest.tgz system application-upload stx-openstack-1.0-19-centos-stable-latest.tgz* > > But it's not working. > > > > So my questions is: > > Is it possible to deploy openstack on the Central Cloud? > > Cheers > > > > -- > > *Alfredo* > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Apr 6 13:51:59 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 6 Apr 2020 15:51:59 +0200 Subject: [Starlingx-discuss] Project confirmation review slides Message-ID: <561F61A2-AC7F-470A-8BAC-5B4AB7B61BB5@gmail.com> Hi, As the community is approaching the confirmation review soon I collected the links to the presentations of other confirmed OSF projects for reference: Kata Containers: https://docs.google.com/presentation/d/1yLY9jbzlt2JHmz4NcGQF78wwckKS6mJja0F5RnM9yQI/edit#slide=id.g4a39e0bbac_0_418 Airship: https://docs.google.com/presentation/d/1tPz0vIj5_-vWYfeqrQZtI6X5P5lZWOKZgy1liHs-dMo/edit#slide=id.g63bf7c793e_1_65 Zuul: https://zuul-ci.org/confirmation/ Hope this helps. Thanks, Ildikó From cboylan at sapwetik.org Mon Apr 6 17:50:15 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 06 Apr 2020 10:50:15 -0700 Subject: [Starlingx-discuss] New OpenDev Communication Channels Message-ID: <337e23d8-8ae8-4f03-a83c-64add1b450ec@www.fastmail.com> Hello All, Recently, we've transitioned to using #opendev on Freenode for our synchronous IRC communications. Since then we've spun up a new service-discuss at lists.opendev.org mailing list [1] where we'll plan changes to services, notify of meetings, answer questions about services and usage, and otherwise communicate about OpenDev. service-announce at lists.opendev.org [2] will remain for important announcements. If you're interested in the developer infrastructure we run please join us on these mailing lists. We encourage every developer to at least subscribe to the service-announce[2] list. It will be very low traffic, and used only for important announcements with wide impact. We are also going to start having our weekly team meeting in #opendev-meeting. The time will continue to be 19:00 UTC Tuesdays. See you there, Clark [1] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss [2] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce From ildiko.vancsa at gmail.com Mon Apr 6 18:59:02 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 6 Apr 2020 20:59:02 +0200 Subject: [Starlingx-discuss] OSF Community Presentation & Recording Message-ID: <2F087424-073A-4E1E-BFC8-C878EF2A8C70@gmail.com> Hi everyone, Thank you to those who attended any of the community meetings last week! If you missed one of the calls last week, below are links to the presentation [1], recording in English [2], and recording in Mandarin [3]. A lot of links were discussed and you can find those in the meeting section of the notes as well as the chat from the recordings. We are planning to do this format with project and community updates and OSF event updates quarterly. Stay tuned for the next meeting, and let me know if you have any questions in the meantime. In addition to the quarterly meetings, we would like to hear from the project communities on topics you would like to cover in community meetings or have covered. If you have an idea you would like to share, please drop it in this etherpad [4]. If you see a topic already shared that you would like to collaborate on, please share your name, email and IRC nick next to the topic. Thanks, Ildikó [1] https://docs.google.com/presentation/d/1l05skj_BCfF8fgYWu4n0b1rQmbNhHp8sMeYcb-v-rdA/edit?usp=sharing [2] https://zoom.us/rec/share/7vVXdIvopzxIYbPztF7SVpAKXYnbX6a82iMaqfZfmEl1b0Fqb6j3Zh47qPSV_ar2 [3] https://zoom.us/rec/share/zudNaIrQ6mNLR9Lvr2Xxf5QQIL7geaa8hCcf_vsIxEwoHkn0b8k_fEoYuXLsNi8C?startTime=1585879294000 [4] https://etherpad.openstack.org/p/OSF_Community_Meetings From build.starlingx at gmail.com Mon Apr 6 21:52:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 6 Apr 2020 17:52:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_last_commits - Build # 190 - Failure! Message-ID: <1299474289.1147.1586209971028.JavaMail.javamailuser@localhost> Project: STX_last_commits Build #: 190 Status: Failure Timestamp: 20200406T215247Z Check logs at: $PUBLISH_LOGS_URL -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20200406T213947Z MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers From abhideodhar at gmail.com Tue Apr 7 03:47:13 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Tue, 7 Apr 2020 09:17:13 +0530 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: can someone please help me? Regards Abhijit On Mon, Apr 6, 2020 at 12:38 PM Abhijit Deodhar wrote: > Ok, I tried that step and it worked. But now I am hitting an issue at the > next step: > [image: image.png] > > How to get past this error or debug it? > > Thanks > Abhijit > > On Mon, Apr 6, 2020 at 12:30 PM Yoshida, Shigeru < > Shigeru.Yoshida at windriver.com> wrote: > >> Hi Abhijit, >> >> Please try following commands on controller-0: >> >> source /etc/platform/openrc >> OAM_IF=enp2s1 >> system host-if-modify controller-1 $OAM_IF -c platform >> system interface-network-assign controller-1 $OAM_IF oam >> system interface-network-assign controller-1 mgmt0 cluster-host >> >> controller-1 is not configured at that point and system command normally >> be activated on active controller. >> >> Thanks, >> Shigeru >> >> >> From: Abhijit Deodhar >> Sent: Monday, April 6, 2020 3:25 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] StarlingX install question >> >> Forgot to mention that I tried doing this step to enter the admin mode, >> but the openrc script doesnt seem to exist on controller-1 >> >> >> >> >> So I am not sure how to proceed. >> >> Please advise. >> >> ~Abhijit >> >> On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar > abhideodhar at gmail.com> wrote: >> Hi, >> >> I am trying to install StarlingX on virtual standard with controller >> storage configuration. I am following the steps mentioned in this document: >> >> >> https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html >> >> >> I reached the step where 2 controllers and 2 workers are up and running. >> Now I am confused with "configure controller-1" step. >> >> https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 >> >> >> I see an error while doing this step on controller-1: >> >> >> >> I tried using sudo to repeat the step: >> >> >> Can someone please help me with this step to proceed with the >> installation? >> >> Regards >> Abhijit >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 24894 bytes Desc: not available URL: From oliver.lovaszi at intel.com Tue Apr 7 06:46:02 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Tue, 7 Apr 2020 06:46:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200406 Message-ID: Sanity Test from 2020-April-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200405T230013Z/outputs/iso/) 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 [PASS] 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 External - 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 [Not executed] Virtual tests were not triggered for this image. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver.lovaszi at intel.com Tue Apr 7 06:53:18 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Tue, 7 Apr 2020 06:53:18 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200405 In-Reply-To: References: Message-ID: Sanity Test from 2020-April-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200405T080246Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) [BLOCKED] Setup 04 TCs [PASS] The sanity was blocked because we faced this issue: https://bugs.launchpad.net/starlingx/+bug/1856078 TOTAL: [ 4 TCs ] Standard External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhideodhar at gmail.com Mon Apr 6 07:00:59 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Mon, 6 Apr 2020 12:30:59 +0530 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Ok, I tried it from controller-0 and that step worked. But now I am stuck at the next step: [image: image.png] Since the step failed, I tried to repeat it. But I get an already configured error as shown below: [image: image.png] Please advise on how to proceed further? Thank you Abhijit On Mon, Apr 6, 2020 at 12:23 PM Yoshida, Shigeru < Shigeru.Yoshida at windriver.com> wrote: > Hi Abhijit, > > > > Please try following commands on controller-0: > > > > source /etc/platform/openrc > > OAM_IF=enp2s1 > > system host-if-modify controller-1 $OAM_IF -c platform > > system interface-network-assign controller-1 $OAM_IF oam > > system interface-network-assign controller-1 mgmt0 cluster-host > > > > controller-1 is not configured at that point and system command normally > be activated on active controller. > > > > Thanks, > > Shigeru > > > > *From:* Abhijit Deodhar > *Sent:* Monday, April 6, 2020 3:25 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] StarlingX install question > > > > Forgot to mention that I tried doing this step to enter the admin mode, > but the openrc script doesnt seem to exist on controller-1 > > > > > > [image: image.png] > > > > So I am not sure how to proceed. > > > > Please advise. > > > > ~Abhijit > > > > On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar > wrote: > > Hi, > > > > I am trying to install StarlingX on virtual standard with controller > storage configuration. I am following the steps mentioned in this document: > > > > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html > > > > > I reached the step where 2 controllers and 2 workers are up and running. > Now I am confused with "configure controller-1" step. > > > https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 > > > > > I see an error while doing this step on controller-1: > > > > [image: image.png] > > > > I tried using sudo to repeat the step: > > [image: image.png] > > > > Can someone please help me with this step to proceed with the installation? > > > > Regards > > Abhijit > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5108 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 35463 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 48750 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 25096 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 4877 bytes Desc: not available URL: From oliver.lovaszi at intel.com Mon Apr 6 14:49:21 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Mon, 6 Apr 2020 14:49:21 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200405 Message-ID: Sanity Test from 2020-April-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200405T080246Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) [BLOCKED] Setup 04 TCs [PASS] The sanity was blocked because we faced this issue: https://bugs.launchpad.net/starlingx/+bug/1856078 TOTAL: [ 4 TCs ] Standard External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From oliver.lovaszi at intel.com Tue Apr 7 05:50:22 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Tue, 7 Apr 2020 05:50:22 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200405 In-Reply-To: References: Message-ID: Sanity Test from 2020-April-06 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200405T080246Z/outputs/iso/ ) 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 [PASS] 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 External - 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) [BLOCKED] Setup 04 TCs [PASS] The sanity was blocked because we faced this issue: https://bugs.launchpad.net/starlingx/+bug/1856078 TOTAL: [ 4 TCs ] Standard External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Apr 7 07:46:02 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 7 Apr 2020 07:46:02 +0000 Subject: [Starlingx-discuss] Agenda for WW15.2 (April 7) Distro-OpenStack project meeting Message-ID: <6AB6FA83-FCE4-4234-93A9-9E13880A2FCA@intel.com> Agenda: 1. Containerized OpenStack Service Upgrade to “Ussuri” -Chant/Kunpeng @99Cloud, Zhipeng at Intel 2. Host OpenStack Clients and services Upgrade to “Train” – Yan at Intel 3. LP review - All [0]:upgrade plan in details: https://docs.google.com/spreadsheets/d/1BEHR7kFxbnN4h2IN0O5tJS7WJlYaET7eoUiDtOmsOtE/edit#gid=568723700 [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Apr 7 08:11:02 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 7 Apr 2020 08:11:02 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 4/8/2020 Message-ID: Agenda for 4/8 meeting: - Kata container As Brent request , discuss kata evluation. - ceph containerization https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/716792/ https://review.opendev.org/#/c/714857/ - centos8 upgrade (shuicheng/Austin) kernel-rt upgrade: - Jim ask for provide kernel-rt srpm , how to handle this ? - Test team from intel cannot start eb as infrastructure is not ready this week. centos8 branch rebase - python3 upgrade status (An Ran) -open From yan.chen at intel.com Tue Apr 7 08:11:07 2020 From: yan.chen at intel.com (Chen, Yan) Date: Tue, 7 Apr 2020 08:11:07 +0000 Subject: [Starlingx-discuss] Agenda for WW15.2 (April 7) Distro-OpenStack project meeting In-Reply-To: <6AB6FA83-FCE4-4234-93A9-9E13880A2FCA@intel.com> References: <6AB6FA83-FCE4-4234-93A9-9E13880A2FCA@intel.com> Message-ID: <9752d688adef4d1387ca12c1d297146f@intel.com> Hi All For the task Host OpenStack Clients and services upgrade to “train”, here’s the patch list for review: https://review.opendev.org/#/q/status:open+topic:train_upgrade Storyboard: https://storyboard.openstack.org/#!/story/2007502 Thanks! Yan From: Hu, Yong Sent: Tuesday, April 7, 2020 3:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda for WW15.2 (April 7) Distro-OpenStack project meeting Agenda: 1. Containerized OpenStack Service Upgrade to “Ussuri” -Chant/Kunpeng @99Cloud, Zhipeng at Intel 2. Host OpenStack Clients and services Upgrade to “Train” – Yan at Intel 3. LP review - All [0]:upgrade plan in details: https://docs.google.com/spreadsheets/d/1BEHR7kFxbnN4h2IN0O5tJS7WJlYaET7eoUiDtOmsOtE/edit#gid=568723700 [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Apr 7 09:13:01 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Apr 2020 05:13:01 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 217 - Failure! Message-ID: <1189587865.1156.1586250783679.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 217 Status: Failure Timestamp: 20200407T091256Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200407T091246Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: flock.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200407T091246Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200407T091246Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From build.starlingx at gmail.com Tue Apr 7 09:13:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 7 Apr 2020 05:13:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 73 - Failure! Message-ID: <1149425428.1159.1586250786895.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 73 Status: Failure Timestamp: 20200407T091246Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200407T091246Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From oliver.lovaszi at intel.com Tue Apr 7 11:47:35 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Tue, 7 Apr 2020 11:47:35 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200406 Message-ID: Sanity Test from 2020-April-07 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200406T230012Z/outputs/iso/ ) 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 [PASS] 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 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - 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 External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 47 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 61 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Apr 7 16:36:24 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 7 Apr 2020 18:36:24 +0200 Subject: [Starlingx-discuss] Looking for election officials Message-ID: <0224D32D-CCAC-4238-BDA8-F4ADD961C50B@gmail.com> Hi StarlingX Community, As you know we have an election process to ensure to have people from the community elected by the community stepping up to take leadership positions. If you’re unfamiliar you can read more about the process here: https://docs.starlingx.io/election/ We have a small group of election officials who have the duties to drive the process and ensure it goes as described on the aforementioned page. In order to pass on the experience and knowledge as well as let the current officials to run for some positions themselves we are looking for people who would be interested in learning the process and helping out to run it. Please respond to this thread or reach out to me if you’re interested in joining the election officials group! Thanks and Best Regards, Ildikó (IRC: ildikov) From sgw at linux.intel.com Tue Apr 7 18:58:11 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 7 Apr 2020 11:58:11 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: Hi Yipeng, Sorry for the delay in getting back to you, I was looking into the build failure and trying understand how we handle the difference between the PBR SemVer [0] and PEP440 [1]. Specifically when there is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. So we need to also change the spec files %files section for the egg-info file to wild-card that file instead of having a specific version listed. For example in the starlingx-dashboard spec file: diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec b/starlingx-dashboard/centos/starlingx-dashboard.spec index 7fbee65..399a9bd 100644 --- a/starlingx-dashboard/centos/starlingx-dashboard.spec +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT %files %{python2_sitelib}/%{py_pkg_name} -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info +%{python2_sitelib}/%{py_pkg_name}-*.egg-info %{enabled_dir} %{stx_themes_dir} And as discussed in Jeremy's email we should be adding the "Sem-Ver: feature" in the commit message, just once per repo. See Bin's pending commit in fault [2]. You will have to back and fix fault and other pending commits with the wild-card change for the egg-info file in the spec file. Finally all PBR related reviews should have a Depends-On: https://review.opendev.org/#/c/691632/ So it does not get merged before the enabling code in the build tools merges. Hope this clarifies things and gets the PBR work unblocked. I am going through the reviews and trying to provide some additional review comments. We can also talk about this tomorrow during the Distro call [3] Sau! [0] https://docs.openstack.org/pbr/3.0.0/semver.html [1] https://www.python.org/dev/peps/pep-0440/ [2] https://review.opendev.org/#/c/691647/ [3] On 3/30/20 6:52 PM, 何义鹏 wrote: > >  Saul! > > Thank you for your answer! But how should I use the semMem-ver tag? > ------------------ Original ------------------ > *From: * "Saul Wold"; > *Date: * Sat, Mar 28, 2020 07:02 AM > *To: * "何义鹏"; "Penney, > Don"; "Scott > Little"; "Miller, > Frank"; > *Cc: * "曹明晓"; "杨永金" > ; "桂来军"; > "starlingx-discuss"; > *Subject: * Re: [Starlingx-discuss] enable pbr version > Yipeng, > > > I replied the other day, wanting to confirm if you have any additional > changes in your local git repo? It seems that we need to consider a > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: > feature" tag in a commit to move the pbr versioning forward. > > BUILD Team (Don, Scott, Frank): > > Here's the general issue, we tag on the release branches, not master > (although we have a v3.0.0.rc0 tag on master), we need to either add a > Sem_Ver: feature tag to increment version's major number, or add a > pre-tag of the 4.0 release. > > Thoughts from the build team?  I think we discussed part of the before, > but want to do a quick revisit of the thread back in Nov [1], I think we > had agreed to use Sem_Ver but it's not in the email thread > > > [0] > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html > > > On 3/26/20 7:26 PM, 何义鹏 wrote: > > > > Yes, building the rpm of the starlingx dashboard is a necessary step for > > my build-iso. > > > > Maybe Saul can respond to the question that python builds allow several > > versions of components. > > > Jeremy replied to this earlier in the week, the issue appears to be the > way we tagged rc0, we might need to have change our tagging.  He also > stated that the number of components is not a limiting factor. > > Sau! > > ------------------ Original ------------------ > > *From: * "Penney, Don"; > > *Date: * Wed, Mar 25, 2020 10:11 PM > > *To: * "何义鹏"; "Saul > > Wold(sgw at linux.intel.com)"; > > *Cc: > > > * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; > > > > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version > > > > Please keep starlingx-discuss on the receiver list. > > > > You had indicated build-iso was failing, but the build.log you provided > > appears to be the RPM build log for starlingx-dashboard. > > > > Processing files: starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch > > > > error: File not found: > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > > > RPM build errors: > > > >      File not found: > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > > > > Child return code was: 1 > > > > EXCEPTION: [Error()] > > > > Traceback (most recent call last): > > > >    File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", > > line 95, in trace > > > >      result = func(*args, **kw) > > > >    File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line 746, > > in do_with_status > > > >      raise exception.Error("Command failed: \n # %s\n%s" % (command, > > output), child.returncode) > > > > mockbuild.exception.Error: Command failed: > > > >   # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps > > /builddir/build/SPECS/starlingx-dashboard.spec > > > > Looking through the build.log, I see the following: > > > > Copying starlingx_dashboard.egg-info to > > > build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info > > > > So in the build, it’s creating the egg with the version set to > > 2.9999.9999rc1.dev23, while the %files is expecting it to be > > 2.9999.9999.rc1.dev23. > > > > Looking further through the build.log, there’s the following: > > > > + /usr/bin/python2 setup.py install -O1 --skip-build --root > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 > > > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' > > > >    normalized_version, > > > > running install > > > > Maybe the python build only allows 4 version components? > > > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] > > *Sent:* Tuesday, March 24, 2020 9:59 PM > > *To:* Penney, Don > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version > > > > Hi Saul, > > > > I added the error log to the attachment. Do you need other files for > > analysis? > > > > Thank you for your help. > > > >     yipeng.he! > > > > ------------------ Original ------------------ > > > > *From: * "Penney, Don"; > > > > *Date: * Wed, Mar 25, 2020 04:24 AM > > > > *To: * "Saul Wold"; "何义鹏" > ; > > > > *Cc: * "桂来军"; "杨永金" > > ; "曹明晓"; > > "starlingx-discuss"; > > > > *Subject: * RE: [Starlingx-discuss] enable pbr version > > > > Hi Yipeng, > > > > Can you provide more info? What was the error you saw from build-iso? > > > > > > -----Original Message----- > > From: Saul Wold [mailto:sgw at linux.intel.com] > > Sent: Monday, March 23, 2020 6:45 PM > > To: 何义鹏 > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss > > Subject: Re: [Starlingx-discuss] enable pbr version > > > > > > Hi Yipeng, > > > > I was out last week on vacation, so I am catching up now. > > > > I think you would have to investigate build-iso and associated scripts > > and tools to see if there is an awk, sed or some other command that is > > not parsing the extended version.  I have not investigated this further, > > that's my initial assessment. > > > > Can you be more specific about what the error is or provide a log file > > of the build-iso process? > > > > Thanks for working on this project. > > > >    Sau! > > > > > > > > On 3/19/20 12:21 AM, 何义鹏wrote: > >> Hello Saul > >> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. > >> I encountered the following issue when trying to build iso: > >> It fails when the suffix of the version generated by the PBR tool ended > >> with number, for instance the building fails if the version id is > >> 2.999.9999.rc1.dev23, > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO building was > >> successful. > >> I don't knwo why this happens, could please support and advice the > >> solution for this issue. > >> > >> > >> Yipeng.He > >> > >> _______________________________________________ > >> 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 Frank.Miller at windriver.com Tue Apr 7 21:59:53 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 7 Apr 2020 21:59:53 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo Message-ID: Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhideodhar at gmail.com Wed Apr 8 04:57:11 2020 From: abhideodhar at gmail.com (Abhijit Deodhar) Date: Wed, 8 Apr 2020 10:27:11 +0530 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Please help me On Mon, Apr 6, 2020 at 12:38 PM Abhijit Deodhar wrote: > Ok, I tried that step and it worked. But now I am hitting an issue at the > next step: > [image: image.png] > > How to get past this error or debug it? > > Thanks > Abhijit > > On Mon, Apr 6, 2020 at 12:30 PM Yoshida, Shigeru < > Shigeru.Yoshida at windriver.com> wrote: > >> Hi Abhijit, >> >> Please try following commands on controller-0: >> >> source /etc/platform/openrc >> OAM_IF=enp2s1 >> system host-if-modify controller-1 $OAM_IF -c platform >> system interface-network-assign controller-1 $OAM_IF oam >> system interface-network-assign controller-1 mgmt0 cluster-host >> >> controller-1 is not configured at that point and system command normally >> be activated on active controller. >> >> Thanks, >> Shigeru >> >> >> From: Abhijit Deodhar >> Sent: Monday, April 6, 2020 3:25 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] StarlingX install question >> >> Forgot to mention that I tried doing this step to enter the admin mode, >> but the openrc script doesnt seem to exist on controller-1 >> >> >> >> >> So I am not sure how to proceed. >> >> Please advise. >> >> ~Abhijit >> >> On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar > abhideodhar at gmail.com> wrote: >> Hi, >> >> I am trying to install StarlingX on virtual standard with controller >> storage configuration. I am following the steps mentioned in this document: >> >> >> https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html >> >> >> I reached the step where 2 controllers and 2 workers are up and running. >> Now I am confused with "configure controller-1" step. >> >> https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 >> >> >> I see an error while doing this step on controller-1: >> >> >> >> I tried using sudo to repeat the step: >> >> >> Can someone please help me with this step to proceed with the >> installation? >> >> Regards >> Abhijit >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 24894 bytes Desc: not available URL: From build.starlingx at gmail.com Wed Apr 8 08:02:59 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 8 Apr 2020 04:02:59 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 226 - Failure! Message-ID: <471163157.1184.1586332981254.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 226 Status: Failure Timestamp: 20200408T080254Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200408T080244Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: flock.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200408T080244Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200408T080244Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock From build.starlingx at gmail.com Wed Apr 8 08:03:03 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 8 Apr 2020 04:03:03 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 74 - Still Failing! In-Reply-To: <2028258383.1157.1586250784491.JavaMail.javamailuser@localhost> References: <2028258383.1157.1586250784491.JavaMail.javamailuser@localhost> Message-ID: <49061547.1187.1586332984572.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 74 Status: Still Failing Timestamp: 20200408T080244Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200408T080244Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false From stasik at stasik.com Wed Apr 8 09:49:28 2020 From: stasik at stasik.com (Sten Gruener) Date: Wed, 8 Apr 2020 11:49:28 +0200 Subject: [Starlingx-discuss] Load Balancer for k8s in StarlingX In-Reply-To: References: Message-ID: Dear community, I'd like to use StarlingX as k8s cluster, is there some LoadBalancer provided like metalLB or how am I supposed to expose services externally? Is there a generic recommendation or best practice to expose services available also in a High Availability setting? BR Sten > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Apr 8 11:35:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Apr 2020 11:35:27 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 8, 2020) Message-ID: Hi all, reminder of the TSC/Community call coming up. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200408T1400 From Bill.Zvonar at windriver.com Wed Apr 8 12:03:32 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Apr 2020 12:03:32 +0000 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Hi Abhijit, I’ll put this on the agenda for the community call today, will see if we can get someone to help out. Bill… From: Abhijit Deodhar Sent: Wednesday, April 8, 2020 12:57 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX install question Please help me On Mon, Apr 6, 2020 at 12:38 PM Abhijit Deodhar > wrote: Ok, I tried that step and it worked. But now I am hitting an issue at the next step: [image.png] How to get past this error or debug it? Thanks Abhijit On Mon, Apr 6, 2020 at 12:30 PM Yoshida, Shigeru > wrote: Hi Abhijit, Please try following commands on controller-0: source /etc/platform/openrc OAM_IF=enp2s1 system host-if-modify controller-1 $OAM_IF -c platform system interface-network-assign controller-1 $OAM_IF oam system interface-network-assign controller-1 mgmt0 cluster-host controller-1 is not configured at that point and system command normally be activated on active controller. Thanks, Shigeru From: Abhijit Deodhar > Sent: Monday, April 6, 2020 3:25 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX install question Forgot to mention that I tried doing this step to enter the admin mode, but the openrc script doesnt seem to exist on controller-1 So I am not sure how to proceed. Please advise. ~Abhijit On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar > wrote: Hi, I am trying to install StarlingX on virtual standard with controller storage configuration. I am following the steps mentioned in this document: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html I reached the step where 2 controllers and 2 workers are up and running. Now I am confused with "configure controller-1" step. https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 I see an error while doing this step on controller-1: I tried using sudo to repeat the step: Can someone please help me with this step to proceed with the installation? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 53164 bytes Desc: image003.png URL: From nicolae.jascanu at intel.com Tue Apr 7 18:11:02 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 7 Apr 2020 18:11:02 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 04/07/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 04/07/2020 Attendees: Mihail, Nicolae, Cosmin, Claudiu, Bruce, Ambarish, George, Oliver, Ruediger 1. Sanity Status: * Sanity issues reported by WR: * 1855474 - OpenStack pods were not recovered after force reboot active controller * 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps) * https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock * https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response * https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation * Sanity issues reported by Intel: * This week: ? executed on Monolithic - green ? executed on Layered - no new discoveries * Private registry used by Intel: some container images changed and not picked up in private registry - now resolved ? manually update the mirror registry * May look into adding ipv6 configs for the long term * Rework the Jenkins jobs ? virtual sanity check is trigered automatically ? baremetal sanity check is trigered manually - in order to control the Monolitic and Layered * pipeline to trigger the virtual 2. stx4.0 testing * Release plan: * https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 * Kata: intend to start early. target test complete by 05/08 * Rook: intend to start early. target test complete by 05/22 * Fault containerization: target test complete by 05/29 * Centos8: no server with TPM, mellanox cards; integrity may not be testable * TSN support in kata container: target test complete by 05/29 * OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04 * OpenStack upversion: ? automated and manual test update needed, may be time consuming ? target 06-05 * Layered build is being tested daily with issues ? image did not build - fixed ? 03-31 build still failed, but went further * Targeted feature completion date: 06-08 * Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing * Targeted regresion completion date: 06-15 (pushing out 1 week) * Propose no openstack regression between 06-08 to 06-15 3. Feature testing: * Engineering Build received on Monday for Kernel upgrade * TMP * Network regression tests using servers with Mellanox * Engineering Build it is expected at the end of week to test containerezed features * Feature: ? Kata - information is gathered in Intel's wiki. 4. Unified santiy * Intel will bring in robot sanity as is into pytest framework ? Almost all the converted test cases are pushed in openstream * For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones ? need to be aligned with Yang - on features, naming, folders ? need to look at the existing pytest sanity * Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment * The commits from Gitlab where pushed into opendev ? use for sanity setup the opendev code 4. Opens * Servers/test environment setup within Nic's team: * In progress - cabling, configuring ports, etc ? today work in progress at switches ? almost ready the faceless account * Will know more by end of week. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From austin.sun at intel.com Wed Apr 8 14:00:29 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 8 Apr 2020 14:00:29 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 4/8/2020 Message-ID: MoM for 4/8 meeting: - Kata container Steven shared a good evelution. Thanks Steven kata will release new version @4/22 - ceph containerization https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/716792/ https://review.opendev.org/#/c/714857/ martin will share the migration steps once it is ready/ - centos8 upgrade (shuicheng/Austin) kernel-rt upgrade: - Jim ask for provide kernel-rt srpm , how to handle this ? https://review.opendev.org/#/c/711152/ further discuss via email. - Test team from intel cannot start eb as infrastructure is not ready this week. centos8 branch rebase. one nfv git is under review due to zuul failure will enable layer builder once zuul failure fixx - python3 upgrade status (An Ran) engtools --> reviewed logmgmt --> committed under testing nova-api-proxy---> committed under testing work-utils ---> not committed yet . 7 will generate and pre-test , but not target for stx.4.0 others will do exploration on centos8 feature branch - PBR -open Thanks. BR Austin Sun. From Barton.Wensley at windriver.com Wed Apr 8 15:03:04 2020 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 8 Apr 2020 15:03:04 +0000 Subject: [Starlingx-discuss] StarlingX install question In-Reply-To: References: Message-ID: Abhijit, I have a few suggestions that might help: · If this is your first time installing StarlingX, I think it would be better to try an AIO Simplex installation first - as per https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/aio_simplex.html. · In any case, since you ran into earlier issues, I think it would make sense for you to re-start your installation from the beginning. If you hit issues in a fresh installation, send a new email to the mailing list. Please let us know the name of the load you are using as well. Bart From: Abhijit Deodhar [mailto:abhideodhar at gmail.com] Sent: April 8, 2020 12:57 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX install question Please help me On Mon, Apr 6, 2020 at 12:38 PM Abhijit Deodhar > wrote: Ok, I tried that step and it worked. But now I am hitting an issue at the next step: [image.png] How to get past this error or debug it? Thanks Abhijit On Mon, Apr 6, 2020 at 12:30 PM Yoshida, Shigeru > wrote: Hi Abhijit, Please try following commands on controller-0: source /etc/platform/openrc OAM_IF=enp2s1 system host-if-modify controller-1 $OAM_IF -c platform system interface-network-assign controller-1 $OAM_IF oam system interface-network-assign controller-1 mgmt0 cluster-host controller-1 is not configured at that point and system command normally be activated on active controller. Thanks, Shigeru From: Abhijit Deodhar > Sent: Monday, April 6, 2020 3:25 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX install question Forgot to mention that I tried doing this step to enter the admin mode, but the openrc script doesnt seem to exist on controller-1 So I am not sure how to proceed. Please advise. ~Abhijit On Mon, Apr 6, 2020 at 11:44 AM Abhijit Deodhar > wrote: Hi, I am trying to install StarlingX on virtual standard with controller storage configuration. I am following the steps mentioned in this document: https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html I reached the step where 2 controllers and 2 workers are up and running. Now I am confused with "configure controller-1" step. https://docs.starlingx.io/deploy_install_guides/r3_release/virtual/controller_storage_install_kubernetes.html#configure-controller-1 I see an error while doing this step on controller-1: I tried using sudo to repeat the step: Can someone please help me with this step to proceed with the installation? Regards Abhijit -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 53164 bytes Desc: image001.png URL: From Bill.Zvonar at windriver.com Wed Apr 8 15:04:09 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 8 Apr 2020 15:04:09 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 8, 2020) In-Reply-To: References: Message-ID: >From today's meeting... - Community Business - Standing Topics - Sanity - Monolithic: all green - Layered: all green but not fully layered yet - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008250.html - some additional steps to be done before we can cut over to this fully - validate that the container images work ok & optimize the build times - Gerrit Reviews in Need of Attention - none this week - CentOS 8 Kernel Upgrade Plan - test plan areas discussed in distro non-opentack meeting: https://etherpad.openstack.org/p/stx-distro-other - also working through questions/advice from JimS - target completion & merge is end of April - will continue to track progress weekly - Topics for this Week - election officials opportunity - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008260.html - PSA: stx-kernel repo - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008262.html - build team is ready to do this, requires a freeze to kernel updates - what's a good time? - impact to the team doing the kernel upgrade? - they'll have to move all the code to the new repo - the plan is start tomorrow & try to limit the duration of the lockdown - it'll be ~1-3 days - PSA: Project confirmation review slides - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008244.html - PSA: OSF Community Presentation & Recording - http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008246.html - Open Sanity: Dariush/Yang - next step is to reach out to the OpenDev folks on IRC - Open Requests for Help - StarlingX install question (Abhijit Deodhar): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008263.html - agreed that Abhijit should start from scratch & try again - collect logs/info & bring those back to the mailing list for further help - and that if there is found to be a real software or doc issue, this should be raised as a Launchpad - Bart will respond - Bruce mentioned that Minguan (sp?) produced an info graphic re: using proxies - Greg asked re: tools that Abraham/GDC had created previously - still maintained? - Saul will check if these are still working correctly - maybe we can point Abhijit at these - Load Balancer for k8s in StarlingX (Sten Gruener): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008266.html - not currently supported - would require a spec - metalLB would be a good candidate, but would require investigation - Brent will respond -----Original Message----- From: Zvonar, Bill Sent: Wednesday, April 8, 2020 7:35 AM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Apr 8, 2020) Hi all, reminder of the TSC/Community call coming up. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200408T1400 From oliver.lovaszi at intel.com Wed Apr 8 16:55:10 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Wed, 8 Apr 2020 16:55:10 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200408 Message-ID: Sanity Test from 2020-April-08 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200408T013012Z/outputs/iso/ ) 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 [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 62 TCs ] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 48 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 60 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Recoverable test case failures observed due to HTTP errors. AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 60 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 48 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 61 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steven.Webster at windriver.com Thu Apr 9 00:44:09 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Thu, 9 Apr 2020 00:44:09 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 4/8/2020 In-Reply-To: References: Message-ID: Hi All, Thanks for allowing me the opportunity to discuss the results of my Kata container + StarlingX functionality investigation this morning. I've uploaded the slide deck to: https://drive.google.com/drive/folders/19iPEuVGCCfKLy9t0_otPAUuizqWmnB8t Cheers, Steve ________________________________ From: Sun, Austin Sent: Wednesday, April 8, 2020 10:00 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 4/8/2020 MoM for 4/8 meeting: - Kata container Steven shared a good evelution. Thanks Steven kata will release new version @4/22 - ceph containerization https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/716792/ https://review.opendev.org/#/c/714857/ martin will share the migration steps once it is ready/ - centos8 upgrade (shuicheng/Austin) kernel-rt upgrade: - Jim ask for provide kernel-rt srpm , how to handle this ? https://review.opendev.org/#/c/711152/ further discuss via email. - Test team from intel cannot start eb as infrastructure is not ready this week. centos8 branch rebase. one nfv git is under review due to zuul failure will enable layer builder once zuul failure fixx - python3 upgrade status (An Ran) engtools --> reviewed logmgmt --> committed under testing nova-api-proxy---> committed under testing work-utils ---> not committed yet . 7 will generate and pre-test , but not target for stx.4.0 others will do exploration on centos8 feature branch - PBR -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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Apr 9 01:50:45 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 9 Apr 2020 01:50:45 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: Message-ID: Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Apr 9 02:03:16 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 9 Apr 2020 02:03:16 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: Message-ID: Thank-you Austin for confirming. Davlet Panech will start this work on Thursday and let us all know when we need to freeze stx-integ and also when the new stx-kernel repo is created and ready for all to use. Frank From: Sun, Austin Sent: Wednesday, April 08, 2020 9:51 PM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank > Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver.lovaszi at intel.com Thu Apr 9 13:20:50 2020 From: oliver.lovaszi at intel.com (Lovaszi, Oliver) Date: Thu, 9 Apr 2020 13:20:50 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200408 Message-ID: Sanity Test from 2020-April-09(http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200408T173705Z/outputs/iso/ ) 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 06 TCs [PASS] TOTAL: [ 61 TCs ] [PASS] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 51 TCs [PASS] Sanity Platform 06 TCs [PASS] TOTAL: [ 62 TCs ] [PASS] Standard - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 48 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 60 TCs ] [PASS] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 65 TCs ] [PASS] =========================================== 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: [ 60 TCs ] AIO - Duplex [PASS] Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs ] Standard - Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 48 TCs [PASS] Sanity Platform 08 TCs [PASS] TOTAL: [ 61 TCs ] Standard External - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 09 TCs [PASS] TOTAL: [ 61 TCs ] Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From Frank.Miller at windriver.com Thu Apr 9 13:22:54 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 9 Apr 2020 13:22:54 +0000 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Agenda Message-ID: Agenda for today's build meeting: 1. Moving kernel into stx-kernel a) Steps required and forecast for each b) When do we have to tell community that stx-integ is frozen for a couple of days? 2. Build layering update: a) Current method detects ~400 rpms that have changed resulting in slow flock build times: update on attemtps to reduce this b) Need for kmod version to change when kernel changes - this would have prevented the sanity issue with picking up the wrong kmod rpms c) Build avoidance options: review and evaluate d) Build times - where are we at? 3. PBR Zoom: https://zoom.us/j/342730236 Etherpad: https://etherpad.openstack.org/p/stx-build Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Thu Apr 9 15:16:21 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Thu, 9 Apr 2020 15:16:21 +0000 Subject: [Starlingx-discuss] stx-integ repo freeze Message-ID: Good morning, We are in the process of extracting the kernel from stx-integ. Please avoid committing to integ/master until we are done, I'll send a separate email at that point. See also: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008262.html Thank you, Davlet Panech -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Apr 9 17:48:14 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 9 Apr 2020 17:48:14 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Release meeting Message-ID: My apologies for the short notice, but I am unable to chair the meeting today. I need to cancel. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1919 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Thu Apr 9 17:50:15 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 9 Apr 2020 17:50:15 +0000 Subject: [Starlingx-discuss] No stx release meeting today at 2pm ET Message-ID: My apologies for the short notice, but I am unable to chair the starlingx release meeting today. I need to cancel. Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From corvus at inaugust.com Thu Apr 9 23:25:27 2020 From: corvus at inaugust.com (James E. Blair) Date: Thu, 09 Apr 2020 16:25:27 -0700 Subject: [Starlingx-discuss] Etherpad and Gerrit maintenance on 2020-04-10 Message-ID: <87pncgfdi0.fsf@meyer.lemoncheese.net> Hi, Tomorrow, April 10, 2020, the OpenDev team will be performing minor updates to two services. * Gerrit restart for https://review.opendev.org/ at 16:00 UTC. This should be a momentary outage to restart the service in a container. We will maintain the same version in the same configuration; this is a preparatory step in order to perform future version upgrades more easily. Other than a short outage of about a minute, there should be no service impact or visible changes, but since the environment is changing, we wanted to announce this in case any problems are detected. * Etherpad migration and domain change at 17:00 UTC. We will migrate the data currently hosted on etherpad.openstack.org to a new server, also running in a container, on etherpad.opendev.org. We will set up redirects so that on completion of the migration, all etherpad.openstack.org URLs will redirect to the same pages on etherpad.opendev.org. https://etherpad.opendev.org/ will become the new canonical service URL. This also includes an upgrade to the latest release of Etherpad Lite (1.8.0). This involves a database migration as well. The service will be unavailable for the duration of this migration (expected to be about 30 minutes). Please report any issues in #opendev on Freenode or to the service-discuss at lists.opendev.org mailing list. Note that this message is being sent to service-announce and several other lists. Future announcements of this type will only be sent to service-announce, so please sign up[1] for that list if you haven't already. [1] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce -Jim From mihail-laurentiu.trica at intel.com Fri Apr 10 22:39:41 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Fri, 10 Apr 2020 22:39:41 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200410 Message-ID: Sanity Test from 2020-April-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200410T013013Z/outputs/iso/) 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 External - 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 - 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 External - 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, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Sat Apr 11 15:26:32 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Sat, 11 Apr 2020 15:26:32 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-08 Message-ID: Hello all, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-08 * All -- reviews merged since last week: 1. AR Mary ask Ritu about updates to the other install guides. * All -- bug status -- 2 new bugs * [Fixed] Keynote & ppt template links broken on starlingx.io. https://bugs.launchpad.net/starlingx/+bug/1870596 * Backup & restore procedure info https://bugs.launchpad.net/starlingx/+bug/1871065 * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Windows Active Dir content -- Review available: https://review.opendev.org/#/c/712111/ ? Mary updated review. More changes from Greg. Open ? to Teresa Ho for script location. * Upgrade Kubernetes version -- Review available: https://review.opendev.org/#/c/712583/ ? AR Mary to update review: leave it as-is in the docs for now. We can take it out if it seems to churn a lot. * no update: Assignment of R4 doc tasks * All -- Opens * AR Mary -- Publicize how we want to receive docs input via Discuss list. ? #1 (preferred) Submit a review. We can point to the contributor guide and note that we will help with edits/formatting. #2. Otherwise, provide raw input via launchpad. * Bruce has a formal development process document https://docs.starlingx.io/contributor/development_process.html * Bart suggested that we add folks from the test group to doc reviews. Bruce will bring it to the test group meeting this week. * WIP: Docker proxy setup ongoing questions w/Saul: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008189.html and email from Greg. Priority 1 task ? Review https://review.opendev.org/#/c/718298/ * no update: Brucej -- let's discuss Ildiko's email (STX feedback): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008088.html * no update: All -- Wiki status * Reviews in progress: ? STX IPv6 deployment https://review.opendev.org/#/c/718302/ ? Modifying layered build commands (add pike / remove pike) This review is valid for the current situation. https://review.opendev.org/#/c/717424/ * We think in the next month will be done. AR Mary put -1 and comment that we will revisit in 4 weeks. ? updated: Certificate config and management https://review.opendev.org/#/c/714821/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Apr 13 12:07:22 2020 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 13 Apr 2020 12:07:22 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting In-Reply-To: References: Message-ID: Hi Frank & bob I write some slides for rook migration for tomorrow's containerization meeting. https://drive.google.com/file/d/1pojKWqFXxJACHkDxPLm8ZJN992dz8-6S/view?usp=sharing patch for review https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/714857/ https://review.opendev.org/#/c/716792/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 10:10 PM To: 'Miller, Frank' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: StarlingX Containerization Meeting Hi Frank I share on google drive, with anyone could access with this link https://drive.google.com/file/d/1GFO6-72lmVt5av_pX1EfXocibSEcPDJJ/view?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 8:12 PM To: Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: StarlingX Containerization Meeting Hi Frank I prepare some slide for today's ceph containerization topic https://docs.google.com/presentation/d/16xI-woOIvMtM6aL7Nlmo1ICtZPDzSl2OvD3p6lrPsVY/edit?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, March 31, 2020 8:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 22, Issue 124 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX Containerization Meeting (Miller, Frank) 2. Fwd: [all] Virtualized PTG Brainstorming Community Meetings (Kendall Nelson) 3. Re: Docker Proxy Setup (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Mar 2020 22:24:12 +0000 From: "Miller, Frank" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Content-Type: text/plain; charset="iso-8859-1" The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: 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: 2832 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Mon, 30 Mar 2020 15:42:59 -0700 From: Kendall Nelson To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings Message-ID: Content-Type: text/plain; charset="utf-8" Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 31 Mar 2020 00:38:07 +0000 From: "Lin, Shuicheng" To: Saul Wold , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Docker Proxy Setup Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 22, Issue 124 ************************************************** From mihail-laurentiu.trica at intel.com Mon Apr 13 16:05:57 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Mon, 13 Apr 2020 16:05:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200413 Message-ID: Sanity Test from 2020-April-13 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200412T230013Z/outputs/iso/) 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 ] 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 External - 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 - 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 External - 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 ] There was an error at provisioning the Duplex setup on Bare Metal, there were no sanity tests run on Duplex at all. There are no issues on Duplex in the virtual environment. We are investigating the issue with Duplex on Bare Metal. Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Apr 13 21:30:02 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 13 Apr 2020 21:30:02 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting In-Reply-To: References: Message-ID: Martin: Unfortunately I cannot host the containerization meeting on Tuesday this week due to a conflict. Can we review your slides during the first 30 minutes of the Wednesday distro-nonopenstack meeting? Frank -----Original Message----- From: Chen, Haochuan Z Sent: Monday, April 13, 2020 8:07 AM To: Miller, Frank ; Church, Robert Cc: starlingx-discuss at lists.starlingx.io; Qi, Mingyuan ; Sun, Austin ; Hu, Yong Subject: RE: StarlingX Containerization Meeting Hi Frank & bob I write some slides for rook migration for tomorrow's containerization meeting. https://drive.google.com/file/d/1pojKWqFXxJACHkDxPLm8ZJN992dz8-6S/view?usp=sharing patch for review https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/714857/ https://review.opendev.org/#/c/716792/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 10:10 PM To: 'Miller, Frank' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: StarlingX Containerization Meeting Hi Frank I share on google drive, with anyone could access with this link https://drive.google.com/file/d/1GFO6-72lmVt5av_pX1EfXocibSEcPDJJ/view?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 8:12 PM To: Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: StarlingX Containerization Meeting Hi Frank I prepare some slide for today's ceph containerization topic https://docs.google.com/presentation/d/16xI-woOIvMtM6aL7Nlmo1ICtZPDzSl2OvD3p6lrPsVY/edit?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, March 31, 2020 8:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 22, Issue 124 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX Containerization Meeting (Miller, Frank) 2. Fwd: [all] Virtualized PTG Brainstorming Community Meetings (Kendall Nelson) 3. Re: Docker Proxy Setup (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Mar 2020 22:24:12 +0000 From: "Miller, Frank" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Content-Type: text/plain; charset="iso-8859-1" The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: 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: 2832 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Mon, 30 Mar 2020 15:42:59 -0700 From: Kendall Nelson To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings Message-ID: Content-Type: text/plain; charset="utf-8" Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 31 Mar 2020 00:38:07 +0000 From: "Lin, Shuicheng" To: Saul Wold , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Docker Proxy Setup Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 22, Issue 124 ************************************************** From Frank.Miller at windriver.com Mon Apr 13 21:35:24 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 13 Apr 2020 21:35:24 +0000 Subject: [Starlingx-discuss] StarlingX containerization meeting cancelled for Apr 14 Message-ID: StarlingX Community: Please note that I need to cancel the bi-weekly meeting planned for Tuesday April 14. Please email if you have any topics related to containers that need to be discussed. I suggest that the rook topic be covered during the Wednesday non-OpenStack distro meeting. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Apr 14 01:28:52 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 14 Apr 2020 01:28:52 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting In-Reply-To: References: Message-ID: Thanks Frank. Let me add this to Weds non-openstack meeting agenda . please help to invite stakeholders join. Thanks. BR Austin Sun. -----Original Message----- From: Miller, Frank Sent: Tuesday, April 14, 2020 5:30 AM To: Chen, Haochuan Z ; Church, Robert Cc: starlingx-discuss at lists.starlingx.io; Qi, Mingyuan ; Sun, Austin ; Hu, Yong Subject: RE: StarlingX Containerization Meeting Martin: Unfortunately I cannot host the containerization meeting on Tuesday this week due to a conflict. Can we review your slides during the first 30 minutes of the Wednesday distro-nonopenstack meeting? Frank -----Original Message----- From: Chen, Haochuan Z Sent: Monday, April 13, 2020 8:07 AM To: Miller, Frank ; Church, Robert Cc: starlingx-discuss at lists.starlingx.io; Qi, Mingyuan ; Sun, Austin ; Hu, Yong Subject: RE: StarlingX Containerization Meeting Hi Frank & bob I write some slides for rook migration for tomorrow's containerization meeting. https://drive.google.com/file/d/1pojKWqFXxJACHkDxPLm8ZJN992dz8-6S/view?usp=sharing patch for review https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/714857/ https://review.opendev.org/#/c/716792/ BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 10:10 PM To: 'Miller, Frank' Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: StarlingX Containerization Meeting Hi Frank I share on google drive, with anyone could access with this link https://drive.google.com/file/d/1GFO6-72lmVt5av_pX1EfXocibSEcPDJJ/view?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: Chen, Haochuan Z Sent: Tuesday, March 31, 2020 8:12 PM To: Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: StarlingX Containerization Meeting Hi Frank I prepare some slide for today's ceph containerization topic https://docs.google.com/presentation/d/16xI-woOIvMtM6aL7Nlmo1ICtZPDzSl2OvD3p6lrPsVY/edit?usp=sharing BR! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, March 31, 2020 8:38 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 22, Issue 124 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. StarlingX Containerization Meeting (Miller, Frank) 2. Fwd: [all] Virtualized PTG Brainstorming Community Meetings (Kendall Nelson) 3. Re: Docker Proxy Setup (Lin, Shuicheng) ---------------------------------------------------------------------- Message: 1 Date: Mon, 30 Mar 2020 22:24:12 +0000 From: "Miller, Frank" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Content-Type: text/plain; charset="iso-8859-1" The next containerization meeting is scheduled for Tuesday Mar 31st. Agenda: 1. STX4.0 features: Kata containers [2006145] - update on remaining work items -- Shuicheng Lin - switch armada to run with containerd - upgrade kata packages newer than 1.11.0-alpha0 to include ipv6 fixes - Documentation for config and usage of Kata containers in STX Decouple container applications from platform [2006537] -- Angie Wang - what work items remain? - Updated forecast for feature complete? Upversion container components [2006999] -- Bob Church - upversion of calico to 3.12 & multus to 3.4 - upversion of kubernetes to 1.18 Add support for Helm v3 [2007000] - Jim Gauld - current status Ceph containerization [2005527] -- Martin Chen - review Martin's proposal email from March 16 Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: 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: 2832 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Mon, 30 Mar 2020 15:42:59 -0700 From: Kendall Nelson To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings Message-ID: Content-Type: text/plain; charset="utf-8" Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Tue, 31 Mar 2020 00:38:07 +0000 From: "Lin, Shuicheng" To: Saul Wold , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Docker Proxy Setup Message-ID: <9700A18779F35F49AF027300A49E7C766397BCA9 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi Saul, It seems the cmd has been updated. You could use "system service-parameter-list" to get the list first. Then you could modify it like below cmd: system service-parameter-modify docker proxy http_proxy=HTTP_PROXY In my test, the modification will not be applied until you lock&unlock controller. You could find there is "Configuration is out-of-date" message with "fm alarm-list". Best Regards Shuicheng -----Original Message----- From: Saul Wold Sent: Tuesday, March 31, 2020 12:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docker Proxy Setup Hi There, I am reviewing the Docker Proxy Configuration page [0]. I tried to run the service-parameter-modify and get the following error message: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy Service Parameter not found: service platform, section docker, name http://my.proxy.com:1080 I also tried using name=value: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-modify platform docker http_proxy=http://my.proxy.com:1080 Service Parameter not found: service platform, section docker, name http_proxy I looked at service-parameter-list and there is no docker section as part of the platform service, so I tried to use service-parameter-add and got the following error: [sysadmin at controller-0 ~(keystone_admin)]$ system service-parameter-add platform docker http_proxy=http://my.proxy.com:1080 Invalid service section docker. It seems that the Docker Proxy Config docs page it out of date and/or not working correctly, can someone let me know what I am doing wrong? [0] https://docs.starlingx.io/configuration/docker_proxy_config.html Thanks Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 22, Issue 124 ************************************************** From yipeng.he at jitstack.com Tue Apr 14 02:43:51 2020 From: yipeng.he at jitstack.com (=?utf-8?B?5L2V5LmJ6bmP?=) Date: Tue, 14 Apr 2020 10:43:51 +0800 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: Hi Saul, I'm sorry it took so long to recover your mail. Recently, there was a problem when I modified according to the method you provided under patch. I tried to change all the versions in the patch of starlingx-starboard to pbr_version. But the result still failed to build iso. yipeng.he!   ------------------ Original ------------------ From:  "Saul Wold" From sgw at linux.intel.com Tue Apr 14 05:13:43 2020 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 13 Apr 2020 22:13:43 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> Message-ID: <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> Can you please provide more details about what you did and how you tried to create the ISO? The information here is not very helpful. Maybe the community members in China can help you get the build to work correctly. Sau! On 4/13/20 7:43 PM, 何义鹏 wrote: > > Hi Saul, > > I'm sorry it took so long to recover your mail. > > Recently, there was a problem when I modified according to the method > you provided under patch. > I tried to change all the versions in the patch of starlingx-starboard > to pbr_version. > But the result still failed to build iso. > > yipeng.he! > ------------------ Original ------------------ > *From: * "Saul Wold"; > *Date: * Wed, Apr 8, 2020 02:58 AM > *To: * "starlingx-discuss"; "何义 > 鹏"; > *Subject: * Re: [Starlingx-discuss] enable pbr version > > Hi Yipeng, > > Sorry for the delay in getting back to you, I was looking into the build > failure and trying understand how we handle the difference between the > PBR SemVer [0] and PEP440 [1]. Specifically when there is a "Pre" tag > like rc0, b1 such as 4.0.0.rc0. When PEP440 normalizes that semver tag > to create the egg-info versio it comes out as 4.0.0rc0.egg-info. > > So we need to also change the spec files %files section for the egg-info > file to wild-card that file instead of having a specific version listed. > > For example in the starlingx-dashboard spec file: > > diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec > b/starlingx-dashboard/centos/starlingx-dashboard.spec > index 7fbee65..399a9bd 100644 > --- a/starlingx-dashboard/centos/starlingx-dashboard.spec > +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec > @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >   %files >   %{python2_sitelib}/%{py_pkg_name} > > -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info > +%{python2_sitelib}/%{py_pkg_name}-*.egg-info > >   %{enabled_dir} >   %{stx_themes_dir} > > And as discussed in Jeremy's email we should be adding the "Sem-Ver: > feature" in the commit message, just once per repo. See Bin's pending > commit in fault [2]. You will have to back and fix fault and other > pending commits with the wild-card change for the egg-info file in the > spec file. > > Finally all PBR related reviews should have a > Depends-On: https://review.opendev.org/#/c/691632/ > > So it does not get merged before the enabling code in the build tools > merges. > > Hope this clarifies things and gets the PBR work unblocked. I am going > through the reviews and trying to provide some additional review comments. > We can also talk about this tomorrow during the Distro call [3] > > Sau! > > > [0] https://docs.openstack.org/pbr/3.0.0/semver.html > [1] https://www.python.org/dev/peps/pep-0440/ > [2] https://review.opendev.org/#/c/691647/ > [3] > On 3/30/20 6:52 PM, 何义鹏 wrote: > > > >   Saul! > > > > Thank you for your answer! But how should I use the semMem-ver tag? > > ------------------ Original ------------------ > > *From: * "Saul Wold"; > > *Date: * Sat, Mar 28, 2020 07:02 AM > > *To: * "何义鹏"; "Penney, > > Don"; "Scott > > Little"; "Miller, > > Frank"; > > *Cc: * "曹明晓"; "杨永金" > > ; "桂来军"; > > "starlingx-discuss"; > > *Subject: * Re: [Starlingx-discuss] enable pbr version > > Yipeng, > > > > > > I replied the other day, wanting to confirm if you have any additional > > changes in your local git repo? It seems that we need to consider a > > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: > > feature" tag in a commit to move the pbr versioning forward. > > > > BUILD Team (Don, Scott, Frank): > > > > Here's the general issue, we tag on the release branches, not master > > (although we have a v3.0.0.rc0 tag on master), we need to either add a > > Sem_Ver: feature tag to increment version's major number, or add a > > pre-tag of the 4.0 release. > > > > Thoughts from the build team?  I think we discussed part of the before, > > but want to do a quick revisit of the thread back in Nov [1], I think we > > had agreed to use Sem_Ver but it's not in the email thread > > > > > > [0] > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html > > > > > > On 3/26/20 7:26 PM, 何义鹏 wrote: > >  > > >  > Yes, building the rpm of the starlingx dashboard is a necessary > step for > >  > my build-iso. > >  > > >  > Maybe Saul can respond to the question that python builds allow > several > >  > versions of components. > >  > > > Jeremy replied to this earlier in the week, the issue appears to be the > > way we tagged rc0, we might need to have change our tagging.  He also > > stated that the number of components is not a limiting factor. > > > > Sau! > >  > ------------------ Original ------------------ > >  > *From: * "Penney, Don"; > >  > *Date: * Wed, Mar 25, 2020 10:11 PM > >  > *To: * "何义鹏"; "Saul > >  > Wold(sgw at linux.intel.com)"; > >  > *Cc: > >  > > > > * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; > > > > >  > > >  > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version > >  > > >  > Please keep starlingx-discuss on the receiver list. > >  > > >  > You had indicated build-iso was failing, but the build.log you > provided > >  > appears to be the RPM build log for starlingx-dashboard. > >  > > >  > Processing files: > starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch > >  > > >  > error: File not found: > >  > > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > >  > > >  > RPM build errors: > >  > > >  >      File not found: > >  > > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info > >  > > >  > Child return code was: 1 > >  > > >  > EXCEPTION: [Error()] > >  > > >  > Traceback (most recent call last): > >  > > >  >    File > "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", > >  > line 95, in trace > >  > > >  >      result = func(*args, **kw) > >  > > >  >    File "/usr/lib/python3.6/site-packages/mockbuild/util.py", line > 746, > >  > in do_with_status > >  > > >  >      raise exception.Error("Command failed: \n # %s\n%s" % (command, > >  > output), child.returncode) > >  > > >  > mockbuild.exception.Error: Command failed: > >  > > >  >   # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps > >  > /builddir/build/SPECS/starlingx-dashboard.spec > >  > > >  > Looking through the build.log, I see the following: > >  > > >  > Copying starlingx_dashboard.egg-info to > >  > > > > build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info > >  > > >  > So in the build, it’s creating the egg with the version set to > >  > 2.9999.9999rc1.dev23, while the %files is expecting it to be > >  > 2.9999.9999.rc1.dev23. > >  > > >  > Looking further through the build.log, there’s the following: > >  > > >  > + /usr/bin/python2 setup.py install -O1 --skip-build --root > >  > > > > /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 > >  > > >  > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: UserWarning: > >  > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' > >  > > >  >    normalized_version, > >  > > >  > running install > >  > > >  > Maybe the python build only allows 4 version components? > >  > > >  > *From:*何义鹏[mailto:yipeng.he at jitstack.com] > >  > *Sent:* Tuesday, March 24, 2020 9:59 PM > >  > *To:* Penney, Don > >  > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version > >  > > >  > Hi Saul, > >  > > >  > I added the error log to the attachment. Do you need other files for > >  > analysis? > >  > > >  > Thank you for your help. > >  > > >  >     yipeng.he! > >  > > >  > ------------------ Original ------------------ > >  > > >  > *From: * "Penney, Don"; > >  > > >  > *Date: * Wed, Mar 25, 2020 04:24 AM > >  > > >  > *To: * "Saul Wold"; "何义鹏" > > ; > >  > > >  > *Cc: * "桂来军"; "杨永金" > >  > ; "曹明晓"; > >  > "starlingx-discuss"; > >  > > >  > *Subject: * RE: [Starlingx-discuss] enable pbr version > >  > > >  > Hi Yipeng, > >  > > >  > Can you provide more info? What was the error you saw from build-iso? > >  > > >  > > >  > -----Original Message----- > >  > From: Saul Wold [mailto:sgw at linux.intel.com] > >  > Sent: Monday, March 23, 2020 6:45 PM > >  > To: 何义鹏 > >  > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss > >  > Subject: Re: [Starlingx-discuss] enable pbr version > >  > > >  > > >  > Hi Yipeng, > >  > > >  > I was out last week on vacation, so I am catching up now. > >  > > >  > I think you would have to investigate build-iso and associated scripts > >  > and tools to see if there is an awk, sed or some other command that is > >  > not parsing the extended version.  I have not investigated this > further, > >  > that's my initial assessment. > >  > > >  > Can you be more specific about what the error is or provide a log file > >  > of the build-iso process? > >  > > >  > Thanks for working on this project. > >  > > >  >    Sau! > >  > > >  > > >  > > >  > On 3/19/20 12:21 AM, 何义鹏wrote: > >  >> Hello Saul > >  >> > >  >> I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. > >  >> I encountered the following issue when trying to build iso: > >  >> It fails when the suffix of the version generated by the PBR tool > ended > >  >> with number, for instance the building fails if the version id is > >  >> 2.999.9999.rc1.dev23, > >  >> and when I replaced it with 2.999.9999.rc1.dev, the ISO building was > >  >> successful. > >  >> I don't knwo why this happens, could please support and advice the > >  >> solution for this issue. > >  >> > >  >> > >  >> Yipeng.He > >  >> > >  >> _______________________________________________ > >  >> 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 > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From austin.sun at intel.com Tue Apr 14 12:12:13 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 14 Apr 2020 12:12:13 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 4/15/2020 Message-ID: Hi All: Agenda for 4/15 meeting: - ceph containerization martin will share the steps migration from native ceph to rook(containerization ceph) https://drive.google.com/file/d/1pojKWqFXxJACHkDxPLm8ZJN992dz8-6S/view?usp=sharing lvm/gpt table discuss - kernel upgrade : - centos8 upgrade: - python3 upgrade - PBR - open Please feel free to add topic in https://etherpad.opendev.org/p/stx-distro-other Thanks. Austin Sun. From maryx.camp at intel.com Tue Apr 14 14:39:14 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Tue, 14 Apr 2020 14:39:14 +0000 Subject: [Starlingx-discuss] PSA: Contributing to Docs Message-ID: This is a Public Service Announcement. As we head towards Release 4, we want the new STX features to be fully described so that the users will have the best possible experience. To contribute to the StarlingX documentation, whether it's new R4 content or if you find a doc bug, you have these options: * DIY: Create the new doc text as a RST file or update an existing RST file. Check the HTML output and submit a review, as described in the Contributor's Guide [1]. * Open a Launchpad bug [2], tag it as stx.docs, and include the new doc text in raw form. For both options, the docs team is ready to help you with format, grammar, links to other STX docs, building the docs locally, etc. Please let me know if you have any questions, and feel free to join our weekly call on Wednesdays at 12:30 Pacific (15:30 Eastern). Thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com [1] https://docs.starlingx.io/contributor/doc_contribute_guide.html [2] https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Tue Apr 14 15:49:12 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Tue, 14 Apr 2020 15:49:12 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200414 Message-ID: Sanity Test from 2020-April-14 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200414T084726Z/outputs/iso/) 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 External - 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 External - 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 ] There was a temporary error at provisioning on the Standard setup on Virtual environment, we are investigating the issue. Regards, STX Validation Team Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Apr 14 16:42:30 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 14 Apr 2020 09:42:30 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> Message-ID: <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> Yipeng, I hope you can join the Distro meeting in your evening tomorrow and we can disuses this issue. Thanks Sau! On 4/13/20 10:13 PM, Saul Wold wrote: > Can you please provide more details about what you did and how you tried > to create the ISO? > > The information here is not very helpful.  Maybe the community members > in China can help you get the build to work correctly. > > Sau! > > > On 4/13/20 7:43 PM, 何义鹏 wrote: >> >> Hi Saul, >> >> I'm sorry it took so long to recover your mail. >> >> Recently, there was a problem when I modified according to the method >> you provided under patch. >> I tried to change all the versions in the patch of starlingx-starboard >> to pbr_version. >> But the result still failed to build iso. >> >> yipeng.he! >> ------------------ Original ------------------ >> *From: * "Saul Wold"; >> *Date: * Wed, Apr 8, 2020 02:58 AM >> *To: * "starlingx-discuss"; "何 >> 义 鹏"; >> *Subject: * Re: [Starlingx-discuss] enable pbr version >> >> Hi Yipeng, >> >> Sorry for the delay in getting back to you, I was looking into the build >> failure and trying understand how we handle the difference between the >> PBR SemVer [0] and PEP440 [1]. Specifically when there is a "Pre" tag >> like rc0, b1 such as 4.0.0.rc0. When PEP440 normalizes that semver tag >> to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >> >> So we need to also change the spec files %files section for the egg-info >> file to wild-card that file instead of having a specific version listed. >> >> For example in the starlingx-dashboard spec file: >> >> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >> b/starlingx-dashboard/centos/starlingx-dashboard.spec >> index 7fbee65..399a9bd 100644 >> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>    %files >>    %{python2_sitelib}/%{py_pkg_name} >> >> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >> >>    %{enabled_dir} >>    %{stx_themes_dir} >> >> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >> feature" in the commit message, just once per repo. See Bin's pending >> commit in fault [2]. You will have to back and fix fault and other >> pending commits with the wild-card change for the egg-info file in the >> spec file. >> >> Finally all PBR related reviews should have a >> Depends-On: https://review.opendev.org/#/c/691632/ >> >> So it does not get merged before the enabling code in the build tools >> merges. >> >> Hope this clarifies things and gets the PBR work unblocked. I am going >> through the reviews and trying to provide some additional review >> comments. >> We can also talk about this tomorrow during the Distro call [3] >> >> Sau! >> >> >> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >> [1] https://www.python.org/dev/peps/pep-0440/ >> [2] https://review.opendev.org/#/c/691647/ >> [3] >> On 3/30/20 6:52 PM, 何义鹏 wrote: >>  > >>  >   Saul! >>  > >>  > Thank you for your answer! But how should I use the semMem-ver tag? >>  > ------------------ Original ------------------ >>  > *From: * "Saul Wold"; >>  > *Date: * Sat, Mar 28, 2020 07:02 AM >>  > *To: * "何义鹏"; "Penney, >>  > Don"; "Scott >>  > Little"; "Miller, >>  > Frank"; >>  > *Cc: * "曹明晓"; "杨永金" >>  > ; "桂来军"; >>  > "starlingx-discuss"; >>  > *Subject: * Re: [Starlingx-discuss] enable pbr version >>  > Yipeng, >>  > >>  > >>  > I replied the other day, wanting to confirm if you have any additional >>  > changes in your local git repo? It seems that we need to consider a >>  > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>  > feature" tag in a commit to move the pbr versioning forward. >>  > >>  > BUILD Team (Don, Scott, Frank): >>  > >>  > Here's the general issue, we tag on the release branches, not master >>  > (although we have a v3.0.0.rc0 tag on master), we need to either add a >>  > Sem_Ver: feature tag to increment version's major number, or add a >>  > pre-tag of the 4.0 release. >>  > >>  > Thoughts from the build team?  I think we discussed part of the >> before, >>  > but want to do a quick revisit of the thread back in Nov [1], I >> think we >>  > had agreed to use Sem_Ver but it's not in the email thread >>  > >>  > >>  > [0] >>  > >> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html >> >>  > >>  > >>  > On 3/26/20 7:26 PM, 何义鹏 wrote: >>  >  > >>  >  > Yes, building the rpm of the starlingx dashboard is a necessary >> step for >>  >  > my build-iso. >>  >  > >>  >  > Maybe Saul can respond to the question that python builds allow >> several >>  >  > versions of components. >>  >  > >>  > Jeremy replied to this earlier in the week, the issue appears to be >> the >>  > way we tagged rc0, we might need to have change our tagging.  He also >>  > stated that the number of components is not a limiting factor. >>  > >>  > Sau! >>  >  > ------------------ Original ------------------ >>  >  > *From: * "Penney, Don"; >>  >  > *Date: * Wed, Mar 25, 2020 10:11 PM >>  >  > *To: * "何义鹏"; "Saul >>  >  > Wold(sgw at linux.intel.com)"; >>  >  > *Cc: >>  >  > >>  > >> * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; >> >>  > >>  >  > >>  >  > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>  >  > >>  >  > Please keep starlingx-discuss on the receiver list. >>  >  > >>  >  > You had indicated build-iso was failing, but the build.log you >> provided >>  >  > appears to be the RPM build log for starlingx-dashboard. >>  >  > >>  >  > Processing files: >> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>  >  > >>  >  > error: File not found: >>  >  > >>  > >> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info >> >>  >  > >>  >  > RPM build errors: >>  >  > >>  >  >      File not found: >>  >  > >>  > >> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info >> >>  >  > >>  >  > Child return code was: 1 >>  >  > >>  >  > EXCEPTION: [Error()] >>  >  > >>  >  > Traceback (most recent call last): >>  >  > >>  >  >    File >> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>  >  > line 95, in trace >>  >  > >>  >  >      result = func(*args, **kw) >>  >  > >>  >  >    File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >> line 746, >>  >  > in do_with_status >>  >  > >>  >  >      raise exception.Error("Command failed: \n # %s\n%s" % >> (command, >>  >  > output), child.returncode) >>  >  > >>  >  > mockbuild.exception.Error: Command failed: >>  >  > >>  >  >   # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps >>  >  > /builddir/build/SPECS/starlingx-dashboard.spec >>  >  > >>  >  > Looking through the build.log, I see the following: >>  >  > >>  >  > Copying starlingx_dashboard.egg-info to >>  >  > >>  > >> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info >> >>  >  > >>  >  > So in the build, it’s creating the egg with the version set to >>  >  > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>  >  > 2.9999.9999.rc1.dev23. >>  >  > >>  >  > Looking further through the build.log, there’s the following: >>  >  > >>  >  > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>  >  > >>  > >> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 >> >>  >  > >>  >  > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >> UserWarning: >>  >  > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>  >  > >>  >  >    normalized_version, >>  >  > >>  >  > running install >>  >  > >>  >  > Maybe the python build only allows 4 version components? >>  >  > >>  >  > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>  >  > *Sent:* Tuesday, March 24, 2020 9:59 PM >>  >  > *To:* Penney, Don >>  >  > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>  >  > >>  >  > Hi Saul, >>  >  > >>  >  > I added the error log to the attachment. Do you need other files >> for >>  >  > analysis? >>  >  > >>  >  > Thank you for your help. >>  >  > >>  >  >     yipeng.he! >>  >  > >>  >  > ------------------ Original ------------------ >>  >  > >>  >  > *From: * "Penney, Don"; >>  >  > >>  >  > *Date: * Wed, Mar 25, 2020 04:24 AM >>  >  > >>  >  > *To: * "Saul Wold"; "何义鹏" >>  > ; >>  >  > >>  >  > *Cc: * "桂来军"; "杨永金" >>  >  > ; "曹明晓"; >>  >  > "starlingx-discuss"; >>  >  > >>  >  > *Subject: * RE: [Starlingx-discuss] enable pbr version >>  >  > >>  >  > Hi Yipeng, >>  >  > >>  >  > Can you provide more info? What was the error you saw from >> build-iso? >>  >  > >>  >  > >>  >  > -----Original Message----- >>  >  > From: Saul Wold [mailto:sgw at linux.intel.com] >>  >  > Sent: Monday, March 23, 2020 6:45 PM >>  >  > To: 何义鹏 >>  >  > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>  >  > Subject: Re: [Starlingx-discuss] enable pbr version >>  >  > >>  >  > >>  >  > Hi Yipeng, >>  >  > >>  >  > I was out last week on vacation, so I am catching up now. >>  >  > >>  >  > I think you would have to investigate build-iso and associated >> scripts >>  >  > and tools to see if there is an awk, sed or some other command >> that is >>  >  > not parsing the extended version.  I have not investigated this >> further, >>  >  > that's my initial assessment. >>  >  > >>  >  > Can you be more specific about what the error is or provide a >> log file >>  >  > of the build-iso process? >>  >  > >>  >  > Thanks for working on this project. >>  >  > >>  >  >    Sau! >>  >  > >>  >  > >>  >  > >>  >  > On 3/19/20 12:21 AM, 何义鹏wrote: >>  >  >> Hello Saul >>  >  >> >>  >  >> I'm Yipeng He from JITStack, and I'm taking over the tasks of PBR. >>  >  >> I encountered the following issue when trying to build iso: >>  >  >> It fails when the suffix of the version generated by the PBR >> tool ended >>  >  >> with number, for instance the building fails if the version id is >>  >  >> 2.999.9999.rc1.dev23, >>  >  >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >> building was >>  >  >> successful. >>  >  >> I don't knwo why this happens, could please support and advice the >>  >  >> solution for this issue. >>  >  >> >>  >  >> >>  >  >> Yipeng.He >>  >  >> >>  >  >> _______________________________________________ >>  >  >> 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 >>  > >> >> _______________________________________________ >> 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 kennelson11 at gmail.com Tue Apr 14 17:00:32 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 14 Apr 2020 10:00:32 -0700 Subject: [Starlingx-discuss] Virtual PTG Layout & Signup Message-ID: Greetings! I am sure you have all been anxiously awaiting more details on how we are going to virtualize the PTG :) After the community meetings we had last week/the week before to understand the key challenges and ideate on solutions, we have a plan! The virtual event will be held from Monday June 1 to Friday June 5. We set up available times in 3 different time windows where each window is a cross over time between at least 2 regions (Window A - Americas/Europe, Window B - Europe/APAC, and Window C - APAC/Americas). Here is an ethercalc[1]. We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. 1. Cross project discussions (i.e. SIGs and horizonal teams), try to schedule yourselves towards the start of the week so that any discussions that might shape those of vertical teams might happen first. 2. Vertical teams (ex. Nova, Cyborg, Manila) should wait till April 6th at 7:00 UTC to start signing up for slots to help prioritize the scheduling of cross project conversations. 3. No team (SIG, horizonal project, vertical project, etc) can sign up for more than 4 hours per UTC day to help keep participants actively engaged. 4. No team (SIG, horizonal project, vertical project, etc) can sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Once every team has had a chance to sign up (lets say two weeks from today April 28th at 7:00 UTC) if signing up for more time makes sense, it will be possible. We want to encourage ANY team to sign up, even those that had originally said no to the initial outreach when the PTG was supposed to be in person. The more the merrier! Once you have signed up for time slots, please also fill out this survey[2] with your team information. We need this additional information to help shape other decisions down the road and coordinate other details closer to the event. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Continue to check back for updates at openstack.org/ptg. -the Kendalls (diablo_rojo & wendallkaters) [1] https://ethercalc.openstack.org/126u8ek25noy [2] https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Apr 8 15:03:04 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 8 Apr 2020 15:03:04 +0000 Subject: [Starlingx-discuss] Mingyuan's proxy infograpic Message-ID: <9A85D2917C58154C960D95352B22818BFB07E858@fmsmsx123.amr.corp.intel.com> Here is the infographic on proxy setup that Mingyuan put together. Kudos to him for this! The docs team will take the AR to add this to our docs. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Starlingx_proxy.png Type: image/png Size: 116023 bytes Desc: Starlingx_proxy.png URL: From yang.liu at windriver.com Tue Apr 14 15:45:08 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 14 Apr 2020 15:45:08 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 04/14/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 04/14/2020 Attendees: Yang, Bernd, Bruce, Mihail, Nicolae, Alex, Oliver, Ruediger, Cosmin, Sharath, Chris · Sanity Status: * https://bugs.launchpad.net/neutron/+bug/1870569 - Unable to create network without default network_segment_range * Command failed: openstack network create --project --provider-network-type=vlan --provider-physical-network= --share * Provisioning is not completed on baremetal duplex system - further investigation needed · stx4.0 testing * Feature testing (https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0) § Centos8: Started testing. No server with TPM yet, but tested whatever can be done without the actual hardware. No servers with CX4/5 card yet - in progress to set up. § Upversion Openstack services used by flock components on host: · Got ENG load - executed several tests. Still in progress. · Automation update may be needed due to OpenStack client upversion § Windows Active directory in progress § Red fish virtual media support in progress * Regression testing: § Starting in May. Suggest to start pulling in test cases. · Open topics * Unified Sanity: § Currently, sanity is using robot test cases in Intel's internal repo. Plan is to switch to community repo > then switch to pytest test cases. § Bruce still looking for volunteer to help set up the virtual environment to run test in the open * Static Code analytics tool - bandit § Sharath will provide the bug numbers to Bruce to discuss in another forum. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Tue Apr 14 17:45:05 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 14 Apr 2020 17:45:05 +0000 Subject: [Starlingx-discuss] stx-integ repo freeze In-Reply-To: References: Message-ID: This is done now - repos and manifests have been updated. The new repo is starlingx/kernel, extracted out of starlingx/integ. If you are doing your own builds, please re-sync your starlingx/master manifest. We are running a monolithic build right now to make sure there are no issues. Thanks, D. ________________________________ From: Panech, Davlet Sent: April 9, 2020 11:16 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stx-integ repo freeze Good morning, We are in the process of extracting the kernel from stx-integ. Please avoid committing to integ/master until we are done, I'll send a separate email at that point. See also: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008262.html Thank you, Davlet Panech -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Tue Apr 14 18:37:01 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Tue, 14 Apr 2020 18:37:01 +0000 Subject: [Starlingx-discuss] [TSC] TSC minutes - 4/9 Message-ID: <3D27D7CC-CE98-4B0D-874D-F8425FEF6F8F@windriver.com> Hi all; Please see below the minutes for 4/8/2020: * Project confirmation o Board meeting June 7th o Pre-meeting to be planned o Other confirmed projects get feedback - need 1 or 2 weeks for feedback - so we need a deck available for review by May 15th * Virtual PTG - first week of June o Planning for STX 5.0 o Focused sesssion with Kata o The TSC is looking for *input to the Virtual PTG agenda* * it would be great to have topics from users and developers for what they would like to discuss at the PTG. This will help make a remote session, more interactive and interesting for all. o Only 2 hours per day where there is good overlap o Are there adjacent communities that we would invite to virtual PTG (Edge WG is doing this)? § Kata community § Identify topics so the agendas can be aligned * Sanity - results - initiative to run on VM's on o is it possible to use Zuul - VM's ? o Leverage virtual environments to o Issue is how to get image onto the virtual environment o Triggered by build and what is the trigger for Zuul § Engage the Zuul community/Infrastructure team · Reach out via IRC - opendev channel o Do we want to prototype the approach and see what is possible? Yes o Virtual on Virtual what are the challenges ? Topic backlog: * Containerizing more services * How do we do retrospectives as a community? * Ideas for future Hack-a-thons * Eco-system collaborations - Packet, Cengn others -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Apr 14 19:23:44 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 14 Apr 2020 19:23:44 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 15, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200415T1400 From Robert.Church at windriver.com Tue Apr 14 21:21:45 2020 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 14 Apr 2020 21:21:45 +0000 Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 Message-ID: As part of updating the container components for STX 4.0, changes have been merged to enable the latest release of Kubernetes: https://review.opendev.org/#/q/topic:k8s_upversion+(status:open+OR+status:merged) Anyone behind a firewall who pulls docker images into a local repository will need to grab some updated images: k8s.gcr.io/coredns:1.6.7 k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/pause:3.2 Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Apr 15 13:19:30 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 15 Apr 2020 15:19:30 +0200 Subject: [Starlingx-discuss] Edge sessions on the virtual PTG - ACTION NEEDED Message-ID: <9184A423-9779-4155-8F96-11DE63E62C1A@gmail.com> Hi, I’m reaching out to you as I’m organizing the sessions for the OSF Edge Computing Group to go through edge related topics that are in interest on the official schedule[2] of the virtual PTG[1]. As this area is in interest for StarlingX as well it would be great to have contributors of this community attending the edge sessions and contribute to our discussions including cross-project collaboration related items. The working group members are currently considering to book three blocks (~2 hours) to cover reference architecture and testing discussions as well as topics that are in interest for cross—project collaboration. More details are on our PTG planning etherpad[3]. I created a Doodle poll[4] with time slots that are doable around the globe. Please __fill it out as soon as you can__ if you are interested in joining. The current approach is to look into the most popular slot to turn it into a cross-project discussion as well as booking the three most popular slots overall to cover the aforementioned topics. Please let me know if you have any questions. Thanks and Best Regards, Ildikó [1] http://lists.openstack.org/pipermail/edge-computing/2020-April/000699.html [2] https://ethercalc.openstack.org/126u8ek25noy [3] https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020 [4] https://doodle.com/poll/gpd4hg6ambryi8c9 From Bill.Zvonar at windriver.com Wed Apr 15 14:44:07 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 15 Apr 2020 14:44:07 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 15, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * Monolithic: all green since last week * Nic mentioned that today's build is having issues, Don investigated - couple of updates went in yesterday, broke installation * Layered: all green * pending confirmation of last step of validating the docker images that come out of the layered build - Scott/Nic to validate * Bart raised concern about having to manually update version info with layered build, partially solved by PBR - to be discussed in the Build meeting tomorrow * Gerrit Reviews in Need of Attention * Host side OpenStack services/clients upgrade to Train: @Brent and other reviewers, please help to review. * Storyboard: https://storyboard.openstack.org/#!/story/2007502 (Test result updated in the comments.) * Patch list under review: https://review.opendev.org/#/q/topic:train_upgrade+status:open (These patches are expected to be merged together.) * OpenStack related patches * https://review.opendev.org/#/c/716524/ Last patch for bug1859641 IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status * https://review.opendev.org/#/c/699532/ bug 1855474 OpenStack pods were not recovered after force reboot active controller * https://review.opendev.org/#/q/topic:for_ussuri+(status:open+OR+status:merged) OpenStack Ussuri upgrade patch list under review * CentOS 8 Kernel Upgrade Plan * Austin: they'll move the kernel to the new repo & need a place for the pre-built kernel srpms to be hosted - Scott to look into that * Topics for this Week * stx-integ repo freeze complete (Davlet): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008299.html * PSA: Contributing to Docs (Mary): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008293.html * Open Requests for Help * nothing this week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, April 14, 2020 3:24 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Apr 15, 2020) Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200415T1400 From Don.Penney at windriver.com Wed Apr 15 14:53:53 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 15 Apr 2020 14:53:53 +0000 Subject: [Starlingx-discuss] Installation fails for 20200415T013011Z build Message-ID: Hi folks, A couple of updates merged yesterday that are causing installation failures: The following error occurred while installing. This is a fatal error and installation will be aborted. YumRPMTransError: Could not run transaction. file /usr/lib/application/metadata.yaml conflicts between attempted installs of stx-nginx-ingress-controller-helm-1.0-1.tis.noarch and stx-cert-manager- helm-1.0-1.tis.noarch These updates have been reverted and we've kicked off a new CENGN build. If you have rebased since about 4PM Eastern time yesterday, you will need to rebase now to pick up the reversions. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Wed Apr 15 15:13:46 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Wed, 15 Apr 2020 15:13:46 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200415 Message-ID: Sanity Test from 2020-April-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200415T013011Z/outputs/iso/) Status: RED We have ran the installation twice on Jenkins Bare Metal, twice on Virtual environment and twice on local installations, they all failed with the same errors. The important part of the log (the one that is showing the errors) can be accessed here http://paste.openstack.org/show/792171/. All installations failed with a timeout when connecting via ssh. Today’s community call revealed that some updates have been made. We will not create Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer /) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Wed Apr 15 15:16:03 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Wed, 15 Apr 2020 15:16:03 +0000 Subject: [Starlingx-discuss] Installation fails for 20200415T013011Z build In-Reply-To: References: Message-ID: Hello, We will try again with the next image. Unfortunately it is late for us in Europe, we will try again tomorrow with the image that is being built automatically. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer From: Penney, Don Sent: Wednesday, April 15, 2020 5:54 PM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] Installation fails for 20200415T013011Z build Hi folks, A couple of updates merged yesterday that are causing installation failures: The following error occurred while installing. This is a fatal error and installation will be aborted. YumRPMTransError: Could not run transaction. file /usr/lib/application/metadata.yaml conflicts between attempted installs of stx-nginx-ingress-controller-helm-1.0-1.tis.noarch and stx-cert-manager- helm-1.0-1.tis.noarch These updates have been reverted and we’ve kicked off a new CENGN build. If you have rebased since about 4PM Eastern time yesterday, you will need to rebase now to pick up the reversions. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From stasik at stasik.com Wed Apr 15 16:12:07 2020 From: stasik at stasik.com (Sten Gruener) Date: Wed, 15 Apr 2020 18:12:07 +0200 Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc Message-ID: Dear community, we have got starlingx running on bare metal and experience an issue that docker demon claims only 4 cpus out of 32. "docker info" output contains CPUs: 4 "nproc" also returns 4 "nproc --all" returns 32 as expected /usr/lib/systemd/system/docker.service contains LimitNPROC=infinity LimitCORE=infinity Where are these limit of 4 set and how can I change them? BR Sten -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tee.Ngo at windriver.com Wed Apr 15 16:21:26 2020 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Wed, 15 Apr 2020 16:21:26 +0000 Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc In-Reply-To: References: Message-ID: Hi, You must have deployed an All-in-one. The value reflects the number of cores reserved for platform services “source /etc/platform/openrc|grep Platform”. You can allocate more cores to platform using system host-cpu-modify command. A host lock/unlock will be required. Tee From: Sten Gruener [mailto:stasik at stasik.com] Sent: April-15-20 12:12 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc Dear community, we have got starlingx running on bare metal and experience an issue that docker demon claims only 4 cpus out of 32. "docker info" output contains CPUs: 4 "nproc" also returns 4 "nproc --all" returns 32 as expected /usr/lib/systemd/system/docker.service contains LimitNPROC=infinity LimitCORE=infinity Where are these limit of 4 set and how can I change them? BR Sten -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tee.Ngo at windriver.com Wed Apr 15 16:45:19 2020 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Wed, 15 Apr 2020 16:45:19 +0000 Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc In-Reply-To: References: Message-ID: One correction, “source /etc/platform/openrc|grep Platform”, should be “source /etc/platform/openrc; system host-cpu-list controller-0|grep Platform” If you get an error “Can not lock an active controller” then you will need to run a system host-swact command first before you can lock the host. Repeat the same steps for the other controller. Tee From: Ngo, Tee Sent: April-15-20 12:21 PM To: Sten Gruener; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] CPU configuration for dockerd and nproc Hi, You must have deployed an All-in-one. The value reflects the number of cores reserved for platform services “source /etc/platform/openrc|grep Platform”. You can allocate more cores to platform using system host-cpu-modify command. A host lock/unlock will be required. Tee From: Sten Gruener [mailto:stasik at stasik.com] Sent: April-15-20 12:12 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CPU configuration for dockerd and nproc Dear community, we have got starlingx running on bare metal and experience an issue that docker demon claims only 4 cpus out of 32. "docker info" output contains CPUs: 4 "nproc" also returns 4 "nproc --all" returns 32 as expected /usr/lib/systemd/system/docker.service contains LimitNPROC=infinity LimitCORE=infinity Where are these limit of 4 set and how can I change them? BR Sten -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Wed Apr 15 17:51:41 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Wed, 15 Apr 2020 17:51:41 +0000 Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 In-Reply-To: References: Message-ID: Hi Robert, Thank you for the announcement. We’ve pushed the images on the local repository. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Church, Robert Sent: Wednesday, April 15, 2020 00:22 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 As part of updating the container components for STX 4.0, changes have been merged to enable the latest release of Kubernetes: https://review.opendev.org/#/q/topic:k8s_upversion+(status:open+OR+status:merged) Anyone behind a firewall who pulls docker images into a local repository will need to grab some updated images: k8s.gcr.io/coredns:1.6.7 k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/pause:3.2 Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Wed Apr 15 19:35:06 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 15 Apr 2020 21:35:06 +0200 Subject: [Starlingx-discuss] Upcoming TSC elections Message-ID: Hi StarlingX Community, The 2020 H1 TSC election period is starting in just a bit over a month from now. This email contains important information about the elections, please read carefully. We have 4 seats up for election this time around. For all the details on the elections please visit: https://docs.starlingx.io/election/ The nomination period officially begins on __May 19, 2020, 20:00 UTC__. Please read the stipulations and timelines for candidates and electorate contained in the above governance documentation. IMPORTANT REMINDER: If you would like to run for any open seat you need to register as an OpenStack Foundation individual member prior to when the nomination period starts. Also please note that you are required to confirm your preferred email address in Gerrit by __May 12, 2020 00:00 UTC__ as described here: https://docs.starlingx.io/election/#electorate to make sure ballots are sent out to the correct addresses. Please note, if no more than 4 candidates are nominated till the end of the nomination period who also match all requirements of the TSC group, that candidates will win by acclaim, and there will be no poll. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://docs.starlingx.io/election/#election-officials From Robert.Church at windriver.com Wed Apr 15 19:45:32 2020 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 15 Apr 2020 19:45:32 +0000 Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 In-Reply-To: References: Message-ID: Please include the following as well: k8s.gcr.io/etcd:3.4.3-0 The full list is: k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/pause:3.2 k8s.gcr.io/etcd:3.4.3-0 k8s.gcr.io/coredns:1.6.7 Previously, I only checked the list of deployed images in the cluster. Since we run etcd natively this is not deployed in the cluster, but is still required to be pulled as part of bringing up Kubernetes. Bob From: "Jascanu, Nicolae" Date: Wednesday, April 15, 2020 at 12:52 PM To: Robert Church , "'starlingx-discuss at lists.starlingx.io'" Subject: RE: Kubernetes upgrade to v1.18.1 Hi Robert, Thank you for the announcement. We’ve pushed the images on the local repository. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Church, Robert Sent: Wednesday, April 15, 2020 00:22 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Kubernetes upgrade to v1.18.1 As part of updating the container components for STX 4.0, changes have been merged to enable the latest release of Kubernetes: https://review.opendev.org/#/q/topic:k8s_upversion+(status:open+OR+status:merged) Anyone behind a firewall who pulls docker images into a local repository will need to grab some updated images: k8s.gcr.io/coredns:1.6.7 k8s.gcr.io/kube-apiserver:v1.18.1 k8s.gcr.io/kube-controller-manager:v1.18.1 k8s.gcr.io/kube-proxy:v1.18.1 k8s.gcr.io/kube-scheduler:v1.18.1 k8s.gcr.io/pause:3.2 Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3924 bytes Desc: image001.png URL: From austin.sun at intel.com Thu Apr 16 02:05:11 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 16 Apr 2020 02:05:11 +0000 Subject: [Starlingx-discuss] MoM: Weekly StarlingX non-OpenStack distro meeting, 4/15/2020 Message-ID: Hi All: Thanks martin presenting migration ceph solution. Thanks All sharing the thought and giving advices . MoM for 4/15 meeting: - ceph containerization martin will share the steps migration from native ceph to rook(containerization ceph) https://drive.google.com/file/d/1pojKWqFXxJACHkDxPLm8ZJN992dz8-6S/view?usp=sharing open topic: Bob and Brent will give some more comments or advice for those items. rook: 1) open topic for lvm/gpt table new rook application. migration: 1) ceph osd journal , any better way to use original journal disk like /dev/sdb2. 2) storage node need to be added to k8s to support migration 3) after migration, storage backend is need to be disabled or removed patches are waitting for review https://review.opendev.org/#/c/714857/ https://review.opendev.org/#/c/716792/ https://review.opendev.org/#/c/713084/ - kernel upgrade : 1) waitting kernel-rt/rt-setup pre-built srpm 2) waitting new kernel repo . - centos8 upgrade: python-keyring, drdb-tools, python-html5lib, python-3parclient, python-lefthandclient, lighttpd have been upgraded, and uploaded gerrit still some build error, rebasing. Thanks. BR Austin Sun. From maryx.camp at intel.com Thu Apr 16 02:09:21 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 16 Apr 2020 02:09:21 +0000 Subject: [Starlingx-discuss] [docs] Provide doc input for 2006145 In-Reply-To: <9700A18779F35F49AF027300A49E7C766397D10B@SHSMSX104.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C766397D10B@SHSMSX104.ccr.corp.intel.com> Message-ID: Hi Shuicheng, Apologies for the delayed response. I opened a LaunchPad to track this: https://bugs.launchpad.net/starlingx/+bug/1873109 Next steps: I will create the RST file with your source text, submit a review, and add you as one of the reviewers. If you have any questions, please let me know. Thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Lin, Shuicheng Sent: Friday, April 3, 2020 4:26 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs] Provide doc input for 2006145 Hi all, Kata Container is supported in StarlingX recently. Here is the doc for how to run kata container in StarlingX. Please help review it, and feel free to notify me if anything is missed or you have question on it. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Thu Apr 16 02:26:13 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 16 Apr 2020 02:26:13 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-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 on Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-15 * All -- reviews merged since last week: 3 * All -- bug status -- 3 total * [new bug last week] Backup & restore procedure info, new doc content https://bugs.launchpad.net/starlingx/+bug/1871065 * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Upgrade Kubernetes version -- Review available: https://review.opendev.org/#/c/712583/ AR Mary to update review with latest feedback. * no update: Assignment of R4 doc tasks * All -- Opens * WIP: Docker proxy setup Priority 1 task ? First review merged (1 R3 install guide): https://review.opendev.org/#/c/718298/ ? New review (7 R3 install guides): https://review.opendev.org/#/c/720252/ ? AR Mary update patchset to add pointer to new docker proxy page at the next-higher-level of install guides (similar to the IPv4 note, 1 per Rx folder, see https://review.opendev.org/#/c/718302/) * Brucej -- let's discuss Ildiko's email, esp. network documentation (STX feedback): http://lists.starlingx.io/pipermail/starlingx-discuss/2020-March/008088.html ? AR Greg to make a doc story - ask for help from networking team. We need overview of how to configure networking in STX. ? Mapping between STX networking, how we differ from OpenStack behavior, then point to OpenStack for more details. ? "The way how OpenStack networking was propagated over data networks turned out to be very problematic and caused hitting the wall a few times. In details you have to configure data networks over the platform management components, but then you have to set VLAN's you are going to use over data networks on the OpenStack side. This was not documented anywhere." * Reviews in progress: ? STX IPv6 deployment https://review.opendev.org/#/c/718302/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Apr 16 05:24:45 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 16 Apr 2020 05:24:45 +0000 Subject: [Starlingx-discuss] [docs] Provide doc input for 2006145 In-Reply-To: References: <9700A18779F35F49AF027300A49E7C766397D10B@SHSMSX104.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C7663987E82@SHSMSX104.ccr.corp.intel.com> Hi Mary, Thanks for helping me on the task. Let me know if there is any problem. Best Regards Shuicheng From: Camp, MaryX Sent: Thursday, April 16, 2020 10:09 AM To: Lin, Shuicheng ; starlingx-discuss at lists.starlingx.io Subject: RE: [docs] Provide doc input for 2006145 Hi Shuicheng, Apologies for the delayed response. I opened a LaunchPad to track this: https://bugs.launchpad.net/starlingx/+bug/1873109 Next steps: I will create the RST file with your source text, submit a review, and add you as one of the reviewers. If you have any questions, please let me know. Thanks, Mary Camp PTIGlobal Technical Writer | maryx.camp at intel.com From: Lin, Shuicheng > Sent: Friday, April 3, 2020 4:26 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs] Provide doc input for 2006145 Hi all, Kata Container is supported in StarlingX recently. Here is the doc for how to run kata container in StarlingX. Please help review it, and feel free to notify me if anything is missed or you have question on it. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Apr 16 07:35:52 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Apr 2020 09:35:52 +0200 Subject: [Starlingx-discuss] Deleting old Zoom recordings? Message-ID: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> Hi, I’m reaching out to you about the recordings of the Zoom meetings as the currently available storage space for these is running out. One of the solutions is to keep a running window, I think one of the options Zoom offers is to delete files that are older than a year. I can check if the timeframe is configurable. Before going into deep details I would like to get the community’s preference on the way forward first. Do people find this as an acceptable approach? Please let me know your thoughts. Thanks, Ildikó From Frank.Miller at windriver.com Thu Apr 16 12:55:00 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 16 Apr 2020 12:55:00 +0000 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Agenda Message-ID: Agenda for today's build meeting: 1. Build layering: a) Decision on kmod upversion when kernel changes b) Discussion on other scenarios when a packahe version update must be done and how to address each - Flock python packages --> PBR is solution? - Distro packages - is this a likely scenario or can it be hand managed? c) Status of sanity for docker layer build d) What work items remain before project can cutover to build layering? 2. kernel-rt srpm approach 3. PBR update 4. Jenkins git repo status 5. Build avoidance algorithm review. Goal is to either identify issues/improvements or be satisfied it is the correct approach. Plan would be to have a review for next week's build meeting. Zoom: https://zoom.us/j/342730236 Etherpad: https://etherpad.openstack.org/p/stx-build Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From mihail-laurentiu.trica at intel.com Thu Apr 16 13:10:00 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Thu, 16 Apr 2020 13:10:00 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 Message-ID: Sanity Test from 2020-April-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200416T013011Z/outputs/iso/) Status: RED We have ran the installation twice on Bare Metal and both times installation failed at the Ansible step (the issue is different than yesterday). The error log can be seen here http://paste.openstack.org/show/792225/. The Virtual environment installation did not fail, there are only 12 failed tests on Duplex configuration only. Considering that setup has failed on Bare Metal, we are investigating if these 12 tests (that failed only on Duplex configuration) are showing real issues or not. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Apr 16 13:44:50 2020 From: scott.little at windriver.com (Scott Little) Date: Thu, 16 Apr 2020 09:44:50 -0400 Subject: [Starlingx-discuss] [Build] Build Avoidance algorithm Message-ID: For those that are curious about the current Build Avoidance algorithm... Note: The foundational principle of build avoidance is that it is faster to download the rpms than it is to build them.  This is likely only true the host for reference builds and the consumer are close to each other and share a high speed link.  It is not practical for mirror.starlingx.cengn.ca to serve as provider of reference builds for the world.  The real goal is for a corporate office to have a provider of reference builds to the designers within their corporate network. Which reference build server to use? - A data file, not supplied by the STX gits, is required to describe your reference build server. It's location should be ... $MY_REPO/local-build-data/build_avoidance_source - The required fields, and hypothetical values are ... BUILD_AVOIDANCE_DATE_FORMAT="%Y%m%d" BUILD_AVOIDANCE_TIME_FORMAT="%H%M%S" BUILD_AVOIDANCE_DATE_TIME_DELIM="T" BUILD_AVOIDANCE_DATE_TIME_POSTFIX="Z" BUILD_AVOIDANCE_DATE_UTC=0 BUILD_AVOIDANCE_FILE_TRANSFER="rsync" BUILD_AVOIDANCE_USR="jenkins" BUILD_AVOIDANCE_HOST="my-builder.my-company.com" BUILD_AVOIDANCE_DIR="/localdisk/loadbuild/jenkins/master" Reference build server - The reference build server should build regularly, e.g. daily - The MY_WORKSPACE variable set prior to a reference build should be ... TIMESTAMP=$(date +${BUILD_AVOIDANCE_DATE_FORMAT}${BUILD_AVOIDANCE_DATE_TIME_DELIM}${BUILD_AVOIDANCE_TIME_FORMAT}${BUILD_AVOIDANCE_DATE_TIME_POSTFIX}) export MY_WORKSPACE=${BUILD_AVOIDANCE_DIR}/${TIMESTAMP} - Builds should be preserved for a useful period of time. e.g. at least two weeks Which reference build to use? - The reference builds side = Build contexts of all builds are collected into a common directory. = Context files are prefixed by the build time stamp allowing chronological traversal of the files. - On the consumer side = The set of available reference build context are downloaded = Traverse the set of available build contexts from newest to oldest. + If all sha of all gits in a candidate reference build are also present in our local git context we stop traversal and will use this reference build. = If selected reference build is newer than the last (if any) reference build that we downloaded, then download the selected build context, else do nothing. Downloading a selected reference build - The list of artifacts to download is captured in datafile $MY_REPO/build-data/build_avoidance_source. = The following paths are relative to $MY_WORKSPACE/$BUILD_TYPE BUILD_AVOIDANCE_SRPM_DIRECTORIES="inputs srpm_assemble rpmbuild/SRPMS rpmbuild/SOURCES" BUILD_AVOIDANCE_SRPM_FILES="" BUILD_AVOIDANCE_RPM_DIRECTORIES="results rpmbuild/RPMS rpmbuild/SPECS repo/cgcs-tis-repo/dependancy-cache" BUILD_AVOIDANCE_RPM_FILES=".platform_release" = details of the files and directories downloaded inputs = Working directory used to assemble srpms from git or tarball srpm_assemble = working directory used to assemble srpms from upstream srpms rpmbuild/SRPMS = Assembled stx src.rpms that we will build rpmbuild/SOURCES = Additional per package metadata data collected to support build avoidance rpmbuild/SOURCES//srpm_reference.md5 = md5sums of all files that go into building the STX src.rpm results = per package build logs and artifacts generated by mockchain rpmbuild/RPMS = Build rpms rpmbuild/SPECS = spec files of build rpms repo/cgcs-tis-repo/dependancy-cache = build-pkgs data summarazing = The 'Requires' of rpms = the 'BuildRequires' of src.rpms = What rpms are derived from what src.rpms .platform_release = the platform release value - The reference builds side = The only extra step to support build avoidance is to generate rpmbuild/SOURCES//srpm_reference.md5 files - On the consumer side = For each build type we want... + For each file or subdirectory listed in $MY_REPO/build-data/build_avoidance_source * rsync the file or directory with options to preserve the file time stamp Build src.rpms - for each build type = For each package + Generate a list of input files for the current package + Generate a srpm_reference.md5 file for the current inputs. + compare srpm_reference.md5 files for current and reference builds. * If different (list of files, or md5sum of those files), we need to rebuild this src.rpm Build RPMS - for each build type = For each package + or list of rpms build by src.rpm * if rpm is missing, must rebuild package * if rpm is wrong version, must rebuild package * if rpm older than src.rpm, then must rebuild package NOTE: Assumes reference build and consumer are on NTP time, and any drift is well below the download time for the reference build -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Apr 16 15:21:45 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 16 Apr 2020 11:21:45 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_repo_sync_layered - Build # 255 - Failure! Message-ID: <1454036309.1204.1587050507468.JavaMail.javamailuser@localhost> Project: STX_repo_sync_layered Build #: 255 Status: Failure Timestamp: 20200416T152134Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200416T152119Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MANIFEST: containers.xml PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/20200416T152119Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20200416T152119Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers From bruce.e.jones at intel.com Thu Apr 16 15:34:42 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 16 Apr 2020 15:34:42 +0000 Subject: [Starlingx-discuss] Deleting old Zoom recordings? In-Reply-To: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> References: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> Message-ID: <9A85D2917C58154C960D95352B22818B0108098F84@fmsmsx121.amr.corp.intel.com> It sounds like the running window is a good approach. Do we know if or how often those files are actually accessed? brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, April 16, 2020 12:36 AM To: starlingx Subject: [Starlingx-discuss] Deleting old Zoom recordings? Hi, I’m reaching out to you about the recordings of the Zoom meetings as the currently available storage space for these is running out. One of the solutions is to keep a running window, I think one of the options Zoom offers is to delete files that are older than a year. I can check if the timeframe is configurable. Before going into deep details I would like to get the community’s preference on the way forward first. Do people find this as an acceptable approach? Please let me know your thoughts. Thanks, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Thu Apr 16 15:53:34 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 16 Apr 2020 15:53:34 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 In-Reply-To: References: Message-ID: There is not enough info in the paste link to see why ansible failed. You likely need more input from ansible or look at the logs. Suspicion is you may be missing some of the images required now that Kubernetes has been moved to v1.18 – have you checked all the images are in your repository as listed by Bob Church in his email yesterday? Frank From: Trica, Mihail-Laurentiu Sent: Thursday, April 16, 2020 9:10 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 Sanity Test from 2020-April-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200416T013011Z/outputs/iso/) Status: RED We have ran the installation twice on Bare Metal and both times installation failed at the Ansible step (the issue is different than yesterday). The error log can be seen here http://paste.openstack.org/show/792225/. The Virtual environment installation did not fail, there are only 12 failed tests on Duplex configuration only. Considering that setup has failed on Bare Metal, we are investigating if these 12 tests (that failed only on Duplex configuration) are showing real issues or not. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Thu Apr 16 17:54:25 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 16 Apr 2020 17:54:25 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 In-Reply-To: References: Message-ID: Hi Frank, The images were installed yesterday in the mirror registry. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Miller, Frank Sent: Thursday, April 16, 2020 18:54 To: Trica, Mihail-Laurentiu ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 There is not enough info in the paste link to see why ansible failed. You likely need more input from ansible or look at the logs. Suspicion is you may be missing some of the images required now that Kubernetes has been moved to v1.18 – have you checked all the images are in your repository as listed by Bob Church in his email yesterday? Frank From: Trica, Mihail-Laurentiu > Sent: Thursday, April 16, 2020 9:10 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200416 Sanity Test from 2020-April-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200416T013011Z/outputs/iso/) Status: RED We have ran the installation twice on Bare Metal and both times installation failed at the Ansible step (the issue is different than yesterday). The error log can be seen here http://paste.openstack.org/show/792225/. The Virtual environment installation did not fail, there are only 12 failed tests on Duplex configuration only. Considering that setup has failed on Bare Metal, we are investigating if these 12 tests (that failed only on Duplex configuration) are showing real issues or not. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From ildiko.vancsa at gmail.com Thu Apr 16 19:20:16 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 16 Apr 2020 21:20:16 +0200 Subject: [Starlingx-discuss] Deleting old Zoom recordings? In-Reply-To: <9A85D2917C58154C960D95352B22818B0108098F84@fmsmsx121.amr.corp.intel.com> References: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> <9A85D2917C58154C960D95352B22818B0108098F84@fmsmsx121.amr.corp.intel.com> Message-ID: <235917DA-FF27-477C-B59A-001A4558A408@gmail.com> Hi Bruce, The only data I can see on the Zoom admin web page is that how many times a recording was viewed, but it doesn’t show a timeline if any of the older ones were recently accessed or not. Even to see how many times they were viewed in total I need to go recording by recording on the web so it’s a slow manual process. I can create a Doodle poll asking if people are interested in accessing recordings that are older than a year and use that for the decision. Do you think that would be worthwhile to do? Thanks, Ildikó > On Apr 16, 2020, at 17:34, Jones, Bruce E wrote: > > It sounds like the running window is a good approach. Do we know if or how often those files are actually accessed? > > brucej > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Thursday, April 16, 2020 12:36 AM > To: starlingx > Subject: [Starlingx-discuss] Deleting old Zoom recordings? > > Hi, > > I’m reaching out to you about the recordings of the Zoom meetings as the currently available storage space for these is running out. > > One of the solutions is to keep a running window, I think one of the options Zoom offers is to delete files that are older than a year. I can check if the timeframe is configurable. > > Before going into deep details I would like to get the community’s preference on the way forward first. Do people find this as an acceptable approach? > > Please let me know your thoughts. > > Thanks, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Steven.Webster at windriver.com Fri Apr 17 01:43:50 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Fri, 17 Apr 2020 01:43:50 +0000 Subject: [Starlingx-discuss] MoM: Bi-Weekly StarlingX networking meeting, 4/16/2020 Message-ID: MoM for 4/16 meeting: * TSN * https://storyboard.openstack.org/#!/story/2006746 * Found resolution to traffic loss issue in test setup * Kata container kernel / rootfs has been built w/ TSN support * Intention is that a recipe / documentation will be provided for users that also want to include this functionality * * IPv6 PXE boot network support * https://storyboard.openstack.org/#!/story/2006442 * No updates since Joseph R provided feedback March 20 * Action: Steve to reach out to the prime to see if the issues noted on the mailing list are resolved * Test * Kata container testing planned for April 27 * Hardware setup on-site is ongoing. Starting with AIO-SX / switch config * Bug updates: * New: * https://bugs.launchpad.net/starlingx/+bug/1871469 -- Unable to set Default route in POD with static IP connected with SR-IOV VFs interfaces in Simplex * Will be marked invalid as relates to Multus 3.4 issue on STX 3.0 * Updated: * https://bugs.launchpad.net/starlingx/+bug/1866230 - Tracebacks related to LLPD neighbor (INSERT INTO lldp_tlvs) filling sysinv.log * In progress * https://bugs.launchpad.net/starlingx/+bug/1862651 -- IPv6 DC: 100.113 alarm "'DATA-NETWORK0' interface failed" raised at both system controller and subclouds after installation * Assigned to Thomas G * https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" * Very close to being resolved, one more review to go * General: * Request for expanded StarlingX network documentation. * Example: Description of an OAM network, data network, platform network, etc * Action: Steve to raise a LP to track, review the current documentation and identify areas where we can increase coverage Thanks, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Apr 17 02:06:09 2020 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 17 Apr 2020 02:06:09 +0000 Subject: [Starlingx-discuss] nominate several core reviewers on 3 STX projects Message-ID: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> Hi cores, I would like to nominate these guys as core reviewers in following project: 1. project:starlingx/integ: Sun, Austin austin.sun at intel.com 2. project:starlingx/kernel: Lin, Shuicheng shuicheng.lin at intel.com 3. project:starlingx/docs: Wang, Yi C yi.c.wang at intel.com These 3 guys have been working on StarlingX since 2018 March, and they contributed considerate number of patches for features, integrations and bug fixes. Upgrading them to core reviewers will enable them to contribute more on StarlingX and have better coverage on the patch review in Asian time zone. So, please let us know your feedback. Thanks! Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Fri Apr 17 02:58:33 2020 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 17 Apr 2020 02:58:33 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: Message-ID: Hi Frank: It seems centos8 feature branch is missing stx-kernel repo , would you like to help to create ? Thanks. BR Austin Sun. From: Miller, Frank Sent: Thursday, April 9, 2020 10:03 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Thank-you Austin for confirming. Davlet Panech will start this work on Thursday and let us all know when we need to freeze stx-integ and also when the new stx-kernel repo is created and ready for all to use. Frank From: Sun, Austin > Sent: Wednesday, April 08, 2020 9:51 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank > Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Apr 17 08:03:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 17 Apr 2020 04:03:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 84 - Failure! Message-ID: <118129949.1210.1587110613504.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 84 Status: Failure Timestamp: 20200417T080245Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200417T080245Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From austin.sun at intel.com Fri Apr 17 12:45:05 2020 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 17 Apr 2020 12:45:05 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Message-ID: Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Apr 17 15:00:57 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 17 Apr 2020 15:00:57 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> I thought that dist-cloud sub-nodes are Kubernetes only - without OpenStack support... brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Apr 17 15:40:02 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 17 Apr 2020 15:40:02 +0000 Subject: [Starlingx-discuss] nominate several core reviewers on 3 STX projects In-Reply-To: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> References: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> Message-ID: +1 From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Thursday, April 16, 2020 10:06 PM To: starlingx-discuss at lists.starlingx.io Cc: Sun, Austin; Lin, Shuicheng; Wang, Yi C Subject: [Starlingx-discuss] nominate several core reviewers on 3 STX projects Hi cores, I would like to nominate these guys as core reviewers in following project: 1. project:starlingx/integ: Sun, Austin austin.sun at intel.com 2. project:starlingx/kernel: Lin, Shuicheng shuicheng.lin at intel.com 3. project:starlingx/docs: Wang, Yi C yi.c.wang at intel.com These 3 guys have been working on StarlingX since 2018 March, and they contributed considerate number of patches for features, integrations and bug fixes. Upgrading them to core reviewers will enable them to contribute more on StarlingX and have better coverage on the patch review in Asian time zone. So, please let us know your feedback. Thanks! Regards, Yong -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Apr 17 17:04:56 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 17 Apr 2020 17:04:56 +0000 Subject: [Starlingx-discuss] patches needing review Message-ID: <9A85D2917C58154C960D95352B22818B01080A41F8@fmsmsx123.amr.corp.intel.com> These patches need attention - please review and provide feedback: Host side OpenStack services/clients upgrade to Train: @Brent and other reviewers, please help to review. Storyboard: https://storyboard.openstack.org/#!/story/2007502 (Test result updated in the comments.) Patch list under review: https://review.opendev.org/#/q/topic:train_upgrade+status:open (These patches are expected to be merged together.) OpenStack related patches https://review.opendev.org/#/c/699532/ bug 1855474 OpenStack pods were not recovered after force reboot active controller Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruediger.stock at intel.com Fri Apr 17 17:44:00 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Fri, 17 Apr 2020 17:44:00 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200417 Message-ID: Sanity Test from 2020-April-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200417T013011Z/outputs/iso/) 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 External - 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 - 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 External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Apr 17 17:55:56 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 17 Apr 2020 17:55:56 +0000 Subject: [Starlingx-discuss] Deleting old Zoom recordings? In-Reply-To: <235917DA-FF27-477C-B59A-001A4558A408@gmail.com> References: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> <9A85D2917C58154C960D95352B22818B0108098F84@fmsmsx121.amr.corp.intel.com> <235917DA-FF27-477C-B59A-001A4558A408@gmail.com> Message-ID: <9A85D2917C58154C960D95352B22818B01080A52B5@fmsmsx123.amr.corp.intel.com> Ildiko, I think if you posted "I'm going to remove older recordings in a week unless someone objects", that would be good enough. brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, April 16, 2020 12:20 PM To: Jones, Bruce E Cc: starlingx Subject: Re: [Starlingx-discuss] Deleting old Zoom recordings? Hi Bruce, The only data I can see on the Zoom admin web page is that how many times a recording was viewed, but it doesn’t show a timeline if any of the older ones were recently accessed or not. Even to see how many times they were viewed in total I need to go recording by recording on the web so it’s a slow manual process. I can create a Doodle poll asking if people are interested in accessing recordings that are older than a year and use that for the decision. Do you think that would be worthwhile to do? Thanks, Ildikó > On Apr 16, 2020, at 17:34, Jones, Bruce E wrote: > > It sounds like the running window is a good approach. Do we know if or how often those files are actually accessed? > > brucej > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Thursday, April 16, 2020 12:36 AM > To: starlingx > Subject: [Starlingx-discuss] Deleting old Zoom recordings? > > Hi, > > I’m reaching out to you about the recordings of the Zoom meetings as the currently available storage space for these is running out. > > One of the solutions is to keep a running window, I think one of the options Zoom offers is to delete files that are older than a year. I can check if the timeframe is configurable. > > Before going into deep details I would like to get the community’s preference on the way forward first. Do people find this as an acceptable approach? > > Please let me know your thoughts. > > Thanks, > Ildikó > > > > _______________________________________________ > 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 Fri Apr 17 18:04:27 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Fri, 17 Apr 2020 18:04:27 +0000 Subject: [Starlingx-discuss] Deleting old Zoom recordings? In-Reply-To: <9A85D2917C58154C960D95352B22818B01080A52B5@fmsmsx123.amr.corp.intel.com> References: <9A57F494-3717-4C0A-B95C-6652C21AAF41@gmail.com> <9A85D2917C58154C960D95352B22818B0108098F84@fmsmsx121.amr.corp.intel.com> <235917DA-FF27-477C-B59A-001A4558A408@gmail.com> <9A85D2917C58154C960D95352B22818B01080A52B5@fmsmsx123.amr.corp.intel.com> Message-ID: Sounds good to me... -----Original Message----- From: Jones, Bruce E Sent: Friday, April 17, 2020 1:56 PM To: Ildiko Vancsa Cc: starlingx Subject: Re: [Starlingx-discuss] Deleting old Zoom recordings? Ildiko, I think if you posted "I'm going to remove older recordings in a week unless someone objects", that would be good enough. brucej -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, April 16, 2020 12:20 PM To: Jones, Bruce E Cc: starlingx Subject: Re: [Starlingx-discuss] Deleting old Zoom recordings? Hi Bruce, The only data I can see on the Zoom admin web page is that how many times a recording was viewed, but it doesn’t show a timeline if any of the older ones were recently accessed or not. Even to see how many times they were viewed in total I need to go recording by recording on the web so it’s a slow manual process. I can create a Doodle poll asking if people are interested in accessing recordings that are older than a year and use that for the decision. Do you think that would be worthwhile to do? Thanks, Ildikó > On Apr 16, 2020, at 17:34, Jones, Bruce E wrote: > > It sounds like the running window is a good approach. Do we know if or how often those files are actually accessed? > > brucej > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: Thursday, April 16, 2020 12:36 AM > To: starlingx > Subject: [Starlingx-discuss] Deleting old Zoom recordings? > > Hi, > > I’m reaching out to you about the recordings of the Zoom meetings as the currently available storage space for these is running out. > > One of the solutions is to keep a running window, I think one of the options Zoom offers is to delete files that are older than a year. I can check if the timeframe is configurable. > > Before going into deep details I would like to get the community’s preference on the way forward first. Do people find this as an acceptable approach? > > Please let me know your thoughts. > > Thanks, > Ildikó > > > > _______________________________________________ > 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 Davlet.Panech at windriver.com Fri Apr 17 22:57:55 2020 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Fri, 17 Apr 2020 22:57:55 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: , Message-ID: Hi Austin, We will look into it on Monday, D. ________________________________ From: Sun, Austin Sent: April 16, 2020 10:58 PM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: It seems centos8 feature branch is missing stx-kernel repo , would you like to help to create ? Thanks. BR Austin Sun. From: Miller, Frank Sent: Thursday, April 9, 2020 10:03 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Thank-you Austin for confirming. Davlet Panech will start this work on Thursday and let us all know when we need to freeze stx-integ and also when the new stx-kernel repo is created and ready for all to use. Frank From: Sun, Austin > Sent: Wednesday, April 08, 2020 9:51 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank > Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I’m sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Sat Apr 18 01:06:17 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 18 Apr 2020 01:06:17 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only - without OpenStack support... brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Sat Apr 18 01:18:36 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sat, 18 Apr 2020 01:18:36 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: , Message-ID: Thanks a lot Davlet. BR Austin Sun. From: Panech, Davlet Sent: Saturday, April 18, 2020 6:58 AM To: Sun, Austin ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Creating stx-kernel repo Hi Austin, We will look into it on Monday, D. ________________________________ From: Sun, Austin > Sent: April 16, 2020 10:58 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: It seems centos8 feature branch is missing stx-kernel repo , would you like to help to create ? Thanks. BR Austin Sun. From: Miller, Frank > Sent: Thursday, April 9, 2020 10:03 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Thank-you Austin for confirming. Davlet Panech will start this work on Thursday and let us all know when we need to freeze stx-integ and also when the new stx-kernel repo is created and ready for all to use. Frank From: Sun, Austin > Sent: Wednesday, April 08, 2020 9:51 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank > Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sat Apr 18 03:07:54 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 17 Apr 2020 23:07:54 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 245 - Failure! Message-ID: <2137017464.1214.1587179275294.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 245 Status: Failure Timestamp: 20200418T030147Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200417T224901Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200417T224901Z DOCKER_BUILD_ID: jenkins-master-flock-20200417T224901Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200417T224901Z/logs FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200417T224901Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From build.starlingx at gmail.com Sat Apr 18 03:07:57 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 17 Apr 2020 23:07:57 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 85 - Still Failing! In-Reply-To: <1026156502.1208.1587110610333.JavaMail.javamailuser@localhost> References: <1026156502.1208.1587110610333.JavaMail.javamailuser@localhost> Message-ID: <90032945.1217.1587179278598.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 85 Status: Still Failing Timestamp: 20200417T224901Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200417T224901Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Apr 18 08:21:36 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 18 Apr 2020 04:21:36 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 86 - Still Failing! In-Reply-To: <1246484388.1215.1587179276249.JavaMail.javamailuser@localhost> References: <1246484388.1215.1587179276249.JavaMail.javamailuser@localhost> Message-ID: <1064096248.1224.1587198097794.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 86 Status: Still Failing Timestamp: 20200418T080331Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200418T080331Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Sat Apr 18 08:21:32 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sat, 18 Apr 2020 04:21:32 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 248 - Failure! Message-ID: <2120460049.1221.1587198094077.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 248 Status: Failure Timestamp: 20200418T081511Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200418T080331Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20200418T080331Z DOCKER_BUILD_ID: jenkins-master-flock-20200418T080331Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200418T080331Z/logs FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20200418T080331Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true From 18245043314 at 163.com Sat Apr 18 10:52:07 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Sat, 18 Apr 2020 18:52:07 +0800 (CST) Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Message-ID: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sat Apr 18 18:57:23 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sat, 18 Apr 2020 18:57:23 +0000 Subject: [Starlingx-discuss] Minutes: Minutes: StarlingX Release Meetng - Apr 16/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Status - Feature Status: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 - Features progressing nicely - Upcoming Feature Merges: - Kata Container Rebase: 4/30 / Prime: Austin - Containerize Ceph - Rook Integration: 5/5 / Prime: Austin - K8s & Container Components Upversion: 4/30 / Prime: Frank - Kernel Upversion: 4/30 / Prime: Austin - Upversion Openstack services on host to train: 4/17 / Prime: Yong - Flock Versioning: 4/30 / Prime: Saul - Layered Build: 4/15 / Prime: Frank - ACTION: Feature Primes, If there are changes to any of the above plans, please let the release team know and update the "Forecast" date in the Feature Status spreadsheet. - Bug Backlog - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 - Total: 86 - Need to start watching the bug backlog and the age of the bugs - Expect teams to pivot to bug resolution once their features wrap up From scott.little at windriver.com Sat Apr 18 21:15:31 2020 From: scott.little at windriver.com (Scott Little) Date: Sat, 18 Apr 2020 17:15:31 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 85 - Still Failing! In-Reply-To: <90032945.1217.1587179278598.JavaMail.javamailuser@localhost> References: <1026156502.1208.1587110610333.JavaMail.javamailuser@localhost> <90032945.1217.1587179278598.JavaMail.javamailuser@localhost> Message-ID: Package stx-nginx-ingress-controller-helm fails to build due to missing 'BuildRequires' on package 'helm' This new package lacks any BuildRequires which is highly implausible. Please folks, test  compile your new package in a clean environment! e.g. build-pkgs --clean build-pkgs  stx-nginx-ingress-controller-helm Scott On 2020-04-17 11:07 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_layer_flock_master_master > Build #: 85 > Status: Still Failing > Timestamp: 20200417T224901Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200417T224901Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: 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 austin.sun at intel.com Sun Apr 19 05:36:53 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 19 Apr 2020 05:36:53 +0000 Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> Message-ID: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Sun Apr 19 07:14:33 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 19 Apr 2020 07:14:33 +0000 Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> Message-ID: is this 4.9T sda size or all disks size ? how much sda is ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 2:36 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" > wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Mon Apr 20 04:49:46 2020 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 20 Apr 2020 04:49:46 +0000 Subject: [Starlingx-discuss] Creating stx-kernel repo In-Reply-To: References: , Message-ID: <9700A18779F35F49AF027300A49E7C7663988A4E@SHSMSX104.ccr.corp.intel.com> Hi Davlet, Zuul is not enabled for kernel git yet, please help enable it. Thanks. Best Regards Shuicheng From: Panech, Davlet Sent: Saturday, April 18, 2020 6:58 AM To: Sun, Austin ; Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Creating stx-kernel repo Hi Austin, We will look into it on Monday, D. ________________________________ From: Sun, Austin > Sent: April 16, 2020 10:58 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: It seems centos8 feature branch is missing stx-kernel repo , would you like to help to create ? Thanks. BR Austin Sun. From: Miller, Frank > Sent: Thursday, April 9, 2020 10:03 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Thank-you Austin for confirming. Davlet Panech will start this work on Thursday and let us all know when we need to freeze stx-integ and also when the new stx-kernel repo is created and ready for all to use. Frank From: Sun, Austin > Sent: Wednesday, April 08, 2020 9:51 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Creating stx-kernel repo Hi Frank: Thanks. As this is just limited impact for kernel upgrade work , it is ok for kernel -upgrade work. Please let us know the change were merged , we will prepare kernel upgrade patch rebase. Thanks. BR Austin Sun. From: Miller, Frank > Sent: Wednesday, April 8, 2020 6:00 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Creating stx-kernel repo Folks: At the community Build meeting last week we agreed to carve out the kernel from stx-integ and put it into its own repo as part of the build layering project [1]. This will help reduce build times further by ensuring the kernel is built only when there is a specific commit in the kernel repo. I'm sending this email to let the community know that this work is starting soon. The Build team will let you know once a cutover date is determined. Frank Miller PL for StarlingX Build [1] https://storyboard.openstack.org/#!/story/2006166 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Apr 20 08:38:31 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 20 Apr 2020 10:38:31 +0200 Subject: [Starlingx-discuss] Edge sessions on the virtual PTG - UPDATE In-Reply-To: <9184A423-9779-4155-8F96-11DE63E62C1A@gmail.com> References: <9184A423-9779-4155-8F96-11DE63E62C1A@gmail.com> Message-ID: <3AFD3BA5-2522-4A30-98FA-9D97197D8C2D@gmail.com> Hi, Thanks to all of you who participated in the poll. Based on the responses we will hold the cross project session on __Wednesday (June 3) 1300 UTC - 1600 UTC__. Further OSF Edge Computing Group sessions are: * Monday (June 1) 1400 UTC - 1600 UTC * Tuesday (June 2) 1300 UTC - 1600 UTC As a reminder we are collecting discussion topics and building the agenda for the event on this etherpad: https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020 Please feel free to drop agenda items and discussion topics into the etherpad. Also please let me know if you have any questions. Thanks, Ildikó > On Apr 15, 2020, at 15:19, Ildiko Vancsa wrote: > > Hi, > > I’m reaching out to you as I’m organizing the sessions for the OSF Edge Computing Group to go through edge related topics that are in interest on the official schedule[2] of the virtual PTG[1]. As this area is in interest for StarlingX as well it would be great to have contributors of this community attending the edge sessions and contribute to our discussions including cross-project collaboration related items. > > The working group members are currently considering to book three blocks (~2 hours) to cover reference architecture and testing discussions as well as topics that are in interest for cross—project collaboration. More details are on our PTG planning etherpad[3]. > > I created a Doodle poll[4] with time slots that are doable around the globe. Please __fill it out as soon as you can__ if you are interested in joining. > > The current approach is to look into the most popular slot to turn it into a cross-project discussion as well as booking the three most popular slots overall to cover the aforementioned topics. > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > > [1] http://lists.openstack.org/pipermail/edge-computing/2020-April/000699.html > [2] https://ethercalc.openstack.org/126u8ek25noy > [3] https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020 > [4] https://doodle.com/poll/gpd4hg6ambryi8c9 From ruediger.stock at intel.com Mon Apr 20 14:51:02 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Mon, 20 Apr 2020 14:51:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200418 Message-ID: Sanity Test from 2020-April-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200418T204518Z/outputs/iso/) 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 External - 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 - 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 External - 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 ] Spurious non-reproducing networking issues were seen with external storage. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sabeel.Ansari at windriver.com Mon Apr 20 16:43:03 2020 From: Sabeel.Ansari at windriver.com (Ansari, Sabeel) Date: Mon, 20 Apr 2020 16:43:03 +0000 Subject: [Starlingx-discuss] cert-manager images Message-ID: Hi StarlingX Community, As part of the cert-manager app support in Stx 4.0, anyone using a private container registry to install from, should pull the following images and push them to your private container registry: quay.io/jetstack/cert-manager-controller:v0.14.2 quay.io/jetstack/cert-manager-webhook:v0.14.2 quay.io/jetstack/cert-manager-cainjector:v0.14.2 quay.io/jetstack/cert-manager-acmesolver:v0.14.2 FYI: https://review.opendev.org/#/q/topic:cert-mgr+(status:open+OR+status:merged) Best regards, Sabeel -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Tue Apr 21 06:30:09 2020 From: yong.hu at intel.com (Hu, Yong) Date: Tue, 21 Apr 2020 06:30:09 +0000 Subject: [Starlingx-discuss] agenda for distro-openstack-meetings - WW17.2 Message-ID: <5E596020-D889-472D-B8FF-5F26C1711FFE@intel.com> 04/21/2020 meeting Agenda: 1. Containerized OpenStack Service Upgrade to “Ussuri” [0] - to be updated by Chant at 99Cloud and Zhipeng at Intel 2. Host OpenStack Clients and services Upgrade to “Train” - Yan @Intel, Nic at Intel to update 3. LP review [1]  [0]:upgrade plan in details: https://docs.google.com/spreadsheets/d/1BEHR7kFxbnN4h2IN0O5tJS7WJlYaET7eoUiDtOmsOtE/edit#gid=568723700 [1] OPEN LPs on distro.openstack: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack [2] Ussuri schedule: https://releases.openstack.org/ussuri/schedule.html Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings Regards, Yong From ildiko.vancsa at gmail.com Tue Apr 21 07:23:02 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 21 Apr 2020 09:23:02 +0200 Subject: [Starlingx-discuss] Fwd: [OpenStack Foundation] Virtual OpenDev Update References: Message-ID: <4A1E58C4-D45C-461E-840C-49B8EC85FE70@gmail.com> Hi StarlingX Community, Please find some updates below about the upcoming virtual OpenDev event. Thanks, Ildikó > Begin forwarded message: > > From: Ashlee Ferguson > Subject: Re: [OpenStack Foundation] Virtual OpenDev Update > > Hi everyone, > > Welcome to the next stage of planning the virtual OpenDev events! These events are for the community, by the community, so we continue to need your help on the next step. > > Don’t know what OpenDev events[1] are? They are interactive discussions critical to the open source advancements addressing current challenges in cloud infrastructure. The goal of the virtual OpenDev events is the same as past OpenDev events: identify the questions we don’t yet have answers for, dive in and determine the work ahead of us, share use cases, and learn from other people asking those same questions. For this round, the community is tackling hardware automation, open infrastructure at scale, and containers. > > Now it’s your turn to influence the direction and future of open infrastructure. We want to know which topics are most critical to your team, organization, and environments. We also know that virtual events add a level of complexity since everyone is spread around the world, so we want to know what time zones work best for you. Please include any flexibility so we can accommodate as many global community members as possible. > > OpenDev will be organized as a three part series. First up: Large-scale Usage of Open Infrastructure Software. > > What are your next steps? > Visit this etherpad[2] and +1 the time zones you’re available and the topics you would like to cover - please provide your input by Thursday, April 23. > Add these dates to your calendar: June 29 - July 1 (Keep in mind, these will be 3 hour time blocks each day based on the timezone input received. We will send out calendar invitations once we determine the best time zone). > Stay updated via the landing page[1] where we will continue to post updates as well as registration information once it’s available. > > This is only the beginning! Keep the next dates[1] held tentatively for the other two rounds of OpenDev events. We will continue to update the mailing list as we have more information, but the OpenDev website is the best place to stay updated. > > Questions - let us know at events at openstack.org . > > Thanks! > Ashlee > > > [1] https://www.openstack.org/events/opendev-2020/ > [2]https://etherpad.opendev.org/p/OpenDev_LargeScaleUsage > > > Ashlee Ferguson > Community & Events Coordinator > OpenStack Foundation > >> On Mar 31, 2020, at 4:34 PM, Ashlee Ferguson > wrote: >> >> Hi everyone, >> >> As we continue to gather feedback and discuss what a virtual OpenDev will look like, we wanted to provide you with an update around the event. While we are still attempting to solve some of the riddles of virtual event world, we did come up with some decisions that give us something to build on, which are based on input and experience from members of the Programming Committee. >> >> Decisions: >> - OpenDev will happen after the Virtual PTG (exact format and timing TBD) >> - Will not be simultaneous/parallel Tracks so everyone has the opportunity to participate in more than one >> - 3 Tracks, each on different date: >> - Hardware Automation >> - Large Scale Ops >> - Containers in Production >> >> We also discussed the original intent and goals of OpenDev to make sure we’re still heading in a direction that’s beneficial for the community, especially since it will no longer directly precede the upcoming PTG. Similar to past OpenDev events, the goal is to identify the questions we don’t have the answers for, and to use that time to dive in and determine the work ahead of us, working together, sharing use cases, and learning from other people asking those same questions. >> >> High-level decisions, goals, and some areas we’re looking for feedback are in the etherpad below. As you continue to experience this new amazing world of virtual events, please add any feedback or ideas to the etherpad below. We’re looking forward to creating virtual OpenDev with you all! >> >> https://etherpad.openstack.org/p/Virtual_OpenDev_Planning >> >> Ashlee >> >> >> Ashlee Ferguson >> Community & Events Coordinator >> OpenStack Foundation >> >> _______________________________________________ >> > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From 18245043314 at 163.com Sun Apr 19 06:35:50 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Sun, 19 Apr 2020 14:35:50 +0800 (CST) Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> Message-ID: <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: puppet.log URL: From 18245043314 at 163.com Sun Apr 19 07:37:48 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Sun, 19 Apr 2020 15:37:48 +0800 (CST) Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> Message-ID: <2322c12f.768f.171915f3875.Coremail.18245043314@163.com> 4.9T is sda size. the "lsblk" on my startlingx looks like this: 在 2020-04-19 15:14:33,"Sun, Austin" 写道: is this 4.9T sda size or all disks size ? how much sda is ? Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 2:36 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To:starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 122302 bytes Desc: not available URL: From austin.sun at intel.com Sun Apr 19 08:01:31 2020 From: austin.sun at intel.com (Sun, Austin) Date: Sun, 19 Apr 2020 08:01:31 +0000 Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: <2322c12f.768f.171915f3875.Coremail.18245043314@163.com> References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> <2322c12f.768f.171915f3875.Coremail.18245043314@163.com> Message-ID: Sda is so big. rich man :) Get some search result from web [1] Would you like check the result via the command cat /sys/block/sda/device/../*/scsi_disk/*/max_write_same_blocks it is 0 in my setup . if it is 1 , you might change to 0 and try . disable write same like this: echo 0 | tee /sys/block/*/device/../*/scsi_disk/*/max_write_same_blocks (for the relevant backend devices) If you use LVM, you may need to vgchange -an ; vgchange -ay after that, (at least for the relevant VGs), if they have already been activated. [1] https://lists.linbit.com/pipermail/drbd-user/2017-February/023024.html Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 3:38 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal 4.9T is sda size. the "lsblk" on my startlingx looks like this: [cid:image001.png at 01D61663.B8251660] 在 2020-04-19 15:14:33,"Sun, Austin" > 写道: is this 4.9T sda size or all disks size ? how much sda is ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 2:36 PM To: Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" > wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 122302 bytes Desc: image001.png URL: From 18245043314 at 163.com Sun Apr 19 08:16:33 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Sun, 19 Apr 2020 16:16:33 +0800 (CST) Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal In-Reply-To: References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> <2322c12f.768f.171915f3875.Coremail.18245043314@163.com> Message-ID: <40bf40c6.7e49.1719182afdc.Coremail.18245043314@163.com> The machine belongs to my school. How rich a school it is! :-) I have tried that method. Without any change, the result of "cat /sys/block/sda/device/../*/scsi_disk/*/max_write_same_blocks" is already 0. BTW, the puppy log has some errors, but I think the most important one is listed below: =============================================== 2020-04-18T03:07:22.686 Error: 2020-04-18 03:07:22 +0000 drbdadm -- --assume-peer-has-space resize drbd-dockerdistribution returned 10 instead of one of [0] 2020-04-18T03:07:22.691 /usr/share/ruby/vendor_ruby/puppet/util/errors.rb:106:in `fail' 2020-04-18T03:07:22.696 /usr/share/ruby/vendor_ruby/puppet/type/exec.rb:160:in `sync' 2020-04-18T03:07:22.702 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `sync' 2020-04-18T03:07:22.709 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:134:in `sync_if_needed' 2020-04-18T03:07:22.715 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `block in perform_changes' 2020-04-18T03:07:22.721 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in `each' 2020-04-18T03:07:22.727 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in `perform_changes' 2020-04-18T03:07:22.732 /usr/share/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in `evaluate' 2020-04-18T03:07:22.739 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:230:in `apply' 2020-04-18T03:07:22.744 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:246:in `eval_resource' 2020-04-18T03:07:22.750 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:163:in `call' 2020-04-18T03:07:22.756 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:163:in `block (2 levels) in evaluate' 2020-04-18T03:07:22.761 /usr/share/ruby/vendor_ruby/puppet/util.rb:386:in `block in thinmark' 2020-04-18T03:07:22.768 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:07:22.774 /usr/share/ruby/vendor_ruby/puppet/util.rb:385:in `thinmark' 2020-04-18T03:07:22.781 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:163:in `block in evaluate' 2020-04-18T03:07:22.787 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse' 2020-04-18T03:07:22.792 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:07:22.799 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:07:22.806 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:07:22.812 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:07:22.818 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:07:22.824 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:07:22.830 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:07:22.837 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:07:22.843 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:07:22.850 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:07:22.855 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:07:22.861 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:07:22.867 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:07:22.874 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:07:22.880 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:07:22.887 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:07:22.893 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:07:22.900 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:07:22.906 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:07:22.912 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:07:22.918 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:07:22.923 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:07:22.929 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:07:22.935 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:07:22.941 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:07:22.946 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:07:22.952 /usr/bin/puppet:5:in `
' 2020-04-18T03:07:22.957 Error: 2020-04-18 03:07:22 +0000 /Stage[main]/Platform::Drbd::Dockerdistribution::Bootstrap/Platform::Drbd::Filesystem[drbd-dockerdistribution]/Exec[drbd resize drbd-dockerdistribution]/returns: change from notrun to 0 failed: drbdadm -- --assume-peer-has-space resize drbd-dockerdistribution returned 10 instead of one of [0] ====================================================== It seems that drbdadm doesn't work. And I am not sure what is Error 10 is. I wonder if you have some hints, 在 2020-04-19 16:01:31,"Sun, Austin" 写道: Sda is so big. rich man :) Get some search result from web [1] Would you like check the result via the command cat /sys/block/sda/device/../*/scsi_disk/*/max_write_same_blocks it is 0 in my setup . if it is 1 , you might change to 0 and try . disable write same like this: echo 0 | tee /sys/block/*/device/../*/scsi_disk/*/max_write_same_blocks (for the relevant backend devices) If you use LVM, you may need to vgchange -an ; vgchange -ay after that, (at least for the relevant VGs), if they have already been activated. [1] https://lists.linbit.com/pipermail/drbd-user/2017-February/023024.html Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 3:38 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re:RE: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal 4.9T is sda size. the "lsblk" on my startlingx looks like this: 在 2020-04-19 15:14:33,"Sun, Austin" 写道: is this 4.9T sda size or all disks size ? how much sda is ? Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Sunday, April 19, 2020 2:36 PM To: Sun, Austin Cc:starlingx-discuss at lists.starlingx.io Subject: Re:RE: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From:周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To:starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 122302 bytes Desc: not available URL: From 18245043314 at 163.com Mon Apr 20 03:13:09 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Mon, 20 Apr 2020 11:13:09 +0800 (CST) Subject: [Starlingx-discuss] problems with installing starlingx 3.0 in bare metal Message-ID: <371a57aa.69b2.171959345fa.Coremail.18245043314@163.com> Dear Sir: When installing starlingx in bare netal environement, It falls. When I search error in the puppet.log, There is a warning "resource 'drbd-platform' mentioned in 'resync-after' option is not known." showing serveral times, which leads to a process terminating. I just wonder whether this problem is the cause of the fail of installing. Do you have some hints? BTW, the attached is the whole puppet log file. yours zhou qingang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: puppet.log URL: From zhaos at neusoft.com Tue Apr 21 09:31:10 2020 From: zhaos at neusoft.com (zhaos at neusoft.com) Date: Tue, 21 Apr 2020 17:31:10 +0800 Subject: [Starlingx-discuss] =?gb2312?b?u9i4tDogIGVycm9yIHdoZW4gaW5zdGFs?= =?gb2312?b?bGluZyBzdGFybGluZ3gzLjAgYWxsLWluLW9uZQlpbiBiYXJlIG1l?= =?gb2312?b?dGFs?= In-Reply-To: <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> References: <251297f9.ad84.1718ceac1e5.Coremail.18245043314@163.com> <12458d76.6ad1.17191267b37.Coremail.18245043314@163.com> Message-ID: <002001d617bf$9e33b6f0$da9b24d0$@neusoft.com> Hi friend: I feel that the range of the oam_floating_address network segment you configured is inconsistent with the oam_subnet network segment. external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 <-- pay attention If you are in China, you need to build a Local registry and then configure it at localhost.yml: Example: docker_registries: k8s.gcr.io: url: gcr.io: url: quay.io: url: docker.io: url: docker.elastic.co: url: defaults: url: 192.168.3.102:5000 <--Need to change to your local IP secure: False 发件人: 周擎阳 <18245043314 at 163.com> 发送时间: 2020年4月19日 14:36 收件人: Sun, Austin 抄送: starlingx-discuss at lists.starlingx.io 主题: Re: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear Sir: 1.) I am installing in bare metal environment, funny thing is that the process works when I install it in virtual environment in the same machine. The memory is 250G and the disk is 4.9T. 2.) the localhost.yml is just the one in the guide. Here is the detail: =============================================================== system_mode: simplex dns_servers: - 8.8.8.8 - 8.8.4.4 external_oam_subnet: 172.16.0.0/16 external_oam_gateway_address: 172.16.0.1 external_oam_floating_address: 172.16.10.205 admin_username: admin admin_password: ASdf1234!@#$ ansible_become_pass: ASdf1234!@#$ # Add these lines to configure Docker to use a proxy server # docker_http_proxy: http://my.proxy.com:1080 # docker_https_proxy: https://my.proxy.com:1443 # docker_no_proxy: # - 1.2.3.4 =============================================================== 3.) For the log file is too long, I simply attach it to this email. For convenience I simply put the error part of the log file below: =============================================================== 2020-04-18T03:10:32.010 Error: 2020-04-18 03:10:32 +0000 Failed to apply catalog: Execution of '/usr/bin/openstack --os-interface internal role list --quiet --format csv' returned 1: Unable to establish connection to http://127.0.0.1:5000/v3/roles?: HTTPConnectionPool(host='127.0.0.1', port=5000): Max retries exceeded with url: /v3/roles (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 44, for a total of 170 seconds) 2020-04-18T03:10:32.017 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:126:in `rescue in block (2 levels) in request' 2020-04-18T03:10:32.021 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:88:in `block (2 levels) in request' 2020-04-18T03:10:32.026 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `loop' 2020-04-18T03:10:32.032 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:87:in `block in request' 2020-04-18T03:10:32.039 /usr/share/ruby/vendor_ruby/puppet/util.rb:128:in `withenv' 2020-04-18T03:10:32.043 /usr/share/openstack-puppet/modules/openstacklib/lib/puppet/provider/openstack.rb:82:in `request' 2020-04-18T03:10:32.049 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:325:in `request_by_service_token' 2020-04-18T03:10:32.055 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:258:in `rescue in request' 2020-04-18T03:10:32.061 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone.rb:254:in `request' 2020-04-18T03:10:32.067 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:51:in `instances' 2020-04-18T03:10:32.073 /usr/share/openstack-puppet/modules/keystone/lib/puppet/provider/keystone_role/openstack.rb:64:in `prefetch' 2020-04-18T03:10:32.079 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:323:in `prefetch' 2020-04-18T03:10:32.085 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:223:in `prefetch_if_necessary' 2020-04-18T03:10:32.091 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:107:in `block in evaluate' 2020-04-18T03:10:32.096 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `call' 2020-04-18T03:10:32.102 /usr/share/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:116:in `traverse' 2020-04-18T03:10:32.108 /usr/share/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' 2020-04-18T03:10:32.114 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' 2020-04-18T03:10:32.121 /usr/share/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' 2020-04-18T03:10:32.126 /usr/share/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' 2020-04-18T03:10:32.132 /usr/share/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' 2020-04-18T03:10:32.138 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' 2020-04-18T03:10:32.143 /usr/share/ruby/vendor_ruby/puppet/util.rb:223:in `block in benchmark' 2020-04-18T03:10:32.148 /usr/share/ruby/benchmark.rb:296:in `realtime' 2020-04-18T03:10:32.154 /usr/share/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 2020-04-18T03:10:32.160 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' 2020-04-18T03:10:32.166 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' 2020-04-18T03:10:32.171 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' 2020-04-18T03:10:32.176 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.182 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.188 /usr/share/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' 2020-04-18T03:10:32.193 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' 2020-04-18T03:10:32.199 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' 2020-04-18T03:10:32.204 /usr/share/ruby/vendor_ruby/puppet/context.rb:65:in `override' 2020-04-18T03:10:32.210 /usr/share/ruby/vendor_ruby/puppet.rb:241:in `override' 2020-04-18T03:10:32.216 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' 2020-04-18T03:10:32.222 /usr/share/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' 2020-04-18T03:10:32.229 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `block in run' 2020-04-18T03:10:32.234 /usr/share/ruby/vendor_ruby/puppet/util.rb:540:in `exit_on_fail' 2020-04-18T03:10:32.240 /usr/share/ruby/vendor_ruby/puppet/application.rb:344:in `run' 2020-04-18T03:10:32.246 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' 2020-04-18T03:10:32.251 /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' 2020-04-18T03:10:32.256 /usr/bin/puppet:5:in `
' ========================================================================================== thanks, yours, zhou qingyang. At 2020-04-19 13:36:53, "Sun, Austin" > wrote: Hi qingyang: Would you like to share some more info? 1) are u install in bare metal or virtual environment ? how much are memory and disk ? 2) could you provide localhost.yml you are using ? 3) provide /var/log/puppet/latest/puppet.log ? Thanks. BR Austin Sun. From: 周擎阳 <18245043314 at 163.com> Sent: Saturday, April 18, 2020 6:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] error when installing starlingx3.0 all-in-one in bare metal Dear sir: I am trying to install starlingx following the all-in-one link:https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex.html. However I stuck in the "ansible" step. From the dmesg, I can see the errors below: [79591.931815] block drbd0: Resize while not connected was forced by the user! [79592.058071] block drbd8: local WRITE IO error sector 1296+4088 on dm-8 [79592.058083] block drbd8: disk( UpToDate -> Failed ) [79592.058113] block drbd8: Local IO failed in __req_mod. Detaching... [79592.058146] block drbd8: IO ERROR: neither local nor remote data, sector 0+0 [79592.058178] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 [79592.061512] block drbd8: IO ERROR: neither local nor remote data, sector 5384+4096 [79592.061603] drbd8: WRITE SAME failed. Manually zeroing. [79592.061664] block drbd8: IO ERROR: neither local nor remote data, sector 5384+256 [79592.061764] block drbd8: IO ERROR: neither local nor remote data, sector 5640+256 [79592.061859] block drbd8: IO ERROR: neither local nor remote data, sector 5896+256 [79592.061880] block drbd8: helper command: /sbin/drbdadm pri-on-incon-degr minor-8 exit code 0 (0x0) [79592.061972] block drbd8: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79592.061988] block drbd8: disk( Failed -> Diskless ) [79592.835252] block drbd0: local WRITE IO error sector 2328+4080 on dm-3 [79592.835262] block drbd0: disk( UpToDate -> Failed ) [79592.835293] block drbd0: Local IO failed in __req_mod. Detaching... [79592.835369] drbd0: WRITE SAME failed. Manually zeroing. [79592.835388] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 [79592.838928] block drbd0: helper command: /sbin/drbdadm pri-on-incon-degr minor-0 exit code 0 (0x0) [79592.838970] block drbd0: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79592.838980] block drbd0: disk( Failed -> Diskless ) [79593.038394] EXT4-fs error (device drbd0): ext4_wait_block_bitmap:516: comm initdb: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79593.038541] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79593.038686] EXT4-fs warning (device drbd0): ext4_end_bio:302: I/O error -5 writing to inode 29 (offset 0 size 20480 starting block 65536) [79593.038689] Buffer I/O error on device drbd0, logical block 65536 [79593.038743] Buffer I/O error on device drbd0, logical block 65537 [79593.038805] Buffer I/O error on device drbd0, logical block 65538 [79593.038858] Buffer I/O error on device drbd0, logical block 65539 [79593.038911] Buffer I/O error on device drbd0, logical block 65540 [79595.501408] block drbd2: Resize while not connected was forced by the user! [79595.701486] EXT4-fs (drbd5): mounted filesystem with ordered data mode. Opts: (null) [79595.731488] EXT4-fs (drbd5): re-mounted. Opts: (null) [79595.755858] block drbd5: Resize while not connected was forced by the user! [79596.382427] EXT4-fs (drbd1): mounted filesystem with ordered data mode. Opts: (null) [79596.427131] EXT4-fs (drbd1): re-mounted. Opts: (null) [79596.456439] block drbd1: Resize while not connected was forced by the user! [79596.763258] block drbd1: local WRITE IO error sector 2320+4088 on dm-9 [79596.763270] block drbd1: disk( UpToDate -> Failed ) [79596.763304] block drbd1: Local IO failed in __req_mod. Detaching... [79596.763412] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 [79596.767304] block drbd1: helper command: /sbin/drbdadm pri-on-incon-degr minor-1 exit code 0 (0x0) [79596.767348] block drbd1: 2048 MB (524263 bits) marked out-of-sync by on disk bit-map. [79596.767358] block drbd1: disk( Failed -> Diskless ) [79596.788531] drbd1: WRITE SAME failed. Manually zeroing. [79597.168463] block drbd7: role( Secondary -> Primary ) disk( Inconsistent -> UpToDate ) [79597.179035] block drbd7: Forced to consider local data as UpToDate! [79597.179053] block drbd7: new current UUID 9759105C28A7AAAD:0000000000000004:0000000000000000:0000000000000000 [79597.616990] block drbd0: 52 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79597.616999] block drbd0: IO ERROR: neither local nor remote data, sector 1572864+8 [79597.617096] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617187] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.617274] Aborting journal on device drbd0-8. [79597.617328] Buffer I/O error on dev drbd0, logical block 196608, lost sync page write [79597.617417] JBD2: Error -5 detected when updating journal superblock for drbd0-8. [79597.680678] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.680772] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.680859] Aborting journal on device drbd8-8. [79597.680914] Buffer I/O error on dev drbd8, logical block 65536, lost sync page write [79597.681003] JBD2: Error -5 detected when updating journal superblock for drbd8-8. [79597.760212] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760337] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79597.760450] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [79597.760551] EXT4-fs (drbd0): Remounting filesystem read-only [79597.760620] EXT4-fs (drbd0): previous I/O error to superblock detected [79597.760682] Buffer I/O error on dev drbd0, logical block 0, lost sync page write [79600.177668] block drbd5: local WRITE IO error sector 1296+4088 on dm-2 [79600.177680] block drbd5: disk( UpToDate -> Failed ) [79600.177711] block drbd5: Local IO failed in __req_mod. Detaching... [79600.177786] drbd5: WRITE SAME failed. Manually zeroing. [79600.177813] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 [79600.181353] block drbd5: helper command: /sbin/drbdadm pri-on-incon-degr minor-5 exit code 0 (0x0) [79600.181396] block drbd5: 1024 MB (262127 bits) marked out-of-sync by on disk bit-map. [79600.181406] block drbd5: disk( Failed -> Diskless ) [79601.244660] EXT4-fs error (device drbd1): ext4_wait_block_bitmap:516: comm async_310: Cannot read block bitmap - block_group = 1, block_bitmap = 258 [79601.244825] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79601.244989] EXT4-fs warning (device drbd1): ext4_end_bio:302: I/O error -5 writing to inode 17 (offset 0 size 4096 starting block 65536) [79601.244994] Buffer I/O error on device drbd1, logical block 65536 [79601.607395] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607495] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79601.607582] Aborting journal on device drbd1-8. [79601.607638] Buffer I/O error on dev drbd1, logical block 196608, lost sync page write [79601.607727] JBD2: Error -5 detected when updating journal superblock for drbd1-8. [79602.351833] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.351905] block drbd1: 28 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [79602.351909] block drbd1: IO ERROR: neither local nor remote data, sector 0+8 [79602.351970] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79602.352063] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [79602.352159] EXT4-fs (drbd1): Remounting filesystem read-only [79602.352216] EXT4-fs (drbd1): previous I/O error to superblock detected [79602.352274] Buffer I/O error on dev drbd1, logical block 0, lost sync page write [79605.662600] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662694] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [79605.662781] Aborting journal on device drbd5-8. [79605.662836] Buffer I/O error on dev drbd5, logical block 65536, lost sync page write [79605.662924] JBD2: Error -5 detected when updating journal superblock for drbd5-8. [80656.347102] block drbd8: 3 messages suppressed in /builddir/build/BUILD/drbd-8.4.11-1/obj/default/drbd_req.c:1446. [80656.347111] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80656.347330] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80656.347372] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.347586] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80656.347798] EXT4-fs error (device drbd8): ext4_journal_check_start:56: Detected aborted journal [80656.348118] EXT4-fs (drbd8): Remounting filesystem read-only [80656.348130] EXT4-fs (drbd8): previous I/O error to superblock detected [80656.348135] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80656.348140] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80661.007923] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80661.008142] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80663.424845] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80663.425063] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80670.001525] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80670.001751] EXT4-fs warning (device drbd8): __ext4_read_dirblock:902: error reading directory block (ino 2, block 0) [80817.182038] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.182271] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.182529] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.182723] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.182956] Buffer I/O error on dev drbd8, logical block 0, lost sync page write [80817.186801] block drbd8: IO ERROR: neither local nor remote data, sector 1096+8 [80817.187036] EXT4-fs error (device drbd8): ext4_find_entry:1312: inode #2: comm sh: reading directory lblock 0 [80817.187271] EXT4-fs (drbd8): previous I/O error to superblock detected [80817.187457] block drbd8: IO ERROR: neither local nor remote data, sector 0+8 [80817.187648] Buffer I/O error on dev drbd8, logical block 0, lost sync page write I guess there are something wrong with drbd, but I am not sure about the problem. Do you have any ideas or do you need more information to solve it? Thanks. yours, zhou qingyang. --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Apr 21 14:02:31 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 21 Apr 2020 14:02:31 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 4/21/2020 Message-ID: Hi All: Agenda for 4/21 meeting: - ceph containerization - kernel upgrade : - centos8 upgrade: - python3 - pbr version Thanks. BR Austin Sun. From 18245043314 at 163.com Tue Apr 21 14:25:55 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Tue, 21 Apr 2020 22:25:55 +0800 (CST) Subject: [Starlingx-discuss] questions about stx disks. Message-ID: <66cebd92.ebbc.1719d2191c5.Coremail.18245043314@163.com> Dear sir: I just read the all-in-one bare metal installing guide "https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html", and also I have 3 questions. 1.) the "Primary disk" part says that we need 500G SDD, does that misspell with SSD? 2.) Can just a simple 500G HDD work? 3.) Now I just have one huge disk which is 5TB, can I install stx on that? Do I have to modify sth or Can I just do partition after installing the bootimage? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Apr 21 14:44:01 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 21 Apr 2020 07:44:01 -0700 Subject: [Starlingx-discuss] nominate several core reviewers on 3 STX projects In-Reply-To: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> References: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> Message-ID: <9f44a045-f13f-00cb-4ffd-50eb865b84c6@linux.intel.com> Agreed, let's close on this in the Distro meeting tomorrow. Sau! On 4/16/20 7:06 PM, Hu, Yong wrote: > Hi cores, > > I would like to nominate these guys as core reviewers in following project: > > 1. project:starlingx/integ:   Sun, Austin austin.sun at intel.com > > 2. project:starlingx/kernel:  Lin, Shuicheng shuicheng.lin at intel.com > > 3. project:starlingx/docs: Wang, Yi C yi.c.wang at intel.com > > > These 3 guys have been working on StarlingX since 2018 March, and they > contributed considerate number of patches for features, integrations and > bug fixes. > > Upgrading them to core reviewers will enable them to contribute more on > StarlingX and have better coverage on the patch review in Asian time zone. > > So, please let us know your feedback. Thanks! > > Regards, > > Yong > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From ruediger.stock at intel.com Tue Apr 21 15:50:36 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Tue, 21 Apr 2020 15:50:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Message-ID: Sanity Test from 2020-April-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200420T230011Z/outputs/iso/) Status: RED =========================================== All setups were struck by https://bugs.launchpad.net/starlingx/+bug/1874106 during initial installation of the cluster. The issue seen is similar to https://bugs.launchpad.net/starlingx/+bug/1873884 but not identical. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Apr 21 17:01:19 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 21 Apr 2020 17:01:19 +0000 Subject: [Starlingx-discuss] questions about stx disks. In-Reply-To: <66cebd92.ebbc.1719d2191c5.Coremail.18245043314@163.com> References: <66cebd92.ebbc.1719d2191c5.Coremail.18245043314@163.com> Message-ID: <9A85D2917C58154C960D95352B22818B01080ACBDB@fmsmsx123.amr.corp.intel.com> 1) Looks like you found a typo in our docs, sorry about that. We’ll fix it. 2) Yes, HDD’s will work but SSD’s are faster. 3) The 500G is a recommended minimum. More is always better :) From: 周擎阳 [mailto:18245043314 at 163.com] Sent: Tuesday, April 21, 2020 7:26 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] questions about stx disks. Dear sir: I just read the all-in-one bare metal installing guide "https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html", and also I have 3 questions. 1.) the "Primary disk" part says that we need 500G SDD, does that misspell with SSD? 2.) Can just a simple 500G HDD work? 3.) Now I just have one huge disk which is 5TB, can I install stx on that? Do I have to modify sth or Can I just do partition after installing the bootimage? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Apr 21 21:28:17 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 21 Apr 2020 14:28:17 -0700 Subject: [Starlingx-discuss] Adding Bandit to additional repos and packages Message-ID: Flock Folks, Sorry I missed the Flock meeting this morning, I would like to discuss this in the community meeting if we have time. We are working to add bandit[0] (the python static scanner), running it over all python. Sharath is starting with adding a general zuul project template [1] that will be available to all StarlingX repos. An example of it's usage is in fault [2]. As Al pointed out in the initial (now abandoned) config review, we are running bandit in sysinv. I would like to know what the history of having tox.ini in the lower directories is. As we want to run bandit on all the python code in config and other repos. Is this something we can undo and move up? Also, are we tracking someplace when we move something to the skip category? I see that most of the High issues are currently being skipped. If we are skipping known issues, can we use the baseline feature somehow to catch potential new issues? Thanks Sau! [0] https://github.com/PyCQA/bandit [1] https://review.opendev.org/#/c/721294/ [2] https://review.opendev.org/#/c/721307/ From Bill.Zvonar at windriver.com Tue Apr 21 23:46:18 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 21 Apr 2020 23:46:18 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 22, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand - the following items are on the agenda now: - Core Reviewer Nominations - Maintenance Releases for stx.2.0 & stx.3.0 - Running Sanity in the Open - Adding Bandit to additional repos and packages 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=20200422T1400 From zhipengs.liu at intel.com Wed Apr 22 03:17:21 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 22 Apr 2020 03:17:21 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 In-Reply-To: References: Message-ID: Hi all, >From log, it failed to extract tarball during openstack apply I have checked change log. It may be related to below merge /cgcs-root/stx/nginx-ingress-controller-armada-app d1d2cd3326dbc13d0260e292000138d6181ec8c8 2020-04-17 11:04:29 -0400 Sabeel Ansari Sabeel.Ansari at windriver.com Initial commit of nginx-ingress-controller app https://review.opendev.org/#/c/718457/ @ Sabeel Ansari, could you help to double check it. Thanks! Zhipeng From: Stock, Ruediger Sent: 2020年4月21日 23:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Sanity Test from 2020-April-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200420T230011Z/outputs/iso/) Status: RED =========================================== All setups were struck by https://bugs.launchpad.net/starlingx/+bug/1874106 during initial installation of the cluster. The issue seen is similar to https://bugs.launchpad.net/starlingx/+bug/1873884 but not identical. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Wed Apr 22 03:24:20 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 21 Apr 2020 20:24:20 -0700 Subject: [Starlingx-discuss] enable pbr version In-Reply-To: <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> Message-ID: <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> Hi Again Yipeng, I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. Sau! [0] https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_Non-OpenStack_Team_Call On 4/14/20 9:42 AM, Saul Wold wrote: > Yipeng, > > I hope you can join the Distro meeting in your evening tomorrow and we > can disuses this issue. > > Thanks > >   Sau! > > > On 4/13/20 10:13 PM, Saul Wold wrote: >> Can you please provide more details about what you did and how you >> tried to create the ISO? >> >> The information here is not very helpful.  Maybe the community members >> in China can help you get the build to work correctly. >> >> Sau! >> >> >> On 4/13/20 7:43 PM, 何义鹏 wrote: >>> >>> Hi Saul, >>> >>> I'm sorry it took so long to recover your mail. >>> >>> Recently, there was a problem when I modified according to the method >>> you provided under patch. >>> I tried to change all the versions in the patch of >>> starlingx-starboard to pbr_version. >>> But the result still failed to build iso. >>> >>> yipeng.he! >>> ------------------ Original ------------------ >>> *From: * "Saul Wold"; >>> *Date: * Wed, Apr 8, 2020 02:58 AM >>> *To: * "starlingx-discuss"; "何 >>> 义 鹏"; >>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>> >>> Hi Yipeng, >>> >>> Sorry for the delay in getting back to you, I was looking into the build >>> failure and trying understand how we handle the difference between the >>> PBR SemVer [0] and PEP440 [1]. Specifically when there is a "Pre" tag >>> like rc0, b1 such as 4.0.0.rc0. When PEP440 normalizes that semver tag >>> to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>> >>> So we need to also change the spec files %files section for the egg-info >>> file to wild-card that file instead of having a specific version listed. >>> >>> For example in the starlingx-dashboard spec file: >>> >>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>> index 7fbee65..399a9bd 100644 >>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>>    %files >>>    %{python2_sitelib}/%{py_pkg_name} >>> >>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>> >>>    %{enabled_dir} >>>    %{stx_themes_dir} >>> >>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>> feature" in the commit message, just once per repo. See Bin's pending >>> commit in fault [2]. You will have to back and fix fault and other >>> pending commits with the wild-card change for the egg-info file in the >>> spec file. >>> >>> Finally all PBR related reviews should have a >>> Depends-On: https://review.opendev.org/#/c/691632/ >>> >>> So it does not get merged before the enabling code in the build tools >>> merges. >>> >>> Hope this clarifies things and gets the PBR work unblocked. I am going >>> through the reviews and trying to provide some additional review >>> comments. >>> We can also talk about this tomorrow during the Distro call [3] >>> >>> Sau! >>> >>> >>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>> [1] https://www.python.org/dev/peps/pep-0440/ >>> [2] https://review.opendev.org/#/c/691647/ >>> [3] >>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>>  > >>>  >   Saul! >>>  > >>>  > Thank you for your answer! But how should I use the semMem-ver tag? >>>  > ------------------ Original ------------------ >>>  > *From: * "Saul Wold"; >>>  > *Date: * Sat, Mar 28, 2020 07:02 AM >>>  > *To: * "何义鹏"; "Penney, >>>  > Don"; "Scott >>>  > Little"; "Miller, >>>  > Frank"; >>>  > *Cc: * "曹明晓"; "杨永金" >>>  > ; "桂来军"; >>>  > "starlingx-discuss"; >>>  > *Subject: * Re: [Starlingx-discuss] enable pbr version >>>  > Yipeng, >>>  > >>>  > >>>  > I replied the other day, wanting to confirm if you have any >>> additional >>>  > changes in your local git repo? It seems that we need to consider a >>>  > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>>  > feature" tag in a commit to move the pbr versioning forward. >>>  > >>>  > BUILD Team (Don, Scott, Frank): >>>  > >>>  > Here's the general issue, we tag on the release branches, not master >>>  > (although we have a v3.0.0.rc0 tag on master), we need to either >>> add a >>>  > Sem_Ver: feature tag to increment version's major number, or add a >>>  > pre-tag of the 4.0 release. >>>  > >>>  > Thoughts from the build team?  I think we discussed part of the >>> before, >>>  > but want to do a quick revisit of the thread back in Nov [1], I >>> think we >>>  > had agreed to use Sem_Ver but it's not in the email thread >>>  > >>>  > >>>  > [0] >>>  > >>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006790.html >>> >>>  > >>>  > >>>  > On 3/26/20 7:26 PM, 何义鹏 wrote: >>>  >  > >>>  >  > Yes, building the rpm of the starlingx dashboard is a necessary >>> step for >>>  >  > my build-iso. >>>  >  > >>>  >  > Maybe Saul can respond to the question that python builds allow >>> several >>>  >  > versions of components. >>>  >  > >>>  > Jeremy replied to this earlier in the week, the issue appears to >>> be the >>>  > way we tagged rc0, we might need to have change our tagging.  He also >>>  > stated that the number of components is not a limiting factor. >>>  > >>>  > Sau! >>>  >  > ------------------ Original ------------------ >>>  >  > *From: * "Penney, Don"; >>>  >  > *Date: * Wed, Mar 25, 2020 10:11 PM >>>  >  > *To: * "何义鹏"; "Saul >>>  >  > Wold(sgw at linux.intel.com)"; >>>  >  > *Cc: >>>  >  > >>>  > >>> * "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.starlingx.io)"; >>> >>>  > >>>  >  > >>>  >  > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>>  >  > >>>  >  > Please keep starlingx-discuss on the receiver list. >>>  >  > >>>  >  > You had indicated build-iso was failing, but the build.log you >>> provided >>>  >  > appears to be the RPM build log for starlingx-dashboard. >>>  >  > >>>  >  > Processing files: >>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>>  >  > >>>  >  > error: File not found: >>>  >  > >>>  > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info >>> >>>  >  > >>>  >  > RPM build errors: >>>  >  > >>>  >  >      File not found: >>>  >  > >>>  > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9999.9999.rc1.dev23*.egg-info >>> >>>  >  > >>>  >  > Child return code was: 1 >>>  >  > >>>  >  > EXCEPTION: [Error()] >>>  >  > >>>  >  > Traceback (most recent call last): >>>  >  > >>>  >  >    File >>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>>  >  > line 95, in trace >>>  >  > >>>  >  >      result = func(*args, **kw) >>>  >  > >>>  >  >    File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>> line 746, >>>  >  > in do_with_status >>>  >  > >>>  >  >      raise exception.Error("Command failed: \n # %s\n%s" % >>> (command, >>>  >  > output), child.returncode) >>>  >  > >>>  >  > mockbuild.exception.Error: Command failed: >>>  >  > >>>  >  >   # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps >>>  >  > /builddir/build/SPECS/starlingx-dashboard.spec >>>  >  > >>>  >  > Looking through the build.log, I see the following: >>>  >  > >>>  >  > Copying starlingx_dashboard.egg-info to >>>  >  > >>>  > >>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.dev23-py2.7.egg-info >>> >>>  >  > >>>  >  > So in the build, it’s creating the egg with the version set to >>>  >  > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>>  >  > 2.9999.9999.rc1.dev23. >>>  >  > >>>  >  > Looking further through the build.log, there’s the following: >>>  >  > >>>  >  > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>>  >  > >>>  > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.x86_64 >>> >>>  >  > >>>  >  > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>> UserWarning: >>>  >  > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>>  >  > >>>  >  >    normalized_version, >>>  >  > >>>  >  > running install >>>  >  > >>>  >  > Maybe the python build only allows 4 version components? >>>  >  > >>>  >  > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>>  >  > *Sent:* Tuesday, March 24, 2020 9:59 PM >>>  >  > *To:* Penney, Don >>>  >  > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>>  >  > >>>  >  > Hi Saul, >>>  >  > >>>  >  > I added the error log to the attachment. Do you need other >>> files for >>>  >  > analysis? >>>  >  > >>>  >  > Thank you for your help. >>>  >  > >>>  >  >     yipeng.he! >>>  >  > >>>  >  > ------------------ Original ------------------ >>>  >  > >>>  >  > *From: * "Penney, Don"; >>>  >  > >>>  >  > *Date: * Wed, Mar 25, 2020 04:24 AM >>>  >  > >>>  >  > *To: * "Saul Wold"; "何义鹏" >>>  > ; >>>  >  > >>>  >  > *Cc: * "桂来军"; "杨永金" >>>  >  > ; "曹明晓"; >>>  >  > "starlingx-discuss"; >>>  >  > >>>  >  > *Subject: * RE: [Starlingx-discuss] enable pbr version >>>  >  > >>>  >  > Hi Yipeng, >>>  >  > >>>  >  > Can you provide more info? What was the error you saw from >>> build-iso? >>>  >  > >>>  >  > >>>  >  > -----Original Message----- >>>  >  > From: Saul Wold [mailto:sgw at linux.intel.com] >>>  >  > Sent: Monday, March 23, 2020 6:45 PM >>>  >  > To: 何义鹏 >>>  >  > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>>  >  > Subject: Re: [Starlingx-discuss] enable pbr version >>>  >  > >>>  >  > >>>  >  > Hi Yipeng, >>>  >  > >>>  >  > I was out last week on vacation, so I am catching up now. >>>  >  > >>>  >  > I think you would have to investigate build-iso and associated >>> scripts >>>  >  > and tools to see if there is an awk, sed or some other command >>> that is >>>  >  > not parsing the extended version.  I have not investigated this >>> further, >>>  >  > that's my initial assessment. >>>  >  > >>>  >  > Can you be more specific about what the error is or provide a >>> log file >>>  >  > of the build-iso process? >>>  >  > >>>  >  > Thanks for working on this project. >>>  >  > >>>  >  >    Sau! >>>  >  > >>>  >  > >>>  >  > >>>  >  > On 3/19/20 12:21 AM, 何义鹏wrote: >>>  >  >> Hello Saul >>>  >  >> >>>  >  >> I'm Yipeng He from JITStack, and I'm taking over the tasks of >>> PBR. >>>  >  >> I encountered the following issue when trying to build iso: >>>  >  >> It fails when the suffix of the version generated by the PBR >>> tool ended >>>  >  >> with number, for instance the building fails if the version id is >>>  >  >> 2.999.9999.rc1.dev23, >>>  >  >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>> building was >>>  >  >> successful. >>>  >  >> I don't knwo why this happens, could please support and advice >>> the >>>  >  >> solution for this issue. >>>  >  >> >>>  >  >> >>>  >  >> Yipeng.He >>>  >  >> >>>  >  >> _______________________________________________ >>>  >  >> 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 >>>  > >>> >>> _______________________________________________ >>> 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 Wed Apr 22 03:55:36 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 22 Apr 2020 03:55:36 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 In-Reply-To: References: Message-ID: The patch https://review.opendev.org/721286 in LP 1873884 should fix this issue. Zhipeng From: Liu, ZhipengS Sent: 2020年4月22日 11:17 To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Hu, Yong Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Hi all, >From log, it failed to extract tarball during openstack apply I have checked change log. It may be related to below merge /cgcs-root/stx/nginx-ingress-controller-armada-app d1d2cd3326dbc13d0260e292000138d6181ec8c8 2020-04-17 11:04:29 -0400 Sabeel Ansari Sabeel.Ansari at windriver.com Initial commit of nginx-ingress-controller app https://review.opendev.org/#/c/718457/ @ Sabeel Ansari, could you help to double check it. Thanks! Zhipeng From: Stock, Ruediger > Sent: 2020年4月21日 23:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Sanity Test from 2020-April-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200420T230011Z/outputs/iso/) Status: RED =========================================== All setups were struck by https://bugs.launchpad.net/starlingx/+bug/1874106 during initial installation of the cluster. The issue seen is similar to https://bugs.launchpad.net/starlingx/+bug/1873884 but not identical. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruediger.stock at intel.com Wed Apr 22 05:40:35 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Wed, 22 Apr 2020 05:40:35 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 In-Reply-To: References: Message-ID: Hello Zhipeng, this change is expected to be contained in todays builds by cengn, right? For the builds started yesterday the merge came in to late. Regards, Rüdiger From: Liu, ZhipengS Sent: Wednesday, April 22, 2020 5:56 AM To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Hu, Yong Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 The patch https://review.opendev.org/721286 in LP 1873884 should fix this issue. Zhipeng From: Liu, ZhipengS > Sent: 2020年4月22日 11:17 To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada >; Hu, Yong > Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Hi all, From log, it failed to extract tarball during openstack apply I have checked change log. It may be related to below merge /cgcs-root/stx/nginx-ingress-controller-armada-app d1d2cd3326dbc13d0260e292000138d6181ec8c8 2020-04-17 11:04:29 -0400 Sabeel Ansari Sabeel.Ansari at windriver.com Initial commit of nginx-ingress-controller app https://review.opendev.org/#/c/718457/ @ Sabeel Ansari, could you help to double check it. Thanks! Zhipeng From: Stock, Ruediger > Sent: 2020年4月21日 23:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Sanity Test from 2020-April-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200420T230011Z/outputs/iso/) Status: RED =========================================== All setups were struck by https://bugs.launchpad.net/starlingx/+bug/1874106 during initial installation of the cluster. The issue seen is similar to https://bugs.launchpad.net/starlingx/+bug/1873884 but not identical. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Apr 22 05:43:51 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 22 Apr 2020 05:43:51 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 In-Reply-To: References: Message-ID: Hi Ruediger, It is in below build. FYI. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200422T013012Z/outputs/CHANGELOG.txt ./cgcs-root 1a0484eecc2c0eab0dc05950469ef7c1723af48a 2020-04-20 12:14:16 -0400 Scott Little scott.little at windriver.com find_chartfile returns multiple erroneous files Thanks! Zhipeng From: Stock, Ruediger Sent: 2020年4月22日 13:41 To: Liu, ZhipengS ; Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada ; Hu, Yong Subject: RE: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Hello Zhipeng, this change is expected to be contained in todays builds by cengn, right? For the builds started yesterday the merge came in to late. Regards, Rüdiger From: Liu, ZhipengS > Sent: Wednesday, April 22, 2020 5:56 AM To: Liu, ZhipengS >; starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada >; Hu, Yong > Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 The patch https://review.opendev.org/721286 in LP 1873884 should fix this issue. Zhipeng From: Liu, ZhipengS > Sent: 2020年4月22日 11:17 To: starlingx-discuss at lists.starlingx.io Cc: Khalil, Ghada >; Hu, Yong > Subject: Re: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Hi all, From log, it failed to extract tarball during openstack apply I have checked change log. It may be related to below merge /cgcs-root/stx/nginx-ingress-controller-armada-app d1d2cd3326dbc13d0260e292000138d6181ec8c8 2020-04-17 11:04:29 -0400 Sabeel Ansari Sabeel.Ansari at windriver.com Initial commit of nginx-ingress-controller app https://review.opendev.org/#/c/718457/ @ Sabeel Ansari, could you help to double check it. Thanks! Zhipeng From: Stock, Ruediger > Sent: 2020年4月21日 23:51 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200421 Sanity Test from 2020-April-21 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200420T230011Z/outputs/iso/) Status: RED =========================================== All setups were struck by https://bugs.launchpad.net/starlingx/+bug/1874106 during initial installation of the cluster. The issue seen is similar to https://bugs.launchpad.net/starlingx/+bug/1873884 but not identical. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From 18245043314 at 163.com Wed Apr 22 07:32:31 2020 From: 18245043314 at 163.com (=?GBK?B?1tzH5tH0?=) Date: Wed, 22 Apr 2020 15:32:31 +0800 (CST) Subject: [Starlingx-discuss] can one huge disk work? Message-ID: <3ab11d56.9875.171a0cd74e9.Coremail.18245043314@163.com> Dear sir: In the installing guide "https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html", I find stx need a least 2 disks, but now that I have only one disk with 5TB, can I install stx on that single disk? -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Apr 22 07:38:34 2020 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 22 Apr 2020 07:38:34 +0000 Subject: [Starlingx-discuss] can one huge disk work? In-Reply-To: <3ab11d56.9875.171a0cd74e9.Coremail.18245043314@163.com> References: <3ab11d56.9875.171a0cd74e9.Coremail.18245043314@163.com> Message-ID: No, we need at least 2 hard disks. One is for system partition and another is for data partition. From: 周擎阳 <18245043314 at 163.com> Date: Wednesday, April 22, 2020 at 3:34 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] can one huge disk work? Dear sir: In the installing guide "https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html", I find stx need a least 2 disks, but now that I have only one disk with 5TB, can I install stx on that single disk? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Wed Apr 22 13:05:00 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 22 Apr 2020 13:05:00 +0000 Subject: [Starlingx-discuss] Adding Bandit to additional repos and packages In-Reply-To: References: Message-ID: For someting like sysinv, ideally it would have been in its own repo, but in order to get zuul to run pep8/pylint settings that are different from other python modules in the same repo, we needed to structure the zuul and tox.ini files that way. This allowed us to gradually increase the strictness of the checks in each component without breaking other zuul checks for other pieces in the same repo. It also allows us to scope the zuul jobs, so that a change in sysinv does not always run an unrelated zuul check against something else in the same repo (ie: cgtsclient) Note: There is both a [testest:pep8] section and a [flake8] section in the tox.ini files. which allows a job to have a unified target and the component to have a customized settting. Likely we would have a [testest:bandit] which is what the zuul job would run, and a [bandit] section to allow per repo settings to be adjusted and improved over time. Al ________________________________ From: Saul Wold Sent: Tuesday, April 21, 2020 5:28 PM To: starlingx-discuss at lists.starlingx.io ; Kumar, Sharath ; Bailey, Henry Albert (Al) Subject: Adding Bandit to additional repos and packages Flock Folks, Sorry I missed the Flock meeting this morning, I would like to discuss this in the community meeting if we have time. We are working to add bandit[0] (the python static scanner), running it over all python. Sharath is starting with adding a general zuul project template [1] that will be available to all StarlingX repos. An example of it's usage is in fault [2]. As Al pointed out in the initial (now abandoned) config review, we are running bandit in sysinv. I would like to know what the history of having tox.ini in the lower directories is. As we want to run bandit on all the python code in config and other repos. Is this something we can undo and move up? Also, are we tracking someplace when we move something to the skip category? I see that most of the High issues are currently being skipped. If we are skipping known issues, can we use the baseline feature somehow to catch potential new issues? Thanks Sau! [0] https://github.com/PyCQA/bandit [1] https://review.opendev.org/#/c/721294/ [2] https://review.opendev.org/#/c/721307/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Apr 22 15:06:15 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 22 Apr 2020 15:06:15 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 22, 2020) In-Reply-To: References: Message-ID: >From today's meeting... * Standing Topics * Sanity * Monolithic * 20200415 Red * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008306.html * will queue this up to discuss next week, re: RCA * 20200416 Red * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008320.html * related to Kubernetes 1.18? * ditto re: RCA next week * 20200417 Green * 20200421 Red * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008365.html * due to build tool change - this has been fixed, it's in today's build * Layered * 20200418 Green * no other sanities since last week * feels like we're closing to being able to cut over to Layered Builds as default - target is to do this week (Thu) * Gerrit Reviews in Need of Attention * ceph containerization https://review.opendev.org/#/c/716792/ https://review.opendev.org/#/c/721443/ https://review.opendev.org/#/c/714857/ https://review.opendev.org/#/c/713084/ https://review.opendev.org/#/c/721785/ https://review.opendev.org/#/c/720637/ https://review.opendev.org/#/c/721765/ * Saul provided a gentle reminder to the cores to review their queues at least once daily * Don suggested sending this gentle reminder to the discuss list - AR: Bill * CentOS 8 Kernel Upgrade Plan * sanity ran ok with kernel in new repo * working to adopot the pre-built srpm, might be at risk for end of month, but still going for it * Topics for this Week * Core Reviewer Nominations: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008328.html * all 3 approved * Saul will update the core reviewers files (and remove any lingering GDC names) * Maintenance Releases for stx.2.0 & stx.3.0 -- Bruce & Ghada * A # of fixes were sourced in the branches. Test teams are resource constrained to test mtce releases. * Is there a need in the community to release these mtce releases? Any timeline requests? * no comments here - Ghada will send the question out on the mailing list * Running Sanity in the Open - minimum requirements * 1 VM for Simplex * bootable via PXE or other network boot protocols from a Cengn binary - if physical machine * for VM, provide a QCOW2 image - need to sort out how frequently we do this & what config - more to discuss * Bill to follow up * Adding Bandit to additional repos and packages: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008367.html * didn't get to this this week, Saul will follow up on mailing list, will put it on next week's agenda if required * ARs from Previous Meetings * 4/15 * layered build - validating docker images (Scott/Nic) - to be discussed in Build meeting tomorrow * manually updating version info (Build team + Bart) * home for pre-built srpms (Scott, Austin) * Open Requests for Help * problems with installing starlingx 3.0 in bare metal: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008360.html -----Original Message----- From: Zvonar, Bill Sent: Tuesday, April 21, 2020 7:46 PM To: starlingx-discuss at lists.starlingx.io Subject: Community (& TSC) Call (Apr 22, 2020) Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand - the following items are on the agenda now: - Core Reviewer Nominations - Maintenance Releases for stx.2.0 & stx.3.0 - Running Sanity in the Open - Adding Bandit to additional repos and packages 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=20200422T1400 From yang.liu at windriver.com Tue Apr 21 15:42:11 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Tue, 21 Apr 2020 15:42:11 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 04/21/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 04/21/2020 Attendees: Yang, Cosmin, Chris, Nicolae, Bernd, George, Ruediger · Sanity Status: * https://bugs.launchpad.net/starlingx/+bug/1873933 - After system initial, some pods stays at NodeAffinity status § Suggest sanity folks to check this manually * https://bugs.launchpad.net/neutron/+bug/1870569 - Unable to create network without default network_segment_range § Command failed: openstack network create --project --provider-network-type=vlan --provider-physical-network= --share * stx-openstack failed to apply - LP on the way § May be similar to 1873884 · stx4.0 testing * Feature testing: § https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 § Centos8: · Used a designer load provided Yong. · No baremetal sx/dx yet, cannot check TPM/CX4/5 related test cases. · Making progress in setting up sx - still seeing error. § Upversion Openstack services used by flock components on host: · Got eng load o Executed robot sanity and barbican test cases and results were okay o ETA to complete testing on eng load: May 1st § Upgrade Containerized OpenStack to Ussuri · Yong's team may provide eng load by end of week § Windows Active directory in progress · Running on Distributed Cloud § Red fish virtual media support in progress · Completing soon. ETA: May1st week. § Kubernetes Upgrade Support in progress · ETA: End of May1st week * Regression testing: § Starting in mid-May. Will pull in test cases. § Nic: Some risk in setting up baremetal servers. · Simplex is done - waiting for green load to confirm. Took 3-4 days to configure and update. · Duplex will be started on Apr 22. · Open topic * Test in the open: § Bill sent out email to OpenDev guys - need feedback on config · Suggest to start with simplex in virtual · Need to ask how OpenDev does test in the open with virtual on virtual o Nic's team will try virtual on virtual to experiment -------------- next part -------------- An HTML attachment was scrubbed... URL: From cherish.cao at jitstack.com Wed Apr 22 16:13:07 2020 From: cherish.cao at jitstack.com (cherish.cao at jitstack.com) Date: Thu, 23 Apr 2020 00:13:07 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiAgZW5hYmxlIHBiciB2ZXJz?= =?utf-8?q?ion?= In-Reply-To: <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> Message-ID: <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com>+7DBCED111C73F24E Hi Saul: We have solved some problems related to PBR and submitted relevant codes. Due to Yipeng's limited proficiency of English, he handles the mails slowly. I'm sorry about that. JITStack will continue to invest in PBR-related patches, please don't worry. After that, I've organized a team for the work related to PBR and ChornXie(chron.xie at jitstack.com) will join us in order to assist Yipeng to promote the work. Sorry again for the confusion. In addition, do you have instant messaging software,like Wechat or something, I think this may speed up the promotion of PBR. Thanks Cherish.Cao -----邮件原件----- 发件人: Saul Wold 发送时间: 2020年4月22日 11:24 收件人: 何义鹏 抄送: 曹明晓 ; 桂来军 ; starlingx-discuss 主题: Re: [Starlingx-discuss] enable pbr version Hi Again Yipeng, I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. Sau! [0] https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_Non-OpenStack_Team_Call On 4/14/20 9:42 AM, Saul Wold wrote: > Yipeng, > > I hope you can join the Distro meeting in your evening tomorrow and we > can disuses this issue. > > Thanks > > Sau! > > > On 4/13/20 10:13 PM, Saul Wold wrote: >> Can you please provide more details about what you did and how you >> tried to create the ISO? >> >> The information here is not very helpful. Maybe the community >> members in China can help you get the build to work correctly. >> >> Sau! >> >> >> On 4/13/20 7:43 PM, 何义鹏 wrote: >>> >>> Hi Saul, >>> >>> I'm sorry it took so long to recover your mail. >>> >>> Recently, there was a problem when I modified according to the >>> method you provided under patch. >>> I tried to change all the versions in the patch of >>> starlingx-starboard to pbr_version. >>> But the result still failed to build iso. >>> >>> yipeng.he! >>> ------------------ Original ------------------ >>> *From: * "Saul Wold"; >>> *Date: * Wed, Apr 8, 2020 02:58 AM >>> *To: * "starlingx-discuss"; "何 >>> 义 鹏"; >>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>> >>> Hi Yipeng, >>> >>> Sorry for the delay in getting back to you, I was looking into the >>> build failure and trying understand how we handle the difference >>> between the PBR SemVer [0] and PEP440 [1]. Specifically when there >>> is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 >>> normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>> >>> So we need to also change the spec files %files section for the >>> egg-info file to wild-card that file instead of having a specific version listed. >>> >>> For example in the starlingx-dashboard spec file: >>> >>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>> index 7fbee65..399a9bd 100644 >>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>> %files >>> %{python2_sitelib}/%{py_pkg_name} >>> >>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>> >>> %{enabled_dir} >>> %{stx_themes_dir} >>> >>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>> feature" in the commit message, just once per repo. See Bin's >>> pending commit in fault [2]. You will have to back and fix fault and >>> other pending commits with the wild-card change for the egg-info >>> file in the spec file. >>> >>> Finally all PBR related reviews should have a >>> Depends-On: https://review.opendev.org/#/c/691632/ >>> >>> So it does not get merged before the enabling code in the build >>> tools merges. >>> >>> Hope this clarifies things and gets the PBR work unblocked. I am >>> going through the reviews and trying to provide some additional >>> review comments. >>> We can also talk about this tomorrow during the Distro call [3] >>> >>> Sau! >>> >>> >>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>> [1] https://www.python.org/dev/peps/pep-0440/ >>> [2] https://review.opendev.org/#/c/691647/ >>> [3] >>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>> > >>> > Saul! >>> > >>> > Thank you for your answer! But how should I use the semMem-ver tag? >>> > ------------------ Original ------------------ >>> > *From: * "Saul Wold"; >>> > *Date: * Sat, Mar 28, 2020 07:02 AM >>> > *To: * "何义鹏"; "Penney, >>> > Don"; "Scott >>> > Little"; "Miller, >>> > Frank"; >>> > *Cc: * "曹明晓"; "杨永金" >>> > ; "桂来军"; >>> > "starlingx-discuss"; >>> > *Subject: * Re: [Starlingx-discuss] enable pbr version >>> > Yipeng, >>> > >>> > >>> > I replied the other day, wanting to confirm if you have any >>> additional >>> > changes in your local git repo? It seems that we need to consider >>> a >>> > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>> > feature" tag in a commit to move the pbr versioning forward. >>> > >>> > BUILD Team (Don, Scott, Frank): >>> > >>> > Here's the general issue, we tag on the release branches, not >>> master >>> > (although we have a v3.0.0.rc0 tag on master), we need to either >>> add a >>> > Sem_Ver: feature tag to increment version's major number, or add >>> a >>> > pre-tag of the 4.0 release. >>> > >>> > Thoughts from the build team? I think we discussed part of the >>> before, >>> > but want to do a quick revisit of the thread back in Nov [1], I >>> think we >>> > had agreed to use Sem_Ver but it's not in the email thread >>> > >>> > >>> > [0] >>> > >>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/ >>> 006790.html >>> >>> > >>> > >>> > On 3/26/20 7:26 PM, 何义鹏 wrote: >>> > > >>> > > Yes, building the rpm of the starlingx dashboard is a >>> necessary step for >>> > > my build-iso. >>> > > >>> > > Maybe Saul can respond to the question that python builds >>> allow several >>> > > versions of components. >>> > > >>> > Jeremy replied to this earlier in the week, the issue appears to >>> be the >>> > way we tagged rc0, we might need to have change our tagging. He >>> also >>> > stated that the number of components is not a limiting factor. >>> > >>> > Sau! >>> > > ------------------ Original ------------------ >>> > > *From: * "Penney, Don"; >>> > > *Date: * Wed, Mar 25, 2020 10:11 PM >>> > > *To: * "何义鹏"; "Saul >>> > > Wold(sgw at linux.intel.com)"; >>> > > *Cc: >>> > > >>> > >>> * >>> "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.star >>> lingx.io)"; >>> >>> > >>> > > >>> > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>> > > >>> > > Please keep starlingx-discuss on the receiver list. >>> > > >>> > > You had indicated build-iso was failing, but the build.log you >>> provided >>> > > appears to be the RPM build log for starlingx-dashboard. >>> > > >>> > > Processing files: >>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>> > > >>> > > error: File not found: >>> > > >>> > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9 >>> 999.9999.rc1.dev23*.egg-info >>> >>> > > >>> > > RPM build errors: >>> > > >>> > > File not found: >>> > > >>> > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9 >>> 999.9999.rc1.dev23*.egg-info >>> >>> > > >>> > > Child return code was: 1 >>> > > >>> > > EXCEPTION: [Error()] >>> > > >>> > > Traceback (most recent call last): >>> > > >>> > > File >>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>> > > line 95, in trace >>> > > >>> > > result = func(*args, **kw) >>> > > >>> > > File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>> line 746, >>> > > in do_with_status >>> > > >>> > > raise exception.Error("Command failed: \n # %s\n%s" % >>> (command, >>> > > output), child.returncode) >>> > > >>> > > mockbuild.exception.Error: Command failed: >>> > > >>> > > # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 >>> --nodeps >>> > > /builddir/build/SPECS/starlingx-dashboard.spec >>> > > >>> > > Looking through the build.log, I see the following: >>> > > >>> > > Copying starlingx_dashboard.egg-info to >>> > > >>> > >>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.de >>> v23-py2.7.egg-info >>> >>> > > >>> > > So in the build, it’s creating the egg with the version set to >>> > > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>> > > 2.9999.9999.rc1.dev23. >>> > > >>> > > Looking further through the build.log, there’s the following: >>> > > >>> > > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>> > > >>> > >>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>> 0.tis.x86_64 >>> >>> > > >>> > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>> UserWarning: >>> > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>> > > >>> > > normalized_version, >>> > > >>> > > running install >>> > > >>> > > Maybe the python build only allows 4 version components? >>> > > >>> > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>> > > *Sent:* Tuesday, March 24, 2020 9:59 PM >>> > > *To:* Penney, Don >>> > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>> > > >>> > > Hi Saul, >>> > > >>> > > I added the error log to the attachment. Do you need other >>> files for >>> > > analysis? >>> > > >>> > > Thank you for your help. >>> > > >>> > > yipeng.he! >>> > > >>> > > ------------------ Original ------------------ >>> > > >>> > > *From: * "Penney, Don"; >>> > > >>> > > *Date: * Wed, Mar 25, 2020 04:24 AM >>> > > >>> > > *To: * "Saul Wold"; "何义鹏" >>> > ; >>> > > >>> > > *Cc: * "桂来军"; "杨永金" >>> > > ; "曹明晓"; >>> > > "starlingx-discuss"; >>> > > >>> > > *Subject: * RE: [Starlingx-discuss] enable pbr version >>> > > >>> > > Hi Yipeng, >>> > > >>> > > Can you provide more info? What was the error you saw from >>> build-iso? >>> > > >>> > > >>> > > -----Original Message----- >>> > > From: Saul Wold [mailto:sgw at linux.intel.com] >>> > > Sent: Monday, March 23, 2020 6:45 PM >>> > > To: 何义鹏 >>> > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>> > > Subject: Re: [Starlingx-discuss] enable pbr version >>> > > >>> > > >>> > > Hi Yipeng, >>> > > >>> > > I was out last week on vacation, so I am catching up now. >>> > > >>> > > I think you would have to investigate build-iso and associated >>> scripts >>> > > and tools to see if there is an awk, sed or some other command >>> that is >>> > > not parsing the extended version. I have not investigated >>> this further, >>> > > that's my initial assessment. >>> > > >>> > > Can you be more specific about what the error is or provide a >>> log file >>> > > of the build-iso process? >>> > > >>> > > Thanks for working on this project. >>> > > >>> > > Sau! >>> > > >>> > > >>> > > >>> > > On 3/19/20 12:21 AM, 何义鹏wrote: >>> > >> Hello Saul >>> > >> >>> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks of >>> PBR. >>> > >> I encountered the following issue when trying to build iso: >>> > >> It fails when the suffix of the version generated by the PBR >>> tool ended >>> > >> with number, for instance the building fails if the version >>> id is >>> > >> 2.999.9999.rc1.dev23, >>> > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>> building was >>> > >> successful. >>> > >> I don't knwo why this happens, could please support and >>> advice the >>> > >> solution for this issue. >>> > >> >>> > >> >>> > >> Yipeng.He >>> > >> >>> > >> _______________________________________________ >>> > >> 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 >>> > >>> >>> _______________________________________________ >>> 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 Wed Apr 22 16:18:10 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 22 Apr 2020 09:18:10 -0700 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiAgZW5hYmxlIHBiciB2ZXJz?= =?utf-8?q?ion?= In-Reply-To: <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com> Message-ID: <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> Hi Cherish, Nice to hear from you again. See comments below On 4/22/20 9:13 AM, cherish.cao at jitstack.com wrote: > Hi Saul: > We have solved some problems related to PBR and submitted relevant codes. Due to Yipeng's limited proficiency of English, he handles the mails slowly. I am glad to hear your working on this, I have reviewed and commented on all the changes submitted, the last change was last week, so I hope to see some updates soon. > I'm sorry about that. JITStack will continue to invest in PBR-related patches, please don't worry. > After that, I've organized a team for the work related to PBR and ChornXie(chron.xie at jitstack.com) will join us in order to assist Yipeng to promote the work. Sorry again for the confusion. > I look forward to seeing the updates and will review them as soon as possible, this work is important and we would like to get it completed soon. Thanks again for your commitment to StarlingX Sau! > In addition, do you have instant messaging software,like Wechat or something, I think this may speed up the promotion of PBR. > > Thanks > Cherish.Cao > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年4月22日 11:24 > 收件人: 何义鹏 > 抄送: 曹明晓 ; 桂来军 ; starlingx-discuss > 主题: Re: [Starlingx-discuss] enable pbr version > > > Hi Again Yipeng, > > I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. > > Sau! > > [0] > https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distro_Non-OpenStack_Team_Call > > On 4/14/20 9:42 AM, Saul Wold wrote: >> Yipeng, >> >> I hope you can join the Distro meeting in your evening tomorrow and we >> can disuses this issue. >> >> Thanks >> >> Sau! >> >> >> On 4/13/20 10:13 PM, Saul Wold wrote: >>> Can you please provide more details about what you did and how you >>> tried to create the ISO? >>> >>> The information here is not very helpful. Maybe the community >>> members in China can help you get the build to work correctly. >>> >>> Sau! >>> >>> >>> On 4/13/20 7:43 PM, 何义鹏 wrote: >>>> >>>> Hi Saul, >>>> >>>> I'm sorry it took so long to recover your mail. >>>> >>>> Recently, there was a problem when I modified according to the >>>> method you provided under patch. >>>> I tried to change all the versions in the patch of >>>> starlingx-starboard to pbr_version. >>>> But the result still failed to build iso. >>>> >>>> yipeng.he! >>>> ------------------ Original ------------------ >>>> *From: * "Saul Wold"; >>>> *Date: * Wed, Apr 8, 2020 02:58 AM >>>> *To: * "starlingx-discuss"; "何 >>>> 义 鹏"; >>>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> >>>> Hi Yipeng, >>>> >>>> Sorry for the delay in getting back to you, I was looking into the >>>> build failure and trying understand how we handle the difference >>>> between the PBR SemVer [0] and PEP440 [1]. Specifically when there >>>> is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 >>>> normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>>> >>>> So we need to also change the spec files %files section for the >>>> egg-info file to wild-card that file instead of having a specific version listed. >>>> >>>> For example in the starlingx-dashboard spec file: >>>> >>>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> index 7fbee65..399a9bd 100644 >>>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>>> %files >>>> %{python2_sitelib}/%{py_pkg_name} >>>> >>>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>>> >>>> %{enabled_dir} >>>> %{stx_themes_dir} >>>> >>>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>>> feature" in the commit message, just once per repo. See Bin's >>>> pending commit in fault [2]. You will have to back and fix fault and >>>> other pending commits with the wild-card change for the egg-info >>>> file in the spec file. >>>> >>>> Finally all PBR related reviews should have a >>>> Depends-On: https://review.opendev.org/#/c/691632/ >>>> >>>> So it does not get merged before the enabling code in the build >>>> tools merges. >>>> >>>> Hope this clarifies things and gets the PBR work unblocked. I am >>>> going through the reviews and trying to provide some additional >>>> review comments. >>>> We can also talk about this tomorrow during the Distro call [3] >>>> >>>> Sau! >>>> >>>> >>>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>>> [1] https://www.python.org/dev/peps/pep-0440/ >>>> [2] https://review.opendev.org/#/c/691647/ >>>> [3] >>>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>>> > >>>> > Saul! >>>> > >>>> > Thank you for your answer! But how should I use the semMem-ver tag? >>>> > ------------------ Original ------------------ >>>> > *From: * "Saul Wold"; >>>> > *Date: * Sat, Mar 28, 2020 07:02 AM >>>> > *To: * "何义鹏"; "Penney, >>>> > Don"; "Scott >>>> > Little"; "Miller, >>>> > Frank"; >>>> > *Cc: * "曹明晓"; "杨永金" >>>> > ; "桂来军"; >>>> > "starlingx-discuss"; >>>> > *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> > Yipeng, >>>> > >>>> > >>>> > I replied the other day, wanting to confirm if you have any >>>> additional >>>> > changes in your local git repo? It seems that we need to consider >>>> a >>>> > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>>> > feature" tag in a commit to move the pbr versioning forward. >>>> > >>>> > BUILD Team (Don, Scott, Frank): >>>> > >>>> > Here's the general issue, we tag on the release branches, not >>>> master >>>> > (although we have a v3.0.0.rc0 tag on master), we need to either >>>> add a >>>> > Sem_Ver: feature tag to increment version's major number, or add >>>> a >>>> > pre-tag of the 4.0 release. >>>> > >>>> > Thoughts from the build team? I think we discussed part of the >>>> before, >>>> > but want to do a quick revisit of the thread back in Nov [1], I >>>> think we >>>> > had agreed to use Sem_Ver but it's not in the email thread >>>> > >>>> > >>>> > [0] >>>> > >>>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/ >>>> 006790.html >>>> >>>> > >>>> > >>>> > On 3/26/20 7:26 PM, 何义鹏 wrote: >>>> > > >>>> > > Yes, building the rpm of the starlingx dashboard is a >>>> necessary step for >>>> > > my build-iso. >>>> > > >>>> > > Maybe Saul can respond to the question that python builds >>>> allow several >>>> > > versions of components. >>>> > > >>>> > Jeremy replied to this earlier in the week, the issue appears to >>>> be the >>>> > way we tagged rc0, we might need to have change our tagging. He >>>> also >>>> > stated that the number of components is not a limiting factor. >>>> > >>>> > Sau! >>>> > > ------------------ Original ------------------ >>>> > > *From: * "Penney, Don"; >>>> > > *Date: * Wed, Mar 25, 2020 10:11 PM >>>> > > *To: * "何义鹏"; "Saul >>>> > > Wold(sgw at linux.intel.com)"; >>>> > > *Cc: >>>> > > >>>> > >>>> * >>>> "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.star >>>> lingx.io)"; >>>> >>>> > >>>> > > >>>> > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Please keep starlingx-discuss on the receiver list. >>>> > > >>>> > > You had indicated build-iso was failing, but the build.log you >>>> provided >>>> > > appears to be the RPM build log for starlingx-dashboard. >>>> > > >>>> > > Processing files: >>>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>>> > > >>>> > > error: File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > RPM build errors: >>>> > > >>>> > > File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2.9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > Child return code was: 1 >>>> > > >>>> > > EXCEPTION: [Error()] >>>> > > >>>> > > Traceback (most recent call last): >>>> > > >>>> > > File >>>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>>> > > line 95, in trace >>>> > > >>>> > > result = func(*args, **kw) >>>> > > >>>> > > File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>>> line 746, >>>> > > in do_with_status >>>> > > >>>> > > raise exception.Error("Command failed: \n # %s\n%s" % >>>> (command, >>>> > > output), child.returncode) >>>> > > >>>> > > mockbuild.exception.Error: Command failed: >>>> > > >>>> > > # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 >>>> --nodeps >>>> > > /builddir/build/SPECS/starlingx-dashboard.spec >>>> > > >>>> > > Looking through the build.log, I see the following: >>>> > > >>>> > > Copying starlingx_dashboard.egg-info to >>>> > > >>>> > >>>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.de >>>> v23-py2.7.egg-info >>>> >>>> > > >>>> > > So in the build, it’s creating the egg with the version set to >>>> > > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>>> > > 2.9999.9999.rc1.dev23. >>>> > > >>>> > > Looking further through the build.log, there’s the following: >>>> > > >>>> > > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23- >>>> 0.tis.x86_64 >>>> >>>> > > >>>> > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>>> UserWarning: >>>> > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>>> > > >>>> > > normalized_version, >>>> > > >>>> > > running install >>>> > > >>>> > > Maybe the python build only allows 4 version components? >>>> > > >>>> > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>>> > > *Sent:* Tuesday, March 24, 2020 9:59 PM >>>> > > *To:* Penney, Don >>>> > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Saul, >>>> > > >>>> > > I added the error log to the attachment. Do you need other >>>> files for >>>> > > analysis? >>>> > > >>>> > > Thank you for your help. >>>> > > >>>> > > yipeng.he! >>>> > > >>>> > > ------------------ Original ------------------ >>>> > > >>>> > > *From: * "Penney, Don"; >>>> > > >>>> > > *Date: * Wed, Mar 25, 2020 04:24 AM >>>> > > >>>> > > *To: * "Saul Wold"; "何义鹏" >>>> > ; >>>> > > >>>> > > *Cc: * "桂来军"; "杨永金" >>>> > > ; "曹明晓"; >>>> > > "starlingx-discuss"; >>>> > > >>>> > > *Subject: * RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > Can you provide more info? What was the error you saw from >>>> build-iso? >>>> > > >>>> > > >>>> > > -----Original Message----- >>>> > > From: Saul Wold [mailto:sgw at linux.intel.com] >>>> > > Sent: Monday, March 23, 2020 6:45 PM >>>> > > To: 何义鹏 >>>> > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>>> > > Subject: Re: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > I was out last week on vacation, so I am catching up now. >>>> > > >>>> > > I think you would have to investigate build-iso and associated >>>> scripts >>>> > > and tools to see if there is an awk, sed or some other command >>>> that is >>>> > > not parsing the extended version. I have not investigated >>>> this further, >>>> > > that's my initial assessment. >>>> > > >>>> > > Can you be more specific about what the error is or provide a >>>> log file >>>> > > of the build-iso process? >>>> > > >>>> > > Thanks for working on this project. >>>> > > >>>> > > Sau! >>>> > > >>>> > > >>>> > > >>>> > > On 3/19/20 12:21 AM, 何义鹏wrote: >>>> > >> Hello Saul >>>> > >> >>>> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks of >>>> PBR. >>>> > >> I encountered the following issue when trying to build iso: >>>> > >> It fails when the suffix of the version generated by the PBR >>>> tool ended >>>> > >> with number, for instance the building fails if the version >>>> id is >>>> > >> 2.999.9999.rc1.dev23, >>>> > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>>> building was >>>> > >> successful. >>>> > >> I don't knwo why this happens, could please support and >>>> advice the >>>> > >> solution for this issue. >>>> > >> >>>> > >> >>>> > >> Yipeng.He >>>> > >> >>>> > >> _______________________________________________ >>>> > >> 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 >>>> > >>>> >>>> _______________________________________________ >>>> 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 Wed Apr 22 16:21:24 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 22 Apr 2020 09:21:24 -0700 Subject: [Starlingx-discuss] nominate several core reviewers on 3 STX projects In-Reply-To: <9f44a045-f13f-00cb-4ffd-50eb865b84c6@linux.intel.com> References: <2C8F09B1-929E-41AD-9A9C-B1987C423D3E@intel.com> <9f44a045-f13f-00cb-4ffd-50eb865b84c6@linux.intel.com> Message-ID: <50a6f717-3c84-3b90-b715-f2e0213de6e3@linux.intel.com> As we closed on this in the Community call, I added Austin and Shuicheng to the appropriate core groups. Sau! On 4/21/20 7:44 AM, Saul Wold wrote: > > Agreed, let's close on this in the Distro meeting tomorrow. > > Sau! > > > On 4/16/20 7:06 PM, Hu, Yong wrote: >> Hi cores, >> >> I would like to nominate these guys as core reviewers in following >> project: >> >>  1. project:starlingx/integ:   Sun, Austin austin.sun at intel.com >>     >>  2. project:starlingx/kernel:  Lin, Shuicheng shuicheng.lin at intel.com >>     >>  3. project:starlingx/docs: Wang, Yi C yi.c.wang at intel.com >>     >> >> These 3 guys have been working on StarlingX since 2018 March, and they >> contributed considerate number of patches for features, integrations >> and bug fixes. >> >> Upgrading them to core reviewers will enable them to contribute more >> on StarlingX and have better coverage on the patch review in Asian >> time zone. >> >> So, please let us know your feedback. Thanks! >> >> Regards, >> >> Yong >> >> >> _______________________________________________ >> 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 cherish.cao at jitstack.com Wed Apr 22 16:29:01 2020 From: cherish.cao at jitstack.com (cherish.cao at jitstack.com) Date: Thu, 23 Apr 2020 00:29:01 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiDlm57lpI06ICBlbmFibGUg?= =?utf-8?q?pbr_version?= In-Reply-To: <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com> <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> Message-ID: <00a501d618c3$2293f6e0$67bbe4a0$@jitstack.com>+253C5D7DA29540D8 Hi Saul: I will push forward as soon as possible. Thanks. -----邮件原件----- 发件人: Saul Wold 发送时间: 2020年4月23日 0:18 收件人: cherish.cao at jitstack.com; '何义鹏' 抄送: 'chron.xie' ; 'starlingx-discuss' 主题: Re: 回复: [Starlingx-discuss] enable pbr version Hi Cherish, Nice to hear from you again. See comments below On 4/22/20 9:13 AM, cherish.cao at jitstack.com wrote: > Hi Saul: > We have solved some problems related to PBR and submitted relevant codes. Due to Yipeng's limited proficiency of English, he handles the mails slowly. I am glad to hear your working on this, I have reviewed and commented on all the changes submitted, the last change was last week, so I hope to see some updates soon. > I'm sorry about that. JITStack will continue to invest in PBR-related patches, please don't worry. > After that, I've organized a team for the work related to PBR and ChornXie(chron.xie at jitstack.com) will join us in order to assist Yipeng to promote the work. Sorry again for the confusion. > I look forward to seeing the updates and will review them as soon as possible, this work is important and we would like to get it completed soon. Thanks again for your commitment to StarlingX Sau! > In addition, do you have instant messaging software,like Wechat or something, I think this may speed up the promotion of PBR. > > Thanks > Cherish.Cao > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年4月22日 11:24 > 收件人: 何义鹏 > 抄送: 曹明晓 ; 桂来军 ; > starlingx-discuss > 主题: Re: [Starlingx-discuss] enable pbr version > > > Hi Again Yipeng, > > I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. > > Sau! > > [0] > https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distr > o_Non-OpenStack_Team_Call > > On 4/14/20 9:42 AM, Saul Wold wrote: >> Yipeng, >> >> I hope you can join the Distro meeting in your evening tomorrow and >> we can disuses this issue. >> >> Thanks >> >> Sau! >> >> >> On 4/13/20 10:13 PM, Saul Wold wrote: >>> Can you please provide more details about what you did and how you >>> tried to create the ISO? >>> >>> The information here is not very helpful. Maybe the community >>> members in China can help you get the build to work correctly. >>> >>> Sau! >>> >>> >>> On 4/13/20 7:43 PM, 何义鹏 wrote: >>>> >>>> Hi Saul, >>>> >>>> I'm sorry it took so long to recover your mail. >>>> >>>> Recently, there was a problem when I modified according to the >>>> method you provided under patch. >>>> I tried to change all the versions in the patch of >>>> starlingx-starboard to pbr_version. >>>> But the result still failed to build iso. >>>> >>>> yipeng.he! >>>> ------------------ Original ------------------ >>>> *From: * "Saul Wold"; >>>> *Date: * Wed, Apr 8, 2020 02:58 AM >>>> *To: * "starlingx-discuss"; >>>> "何 >>>> 义 鹏"; >>>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> >>>> Hi Yipeng, >>>> >>>> Sorry for the delay in getting back to you, I was looking into the >>>> build failure and trying understand how we handle the difference >>>> between the PBR SemVer [0] and PEP440 [1]. Specifically when there >>>> is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 >>>> normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>>> >>>> So we need to also change the spec files %files section for the >>>> egg-info file to wild-card that file instead of having a specific version listed. >>>> >>>> For example in the starlingx-dashboard spec file: >>>> >>>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> index 7fbee65..399a9bd 100644 >>>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>>> %files >>>> %{python2_sitelib}/%{py_pkg_name} >>>> >>>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>>> >>>> %{enabled_dir} >>>> %{stx_themes_dir} >>>> >>>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>>> feature" in the commit message, just once per repo. See Bin's >>>> pending commit in fault [2]. You will have to back and fix fault >>>> and other pending commits with the wild-card change for the >>>> egg-info file in the spec file. >>>> >>>> Finally all PBR related reviews should have a >>>> Depends-On: https://review.opendev.org/#/c/691632/ >>>> >>>> So it does not get merged before the enabling code in the build >>>> tools merges. >>>> >>>> Hope this clarifies things and gets the PBR work unblocked. I am >>>> going through the reviews and trying to provide some additional >>>> review comments. >>>> We can also talk about this tomorrow during the Distro call [3] >>>> >>>> Sau! >>>> >>>> >>>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>>> [1] https://www.python.org/dev/peps/pep-0440/ >>>> [2] https://review.opendev.org/#/c/691647/ >>>> [3] >>>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>>> > >>>> > Saul! >>>> > >>>> > Thank you for your answer! But how should I use the semMem-ver tag? >>>> > ------------------ Original ------------------ >>>> > *From: * "Saul Wold"; >>>> > *Date: * Sat, Mar 28, 2020 07:02 AM >>>> > *To: * "何义鹏"; "Penney, >>>> > Don"; "Scott >>>> > Little"; "Miller, >>>> > Frank"; >>>> > *Cc: * "曹明晓"; "杨永金" >>>> > ; "桂来军"; >>>> > "starlingx-discuss"; >>>> > *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> > Yipeng, >>>> > >>>> > >>>> > I replied the other day, wanting to confirm if you have any >>>> additional >>>> > changes in your local git repo? It seems that we need to >>>> consider a >>>> > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>>> > feature" tag in a commit to move the pbr versioning forward. >>>> > >>>> > BUILD Team (Don, Scott, Frank): >>>> > >>>> > Here's the general issue, we tag on the release branches, not >>>> master >>>> > (although we have a v3.0.0.rc0 tag on master), we need to >>>> either add a >>>> > Sem_Ver: feature tag to increment version's major number, or >>>> add a >>>> > pre-tag of the 4.0 release. >>>> > >>>> > Thoughts from the build team? I think we discussed part of the >>>> before, >>>> > but want to do a quick revisit of the thread back in Nov [1], I >>>> think we >>>> > had agreed to use Sem_Ver but it's not in the email thread >>>> > >>>> > >>>> > [0] >>>> > >>>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November >>>> / >>>> 006790.html >>>> >>>> > >>>> > >>>> > On 3/26/20 7:26 PM, 何义鹏 wrote: >>>> > > >>>> > > Yes, building the rpm of the starlingx dashboard is a >>>> necessary step for >>>> > > my build-iso. >>>> > > >>>> > > Maybe Saul can respond to the question that python builds >>>> allow several >>>> > > versions of components. >>>> > > >>>> > Jeremy replied to this earlier in the week, the issue appears >>>> to be the >>>> > way we tagged rc0, we might need to have change our tagging. >>>> He also >>>> > stated that the number of components is not a limiting factor. >>>> > >>>> > Sau! >>>> > > ------------------ Original ------------------ >>>> > > *From: * "Penney, Don"; >>>> > > *Date: * Wed, Mar 25, 2020 10:11 PM >>>> > > *To: * "何义鹏"; "Saul >>>> > > Wold(sgw at linux.intel.com)"; >>>> > > *Cc: >>>> > > >>>> > >>>> * >>>> "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.sta >>>> r lingx.io)"; >>>> >>>> > >>>> > > >>>> > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Please keep starlingx-discuss on the receiver list. >>>> > > >>>> > > You had indicated build-iso was failing, but the build.log >>>> you provided >>>> > > appears to be the RPM build log for starlingx-dashboard. >>>> > > >>>> > > Processing files: >>>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>>> > > >>>> > > error: File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>> 9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > RPM build errors: >>>> > > >>>> > > File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>> 9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > Child return code was: 1 >>>> > > >>>> > > EXCEPTION: [Error()] >>>> > > >>>> > > Traceback (most recent call last): >>>> > > >>>> > > File >>>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>>> > > line 95, in trace >>>> > > >>>> > > result = func(*args, **kw) >>>> > > >>>> > > File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>>> line 746, >>>> > > in do_with_status >>>> > > >>>> > > raise exception.Error("Command failed: \n # %s\n%s" % >>>> (command, >>>> > > output), child.returncode) >>>> > > >>>> > > mockbuild.exception.Error: Command failed: >>>> > > >>>> > > # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 >>>> --nodeps >>>> > > /builddir/build/SPECS/starlingx-dashboard.spec >>>> > > >>>> > > Looking through the build.log, I see the following: >>>> > > >>>> > > Copying starlingx_dashboard.egg-info to >>>> > > >>>> > >>>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.d >>>> e >>>> v23-py2.7.egg-info >>>> >>>> > > >>>> > > So in the build, it’s creating the egg with the version set to >>>> > > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>>> > > 2.9999.9999.rc1.dev23. >>>> > > >>>> > > Looking further through the build.log, there’s the following: >>>> > > >>>> > > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64 >>>> >>>> > > >>>> > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>>> UserWarning: >>>> > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>>> > > >>>> > > normalized_version, >>>> > > >>>> > > running install >>>> > > >>>> > > Maybe the python build only allows 4 version components? >>>> > > >>>> > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>>> > > *Sent:* Tuesday, March 24, 2020 9:59 PM >>>> > > *To:* Penney, Don >>>> > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Saul, >>>> > > >>>> > > I added the error log to the attachment. Do you need other >>>> files for >>>> > > analysis? >>>> > > >>>> > > Thank you for your help. >>>> > > >>>> > > yipeng.he! >>>> > > >>>> > > ------------------ Original ------------------ >>>> > > >>>> > > *From: * "Penney, Don"; >>>> > > >>>> > > *Date: * Wed, Mar 25, 2020 04:24 AM >>>> > > >>>> > > *To: * "Saul Wold"; "何义鹏" >>>> > ; >>>> > > >>>> > > *Cc: * "桂来军"; "杨永金" >>>> > > ; "曹明晓"; >>>> > > "starlingx-discuss"; >>>> > > >>>> > > *Subject: * RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > Can you provide more info? What was the error you saw from >>>> build-iso? >>>> > > >>>> > > >>>> > > -----Original Message----- >>>> > > From: Saul Wold [mailto:sgw at linux.intel.com] >>>> > > Sent: Monday, March 23, 2020 6:45 PM >>>> > > To: 何义鹏 >>>> > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>>> > > Subject: Re: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > I was out last week on vacation, so I am catching up now. >>>> > > >>>> > > I think you would have to investigate build-iso and >>>> associated scripts >>>> > > and tools to see if there is an awk, sed or some other >>>> command that is >>>> > > not parsing the extended version. I have not investigated >>>> this further, >>>> > > that's my initial assessment. >>>> > > >>>> > > Can you be more specific about what the error is or provide >>>> a log file >>>> > > of the build-iso process? >>>> > > >>>> > > Thanks for working on this project. >>>> > > >>>> > > Sau! >>>> > > >>>> > > >>>> > > >>>> > > On 3/19/20 12:21 AM, 何义鹏wrote: >>>> > >> Hello Saul >>>> > >> >>>> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks >>>> of PBR. >>>> > >> I encountered the following issue when trying to build iso: >>>> > >> It fails when the suffix of the version generated by the >>>> PBR tool ended >>>> > >> with number, for instance the building fails if the version >>>> id is >>>> > >> 2.999.9999.rc1.dev23, >>>> > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>>> building was >>>> > >> successful. >>>> > >> I don't knwo why this happens, could please support and >>>> advice the >>>> > >> solution for this issue. >>>> > >> >>>> > >> >>>> > >> Yipeng.He >>>> > >> >>>> > >> _______________________________________________ >>>> > >> 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 >>>> > >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > From ruediger.stock at intel.com Wed Apr 22 17:41:30 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Wed, 22 Apr 2020 17:41:30 +0000 Subject: [Starlingx-discuss] Sanity Master Test MONOLITHIC build ISO 20200422 Message-ID: Sanity Test from 2020-April-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20200422T013012Z/outputs/iso/) 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 ] 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 External - 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 - 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 External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Apr 22 17:52:07 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 22 Apr 2020 19:52:07 +0200 Subject: [Starlingx-discuss] Virtual PTG preparations - ACTION NEEDED Message-ID: <8D9FA3C1-E0CA-48E6-A319-19482BD1123A@gmail.com> Hi StarlingX Community, It is time to start building the agenda for the virtual PTG[1] that will happen in June 1-5 and book time slots the community would like to use. We need to decide how much time the community would like to use __in total__. We can book slots accordingly throughout the week with no more than __4 hours per day (in UTC hours)__. I created an etherpad[2] to throw in agenda items and time estimates. __Please add items and time estimates to the etherpad as soon as possible__. I also added an attendee section to the etherpad. Please __sign up and add your region__ based on where you’re located/will be at the time of the virtual PTG. The options are Americas, EMEA, APAC. With adding the regions it helps narrowing down which time blocks we should aim for to find the slots that work for the most. Please let me know if you have any questions. Thanks, Ildikó [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008296.html [2] https://etherpad.opendev.org/p/stx-virtual-PTG-June From kennelson11 at gmail.com Wed Apr 22 18:47:09 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 22 Apr 2020 11:47:09 -0700 Subject: [Starlingx-discuss] Fwd: [all] [PTL][TC] PTG Signup Reminder & PTG Registration In-Reply-To: References: Message-ID: Hello! ==Virtual PTG Signup== Wanted to take a second to remind teams about the process for signing up for virtual PTG slots. 0. Look at the slots available and talk to your contributors and team members to find out the best times to signup for. 1. Sign up in the ethercalc [1] for the time slots your team needs. You can sign up for up to 4 hours/day and 16 hours/ the week (restrictions in place until *April 28th at 7:00 UTC*). If you are a SIG or WG, try to keep your conversations at the start of the week wherever possible. Vertical teams, try to focus your conversations towards the latter part of the week (Wednesday-Friday). *AND* 2. Fill out the survey [2] to give us the other team information we need to help facilitate the event. We NEED you to do both steps! I can see a number of teams that have signed up for time, but haven't filled out the survey so please do so ASAP. There are still a lot of slots left! Original thread[3]. ==Registration== After a lot of discussion, we have decided to have registration. It is free but its still extremely important that you register as this is primarily so we have a way to contact attendees with information about the event as we figure the rest of the details out. We will have the registration live next week. -the Kendalls (diablo_rojo & wendallkaters) [1] Ethercalc:https://ethercalc.openstack.org/126u8ek25noy [2] Survey: https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey [3] PTG Layout & Signup Thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Apr 23 00:55:21 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 23 Apr 2020 00:55:21 +0000 Subject: [Starlingx-discuss] [TSC] Minutes - 4/22 Message-ID: <943EE77D-B55C-4514-9B7C-C1173CF9087F@windriver.com> Hi all; Please see notes below from today's TSC call. • Confirmation review - Timeline • OSF feedback and dry run - 5/1 slides available • other projects and OSF staff prior to the call • week of the 4th • Pre- review - plan for week of 11th • Board meeting - June 7th • Virtual PTG planning - First week of June - will be held remotely o Agenda -  • STX community • https://etherpad.opendev.org/p/stx-virtual-PTG-June • Ethercalc used to book slots o https://ethercalc.openstack.org/126u8ek25noy • Topics: o Release 4 - active development o Release 5 planning o Futures o Testing o User adoption • Cross project • Kata containers community • Edge computing - 1300-1600 UTC  • Others? (Airship - projects we are leveraging?) o Time zone leverage • 3 zones established  • How do we want to leverage? Regards; Ian From cherish.cao at jitstack.com Thu Apr 23 03:51:44 2020 From: cherish.cao at jitstack.com (cherish.cao at jitstack.com) Date: Thu, 23 Apr 2020 11:51:44 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiDlm57lpI06ICBlbmFibGUg?= =?utf-8?q?pbr_version?= In-Reply-To: <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com> <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> Message-ID: <000a01d61922$8227fed0$8677fc70$@jitstack.com>+D021E520B993E483 Hi Saul: The code has been resubmitted in the old branch (https://review.opendev.org/#/c/710923/),in addition, do we need to discard or delete the newly created branch? (https://review.opendev.org/#/c/720195/) -----邮件原件----- 发件人: Saul Wold 发送时间: 2020年4月23日 0:18 收件人: cherish.cao at jitstack.com; '何义鹏' 抄送: 'chron.xie' ; 'starlingx-discuss' 主题: Re: 回复: [Starlingx-discuss] enable pbr version Hi Cherish, Nice to hear from you again. See comments below On 4/22/20 9:13 AM, cherish.cao at jitstack.com wrote: > Hi Saul: > We have solved some problems related to PBR and submitted relevant codes. Due to Yipeng's limited proficiency of English, he handles the mails slowly. I am glad to hear your working on this, I have reviewed and commented on all the changes submitted, the last change was last week, so I hope to see some updates soon. > I'm sorry about that. JITStack will continue to invest in PBR-related patches, please don't worry. > After that, I've organized a team for the work related to PBR and ChornXie(chron.xie at jitstack.com) will join us in order to assist Yipeng to promote the work. Sorry again for the confusion. > I look forward to seeing the updates and will review them as soon as possible, this work is important and we would like to get it completed soon. Thanks again for your commitment to StarlingX Sau! > In addition, do you have instant messaging software,like Wechat or something, I think this may speed up the promotion of PBR. > > Thanks > Cherish.Cao > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年4月22日 11:24 > 收件人: 何义鹏 > 抄送: 曹明晓 ; 桂来军 ; > starlingx-discuss > 主题: Re: [Starlingx-discuss] enable pbr version > > > Hi Again Yipeng, > > I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. > > Sau! > > [0] > https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distr > o_Non-OpenStack_Team_Call > > On 4/14/20 9:42 AM, Saul Wold wrote: >> Yipeng, >> >> I hope you can join the Distro meeting in your evening tomorrow and >> we can disuses this issue. >> >> Thanks >> >> Sau! >> >> >> On 4/13/20 10:13 PM, Saul Wold wrote: >>> Can you please provide more details about what you did and how you >>> tried to create the ISO? >>> >>> The information here is not very helpful. Maybe the community >>> members in China can help you get the build to work correctly. >>> >>> Sau! >>> >>> >>> On 4/13/20 7:43 PM, 何义鹏 wrote: >>>> >>>> Hi Saul, >>>> >>>> I'm sorry it took so long to recover your mail. >>>> >>>> Recently, there was a problem when I modified according to the >>>> method you provided under patch. >>>> I tried to change all the versions in the patch of >>>> starlingx-starboard to pbr_version. >>>> But the result still failed to build iso. >>>> >>>> yipeng.he! >>>> ------------------ Original ------------------ >>>> *From: * "Saul Wold"; >>>> *Date: * Wed, Apr 8, 2020 02:58 AM >>>> *To: * "starlingx-discuss"; >>>> "何 >>>> 义 鹏"; >>>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> >>>> Hi Yipeng, >>>> >>>> Sorry for the delay in getting back to you, I was looking into the >>>> build failure and trying understand how we handle the difference >>>> between the PBR SemVer [0] and PEP440 [1]. Specifically when there >>>> is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 >>>> normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>>> >>>> So we need to also change the spec files %files section for the >>>> egg-info file to wild-card that file instead of having a specific version listed. >>>> >>>> For example in the starlingx-dashboard spec file: >>>> >>>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> index 7fbee65..399a9bd 100644 >>>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>>> %files >>>> %{python2_sitelib}/%{py_pkg_name} >>>> >>>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>>> >>>> %{enabled_dir} >>>> %{stx_themes_dir} >>>> >>>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>>> feature" in the commit message, just once per repo. See Bin's >>>> pending commit in fault [2]. You will have to back and fix fault >>>> and other pending commits with the wild-card change for the >>>> egg-info file in the spec file. >>>> >>>> Finally all PBR related reviews should have a >>>> Depends-On: https://review.opendev.org/#/c/691632/ >>>> >>>> So it does not get merged before the enabling code in the build >>>> tools merges. >>>> >>>> Hope this clarifies things and gets the PBR work unblocked. I am >>>> going through the reviews and trying to provide some additional >>>> review comments. >>>> We can also talk about this tomorrow during the Distro call [3] >>>> >>>> Sau! >>>> >>>> >>>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>>> [1] https://www.python.org/dev/peps/pep-0440/ >>>> [2] https://review.opendev.org/#/c/691647/ >>>> [3] >>>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>>> > >>>> > Saul! >>>> > >>>> > Thank you for your answer! But how should I use the semMem-ver tag? >>>> > ------------------ Original ------------------ >>>> > *From: * "Saul Wold"; >>>> > *Date: * Sat, Mar 28, 2020 07:02 AM >>>> > *To: * "何义鹏"; "Penney, >>>> > Don"; "Scott >>>> > Little"; "Miller, >>>> > Frank"; >>>> > *Cc: * "曹明晓"; "杨永金" >>>> > ; "桂来军"; >>>> > "starlingx-discuss"; >>>> > *Subject: * Re: [Starlingx-discuss] enable pbr version >>>> > Yipeng, >>>> > >>>> > >>>> > I replied the other day, wanting to confirm if you have any >>>> additional >>>> > changes in your local git repo? It seems that we need to >>>> consider a >>>> > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>>> > feature" tag in a commit to move the pbr versioning forward. >>>> > >>>> > BUILD Team (Don, Scott, Frank): >>>> > >>>> > Here's the general issue, we tag on the release branches, not >>>> master >>>> > (although we have a v3.0.0.rc0 tag on master), we need to >>>> either add a >>>> > Sem_Ver: feature tag to increment version's major number, or >>>> add a >>>> > pre-tag of the 4.0 release. >>>> > >>>> > Thoughts from the build team? I think we discussed part of the >>>> before, >>>> > but want to do a quick revisit of the thread back in Nov [1], I >>>> think we >>>> > had agreed to use Sem_Ver but it's not in the email thread >>>> > >>>> > >>>> > [0] >>>> > >>>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November >>>> / >>>> 006790.html >>>> >>>> > >>>> > >>>> > On 3/26/20 7:26 PM, 何义鹏 wrote: >>>> > > >>>> > > Yes, building the rpm of the starlingx dashboard is a >>>> necessary step for >>>> > > my build-iso. >>>> > > >>>> > > Maybe Saul can respond to the question that python builds >>>> allow several >>>> > > versions of components. >>>> > > >>>> > Jeremy replied to this earlier in the week, the issue appears >>>> to be the >>>> > way we tagged rc0, we might need to have change our tagging. >>>> He also >>>> > stated that the number of components is not a limiting factor. >>>> > >>>> > Sau! >>>> > > ------------------ Original ------------------ >>>> > > *From: * "Penney, Don"; >>>> > > *Date: * Wed, Mar 25, 2020 10:11 PM >>>> > > *To: * "何义鹏"; "Saul >>>> > > Wold(sgw at linux.intel.com)"; >>>> > > *Cc: >>>> > > >>>> > >>>> * >>>> "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.sta >>>> r lingx.io)"; >>>> >>>> > >>>> > > >>>> > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Please keep starlingx-discuss on the receiver list. >>>> > > >>>> > > You had indicated build-iso was failing, but the build.log >>>> you provided >>>> > > appears to be the RPM build log for starlingx-dashboard. >>>> > > >>>> > > Processing files: >>>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>>> > > >>>> > > error: File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>> 9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > RPM build errors: >>>> > > >>>> > > File not found: >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>> 9 >>>> 999.9999.rc1.dev23*.egg-info >>>> >>>> > > >>>> > > Child return code was: 1 >>>> > > >>>> > > EXCEPTION: [Error()] >>>> > > >>>> > > Traceback (most recent call last): >>>> > > >>>> > > File >>>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>>> > > line 95, in trace >>>> > > >>>> > > result = func(*args, **kw) >>>> > > >>>> > > File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>>> line 746, >>>> > > in do_with_status >>>> > > >>>> > > raise exception.Error("Command failed: \n # %s\n%s" % >>>> (command, >>>> > > output), child.returncode) >>>> > > >>>> > > mockbuild.exception.Error: Command failed: >>>> > > >>>> > > # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 >>>> --nodeps >>>> > > /builddir/build/SPECS/starlingx-dashboard.spec >>>> > > >>>> > > Looking through the build.log, I see the following: >>>> > > >>>> > > Copying starlingx_dashboard.egg-info to >>>> > > >>>> > >>>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.d >>>> e >>>> v23-py2.7.egg-info >>>> >>>> > > >>>> > > So in the build, it’s creating the egg with the version set to >>>> > > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>>> > > 2.9999.9999.rc1.dev23. >>>> > > >>>> > > Looking further through the build.log, there’s the following: >>>> > > >>>> > > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>>> > > >>>> > >>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>> - >>>> 0.tis.x86_64 >>>> >>>> > > >>>> > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>>> UserWarning: >>>> > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>>> > > >>>> > > normalized_version, >>>> > > >>>> > > running install >>>> > > >>>> > > Maybe the python build only allows 4 version components? >>>> > > >>>> > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>>> > > *Sent:* Tuesday, March 24, 2020 9:59 PM >>>> > > *To:* Penney, Don >>>> > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Saul, >>>> > > >>>> > > I added the error log to the attachment. Do you need other >>>> files for >>>> > > analysis? >>>> > > >>>> > > Thank you for your help. >>>> > > >>>> > > yipeng.he! >>>> > > >>>> > > ------------------ Original ------------------ >>>> > > >>>> > > *From: * "Penney, Don"; >>>> > > >>>> > > *Date: * Wed, Mar 25, 2020 04:24 AM >>>> > > >>>> > > *To: * "Saul Wold"; "何义鹏" >>>> > ; >>>> > > >>>> > > *Cc: * "桂来军"; "杨永金" >>>> > > ; "曹明晓"; >>>> > > "starlingx-discuss"; >>>> > > >>>> > > *Subject: * RE: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > Can you provide more info? What was the error you saw from >>>> build-iso? >>>> > > >>>> > > >>>> > > -----Original Message----- >>>> > > From: Saul Wold [mailto:sgw at linux.intel.com] >>>> > > Sent: Monday, March 23, 2020 6:45 PM >>>> > > To: 何义鹏 >>>> > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>>> > > Subject: Re: [Starlingx-discuss] enable pbr version >>>> > > >>>> > > >>>> > > Hi Yipeng, >>>> > > >>>> > > I was out last week on vacation, so I am catching up now. >>>> > > >>>> > > I think you would have to investigate build-iso and >>>> associated scripts >>>> > > and tools to see if there is an awk, sed or some other >>>> command that is >>>> > > not parsing the extended version. I have not investigated >>>> this further, >>>> > > that's my initial assessment. >>>> > > >>>> > > Can you be more specific about what the error is or provide >>>> a log file >>>> > > of the build-iso process? >>>> > > >>>> > > Thanks for working on this project. >>>> > > >>>> > > Sau! >>>> > > >>>> > > >>>> > > >>>> > > On 3/19/20 12:21 AM, 何义鹏wrote: >>>> > >> Hello Saul >>>> > >> >>>> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks >>>> of PBR. >>>> > >> I encountered the following issue when trying to build iso: >>>> > >> It fails when the suffix of the version generated by the >>>> PBR tool ended >>>> > >> with number, for instance the building fails if the version >>>> id is >>>> > >> 2.999.9999.rc1.dev23, >>>> > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>>> building was >>>> > >> successful. >>>> > >> I don't knwo why this happens, could please support and >>>> advice the >>>> > >> solution for this issue. >>>> > >> >>>> > >> >>>> > >> Yipeng.He >>>> > >> >>>> > >> _______________________________________________ >>>> > >> 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 >>>> > >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>> s >>>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > From nicolae.jascanu at intel.com Thu Apr 23 10:06:52 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Thu, 23 Apr 2020 10:06:52 +0000 Subject: [Starlingx-discuss] =?windows-1252?q?Sanity_-_using_EB_for_Host_O?= =?windows-1252?q?penStack_Clients_and_services_Upgrade_to_=93Train=94?= Message-ID: Sanity Test using EB for Host OpenStack Clients and services Upgrade to “Train” http://dcp-dev.intel.com/pub/users-share/chenyan/train/engbuild/ 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 External - 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, STX Validation Team Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Thu Apr 23 13:46:11 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 23 Apr 2020 13:46:11 +0000 Subject: [Starlingx-discuss] StarlingX Weekly Build Meeting Agenda Message-ID: Agenda for today's build meeting: 1. Build layering cutover: - Docker layer sanity - Cutover production builds for tonight's build? 2. Build avoidance algorithm review: - Scott to present the algorithm (email sent April 16) - Team to decide if algorithm is sound or identify any potential issues 3. Other topics Zoom: https://zoom.us/j/342730236 Etherpad: https://etherpad.openstack.org/p/stx-build Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruediger.stock at intel.com Thu Apr 23 15:08:39 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Thu, 23 Apr 2020 15:08:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200422 Message-ID: Sanity Test from 2020-April-22 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200422T083809Z/outputs/iso/) 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 ] 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 External - 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 - 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 External - 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, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Apr 23 15:23:54 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 23 Apr 2020 15:23:54 +0000 Subject: [Starlingx-discuss] Production builds to cutover to using Layered Build Message-ID: During the community build meeting today we confirmed that layered builds are now ready to be fully enabled for the StarlingX project. In the next day or two the CENGN production builds will cutover to use layered builds exclusively and the monolithic builds will be retired. Developers can use either approach but the official daily builds from CENGN will now move to use layered builds. Scott and Nicolae will send out an additional email once this has been completed. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Apr 23 16:07:59 2020 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 23 Apr 2020 09:07:59 -0700 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSNOiDlm57lpI06IGVuYWJsZSBw?= =?utf-8?q?br_version?= In-Reply-To: <000a01d61922$8227fed0$8677fc70$@jitstack.com> References: <8bcac498-3c26-e09a-9d6d-944df9dcbfc4@linux.intel.com> <21008692-fe6b-3b65-ab7a-70b80f73ce78@linux.intel.com> <5f44d70a-c7bc-f57e-d541-989219af5b2f@linux.intel.com> <2a4d7b65-c52d-7bc5-9072-d4357e6d913d@linux.intel.com> <356ad3ca-b7df-af95-be78-03988e40c561@linux.intel.com> <002c01d618c0$e9e7ac30$bdb70490$@jitstack.com> <81b76ef7-c231-abde-9540-758f791d8469@linux.intel.com> <000a01d61922$8227fed0$8677fc70$@jitstack.com> Message-ID: On 4/22/20 8:51 PM, cherish.cao at jitstack.com wrote: > Hi Saul: > The code has been resubmitted in the old branch (https://review.opendev.org/#/c/710923/),in addition, do we need to discard or delete the newly created branch? > (https://review.opendev.org/#/c/720195/) > Yes, the 720195 review should be abandoned. Sau! > > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2020年4月23日 0:18 > 收件人: cherish.cao at jitstack.com; '何义鹏' > 抄送: 'chron.xie' ; 'starlingx-discuss' > 主题: Re: 回复: [Starlingx-discuss] enable pbr version > > Hi Cherish, > > Nice to hear from you again. > > See comments below > > On 4/22/20 9:13 AM, cherish.cao at jitstack.com wrote: >> Hi Saul: >> We have solved some problems related to PBR and submitted relevant codes. Due to Yipeng's limited proficiency of English, he handles the mails slowly. > I am glad to hear your working on this, I have reviewed and commented on all the changes submitted, the last change was last week, so I hope to see some updates soon. > >> I'm sorry about that. JITStack will continue to invest in PBR-related patches, please don't worry. >> After that, I've organized a team for the work related to PBR and ChornXie(chron.xie at jitstack.com) will join us in order to assist Yipeng to promote the work. Sorry again for the confusion. >> > I look forward to seeing the updates and will review them as soon as possible, this work is important and we would like to get it completed soon. > > Thanks again for your commitment to StarlingX > > Sau! > > >> In addition, do you have instant messaging software,like Wechat or something, I think this may speed up the promotion of PBR. >> >> Thanks >> Cherish.Cao >> >> -----邮件原件----- >> 发件人: Saul Wold >> 发送时间: 2020年4月22日 11:24 >> 收件人: 何义鹏 >> 抄送: 曹明晓 ; 桂来军 ; >> starlingx-discuss >> 主题: Re: [Starlingx-discuss] enable pbr version >> >> >> Hi Again Yipeng, >> >> I hope you are well, will you be able to continue working on PBR? Also maybe you could join us at the Distro call [0] in your evening. >> >> Sau! >> >> [0] >> https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_Pacific_-_Distr >> o_Non-OpenStack_Team_Call >> >> On 4/14/20 9:42 AM, Saul Wold wrote: >>> Yipeng, >>> >>> I hope you can join the Distro meeting in your evening tomorrow and >>> we can disuses this issue. >>> >>> Thanks >>> >>> Sau! >>> >>> >>> On 4/13/20 10:13 PM, Saul Wold wrote: >>>> Can you please provide more details about what you did and how you >>>> tried to create the ISO? >>>> >>>> The information here is not very helpful. Maybe the community >>>> members in China can help you get the build to work correctly. >>>> >>>> Sau! >>>> >>>> >>>> On 4/13/20 7:43 PM, 何义鹏 wrote: >>>>> >>>>> Hi Saul, >>>>> >>>>> I'm sorry it took so long to recover your mail. >>>>> >>>>> Recently, there was a problem when I modified according to the >>>>> method you provided under patch. >>>>> I tried to change all the versions in the patch of >>>>> starlingx-starboard to pbr_version. >>>>> But the result still failed to build iso. >>>>> >>>>> yipeng.he! >>>>> ------------------ Original ------------------ >>>>> *From: * "Saul Wold"; >>>>> *Date: * Wed, Apr 8, 2020 02:58 AM >>>>> *To: * "starlingx-discuss"; >>>>> "何 >>>>> 义 鹏"; >>>>> *Subject: * Re: [Starlingx-discuss] enable pbr version >>>>> >>>>> Hi Yipeng, >>>>> >>>>> Sorry for the delay in getting back to you, I was looking into the >>>>> build failure and trying understand how we handle the difference >>>>> between the PBR SemVer [0] and PEP440 [1]. Specifically when there >>>>> is a "Pre" tag like rc0, b1 such as 4.0.0.rc0. When PEP440 >>>>> normalizes that semver tag to create the egg-info versio it comes out as 4.0.0rc0.egg-info. >>>>> >>>>> So we need to also change the spec files %files section for the >>>>> egg-info file to wild-card that file instead of having a specific version listed. >>>>> >>>>> For example in the starlingx-dashboard spec file: >>>>> >>>>> diff --git a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>>> b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>>> index 7fbee65..399a9bd 100644 >>>>> --- a/starlingx-dashboard/centos/starlingx-dashboard.spec >>>>> +++ b/starlingx-dashboard/centos/starlingx-dashboard.spec >>>>> @@ -62,7 +62,7 @@ rm -rf $RPM_BUILD_ROOT >>>>> %files >>>>> %{python2_sitelib}/%{py_pkg_name} >>>>> >>>>> -%{python2_sitelib}/%{py_pkg_name}-%{version}*.egg-info >>>>> +%{python2_sitelib}/%{py_pkg_name}-*.egg-info >>>>> >>>>> %{enabled_dir} >>>>> %{stx_themes_dir} >>>>> >>>>> And as discussed in Jeremy's email we should be adding the "Sem-Ver: >>>>> feature" in the commit message, just once per repo. See Bin's >>>>> pending commit in fault [2]. You will have to back and fix fault >>>>> and other pending commits with the wild-card change for the >>>>> egg-info file in the spec file. >>>>> >>>>> Finally all PBR related reviews should have a >>>>> Depends-On: https://review.opendev.org/#/c/691632/ >>>>> >>>>> So it does not get merged before the enabling code in the build >>>>> tools merges. >>>>> >>>>> Hope this clarifies things and gets the PBR work unblocked. I am >>>>> going through the reviews and trying to provide some additional >>>>> review comments. >>>>> We can also talk about this tomorrow during the Distro call [3] >>>>> >>>>> Sau! >>>>> >>>>> >>>>> [0] https://docs.openstack.org/pbr/3.0.0/semver.html >>>>> [1] https://www.python.org/dev/peps/pep-0440/ >>>>> [2] https://review.opendev.org/#/c/691647/ >>>>> [3] >>>>> On 3/30/20 6:52 PM, 何义鹏 wrote: >>>>> > >>>>> > Saul! >>>>> > >>>>> > Thank you for your answer! But how should I use the semMem-ver tag? >>>>> > ------------------ Original ------------------ >>>>> > *From: * "Saul Wold"; >>>>> > *Date: * Sat, Mar 28, 2020 07:02 AM >>>>> > *To: * "何义鹏"; "Penney, >>>>> > Don"; "Scott >>>>> > Little"; "Miller, >>>>> > Frank"; >>>>> > *Cc: * "曹明晓"; "杨永金" >>>>> > ; "桂来军"; >>>>> > "starlingx-discuss"; >>>>> > *Subject: * Re: [Starlingx-discuss] enable pbr version >>>>> > Yipeng, >>>>> > >>>>> > >>>>> > I replied the other day, wanting to confirm if you have any >>>>> additional >>>>> > changes in your local git repo? It seems that we need to >>>>> consider a >>>>> > couple of options to possibly "pre-tag" 4.0 or use the "Sem_Ver: >>>>> > feature" tag in a commit to move the pbr versioning forward. >>>>> > >>>>> > BUILD Team (Don, Scott, Frank): >>>>> > >>>>> > Here's the general issue, we tag on the release branches, not >>>>> master >>>>> > (although we have a v3.0.0.rc0 tag on master), we need to >>>>> either add a >>>>> > Sem_Ver: feature tag to increment version's major number, or >>>>> add a >>>>> > pre-tag of the 4.0 release. >>>>> > >>>>> > Thoughts from the build team? I think we discussed part of the >>>>> before, >>>>> > but want to do a quick revisit of the thread back in Nov [1], I >>>>> think we >>>>> > had agreed to use Sem_Ver but it's not in the email thread >>>>> > >>>>> > >>>>> > [0] >>>>> > >>>>> http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November >>>>> / >>>>> 006790.html >>>>> >>>>> > >>>>> > >>>>> > On 3/26/20 7:26 PM, 何义鹏 wrote: >>>>> > > >>>>> > > Yes, building the rpm of the starlingx dashboard is a >>>>> necessary step for >>>>> > > my build-iso. >>>>> > > >>>>> > > Maybe Saul can respond to the question that python builds >>>>> allow several >>>>> > > versions of components. >>>>> > > >>>>> > Jeremy replied to this earlier in the week, the issue appears >>>>> to be the >>>>> > way we tagged rc0, we might need to have change our tagging. >>>>> He also >>>>> > stated that the number of components is not a limiting factor. >>>>> > >>>>> > Sau! >>>>> > > ------------------ Original ------------------ >>>>> > > *From: * "Penney, Don"; >>>>> > > *Date: * Wed, Mar 25, 2020 10:11 PM >>>>> > > *To: * "何义鹏"; "Saul >>>>> > > Wold(sgw at linux.intel.com)"; >>>>> > > *Cc: >>>>> > > >>>>> > >>>>> * >>>>> "'starlingx-discuss at lists.starlingx.io'(starlingx-discuss at lists.sta >>>>> r lingx.io)"; >>>>> >>>>> > >>>>> > > >>>>> > > *Subject: * RE: Re:RE: [Starlingx-discuss] enable pbr version >>>>> > > >>>>> > > Please keep starlingx-discuss on the receiver list. >>>>> > > >>>>> > > You had indicated build-iso was failing, but the build.log >>>>> you provided >>>>> > > appears to be the RPM build log for starlingx-dashboard. >>>>> > > >>>>> > > Processing files: >>>>> starlingx-dashboard-2.9999.9999.rc1.dev23-0.tis.noarch >>>>> > > >>>>> > > error: File not found: >>>>> > > >>>>> > >>>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>>> - >>>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>>> 9 >>>>> 999.9999.rc1.dev23*.egg-info >>>>> >>>>> > > >>>>> > > RPM build errors: >>>>> > > >>>>> > > File not found: >>>>> > > >>>>> > >>>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>>> - >>>>> 0.tis.x86_64/usr/lib/python2.7/site-packages/starlingx_dashboard-2. >>>>> 9 >>>>> 999.9999.rc1.dev23*.egg-info >>>>> >>>>> > > >>>>> > > Child return code was: 1 >>>>> > > >>>>> > > EXCEPTION: [Error()] >>>>> > > >>>>> > > Traceback (most recent call last): >>>>> > > >>>>> > > File >>>>> "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", >>>>> > > line 95, in trace >>>>> > > >>>>> > > result = func(*args, **kw) >>>>> > > >>>>> > > File "/usr/lib/python3.6/site-packages/mockbuild/util.py", >>>>> line 746, >>>>> > > in do_with_status >>>>> > > >>>>> > > raise exception.Error("Command failed: \n # %s\n%s" % >>>>> (command, >>>>> > > output), child.returncode) >>>>> > > >>>>> > > mockbuild.exception.Error: Command failed: >>>>> > > >>>>> > > # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 >>>>> --nodeps >>>>> > > /builddir/build/SPECS/starlingx-dashboard.spec >>>>> > > >>>>> > > Looking through the build.log, I see the following: >>>>> > > >>>>> > > Copying starlingx_dashboard.egg-info to >>>>> > > >>>>> > >>>>> build/bdist.linux-x86_64/wheel/starlingx_dashboard-2.9999.9999rc1.d >>>>> e >>>>> v23-py2.7.egg-info >>>>> >>>>> > > >>>>> > > So in the build, it’s creating the egg with the version set to >>>>> > > 2.9999.9999rc1.dev23, while the %files is expecting it to be >>>>> > > 2.9999.9999.rc1.dev23. >>>>> > > >>>>> > > Looking further through the build.log, there’s the following: >>>>> > > >>>>> > > + /usr/bin/python2 setup.py install -O1 --skip-build --root >>>>> > > >>>>> > >>>>> /builddir/build/BUILDROOT/starlingx-dashboard-2.9999.9999.rc1.dev23 >>>>> - >>>>> 0.tis.x86_64 >>>>> >>>>> > > >>>>> > > /usr/lib/python2.7/site-packages/setuptools/dist.py:355: >>>>> UserWarning: >>>>> > > Normalizing '2.9999.9999.rc1.dev23' to '2.9999.9999rc1.dev23' >>>>> > > >>>>> > > normalized_version, >>>>> > > >>>>> > > running install >>>>> > > >>>>> > > Maybe the python build only allows 4 version components? >>>>> > > >>>>> > > *From:*何义鹏[mailto:yipeng.he at jitstack.com] >>>>> > > *Sent:* Tuesday, March 24, 2020 9:59 PM >>>>> > > *To:* Penney, Don >>>>> > > *Subject:* Re:RE: [Starlingx-discuss] enable pbr version >>>>> > > >>>>> > > Hi Saul, >>>>> > > >>>>> > > I added the error log to the attachment. Do you need other >>>>> files for >>>>> > > analysis? >>>>> > > >>>>> > > Thank you for your help. >>>>> > > >>>>> > > yipeng.he! >>>>> > > >>>>> > > ------------------ Original ------------------ >>>>> > > >>>>> > > *From: * "Penney, Don"; >>>>> > > >>>>> > > *Date: * Wed, Mar 25, 2020 04:24 AM >>>>> > > >>>>> > > *To: * "Saul Wold"; "何义鹏" >>>>> > ; >>>>> > > >>>>> > > *Cc: * "桂来军"; "杨永金" >>>>> > > ; "曹明晓"; >>>>> > > "starlingx-discuss"; >>>>> > > >>>>> > > *Subject: * RE: [Starlingx-discuss] enable pbr version >>>>> > > >>>>> > > Hi Yipeng, >>>>> > > >>>>> > > Can you provide more info? What was the error you saw from >>>>> build-iso? >>>>> > > >>>>> > > >>>>> > > -----Original Message----- >>>>> > > From: Saul Wold [mailto:sgw at linux.intel.com] >>>>> > > Sent: Monday, March 23, 2020 6:45 PM >>>>> > > To: 何义鹏 >>>>> > > Cc: 桂来军; 杨永金; 曹明晓; starlingx-discuss >>>>> > > Subject: Re: [Starlingx-discuss] enable pbr version >>>>> > > >>>>> > > >>>>> > > Hi Yipeng, >>>>> > > >>>>> > > I was out last week on vacation, so I am catching up now. >>>>> > > >>>>> > > I think you would have to investigate build-iso and >>>>> associated scripts >>>>> > > and tools to see if there is an awk, sed or some other >>>>> command that is >>>>> > > not parsing the extended version. I have not investigated >>>>> this further, >>>>> > > that's my initial assessment. >>>>> > > >>>>> > > Can you be more specific about what the error is or provide >>>>> a log file >>>>> > > of the build-iso process? >>>>> > > >>>>> > > Thanks for working on this project. >>>>> > > >>>>> > > Sau! >>>>> > > >>>>> > > >>>>> > > >>>>> > > On 3/19/20 12:21 AM, 何义鹏wrote: >>>>> > >> Hello Saul >>>>> > >> >>>>> > >> I'm Yipeng He from JITStack, and I'm taking over the tasks >>>>> of PBR. >>>>> > >> I encountered the following issue when trying to build iso: >>>>> > >> It fails when the suffix of the version generated by the >>>>> PBR tool ended >>>>> > >> with number, for instance the building fails if the version >>>>> id is >>>>> > >> 2.999.9999.rc1.dev23, >>>>> > >> and when I replaced it with 2.999.9999.rc1.dev, the ISO >>>>> building was >>>>> > >> successful. >>>>> > >> I don't knwo why this happens, could please support and >>>>> advice the >>>>> > >> solution for this issue. >>>>> > >> >>>>> > >> >>>>> > >> Yipeng.He >>>>> > >> >>>>> > >> _______________________________________________ >>>>> > >> 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 >>>>> > >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>>>> s >>>>> >>>> >>>> _______________________________________________ >>>> 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 Fri Apr 24 01:00:41 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 24 Apr 2020 01:00:41 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meetng - Apr 23/2020 Message-ID: Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Tracking: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 - Upcoming Feature Merges: - Kata Container Rebase: 4/30 / Prime: Austin - Was waiting for kata release was available at 4/22. Expect this to be on track or close - Containerize Ceph - Rook Integration: 5/5 / Prime: Austin - Code complete / Code reviews are up. Requested cores to review - K8s & Container Components Upversion: 4/30 / Prime: Frank - calico, multus & k8s are upversioned and merged - Remaining: helm v3 - Kernel Upversion: 4/30 / Prime: Austin - https://review.opendev.org/#/q/topic:4.18_kernel+(status:open+OR+status:merged) - kernel-rt srprm issue is addressed - Code reviews are up. Looks on track - Upversion Openstack services on host to train: 4/17 / Prime: Yong - https://review.opendev.org/#/q/topic:train_upgrade+(status:open+OR+status:merged) - Code reviews are up and mostly approved. Looks on track - Flock Versioning: 4/30 / Prime: Saul - Still targeting this date - Layered Build: 4/15 / Prime: Frank - Cutover planned for this week. Remaining items wrapping up by next week. Forecasted to May 1. - Test Status - Hardware arrived in Romania - Team is working on system setup now; configured AIO-DX and working on the first external storage setup next From ruediger.stock at intel.com Fri Apr 24 15:09:05 2020 From: ruediger.stock at intel.com (Stock, Ruediger) Date: Fri, 24 Apr 2020 15:09:05 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200423 Message-ID: Sanity Test from 2020-April-24 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200423T084814Z/outputs/iso/) Status: RED All bare metal tests were affected by a required update to defaultbackend:1.4. As this version was not available in our mirror the builds failed. We triggered a new test cycle. Regards, STX Validation Team Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Apr 24 15:23:42 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 24 Apr 2020 08:23:42 -0700 Subject: [Starlingx-discuss] How to create gerrit search queries In-Reply-To: References: Message-ID: Cores: As a follow up to my gentle reminder for, this is what I do to check my pending reviews. I edit my gerrit preferences [0], the bottom of that page has a "My Menu" which you can then add or delete items that show up on the top menu when you select "My". The list starts with Changes, Draft Comments, Edits, ... You can create a URL, which is actually the search query such as follows: This is my default reviews page: #/q/(p:starlingx/tools+OR+p:starlingx/root+OR+p:starlingx/specs+OR+p:starlingx/integ+OR+p:starlingx/manifest+OR+p:starlingx/zuul-jobs+OR+p:starlingx/compile+OR+p:starlingx/config-files+OR+p:starlingx/utilities+OR+p:starlingx/kernel)+AND+is:open This example is for all StarlingX projects with a specific topic (PBR) #/q/projects:starlingx+AND+topic:pbr You can get more information from the search documentation [1]. I hope this help you all. Sau! [0] https://review.opendev.org/#/settings/preferences [1] https://review.opendev.org/Documentation/user-search.html On 4/22/20 8:06 AM, Zvonar, Bill wrote: > From today's meeting... > > * Standing Topics > > * Sanity > > * Monolithic > * 20200415 Red > * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008306.html > * will queue this up to discuss next week, re: RCA > * 20200416 Red > * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008320.html > * related to Kubernetes 1.18? > * ditto re: RCA next week > * 20200417 Green > * 20200421 Red > * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008365.html > * due to build tool change - this has been fixed, it's in today's build > > * Layered > * 20200418 Green > * no other sanities since last week > * feels like we're closing to being able to cut over to Layered Builds as default - target is to do this week (Thu) > > * Gerrit Reviews in Need of Attention > > * ceph containerization > https://review.opendev.org/#/c/716792/ > https://review.opendev.org/#/c/721443/ > https://review.opendev.org/#/c/714857/ > https://review.opendev.org/#/c/713084/ > https://review.opendev.org/#/c/721785/ > https://review.opendev.org/#/c/720637/ > https://review.opendev.org/#/c/721765/ > > * Saul provided a gentle reminder to the cores to review their queues at least once daily > * Don suggested sending this gentle reminder to the discuss list - AR: Bill > > * CentOS 8 Kernel Upgrade Plan > > * sanity ran ok with kernel in new repo > * working to adopot the pre-built srpm, might be at risk for end of month, but still going for it > > * Topics for this Week > > * Core Reviewer Nominations: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008328.html > * all 3 approved > * Saul will update the core reviewers files (and remove any lingering GDC names) > > * Maintenance Releases for stx.2.0 & stx.3.0 -- Bruce & Ghada > * A # of fixes were sourced in the branches. Test teams are resource constrained to test mtce releases. > * Is there a need in the community to release these mtce releases? Any timeline requests? > * no comments here - Ghada will send the question out on the mailing list > > * Running Sanity in the Open - minimum requirements > * 1 VM for Simplex > * bootable via PXE or other network boot protocols from a Cengn binary - if physical machine > * for VM, provide a QCOW2 image - need to sort out how frequently we do this & what config - more to discuss > * Bill to follow up > > * Adding Bandit to additional repos and packages: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008367.html > * didn't get to this this week, Saul will follow up on mailing list, will put it on next week's agenda if required > > * ARs from Previous Meetings > > * 4/15 > * layered build - validating docker images (Scott/Nic) - to be discussed in Build meeting tomorrow > * manually updating version info (Build team + Bart) > * home for pre-built srpms (Scott, Austin) > > * Open Requests for Help > * problems with installing starlingx 3.0 in bare metal: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008360.html > > > -----Original Message----- > From: Zvonar, Bill > Sent: Tuesday, April 21, 2020 7:46 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Community (& TSC) Call (Apr 22, 2020) > > Hi all, reminder of tomorrow's TSC/Community call. > > As usual, we'll start with TSC business, then we'll move on to the Community call. > > Please feel free to add items to the agenda [0] for the Community call beforehand - the following items are on the agenda now: > > - Core Reviewer Nominations > - Maintenance Releases for stx.2.0 & stx.3.0 > - Running Sanity in the Open > - Adding Bandit to additional repos and packages > > 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=20200422T1400 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From fungi at yuggoth.org Fri Apr 24 15:47:37 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 24 Apr 2020 15:47:37 +0000 Subject: [Starlingx-discuss] How to create gerrit search queries In-Reply-To: References: Message-ID: <20200424154737.dff6h2dkpw5jmrpp@yuggoth.org> You might also be interested in: https://pypi.org/project/gerrit-dash-creator -- 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 scott.little at windriver.com Fri Apr 24 17:24:37 2020 From: scott.little at windriver.com (Scott Little) Date: Fri, 24 Apr 2020 13:24:37 -0400 Subject: [Starlingx-discuss] [Important] Production builds to cutover to using Layered Build In-Reply-To: References: Message-ID: <2ec8e30d-0d87-d9b1-edac-8990a10cf831@windriver.com> The following changes have been made 1) The layered build have been given the preferred build time of 7pm EST (with docker images), or 9:30pm EST (without docker images).  The goal is testable content ready by 1am EST. 2) Latest developer iso image will be found at ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_build/outputs/iso/bootimage.iso http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/latest_green_build/outputs/iso/bootimage.iso 3) The old path, formerly used by monolithic builds, will redirect to the new path.  So this still works ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/bootimage.iso http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/iso/bootimage.iso 4) Docker images are now produced by a fourth build layer, 'containers'. We will continue to build these weekly, rather than daily.  The Helm charts for the latest set of docker images will be found at ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/latest_docker_image_build/outputs/helm-charts/ 5) The old path, formerly used by monolithic builds, will redirect to the new path.  So this still works ... http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/helm-charts/ 6) We don't yet have a 'latest_green_docker_image_build' redirect just yet, but hope to have that working soon. 7) The monolithic build will continue for a time, with builds starting at 4am EST.  These builds will not produce docker images unless a special request is made.   The publication url has moved to http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/latest_build/outputs/iso/bootimage.iso 8) Regular sanity testing will done on the output of the layered build, not the monolithic build. Scott On 2020-04-23 11:23 a.m., Miller, Frank wrote: > During the community build meeting today we confirmed that layered > builds are now ready to be fully enabled for the StarlingX project.  > In the next day or two the CENGN production builds will cutover to use > layered builds exclusively and the monolithic builds will be retired. > Developers can use either approach but the official daily builds from > CENGN will now move to use layered builds. > > Scott and Nicolae will send out an additional email once this has been > completed. > > Frank > > > _______________________________________________ > 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 sgw at linux.intel.com Fri Apr 24 18:19:35 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 24 Apr 2020 11:19:35 -0700 Subject: [Starlingx-discuss] How to create gerrit search queries In-Reply-To: <20200424154737.dff6h2dkpw5jmrpp@yuggoth.org> References: <20200424154737.dff6h2dkpw5jmrpp@yuggoth.org> Message-ID: <9a304220-fe5a-70b3-8751-45e3c4f6e268@linux.intel.com> Folks, Here is the full StarlingX Review Inbox definition [0] which results in this page [1]. You can use the tool Jeremy shared to build a dashboard based on the above definition for the repos you watch. Thought this might help. Sau! [0] https://gerrit-dash-creator.readthedocs.io/en/latest/dashboards/dashboard_starlingx.html [1] https://review.opendev.org/#/dashboard/?title=StarlingX+Review+Inbox&foreach=%28%0Aproject%3Astarlingx%2Fansible%2Dplaybooks+OR%0Aproject%3Astarlingx%2Fclients+OR%0Aproject%3Astarlingx%2Fcompile+OR%0Aproject%3Astarlingx%2Fconfig+OR%0Aproject%3Astarlingx%2Fconfig%2Dfiles+OR%0Aproject%3Astarlingx%2Fcontainers+OR%0Aproject%3Astarlingx%2Fdistcloud+OR%0Aproject%3Astarlingx%2Fdistcloud%2Dclient+OR%0Aproject%3Astarlingx%2Fdocs+OR%0Aproject%3Astarlingx%2Felection+OR%0Aproject%3Astarlingx%2Ffault+OR%0Aproject%3Astarlingx%2Fgovernance+OR%0Aproject%3Astarlingx%2Fgui+OR%0Aproject%3Astarlingx%2Fha+OR%0Aproject%3Astarlingx%2Fhelm%2Dcharts+OR%0Aproject%3Astarlingx%2Finteg+OR%0Aproject%3Astarlingx%2Fmanifest+OR%0Aproject%3Astarlingx%2Fmetal+OR%0Aproject%3Astarlingx%2Fmonitor%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fmonitoring+OR%0Aproject%3Astarlingx%2Fnfv+OR%0Aproject%3Astarlingx%2Fopenstack%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fplatform%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Froot+OR%0Aproject%3Astarlingx%2Fspecs+OR%0Aproject%3Astarlingx%2Fstx%2Dpuppet+OR%0Aproject%3Astarlingx%2Ftest+OR%0Aproject%3Astarlingx%2Ftools+OR%0Aproject%3Astarlingx%2Fupdate+OR%0Aproject%3Astarlingx%2Fupstream+OR%0Aproject%3Astarlingx%2Futilities+OR%0Aproject%3Astarlingx%2Fzuul%2Djobs%0A%29%0Astatus%3Aopen%0ANOT+owner%3Aself%0ANOT+label%3AWorkflow%3C%3D%2D1%0Alabel%3AVerified%3E%3D1%2Czuul%0ANOT+reviewedby%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d On 4/24/20 8:47 AM, Jeremy Stanley wrote: > You might also be interested in: > > https://pypi.org/project/gerrit-dash-creator > > > _______________________________________________ > 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 Apr 24 18:52:07 2020 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 24 Apr 2020 11:52:07 -0700 Subject: [Starlingx-discuss] How to create gerrit search queries In-Reply-To: <9a304220-fe5a-70b3-8751-45e3c4f6e268@linux.intel.com> References: <20200424154737.dff6h2dkpw5jmrpp@yuggoth.org> <9a304220-fe5a-70b3-8751-45e3c4f6e268@linux.intel.com> Message-ID: <5540a5e3-2fc5-f808-c7bf-177c66bd8e41@linux.intel.com> I guess one more thing, the bottom of that page has "Wayward Changes" some quite old! Maybe if they don't get some looking at by the next community meeting, we can review the list then. Sau! On 4/24/20 11:19 AM, Saul Wold wrote: > > Folks, > > Here is the full StarlingX Review Inbox definition [0] which results in > this page [1]. You can use the tool Jeremy shared to build a dashboard > based on the above definition for the repos you watch. > > Thought this might help. > > Sau! > > [0] > https://gerrit-dash-creator.readthedocs.io/en/latest/dashboards/dashboard_starlingx.html > > > [1] > https://review.opendev.org/#/dashboard/?title=StarlingX+Review+Inbox&foreach=%28%0Aproject%3Astarlingx%2Fansible%2Dplaybooks+OR%0Aproject%3Astarlingx%2Fclients+OR%0Aproject%3Astarlingx%2Fcompile+OR%0Aproject%3Astarlingx%2Fconfig+OR%0Aproject%3Astarlingx%2Fconfig%2Dfiles+OR%0Aproject%3Astarlingx%2Fcontainers+OR%0Aproject%3Astarlingx%2Fdistcloud+OR%0Aproject%3Astarlingx%2Fdistcloud%2Dclient+OR%0Aproject%3Astarlingx%2Fdocs+OR%0Aproject%3Astarlingx%2Felection+OR%0Aproject%3Astarlingx%2Ffault+OR%0Aproject%3Astarlingx%2Fgovernance+OR%0Aproject%3Astarlingx%2Fgui+OR%0Aproject%3Astarlingx%2Fha+OR%0Aproject%3Astarlingx%2Fhelm%2Dcharts+OR%0Aproject%3Astarlingx%2Finteg+OR%0Aproject%3Astarlingx%2Fmanifest+OR%0Aproject%3Astarlingx%2Fmetal+OR%0Aproject%3Astarlingx%2Fmonitor%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fmonitoring+OR%0Aproject%3Astarlingx%2Fnfv+OR%0Aproject%3Astarlingx%2Fopenstack%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Fplatform%2Darmada%2Dapp+OR%0Aproject%3Astarlingx%2Froot+OR%0Aproject%3Astarlingx%2Fspecs+OR%0Aproject%3Astarlingx%2Fstx%2Dpuppet+OR%0Aproject%3Astarlingx%2Ftest+OR%0Aproject%3Astarlingx%2Ftools+OR%0Aproject%3Astarlingx%2Fupdate+OR%0Aproject%3Astarlingx%2Fupstream+OR%0Aproject%3Astarlingx%2Futilities+OR%0Aproject%3Astarlingx%2Fzuul%2Djobs%0A%29%0Astatus%3Aopen%0ANOT+owner%3Aself%0ANOT+label%3AWorkflow%3C%3D%2D1%0Alabel%3AVerified%3E%3D1%2Czuul%0ANOT+reviewedby%3Aself&Needs+final+%2B2=label%3ACode%2DReview%3E%3D2+limit%3A50+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself&Passed+Zuul%2C+No+Negative+Feedback+%28Small+Fixes%29=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3C%3D10&Passed+Zuul%2C+No+Negative+Feedback=NOT+label%3ACode%2DReview%3E%3D2+NOT+label%3ACode%2DReview%3C%3D%2D1%2Cstarlingx%2Dcore+delta%3A%3E10&Needs+Feedback+%28Changes+older+than+5+days+that+have+not+been+reviewed+by+anyone%29=NOT+label%3ACode%2DReview%3C%3D%2D1+NOT+label%3ACode%2DReview%3E%3D1+age%3A5d&You+are+a+reviewer%2C+but+haven%27t+voted+in+the+current+revision=NOT+label%3ACode%2DReview%3C%3D%2D1%2Cself+NOT+label%3ACode%2DReview%3E%3D1%2Cself+reviewer%3Aself&Wayward+Changes+%28Changes+with+no+code+review+in+the+last+2days%29=NOT+is%3Areviewed+age%3A2d > > > On 4/24/20 8:47 AM, Jeremy Stanley wrote: >> You might also be interested in: >> >>      https://pypi.org/project/gerrit-dash-creator >> >> >> _______________________________________________ >> 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 maryx.camp at intel.com Fri Apr 24 20:56:47 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 24 Apr 2020 20:56:47 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-22 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-22 * All -- reviews merged since last week: 2 * All -- bug status -- 7 total, 2 oldies, 5 current * [new ww17] Debug guide, Install guide typo * [ww16] Kata containers and Build Avoidance (AR Mary compare bug text to existing guide text here: https://docs.starlingx.io/developer_resources/build_guide.html#build-avoidance) * [ww15] Backup & restore procedure info, review here: https://review.opendev.org/#/c/721772/ * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Assignment of R4 doc tasks ? These stories have no assigned person: * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) Poornima has volunteered for this. Mary assigned her in StoryBoard. * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) AR Mary check discuss archive, may be covered already? If not ask Tao Liu. * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) AR Mary ask Dariush (reference the story) Do we need doc updates? * All -- Opens * Poornima Y. N. joined to discuss her doc review to modify the build guide (https://review.opendev.org/#/c/721517/). She also volunteered to write the layered build guide (see StoryBoard assignment above) * Greg brought up the installation guides - are they being used? are they good? Details in [2]. * Greg had another question: what about the remainder of the doc set? People are raising Launchpads for new features, which is what we want. Details in [2]. * Reviews in progress: * Upgrade Kubernetes version (R4 new content) -- Review available: https://review.opendev.org/#/c/712583/ * STX IPv6 deployment https://review.opendev.org/#/c/718302/ AR Mary email Joseph Richard directly and ask him for input. * WIP Docker proxy setup Priority 1 task Details in [2]. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hu.tianhao at 99cloud.net Sun Apr 26 09:19:19 2020 From: hu.tianhao at 99cloud.net (=?UTF-8?B?6IOh5aSp5piK?=) Date: Sun, 26 Apr 2020 17:19:19 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?Can=27t_reboot/shutdown_VMs=2E?= Message-ID: Hi all, I create some VMs on openstack for stx3.0. And I cannot reboot/shutdown VMs from either dashboard or cli. This is log from nova-api-proxy pod: 2020-04-26 07:55:24,632.632 6 INFO nova_api_proxy.apps.acceptor [-] reboot 2020-04-26 07:55:24,633.633 6 INFO nova_api_proxy.apps.acceptor [-] type : SOFT 2020-04-26 07:55:24,633.633 6 INFO nova_api_proxy.apps.acceptor [-] POST request issued by user (admin) tenant (admin) remote address (172.16.2.145) "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/125f4586-17a5-4358-9110-04c518cc9a92/action" 2020-04-26 07:55:24,633.633 6 INFO nova_api_proxy.apps.acceptor [-] Forward to NFV "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/125f4586-17a5-4358-9110-04c518cc9a92/action", action: (reboot), val:({u'type': u'SOFT'}) 2020-04-26 07:55:24,636.636 6 INFO nova_api_proxy.apps.proxy [-] POST response body: ['\r\n400 The plain HTTP request was sent to HTTPS port\r\n\r\n

400 Bad Request

\r\n
The plain HTTP request was sent to HTTPS port
\r\n
nginx
\r\n\r\n\r\n'] 2020-04-26 07:57:22,882.882 6 INFO nova_api_proxy.apps.acceptor [-] reboot 2020-04-26 07:57:22,883.883 6 INFO nova_api_proxy.apps.acceptor [-] type : SOFT 2020-04-26 07:57:22,883.883 6 INFO nova_api_proxy.apps.acceptor [-] POST request issued by user (admin) tenant (admin) remote address (172.16.2.145) "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/8498e70d-8fb6-44f9-974a-14bfa9ef6288/action" 2020-04-26 07:57:22,883.883 6 INFO nova_api_proxy.apps.acceptor [-] Forward to NFV "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/8498e70d-8fb6-44f9-974a-14bfa9ef6288/action", action: (reboot), val:({u'type': u'SOFT'}) 2020-04-26 07:57:22,885.885 6 INFO nova_api_proxy.apps.proxy [-] POST response body: ['\r\n400 The plain HTTP request was sent to HTTPS port\r\n\r\n

400 Bad Request

\r\n
The plain HTTP request was sent to HTTPS port
\r\n
nginx
\r\n\r\n\r\n'] 2020-04-26 08:38:23,794.794 6 INFO nova_api_proxy.apps.acceptor [-] reboot 2020-04-26 08:38:23,799.799 6 INFO nova_api_proxy.apps.acceptor [-] type : SOFT 2020-04-26 08:38:23,799.799 6 INFO nova_api_proxy.apps.acceptor [-] POST request issued by user (admin) tenant (admin) remote address (172.16.2.145) "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/8498e70d-8fb6-44f9-974a-14bfa9ef6288/action" 2020-04-26 08:38:23,801.801 6 INFO nova_api_proxy.apps.acceptor [-] Forward to NFV "POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/8498e70d-8fb6-44f9-974a-14bfa9ef6288/action", action: (reboot), val:({u'type': u'SOFT'}) 2020-04-26 08:38:23,832.832 6 INFO nova_api_proxy.apps.proxy [-] POST response body: ['\r\n400 The plain HTTP request was sent to HTTPS port\r\n\r\n

400 Bad Request

\r\n
The plain HTTP request was sent to HTTPS port
\r\n
nginx
\r\n\r\n\r\n'] And when I try to stop VM from cli("openstack server stop xxx"), this error occurs: Starting new HTTP connection (1): nova-api-proxy.openstack.svc.cluster.local http://nova-api-proxy.openstack.svc.cluster.local:8774 "GET /v2.1/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a HTTP/1.1" 200 1688 RESP: [200] Connection: keep-alive Content-Length: 1688 Content-Type: application/json Date: Sun, 26 Apr 2020 09:15:11 GMT Openstack-Api-Version: compute 2.1 Vary: OpenStack-API-Version, X-OpenStack-Nova-API-Version X-Compute-Request-Id: req-66b83d55-3013-4b01-9b0b-ace29cf45813 X-Openstack-Nova-Api-Version: 2.1 X-Openstack-Request-Id: req-66b83d55-3013-4b01-9b0b-ace29cf45813 RESP BODY: {"server": {"OS-EXT-STS:task_state": null, "addresses": {"public-net0": [{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:4a:4c:63", "version": 4, "addr": "192.168.101.42", "OS-EXT-IPS:type": "fixed"}]}, "links": [{"href": "http://nova-api.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a", "rel": "self"}, {"href": "http://nova-api.openstack.svc.cluster.local:8774/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a", "rel": "bookmark"}], "image": "", "OS-EXT-STS:vm_state": "active", "OS-EXT-SRV-ATTR:instance_name": "instance-0000000e", "OS-SRV-USG:launched_at": "2020-04-26T09:06:51.000000", "flavor": {"id": "88d9d1c3-9d3f-400f-9833-bc9a961581a1", "links": [{"href": "http://nova-api.openstack.svc.cluster.local:8774/d27de62f56b84376b5de5e50069dfa86/flavors/88d9d1c3-9d3f-400f-9833-bc9a961581a1", "rel": "bookmark"}]}, "id": "e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a", "security_groups": [{"name": "default"}], "user_id": "9781ba055b664b88bc0d81efa8385a0a", "OS-DCF:diskConfig": "AUTO", "accessIPv4": "", "accessIPv6": "", "progress": 0, "OS-EXT-STS:power_state": 1, "OS-EXT-AZ:availability_zone": "nova", "config_drive": "", "status": "ACTIVE", "updated": "2020-04-26T09:06:51Z", "hostId": "ed5b6f56f20a881943d21c2c5c5b438bfc474ad968c2129652789499", "OS-EXT-SRV-ATTR:host": "controller-0", "OS-SRV-USG:terminated_at": null, "key_name": null, "OS-EXT-SRV-ATTR:hypervisor_hostname": "controller-0", "name": "test", "created": "2020-04-26T09:06:08Z", "tenant_id": "d27de62f56b84376b5de5e50069dfa86", "os-extended-volumes:volumes_attached": [{"id": "0e6068c3-2b43-4786-8caf-3e508d746421"}], "metadata": {}}} GET call to compute for http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a used request id req-66b83d55-3013-4b01-9b0b-ace29cf45813 REQ: curl -g -i -X POST http://nova-api-proxy.openstack.svc.cluster.local:8774/v2.1/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a/action -H "Accept: application/json" -H "Content-Type: application/json" -H "User-Agent: python-novaclient" -H "X-Auth-Token: {SHA256}2924d2898529a443db522ba7e087d34d55c1a1816a618c6fcd2b15650466fc38" -H "X-OpenStack-Nova-API-Version: 2.1" -d '{"os-stop": null}' http://nova-api-proxy.openstack.svc.cluster.local:8774 "POST /v2.1/d27de62f56b84376b5de5e50069dfa86/servers/e1ef4f18-6fc3-40ca-ae4f-fa7f263f2f2a/action HTTP/1.1" 400 248 RESP: [400] Connection: keep-alive Content-Length: 248 Content-Type: text/html Date: Sun, 26 Apr 2020 09:15:11 GMT Server: nginx RESP BODY: Omitted, Content-Type is set to text/html. Only application/json responses have their bodies logged. Bad request (HTTP 400) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cliff/app.py", line 402, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python2.7/site-packages/osc_lib/command/command.py", line 41, in run return super(Command, self).run(parsed_args) File "/usr/lib/python2.7/site-packages/cliff/command.py", line 184, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python2.7/site-packages/openstackclient/compute/v2/server.py", line 2347, in take_action server, File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 175, in stop return self.manager.stop(self) File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 1049, in stop resp, body = self._action_return_resp_and_body('os-stop', server, None) File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 2023, in _action_return_resp_and_body return self.api.client.post(url, body=body) File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 381, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) BadRequest: Bad request (HTTP 400) clean_up StopServer: Bad request (HTTP 400) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 135, in run ret_val = super(OpenStackShell, self).run(argv) File "/usr/lib/python2.7/site-packages/cliff/app.py", line 281, in run result = self.run_subcommand(remainder) File "/usr/lib/python2.7/site-packages/osc_lib/shell.py", line 175, in run_subcommand ret_value = super(OpenStackShell, self).run_subcommand(argv) File "/usr/lib/python2.7/site-packages/cliff/app.py", line 402, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python2.7/site-packages/osc_lib/command/command.py", line 41, in run return super(Command, self).run(parsed_args) File "/usr/lib/python2.7/site-packages/cliff/command.py", line 184, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python2.7/site-packages/openstackclient/compute/v2/server.py", line 2347, in take_action server, File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 175, in stop return self.manager.stop(self) File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 1049, in stop resp, body = self._action_return_resp_and_body('os-stop', server, None) File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 2023, in _action_return_resp_and_body return self.api.client.post(url, body=body) File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 381, in post return self.request(url, 'POST', **kwargs) File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 78, in request raise exceptions.from_response(resp, body, url, method) BadRequest: Bad request (HTTP 400) Can anyone give some advice on this problem? Thanks, Tianhao -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Apr 27 17:02:22 2020 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 27 Apr 2020 17:02:22 +0000 Subject: [Starlingx-discuss] [Release] Soliciting feedback on next stx maintenance releases Message-ID: Hello all, The release team is trying to assess the need for issuing maintenance releases for stx.2.0 & stx.3.0. The last stx.2.0 release (stx.2.0.2) was released in October 2019. The last stx.3.0 release (stx.3.0) was release in December 2019. Since then there have been a number of fixes sourced in both release branches to address bugs and vulnerabilities (see [1] & [2] below). Due to community resourcing constraints (especially in the test teams) and the focus on stx.4.0, we have not been able to schedule maintenance releases. If you are actively using stx.2.0 or stx.3.0 and have a strong need for a maintenance release, please let us know what release time-line is needed to meet your plans. Please also note that in the meantime you can build your own load from the appropriate release branch. [1] stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 [2] stx.3.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 Regards, Ghada, Bruce & Bill PS: From nicolae.jascanu at intel.com Mon Apr 27 17:13:59 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Mon, 27 Apr 2020 17:13:59 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Message-ID: Sanity Test from 2020-April-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200426T020107Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We raised a bug: Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Mon Apr 27 17:41:39 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Mon, 27 Apr 2020 19:41:39 +0200 Subject: [Starlingx-discuss] Virtual PTG preparations - ACTION NEEDED In-Reply-To: <8D9FA3C1-E0CA-48E6-A319-19482BD1123A@gmail.com> References: <8D9FA3C1-E0CA-48E6-A319-19482BD1123A@gmail.com> Message-ID: Hi StarlingX Community, It is a friendly reminder to please put discussion topics into the PTG etherpad so that we can estimate the time needed to discuss them. Also please sign up if you are interested in attending and add the region you will be in at the time of the event (June 1-5) to pick the time slots that fit best. The etherpad link: https://etherpad.opendev.org/p/stx-virtual-PTG-June Thanks, Ildikó > On Apr 22, 2020, at 19:52, Ildiko Vancsa wrote: > > Hi StarlingX Community, > > It is time to start building the agenda for the virtual PTG[1] that will happen in June 1-5 and book time slots the community would like to use. > > We need to decide how much time the community would like to use __in total__. We can book slots accordingly throughout the week with no more than __4 hours per day (in UTC hours)__. > > I created an etherpad[2] to throw in agenda items and time estimates. __Please add items and time estimates to the etherpad as soon as possible__. > > I also added an attendee section to the etherpad. Please __sign up and add your region__ based on where you’re located/will be at the time of the virtual PTG. The options are Americas, EMEA, APAC. With adding the regions it helps narrowing down which time blocks we should aim for to find the slots that work for the most. > > Please let me know if you have any questions. > > Thanks, > Ildikó > > [1] http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008296.html > [2] https://etherpad.opendev.org/p/stx-virtual-PTG-June > > From kennelson11 at gmail.com Mon Apr 27 17:48:27 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 27 Apr 2020 10:48:27 -0700 Subject: [Starlingx-discuss] Fwd: [all] Virtual PTG Tooling Requirements & Suggestions In-Reply-To: References: Message-ID: Hello Everyone :) We want to get your input on tooling for the PTG. We have a general idea of what we have for requirements, but wanted to get the community's input- i.e. make sure we aren't missing any. Here is the list of requirements we have right now[1]. Also, if anyone has suggestions of tools that meet these criteria, we would love to hear them! We are gathering and vetting options for the event and want to make sure nothing gets overlooked. -the Kendalls (diablo_rojo & wendallkaters) [1] https://etherpad.opendev.org/p/virt-ptg-requirements -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Apr 27 20:07:43 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 27 Apr 2020 20:07:43 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: The next containerization meeting is scheduled for Tuesday Apr 28th. Agenda: 1. STX 4.0 features: Kata containers [2006145] -- Shuicheng Lin - Upgrade kata to include IPv6 fixes - Documentation for config and usage of kata containers in STX Upversion container components [2006999] -- Bob Church - What components were upversioned? - Can this story be marked complete this week? Add support for Helm v3 [2007000] - Jim Gauld - Have Shuichecng's commits merged? Or what is plan for Shuicheng commits vs overlap with this SB commits? - Remaining work items/forecast for final commits up for review? Decouple container applications from platform [2006537] -- Bob Church - Update on issue with sysinv priveleges vs root priveleges - Other work items? Encrypting K8s Secret Data at Rest [2007243] -- Greg - Brief description of this story - Is the story compelte for stx4.0? Can it be accepted? Create HELM chart for Fault project [2004008] -- Saul or Bangalore team - How is the implementation of Tyler's horizon plugin proposal from Feb 18 going? - After the plugin proposal is implemented, fault containerization can be enabled. Is this still planned for stx4.0? Note: CEPH containerization is covered in the Wednesday distro.nonopenstack meeting. 2. Other topics? - Any critical or very high priority LPs? - tbd Etherpad: https://etherpad.openstack.org/p/stx-containerization Call details: zoom link: 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: 3450 bytes Desc: not available URL: From austin.sun at intel.com Tue Apr 28 05:14:00 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 28 Apr 2020 05:14:00 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting --Cancelled for April 29th Message-ID: StarlingX Community: I have to cancel April 29th non-OpenStack distro meeting . if any topic, we can discuss via mail list. Next meeting will be held on May 6th. Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Tue Apr 28 05:28:03 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Tue, 28 Apr 2020 05:28:03 +0000 Subject: [Starlingx-discuss] =?iso-8859-1?q?=5BURL_wurde_ver=E4ndert=5D__F?= =?iso-8859-1?q?wd=3A_=5Ball=5D_Virtual_PTG_Tooling_Requirements_=26_Sugge?= =?iso-8859-1?q?stions?= In-Reply-To: References: , Message-ID: hi, checkout BigBlueButton: https://bigbluebutton.org/ volker. ________________________________ Von: Kendall Nelson [kennelson11 at gmail.com] Gesendet: Montag, 27. April 2020 19:48 An: starlingx-discuss at lists.starlingx.io Betreff: [URL wurde verändert] [Starlingx-discuss] Fwd: [all] Virtual PTG Tooling Requirements & Suggestions Externe E-Mail! Öffnen Sie nur Links oder Anhänge von vertrauenswürdigen Absendern! Hello Everyone :) We want to get your input on tooling for the PTG. We have a general idea of what we have for requirements, but wanted to get the community's input- i.e. make sure we aren't missing any. Here is the list of requirements we have right now[1]. Also, if anyone has suggestions of tools that meet these criteria, we would love to hear them! We are gathering and vetting options for the event and want to make sure nothing gets overlooked. -the Kendalls (diablo_rojo & wendallkaters) [1] http://Achtung/https://etherpad.opendev.org/p/virt-ptg-requirements -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Tue Apr 28 05:47:49 2020 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Tue, 28 Apr 2020 05:47:49 +0000 Subject: [Starlingx-discuss] [Release] Soliciting feedback on next stx maintenance releases In-Reply-To: References: Message-ID: hi! i'm currently running v3.0, beside the missing swift feature all is running fine. but if i understand you in the right way, STX may provide a patch-able-update package to deploy all the updates? in my way, this is not realy needed, STX 4.0 is right now comming up. my hope is that i can update from v3 to v4 without having to reinstall the whole stack?! I already operate the stack in productive use... volker. ________________________________________ Von: Khalil, Ghada [Ghada.Khalil at windriver.com] Gesendet: Montag, 27. April 2020 19:02 An: starlingx-discuss at lists.starlingx.io Betreff: [URL wurde verändert] [Starlingx-discuss] [Release] Soliciting feedback on next stx maintenance releases Externe E-Mail! Öffnen Sie nur Links oder Anhänge von vertrauenswürdigen Absendern! Hello all, The release team is trying to assess the need for issuing maintenance releases for stx.2.0 & stx.3.0. The last stx.2.0 release (stx.2.0.2) was released in October 2019. The last stx.3.0 release (stx.3.0) was release in December 2019. Since then there have been a number of fixes sourced in both release branches to address bugs and vulnerabilities (see [1] & [2] below). Due to community resourcing constraints (especially in the test teams) and the focus on stx.4.0, we have not been able to schedule maintenance releases. If you are actively using stx.2.0 or stx.3.0 and have a strong need for a maintenance release, please let us know what release time-line is needed to meet your plans. Please also note that in the meantime you can build your own load from the appropriate release branch. [1] stx.2.0 branch: http://Achtung/https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 [2] stx.3.0 branch: http://Achtung/https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.3.0 Regards, Ghada, Bruce & Bill PS: _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://Achtung/http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue Apr 28 08:34:32 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 28 Apr 2020 08:34:32 +0000 Subject: [Starlingx-discuss] FW: [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Andy: I deployed dist-cloud in virtual env based on 20200414, but openstack application on subcloud deployed failed . >From cinder-api po logs: >: Failed to establish a new connection: [Errno -2] Name or service not known',)): ConnectFailure: Unable to establish connection to http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3/auth/tokens: HTTPConnectionPool(host='keystone-admin.openstack.svc.cluster.subcloud1', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) This keystone-admin.openstack.svc.cluster.subcloud1 can not be found in subcloud1 controllers This url seems override from helm keystone: host_fqdn_override: admin: host: keystone-admin.openstack.svc.cluster.subcloud1 public: {} and introduced in commit [1] by you. is these any additional config needed to bring up openstack on subcloud besides the deploy guide [2]? [1] https://review.opendev.org/#/c/697361/1 [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Sun, Austin Sent: Saturday, April 18, 2020 9:06 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E > Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only - without OpenStack support... brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From sgw at linux.intel.com Tue Apr 28 13:44:35 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 28 Apr 2020 06:44:35 -0700 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: References: Message-ID: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> +StarlingX-Discuss On 4/28/20 12:47 AM, An, Ran1 wrote: > Hi Cores: > >    There were some concerns on patch > https://review.opendev.org/#/c/717211/, and we had a discussion on last > Non-Openstack meeting few days ago. > >    By further investigation, there are 4 solutions below.  W*e'd like > to prefer option3 , if no other objection , we will implement option3*. > I am not sure I understand how option 1 and option 3 are different both are modifying upstream projects and require the StarlingX community to maintain a patched version (ie technical debt). Is there an option that modifies the logmgmt code directly instead of changing the daemon code? Sau! > *Background:* > >    Logmgmt uses “daemon.runner. DaemonRunner()” from package > python-daemon to > create/recreate/kill a daemon process in which it run log-rotate and > control system logs size. > > However, python-daemon has a “unbuffered I/O related error” in python3.x > [1], which require us do some changes to upgrade logmgmt to python3. > > *Solutions:* > >    Option 1: fix the bug of python-daemon by adding patch when we build > the python3-daemon rpm.  (implement in patch-717211/ > ) > > * add patch to fix the bug of python-daemon in python3 > * build python3-daemon rpm from python-daemon srpm > >    Option 2: rewrite the entrance function of logmgmt (start_polling()) > following examples provides by PEP 3143 > > > * using “daemon.Context()” instead of “daemon.runner.DaemonRunner() in > entrance function of logmgmt. > * implement a runner class “MyDaemonRunner()” in logmgmt > * build python3-daemon rpm from python-daemon srpm > >               Limitation: the implementation of daemon service required > to write is very similar with “daemon.runner”. > >    Option 3: import python-daemon-3k [2] python3 condition. > > * use "python-daemon-3k" instead of "python-daemon" when the env is > python3 > * add patch to fix the bug of python-daemon in python3 (refer to pull > request #1 from takuti/fix-unbuffered-error > ) > * build python3-daemon rpm from python-daemon-3k release > > >    Option 4: implement a daemon class "MyDaemon" and rewrite the > logmgmt codes with "MyDaemon" > > * implement a daemon class "MyDaemon" (refer to > https://www.workaround.cz/howto-make-code-daemon-python-3) > * rewrite the logmgmt codes with "MyDaemon" > > *Comparation: * > > Option > > > > Pkg provides daemon class > > > > Require build python3-daemon.rpm > > > > maintain offline patch > > > > Stars of github > > > > Changes > > Option1 > > > > python-daemon > > > > Yes > > > > yes > > > > 916 > > > > little > > Option2 > > > > python-daemon > > > > Yes > > > > > > 916 > > > > Medium > > Option3 > > > > python-daemon-3K > > > > Yes > > > > yes > > > > 14 > > > > little > > Option4 > > > > write “MyDaemon” based on basic python libs > > > > No > > > > No > > > > 0 > > > > huge > > [1] https://pagure.io/python-daemon/issue/5; > https://pagure.io/python-daemon/issue/8; > https://pagure.io/python-daemon/issue/36; > > [2] https://pypi.org/project/python-daemon-3K/; we had assessed 4 > projects that implement the python daemon following the PEP 3143 and > “python-daemon-3k” is the most proper for logmgmt. > From fungi at yuggoth.org Tue Apr 28 14:25:05 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 28 Apr 2020 14:25:05 +0000 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> References: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> Message-ID: <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> On 2020-04-28 06:44:35 -0700 (-0700), Saul Wold wrote: > I am not sure I understand how option 1 and option 3 are different > both are modifying upstream projects and require the StarlingX > community to maintain a patched version (ie technical debt). > > Is there an option that modifies the logmgmt code directly instead > of changing the daemon code? [...] It might be possible to subclass daemon.runner and shadow the offending methods, rather than forking the entire codebase. > > Option 3: import python-daemon-3k [2] python3 condition. > > > > * use "python-daemon-3k" instead of "python-daemon" when the > > env is python3 > > * add patch to fix the bug of python-daemon in python3 (refer > > to pull request #1 from takuti/fix-unbuffered-error > > ) > > * build python3-daemon rpm from python-daemon-3k release > > [...] I find it amusing that the comparison is trying to count *GitHub Stars* for a project which isn't actually hosted on GitHub (and when were those ever a mark of quality in the first place?), but more amazing is that it seems to have ignored that python-daemon-3k was last released in 2014 and its Git repository has seen no new commits since 2016, while python-daemon's last release was a mere 6 months ago. Also the patch referred to there looks like it would apply cleanly to both projects (python-daemon-3k is really just a very outdated fork of python-daemon anyway). Similar patches have been proposed to python-daemon, so maybe helping to address the maintainer's concerns with one of those would be a greater benefit to everyone? https://pagure.io/python-daemon/pull-request/7 https://pagure.io/python-daemon/pull-request/27 -- 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 Don.Penney at windriver.com Tue Apr 28 14:34:38 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 28 Apr 2020 14:34:38 +0000 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> References: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> Message-ID: If the sole problem here is the /dev/null redirects, then let's just drop the redirects: https://opendev.org/starlingx/utilities/src/branch/master/utilities/logmgmt/logmgmt/logmgmt/logmgmt.py#L64-L66 I don't think that should have any impact. -----Original Message----- From: Jeremy Stanley [mailto:fungi at yuggoth.org] Sent: Tuesday, April 28, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" On 2020-04-28 06:44:35 -0700 (-0700), Saul Wold wrote: > I am not sure I understand how option 1 and option 3 are different > both are modifying upstream projects and require the StarlingX > community to maintain a patched version (ie technical debt). > > Is there an option that modifies the logmgmt code directly instead of > changing the daemon code? [...] It might be possible to subclass daemon.runner and shadow the offending methods, rather than forking the entire codebase. > > Option 3: import python-daemon-3k [2] python3 condition. > > > > * use "python-daemon-3k" instead of "python-daemon" when the > > env is python3 > > * add patch to fix the bug of python-daemon in python3 (refer > > to pull request #1 from takuti/fix-unbuffered-error > > ) > > * build python3-daemon rpm from python-daemon-3k release > > [...] I find it amusing that the comparison is trying to count *GitHub Stars* for a project which isn't actually hosted on GitHub (and when were those ever a mark of quality in the first place?), but more amazing is that it seems to have ignored that python-daemon-3k was last released in 2014 and its Git repository has seen no new commits since 2016, while python-daemon's last release was a mere 6 months ago. Also the patch referred to there looks like it would apply cleanly to both projects (python-daemon-3k is really just a very outdated fork of python-daemon anyway). Similar patches have been proposed to python-daemon, so maybe helping to address the maintainer's concerns with one of those would be a greater benefit to everyone? https://pagure.io/python-daemon/pull-request/7 https://pagure.io/python-daemon/pull-request/27 -- Jeremy Stanley From sgw at linux.intel.com Tue Apr 28 15:00:37 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 28 Apr 2020 08:00:37 -0700 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> References: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> Message-ID: <01c31afa-3fc7-89fb-28f7-eeb1bed507d6@linux.intel.com> On 4/28/20 7:25 AM, Jeremy Stanley wrote: > On 2020-04-28 06:44:35 -0700 (-0700), Saul Wold wrote: >> I am not sure I understand how option 1 and option 3 are different >> both are modifying upstream projects and require the StarlingX >> community to maintain a patched version (ie technical debt). >> >> Is there an option that modifies the logmgmt code directly instead >> of changing the daemon code? > [...] > > It might be possible to subclass daemon.runner and shadow the > offending methods, rather than forking the entire codebase. > >>> Option 3: import python-daemon-3k [2] python3 condition. >>> >>> * use "python-daemon-3k" instead of "python-daemon" when the >>> env is python3 >>> * add patch to fix the bug of python-daemon in python3 (refer >>> to pull request #1 from takuti/fix-unbuffered-error >>> ) >>> * build python3-daemon rpm from python-daemon-3k release >>> > [...] > > I find it amusing that the comparison is trying to count *GitHub > Stars* for a project which isn't actually hosted on GitHub (and when > were those ever a mark of quality in the first place?), but more > amazing is that it seems to have ignored that python-daemon-3k was > last released in 2014 and its Git repository has seen no new commits > since 2016, while python-daemon's last release was a mere 6 months > ago. > Agreed here, python-daemon is at least creating current releases. > Also the patch referred to there looks like it would apply cleanly > to both projects (python-daemon-3k is really just a very outdated > fork of python-daemon anyway). Similar patches have been proposed to > python-daemon, so maybe helping to address the maintainer's concerns > with one of those would be a greater benefit to everyone? > > https://pagure.io/python-daemon/pull-request/7 > > https://pagure.io/python-daemon/pull-request/27 > BTW, I did try to reach out to Ben Finney (bignose) at his Debian email, but have not gotten a response, if you know of another way to reach out to him could you let us know. Sau! > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From fungi at yuggoth.org Tue Apr 28 15:30:21 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 28 Apr 2020 15:30:21 +0000 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: <01c31afa-3fc7-89fb-28f7-eeb1bed507d6@linux.intel.com> References: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> <01c31afa-3fc7-89fb-28f7-eeb1bed507d6@linux.intel.com> Message-ID: <20200428153020.w4ga7vwk4bc7ehxx@yuggoth.org> On 2020-04-28 08:00:37 -0700 (-0700), Saul Wold wrote: [...] > BTW, I did try to reach out to Ben Finney (bignose) at his Debian > email, but have not gotten a response, if you know of another way > to reach out to him could you let us know. He has some IRC and Matrix contact information listed at https://wiki.debian.org/BenFinney but also maybe just raising a comment on one of the relevant issues or pull requests for https://pagure.io/python-daemon/ would get his attention? -- 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 mihail-laurentiu.trica at intel.com Tue Apr 28 15:52:45 2020 From: mihail-laurentiu.trica at intel.com (Trica, Mihail-Laurentiu) Date: Tue, 28 Apr 2020 15:52:45 +0000 Subject: [Starlingx-discuss] Need help with commit Message-ID: Hello, I have made a few commits and there is just one that is up for review: https://review.opendev.org/#/c/716554/. I have modified the commit following commit review. Yang Liu has been the one that reviewed my commit and the commits of my fellow Intel colleagues. Yang gave it a Code Review +2 and a Workflow +1 and Zuul started its checks again. What I can see now is that Zuul gave it a -2 because one of its pylint check failed(logs are available HERE). The only problem is that it had give it a +1 after I made my final changes. Basically the history for the last patchset is this one: - I uploaded patchset 6, Zuul started its jobs, gave it +1 - Yang did the code review and gave it a Code Review +2 and a Workflow +1 - finally Zuul restarted its checks, but it had an error for the pylint job and it gave it a -2 From the logs the error is not on any of the files that I modified in the commit, but on: “automated-pytest-suite/keywords/storage_helper.py:424:8: E0633: Attempting to unpack a non-sequence defined at line 52 (unpacking-non-sequence)”. My code is not even using storage-helper. How can subsequent checks fail on code that has not been modified? Is there a way to re-trigger Zuul checks? In the meantime I have rebased the commit. Toate cele bune/Kind regards/Mit freundlichen Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem よろしくお願いいたします 此致 敬礼 Mihail-Laurenţiu Trică, Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Tue Apr 28 16:07:42 2020 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 28 Apr 2020 09:07:42 -0700 Subject: [Starlingx-discuss] Need help with commit In-Reply-To: References: Message-ID: <4263f69d-dc32-a49f-7dfd-31feb425cd02@linux.intel.com> On 4/28/20 8:52 AM, Trica, Mihail-Laurentiu wrote: > Hello, > > I have made a few commits and there is just one that is up for review: > https://review.opendev.org/#/c/716554/. I have modified the commit > following commit review. Yang Liu has been the one that reviewed my > commit and the commits of my fellow Intel colleagues. Yang gave it a > Code Review +2 and a Workflow +1 and Zuul started its checks again. What > I can see now is that Zuul gave it a -2 because one of its pylint check > failed(logs are available HERE > ). > The only problem is that it had give it a +1 after I made my final > changes. Basically the history for the last patchset is this one: > > - I uploaded patchset 6, Zuul started its jobs, gave it +1 > > - Yang did the code review and gave it a Code Review +2 and a Workflow +1 > > - finally Zuul restarted its checks, but it had an error for the pylint > job and it gave it a -2 > pylint was changed recently to a newer / stricter version that's why your getting new errors. > From the logs the error is not on any of the files that I modified in > the commit, but on: > “automated-pytest-suite/keywords/storage_helper.py:424:8: E0633: > Attempting to unpack a non-sequence defined at line 52 > (unpacking-non-sequence)”. My code is not even using storage-helper. How > can subsequent checks fail on code that has not been modified? Is there > a way to re-trigger Zuul checks? In the meantime I have rebased the commit. > It's failing not because of the code you added, but because pylint is checking all the code and found an issue since it's running with stricter rules now. you can add a "recheck" reply to your commit from review.opendev.org. Hope that helps Sau! > Toate cele bune/Kind regards/Mit freundlichen > Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem > > よろしくお願いいたします > > 此致 > > 敬礼 > > *Mihail-Laurenţiu Trică*, Software Engineer > > > _______________________________________________ > 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 Apr 28 16:21:13 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 28 Apr 2020 16:21:13 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 29, 2020) Message-ID: Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200429T1400 From Bill.Zvonar at windriver.com Tue Apr 28 16:40:57 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 28 Apr 2020 16:40:57 +0000 Subject: [Starlingx-discuss] Gentle reminder to cores... Message-ID: As discussed in last week's community call, a gentle reminder to the cores to regularly check for pending reviews. Saul sent some tips on how to make it easy to check for your pending reviews: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008395.html. Bill... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Apr 28 16:49:22 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 28 Apr 2020 16:49:22 +0000 Subject: [Starlingx-discuss] Gentle reminder to cores... In-Reply-To: References: Message-ID: As a corollary to that reminder, designers also need to pay attention to their reviews and respond to the comments that are made. There have been a few cases where the "review reminder" brought up on the community call has been waiting on a response from the review author. From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, April 28, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Gentle reminder to cores... As discussed in last week's community call, a gentle reminder to the cores to regularly check for pending reviews. Saul sent some tips on how to make it easy to check for your pending reviews: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008395.html. Bill... -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Apr 28 17:40:22 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 28 Apr 2020 17:40:22 +0000 Subject: [Starlingx-discuss] Gentle reminder to cores... In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818B01080B3B16@fmsmsx123.amr.corp.intel.com> One more thing. If you don't know who the Cores are for a project, you can find them here: https://review.opendev.org/#/admin/groups/?filter=starlingx. Feel free to reach out to them before you post your changes. Early feedback can save lots of time down the road. brucej From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Tuesday, April 28, 2020 9:49 AM To: Zvonar, Bill ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Gentle reminder to cores... As a corollary to that reminder, designers also need to pay attention to their reviews and respond to the comments that are made. There have been a few cases where the "review reminder" brought up on the community call has been waiting on a response from the review author. From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, April 28, 2020 12:41 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Gentle reminder to cores... As discussed in last week's community call, a gentle reminder to the cores to regularly check for pending reviews. Saul sent some tips on how to make it easy to check for your pending reviews: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008395.html. Bill... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Sabeel.Ansari at windriver.com Tue Apr 28 18:08:11 2020 From: Sabeel.Ansari at windriver.com (Ansari, Sabeel) Date: Tue, 28 Apr 2020 18:08:11 +0000 Subject: [Starlingx-discuss] cert-manager images In-Reply-To: References: Message-ID: Hi StarlingX Community, We've had to upversion the cert-manager container image to address functionality issues. Please use version '0.15.0-alpha.1' New image names are: quay.io/jetstack/cert-manager-controller: v0.15.0-alpha.1 quay.io/jetstack/cert-manager-webhook: v0.15.0-alpha.1 quay.io/jetstack/cert-manager-cainjector: v0.15.0-alpha.1 quay.io/jetstack/cert-manager-acmesolver: v0.15.0-alpha.1 Regards, Sabeel From: Ansari, Sabeel Sent: Monday, April 20, 2020 12:43 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: cert-manager images Hi StarlingX Community, As part of the cert-manager app support in Stx 4.0, anyone using a private container registry to install from, should pull the following images and push them to your private container registry: quay.io/jetstack/cert-manager-controller:v0.14.2 quay.io/jetstack/cert-manager-webhook:v0.14.2 quay.io/jetstack/cert-manager-cainjector:v0.14.2 quay.io/jetstack/cert-manager-acmesolver:v0.14.2 FYI: https://review.opendev.org/#/q/topic:cert-mgr+(status:open+OR+status:merged) Best regards, Sabeel -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Apr 28 18:22:02 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 28 Apr 2020 18:22:02 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 In-Reply-To: References: Message-ID: Nicolae: There is not enough info in the LP to debug the RED sanity as it does not show any error logs from the ansible log snippet in the LP. I updated the LP yesterday and requested more info and the LP has not yet been updated. When can you provide more info? Frank From: Jascanu, Nicolae Sent: Monday, April 27, 2020 1:14 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Sanity Test from 2020-April-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200426T020107Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We raised a bug: Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Apr 28 19:10:09 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 28 Apr 2020 19:10:09 +0000 Subject: [Starlingx-discuss] build failures: unable to find train src rpms Message-ID: Hi folks, As part of the train upgrade work, the train repo config file was added with this review: https://review.opendev.org/716883 Unfortunately, it looks like a copy/paste error on the source repo config (label left as centos-openstack-Stein-source) meant that the Train source repo did not get properly mirrored, and download_mirror is unable to find the new train src rpms: Looking for openstack-keystone-16.0.0-1.el7.src.rpm --> run: yumdownloader -q -C -c /tmp/stx_mirror_6Z1HSK/yum.conf --releasever=7 --source openstack-keystone-16.0.0-1.el7 Repository centos-openstack-Stein-source is listed more than once in the configuration Repository CENGN_centos-openstack-Stein-source is listed more than once in the configuration No source RPM found for 1:openstack-keystone-16.0.0-1.el7.noarch No source RPM found for 1:openstack-keystone-16.0.0-1.el7.noarch Nothing to download Warning: openstack-keystone-16.0.0-1.el7.src.rpm not found Looking for openstack-keystone-16.0.0-1.el7.src.rpm --> run: yumdownloader -q -C -c /tmp/stx_mirror_6Z1HSK/yum.conf --releasever=7 --source openstack-keystone-16.0.0-1.el7 Repository centos-openstack-Stein-source is listed more than once in the configuration Repository CENGN_centos-openstack-Stein-source is listed more than once in the configuration No source RPM found for 1:openstack-keystone-16.0.0-1.el7.noarch No source RPM found for 1:openstack-keystone-16.0.0-1.el7.noarch Nothing to download Warning: openstack-keystone-16.0.0-1.el7.src.rpm not found Error: openstack-keystone-16.0.0-1.el7.src.rpm not found As the remaining train reviews merged today, this is causing build failures for folks who have rebased this afternoon. I've posted the following review to fix this repo config: https://review.opendev.org/724127 Once this is merged and CENGN mirrors are updated, the builds should be ok. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Tue Apr 28 19:17:52 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 28 Apr 2020 19:17:52 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200427T233018Z Message-ID: Sanity Test from 2020-April-27 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200427T233018Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We updated the bug Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 We used the helm chart from http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/helm-charts/ Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Tue Apr 28 19:32:57 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Tue, 28 Apr 2020 19:32:57 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 In-Reply-To: References: Message-ID: Hi Frank, The build validated today also failed with the same error. I've updated the bug with collected info. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Miller, Frank Sent: Tuesday, April 28, 2020 21:22 To: Jascanu, Nicolae ; starlingx-discuss at lists.starlingx.io Subject: RE: Sanity Master Test LAYERED build ISO 20200426 Nicolae: There is not enough info in the LP to debug the RED sanity as it does not show any error logs from the ansible log snippet in the LP. I updated the LP yesterday and requested more info and the LP has not yet been updated. When can you provide more info? Frank From: Jascanu, Nicolae > Sent: Monday, April 27, 2020 1:14 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Sanity Test from 2020-April-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200426T020107Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We raised a bug: Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Tue Apr 28 20:47:43 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 28 Apr 2020 20:47:43 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 In-Reply-To: References: Message-ID: Please also provide the full ansible.log that contains the failure. From: Jascanu, Nicolae Sent: Tuesday, April 28, 2020 3:33 PM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: RE: Sanity Master Test LAYERED build ISO 20200426 Hi Frank, The build validated today also failed with the same error. I've updated the bug with collected info. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Miller, Frank > Sent: Tuesday, April 28, 2020 21:22 To: Jascanu, Nicolae >; starlingx-discuss at lists.starlingx.io Subject: RE: Sanity Master Test LAYERED build ISO 20200426 Nicolae: There is not enough info in the LP to debug the RED sanity as it does not show any error logs from the ansible log snippet in the LP. I updated the LP yesterday and requested more info and the LP has not yet been updated. When can you provide more info? Frank From: Jascanu, Nicolae > Sent: Monday, April 27, 2020 1:14 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Sanity Test from 2020-April-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200426T020107Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We raised a bug: Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From Frank.Miller at windriver.com Tue Apr 28 21:06:03 2020 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 28 Apr 2020 21:06:03 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 In-Reply-To: References: Message-ID: The reason for the RED sanity has been determined. Your docker private registry needs to be updated with the new cert-manager image versions specified by Sabeel Ansari's email earlier today. Add those images to your registry and the ansible provisioning should complete. Frank From: Miller, Frank Sent: Tuesday, April 28, 2020 4:48 PM To: Jascanu, Nicolae ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Please also provide the full ansible.log that contains the failure. From: Jascanu, Nicolae > Sent: Tuesday, April 28, 2020 3:33 PM To: Miller, Frank >; starlingx-discuss at lists.starlingx.io Subject: RE: Sanity Master Test LAYERED build ISO 20200426 Hi Frank, The build validated today also failed with the same error. I've updated the bug with collected info. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Miller, Frank > Sent: Tuesday, April 28, 2020 21:22 To: Jascanu, Nicolae >; starlingx-discuss at lists.starlingx.io Subject: RE: Sanity Master Test LAYERED build ISO 20200426 Nicolae: There is not enough info in the LP to debug the RED sanity as it does not show any error logs from the ansible log snippet in the LP. I updated the LP yesterday and requested more info and the LP has not yet been updated. When can you provide more info? Frank From: Jascanu, Nicolae > Sent: Monday, April 27, 2020 1:14 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200426 Sanity Test from 2020-April-26 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200426T020107Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We raised a bug: Apply-failed for cert-manager - https://bugs.launchpad.net/starlingx/+bug/1875449 Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From build.starlingx at gmail.com Wed Apr 29 01:41:04 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 28 Apr 2020 21:41:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 95 - Failure! Message-ID: <1501020722.1243.1588124465569.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 95 Status: Failure Timestamp: 20200429T013646Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200429T013646Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From 18245043314 at 163.com Wed Apr 29 03:45:35 2020 From: 18245043314 at 163.com (zhou) Date: Wed, 29 Apr 2020 11:45:35 +0800 (CST) Subject: [Starlingx-discuss] stuck in installing stx in bare metal Message-ID: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> Dear sir: we are trying to install all-in-one stx in bare metal environment, but we stuck in the screen says "starting terminate plymouth boot screen". Do you have any idea about that problem? yours, zhou qingyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Apr 29 04:01:25 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 29 Apr 2020 04:01:25 +0000 Subject: [Starlingx-discuss] stuck in installing stx in bare metal In-Reply-To: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> References: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> Message-ID: Can you provide details about how you're trying to install? Are you installing from USB? From: zhou [mailto:18245043314 at 163.com] Sent: Tuesday, April 28, 2020 11:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: we are trying to install all-in-one stx in bare metal environment, but we stuck in the screen says "starting terminate plymouth boot screen". Do you have any idea about that problem? yours, zhou qingyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From ran1.an at intel.com Wed Apr 29 04:13:25 2020 From: ran1.an at intel.com (An, Ran1) Date: Wed, 29 Apr 2020 04:13:25 +0000 Subject: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" In-Reply-To: References: <76ac2224-1e73-7086-a459-d5fe02e5c0cc@linux.intel.com> <20200428142505.3jnr3ybjtdobmhpb@yuggoth.org> Message-ID: @Penney, Don drop codes (https://opendev.org/starlingx/utilities/src/branch/master/utilities/logmgmt/logmgmt/logmgmt/logmgmt.py#L64-L66) could not solve the problem bringing by python3 upgradation. The root cause is a bug of python-daemon upstream. @Jeremy Stanley thanks for your "subclass daemon.runner " advice which simplifies the Option 2 and makes it become a good option to choose. By the way, the offline patch in Option 1 is refer to https://pagure.io/python-daemon/pull-request/27, in fact . @Wold, Saul the different between Option1 and Option3 is the bug was fixed in master branch of project https://github.com/jbvsmo/python-daemon and we can expect to drop the offline patch when it comes a new release. However I didn't notice the project imported in Option 3 had not updated release for 6 years, so I'll drop option 3. By the way, both Option2 and Option4 are modifying the logmgmt code directly instead of changing the daemon code. In last, we'll try to commit pull-request to python-daemon upstream to fix this bug. But before that we'll implement Option 2 to support logmgmt python3 upgradation. " Option 2: subclass "daemon.runner.DaemonRunner()" as “MyDaemonRunner()” and override methods refer to https://pagure.io/python-daemon/pull-request/27 . 1) using class “MyDaemonRunner()” instead of “daemon.runner.DaemonRunner()” to create daemon runner; 2) build python3-daemon rpm from python-daemon srpm" Thanks Ran -----Original Message----- From: Penney, Don Sent: Tuesday, April 28, 2020 10:35 PM To: Jeremy Stanley ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" If the sole problem here is the /dev/null redirects, then let's just drop the redirects: https://opendev.org/starlingx/utilities/src/branch/master/utilities/logmgmt/logmgmt/logmgmt/logmgmt.py#L64-L66 I don't think that should have any impact. -----Original Message----- From: Jeremy Stanley [mailto:fungi at yuggoth.org] Sent: Tuesday, April 28, 2020 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] FW: [starlingx-discuss][python3] four solutions for "Add python3-daemon required by logmgmt" On 2020-04-28 06:44:35 -0700 (-0700), Saul Wold wrote: > I am not sure I understand how option 1 and option 3 are different > both are modifying upstream projects and require the StarlingX > community to maintain a patched version (ie technical debt). > > Is there an option that modifies the logmgmt code directly instead of > changing the daemon code? [...] It might be possible to subclass daemon.runner and shadow the offending methods, rather than forking the entire codebase. > > Option 3: import python-daemon-3k [2] python3 condition. > > > > * use "python-daemon-3k" instead of "python-daemon" when the > > env is python3 > > * add patch to fix the bug of python-daemon in python3 (refer > > to pull request #1 from takuti/fix-unbuffered-error > > ) > > * build python3-daemon rpm from python-daemon-3k release > > [...] I find it amusing that the comparison is trying to count *GitHub Stars* for a project which isn't actually hosted on GitHub (and when were those ever a mark of quality in the first place?), but more amazing is that it seems to have ignored that python-daemon-3k was last released in 2014 and its Git repository has seen no new commits since 2016, while python-daemon's last release was a mere 6 months ago. Also the patch referred to there looks like it would apply cleanly to both projects (python-daemon-3k is really just a very outdated fork of python-daemon anyway). Similar patches have been proposed to python-daemon, so maybe helping to address the maintainer's concerns with one of those would be a greater benefit to everyone? https://pagure.io/python-daemon/pull-request/7 https://pagure.io/python-daemon/pull-request/27 -- Jeremy Stanley _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Wed Apr 29 08:02:05 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 04:02:05 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 96 - Still Failing! In-Reply-To: <1353334847.1241.1588124462677.JavaMail.javamailuser@localhost> References: <1353334847.1241.1588124462677.JavaMail.javamailuser@localhost> Message-ID: <197949433.1250.1588147327280.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 96 Status: Still Failing Timestamp: 20200429T041847Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200429T041847Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From build.starlingx at gmail.com Wed Apr 29 11:43:49 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 07:43:49 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 689 - Failure! Message-ID: <1145881719.1253.1588160630413.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 689 Status: Failure Timestamp: 20200429T081625Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200429T080012Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20200429T080012Z DOCKER_BUILD_ID: jenkins-master-20200429T080012Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200429T080012Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/monolithic/20200429T080012Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Wed Apr 29 11:43:52 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 07:43:52 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 525 - Failure! Message-ID: <992097335.1256.1588160633657.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 525 Status: Failure Timestamp: 20200429T080012Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/monolithic/20200429T080012Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: true From Andy.Ning at windriver.com Wed Apr 29 13:07:07 2020 From: Andy.Ning at windriver.com (Ning, Antai (Andy)) Date: Wed, 29 Apr 2020 13:07:07 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> , Message-ID: Hi Austin, What's the output of "openstack endpoint list" on containerized openstack like? keystone-admin should be show up as identity's admin endpoint .... if not, that could be a bug. Also what's the output of "kubectl get ingress --all-namespaces" or "kubectl get ingress --openstack"? I want to see whether the ingress for keystone-admin is created or not. Andy ________________________________ From: Sun, Austin Sent: Tuesday, April 28, 2020 4:34 AM To: Ning, Antai (Andy) ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E Subject: FW: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy: I deployed dist-cloud in virtual env based on 20200414, but openstack application on subcloud deployed failed . >From cinder-api po logs: >: Failed to establish a new connection: [Errno -2] Name or service not known',)): ConnectFailure: Unable to establish connection to http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3/auth/tokens: HTTPConnectionPool(host='keystone-admin.openstack.svc.cluster.subcloud1', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) This keystone-admin.openstack.svc.cluster.subcloud1 can not be found in subcloud1 controllers This url seems override from helm keystone: host_fqdn_override: admin: host: keystone-admin.openstack.svc.cluster.subcloud1 public: {} and introduced in commit [1] by you. is these any additional config needed to bring up openstack on subcloud besides the deploy guide [2]? [1] https://review.opendev.org/#/c/697361/1 [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Sun, Austin Sent: Saturday, April 18, 2020 9:06 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E > Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only – without OpenStack support… brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Wed Apr 29 13:56:56 2020 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Wed, 29 Apr 2020 13:56:56 +0000 Subject: [Starlingx-discuss] Need help with commit In-Reply-To: <4263f69d-dc32-a49f-7dfd-31feb425cd02@linux.intel.com> References: , <4263f69d-dc32-a49f-7dfd-31feb425cd02@linux.intel.com> Message-ID: I uploaded a fix, by clamping pylint (same as I did for 2 other repos that hit the same issue). https://bugs.launchpad.net/starlingx/+bug/1875705 Your review will merge through a 'recheck' after this one merges. If someone wants to keep pylint floating on its latest release (which could cause another break the next time one is released), they could update the 'is_ceph_healthy' method, and/or the 2 places it is called to resolve the issue. Al ________________________________ From: Saul Wold Sent: Tuesday, April 28, 2020 12:07 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Need help with commit On 4/28/20 8:52 AM, Trica, Mihail-Laurentiu wrote: > Hello, > > I have made a few commits and there is just one that is up for review: > https://review.opendev.org/#/c/716554/. I have modified the commit > following commit review. Yang Liu has been the one that reviewed my > commit and the commits of my fellow Intel colleagues. Yang gave it a > Code Review +2 and a Workflow +1 and Zuul started its checks again. What > I can see now is that Zuul gave it a -2 because one of its pylint check > failed(logs are available HERE > ). > The only problem is that it had give it a +1 after I made my final > changes. Basically the history for the last patchset is this one: > > - I uploaded patchset 6, Zuul started its jobs, gave it +1 > > - Yang did the code review and gave it a Code Review +2 and a Workflow +1 > > - finally Zuul restarted its checks, but it had an error for the pylint > job and it gave it a -2 > pylint was changed recently to a newer / stricter version that's why your getting new errors. > From the logs the error is not on any of the files that I modified in > the commit, but on: > “automated-pytest-suite/keywords/storage_helper.py:424:8: E0633: > Attempting to unpack a non-sequence defined at line 52 > (unpacking-non-sequence)”. My code is not even using storage-helper. How > can subsequent checks fail on code that has not been modified? Is there > a way to re-trigger Zuul checks? In the meantime I have rebased the commit. > It's failing not because of the code you added, but because pylint is checking all the code and found an issue since it's running with stricter rules now. you can add a "recheck" reply to your commit from review.opendev.org. Hope that helps Sau! > Toate cele bune/Kind regards/Mit freundlichen > Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem > > よろしくお願いいたします > > 此致 > > 敬礼 > > *Mihail-Laurenţiu Trică*, Software Engineer > > > _______________________________________________ > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Apr 29 14:15:12 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 29 Apr 2020 14:15:12 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> , Message-ID: Hi Andy : Thanks your reply. Some output currently , the result of 'openstack endpoint list' in cinder-bootstrap is [root at cinder-bootstrap-rtxf7 /]# openstack endpoint list | grep identity | 0da674cb1d384ae0999d02b0ababd5c9 | subcloud1 | keystone | identity | True | internal | http://keystone-api.openstack.svc.cluster.local:5000/v3 | | 6eabcff1e83e45e3911940cd3195e09c | subcloud1 | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | e6f5720ee62c4c1ab378fe20c7d6716f | subcloud1 | keystone | identity | True | admin | http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3 | controller-0:~$ kubectl get ingress --all-namespaces NAMESPACE NAME HOSTS ADDRESS PORTS AGE openstack cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h openstack glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h openstack keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h openstack keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h openstack keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h openstack osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h ' kubectl get ingress -openstack' run with error But controller-0:~$ kubectl get ingress -n openstack NAME HOSTS ADDRESS PORTS AGE cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h But keystone-admin.openstack.svc.cluster.subcloud1 cannot be found from host or container : controller-0:~$ curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Name or service not known [root at cinder-bootstrap-rtxf7 /]# curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Unknown error Thanks. BR Austin Sun. From: Ning, Antai (Andy) Sent: Wednesday, April 29, 2020 9:07 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Austin, What's the output of "openstack endpoint list" on containerized openstack like? keystone-admin should be show up as identity's admin endpoint .... if not, that could be a bug. Also what's the output of "kubectl get ingress --all-namespaces" or "kubectl get ingress --openstack"? I want to see whether the ingress for keystone-admin is created or not. Andy ________________________________ From: Sun, Austin > Sent: Tuesday, April 28, 2020 4:34 AM To: Ning, Antai (Andy) >; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E > Subject: FW: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy: I deployed dist-cloud in virtual env based on 20200414, but openstack application on subcloud deployed failed . >From cinder-api po logs: >: Failed to establish a new connection: [Errno -2] Name or service not known',)): ConnectFailure: Unable to establish connection to http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3/auth/tokens: HTTPConnectionPool(host='keystone-admin.openstack.svc.cluster.subcloud1', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) This keystone-admin.openstack.svc.cluster.subcloud1 can not be found in subcloud1 controllers This url seems override from helm keystone: host_fqdn_override: admin: host: keystone-admin.openstack.svc.cluster.subcloud1 public: {} and introduced in commit [1] by you. is these any additional config needed to bring up openstack on subcloud besides the deploy guide [2]? [1] https://review.opendev.org/#/c/697361/1 [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Sun, Austin > Sent: Saturday, April 18, 2020 9:06 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E > Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only - without OpenStack support... brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Andy.Ning at windriver.com Wed Apr 29 15:04:39 2020 From: Andy.Ning at windriver.com (Ning, Antai (Andy)) Date: Wed, 29 Apr 2020 15:04:39 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> , , Message-ID: It looks like a dns issue. "keystone-admin.openstack.svc.cluster.subcloud1" is not resolvable. coredns should be able to resolve this FQDN, but looks like it can't. So it can be bug. You may want to raise a LP for it. Thanks, Andy ________________________________ From: Sun, Austin Sent: Wednesday, April 29, 2020 10:15 AM To: Ning, Antai (Andy) ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E Subject: RE: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy : Thanks your reply. Some output currently , the result of ‘openstack endpoint list’ in cinder-bootstrap is [root at cinder-bootstrap-rtxf7 /]# openstack endpoint list | grep identity | 0da674cb1d384ae0999d02b0ababd5c9 | subcloud1 | keystone | identity | True | internal | http://keystone-api.openstack.svc.cluster.local:5000/v3 | | 6eabcff1e83e45e3911940cd3195e09c | subcloud1 | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | e6f5720ee62c4c1ab378fe20c7d6716f | subcloud1 | keystone | identity | True | admin | http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3 | controller-0:~$ kubectl get ingress --all-namespaces NAMESPACE NAME HOSTS ADDRESS PORTS AGE openstack cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h openstack glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h openstack keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h openstack keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h openstack keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h openstack osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h ‘ kubectl get ingress –openstack’ run with error But controller-0:~$ kubectl get ingress -n openstack NAME HOSTS ADDRESS PORTS AGE cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h But keystone-admin.openstack.svc.cluster.subcloud1 cannot be found from host or container : controller-0:~$ curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Name or service not known [root at cinder-bootstrap-rtxf7 /]# curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Unknown error Thanks. BR Austin Sun. From: Ning, Antai (Andy) Sent: Wednesday, April 29, 2020 9:07 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Austin, What's the output of "openstack endpoint list" on containerized openstack like? keystone-admin should be show up as identity's admin endpoint .... if not, that could be a bug. Also what's the output of "kubectl get ingress --all-namespaces" or "kubectl get ingress --openstack"? I want to see whether the ingress for keystone-admin is created or not. Andy ________________________________ From: Sun, Austin > Sent: Tuesday, April 28, 2020 4:34 AM To: Ning, Antai (Andy) >; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E > Subject: FW: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy: I deployed dist-cloud in virtual env based on 20200414, but openstack application on subcloud deployed failed . >From cinder-api po logs: >: Failed to establish a new connection: [Errno -2] Name or service not known',)): ConnectFailure: Unable to establish connection to http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3/auth/tokens: HTTPConnectionPool(host='keystone-admin.openstack.svc.cluster.subcloud1', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) This keystone-admin.openstack.svc.cluster.subcloud1 can not be found in subcloud1 controllers This url seems override from helm keystone: host_fqdn_override: admin: host: keystone-admin.openstack.svc.cluster.subcloud1 public: {} and introduced in commit [1] by you. is these any additional config needed to bring up openstack on subcloud besides the deploy guide [2]? [1] https://review.opendev.org/#/c/697361/1 [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Sun, Austin > Sent: Saturday, April 18, 2020 9:06 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E > Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only – without OpenStack support… brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Apr 29 15:07:41 2020 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 29 Apr 2020 15:07:41 +0000 Subject: [Starlingx-discuss] Community (& TSC) Call (Apr 29, 2020) Message-ID: >From today's meeting... * Standing Topics * Sanity * Monolithic * Green for 20200422, the last one * Layered * Green for 20200422 * Red for 20200423 - mirror issue w/ defaultbackend * also needed to be updated and was done - so also possibly an issue w/ the script (see next comment) * Red for 20200426 - didn't have the new cert-manager image versions * Red for 20200427 - still due to cert-manager image versions? * per Nic, they have a script that automatically synchs the private registry w/ the .lst changes * Build Issues - do to issues with new repos added - incompatiblities w/ .lst file * options to avoid * add the new stuff first, without removing the old stuff - don't gamble the build on the new stuff going in cleanly * then make sure the stuff is there on the CENGN mirror before you do your final commit * AR: build team to share a set of checks for devs/cores to follow when doing a repo add/change * Gerrit Reviews in Need of Attention * nothing new this week here * CentOS 8 Kernel Upgrade Plan * per Saul, final reviews are up & being reviewed - lots of reviewing to be done * Topics for this Week * StarlingX App Store :) (brucej) * a thought for now - could we share pre-built applications, optimized for StarlingX * encourage the adoption of StarlingX by building such an ecosystem * Ildiko opined that it might be a good blog post * Ian said there's one in the works re: ONAP on StarlingX * Adding Bandit to additional repos and packages * http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008367.html * Saul will raise this for discussion at the next Flock meeting * ARs from Previous Meetings * 4/22 * Bill still to follow up on on red sanities from 0415 & 0416 * 4/15 * layered build - validating docker images (Scott/Nic) - to be discussed in Build meeting tomorrow * manually updating version info (Build team + Bart) * home for pre-built srpms (Scott, Austin) * follow up with OpenDev re: VM for running SX sanity pending QCOW2 image (Bill, Build) * Open Requests for Help * the way to enable swift in starlingx: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-February/007758.html * Volker has asked if the community can consider this request again - anybody up for having a look? * Can't reboot/shutdown VMs: http://lists.starlingx.io/pipermail/starlingx-discuss/2020-April/008401.html -----Original Message----- From: Zvonar, Bill Sent: Tuesday, April 28, 2020 12:21 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community (& TSC) Call (Apr 29, 2020) Hi all, reminder of tomorrow's TSC/Community call. As usual, we'll start with TSC business, then we'll move on to the Community call. Please feel free to add items to the agenda [0] for the Community call beforehand. 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=20200429T1400 From austin.sun at intel.com Wed Apr 29 15:14:01 2020 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 29 Apr 2020 15:14:01 +0000 Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080A20DF@fmsmsx123.amr.corp.intel.com> , , Message-ID: Thanks. Here it is : https://bugs.launchpad.net/starlingx/+bug/1875914 Thanks. BR Austin Sun. From: Ning, Antai (Andy) Sent: Wednesday, April 29, 2020 11:05 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud It looks like a dns issue. "keystone-admin.openstack.svc.cluster.subcloud1" is not resolvable. coredns should be able to resolve this FQDN, but looks like it can't. So it can be bug. You may want to raise a LP for it. Thanks, Andy ________________________________ From: Sun, Austin > Sent: Wednesday, April 29, 2020 10:15 AM To: Ning, Antai (Andy) >; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E > Subject: RE: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy : Thanks your reply. Some output currently , the result of 'openstack endpoint list' in cinder-bootstrap is [root at cinder-bootstrap-rtxf7 /]# openstack endpoint list | grep identity | 0da674cb1d384ae0999d02b0ababd5c9 | subcloud1 | keystone | identity | True | internal | http://keystone-api.openstack.svc.cluster.local:5000/v3 | | 6eabcff1e83e45e3911940cd3195e09c | subcloud1 | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | e6f5720ee62c4c1ab378fe20c7d6716f | subcloud1 | keystone | identity | True | admin | http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3 | controller-0:~$ kubectl get ingress --all-namespaces NAMESPACE NAME HOSTS ADDRESS PORTS AGE openstack cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h openstack glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h openstack keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h openstack keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h openstack keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h openstack osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h ' kubectl get ingress -openstack' run with error But controller-0:~$ kubectl get ingress -n openstack NAME HOSTS ADDRESS PORTS AGE cinder cinder,cinder.openstack,cinder.openstack.svc.cluster.local 80 31h glance glance,glance.openstack,glance.openstack.svc.cluster.local 80 31h keystone keystone,keystone.openstack,keystone.openstack.svc.cluster.local 80 31h keystone-admin keystone-admin,keystone-admin.openstack,keystone-admin.openstack.svc.cluster.local 80 31h keystone-admin-cluster-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h keystone-admin-namespace-fqdn keystone-admin.openstack.svc.cluster.subcloud1 80 31h openstack-osh-openstack-ingress *.openstack.svc.cluster.local 80 31h osh-openstac-mgr-e50215 osh-openstac-mgr-e50215,osh-openstac-mgr-e50215.openstack,osh-openstac-mgr-e50215.openstack.svc.cluster.local 80 31h But keystone-admin.openstack.svc.cluster.subcloud1 cannot be found from host or container : controller-0:~$ curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Name or service not known [root at cinder-bootstrap-rtxf7 /]# curl http://keystone-admin.openstack.svc.cluster.subcloud1 curl: (6) Could not resolve host: keystone-admin.openstack.svc.cluster.subcloud1; Unknown error Thanks. BR Austin Sun. From: Ning, Antai (Andy) > Sent: Wednesday, April 29, 2020 9:07 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Cc: Jones, Bruce E > Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Austin, What's the output of "openstack endpoint list" on containerized openstack like? keystone-admin should be show up as identity's admin endpoint .... if not, that could be a bug. Also what's the output of "kubectl get ingress --all-namespaces" or "kubectl get ingress --openstack"? I want to see whether the ingress for keystone-admin is created or not. Andy ________________________________ From: Sun, Austin > Sent: Tuesday, April 28, 2020 4:34 AM To: Ning, Antai (Andy) >; starlingx-discuss at lists.starlingx.io > Cc: Jones, Bruce E > Subject: FW: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Andy: I deployed dist-cloud in virtual env based on 20200414, but openstack application on subcloud deployed failed . >From cinder-api po logs: >: Failed to establish a new connection: [Errno -2] Name or service not known',)): ConnectFailure: Unable to establish connection to http://keystone-admin.openstack.svc.cluster.subcloud1:80/v3/auth/tokens: HTTPConnectionPool(host='keystone-admin.openstack.svc.cluster.subcloud1', port=80): Max retries exceeded with url: /v3/auth/tokens (Caused by NewConnectionError(': Failed to establish a new connection: [Errno -2] Name or service not known',)) This keystone-admin.openstack.svc.cluster.subcloud1 can not be found in subcloud1 controllers This url seems override from helm keystone: host_fqdn_override: admin: host: keystone-admin.openstack.svc.cluster.subcloud1 public: {} and introduced in commit [1] by you. is these any additional config needed to bring up openstack on subcloud besides the deploy guide [2]? [1] https://review.opendev.org/#/c/697361/1 [2] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Sun, Austin > Sent: Saturday, April 18, 2020 9:06 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi Bruce: No, for stx.3.0 the openstack on subcloud works well . central cloud does not support openstack . Thanks. BR Austin Sun. From: Jones, Bruce E > Sent: Friday, April 17, 2020 11:01 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [starlingx] cinder bootstrap failed on subcloud I thought that dist-cloud sub-nodes are Kubernetes only - without OpenStack support... brucej From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Friday, April 17, 2020 5:45 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [starlingx] cinder bootstrap failed on subcloud Hi community: I deployed dist-cloud in virtual env (20200414) , but the openstack application applied failed. The reason is cinder-bootstrap job failed. The logs are [root at cinder-bootstrap-rkp7j /]# openstack volume type show ceph-store The server is currently unavailable. Please try again at a later time.

The Keystone service is temporarily unavailable. (HTTP 503) But openstack endpoint list works fine on this pod Does any one meet same issue on recently ? Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Stefan.Dinescu at windriver.com Wed Apr 29 15:22:37 2020 From: Stefan.Dinescu at windriver.com (Dinescu, Stefan) Date: Wed, 29 Apr 2020 15:22:37 +0000 Subject: [Starlingx-discuss] Upversioning netapp Message-ID: Hello, I m currently working on upversioning the netapp trident installer that is used with the netapp storage backend. Reviews [1] and [2] will be merged soon. As part of this upversioning effort a set of docker images are being updated as well. If you are using your own private docker registry mirror, you should add the following images to your mirror: - docker.io/netapp/trident:20.04.0 - quay.io/k8scsi/csi-provisioner:v1.6.0​ - quay.io/k8scsi/csi-attacher:v2.2.0​ - quay.io/k8scsi/csi-resizer:v0.5.0​ - quay.io/k8scsi/csi-node-driver-registrar:v1.3.0​ - quay.io/k8scsi/csi-snapshotter:v2.1.0 [1]: https://review.opendev.org/723606 [2]: https://review.opendev.org/724237 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Apr 29 16:23:14 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 29 Apr 2020 16:23:14 +0000 Subject: [Starlingx-discuss] June Virtual PTG candidate feature list? Message-ID: <9A85D2917C58154C960D95352B22818B01080B4524@fmsmsx123.amr.corp.intel.com> Do we have a list of candidate features for the vPTG? I'd like to add a few. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Wed Apr 29 16:38:18 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 12:38:18 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 285 - Failure! Message-ID: <2076221490.1260.1588178299734.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 285 Status: Failure Timestamp: 20200429T150941Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200429T150526Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200429T150526Z DOCKER_BUILD_ID: jenkins-master-distro-20200429T150526Z-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/20200429T150526Z/logs FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200429T150526Z/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 Wed Apr 29 16:38:22 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 12:38:22 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 97 - Still Failing! In-Reply-To: <2063757745.1248.1588147323756.JavaMail.javamailuser@localhost> References: <2063757745.1248.1588147323756.JavaMail.javamailuser@localhost> Message-ID: <876349594.1263.1588178302997.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 97 Status: Still Failing Timestamp: 20200429T150526Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200429T150526Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From sgw at linux.intel.com Wed Apr 29 17:00:57 2020 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 29 Apr 2020 10:00:57 -0700 Subject: [Starlingx-discuss] Need help with commit In-Reply-To: References: <4263f69d-dc32-a49f-7dfd-31feb425cd02@linux.intel.com> Message-ID: <7cb231a4-be8b-fe62-5594-008a5c2f305c@linux.intel.com> On 4/29/20 6:56 AM, Bailey, Henry Albert (Al) wrote: > I uploaded a fix, by clamping pylint (same as I did for 2 other repos > that hit the same issue). > https://bugs.launchpad.net/starlingx/+bug/1875705 > Your review will merge through a 'recheck' after this one merges. > Are we sure we want to clamp the version, don't we want to file LP or stories against the pylint issues and fix them and then release the clamp? Maybe we need a general pylint story? I think that we should be keeping up with pylint as it can find real issues. > If someone wants to keep pylint floating on its latest release (which > could cause another break the next time one is released), they could > update the 'is_ceph_healthy' method, and/or the 2 places it is called to > resolve the issue. > > Al > ------------------------------------------------------------------------ > *From:* Saul Wold > *Sent:* Tuesday, April 28, 2020 12:07 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Need help with commit > > > On 4/28/20 8:52 AM, Trica, Mihail-Laurentiu wrote: >> Hello, >> >> I have made a few commits and there is just one that is up for review: >> https://review.opendev.org/#/c/716554/. I have modified the commit >> following commit review. Yang Liu has been the one that reviewed my >> commit and the commits of my fellow Intel colleagues. Yang gave it a >> Code Review +2 and a Workflow +1 and Zuul started its checks again. What >> I can see now is that Zuul gave it a -2 because one of its pylint check >> failed(logs are available HERE >> ). > >> The only problem is that it had give it a +1 after I made my final >> changes. Basically the history for the last patchset is this one: >> >> - I uploaded patchset 6, Zuul started its jobs, gave it +1 >> >> - Yang did the code review and gave it a Code Review +2 and a Workflow +1 >> >> - finally Zuul restarted its checks, but it had an error for the pylint >> job and it gave it a -2 >> > pylint was changed recently to a newer / stricter version that's why > your getting new errors. > >>  From the logs the error is not on any of the files that I modified in >> the commit, but on: >> “automated-pytest-suite/keywords/storage_helper.py:424:8: E0633: >> Attempting to unpack a non-sequence defined at line 52 >> (unpacking-non-sequence)”. My code is not even using storage-helper. How >> can subsequent checks fail on code that has not been modified? Is there >> a way to re-trigger Zuul checks? In the meantime I have rebased the commit. >> > It's failing not because of the code you added, but because pylint is > checking all the code and found an issue since it's running with > stricter rules now. > > you can add a "recheck" reply to your commit from review.opendev.org. > > Hope that helps > >     Sau! > >> Toate cele bune/Kind regards/Mit freundlichen >> Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem >> >> よろしくお願いいたします >> >> 此致 >> >> 敬礼 >> >> *Mihail-Laurenţiu Trică*, Software Engineer >> >> >> _______________________________________________ >> 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 nicolae.jascanu at intel.com Wed Apr 29 17:03:57 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Wed, 29 Apr 2020 17:03:57 +0000 Subject: [Starlingx-discuss] Upversioning netapp In-Reply-To: References: Message-ID: Thank you for announcing this. Regards, Nicolae Jascanu, Ph.D. TSD Engineering Manager [intel-logo] Internet Of Things Group Galati, Romania From: Dinescu, Stefan Sent: Wednesday, April 29, 2020 18:23 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Upversioning netapp Hello, I m currently working on upversioning the netapp trident installer that is used with the netapp storage backend. Reviews [1] and [2] will be merged soon. As part of this upversioning effort a set of docker images are being updated as well. If you are using your own private docker registry mirror, you should add the following images to your mirror: - docker.io/netapp/trident:20.04.0 - quay.io/k8scsi/csi-provisioner:v1.6.0​ - quay.io/k8scsi/csi-attacher:v2.2.0​ - quay.io/k8scsi/csi-resizer:v0.5.0​ - quay.io/k8scsi/csi-node-driver-registrar:v1.3.0​ - quay.io/k8scsi/csi-snapshotter:v2.1.0 [1]: https://review.opendev.org/723606 [2]: https://review.opendev.org/724237 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3923 bytes Desc: image001.png URL: From scott.little at windriver.com Wed Apr 29 18:00:23 2020 From: scott.little at windriver.com (Scott Little) Date: Wed, 29 Apr 2020 14:00:23 -0400 Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 97 - Still Failing! In-Reply-To: <876349594.1263.1588178302997.JavaMail.javamailuser@localhost> References: <2063757745.1248.1588147323756.JavaMail.javamailuser@localhost> <876349594.1263.1588178302997.JavaMail.javamailuser@localhost> Message-ID: <7d00ae91-082b-8c19-7a3b-b06136393eae@windriver.com> https://bugs.launchpad.net/starlingx/+bug/1875945 No lst entry for python2-sphinxcontrib-apidoc. Scott On 2020-04-29 12:38 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_layer_distro_master_master > Build #: 97 > Status: Still Failing > Timestamp: 20200429T150526Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200429T150526Z/logs > -------------------------------------------------------------------------------- > Parameters > > FULL_BUILD: false > FORCE_BUILD: 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 ildiko.vancsa at gmail.com Wed Apr 29 18:28:11 2020 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 29 Apr 2020 20:28:11 +0200 Subject: [Starlingx-discuss] StarlingX confirmation presentation dry-run and feedback session with OSF Message-ID: <1B873953-D8AC-48DC-81CA-63AB8EB2330F@gmail.com> Hi StarlingX Community, I’m reaching out to you about the confirmation process for the StarlingX project. As part of the steps we will hold a presentation dry-run and feedback session with OSF staff. __The time of the meeting is: May 11 at 6am Pacific / 8am Central / 1300 UTC__ Call details are below. Please let me know if you have any questions. Thanks, Ildikó Join Zoom Meeting https://zoom.us/j/98652437540 Meeting ID: 986 5243 7540 One tap mobile +16468769923,,98652437540# US (New York) +16699006833,,98652437540# US (San Jose) Dial by your location +1 646 876 9923 US (New York) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) Meeting ID: 986 5243 7540 Find your local number: https://zoom.us/u/abw3Yq8diE From bruce.e.jones at intel.com Wed Apr 29 19:28:43 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 29 Apr 2020 19:28:43 +0000 Subject: [Starlingx-discuss] Need help with commit In-Reply-To: <7cb231a4-be8b-fe62-5594-008a5c2f305c@linux.intel.com> References: <4263f69d-dc32-a49f-7dfd-31feb425cd02@linux.intel.com> <7cb231a4-be8b-fe62-5594-008a5c2f305c@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818B01080B486B@fmsmsx123.amr.corp.intel.com> +1 to Saul. I agree that clamping the version is not the correct approach. We should bite the bullet and fix the issues as they are found. brucej -----Original Message----- From: Saul Wold Sent: Wednesday, April 29, 2020 10:01 AM To: Bailey, Henry Albert (Al) ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Need help with commit On 4/29/20 6:56 AM, Bailey, Henry Albert (Al) wrote: > I uploaded a fix, by clamping pylint (same as I did for 2 other repos > that hit the same issue). > https://bugs.launchpad.net/starlingx/+bug/1875705 > Your review will merge through a 'recheck' after this one merges. > Are we sure we want to clamp the version, don't we want to file LP or stories against the pylint issues and fix them and then release the clamp? Maybe we need a general pylint story? I think that we should be keeping up with pylint as it can find real issues. > If someone wants to keep pylint floating on its latest release (which > could cause another break the next time one is released), they could > update the 'is_ceph_healthy' method, and/or the 2 places it is called > to resolve the issue. > > Al > ---------------------------------------------------------------------- > -- > *From:* Saul Wold > *Sent:* Tuesday, April 28, 2020 12:07 PM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] Need help with commit > > > On 4/28/20 8:52 AM, Trica, Mihail-Laurentiu wrote: >> Hello, >> >> I have made a few commits and there is just one that is up for review: >> https://review.opendev.org/#/c/716554/. I have modified the commit >> following commit review. Yang Liu has been the one that reviewed my >> commit and the commits of my fellow Intel colleagues. Yang gave it a >> Code Review +2 and a Workflow +1 and Zuul started its checks again. >> What I can see now is that Zuul gave it a -2 because one of its >> pylint check failed(logs are available HERE >> ). > >> The only problem is that it had give it a +1 after I made my final >> changes. Basically the history for the last patchset is this one: >> >> - I uploaded patchset 6, Zuul started its jobs, gave it +1 >> >> - Yang did the code review and gave it a Code Review +2 and a >> Workflow +1 >> >> - finally Zuul restarted its checks, but it had an error for the >> pylint job and it gave it a -2 >> > pylint was changed recently to a newer / stricter version that's why > your getting new errors. > >>  From the logs the error is not on any of the files that I modified >>in the commit, but on: >> “automated-pytest-suite/keywords/storage_helper.py:424:8: E0633: >> Attempting to unpack a non-sequence defined at line 52 >>(unpacking-non-sequence)”. My code is not even using storage-helper. >>How can subsequent checks fail on code that has not been modified? Is >>there a way to re-trigger Zuul checks? In the meantime I have rebased the commit. >> > It's failing not because of the code you added, but because pylint is > checking all the code and found an issue since it's running with > stricter rules now. > > you can add a "recheck" reply to your commit from review.opendev.org. > > Hope that helps > >     Sau! > >> Toate cele bune/Kind regards/Mit freundlichen >> Grüßen/Cordialement/Cordiali saluti/с уважением/z poważaniem >> >> よろしくお願いいたします >> >> 此致 >> >> 敬礼 >> >> *Mihail-Laurenţiu Trică*, Software Engineer >> >> >> _______________________________________________ >> 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 Sabeel.Ansari at windriver.com Wed Apr 29 20:01:45 2020 From: Sabeel.Ansari at windriver.com (Ansari, Sabeel) Date: Wed, 29 Apr 2020 20:01:45 +0000 Subject: [Starlingx-discuss] Openstack issues Message-ID: Hi, Last couple of days, I've noticed that stx-openstack has been quite unstable on both VM & hw platforms. Multiple times, it was noticed the 'system application-apply stx-openstack' command fail to apply and hang or quit with errors. I just pushed a commit on this project to clean up nginx-ingress-controller in the kube-system namespace. This is a minor change and does not affect other components (read: the instability is not addressed by this). The cleanup is marked as part of the cert-mgr work - since nginx-ingress-controller is now introduced as a standalone app. This commit removes the external facing (kube-system namespace) nginx ingress-controller. The internal ingress controller (in openstack namespace) has no changes. Regards, Sabeel -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Wed Apr 29 21:24:47 2020 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 29 Apr 2020 21:24:47 +0000 Subject: [Starlingx-discuss] June Virtual PTG candidate feature list? Message-ID: Hi Bruce; There is a placeholder for R5 on the PTG etherpad [0]. I would start with a list there for now. Regards; Ian [0] - https://etherpad.opendev.org/p/stx-virtual-PTG-June From: "Jones, Bruce E" Date: Wednesday, April 29, 2020 at 12:25 PM To: StarlingX ML Subject: [Starlingx-discuss] June Virtual PTG candidate feature list? Do we have a list of candidate features for the vPTG? I’d like to add a few. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicolae.jascanu at intel.com Wed Apr 29 22:14:11 2020 From: nicolae.jascanu at intel.com (Jascanu, Nicolae) Date: Wed, 29 Apr 2020 22:14:11 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200427T233018Z Message-ID: Sanity Test from 2020-April-27 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200427T233018Z/outputs/iso/) Status: RED Provisioning is failing for all configurations. We created a new bug: https://bugs.launchpad.net/starlingx/+bug/1875986 We used the helm chart from http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/helm-charts/ Regards, STX Validation Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Apr 30 03:04:11 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 23:04:11 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 287 - Failure! Message-ID: <1118756797.1267.1588215852754.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer_layered Build #: 287 Status: Failure Timestamp: 20200430T013518Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200430T013118Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200430T013118Z DOCKER_BUILD_ID: jenkins-master-distro-20200430T013118Z-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/20200430T013118Z/logs FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200430T013118Z/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 Thu Apr 30 03:04:15 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 29 Apr 2020 23:04:15 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 98 - Still Failing! In-Reply-To: <404725626.1261.1588178300563.JavaMail.javamailuser@localhost> References: <404725626.1261.1588178300563.JavaMail.javamailuser@localhost> Message-ID: <204088410.1270.1588215856435.JavaMail.javamailuser@localhost> Project: STX_build_layer_distro_master_master Build #: 98 Status: Still Failing Timestamp: 20200430T013118Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/20200430T013118Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From 18245043314 at 163.com Thu Apr 30 03:15:39 2020 From: 18245043314 at 163.com (zhou) Date: Thu, 30 Apr 2020 11:15:39 +0800 (CST) Subject: [Starlingx-discuss] stuck in installing stx in bare metal In-Reply-To: References: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> Message-ID: <48031802.7b2f.171c915282f.Coremail.18245043314@163.com> Dear sir: No, We don't use USB for we cannot get in touch with the machine right now. We connect to the machine with IMPL network, and insert the stx boot image with function called "virtual storage" in the ikvm environment. Do we have to plug the USB into the machine physically? yours, zhou qingyang 在 2020-04-29 12:01:25,"Penney, Don" 写道: Can you provide details about how you’re trying to install? Are you installing from USB? From: zhou [mailto:18245043314 at 163.com] Sent: Tuesday, April 28, 2020 11:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: we are trying to install all-in-one stx in bare metal environment, but we stuck in the screen says "starting terminate plymouth boot screen". Do you have any idea about that problem? yours, zhou qingyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Apr 30 03:35:26 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 30 Apr 2020 03:35:26 +0000 Subject: [Starlingx-discuss] stuck in installing stx in bare metal In-Reply-To: <48031802.7b2f.171c915282f.Coremail.18245043314@163.com> References: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> <48031802.7b2f.171c915282f.Coremail.18245043314@163.com> Message-ID: Hi zhou: No, IMPI virtual storage worked fine for installing starlingx . 1) what kind of HW config ? does it have any vpu/gpu ? 2) have you enter select menu “Graphical Console” and “Serial Console” and what is your choice if you enter this menu ? Thanks. BR Austin Sun. From: zhou <18245043314 at 163.com> Sent: Thursday, April 30, 2020 11:16 AM To: Penney, Don Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: No, We don't use USB for we cannot get in touch with the machine right now. We connect to the machine with IMPL network, and insert the stx boot image with function called "virtual storage" in the ikvm environment. Do we have to plug the USB into the machine physically? yours, zhou qingyang 在 2020-04-29 12:01:25,"Penney, Don" > 写道: Can you provide details about how you’re trying to install? Are you installing from USB? From: zhou [mailto:18245043314 at 163.com] Sent: Tuesday, April 28, 2020 11:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: we are trying to install all-in-one stx in bare metal environment, but we stuck in the screen says "starting terminate plymouth boot screen". Do you have any idea about that problem? yours, zhou qingyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From 18245043314 at 163.com Thu Apr 30 03:54:26 2020 From: 18245043314 at 163.com (zhou) Date: Thu, 30 Apr 2020 11:54:26 +0800 (CST) Subject: [Starlingx-discuss] stuck in installing stx in bare metal In-Reply-To: References: <2f0b8939.62de.171c40a3619.Coremail.18245043314@163.com> <48031802.7b2f.171c915282f.Coremail.18245043314@163.com> Message-ID: <1c6540fa.8e34.171c938abf0.Coremail.18245043314@163.com> Dear sir, 1.) No, the HW config says that our machine has 2 cpus but no vcpu/gpu. 2.) Yes, we are using "Graphical Console” because "Serial Console" will stuck in the very beginning: the screen will turn black after chosing that and just stuck there. yours, zhou qingyang. 在 2020-04-30 11:35:26,"Sun, Austin" 写道: Hi zhou: No, IMPI virtual storage worked fine for installing starlingx . 1) what kind of HW config ? does it have any vpu/gpu ? 2) have you enter select menu “Graphical Console” and “Serial Console” and what is your choice if you enter this menu ? Thanks. BR Austin Sun. From: zhou <18245043314 at 163.com> Sent: Thursday, April 30, 2020 11:16 AM To: Penney, Don Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: No, We don't use USB for we cannot get in touch with the machine right now. We connect to the machine with IMPL network, and insert the stx boot image with function called "virtual storage" in the ikvm environment. Do we have to plug the USB into the machine physically? yours, zhou qingyang 在 2020-04-29 12:01:25,"Penney, Don" 写道: Can you provide details about how you’re trying to install? Are you installing from USB? From: zhou [mailto:18245043314 at 163.com] Sent: Tuesday, April 28, 2020 11:46 PM To:starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] stuck in installing stx in bare metal Dear sir: we are trying to install all-in-one stx in bare metal environment, but we stuck in the screen says "starting terminate plymouth boot screen". Do you have any idea about that problem? yours, zhou qingyang -------------- next part -------------- An HTML attachment was scrubbed... URL: From vnish11 at gmail.com Thu Apr 30 04:02:19 2020 From: vnish11 at gmail.com (Nishant Verma) Date: Thu, 30 Apr 2020 00:02:19 -0400 Subject: [Starlingx-discuss] installation help Message-ID: Hi All, I am trying to install StarlingX on my machine. I opted for Bare metal All-in-one Simplex Installation R3.0 k8s version. I am having an issue in assigning host storage list for controller node. [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list controller-0 +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ | uuid | device_no | device_ | device_ | size_ | available_ | rpm | serial_ | device_path | | | de | num | type | gib | gib | | id | | +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ | d00e1340-4b9b-48f5-b5fe-977aeae8a46e | /dev/sda | 2048 | SSD | 232. | 23.863 | N/A | S21NNXB | /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0 | | | | | | 885 | | | GA49712 | | | | | | | | | | H | | | | | | | | | | | | +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ After that, I executed: [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} But as I highlighted the above difference, I am looking for sdb whereas I don’t have that in my system configuration. Because of that allpcation of storage for controller is failing and I am not able to unlock controller. [sysadmin at controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Cannot unlock node until at least 1 osd stor is configured for tier 'storage' Please guide me, what to do to resolve the issue. Thanks in advance. -NV -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Apr 30 04:57:19 2020 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 30 Apr 2020 04:57:19 +0000 Subject: [Starlingx-discuss] installation help In-Reply-To: References: Message-ID: Hi Verma: The additional disk like sdb is requested for R3.0 release for storage backend ceph . Please check HW Requirements [1]. [1] https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html From: Nishant Verma Sent: Thursday, April 30, 2020 12:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] installation help Hi All, I am trying to install StarlingX on my machine. I opted for Bare metal All-in-one Simplex Installation R3.0 k8s version. I am having an issue in assigning host storage list for controller node. [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list controller-0 +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ | uuid | device_no | device_ | device_ | size_ | available_ | rpm | serial_ | device_path | | | de | num | type | gib | gib | | id | | +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ | d00e1340-4b9b-48f5-b5fe-977aeae8a46e | /dev/sda | 2048 | SSD | 232. | 23.863 | N/A | S21NNXB | /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0 | | | | | | 885 | | | GA49712 | | | | | | | | | | H | | | | | | | | | | | | +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ After that, I executed: [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} But as I highlighted the above difference, I am looking for sdb whereas I don’t have that in my system configuration. Because of that allpcation of storage for controller is failing and I am not able to unlock controller. [sysadmin at controller-0 ~(keystone_admin)]$ system host-unlock controller-0 Cannot unlock node until at least 1 osd stor is configured for tier 'storage' Please guide me, what to do to resolve the issue. Thanks in advance. -NV -------------- next part -------------- An HTML attachment was scrubbed... URL: From yu.chengde at 99cloud.net Thu Apr 30 10:11:11 2020 From: yu.chengde at 99cloud.net (YuChengDe) Date: Thu, 30 Apr 2020 18:11:11 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5BOpenStack_Upgrade=5D_Failed_when?= =?utf-8?q?_armada-helm_apply_stx-openstack?= Message-ID: Hi Chris: The ussuri openstack images that was installed httpd or apache need rh-python3-mod_wsgi.rpm package. Without this package, armada-helm can not apply stx-openstack. I have put this package in loci/bindep.txt. Please help to review this patch. Many thanks. https://review.opendev.org/#/c/718603/ -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Apr 30 12:25:31 2020 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 30 Apr 2020 08:25:31 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_build_layer_flock_master_master - Build # 99 - Failure! Message-ID: <644257181.1276.1588249532883.JavaMail.javamailuser@localhost> Project: STX_build_layer_flock_master_master Build #: 99 Status: Failure Timestamp: 20200430T122004Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200430T122004Z/logs -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false From vnish11 at gmail.com Thu Apr 30 12:32:06 2020 From: vnish11 at gmail.com (Nishant Verma) Date: Thu, 30 Apr 2020 08:32:06 -0400 Subject: [Starlingx-discuss] installation help In-Reply-To: References: Message-ID: Thanks for the reply. To overcome the issue, I attached the external harddisk to the system. sdb 8:16 0 1.8T 0 disk /data But still I am facing same issue because command host-disk-list is still not able to see the sdb device and at the same time I am able to use the disk as I mounted it and formatted as ext4. On Thu, Apr 30, 2020 at 12:57 AM Sun, Austin wrote: > Hi Verma: > > The additional disk like sdb is requested for R3.0 release for storage > backend ceph . > > Please check HW Requirements [1]. > > > > [1] > https://docs.starlingx.io/deploy_install_guides/r3_release/bare_metal/aio_simplex_hardware.html > > > > *From:* Nishant Verma > *Sent:* Thursday, April 30, 2020 12:02 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] installation help > > > > Hi All, > > > > I am trying to install StarlingX on my machine. I opted for Bare metal > All-in-one Simplex Installation R3.0 k8s version. > > I am having an issue in assigning host storage list for controller node. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list > controller-0 > > > +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ > > | uuid | device_no | device_ | device_ | > size_ | available_ | rpm | serial_ | device_path > | > > | | de | num | type | > gib | gib | | id | > | > > > +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ > > | d00e1340-4b9b-48f5-b5fe-977aeae8a46e | /dev/sda | 2048 | SSD | > 232. | 23.863 | N/A | S21NNXB | > /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0 | > > | | | | | > 885 | | | GA49712 | > | > > | | | | | > | | | H | > | > > | | | | | > | | | | > | > > > +--------------------------------------+-----------+---------+---------+-------+------------+-----+---------+--------------------------------------------+ > > > > After that, I executed: > > [sysadmin at controller-0 ~(keystone_admin)]$ system host-disk-list > controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system > host-stor-add controller-0 {} > > > > But as I highlighted the above difference, I am looking for sdb whereas I > don’t have that in my system configuration. Because of that allpcation of > storage for controller is failing and I am not able to unlock controller. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system host-unlock controller-0 > > Cannot unlock node until at least 1 osd stor is configured for tier > 'storage' > > > > Please guide me, what to do to resolve the issue. Thanks in advance. > > > > -NV > > > > > > > -- Rgds, Nishant -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Thu Apr 30 14:03:33 2020 From: yang.liu at windriver.com (Liu, Yang (YOW)) Date: Thu, 30 Apr 2020 14:03:33 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes - 04/28/2020 Message-ID: Agenda/meeting notes are posted here: https://etherpad.openstack.org/p/stx-test Agenda for 04/28/2020 Attendees: Yang, Cosmin, Nicolae, GeorgeP, Ruediger, Mihail, GeorgeC, Bruce · Sanity Status: * stx-openstack apply failed: https://bugs.launchpad.net/starlingx/+bug/1875449 · stx4.0 testing: * Feature testing: § https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRypzcCpQ6U/edit#gid=0 § Centos8: · Test in progress on new eng load · TPM works on official load - will try on the new eng load · Server with Mellonox is not set up yet § Upversion Openstack services used by flock components on host: · Test completed on eng load § Upgrade Containerized OpenStack to Ussuri · Got eng load, not yet started § Windows Active directory completed · New issue reported § Red fish virual media support in progress · Completing soon. ETA: May1st week. § Kubernetes Upgrade Support in progress · ETA: End of May1st week. Running regression test cases. * Regression testing: § Starting in mid-May. Will pull in test cases. § Nic: Still having risk - configured two system types, more to go. · Two Simplex servers are done - will be used in daily sanity and regression · Two Duplex systems are done - will be used in daily sanity and regression · Standard is in progress - encountered BIOS issue. Expect to complete this week. · Storage is in progress - encountered issues. · Open topic * Test in the open: § Bill sent out email to OpenDev guys - need feedback on config · Have not seen progress · Need to ask how OpenDev does test in the open with virtual on virtual o Nic's team tried virtual on virtual to experiement § VMWARE does not support it § Will try on virtualbox instead * Mihail: § zuul failed - Mihail will email community * code review needs 2 +2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Thu Apr 30 14:47:41 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Thu, 30 Apr 2020 14:47:41 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-29 Message-ID: Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST.   [1]   Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings   [2]   Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-29      All -- reviews merged since last week:  1 (IPv6) All -- bug status -- 7 total, 4 WIP [new ww18] admin endpoints in distributed cloud are changed to https. Where does this go in the docs? Find the place(s) where dist cloud is mentioned -- installation. [ww17]  Debug guide [not started] and Install guide typo [WIP] [ww16] Kata containers [WIP, location under Kubernetes operations] and Build Avoidance (not started; AR Mary compare bug text to existing guide) [ww15] Backup & restore procedure info [WIP, review: 721772]  Ping Mihnea again, cc Frank Miller. Add to Operations section.  All -- Opens from Mary: 2 reviews from Ritu Raj haven't passed the Zuul verification for some reason.  Opendev team may be able to help, send email to this address:  service-discuss at lists.opendev.org If no answer, Mary can try to pull down copy of the review and recommit.   [Dean T used to be able to help, not on project anymore] from Bruce: attended marketing call with foundation today, significant need for blog posts, esp new release, new content. Mary is available to help with edits/proofing as needed.  AR for Bruce and Greg to find likely authors for blog posts within the teams.  Search option for docs: MAKE A STORY - our docs page should have a search option. [Mary ask Kris about search, was it looked into?]   Reviews in progress:    Upgrade Kubernetes version (R4 new content) -- Needs final +2.  WIP: Docker proxy setup Priority 1 task First review merged (1 R3 install guide):  https://review.opendev.org/#/c/718298/ Second review merged (7 R3 install guides): https://review.opendev.org/#/c/720252/ AR Mary update patchset to add pointer to new docker proxy page at the next-higher-level of install guides (similar to the IPv4 note, 1 per Rx folder, see https://review.opendev.org/#/c/718302/) Next review will be for 8 R4 guides. 17Apr Discussion about diagrams - want better alignment between Install diags + Docker Proxy (colors, labels, etc) AR Mary look for PPT source 29Apr Got PPT source for R2 from Kris, figure out how to access it and post updated PPT [[ where link / how to find ]] Mary follow on AR: Dig deeper into the Install guides -- compare them, look at the ways we reuse text. Are there more ways to streamline?  2 areas for improvement: Troubleshooting solution aka "if you get this message, try this". Also, "how you can tell this is working" check after install. From bruce.e.jones at intel.com Thu Apr 30 17:36:29 2020 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 30 Apr 2020 17:36:29 +0000 Subject: [Starlingx-discuss] networking across pods / OpenStack VMs Message-ID: <9A85D2917C58154C960D95352B22818B01080B56CB@fmsmsx123.amr.corp.intel.com> I have a question from a potential user for the Networking team. Is it possible in stx.3.0 to connect applications running in K8S pods to apps running in VMs under OpenStack? If so, how? If not, is that something that we could solve in StarlingX or is this something we'd need the respective upstreams to address? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steven.Webster at windriver.com Thu Apr 30 22:04:41 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Thu, 30 Apr 2020 22:04:41 +0000 Subject: [Starlingx-discuss] MoM: Bi-Weekly StarlingX networking meeting, 4/30/2020 Message-ID: MoM for 4/30 meeting: * TSN * https://storyboard.openstack.org/#!/story/2006746 * A guide has been created about how to enable TSN in KATA w/ StarlingX! * https://review.opendev.org/#/c/724461/ * * IPv6 PXE boot network support * https://storyboard.openstack.org/#!/story/2006442 * No updates, Steve has reached out to the owner * Test * General tests are running locally - AIO-SX, AIO-DX * Few intermittent PXE connectivity issues found in automation * TSN / Kata testing not started, but the guide above should be a huge help * Bug updates: * New: * https://bugs.launchpad.net/starlingx/+bug/1875963 - Enhance StarlingX network documentations * * Updated: * https://bugs.launchpad.net/starlingx/+bug/1859641 - IPv6: stx-openstack app apply failed by time out waiting for the condition "grpc_status" * Fixed * https://bugs.launchpad.net/starlingx/+bug/1866230 - Tracebacks related to LLPD neighbor (INSERT INTO lldp_tlvs) filling sysinv.log * Fixed * https://bugs.launchpad.net/starlingx/+bug/1871469 -- Unable to set Default route in POD with static IP connected with SR-IOV VFs interfaces in Simplex * Marked invalid Thanks, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steven.Webster at windriver.com Thu Apr 30 22:11:19 2020 From: Steven.Webster at windriver.com (Webster, Steven) Date: Thu, 30 Apr 2020 22:11:19 +0000 Subject: [Starlingx-discuss] networking across pods / OpenStack VMs In-Reply-To: References: <9A85D2917C58154C960D95352B22818B01080B56CB@fmsmsx123.amr.corp.intel.com>, Message-ID: Forwarding to the list - didn't 'reply all' ________________________________ From: Webster, Steven Sent: Thursday, April 30, 2020 6:09 PM To: Jones, Bruce E Subject: Re: networking across pods / OpenStack VMs Hi Bruce, It's an interesting and (I think) valid question. The key issue is that there is no coordination between openstack (neutron) networking and kubernetes. Here are some thoughts - keep in mind I have not tried any of this! 1. In StarlingX as it stands today, it would probably be possible to connect a container and VM via SR-IOV. Similar to the neutron issue, there's no coordination between openstack (nova) and the kubernetes SR-IOV device plugin. So you'd probably want to dedicate an entire NIC to SR-IOV use for kubernetes, and an entire NIC to openstack, on separate data networks. Otherwise, it would be possible for kubernetes and openstack to grab the same SR-IOV VF. Of course, you'd want to configure the external switch such that the SR-IOV ports dedicated to kubernetes could reach those dedicated to openstack. 2. I think it would be possible to expose a nodePort to an application running in a kubernetes service. Then, the openstack VMs could communicate via with the app via the nodePort by essentially going 'external' [1] 3. Run the application in a kubernetes pod/container running inside the VM (that has joined the bare-metal cluster). The VM would essentially be seen as another node that has joined the cluster. 4. There's a project which aims to solve some of the neutron/k8s integration - kubernetes-kuyr. This aims to enable neutron networking awareness in a kubernetes cluster [2]. We don't integrate or support this project in StarlingX 3.0+ Happy to continue the discussion if anybody else has any thoughts, Steve [1] https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/ Connecting Applications with Services - Kubernetes This specification will create a Service which targets TCP port 80 on any Pod with the run: my-nginx label, and expose it on an abstracted Service port (targetPort: is the port the container accepts traffic on, port: is the abstracted Service port, which can be any port other pods use to access the Service).View Service API object to see the list of supported fields in service definition. kubernetes.io [2] https://github.com/openstack/kuryr-kubernetes [https://avatars2.githubusercontent.com/u/324574?s=400&v=4] GitHub - openstack/kuryr-kubernetes: Kubernetes integration with OpenStack networking The OpenStack Kuryr project enables native Neutron-based networking in Kubernetes. With Kuryr-Kubernetes it's now possible to choose to run both OpenStack VMs and Kubernetes Pods on the same Neutron network if your workloads require it or to use different segments and, for example, route between ... github.com ________________________________ From: Jones, Bruce E Sent: Thursday, April 30, 2020 1:36 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] networking across pods / OpenStack VMs I have a question from a potential user for the Networking team. Is it possible in stx.3.0 to connect applications running in K8S pods to apps running in VMs under OpenStack? If so, how? If not, is that something that we could solve in StarlingX or is this something we’d need the respective upstreams to address? Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From maryx.camp at intel.com Fri Apr 24 03:28:11 2020 From: maryx.camp at intel.com (Camp, MaryX) Date: Fri, 24 Apr 2020 03:28:11 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 2020-04-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 on Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 2020-04-22 * All -- reviews merged since last week: 2 * All -- bug status -- 7 total, 2 oldies, 5 current * [new ww17] Debug guide, Install guide typo * [ww16] Kata containers and Build Avoidance (AR Mary compare bug text to existing guide text here: https://docs.starlingx.io/developer_resources/build_guide.html#build-avoidance) * [ww15] Backup & restore procedure info, review here: https://review.opendev.org/#/c/721772/ * All -- R4 target content: https://storyboard.openstack.org/#!/story/list?status=active&tags=stx.4.0&project_id=1046 * Assignment of R4 doc tasks ? These stories have no assigned person: * https://storyboard.openstack.org/#!/story/2007223 (update build guide w/ layered build info) Poornima has volunteered for this. Mary assigned her in StoryBoard. * https://storyboard.openstack.org/#!/story/2007222 (update dist cloud bare metal install w/ redfish info) AR Mary check discuss archive, may be covered already? If not ask Tao Liu. * https://storyboard.openstack.org/#!/story/2006588 (updates for Dist Cloud) AR Mary ask Dariush (reference the story) Do we need doc updates? * All -- Opens * Poornima Y. N. joined to discuss her doc review to modify the build guide (https://review.opendev.org/#/c/721517/). She also volunteered to write the layered build guide (see StoryBoard assignment above) * Greg brought up the installation guides - are they being used? are they good? Yes and Maybe not good enough... ? At Shanghai meeting, everyone was using their own cheatsheet install guides -- unclear why they were all different. ? Definitely a good idea to ping the discussion list about what docs we have and how we can improve them. ? Mary suggests poll the list after this next wave of improvements with proxy diagram updates and instructions. * Greg had another question: what about the remainder of the doc set? People are raising Launchpads for new features, which is what we want. What about the existing features that aren't documented? ? How to get a roadmap for documenting the rest of the product, if 40% is covered now. Let's start using the Friday meeting for this topic. ? Greg & Kris made a list of post-install topics to work on: https://etherpad.openstack.org/p/stx-docs-backlog This etherpad also links to other lists. ? How to track what isn't documented? For example, the CLI Commands - we could document each one of them, but is that useful? ? Another option is the online help - we could start bugging the designers to put more info in the online help and automate that into our documentation set. * Reviews in progress: * Upgrade Kubernetes version (R4 new content) -- Review available: https://review.opendev.org/#/c/712583/ * STX IPv6 deployment https://review.opendev.org/#/c/718302/ AR Mary email Joseph Richard directly and ask him for input. * WIP Docker proxy setup Priority 1 task ? 2 reviews merged: https://review.opendev.org/#/c/718298/ and https://review.opendev.org/#/c/720252/ ? Mary add pointer to new docker proxy page at the next-higher-level of install guides (similar to the IPv4 note, 1 per Rx folder, see https://review.opendev.org/#/c/718302/) ? Next review will be for 8 R4 guides. ? 17Apr Discussion about diagrams - want better alignment between Install diags + Docker Proxy (colors, labels, etc) AR Mary look for PPT source ? Mary follow on AR: Dig deeper into the Install guides -- compare them, look at the ways we reuse text. Are there more ways to streamline? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Apr 28 15:53:06 2020 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 28 Apr 2020 15:53:06 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: My suggestion about dropping ceph from PROFILES was only to allow folks to get past the build failure to work on issues overall with the intent of revisiting it, not a permanent solution. I think you need to look at the ceph spec and see if you can enable the python3 build. In addition to enabling the python3 build flag at: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 you will need to also add wheel building, such as: https://opendev.org/starlingx/integ/src/branch/master/virt/libvirt-python/centos/meta_patches/0002-Build-python-wheel.patch and include the wheel in the starlingx wheel tarball: https://opendev.org/starlingx/integ/src/branch/master/centos_stable_wheels.inc From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, April 28, 2020 11:31 AM To: Penney, Don; YuChengDe Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, For glance upgrade, we droped “ceph” from the PROFILES list: It do not install python3-rbd and python3-rados, and we can build out glance image and apply it successfully. However, we met below error when we run openstack image create command. File "/var/lib/openstack/lib/python3.6/site-packages/glance_store/_drivers/rbd.py", line 270, in get_connection 2020-04-28T06:16:37.042835916Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi client = rados.Rados(conffile=conffile, rados_id=rados_id) 2020-04-28T06:16:37.04283789Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi AttributeError: 'NoneType' object has no attribute 'Rados' Does it means we could not use ceph as backend if we drop “ceph” from PROFILES? Or we can only use other backend like file system? Any idea for it? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年3月24日 21:42 To: Liu, ZhipengS ; YuChengDe Cc: starlingx-discuss ; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe > Sent: 2020年3月23日 18:55 To: don.penney > Cc: starlingx-discuss >; Somerville, Jim >; Liu, ZhipengS > Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From austin.sun at intel.com Tue Apr 28 05:10:13 2020 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 28 Apr 2020 05:10:13 +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: 6338 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT68031 1.jpg Type: image/jpeg Size: 7963 bytes Desc: ATT68031 1.jpg URL: From zhipengs.liu at intel.com Tue Apr 28 15:30:33 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 28 Apr 2020 15:30:33 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: Hi Don, For glance upgrade, we droped “ceph” from the PROFILES list: It do not install python3-rbd and python3-rados, and we can build out glance image and apply it successfully. However, we met below error when we run openstack image create command. File "/var/lib/openstack/lib/python3.6/site-packages/glance_store/_drivers/rbd.py", line 270, in get_connection 2020-04-28T06:16:37.042835916Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi client = rados.Rados(conffile=conffile, rados_id=rados_id) 2020-04-28T06:16:37.04283789Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi AttributeError: 'NoneType' object has no attribute 'Rados' Does it means we could not use ceph as backend if we drop “ceph” from PROFILES? Or we can only use other backend like file system? Any idea for it? Thanks a lot! Zhipeng From: Penney, Don Sent: 2020年3月24日 21:42 To: Liu, ZhipengS ; YuChengDe Cc: starlingx-discuss ; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe > Sent: 2020年3月23日 18:55 To: don.penney > Cc: starlingx-discuss >; Somerville, Jim >; Liu, ZhipengS > Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: From zhipengs.liu at intel.com Tue Apr 28 16:10:22 2020 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 28 Apr 2020 16:10:22 +0000 Subject: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images In-Reply-To: References: Message-ID: Now we are trying to enable it like below. Not build it from ceph code Instead we found below packages and try to fix related dependency. python36-rbd-13.2.7-0.el7.x86_64.rpm python36-rados-13.2.7-0.el7.x86_64.rpm Thanks! Zhipeng From: Penney, Don Sent: 2020年4月28日 23:53 To: Liu, ZhipengS ; YuChengDe Cc: starlingx-discuss ; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images My suggestion about dropping ceph from PROFILES was only to allow folks to get past the build failure to work on issues overall with the intent of revisiting it, not a permanent solution. I think you need to look at the ceph spec and see if you can enable the python3 build. In addition to enabling the python3 build flag at: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 you will need to also add wheel building, such as: https://opendev.org/starlingx/integ/src/branch/master/virt/libvirt-python/centos/meta_patches/0002-Build-python-wheel.patch and include the wheel in the starlingx wheel tarball: https://opendev.org/starlingx/integ/src/branch/master/centos_stable_wheels.inc From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, April 28, 2020 11:31 AM To: Penney, Don; YuChengDe Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, For glance upgrade, we droped “ceph” from the PROFILES list: It do not install python3-rbd and python3-rados, and we can build out glance image and apply it successfully. However, we met below error when we run openstack image create command. File "/var/lib/openstack/lib/python3.6/site-packages/glance_store/_drivers/rbd.py", line 270, in get_connection 2020-04-28T06:16:37.042835916Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi client = rados.Rados(conffile=conffile, rados_id=rados_id) 2020-04-28T06:16:37.04283789Z stdout F 2020-04-28 06:16:37.036 9 ERROR glance.common.wsgi AttributeError: 'NoneType' object has no attribute 'Rados' Does it means we could not use ceph as backend if we drop “ceph” from PROFILES? Or we can only use other backend like file system? Any idea for it? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年3月24日 21:42 To: Liu, ZhipengS >; YuChengDe > Cc: starlingx-discuss >; Somerville, Jim > Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images python-rbd is coming from the ceph package. It looks like the spec has support for building python3-rbd, but disabled: https://opendev.org/starlingx/integ/src/branch/master/ceph/ceph/centos/ceph.spec#L861 So you could try enabling it. The other option, of course, would be to drop “ceph” from the PROFILES list: https://opendev.org/starlingx/upstream/src/branch/master/openstack/python-glance/centos/stx-glance.stable_docker_image#L8 From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, March 24, 2020 9:33 AM To: YuChengDe; Penney, Don Cc: starlingx-discuss; Somerville, Jim Subject: RE: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Could you help on this python3-rbd dependency issue? We have to fix this issue to finish cinder image build. Thanks a lot! Zhipeng From: YuChengDe > Sent: 2020年3月23日 18:55 To: don.penney > Cc: starlingx-discuss >; Somerville, Jim >; Liu, ZhipengS > Subject: Re:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don: Thank for your suggestion. After exclude the starlingx_dashboard from initial building, we built the stx-horizon successfully. For now, we have the 12/13 openstack image for Ussuri version. The last should be stx-glance. It needs python3-rbd package during building. However, we just have python-rbd package for our enviroment. Do you have any proposal for how to get the required python3-rbd? + yum -y --setopt=skip_missing_names_on_install=False install ceph-common libxml2 python3-rbd postgresql-libs ^[[0mLoaded plugins: fastestmirror, ovl Loading mirror speeds from cached hostfile * base: ftp.sjtu.edu.cn * extras: mirrors.ustc.edu.cn * updates: ftp.sjtu.edu.cn Package libxml2-2.9.1-6.el7_2.3.x86_64 already installed and latest version No package python3-rbd available. ^[[91mError: Not tolerating missing names on install, stopping. ^[[0mThe command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Command (docker) failed, attempt 1 of 1. [http://mailhz.qiye.163.com/qiyeimage/logo/60511048/1576638602260.jpg] -- ————————————————————————————— 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net 发件人:"Liu, ZhipengS" > 发送日期:2020-03-14 10:30:32 收件人:"Penney, Don" >,YuChengDe >,"starlingx-discuss at lists.starlingx.io" > 抄送人:"Somerville, Jim" > 主题:RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! We will try to do it further according to your proposal. Zhipeng From: Penney, Don > Sent: 2020年3月14日 0:24 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I believe this has dependencies on a variety of StarlingX modules which are currently python2 only. You’ll probably need to exclude starlingx-dashboard for your initial builds, until all the required modules are available for python3. That said, it would be using only small components of these. So an initial effort to get python3 wheels for all the required modules may be small. Smaller than the effort to get these running as python3 on-host, certainly. From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Friday, March 13, 2020 12:20 PM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, We have finished 11/13 images build except for horizon and glance. For horizon, it needs starlingx-dashboard python3 whl. However, in our current build, we just build out starlingx-dashboard python2 whl. Do you have any proposal on how to get the required python3 whl. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 21:00 To: 'Liu, ZhipengS' >; 'Penney, Don' >; 'YuChengDe' >; 'starlingx-discuss at lists.starlingx.io' > Cc: 'Somerville, Jim' > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Don, Chant and I already fixed this issue and other related dependent packages. We modified docker file and related script for wheel build, and rebuilt out all python3 wheels for the packages in stable-wheels.cfg. As for libvirt-python, we still use 4.7.0 version and rebuilt out python3 wheel currently. Will let you know the status after finishing all image build. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2020年3月10日 0:06 To: 'Liu, ZhipengS' >; Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images We also had below issue during build other service image. Looking in links: /tmp/wheels/ Collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) Collecting PyMySQL===0.9.3 Downloading PyMySQL-0.9.3-py2.py3-none-any.whl (47 kB) Processing /tmp/wheels/python_memcached-1.59-py2.py3-none-any.whl Collecting six===1.14.0 Downloading six-1.14.0-py2.py3-none-any.whl (10 kB) Collecting cffi===1.14.0 Downloading cffi-1.14.0-cp36-cp36m-manylinux1_x86_64.whl (399 kB) ERROR: Could not find a version that satisfies the requirement uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) (from versions: none) ERROR: No matching distribution found for uWSGI===2.0.17.1 (from -c /tmp/wheels/upper-constraints.txt (line 816)) Actually, we get uWSGI-2.0.17.1-cp27-cp27mu-linux_x86_64.whl through the link in stable-config file. So far, not sure how many python3 packages we need. From: Liu, ZhipengS > Sent: 2020年3月9日 23:44 To: Penney, Don >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: Re: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Thanks Don! See my inline comments. From: Penney, Don > Sent: 2020年3月9日 23:18 To: Liu, ZhipengS >; YuChengDe >; starlingx-discuss at lists.starlingx.io Cc: Somerville, Jim > Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images I think building the openstack master branch will require moving the images to python3. This has implications to the base image, to how we build the base wheels tarball, and possibly to arguments passed to loci (as well as moving to a newer loci SHA). >> Yes, we have to set python3 = true to loci and also fix a small known bug. I believe Al started looking at this last week, but got pulled off to look at some other issues. From your reply, it sounds like maybe you’ve also done some of this? >> Yes When we explicitly add wheels to the tarball, we update the upper-constraints file to align with the module we’ve included. This would be why the build is looking for 4.7.0 here. There is an upper-constraints.txt file in the tarball itself which you can check. >> Yes, in our script, if we have 4.7.0 in stx repo, it will change the version to 4.7.0 from other versions specified in upper-constraints.txt The libvirt wheel building is python2 only, currently. So it would need to be built for python3 - if that’s possible for 4.7.0. If a newer version of libvirt-python is needed for python3 support, then it will need to be updated. I don’t know how big that effort will be. >> From code, libvirt-python 4.7.0 can support both python2 and python3, but in our code, we just add patch to let it build out python2 whl. >> libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, March 05, 2020 1:06 AM To: Penney, Don; YuChengDe; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [OpenStack Upgrade]Failed when build StarlingX docker images Hi Penney, We just used OpenStack master branch and upper-constraint file below https://raw.githubusercontent.com/openstack/requirements/master/upper-constraints.txt libvirt-python===5.10.0;python_version=='2.7' libvirt-python===6.0.0;python_version=='3.6' libvirt-python===6.0.0;python_version=='3.7' In nova setup.cfg. it adds python require info. python-requires = >=3.6 Then we built python3 related packages to the base image and rebuilt nova image to fix python3 issue. But there is still an error below. collecting cryptography===2.8 Downloading cryptography-2.8-cp34-abi3-manylinux2010_x86_64.whl (2.3 MB) ERROR: Could not find a version that satisfies the requirement libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) (from versions: none) ERROR: No matching distribution found for libvirt-python===4.7.0 (from -c /tmp/wheels/upper-constraints.txt (line 274)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 From code, I saw that we already built libvirt_python-4.7.0-cp27-cp27mu-linux_x86_64.whl through a patch which Seems related to python2. cgcs-root/stx/integ/virt/libvirt-python/centos/meta_patches$ 0002-Build-python-wheel.patch It needs libvirt-python whl for python3, right? Do we have plan to upgrade libvirt-python to 6.0.0? Any comment? Thanks a lot! Zhipeng From: Penney, Don > Sent: 2020年2月27日 0:25 To: YuChengDe >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I was able to successfully build stx-nova image in master with no changes. Do you have any customizations in your environment? From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Wednesday, February 26, 2020 10:38 AM To: YuChengDe; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failed when build StarlingX docker images I guess the upstream nova has updated its requirements.txt to drop support for python2 completely. Al has started digging into the work required to move our image builds to python3, but it’s going to be a multi-day effort. We’re checking to see if there’s a temporary workaround to get this build working in the short term. From: YuChengDe [mailto:yu.chengde at 99cloud.net] Sent: Wednesday, February 26, 2020 5:42 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failed when build StarlingX docker images Hi: I have some problem as building the StarlingX docker image. When I built stx-nova through build-stx-base.sh, the process was stuck, and leave the error log as below. Please offer me some suggestions. Many thanks. ... dirname /opt/loci/scripts/install.sh /opt/loci/scripts/pip_install.sh /tmp/heat pycrypto pylint packages='/tmp/heat pycrypto pylint' pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ /tmp/heat pycrypto pylint DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support ... Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.6"' don't match your environment Ignoring sphinxcontrib-applehelp: markers 'python_version == "3.7"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.6"' don't match your environment Ignoring scikit-learn: markers 'python_version == "3.7"' don't match your environment Looking in links: /tmp/wheels/ Processing /tmp/nova ERROR: Package 'nova' requires a different Python: 2.7.5 not in '>=3.6' command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 [Image removed by sender.] -- —————————————————————————————I 九州云信息科技有限公司 99CLOUD Inc. 于成德 产品开发部 邮箱(Email): yu.chengde at 99cloud.net 手机(Mobile): 13816965096 地址(Addr): 上海市局门路427号1号楼206 Room 206, Bldg 1, No.427 JuMen Road, ShangHai, China 网址(Site): http://www.99cloud.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 823 bytes Desc: image001.jpg URL: