April 2019 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] [DOCS] Providing input to the docs.starlingx.io documentation
by Tullis, Michael L 18 Apr '19

18 Apr '19

If you are a StarlingX community member that is making changes to StarlingX code that impacts the end user documentation at https://docs.starlingx.io, then please, after completing your gerrit code review, choose one of the options below to help us update the docs: OPTION #1 * Send an email to starlingx-discuss(a)lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> adding the string “[DOCS] ” as a prefix on the message subject line. * The email should contain: * Short summary of the impact to documentation. * Links to any related Storyboard user stories. * Links to related gerrit code review(s). * Description of new or changed functionality, such as: * behavioral changes * procedural changes * CLI syntax changes * Etc. The StarlingX DOCS team will then take this info and integrate it into https://docs.starlingx.io, update the source .rst file(s) for the doc web pages, submit a PR, and add you as a code reviewer. OPTION #2 If you’re passionate about documentation and would like to update the documentation yourself, even better. See the StarlingX Documentation Contributor Guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html. Thanks, The STX DOCS Team.

1 0

[Starlingx-discuss] Trying to debug a stx-openstack-apply failure
by Saul Wold 18 Apr '19

18 Apr '19

Hi Folks, I have been trying to get a deployment up in a libvirt/qemu environment (non-proxy). I am seeing the following issue. I am using the image that passed (mostly) Sanity Test on Monday 4/15 [0]. I am setting this up in AIO-Simplex mode, I have not setup any kind of registry. It seems to start up all the contains and kubectl get pods shows all the pods Running or Completed. I retrieved the stx-openstack-apply.log from armada as recommended by the Container Debug FAQ [1]. I see multiple Errors that the Application apply aborted due to what seems like download failures. As I said, I am not behind any proxy or firewall. It seems to fail during processing chart: osh-openstack-neutron at 65% Not sure what the next steps are to debug this issue. Thanks Sau! [0] http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190415T23… [1] https://wiki.openstack.org/wiki/StarlingX/Containers/FAQ

4 4

[Starlingx-discuss] FW: Association of unused OSDS to storage
by Poncea, Ovidiu 18 Apr '19

18 Apr '19

Hi Martinez, We have partial storage tiers support in the gui. Thus, storage tiers can only be created through cli but, once created, users can add OSDs to the new tiers through gui (see the interface for adding OSDs). [X] Ovidiu ________________________________ From: Martinez Monroy, Elio [elio.martinez.monroy(a)intel.com] Sent: Tuesday, April 09, 2019 9:44 PM To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] Association of unused OSDS to storage Hi, The scenario requires the association of unused OSDs to a storage tier. For this, the test creates a storage tier in a ceph cluster, which I do and consult this way in CLI: [cid:image002.png@01D4EEDA.52761AA0] Next, the test requires the list of OSDs already created in association with a disk, of which I then take a disk with enough available space to create an OSD into: [cid:image003.png@01D4EEDA.52761AA0] However, in Horizon, I am able to see and create partitions and OSDs in the host detail page for the host that I am modifying here: [cid:image004.png@01D4EEDA.52761AA0] But the only place where I am able to see the storage tiers and clusters is in the Storage Overview tab under Platform, and I am unable to modify anything from it within this page: [cid:image005.png@01D4EEDA.52761AA0] My question would be regarding where else I could find the option to create the storage tier within the ceph_cluster in Horizon, and if there is no way to do it from Horizon, if I could create the tier through CLI commands and then update the OSDs through Horizon instead. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.

1 0

Re: [Starlingx-discuss] Upstreaming Automation Framework
by Hu, Yong 18 Apr '19

18 Apr '19

This is indeed a very meaningful contribution to the community. Thanks! Regarding “Next phase will include upstreaming the test case.”, what kind of test cases would we expect to see? API test cases, functional test cases, and/or performance test cases? Regards, -Yong On 16/04/2019, 4:51 AM, "Waheed, Numan" <Numan.Waheed(a)windriver.com<mailto:Numan.Waheed@windriver.com>> wrote: StarlingX community has felt the lack of an automation framework since the beginning of this project. I am excited to share that we are working on upstreaming the automation framework that Wind River has been using for over three years now. This automation framework is based on PyTest but has been customized by adding Keywords that help test case creation simple and quick for this project. PyTest was chosen as automation framework because of its maintainability, debugability, flexibility and scalability. It has simple syntax and parametrization capability that allows to scale quickly. It possesses strong support for test fixtures and state management via setup/teardown hooks. Test case selection and deselection is fairly easy with the use of Markers. As mentioned earlier, this framework has been in use for over three years. The framework and a set of test cases will become available to community in phases. In the first phase, we will be upstreaming the framework and related keywords. Next phase will include upstreaming the test case. We also plan to create a wiki for helping community members in using this framework and executing automated test cases or writing their own test cases. Stay tuned. Numan.

1 0

[Starlingx-discuss] Contrib or Experimental tools location ??
by Saul Wold 18 Apr '19

18 Apr '19

Folks, I know this was brought up as part of the Virtualbox Python deployment tool, which in that case we decided to keep it as was proposed in stx-tools/depolyment/virtualbox (logical location). We are likely going have more contributions that fall into experimental that the community may want to try. Should we have a contrib or experimental repo or subdirectory in stx-tools for these contributions? For example the "StarlingX in a box" work, or another different deployment tool for qemu? Thoughts? Sau!

6 9

[Starlingx-discuss] DevStack next
by Xie, Cindy 18 Apr '19

18 Apr '19

Dean, As we've enabled majority of flocks services with DevStack, I am trying to understand the plan of next step to use those services in Zuul. My understanding is that more tests needs to be added in Zuul to gate the pre-merge. Do you have a plan to write StoryBoards so that we can have community engineers work on those individual tests? Thanks. - cindy

2 1

[Starlingx-discuss] [Containers] Sanity Test - ISO 20190417
by Perez Ibarra, Maria G 18 Apr '19

18 Apr '19

Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-APRIL-17 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190417T14…>) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: 57 TCS [Fail : 57] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform 05 TCs [FAIL] TOTAL: 57 TCS [Fail : 57 TCs] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: 57 TCS [Fail : 57] Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] | 3 TCs FAIL Sanity Platform 05 TCs [PASS] TOTAL: 57 TCS [Fail : 3] Sanity Test is executed in a Containers - Virtual Environment AIO - Simplex Setup 04 TCs [PASS] 1 TCS FAIL Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 61 TCs PASS ] [Fail : 56 TCs] AIO - Duplex Setup 04 TCs [PASS] 2 TCS FAIL Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 61 TCs PASS ] [Fail : 56 TCs] Standard - Local Storage Setup 04 TCs [PASS] 2 TCS FAIL Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 61 TCs PASS ] [Fail : 56 TCs] Standard - Dedicated Storage Setup 04 TCs [PASS] 2 TCS FAIL Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: [ 61 TCs PASS ] [Fail : 56 TCs] -------------------------------------------------------------------------------- system host-lock failed after swact during lab setup https://bugs.launchpad.net/starlingx/+bug/1824994 application-apply stx-openstack failed due to neutron pods failure https://bugs.launchpad.net/starlingx/+bug/1825045 For more detail of the tests: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests#Sanity-OpenStack Regards Maria G.

1 0

[Starlingx-discuss] [Multi-OS] POC project update
by Victor Rodriguez 18 Apr '19

18 Apr '19

Hello everyone in STX community We are very happy to share with you the current state of the Multi-OS POC project we started a few weeks ago: https://github.com/starlingx-staging/stx-packaging Since our last update: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-March/003618.html There have been new features that we have added: 1) Able to build Ubuntu Live image tooling that resolves runtime dependencies: https://github.com/starlingx-staging/stx-packaging#building-an-image-wip-as… $ make iso ISO_TEMPLATE=ubuntu-16.04.6-server-amd64.iso 2) Able to build the DEB files inside Ubuntu containers ( so you don't need to have an Ubuntu system as workstation ). Even If you are not in a Linux machine but it has docker and Makefile tools, you still can build a Starling X package, for example: $ make package PKG=x.stx-fault/fm-mgr DISTRO=ubuntu BUILD_W_CONT=y The flag BUILD_W_CONT=y will create a docker image with all the environment necessary to build the package and leave the results in stx-packaging/configs/docker-ubuntu-img/results/ You can also set there a specific Packages.gz that you prefer with fixed packages versions for your build. 3) Able to build Centos/Fedora/EPEL RPMs using the same tooling. Here is how it works so far: Inside the directory stx-packaging/configs/docker-centos-img/ the developers can run: $ make build PKG=systemd-219-62.el7.src.rpm MOCK_CONFIG=centos-7-i386 The SRPM should be in the container volume ( in this case /tmp/rpmbuild ) , it is also possible to pass the URL variable as part of the make build sentence $ make build PKG=<package name> MOCK_CONFIG= URL=<url where to get the srpm> It has been tested with multiple MOCK_CONFIG files, the supported ones include Centos / Fedora and EPEL ( check /etc/mock for the specific versions ). Is also possible to add your personal MOCK_CONFIG that can point to your local repository or the mirror you prefer. It also has the capability to pass the .spec file and tarball if developers prefer. A more detailed README will be updated soon with examples on how to use it. Summary: * The first goal of the POC which was to build packages of the project in multiple operating systems ( including Ubuntu/Centos ) works! * This POC does not need to modify the current directory structure * Is scalable to other operating systems Next steps and what current state of the POC doesn't do (yet) : * Feedback from community, especially from STX (current and future) developers * Research on a better approach to solving build dependencies * Bring up a Controller 0 * Build the platform to consume OpenStack containers Thanks a lot to contributors to this project: https://github.com/starlingx-staging/stx-packaging/graphs/contributors Regards Victor Rodriguez

1 0

[Starlingx-discuss] [docs][meetings] docs team meeting minutes 4/17/2019
by Tullis, Michael L 17 Apr '19

17 Apr '19

For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike

1 0

[Starlingx-discuss] [StarlingX in a box] Canceling tomorrow's meeting
by Martinez Landa, Hayde 17 Apr '19

17 Apr '19

Hi All, Due to Mexican Holiday (Maundy Thursday) tomorrow, the StarlingX in a box bi-weekly meeting will be canceled. Best, Hayde

2 2