February 2021 - Starlingx-discuss

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210212T030407Z
by Dimofte, Alexandru 13 Feb '21

13 Feb '21

Sanity Test from 2021-February-12 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… =========================================== 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 [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

1 0

[Starlingx-discuss] Internal endpoint not found
by open infra 12 Feb '21

12 Feb '21

Hi, After installing Stx AIO Simplex, I noticed that system complain for endpoints. Should I run any scripts or activate any service after completion of Openstack installation with STX? I have referred https://docs.starlingx.io/deploy_install_guides/r4_release/openstack/index.… Am I missing anything here? [sysadmin@controller-0 ~(keystone_admin)]$ openstack flavor list internal endpoint for compute service in RegionOne region not found [sysadmin@controller-0 ~(keystone_admin)]$ openstack image list internal endpoint for image service in RegionOne region not found [sysadmin@controller-0 ~(keystone_admin)]$ openstack compute service list internal endpoint for compute service in RegionOne region not found following endpoints are available: http://paste.openstack.org/show/802451/ Services: [sysadmin@controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+----------+-----------------+ | ID | Name | Type | +----------------------------------+----------+-----------------+ | cb8ffd5420d24a08a94679fbadf20fb7 | fm | faultmanagement | | 2445032375f5430a9df5225baa30eced | barbican | key-manager | | 24b4fad8e1f844e39cb1531cef7cf585 | keystone | identity | | 9641b61d35d9487bbdf618cdb7ba3279 | sysinv | platform | | 6baf9deb55de48b597860cdb8621cedb | patching | patching | | 891b5f63ce7f480eab3b69af1650a083 | vim | nfv | | 9d4665b6429a4b959dbfc37062951216 | smapi | smapi | +----------------------------------+----------+-----------------+

2 6

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210211T023342Z
by Dimofte, Alexandru 12 Feb '21

12 Feb '21

Sanity Test from 2021-February-11 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… =========================================== 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 [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

1 0

[Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 1539 - Failure!
by build.starlingx＠gmail.com 11 Feb '21

11 Feb '21

Project: STX_build_lst_audit Build #: 1539 Status: Failure Timestamp: 20210212T024600Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2021… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20210212T023117Z DOCKER_BUILD_ID: jenkins-master-distro-20210212T023117Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2021… PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20210212T023117Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/distro

1 0

[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210210T023311Z
by Dimofte, Alexandru 11 Feb '21

11 Feb '21

Sanity Test from 2021-February-10 (http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… ) Status: GREEN Helm-Chart used: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… =========================================== 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 [Logo Description automatically generated] Dimofte Alexandru Software Engineer STARLINGX TEAM Skype no: +40 336403734 Personal Mobile: +40 743167456 alexandru.dimofte(a)intel.com<mailto:alexandru.dimofte@intel.com> Intel Romania

1 0

[Starlingx-discuss] [STARLINGX 4.0] APPLICATION UPLOAD GETTING FAILED - with LAG Interface
by Lokendra Singh Rathour 10 Feb '21

10 Feb '21

Hello Team, We are trying to setup dedicated Storage setup using StarlingX 4.0 over which we have certain observations/Error during the time of worker Node Configuration for the LAG type Data interfaces. Though we have tweaked the procedure a bit and successfully unlocked the Worker Nodes,we are facing the error in upload the STX Application packages. Steps as followed: STEP 1: We have created bonds for Data Network on Worker Node(reference document: https://docs.starlingx.io/configuration/host_interface_network_config.html#….) * system host-if-add worker-1 -m 1500 -a active_standby data1bond ae eth1 eth2 * system host-if-add worker-1 -m 1500 -a active_standby data2bond ae eth3 eth4 STEP 2: Then further as per the main documents when Configuring data interfaces for worker nodes ( reference document: https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedic…) * SPL=/tmp/tmp-system-port-list * SPIL=/tmp/tmp-system-host-if-list Above files does not have the information of the created Bond interfaces for data Nodes, Further in order to get the the value of ${DATA0IFUUID} and ${DATA1IFUUID} below mentioned commands are executed: DATA0IF=<DATA-0-PORT> DATA1IF=<DATA-1-PORT> PHYSNET0='physnet0' PHYSNET1='physnet1' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list # configure the datanetworks in sysinv, prior to referencing it # in the ``system host-if-modify`` command'. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan for NODE in worker-0 worker-1; do echo "Configuring interface for: $NODE" set -ex system host-port-list ${NODE} --nowrap > ${SPL} system host-if-list -a ${NODE} --nowrap > ${SPIL} DATA0PCIADDR=$(cat $SPL | grep $DATA0IF |awk '{print $8}') DATA1PCIADDR=$(cat $SPL | grep $DATA1IF |awk '{print $8}') DATA0PORTUUID=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $2}') DATA1PORTUUID=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $2}') DATA0PORTNAME=$(cat $SPL | grep ${DATA0PCIADDR} | awk '{print $4}') DATA1PORTNAME=$(cat $SPL | grep ${DATA1PCIADDR} | awk '{print $4}') DATA0IFUUID=$(cat $SPIL | awk -v DATA0PORTNAME=$DATA0PORTNAME '($12 ~ DATA0PORTNAME) {print $2}') DATA1IFUUID=$(cat $SPIL | awk -v DATA1PORTNAME=$DATA1PORTNAME '($12 ~ DATA1PORTNAME) {print $2}') system host-if-modify -m 1500 -n data0 -c data ${NODE} ${DATA0IFUUID} system host-if-modify -m 1500 -n data1 -c data ${NODE} ${DATA1IFUUID} system interface-datanetwork-assign ${NODE} ${DATA0IFUUID} ${PHYSNET0} system interface-datanetwork-assign ${NODE} ${DATA1IFUUID} ${PHYSNET1} set +ex done But in our case these values in the variable(${DATA0IFUUID} and ${DATA1IFUUID}) were not getting populated, therefore we have used the UUID received from command : System host-if-list worker-0 System host-if-list worker-1 We observed that UUID of any ethernet interface mentioned in the file (SPIL=/tmp/tmp-system-host-if-list ) matches with the UUID obtained by running the above command(System host-if-list worker-0 ) , so as we did not get the UUID from the file in case LAG Bonds we passed the Values of UUID directly. STEP 3: Using the change, we were able to successfully unlock the worker Nodes. [sysadmin@controller-0 ~(keystone_admin)]$ system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | available | | 2 | controller-1 | controller | unlocked | enabled | available | | 3 | storage-0 | storage | unlocked | enabled | available | | 4 | storage-1 | storage | unlocked | enabled | available | | 5 | worker-0 | worker | unlocked | enabled | available | | 6 | worker-1 | worker | unlocked | enabled | available | +----+--------------+-------------+----------------+-------------+--------------+ STEP 4: Then Further while running the application-upload: system application-upload stx-openstack-<version>-centos-stable-versioned.tgz Error as below was seen Error: 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app File "/usr/lib64/python2.7/site-packages/sysinv/helm/helm.py", line 317, in _get_helm_chart_overrides 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app cnamespace)) 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app File "/opt/platform/helm/20.06/stx-openstack/1.0-49-centos-stable-versioned/plugins/k8sapp_openstack/helm/neutron.py", line 45, in get_overrides 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app 'hosts': self._get_per_host_overrides() 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app File "/opt/platform/helm/20.06/stx-openstack/1.0-49-centos-stable-versioned/plugins/k8sapp_openstack/helm/neutron.py", line 105, in _get_per_host_overrides 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app 'auto_bridge_add': self._get_host_bridges(host)}) 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app File "/opt/platform/helm/20.06/stx-openstack/1.0-49-centos-stable-versioned/plugins/k8sapp_openstack/helm/neutron.py", line 141, in _get_host_bridges 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app port_name = self._get_interface_port_name(iface) 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app File "/opt/platform/helm/20.06/stx-openstack/1.0-49-centos-stable-versioned/plugins/k8sapp_openstack/helm/neutron.py", line 280, in _get_interface_port_name 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app assert iface['iftype'] == constants.INTERFACE_TYPE_ETHERNET 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app AssertionError 2021-02-05 07:46:40.318 113059 ERROR sysinv.conductor.kube_app Kindly check and help in advising the way forward here w.r.t. as 1. does starlingx support for the bond interface for the Data Networks ? * if yes then do we have any supported document w.r.t the same. Reference Documents: For Deployment: https://docs.starlingx.io/deploy_install_guides/r4_release/bare_metal/dedic… For LAG : : https://docs.starlingx.io/configuration/host_interface_network_config.html#… DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

3 3

[Starlingx-discuss] STX_build_docker_flock_images - Build failed
by Chen, Haochuan Z 10 Feb '21

10 Feb '21

HI scott Now image build fail with stx-keystone-api-proxy, what about skip build fail image, to go on other image build Thanks! Martin, Chen IOTG, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request(a)lists.starlingx.io <starlingx-discuss-request(a)lists.starlingx.io> Sent: Sunday, January 31, 2021 2:22 PM To: starlingx-discuss(a)lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 32, Issue 126 Send Starlingx-discuss mailing list submissions to starlingx-discuss(a)lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request(a)lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner(a)lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. [stable] [build-report] STX_build_docker_flock_images - Build # 321 - Failure! (build.starlingx(a)gmail.com) 2. [stable] [build-report] master STX_build_docker_images_layered - Build # 81 - Still Failing! (build.starlingx(a)gmail.com) 3. [build-report] master STX_build_layer_containers_master_master - Build # 105 - Still Failing! (build.starlingx(a)gmail.com) 4. [stable] [build-report] master STX_build_docker_images_layered - Build # 82 - Still Failing! (build.starlingx(a)gmail.com) 5. [build-report] master STX_build_layer_containers_master_master - Build # 106 - Still Failing! (build.starlingx(a)gmail.com) 6. [stable] [build-report] master STX_build_docker_images_layered - Build # 83 - Still Failing! (build.starlingx(a)gmail.com) 7. [build-report] master STX_build_layer_containers_master_master - Build # 107 - Still Failing! (build.starlingx(a)gmail.com) ---------------------------------------------------------------------- Message: 1 Date: Sat, 30 Jan 2021 19:05:51 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 321 - Failure! Message-ID: <472945709.51.1612051552281.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_flock_images Build #: 321 Status: Failure Timestamp: 20210131T000529Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters WEB_HOST: mirror.starlingx.cengn.ca MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T233107Z OS: centos MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root BASE_VERSION: master-stable-20210130T233107Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… REGISTRY_USERID: slittlewrs LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/logs PUBLISH_TIMESTAMP: 20210130T233107Z FLOCK_VERSION: master-centos-stable-20210130T233107Z WEB_HOST_PORT: 80 PREFIX: master TIMESTAMP: 20210130T233107Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/outputs REGISTRY: docker.io ------------------------------ Message: 2 Date: Sat, 30 Jan 2021 19:05:53 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 81 - Still Failing! Message-ID: <1654307004.54.1612051554528.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images_layered Build #: 81 Status: Still Failing Timestamp: 20210130T234712Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210130T233107Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… MASTER_BUILD_NUMBER: 105 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210130T233107Z DOCKER_BUILD_ID: jenkins-master-containers-20210130T233107Z-builder TIMESTAMP: 20210130T233107Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210130T233107Z/outputs ------------------------------ Message: 3 Date: Sat, 30 Jan 2021 19:05:56 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 105 - Still Failing! Message-ID: <1081325300.57.1612051556649.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_layer_containers_master_master Build #: 105 Status: Still Failing Timestamp: 20210130T233107Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true ------------------------------ Message: 4 Date: Sun, 31 Jan 2021 01:03:45 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 82 - Still Failing! Message-ID: <1063712408.60.1612073026255.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images_layered Build #: 82 Status: Still Failing Timestamp: 20210131T052236Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T050619Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… MASTER_BUILD_NUMBER: 106 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T050619Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T050619Z-builder TIMESTAMP: 20210131T050619Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T050619Z/outputs ------------------------------ Message: 5 Date: Sun, 31 Jan 2021 01:03:48 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 106 - Still Failing! Message-ID: <470021719.63.1612073028646.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_layer_containers_master_master Build #: 106 Status: Still Failing Timestamp: 20210131T050619Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true ------------------------------ Message: 6 Date: Sun, 31 Jan 2021 01:21:38 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] master STX_build_docker_images_layered - Build # 83 - Still Failing! Message-ID: <653138737.66.1612074099171.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images_layered Build #: 83 Status: Still Failing Timestamp: 20210131T062137Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-containers/20210131T060528Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master-containers/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… MASTER_BUILD_NUMBER: 107 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/logs MASTER_JOB_NAME: STX_build_layer_containers_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master-containers PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos/containers PUBLISH_TIMESTAMP: 20210131T060528Z DOCKER_BUILD_ID: jenkins-master-containers-20210131T060528Z-builder TIMESTAMP: 20210131T060528Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/inputs LAYER: containers PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/containers/20210131T060528Z/outputs ------------------------------ Message: 7 Date: Sun, 31 Jan 2021 01:21:40 -0500 (EST) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [build-report] master STX_build_layer_containers_master_master - Build # 107 - Still Failing! Message-ID: <6419772.69.1612074101230.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_layer_containers_master_master Build #: 107 Status: Still Failing Timestamp: 20210131T060528Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/containers/… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true FORCE_BUILD: true ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss(a)lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 32, Issue 126 **************************************************

2 4

[Starlingx-discuss] [docs] [meeting] Docs team notes 10-Feb-21
by Camp, MaryX 10 Feb '21

10 Feb '21

Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 10-Feb-21 All -- reviews merged since last meeting: 3 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. 13 LP are WIP against API documentation, which is generated from source code (low priority). Those reviews are here: https://review.opendev.org/#/q/project:starlingx/config Status/questions/opens How will upstream bugs be assigned? When Launchpads are submitted, Mary will triage them, then bring to this meeting for disposition and assignment. New LP submitted by community member: Documentation needs to be updated for LAG and VLAN type interfaces [https://bugs.launchpad.net/starlingx/+bug/1915285] Installation guides we think have a general note/disclaimer about describing a basic configuration. For this LP, we could add a pointer to Node Management Aggregate info [https://docs.starlingx.io/node_management/starlingx-kubernetes/node_interfa…] For now, we can add more pointers to the install guides to upstreamed docs for special cases like this. AR Mary follow up. New review submitted for STX R5 - Edge Worker for Industrial Deployments: https://review.opendev.org/c/starlingx/docs/+/774595 New section in upstreamed guide about Deployment. Ron says we can delete index.rs1 files after docs are merged/upstreamed. Bruce suggests a glossary/acronym list. We will think about implementing this using the existing abbreviations file. Mary nominates Ron Stone as additional Core Reviewer for Docs - all were in favor. Ron was added to the starlingx-docs-core group. Ron & Juanita were added to the Docs & Infra team members in the wiki: https://wiki.openstack.org/wiki/StarlingX/Docs_and_Infra R5 release notes - DISCUSSION DEFERRED TO NEXT MEETING

1 0

[Starlingx-discuss] Community (& TSC) Call (Feb 10, 2021)
by Zvonar, Bill 10 Feb '21

10 Feb '21

Hi all, reminder of the weekly TSC/Community calls coming up tomorrow. Please feel free to add items to the agenda [0] for the community call. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_… [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210210T1500 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09

1 1

[Starlingx-discuss] rook-ceph patch for enhancement to enable cephfs
by Chen, Haochuan Z 10 Feb '21

10 Feb '21

Hi Bob This is my patch to enable cephfs for rook-ceph. It is enhancement. Please review thanks. https://review.opendev.org/c/starlingx/utilities/+/760503 BR! Martin, Chen IOTG, Software Engineer 021-61164330

1 0