December 2018 - Starlingx-discuss

[Starlingx-discuss] [Newsletter] What's Happening in the Open Infrastructure Community
by Claire Massey 05 Dec '18

05 Dec '18

Hi everyone, This week, the OSF team distributed the first Open Infrastructure Community Newsletter. Our goal with the bi-weekly newsletter is to provide a digest of the latest developments and activities across open infrastructure projects, events and users. This week, the newsletter highlighted the Berlin Summit as well as brief updates from StarlingX and other OSF projects - OpenStack, Airship, Kata Containers and Zuul. You can checkout the full newsletter on Superuser [1], and if you are interested in receiving the upcoming newsletters, you can subscribe here [2]. If you would like to contribute to a future newsletter or have feedback, please reach out to community(a)openstack.org <mailto:community@openstack.org>. Thanks, Claire [1] http://superuser.openstack.org/articles/inside-open-infrastructure-newslett… <http://superuser.openstack.org/articles/inside-open-infrastructure-newslett…> [2] https://www.openstack.org/community/email-signup <https://www.openstack.org/community/email-signup>

1 0

[Starlingx-discuss] [ Test ] Discussion of the Testing strategy
by Cabrales, Ada 05 Dec '18

05 Dec '18

Hello, This meeting is for having a healthy discussion about the testing strategy for StarlingX. Everyone is welcome Ada Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * International numbers available: https://zoom.us/u/ed95sU7aQ

1 0

Re: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5
by Xie, Cindy 05 Dec '18

05 Dec '18

BTW, Victor, for the current build system, because we are building from source for every build, this is not a problem - it will be guaranteed. However, you brought up a good points that this needs to be kept in mind once our build system moving to Koji, and RPM will be retained in Koji repo (like today's mirror). In this case, we have to keep in mind that when certain key components got upgraded (e.g kernel, toolchain, etc), then we have to re-build the impacted pkgs. Thx. - cindy -----Original Message----- From: Xie, Cindy Sent: Wednesday, December 5, 2018 11:43 PM To: 'Victor Rodriguez' <vm.rod25(a)gmail.com>; starlingx-discuss(a)lists.starlingx.io Subject: RE: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5 Victor, Your comments well received, updated minutes here: https://etherpad.openstack.org/p/stx-distro-other + starlingX ML for the correction. thx. - cindy -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25@gmail.com] Sent: Wednesday, December 5, 2018 11:28 PM To: Xie, Cindy <cindy.xie(a)intel.com> Subject: Re: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5 On Wed, Dec 5, 2018 at 8:35 AM Xie, Cindy <cindy.xie(a)intel.com> wrote: > > Agenda & Notes for 12/5 meeting: > 1. minor kernel version upgrade to 3.10.0.957 (Ken) > https://bugs.launchpad.net/starlingx/+bug/1805759 > security concerns regarding current version, want to upgrade the kernel to 957. Want to get the upgraded kernel to master sooner. Requirement is to get to the kernel version soon in StarlingX master. > This minor kernel version is the one in CentOS 7.1810 release: https://storyboard.openstack.org/#!/story/2004521 > from implemenation: kernel upgrade in higher priority and needs to be done in master. > Shuicheng: only rpm version available, sRPM not available yet - AR: Shuicheng to monitor the CentOS package page. > out of tree driver Kernel drivers upgrade: not sure yet if those kernel drivers (drdb, QAT, etc) have been upgraded to 1810 yet. Can seperate this work as other workitem. > Victor: shouldn't we re-build with the new kernel or not? The answer is YES. I said : Should we rebuild the drivers with the new kernel , please send correction to notes All the drivers shoudl be build agains the kernel source code otherwise the ELF file will not patch with the symbols > 2. CentOS 7.6 upgrade planning (Saul) > - get a list of sRPM/RPM packages that being upgrade in CentOS7.6, size the work item (AR: Shuicheng) > - Feature branch creation (AR to Dean, needs to get the rights from Dean to create feature branch. AR for Shuicheng to contact Dean. Rebase from master on weekly basis. ) > CentOS7.1810 was annouced on Dec 3rd. > storyboard created: https://storyboard.openstack.org/#!/story/2004522, will add tasks once sRPM identified. > > 3. non-Openstack patch refactoring status (Zhipeng) > finished most of the tasks for init/config. Only one patch still pending for RabitMQ for final review. > Saul will fire more storyboards when he finds more init/config issue. > last week we find other related stories, 7 stories finished coding, 2 merged, 3 under review, 2 is invalid. > 167 patch reduction in total now out of 402 patches - good job! > > 4. Qemu 3.0 upgrade status (Ghada/Jim) > Qemu basically ready to push. > AR: Saul to review the patches pushed up by Jim on staging branch. Work w/ Dean to review and if it's good to go, will push. > pre-push validation has been done already. > > 5. Ceph upgrade status update (Vivian/Dehao) > Story and task created @ storyboard. Detail doc created and including every patches. Break down big commits into small patches, new PR sent. 6 WR patches added to this PR. Waiting for Dean's review. > Scott provided some comments on Ceph upgrade in openstack Gerrit - patch updated to address the comments. > ISO image can be built and under testing. 32 patches rebased and included in this new ISO image. > dedicated storage node environment setting from Dev side. If you need help, contact Ada... > > 6. Opens (all) > 6.1 kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) We have successfully installed the Lewis Hill, QAT 8970 Adapter, X16,OEM,S,DUAL-CC - J39967-001, after some issues with our infrastructure, we finally started the proper installation of duplex configuration, today we expect to run some of the tests to see if some issue are seen or not. We are using the latest ISO provided by Shuicheng. > > -----Original Appointment----- > From: Xie, Cindy > Sent: Monday, November 5, 2018 2:27 PM > To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, > Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; > Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; > starlingx-discuss(a)lists.starlingx.io > Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, > Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez > Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; > 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; 'Young, Ken'; Arce > Moreno, Abraham; Cobbley, David A > Subject: Weekly StarlingX non-OpenStack Distro meeting > When: Wednesday, December 5, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). > 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: > o https://etherpad.openstack.org/p/stx-distro-other > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss(a)lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

3 2

Re: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5
by Xie, Cindy 05 Dec '18

05 Dec '18

Victor, Your comments well received, updated minutes here: https://etherpad.openstack.org/p/stx-distro-other + starlingX ML for the correction. thx. - cindy -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25@gmail.com] Sent: Wednesday, December 5, 2018 11:28 PM To: Xie, Cindy <cindy.xie(a)intel.com> Subject: Re: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5 On Wed, Dec 5, 2018 at 8:35 AM Xie, Cindy <cindy.xie(a)intel.com> wrote: > > Agenda & Notes for 12/5 meeting: > 1. minor kernel version upgrade to 3.10.0.957 (Ken) > https://bugs.launchpad.net/starlingx/+bug/1805759 > security concerns regarding current version, want to upgrade the kernel to 957. Want to get the upgraded kernel to master sooner. Requirement is to get to the kernel version soon in StarlingX master. > This minor kernel version is the one in CentOS 7.1810 release: https://storyboard.openstack.org/#!/story/2004521 > from implemenation: kernel upgrade in higher priority and needs to be done in master. > Shuicheng: only rpm version available, sRPM not available yet - AR: Shuicheng to monitor the CentOS package page. > out of tree driver Kernel drivers upgrade: not sure yet if those kernel drivers (drdb, QAT, etc) have been upgraded to 1810 yet. Can seperate this work as other workitem. > Victor: shouldn't we re-build with the new kernel or not? The answer is YES. I said : Should we rebuild the drivers with the new kernel , please send correction to notes All the drivers shoudl be build agains the kernel source code otherwise the ELF file will not patch with the symbols > 2. CentOS 7.6 upgrade planning (Saul) > - get a list of sRPM/RPM packages that being upgrade in CentOS7.6, size the work item (AR: Shuicheng) > - Feature branch creation (AR to Dean, needs to get the rights from Dean to create feature branch. AR for Shuicheng to contact Dean. Rebase from master on weekly basis. ) > CentOS7.1810 was annouced on Dec 3rd. > storyboard created: https://storyboard.openstack.org/#!/story/2004522, will add tasks once sRPM identified. > > 3. non-Openstack patch refactoring status (Zhipeng) > finished most of the tasks for init/config. Only one patch still pending for RabitMQ for final review. > Saul will fire more storyboards when he finds more init/config issue. > last week we find other related stories, 7 stories finished coding, 2 merged, 3 under review, 2 is invalid. > 167 patch reduction in total now out of 402 patches - good job! > > 4. Qemu 3.0 upgrade status (Ghada/Jim) > Qemu basically ready to push. > AR: Saul to review the patches pushed up by Jim on staging branch. Work w/ Dean to review and if it's good to go, will push. > pre-push validation has been done already. > > 5. Ceph upgrade status update (Vivian/Dehao) > Story and task created @ storyboard. Detail doc created and including every patches. Break down big commits into small patches, new PR sent. 6 WR patches added to this PR. Waiting for Dean's review. > Scott provided some comments on Ceph upgrade in openstack Gerrit - patch updated to address the comments. > ISO image can be built and under testing. 32 patches rebased and included in this new ISO image. > dedicated storage node environment setting from Dev side. If you need help, contact Ada... > > 6. Opens (all) > 6.1 kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) We have successfully installed the Lewis Hill, QAT 8970 Adapter, X16,OEM,S,DUAL-CC - J39967-001, after some issues with our infrastructure, we finally started the proper installation of duplex configuration, today we expect to run some of the tests to see if some issue are seen or not. We are using the latest ISO provided by Shuicheng. > > -----Original Appointment----- > From: Xie, Cindy > Sent: Monday, November 5, 2018 2:27 PM > To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, > Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; > Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; > starlingx-discuss(a)lists.starlingx.io > Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, > Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez > Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; > 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; 'Young, Ken'; Arce > Moreno, Abraham; Cobbley, David A > Subject: Weekly StarlingX non-OpenStack Distro meeting > When: Wednesday, December 5, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). > 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: > o https://etherpad.openstack.org/p/stx-distro-other > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss(a)lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

1 0

[Starlingx-discuss] Community meeting Dec 5th agenda and notes
by Jones, Bruce E 05 Dec '18

05 Dec '18

Agenda and notes - Dec 5th call * Please register for the January community meeting so we can get a count for logistics (meals, etc...): https://starlingx_jan2019meetup.eventbrite.com<https://starlingx_jan2019meetup.eventbrite.com/> * Discuss planning process and preparation for the community meet-up. o Should the agenda be focused on what the teams are doing? On what features we want to deliver? Or both? ? Ian - split the agenda into: Short term items, big long term items, CI/CD/test, Process & Governance ? Bruce - my goal for the meeting is to finalize the release plan - content and schedule ? Ian - another goal is for the TSC to align on the vision for the project * How do we manage / do planning for features that span sub-project? How do we track the progress of large complex multi-story features? ? Adopting a higher level planning tool - e.g. Jira, Trello, etc...? ? For now using multiple Etherpads to manage and track complex projects o Discuss alignment with OpenStack milestones and the planning assumptions built into that model. Release plan to be reviewed with TSC tomorrow. * Discuss Multi-OS and Zuul project team status since we ran out of time in the Nov 28th meeting. o Multi-OS status: (Bruce) ? Spec review status * Specs still pending: https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx… o https://review.openstack.org/#/c/619801/ o https://review.openstack.org/#/c/621033/ ? Victor to fix the tox failures (trailing white space/etc...). ? DevStack status * https://review.openstack.org/#/c/620988/ - needs reviewers * https://review.openstack.org/#/c/620806/ - Has self WF-1 from Yi while he runs some last minute checks * https://review.openstack.org/#/c/616402/ - Mingyuan to respond to Dean's feedback ? Zuul status (Cesar) * Has been a lower priority. Has been some background activity. Team is not meeting. Cesar is looking for volunteers to join the team! * Should this be part of the Test team? * We should add Test Strategy to the community meeting agenda and have a comprehensive discussion. * Question from the team working on the FlexRAN demo: By default, Ironic services are NOT enabled in StarlingX system. What's the reasons in the background at the first place? BTW, they were not enabled by default in Titanium R5, according to the feedback from FlexRAN team. o This was a decision made at the seed code release to make it an optional feature to cut down on foot print. Only useful for bare metal workloads. This will all be changing in the next release with the new container architecture which will reduce the need for bare metal support (use containers instead). Bruce to follow up with the team to make sure they are OK with manual steps.

1 0

Re: [Starlingx-discuss] Propose to add Al Bailey to core reviewers for stx-config
by Kung, John 05 Dec '18

05 Dec '18

+1 , Ok with me to add Al Bailey as core reviewer for stx-config Thanks, John Kung From: Wensley, Barton [mailto:Barton.Wensley@windriver.com] Sent: Tuesday, December 04, 2018 9:01 AM To: starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Propose to add Al Bailey to core reviewers for stx-config Hi, I'd like to add Al Bailey as a core reviewer for stx-config. Al is one of the top contributers to stx-config - both in code contribution and in doing many useful reviews: http://stackalytics.com/?project_type=all&release=all&metric=all&module=stx… I'd like confirmation (or objections) from the existing cores please... Bart Wensley, Member of Technical Staff, Wind River direct 613.963.1385

2 1

[Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 12/5
by Xie, Cindy 05 Dec '18

05 Dec '18

Agenda & Notes for 12/5 meeting: 1. minor kernel version upgrade to 3.10.0.957 (Ken) https://bugs.launchpad.net/starlingx/+bug/1805759 security concerns regarding current version, want to upgrade the kernel to 957. Want to get the upgraded kernel to master sooner. Requirement is to get to the kernel version soon in StarlingX master. This minor kernel version is the one in CentOS 7.1810 release: https://storyboard.openstack.org/#!/story/2004521 from implemenation: kernel upgrade in higher priority and needs to be done in master. Shuicheng: only rpm version available, sRPM not available yet - AR: Shuicheng to monitor the CentOS package page. out of tree driver Kernel drivers upgrade: not sure yet if those kernel drivers (drdb, QAT, etc) have been upgraded to 1810 yet. Can seperate this work as other workitem. Victor: shouldn't we re-build with the new kernel or not? The answer is YES. 2. CentOS 7.6 upgrade planning (Saul) - get a list of sRPM/RPM packages that being upgrade in CentOS7.6, size the work item (AR: Shuicheng) - Feature branch creation (AR to Dean, needs to get the rights from Dean to create feature branch. AR for Shuicheng to contact Dean. Rebase from master on weekly basis. ) CentOS7.1810 was annouced on Dec 3rd. storyboard created: https://storyboard.openstack.org/#!/story/2004522, will add tasks once sRPM identified. 3. non-Openstack patch refactoring status (Zhipeng) finished most of the tasks for init/config. Only one patch still pending for RabitMQ for final review. Saul will fire more storyboards when he finds more init/config issue. last week we find other related stories, 7 stories finished coding, 2 merged, 3 under review, 2 is invalid. 167 patch reduction in total now out of 402 patches - good job! 4. Qemu 3.0 upgrade status (Ghada/Jim) Qemu basically ready to push. AR: Saul to review the patches pushed up by Jim on staging branch. Work w/ Dean to review and if it's good to go, will push. pre-push validation has been done already. 5. Ceph upgrade status update (Vivian/Dehao) Story and task created @ storyboard. Detail doc created and including every patches. Break down big commits into small patches, new PR sent. 6 WR patches added to this PR. Waiting for Dean's review. Scott provided some comments on Ceph upgrade in openstack Gerrit - patch updated to address the comments. ISO image can be built and under testing. 32 patches rebased and included in this new ISO image. dedicated storage node environment setting from Dev side. If you need help, contact Ada... 6. Opens (all) 6.1 kernel driver upgrade testing status update (Ada/Ricardo/Shuicheng) We have successfully installed the Lewis Hill, QAT 8970 Adapter, X16,OEM,S,DUAL-CC - J39967-001, after some issues with our infrastructure, we finally started the proper installation of duplex configuration, today we expect to run some of the tests to see if some issue are seen or not. We are using the latest ISO provided by Shuicheng. -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Wold, Saul; 'Rowsell, Brent'; Jones, Bruce E; Troyer, Dean; 'Khalil, Ghada'; Waheed, Numan; Lin, Shuicheng; Zhu, Vivian; Shang, Dehao; Liu, ZhipengS; Hu, Yong; Sun, Austin; Somerville, Jim; starlingx-discuss(a)lists.starlingx.io Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Waines, Greg'; 'Chen, Jacky'; Armstrong, Robert H; Perez Rodriguez, Humberto I; Martinez Landa, Hayde; Martinez Monroy, Elio; Hu, Wei W; 'Seiler, Glenn'; 'Eslimi, Dariush'; Gomez, Juan P; Lara, Cesar; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, December 5, 2018 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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: o https://etherpad.openstack.org/p/stx-distro-other

1 0

[Starlingx-discuss] Support IBRS cpu model.
by Sun, Austin 04 Dec '18

04 Dec '18

Hi All: if install StarlingX in compute-node with cpu type 'Skylake-Server-IBRS' , it cannot use 'passthrough' type with keyword hw:cpu_model in favor to create instance It will prompt "No valid host was found. There are not enough hosts available. computer-0: (VCpuModelFilter) Host VCPU model Skylake-Server-IBRS required Passthrough Code 501" After investigation , Libvirt 4.7.0 supports *IBRS (for example IvyBridge-IBRS, Skylake-Server-IBRS) CPU model , but nova and meta favor does not support *IBRS CPU model yet. I have made patch for nova[0] and glance[1]. Nova[0] will support *-IBRS type vcpu when select passthrough Glance[1] will add metadata to support *-IBRS in hw:cpu_model Please review these PRs. Thanks. BR Austin Sun. [0] https://github.com/starlingx-staging/stx-nova/pull/15 [1] https://github.com/starlingx-staging/stx-glance/pull/4

4 13

[Starlingx-discuss] TSC meeting minutes - Nov 29th
by Jolliffe, Ian 04 Dec '18

04 Dec '18

The meeting agenda is here: https://etherpad.openstack.org/p/stx-cores Feel free to propose agenda items, also please recognize we may not get to all items each week. Standing topics: Pending reviews for stx-governance https://review.openstack.org/#/q/project:openstack/stx-governance,n,z Pending reviews for stx-specs https://review.openstack.org/#/q/status:open+AND+project:%255Eopenstack/stx… * Call to TSC members we need some more reviews, please have a look. * We agreed that a simple majority is acceptable and we would wait 48 hours prior to merging after achieving the simple majority. 11/29/18 Distro.openstack project - not active currently. Keep it? Disband it? Use it for driving/tracking work on patch upstreaming and code refactoring? -- brucej (5 min) Proposal is to use this sub-project to track patch elimination and guide this work until we get to master. Rebase would not be part of this project. Agreed by TSC Need to appoint PL/TL for the project - review candidates at next TSC meeting Candidates for PL – call to community members for volunteer Candidates for TL – call to community members for volunteer Can all TSC members attend the proposed Jan 15-16 meetup in Phoenix? -- Bruce (5 min) Looks good for most TSC members, Eventbrite to follow for formal registration for community. Release cadence - changes needed? align with upstream OpenStack? Time based or content based? - Bruce & Ghada (15 min) Recommend we follow the milestone of OpenStack and have our own check list, potentially with some offset (initially 6 weeks and revisit in the future) Proposal is to align to two releases a year along with OpenStack. We could do "dot" release for bugs in between. dot release is defined already and can be done. Can pick up an OpenStack stable as required. Action: Bruce and Ghada will refine the proposal and provide update at next week’s meeting. Update from Brent on patch elimination as discussed on community call (10 min) Brent shared charts - will send out after the call Please provide feedback Update from Miguel - cross project discussions (Neutron/Nova) (5 min) http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000138… Nova response: http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000150… Generally positive response from cross project teams Neutron - Miguel attended the weekly meeting with the STX networking team and the major spec agreed to at the PTG has merged (https://review.openstack.org/#/c/599980 Network Segment Range Management ) Nova - add Stein Numa aware live migration spec - https://review.openstack.org/#/c/599587/ Next release priorities - Ian ( 20 min ) https://ethercalc.openstack.org/fafyo2729fnr Agreed we need a focus meeting on this – sending a proposed time to the TSC – once the meeting time is confirmed it will be posted to the mailing list Action: PL/TL from sub-projects – please review all items tagged as high priority and provide input on whether or not this initiative is staffed for your sub-project or needs to be discussed.

2 1

Re: [Starlingx-discuss] SCM: repo projects revision control
by Liu, Changcheng 04 Dec '18

04 Dec '18

Hi Erich, Do you know which is latest stable version that Ceph could work well on it? I need set the "revision" item for every project as many as possible to fix code repository base. B.R. Changcheng On 00:12 Wed 05 Dec, Cordoba Malibran, Erich wrote: > Hi Liu, > > I think there are two ways to checkout a specific revision in all > projects: > > 1) By using a tag/branch: This should exist in the all the > repositories. For example, you can get the code for the r/2018.10 > release setting the default revision: > > <default remote="starlingx" revision="r/2018.10" /> > > Which BTW doesn't exist in the default.xml for r/2018.10, we need to > fix that. > > 2) Setting a revision per project: This is painful, but you can set a > revision for every repository: > > <project remote="starlingx" name="stx-nfv.git" path="cgcs- > root/stx/stx-nfv" revision="r/2018.10" /> > > Also, you can create/modify your own manifest.xml with the repo tool, > using repo start and other subcommands[0]. The only requirement is that > the manifest.xml should live in a git repository to use repo init. > > I hope this can help. > > -Erich > > [0] https://source.android.com/setup/develop/repo > > > > On Tue, 2018-12-04 at 01:11 +0000, Liu, Changcheng wrote: > > Hi Scott & Dean, > > Is there any way for developers get the exactly same stx source > > code after running below commands? > > repo init -u https://git.starlingx.io/stx-manifest -m default.xml > > repo sync > > > > Currently, some projects are set to be fixed tag/version in > > .repo/manifests/default.xml e.g. kubernetes.git > > 1 +--- 5 lines: <?xml version="1.0" encoding="UTF-8"?>-------- > > ------------------------ > > 6 <remote name="hpe-storage" fetch="https://github.com/hpe-stor > > age" /> > > 7 <remote name="kubernetes" fetch="https://github.com/kubernete > > s" /> > > 8 <remote name="docker" fetch="https://github.com/docker" /> > > 9 +-- 93 lines: <remote name="calico" fetch="https://github.com/p > > rojectcalico" />------ > > 102  > > 103 <project remote="kubernetes" revision="refs/tags/v1.9.6" > > name="kubernetes.git" path="cgcs-root/stx/git/kubernetes"/> > > 104 <project remote="kubernetes" revision="refs/tags/v1.8.3" > > name="dashboard.git" path="cgcs-root/stx/git/kube-dashboard"/> > > 105 +-- 5 lines: <project remote="kubernetes" > > revision="refs/tags/1.14.8" name="dns.git" path="cgcs- > > root/stx/git/kube-dns"/>-- > > > > However, some projects are always moving ahead without setting > > “revision” item. > > > > B.R. > > Changcheng > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

1 0