December 2018 - Starlingx-discuss

[Starlingx-discuss] starlingx-staging projects and OpenStack projects future plan
by Quick Convey 13 Dec '18

13 Dec '18

HI, I there any plan to merge "stx-neutron" and "openstack/neutron". I would like to know the future plan about the projects under https://github.com/starlingx-staging A per my understanding, StarlingX will work only with the OpenStack projects under the https://github.com/starlingx-staging , is it right ? Where can I find the additional commits made in "stx-neutron" for edge use-case., any document ? Thanks,

2 1

[Starlingx-discuss] [build] [meetings] Build team meeting Agenda 12/13/2018
by Lara, Cesar 13 Dec '18

13 Dec '18

Build team meeting Agenda 12/13/2018 - bug triage - ISO files retention follow up - overall picture for next gen build system - holiday schedule - Opens Regards Cesar Lara Software Engineering Manager Open Source Technology Center Sent from my mobile phone

1 0

[Starlingx-discuss] Issue from internal Intel user
by Jones, Bruce E 12 Dec '18

12 Dec '18

Yatindra is trying to deploy StarlingX in Simplex mode. I got the following email today. Can we please give him some guidance as to how to get the system up and running? Thank you! brucej Simplex: Controller-0 configuration was success. - Was able to provision controller-0 host as per the StarlingX Installation Simplex link<https://docs.starlingx.io/installation_guide/simplex.html#simplex>. But after unlocking controller-0 as per command "[wrsroot@controller-0 ~(keystone_admin)]$ system host-unlock controller-0", system get rebooted and unable to get to the login screen giving error like in the attached image(stx_reboot_connect_issue) . It is like "State change failed: device is opened by someone". - Reboot takes multiple time and once after 5 times it reached to login screen. Then when I checked status about the controller-0 "[wrsroot@controller-0 ~(keystone_admin)]$ system host-list", in the availability column it says degraded. See Last command in the link<https://docs.starlingx.io/installation_guide/simplex.html#simplex>. - I tried re-installing, but faced another issue about LVM storage backend remaining in the state of configuring for longer time, hence failing to provision controller-0. Please look in the attached image(stxissue_simplex_lvm_configuring) which is output of command [wrsroot@controller-0 ~(keystone_admin)]$ system storage-backend-list" for better understanding. When I run command "[wrsroot@controller-0 ~(keystone_admin)]$ system storage-backend-add lvm -s cinder --confirmed" there was some issue related to connecting to controller-oam interface. As LVM-storage backend state remained in the configuring state for long time, I tried to delete it which was not possible and neither it allowed me to create another.

1 0

[Starlingx-discuss] changing PLATFORM_RELEASE
by Scott Little 12 Dec '18

12 Dec '18

Or master branch builds are still reporting PLATFORM_RELEASE=18.10. This value is also known as the SW_VERSION. To avoid confusion, I propose the following. After we cut a release branch, should always advance the master branch value by at least +1 month beyond that release, but never greater than -1 month to the next projected release date. I propose changing the current master branch to PLATFORM_RELEASE=19.01 Scott

4 5

[Starlingx-discuss] [ Test ] Strategy posted
by Cabrales, Ada 12 Dec '18

12 Dec '18

Hello Please take a look at the strategy proposal uploaded to the wiki [0], your comments are welcome. Thanks! Ada [0] https://wiki.openstack.org/wiki/StarlingX/TestStrategy

1 0

[Starlingx-discuss] Dec 12th 2018 Community meeting minutes
by Jones, Bruce E 12 Dec '18

12 Dec '18

Agenda and notes - Dec 12 call * Next Release Update -- Ghada & Bruce o Release Plan documented at: https://wiki.openstack.org/wiki/StarlingX/Release_Plan o Discussion Details/Options documented at: https://etherpad.openstack.org/p/stx-releases * Please register for the January community meeting so we can get a count for logistics (meals, etc...): https://starlingx_jan2019meetup.eventbrite.com o (ildikov) As of today we have 14 people registered * Looking for volunteers for the distro.openstack team to work on the rebase to OSF master and on patch resolution. o PL: Bruce o TL per area o Neutron - Matt Peters o Nova - Jim Gauld o Horizon - TBD o Neutron work will be handled in the Networking team o Need a meeting timeslot for the Nova and Horizon work. Tuesday AM PDT? 6am PDT / 1400 UTC o Discuss high level plan for this work e.g. branching, etc... * Holiday meeting schedule o No project meetings will be held for the weeks of Dec 24-28 and Dec 31-Jan 4. All StarlingX meetings are canceled for the holiday. We will resume meetings the week of Jan 7th. * Ada is updating the wiki with our proposed Test Strategy. She will post the link today. Please review and provide feedback. Thank you for reviewing the Test Strategy with the team!

1 0

[Starlingx-discuss] Software Management API Documentation - Software Patching and Upgrade
by Quick Convey 12 Dec '18

12 Dec '18

HI, Could you please share the StralingX Software Management API Documentation. I could not find it in https://github.com/openstack/stx-update Please share an example of Software Patching and Upgrade with service restart. Thanks,

1 0

[Starlingx-discuss] Testing for CPEH upversion to v13.2.0?
by Miller, Frank 12 Dec '18

12 Dec '18

Dehao/Cindy: We see the multiple gerrit reviews out for the ceph upversion work and that these are getting closer to being merged. Ovidiu and I plan to attend the Distro non-Openstack call tomorrow but in case you are trying to merge these today can you answer these questions: 1) What testing has been done with the v13.2.0 to validate that this version of CEPH works with StarlingX? 2) The containerization subproject relies heavily on CEPH, not only for the dedicated storage config but also for the other configs. Can we get access to one of your loads before this is merged to determine if CEPH on the other configs works with v13.2.0 or if there are issues that need to be addressed? Frank

3 2

[Starlingx-discuss] Python2to3 status
by Xie, Cindy 12 Dec '18

12 Dec '18

Ian, Saul, Per TSC request, here is the Python2to3 work items we are tracking and status: 1. Repos for flocks with Python code (11 projects) name Storyboards Status Notes Stx-config https://storyboard.openstack.org/#!/story/2003433 WIP Stx-distcloud https://storyboard.openstack.org/#!/story/2004585 Todo New Stx-distcloud-client https://storyboard.openstack.org/#!/story/2004586 Todo New Stx-fault https://storyboard.openstack.org/#!/story/2003310 Merged Stx-gui https://storyboard.openstack.org/#!/story/2003432 Merged Stx-ha https://storyboard.openstack.org/#!/story/2003430 Merged Stx-integ https://storyboard.openstack.org/#!/story/2002909 WIP Stx-metal https://storyboard.openstack.org/#!/story/2003426 Merged Stx-nfv https://storyboard.openstack.org/#!/story/2003427 WIP Stx-update https://storyboard.openstack.org/#!/story/2003429 Merged Stx-upstream https://storyboard.openstack.org/#!/story/2003428 Merged 2. For openStack repos: as we are moving to Stein, so the previous planned activities to backport those Python2to3 patches from master are no longer required. Checked with storage team, I am assuming other teams shall be in same situation. 3. For other OS packages which are with Python code, detail readiness analysis posted here: https://drive.google.com/open?id=1RT3oJJ5umHXZ_A--sJRpA23qB3LFY-lY. In short, we still found ~73 packages (out of 436) lacking of Python3 transition activities from upstream community. This needs to further worked on and finalize the strategy. We will discuss in Wed's non-openstack distro weekly call if people still want details. @Austin, feel free to add anything. Thx. - cindy

2 1

Re: [Starlingx-discuss] [ Test ] Meeting notes - 12/11/2018
by Cabrales, Ada 12 Dec '18

12 Dec '18

Meeting minutes - 12/11 Attendees: Bruce, Elio, Jose, Maria, Abraham, JC, Numan, JP, Ada, David, Cristopher * Test case template - Numan - Numan presented a proposal for a document for writing test cases - Priority - who will define the priority of the test case? The one writing the test case? Suggestions is to define a set of rules for helping on defining the right priority - Question: who will be responsible for maintaining the test management tool? We need to define a role for taking ownership of this task - Feature field: use the storyboard number - Steps: use descriptive steps - Expected results: include check points - Could be written between developer and testing teams - The template is for unit test and functional test - Working on developing tests for new features is along done - Ada to upload the documents to the wiki * Proposal for an unified test suite - Jose - Jose presented robot framework Open source project supports CLI and GUI tests No extra packages required into the entity being tested Can execute native (Stx specific tests) or external suites (like tempest), bash scripting could also be run into Robot Robot uses tags for building test plans: regression, feature, etc It generates reports automatically - Jose to send the presentation to the mailing list for getting feedback from the community - Numan to contribute with the disadvantages they found when evaluating Robot * Pushed for next week: - Sanity testing: coverage improvement - JC * Opens - Testing strategy document to be sent EOD or early tomorrow, talk about this in the community meeting. - Ada - For the Community meeting on January - where to keep all the testing documentation? (not the test cases) Initially at the wiki, but define the final place (StarlingX docs?)

1 0