lists.starlingx.io
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

Starlingx-discuss

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2021 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2020 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2019 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2018 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
starlingx-discuss@lists.starlingx.io

February 2021

  • 40 participants
  • 106 discussions
[Starlingx-discuss] [build]: py2 starlingx images locked to python modules from June build?
by Penney, Don 25 Mar '21

25 Mar '21
Hi folks, It was discovered that the recent stx-platformclients image was not picking up recent changes made to the distributedcloud-client package (I believe a Launchpad will be raised shortly). Tracing back through the CENGN build logs, the problem appears to stem from the changes introduced by: https://review.opendev.org/#/c/737456/11/build-tools/build-docker-images/do… So for specific images, including stx-platformclients, the image build is now using a reference to a presumably static tarball: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/stx-centos-… Looking at the dir listing, we can see this tarball is dated June 23rd: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ What this means is that these particular images will be using this locked tarball for installing python modules from the wheels (ie. The PIP_PACKAGES list)... which means that an image like stx-platformclients, which is getting various starlingx clients from wheels, will only ever have content from that June 23rd build. Was this the intended behavior? Instead of this "alternate wheels tarball", shouldn't we be generating a wheels tarball with both py2 and py3 support, as long as we're building any py2 images? Thanks, Don.
7 7
0 0
[Starlingx-discuss] Questions on StarlingX upgrades
by Pratik M. 23 Mar '21

23 Mar '21
Hi, Looking at the URL below, I had a few questions to understand the overall upgrade strategy. https://docs.starlingx.io/specs/specs/stx-4.0/approved/starlingx-2007403-pl… Q1: Can I assume that from R4.0 onwards, the intent is that all future releases will support seamless upgrades for both minor and major versions. Q2: Is downgrade an explicit non-goal? Q3: Any hooks for non-stx applications to backup and restore their state? Q4: For a simplex edge node, it involves a N+1 ISO (re)installation. Is a more seamless option on the roadmap Q5. For a simplex edge subcloud, possible to orchestrate this from the central cloud? Q6: Any non-goals for the seamless upgrade, like say CentOS upgrade?. Any pointers to additional info are very welcome. Thanks in advance Pratik
2 2
0 0
[Starlingx-discuss] STX supported/recommended hardware
by open infra 03 Mar '21

03 Mar '21
Hi, Is there a recommended hardware list or a list of tested (by community) hardware? Regards, Danishka
2 4
0 0
[Starlingx-discuss] starlingx: unable to delete images from local registry
by Venkata Ramana Veldanda 02 Mar '21

02 Mar '21
Hi, We are using STX4.0 We have been trying to delete the images from the registry and it doesn't appear to be deleting. The "registry-image-delete" returns success but couldn't figure what is going wrong. Are there corresponding logs where the delete progress can be checked? Also, is there a workaround to delete them? controller-0:/home/sysadmin# source /etc/platform/openrc [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# system registry-image-list --nowrap +----------------------------------------------------------------+ | Image Name | +----------------------------------------------------------------+ | docker.io/nfvpe/multus | | docker.io/starlingx/k8s-cni-sriov | | docker.io/starlingx/k8s-plugins-sriov-network-device | | docker.io/starlingx/n3000-opae | | gcr.io/kubernetes-helm/tiller | | k8s.gcr.io/coredns | | k8s.gcr.io/defaultbackend | | k8s.gcr.io/etcd | | k8s.gcr.io/kube-apiserver | | k8s.gcr.io/kube-controller-manager | | k8s.gcr.io/kube-proxy | | k8s.gcr.io/kube-scheduler | | k8s.gcr.io/pause | | quay.io/airshipit/armada | | quay.io/calico/cni | | quay.io/calico/kube-controllers | | quay.io/calico/node | | quay.io/calico/pod2daemon-flexvol | | quay.io/jetstack/cert-manager-acmesolver | | quay.io/jetstack/cert-manager-cainjector | | quay.io/jetstack/cert-manager-controller | | quay.io/jetstack/cert-manager-webhook | | quay.io/k8scsi/snapshot-controller | | quay.io/kubernetes-ingress-controller/nginx-ingress-controller | | quay.io/stackanetes/kubernetes-entrypoint | | vdu/du-l1 | | vdu/du-testmac | | vdu/dul1 | +----------------------------------------------------------------+ [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# system registry-image-delete vdu/du-testmac:v1 Image vdu/du-testmac:v1 deleted, please run garbage collect to free disk space. [root@controller-0 sysadmin(keystone_admin)]# system registry-image-delete vdu/du-l1:v1 Image vdu/du-l1:v1 deleted, please run garbage collect to free disk space. [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# [root@controller-0 sysadmin(keystone_admin)]# system registry-image-list --nowrap +----------------------------------------------------------------+ | Image Name | +----------------------------------------------------------------+ | docker.io/nfvpe/multus | | docker.io/starlingx/k8s-cni-sriov | | docker.io/starlingx/k8s-plugins-sriov-network-device | | docker.io/starlingx/n3000-opae | | gcr.io/kubernetes-helm/tiller | | k8s.gcr.io/coredns | | k8s.gcr.io/defaultbackend | | k8s.gcr.io/etcd | | k8s.gcr.io/kube-apiserver | | k8s.gcr.io/kube-controller-manager | | k8s.gcr.io/kube-proxy | | k8s.gcr.io/kube-scheduler | | k8s.gcr.io/pause | | quay.io/airshipit/armada | | quay.io/calico/cni | | quay.io/calico/kube-controllers | | quay.io/calico/node | | quay.io/calico/pod2daemon-flexvol | | quay.io/jetstack/cert-manager-acmesolver | | quay.io/jetstack/cert-manager-cainjector | | quay.io/jetstack/cert-manager-controller | | quay.io/jetstack/cert-manager-webhook | | quay.io/k8scsi/snapshot-controller | | quay.io/kubernetes-ingress-controller/nginx-ingress-controller | | quay.io/stackanetes/kubernetes-entrypoint | | vdu/du-l1 | | vdu/du-testmac | | vdu/dul1 | +----------------------------------------------------------------+ [root@controller-0 sysadmin(keystone_admin)]# system registry-image-delete vdu/dul1:v1 Image vdu/dul1:v1 deleted, please run garbage collect to free disk space. [root@controller-0 sysadmin(keystone_admin)]# system registry-garbage-collect Running docker registry garbage collect [root@controller-0 sysadmin(keystone_admin)]# system registry-image-list --nowrap +----------------------------------------------------------------+ | Image Name | +----------------------------------------------------------------+ | docker.io/nfvpe/multus | | docker.io/starlingx/k8s-cni-sriov | | docker.io/starlingx/k8s-plugins-sriov-network-device | | docker.io/starlingx/n3000-opae | | gcr.io/kubernetes-helm/tiller | | k8s.gcr.io/coredns | | k8s.gcr.io/defaultbackend | | k8s.gcr.io/etcd | | k8s.gcr.io/kube-apiserver | | k8s.gcr.io/kube-controller-manager | | k8s.gcr.io/kube-proxy | | k8s.gcr.io/kube-scheduler | | k8s.gcr.io/pause | | quay.io/airshipit/armada | | quay.io/calico/cni | | quay.io/calico/kube-controllers | | quay.io/calico/node | | quay.io/calico/pod2daemon-flexvol | | quay.io/jetstack/cert-manager-acmesolver | | quay.io/jetstack/cert-manager-cainjector | | quay.io/jetstack/cert-manager-controller | | quay.io/jetstack/cert-manager-webhook | | quay.io/k8scsi/snapshot-controller | | quay.io/kubernetes-ingress-controller/nginx-ingress-controller | | quay.io/stackanetes/kubernetes-entrypoint | | vdu/du-l1 | | vdu/du-testmac | | vdu/dul1 | +----------------------------------------------------------------+ [root@controller-0 sysadmin(keystone_admin)]# system registry-image-tags vdu/dul1 [root@controller-0 sysadmin(keystone_admin)]# system registry-image-tags vdu/du-testmac [root@controller-0 sysadmin(keystone_admin)]# system registry-image-tags vdu/du-l1 [root@controller-0 sysadmin(keystone_admin)]# system registry-image-list +----------------------------------------------------------------+ | Image Name | +----------------------------------------------------------------+ | docker.io/nfvpe/multus | | docker.io/starlingx/k8s-cni-sriov | | docker.io/starlingx/k8s-plugins-sriov-network-device | | docker.io/starlingx/n3000-opae | | gcr.io/kubernetes-helm/tiller | | k8s.gcr.io/coredns | | k8s.gcr.io/defaultbackend | | k8s.gcr.io/etcd | | k8s.gcr.io/kube-apiserver | | k8s.gcr.io/kube-controller-manager | | k8s.gcr.io/kube-proxy | | k8s.gcr.io/kube-scheduler | | k8s.gcr.io/pause | | quay.io/airshipit/armada | | quay.io/calico/cni | | quay.io/calico/kube-controllers | | quay.io/calico/node | | quay.io/calico/pod2daemon-flexvol | | quay.io/jetstack/cert-manager-acmesolver | | quay.io/jetstack/cert-manager-cainjector | | quay.io/jetstack/cert-manager-controller | | quay.io/jetstack/cert-manager-webhook | | quay.io/k8scsi/snapshot-controller | | quay.io/kubernetes-ingress-controller/nginx-ingress-controller | | quay.io/stackanetes/kubernetes-entrypoint | | vdu/du-l1 | | vdu/du-testmac | | vdu/dul1 | +----------------------------------------------------------------+ [root@controller-0 sysadmin(keystone_admin)]#
2 2
0 0
[Starlingx-discuss] Merging Multi-OS & Distro Meeting
by Saul Wold 01 Mar '21

01 Mar '21
Folks, I would like to try and reduce our meeting load by one and ideally at a more reasonable time. I would like to propose using the Wed @ 1430 UTC (0630 PT / 2230 China) when Canada/US "spring forward" on March 14th the China time will move to 2130. So there will be 1 late meeting and then shift. Please respond if are part of either of these teams and this time does not work. Another option would be the current Multi-OS time slot on Tuesday at 1530 UTC, but that would mean a 2330 China time shifting after the 14th to 2230. Ildiko, can you confirm that the Wed @ 1430 is available every other week opposite the Release Team meeting (so staring March 4th). Thanks -- Sau!
1 1
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210226T024233Z
by Dimofte, Alexandru 27 Feb '21

27 Feb '21
Sanity Test from 2021-February-26 (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
0 0
[Starlingx-discuss] [build-report] master STX_build_layer_flock_master_master - Build # 404 - Failure!
by build.starlingx@gmail.com 26 Feb '21

26 Feb '21
Project: STX_build_layer_flock_master_master Build #: 404 Status: Failure Timestamp: 20210225T215643Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: true
2 1
0 0
[Starlingx-discuss] [StarlingX 4.0] - Installing StarlingX using External Registry
by Anirudh Gupta 26 Feb '21

26 Feb '21
Hi Team, We need to Install StarlingX Release 4.0 on our Lab machines in which there is no internet connectivity. According to the storyboard link below, https://storyboard.openstack.org/#!/story/2004711 There is a way in which we can clone all the required StarlingX Repos on a Staging Server and use that Server to install StarlingX on our Machines. However, I am unable to find any supporting document for the same. Can someone please help with the following items: - Steps to Setup Local Registry Server - Changes need to be done in /usr/share/ansible/stx-ansible/playbooks/host_vars/bootstrap/default.yml file for the same Regards Anirudh Gupta
1 0
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20210225T023335Z
by Dimofte, Alexandru 26 Feb '21

26 Feb '21
Sanity Test from 2021-February-25 (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
0 0
[Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 1280 - Failure!
by build.starlingx@gmail.com 26 Feb '21

26 Feb '21
Project: STX_build_pre_installer_layered Build #: 1280 Status: Failure Timestamp: 20210225T221255Z Branch: Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-flock/20210225T215643Z DOCKER_BUILD_ID: jenkins-master-flock-20210225T215643Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-flock/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20210… BUILD_IMG: true FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/flock/20210225T215643Z/logs MASTER_JOB_NAME: STX_build_layer_flock_master_master LAYER: flock MY_REPO_ROOT: /localdisk/designer/jenkins/master-flock BUILD_ISO: true
1 0
0 0
  • ← Newer
  • 1
  • 2
  • 3
  • 4
  • ...
  • 11
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.