July 2020 - Starlingx-discuss - lists.starlingx.io

[Starlingx-discuss] Minutes: StarlingX Release Meeting - July 16/2020
by Khalil, Ghada 18 Jul '20

18 Jul '20

Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - Jul 16 2020 stx.4.0 - Build Status - Monolithic build is built, but the containers point to the wrong area (private Scott dockerhub?) - Layered build had issues due to CENGN issues - This is the priority right now. Hope to get it completed today 7/16 - Sanity Status - Started using the monolithic build. Sanity is in progress. - Simplex sanity finished and is green. The rest are still in progress - StoryBoard - https://storyboard.openstack.org/#!/story/list?status=active&project_group_… - Most stories are already closed. A few left to close off: - Ussuri: https://storyboard.openstack.org/#!/story/2007474 - Yong - TSN for Kata: https://storyboard.openstack.org/#!/story/2006746 - Nick - Container Upgrade Prep: https://storyboard.openstack.org/#!/story/2006590 - Dariush - Docs: https://storyboard.openstack.org/#!/story/2007222 - Mary - few stories are continuing in stx.5.0 and will remain open. - Bugs / Cherry-Picks - Cherry-picks have started. Reminder sent to the mailing list today. Ghada also monitoring. - Open Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0&orderby=-datec… - 20 open; about half are related to openstack - Feature Test Update - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRy… - TSN Support in Kata container - Test-cases run and have benchmarks. Testing looked good. - Need to update the test-cases in the google doc and do a final test with the latest stx/4.0 build. - Openstack Rebase to Ussuri - 100 TCs identified. 34 remaining. 11 TCs failed; some LPs opened / more to come. - The remaining TCs will be executed on the 4.0 load. - Regression Test Update - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYti… - Nick: No additional TCs were executed since last week - Yang: Started regression this week. Will move to the latest 4.0 load. - Adjusted Milestones - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpb… - Regression Complete: 2020-07-28 - Release: 2020-07-30 stx.3.0.1 - The commits we were waiting for are all ready to go - There are build issues related to the wheels. - Don is investigating. Should be able to try another build in a few days. stx.5.0 - Need a dedicated session for stx.5.0 planning. Wait until 4.0 is out the door. - Also need to be a bit careful with merges of large featuers in master - Need to review input provided by community related to Openstack rebases and apply learnings in stx.5.0 planning - https://etherpad.opendev.org/p/stx-openstack-rebase

1 0

[Starlingx-discuss] Query on Helm chart version
by N, Poornima Y 18 Jul '20

18 Jul '20

Hi all, Recently while working on one of the development activities I noticed that the Helm version on Starlingx is v2.13.1. While the latest stable version of Helm is already v3.2.4. Is there any plans for upgradation?. Any reasons as to why we are still using Helmv2.13.1? Best Regards, Poornima Y N

2 2

[Starlingx-discuss] [build-report] STX_build_layer_containers_master_master - Build # 43 - Still Failing!
by build.starlingx＠gmail.com 18 Jul '20

18 Jul '20

Project: STX_build_layer_containers_master_master Build #: 43 Status: Still Failing Timestamp: 20200717T172504Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false FORCE_BUILD: false

1 0

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200717T013411Z
by Dimofte, Alexandru 18 Jul '20

18 Jul '20

Sanity Test from 2020-July-17 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200… ) Status: RED Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200… I observed system failing at the provisioning stage on all configurations twice: 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:06:16 [2020-07-17T07:06:16.519Z] Provision :: Tests for provisioning and unlocking controllers, computes and 10:06:16 [2020-07-17T07:06:16.519Z] ============================================================================== 10:39:56 [2020-07-17T07:39:56.218Z] Provisioning Simplex System :: Validates provisioning of a simplex... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] Keyword 'Check Controller Is Unlocked' failed after retrying for 15 minutes. The last error was: You must provide a password via either --os-password or via env[OS_PASSWORD] != unlocked 10:39:56 [2020-07-17T07:39:56.219Z] ------------------------------------------------------------------------------ 10:39:56 [2020-07-17T07:39:56.219Z] Provision :: Tests for provisioning and unlocking controllers, com... | FAIL | 10:39:56 [2020-07-17T07:39:56.219Z] 1 critical test, 0 passed, 1 failed 10:39:56 [2020-07-17T07:39:56.219Z] 1 test total, 0 passed, 1 failed controller-0:~$ . /etc/platform/openrc Openstack Admin credentials can only be loaded from the active controller. controller-0:~$ Regards, STX Validation Team [cid:image002.png@01D65C32.316D3890] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

2 2

[Starlingx-discuss] Sanity RC 4.0 Test MONOLITHIC build ISO 20200715T174043Z
by Dimofte, Alexandru 17 Jul '20

17 Jul '20

Sanity Test from 2020-July-15 (http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/… ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/monolithic/… =========================================== Sanity Test executed on Bare Metal 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 executed on 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 (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 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@01D65BC5.FE0D7CB0] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

2 1

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20200716T043542Z
by Dimofte, Alexandru 17 Jul '20

17 Jul '20

Sanity Test from 2020-July-16 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200… ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200… =========================================== Sanity Test executed on Bare Metal 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 executed on 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 (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 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@01D65BAB.99E97F00] Dimofte Alexandru Software Engineer Transportation Solutions Division Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

1 0

[Starlingx-discuss] Add yum repos and get them propagated to other machines in the cluster
by bnovickovs＠weecodelab.com 17 Jul '20

17 Jul '20

Hi folks, I am wondering, how can I add yum repos to controller and then make those propagated to other machines in the cluster if needed? Is it possible? Thank you

2 1

[Starlingx-discuss] Best way to Upgrade from STX 3.0 to 4.0 without re-installing
by Shashi, Yatindra 17 Jul '20

17 Jul '20

Hi Team, I came to know that possibility to upgrade from stx 3.0 to stx 4.0 seamlessly has been deferred. But would you suggest some best way to do so that there is not much hurdle and I don't need to re-install everything from scratch. Mit freundlichen Grüßen/ with best regards, Yatindra Shashi IoTG DE- Intel Corporation Munich, Germany P Save Paper, Go Digital :) 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

1 0

[Starlingx-discuss] Problem with docker login, wrong realm address returned
by Waines, Greg 17 Jul '20

17 Jul '20

Yeah it’s the /etc/docker-distribution/registry/config.yml file that is the config file for the local registry . And you’re correct that the realm in that file is set to the StarlingX OAM Address. This was done intentionally to support external servers with connectivity to the StarlingX OAM interfaces, as being able to push to the local registry. E.g. a CICD system could push directly to the local registry of this StarlingX system. ( NOTE: it still works for internal starlingx hosts, since they have a path to this OAM IP over the mgmt network. ) So, it is understandable that an external server without connectivity to the StarlingX OAM IP interface, can NOT access the StarlingX local registry. Greg. Hi, I have a STX 3.0 bare metal duplex installation here. Followed the instructions on the web site. Only difference is I added two VLAN interfaces (one for the mgmt network, the other for the cluster-host network). Both controllers are up and running (unlocked, available, online). No alarms. I would like to login to the docker registry (registry.local) from a machine which sits on the mgmt and cluster-host network (but does not have access to the OAM network). When I run the docker login cmd like so: docker login -u admin https://registry.local:9001 I get back: Error response from daemon: Get https://registry.local:9001/v2/: Get https://192.168.30.5:9002/token/?account=admin&client_id=docker&offline_tok…: dial tcp 192.168.30.5:9002: connect: network is unreachable 192.168.30.5 is the floating OAM ip address. Digging a bit deeper I found that this curl command: curl -v -s -H "Content-Type: application/json" -X POST -d '{"username": "'admin'", "password": "'PassWord123*'"}' https://registry.local:9001/v2/_catalog returns: < HTTP/1.1 401 Unauthorized < Content-Type: application/json; charset=utf-8 < Docker-Distribution-Api-Version: registry/2.0 < Www-Authenticate: Bearer realm="https://192.168.30.5:9002/token/ ",service="192.168.204.1:9001",scope="registry:catalog:*" < X-Content-Type-Options: nosniff < Date: Fri, 10 Jul 2020 17:36:33 GMT < Content-Length: 145 So the bearer realm address returned seems to point to the OAM network (to which I don't have access, hence the 'network is unreachable' error). I should also point out the the registry-token-server is configured like so: REGISTRY_TOKEN_SERVER_ADDR=192.168.204.1:9002 REGISTRY_TOKEN_SERVER_ISSUER=bird-token-server REGISTRY_TOKEN_SERVER_KS_ENDPOINT=http://192.168.204.1:5000/v3 REGISTRY_TOKEN_SERVER_TLSCERT=/etc/ssl/private/registry-cert.crt REGISTRY_TOKEN_SERVER_TLSKEY=/etc/ssl/private/registry-cert.key REGISTRY_TOKEN_SERVER_REALM=https://192.168.204.1:9002/token/ REGISTRY_TOKEN_SERVER_KEY=/etc/ssl/private/registry-cert-pkcs1.key Here, the REGISTRY_TOKEN_SERVER_REALM is correctly set to https://192.168.204.1:9002/token/.<https://192.168.204.1:9002/token/> Lastly, the /etc/docker-distribution/registry/config.yml configuration file points to another realm address: auth: token: realm: "https://192.168.30.5:9002/token/" service: "192.168.204.1:9001" issuer: bird-token-server rootcertbundle: /etc/ssl/private/registry-cert.crt What am I missing here? How can I login to the registry from outside the OAM network? Regards, Marc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200710/…> ________________________________ * Previous message (by thread): [Starlingx-discuss] What's the 4.0-rc0 build status?<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009156.html> * Next message (by thread): [Starlingx-discuss] Simplex Installation Question<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009148.html> * Messages sorted by: [ date ]<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/date.html#9…> [ thread ]<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/thread.html…> [ subject ]<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/subject.htm…> [ author ]<http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/author.html…> ________________________________ More information about the Starlingx-discuss mailing list<http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss>

1 0

[Starlingx-discuss] [build-report] STX_4.0_build_layer_containers - Build # 1 - Failure!
by build.starlingx＠gmail.com 16 Jul '20

16 Jul '20

Project: STX_4.0_build_layer_containers Build #: 1 Status: Failure Timestamp: 20200716T054327Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/4.0/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: false

1 0