Brent,
I noticed that we have a storyboard [1] approved for stx.3.0 from Matt. By reading the spec [2], I am thinking this might fall into non-openstack-dist
project scope. Can I volunteer to manage the progress in the community?
Thx. - cindy
[1]
https://storyboard.openstack.org/#!/story/2005733
[2] https://review.opendev.org/#/c/665208/
From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Thursday, June 27, 2019 11:27 AM
To: Zhu, Vivian <vivian.zhu@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>; Fang, Liang A <liang.a.fang@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Thanks, Vivian. Let’s put this discussion thread back to mailing list.
Do you expect StarlingX testing team to do specific testing for these two features?
Thx. – cindy
_____________________________________________
From: Zhu, Vivian
Sent: Thursday, June 27, 2019 10:43 AM
To: Xie, Cindy <cindy.xie@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>; Fang, Liang A <liang.a.fang@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Yes, if stx.3.0 take openstack Train release, no back-port needs to have QAT compression feature supported.
- Vivian
SSG OTC NST Storage
Tel: (8621)61167437
_____________________________________________
From: Xie, Cindy
Sent: Thursday, June 27, 2019 10:42 AM
To: Zhu, Vivian <vivian.zhu@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>; Fang, Liang A
<liang.a.fang@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
My understanding is that stx.3.0 is going to be Train based, thus no back-port will be required, correct?
_____________________________________________
From: Zhu, Vivian
Sent: Thursday, June 27, 2019 9:31 AM
To: Xie, Cindy <cindy.xie@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>; Fang, Liang A <liang.a.fang@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
It depends on starlingx’s preference, usually we don’t want to back-port too many patches to starlingX. We can evaluate how much effort needed to back-port/maintain
those patches to StarlingX once we finish the upstreaming in July.
Thanks!
- Vivian
SSG OTC NST Storage
Tel: (8621)61167437
_____________________________________________
From: Xie, Cindy
Sent: Thursday, June 27, 2019 8:58 AM
To: Zhu, Vivian <vivian.zhu@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Good to know that both of these two features will be in stx.3.0.
For QAT support in Cinder & Glance, are you saying that we will not have patches on StarlingX, but only by picking up Openstack Train, then we will have this
feature in stx.3.0?
Thx. - cindy
_____________________________________________
From: Zhu, Vivian
Sent: Thursday, June 27, 2019 8:54 AM
To: Xie, Cindy <cindy.xie@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Cindy,
Both of those two features are targeting to stx3.0. We spend much time on bug fixing to freeze stx2.0 which impact a bit of ceph containerization BP, we will chase it back.
- Ceph containerization
Tingjie is cooking the BP and plan to have a POC firstly to review by Brent. It is in the highest priority feature in storage team and targeting to stx3.0.
- QAT support in Cinder and Glance.
Liang is responsible for this feature. The code development is on track and plan to submit to community review this or next week. Plan to finish code merging in July and include in
Train release. if Stx.3.0 plan to pick up Train release. This feature has no doubt to be missed. BTW, train release is around Oct.16.
- Vivian
SSG OTC NST Storage
Tel: (8621)61167437
-----Original Message-----
From: Xie, Cindy
Sent: Wednesday, June 26, 2019 11:04 PM
To: Zhu, Vivian <vivian.zhu@intel.com>; Chen, Tingjie <tingjie.chen@intel.com>
Cc: Wang, Shane <shane.wang@intel.com>
Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Vivian/Tingjie,
We discussed stx.3.0 feature which came from storage team:
- Ceph containerization
- QAT support in Cinder and Glance.
Brent & Saul do have concern regarding to the short window for 3.0 and suggest that we plan accordingly with resource feasible plan. I am not sure how you prioritize the above
two items, I will put Ceph containerization in higher priority but you have the call. The suggestion from Brent is to do the work in phases: we may not able to have full feature enabled, but we can have part of functionality in and testable.
Let me know if you can have a plan in place so that we can meet stx.3.0 MS3 (mid of Oct).
Thx. - cindy
-----Original Message-----
From: Xie, Cindy [mailto:cindy.xie@intel.com]
Sent: Wednesday, June 26, 2019 9:44 PM
To:
starlingx-discuss@lists.starlingx.io; Rowsell, Brent <Brent.Rowsell@windriver.com>; Wold, Saul <saul.wold@intel.com>
Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack distro meeting, 6/26
Agenda for 6/26 meeting:
- stx.3.0 feature proposal (All)
- Redfish support (https://storyboard.openstack.org/#!/story/2005861)
- Python2to3 transition (https://wiki.openstack.org/wiki/StarlingX/Python2, story to be created)
- non-Openstack patch cleanup (TBD)
- Ceph containerization (https://storyboard.openstack.org/#!/story/2005527, spec under review:
https://review.opendev.org/#/c/656371/), sizing the effort before we commit the feature into 3.0 timeline. Propose staging option.
- Support Kata container (story to be created), not sure yet if this fits into 3.0. first step is to propose TSC and initiate the discussion. Best to put the discussion/proposal
onto the mailing list.
- QAT support in Cinder & Glance (story to be created). AR to Cindy to discussion w/ Vivian for details.
- systemd standardization. Saul: found from multi-OS effort, systemd was used to launch services, there is some services used sysInv instead of systemd. Needs to standarization
to use systemd and move away from hybrid mode.AR to Saul and Marcela to send the technical proposal to mailing list and create SB.
Each team members can bring up your proposed work items so that we can bring up to TSC for discussion & approval.
- Ceph test status report (Abraham/Fernando)
test status tracking:
https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST0rQd4zg/edit#gid=1145711595
16 pass, 6 blocked, 3 retest
2 patches to address task 30351 under SB#2003909 have been merged yesterday. 4 P1 tests shall be unblocked.
AR: Abraham/Fernando to test the 4 P1 cases with the latest build.
- QAT test status report (Ricardo)
test status tracking:
https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST0rQd4zg/edit#gid=84126711
Moving to embedded QAT devices but not yet replicate the success on PCIe card yet. Will continue to preopare the HW and continue
the testing. Already have instructions from Shuicheng, expect to finish the setup by this week.
RESTAPI disable/enable - pending Numan's advice for howto.
- stx.2.0 bug triage and review (Tingjie/Ovidiu/Daniel/Martin; Bin)
- 1829844 : patch available, under review
- 1829855 , patch WIP will upload today.
- 1830191 , coding done, working on dev testing will post for review tomorrow.
- 1831300 , WIP and need retest. One problem is that we are not on latest mimic version.
-1830938, maybe an upstream Ceph issue, cherry pick might be required.
-1832854, under debug, root cause not clear yet.
-1827258 /1832647, kernel log checked, when OOM found the system allocated >14G huge page memory but the whole system memory is only 16G. From Bin's analysis, there
are 7000 huge pages (each huge page size is 2M).When OOM happens, the system was attempt to allocate 4K pages but failed. From Brent, the system reserve 14.5G for system usage, only if all those 14.5G are used up, then OOM will happen.
- Opens (all)
-----Original Message-----
From: Xie, Cindy
Sent: Tuesday, June 25, 2019 9:50 PM
To:
starlingx-discuss@lists.starlingx.io; Rowsell, Brent <Brent.Rowsell@windriver.com>; Wold, Saul <saul.wold@intel.com>
Subject: RE: Weekly StarlingX non-OpenStack distro meeting
Agenda for 6/26 meeting:
- stx.3.0 feature proposal (All)
- Ceph test status report (Abraham/Fernando)
- QAT test status report (Ricardo)
- stx.2.0 bug triage and review (Tingjie/Ovidiu/Daniel/Martin; Bin)
- Opens (all)
-----Original Appointment-----
From: Xie, Cindy
Sent: Thursday, April 25, 2019 5:42 PM
To: Xie, Cindy; 'zhaos'; 'starlingx-discuss@lists.starlingx.io'; 'Rowsell, Brent'; Wold, Saul
Cc: Hu, Wei W; Jones, Bruce E; 'Eslimi, Dariush'; Cobbley, David A; 'Zhi Zhi2 Chang'; Armstrong, Robert H; 'Waines, Greg'; 'Badea, Daniel'; 'Carlos Cebrian'; 'Seiler, Glenn';
Chen, Tingjie; 'Chen, Jacky'; Komiyama, Takeo; Gomez, Juan P; Peng Tan
Subject: Weekly StarlingX non-OpenStack distro meeting
When: Wednesday, June 26, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi.
Where:
https://zoom.us/j/342730236
. 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:
_______________________________________________
Starlingx-discuss mailing list