September 2019 - Starlingx-discuss

[Starlingx-discuss] Special Sanity Request
by Scott Little 07 Sep '19

07 Sep '19

Ada, Please run a sanity test against the following build: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T04… This is the first post-restructure build to include docker images. Thank You Scott Little

2 4

Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 16, Issue 27
by wang.changjin＠zte.com.cn 06 Sep '19

06 Sep '19

StarlingX 2.0(19.08) ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml TASK [bringup-essential-services : Fail if adding interface addresses failed for reason other than it has been done before] *** failed: [localhost] (item={'_ansible_parsed': True, 'stderr_lines': [u'[Errno 101] Network is unreachable'], u'changed': True, u'stdout': u'', '_ansible_item_result': True, u'msg': u'non-zero return code', u'delta': u'0:00:02.530397', 'stdout_lines': [], 'failed_when_result': False, '_ansible_item_label': u'source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500', u'end': u'2019-09-07 13:11:10.228016', '_ansible_no_log': False, 'item': u'source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500', u'cmd': u'source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500', u'failed': False, u'stderr': u'[Errno 101] Network is unreachable', u'rc': 1, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u'source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin': None}}, u'start': u'2019-09-07 13:11:07.697619', '_ansible_ignore_errors': None}) => {"changed": false, "item": {"changed": true, "cmd": "source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500", "delta": "0:00:02.530397", "end": "2019-09-07 13:11:10.228016", "failed": false, "failed_when_result": false, "invocation": {"module_args": {"_raw_params": "source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500", "_uses_shell": true, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "warn": true}}, "item": "source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500", "msg": "non-zero return code", "rc": 1, "start": "2019-09-07 13:11:07.697619", "stderr": "[Errno 101] Network is unreachable", "stderr_lines": ["[Errno 101] Network is unreachable"], "stdout": "", "stdout_lines": []}, "msg": "source /etc/platform/openrc; system host-if-add controller-0 lo virtual none lo -c platform -m 1500 failed for reason: [Errno 101] Network is unreachable."} failed: [localhost] (item={'_ansible_parsed': True, 'stderr_lines': [u'[Errno 101] Network is unreachable'], u'changed': True, u'stdout': u'', '_ansible_item_result': True, u'msg': u'non-zero return code', u'delta': u'0:00:02.140193', 'stdout_lines': [], 'failed_when_result': False, '_ansible_item_label': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt', u'end': u'2019-09-07 13:11:12.589717', '_ansible_no_log': False, 'item': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt', u'cmd': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt', u'failed': False, u'stderr': u'[Errno 101] Network is unreachable', u'rc': 1, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin': None}}, u'start': u'2019-09-07 13:11:10.449524', '_ansible_ignore_errors': None}) => {"changed": false, "item": {"changed": true, "cmd": "source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt", "delta": "0:00:02.140193", "end": "2019-09-07 13:11:12.589717", "failed": false, "failed_when_result": false, "invocation": {"module_args": {"_raw_params": "source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt", "_uses_shell": true, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "warn": true}}, "item": "source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt", "msg": "non-zero return code", "rc": 1, "start": "2019-09-07 13:11:10.449524", "stderr": "[Errno 101] Network is unreachable", "stderr_lines": ["[Errno 101] Network is unreachable"], "stdout": "", "stdout_lines": []}, "msg": "source /etc/platform/openrc; system interface-network-assign controller-0 lo mgmt failed for reason: [Errno 101] Network is unreachable."} failed: [localhost] (item={'_ansible_parsed': True, 'stderr_lines': [u'[Errno 101] Network is unreachable'], u'changed': True, u'stdout': u'', '_ansible_item_result': True, u'msg': u'non-zero return code', u'delta': u'0:00:02.236828', 'stdout_lines': [], 'failed_when_result': False, '_ansible_item_label': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host', u'end': u'2019-09-07 13:11:15.026358', '_ansible_no_log': False, 'item': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host', u'cmd': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host', u'failed': False, u'stderr': u'[Errno 101] Network is unreachable', u'rc': 1, u'invocation': {u'module_args': {u'warn': True, u'executable': None, u'_uses_shell': True, u'_raw_params': u'source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host', u'removes': None, u'argv': None, u'creates': None, u'chdir': None, u'stdin': None}}, u'start': u'2019-09-07 13:11:12.789530', '_ansible_ignore_errors': None}) => {"changed": false, "item": {"changed": true, "cmd": "source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host", "delta": "0:00:02.236828", "end": "2019-09-07 13:11:15.026358", "failed": false, "failed_when_result": false, "invocation": {"module_args": {"_raw_params": "source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host", "_uses_shell": true, "argv": null, "chdir": null, "creates": null, "executable": null, "removes": null, "stdin": null, "warn": true}}, "item": "source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host", "msg": "non-zero return code", "rc": 1, "start": "2019-09-07 13:11:12.789530", "stderr": "[Errno 101] Network is unreachable", "stderr_lines": ["[Errno 101] Network is unreachable"], "stdout": "", "stdout_lines": []}, "msg": "source /etc/platform/openrc; system interface-network-assign controller-0 lo cluster-host failed for reason: [Errno 101] Network is unreachable."} PLAY RECAP ********************************************************************* localhost : ok=138 changed=55 unreachable=0 failed=1 王长金 Wang ChangJin 电信云及核心网产品团队/无线产品经营部 CCN Product Team/Wireless Product Operation 南京市雨花台区花神大道6号 ZTE Corporation, 6# Huashen Rd, Yuhuatai District, Nanjing, P.R.China, 210012 T: +86 25 52877110 F:+86 25 52870000 M: +86 15850586900 E: wang.changjin(a)zte.com.cn www.zte.com.cn 原始邮件发件人：starlingx-discuss-request(a)lists.starlingx.io <starlingx-discuss-request(a)lists.starlingx.io> 收件人：starlingx-discuss(a)lists.starlingx.io <starlingx-discuss(a)lists.starlingx.io>; 日期：2019年09月07日 05:23 主题：Starlingx-discuss Digest, Vol 16, Issue 27 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_images - Build # 126 - Failure! (build.starlingx(a)gmail.com) 2. [build-report] STX_build_master_master - Build # 239 - Failure! (build.starlingx(a)gmail.com) 3. Re: [stable] [build-report] STX_build_docker_base_image - Build # 132 - Failure! (Scott Little) 4. StarlingX Weekly Containerization Meeting (Miller, Frank) ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Sep 2019 13:14:07 -0400 (EDT) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 126 - Failure! Message-ID: <1992448495.206.1567790048625.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_docker_images Build #: 126 Status: Failure Timestamp: 20190906T170437Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190906T143354Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… MASTER_BUILD_NUMBER: 239 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20190906T143354Z DOCKER_BUILD_ID: jenkins-master-20190906T143354Z-builder TIMESTAMP: 20190906T143354Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/outputs ------------------------------ Message: 2 Date: Fri, 6 Sep 2019 13:14:10 -0400 (EDT) From: build.starlingx(a)gmail.com To: starlingx-discuss(a)lists.starlingx.io Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 239 - Failure! Message-ID: <1455192693.209.1567790051685.JavaMail.javamailuser@localhost> Content-Type: text/plain; charset="utf-8" Project: STX_build_master_master Build #: 239 Status: Failure Timestamp: 20190906T143354Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true ------------------------------ Message: 3 Date: Fri, 6 Sep 2019 16:46:07 -0400 From: Scott Little <scott.little(a)windriver.com> To: <starlingx-discuss(a)lists.starlingx.io> Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 132 - Failure! Message-ID: <f4a3bca8-e44a-6e9c-a407-797a04f81e36(a)windriver.com> Content-Type: text/plain; charset="windows-1252"; Format="flowed" CENGN timed out on pushing an image to dockerhub. Whatever the issue, it's back to normal now. Restarting the job... Scott On 2019-09-06 1:14 p.m., build.starlingx(a)gmail.com wrote: > Project: STX_build_docker_base_image > Build #: 132 > Status: Failure > Timestamp: 20190906T170437Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190906T143354Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/master/cgcs-root > BASE_VERSION: master-stable-20190906T143354Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… > REGISTRY_USERID: slittlewrs > HOST: build.starlingx.cengn.ca > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/logs > OS_VERSION: 7.5.1804 > BUILD_STREAM: stable > REGISTRY_ORG: starlingx > BASE_LATEST_TAG: master-stable-latest > PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/inputs > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/outputs > REGISTRY: docker.io > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss(a)lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190906/…> ------------------------------ Message: 4 Date: Fri, 6 Sep 2019 21:22:40 +0000 From: "Miller, Frank" <Frank.Miller(a)windriver.com> To: "starlingx-discuss(a)lists.starlingx.io" <starlingx-discuss(a)lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX Weekly Containerization Meeting Message-ID: <A43F4E51FB41274EA099B52A6EE25DC19DCE1395(a)ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="iso-8859-1" Folks: I'd appreciate your attendance to update us on the following. If you cannot attend please send a brief email update before the meeting. Thank-you. Agenda for September 9 meeting: 1. stx gating bugs (28, 4 High, 24 Medium) : https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.containers a) Updates on High Priority bugs - what is plan to closure?: o 1817936 Periodic message loss seen between VIM and OpenStack REST APIs [Austin Sun] o 1827246 Access to VM console not working as Horizon redirects to novncproxy.openstack.svc.cluster.local [Zhipeng Liu] o 1836609 application apply fails after compute lock and unlock [Stefan Dinescu] o 1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] b) Updates on older Medium priority bugs - what is the plan to address or close as invalid/not reproducible./etc? o 1817936 Periodic message loss seen between VIM and OpenStack REST APIs [Austin Sun] o 1817958 Containers: Worker nodes are pulling from external registry instead from the internal registry [Erich Cordoba] o 1819021 manifest.yaml with test "enabled: true" fails to apply [An Ran] o 1819688 Image conversion fails with large qcow2 guest image due to insufficient filesystem size [Kristine Bujold] o 1823375 After force reboot of active controller keystone-api pod sometimes hangs [Yong Hu] o 1824881 Unlock after force lock enabled the worker according to maintenance but hypervisor remained down [Erich Cordoba] o 1825056 AIO-SX: overrides for vcpu_pin_set not updated after Platform cpu assignment update and unlock [Jim Gauld] o 1829931 AIO-DX: hypervisor is not up in 5 mins after unlocked standby controller becomes available [Bart Wensley] 2. Stx.3.0 features: a) Status update and forecast for code completion date for the following: o 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] o 2004008: [Feature] Create HELM chart for Fault project [Mario Arevalo/An Ran] o 2005860: Upversion container components [Al Bailey] o [NEW]: Collect tool enhancements for containers [Dan Voiculeasa] b) The following SBs can be accepted: o 2006274: Support authenticated registry for bootstrap and application apply https://storyboard.openstack.org/#!/story/2006274<https://storyboard.openstack.org/> o 2006295: Support Single huge page size for openstack worker node https://storyboard.openstack.org/#!/story/2006295<https://storyboard.openstack.org/> 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 11am EST / 8am PDT / 1600 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190906/…> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4875 bytes Desc: not available URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190906/…> ------------------------------ 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 16, Issue 27 *************************************************

2 3

[Starlingx-discuss] StarlingX Weekly Containerization Meeting
by Miller, Frank 06 Sep '19

06 Sep '19

Folks: I'd appreciate your attendance to update us on the following. If you cannot attend please send a brief email update before the meeting. Thank-you. Agenda for September 9 meeting: 1. stx gating bugs (28, 4 High, 24 Medium) : https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.containers a) Updates on High Priority bugs - what is plan to closure?: o 1817936 Periodic message loss seen between VIM and OpenStack REST APIs [Austin Sun] o 1827246 Access to VM console not working as Horizon redirects to novncproxy.openstack.svc.cluster.local [Zhipeng Liu] o 1836609 application apply fails after compute lock and unlock [Stefan Dinescu] o 1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] b) Updates on older Medium priority bugs - what is the plan to address or close as invalid/not reproducible./etc? o 1817936 Periodic message loss seen between VIM and OpenStack REST APIs [Austin Sun] o 1817958 Containers: Worker nodes are pulling from external registry instead from the internal registry [Erich Cordoba] o 1819021 manifest.yaml with test "enabled: true" fails to apply [An Ran] o 1819688 Image conversion fails with large qcow2 guest image due to insufficient filesystem size [Kristine Bujold] o 1823375 After force reboot of active controller keystone-api pod sometimes hangs [Yong Hu] o 1824881 Unlock after force lock enabled the worker according to maintenance but hypervisor remained down [Erich Cordoba] o 1825056 AIO-SX: overrides for vcpu_pin_set not updated after Platform cpu assignment update and unlock [Jim Gauld] o 1829931 AIO-DX: hypervisor is not up in 5 mins after unlocked standby controller becomes available [Bart Wensley] 2. Stx.3.0 features: a) Status update and forecast for code completion date for the following: o 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] o 2004008: [Feature] Create HELM chart for Fault project [Mario Arevalo/An Ran] o 2005860: Upversion container components [Al Bailey] o [NEW]: Collect tool enhancements for containers [Dan Voiculeasa] b) The following SBs can be accepted: o 2006274: Support authenticated registry for bootstrap and application apply https://storyboard.openstack.org/#!/story/2006274<https://storyboard.openstack.org/> o 2006295: Support Single huge page size for openstack worker node https://storyboard.openstack.org/#!/story/2006295<https://storyboard.openstack.org/> 3. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 11am EST / 8am PDT / 1600 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers

1 0

[Starlingx-discuss] [stable] [build-report] STX_build_docker_base_image - Build # 132 - Failure!
by build.starlingx＠gmail.com 06 Sep '19

06 Sep '19

Project: STX_build_docker_base_image Build #: 132 Status: Failure Timestamp: 20190906T170437Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190906T143354Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20190906T143354Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable REGISTRY_ORG: starlingx BASE_LATEST_TAG: master-stable-latest PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/outputs REGISTRY: docker.io

2 1

[Starlingx-discuss] [build-report] STX_build_master_master - Build # 239 - Failure!
by build.starlingx＠gmail.com 06 Sep '19

06 Sep '19

Project: STX_build_master_master Build #: 239 Status: Failure Timestamp: 20190906T143354Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true

1 0

[Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 126 - Failure!
by build.starlingx＠gmail.com 06 Sep '19

06 Sep '19

Project: STX_build_docker_images Build #: 126 Status: Failure Timestamp: 20190906T170437Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190906T143354Z OS: centos MUNGED_BRANCH: master MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190906T14… MASTER_BUILD_NUMBER: 239 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/logs MASTER_JOB_NAME: STX_build_master_master MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20190906T143354Z DOCKER_BUILD_ID: jenkins-master-20190906T143354Z-builder TIMESTAMP: 20190906T143354Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190906T143354Z/outputs

1 0

[Starlingx-discuss] [starlingx-discuss] How to access openstack services api with OAM IP
by 张鲲鹏 06 Sep '19

06 Sep '19

Hi all, How to access openstack services api with OAM IP in stx2.0? Example: My oam floating ip is 172.16.180.154 I want to access the nova api via 172.16.180.154, what should I do? Thanks Kunpeng

2 1

[Starlingx-discuss] [DOCS] 'Extended Security Profile' removed from installer menu
by Bujold, Kristine 05 Sep '19

05 Sep '19

The install menus were recently changed. See https://bugs.launchpad.net/starlingx/+bug/1839134. Menus for installing from ISO are now; For BIOS First menu: Standard Controller Configuration or All-in-one Controller Configuration or All-in-one (lowlatency) Controller Configuration Second menu: Serial Console or Graphical Console For UEFI First menu: UEFI Standard Controller Configuration or UEFI All-in-one Controller Configuration or UEFI All-in-one (lowlatency) Controller Configuration Second menu: Serial Console or Graphical Console Thanks, Kristine

3 2

[Starlingx-discuss] Meet issue with 2.0 installation guide for baremetal
by Li, Cheng1 05 Sep '19

05 Sep '19

Hi, I am installation the starlingx AIO-duplex on baremetals by following the 2.0 guide[1] and with the ISO build on Sep 2[2]. I notice the following lines in the guide as well as in the AIO-simplex guide. My understanding is that we should select "All-in-one Controller Configuration" instead of "Standard Controller Configuration" for AIO-simple and AIO-duplex deployment. So is this a mistake of the guide? Thanks Make the following menu selections in the installer: 1. First menu: Select 'Standard Controller Configuration' 2. Second menu: Select 'Graphical Console' or 'Textual Console' depending on your terminal access to the console port 3. Third menu: Select 'Standard Security Profile' [1] https://docs.starlingx.io/deploy_install_guides/current/bare_metal_aio_dupl… [2] http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190902T23… Thanks, Cheng

2 2

[Starlingx-discuss] Minutes: StarlingX Release Meeting - Sept 5/2019
by Khalil, Ghada 05 Sep '19

05 Sep '19

Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - September 5 2019 stx.3.0 - Release Plan: https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_Fa… - StoryBoard Dashboard: https://storyboard.openstack.org/#!/board/186 - Went through the spreadsheet and updated feature risk and dates, building on the discussion in the community call. - Action: Feature primes, please review the Release Plan and update as soon as possible. - Agreed to move MS-2 to next week for the following items: - Allow PLs to get more of their feature data in - Allow Ada and test team to come up with feature test plan dates and high-level release test plan - Documentation plan is in place stx.2.0 - Release Notes - Location: https://docs.starlingx.io/releasenotes/r2_release.html - Agreed to add a table of features w/ storyboard references ...similar to what was done for stx.1.0 - Other suggestions are to include a link to the fixed bugs and the open bugs gating the release - Action: Ghada & Bill to work on that - Suggestion from Ildiko: - Moving forward, make this part of the feature development process instead of leaving it to the end of the release. - Agreed to put on the agenda for the community call next week to bring awareness to this. Action: Bill - Maintenance Release - Current Target: the week of Sept 30 (soft target) - stx.2.0 branch: https://review.opendev.org/#/q/projects:+starlingx+branch:r/stx.2.0 - stx.2.0 gating bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2.0 - Current count: 13 - As of Sept 5, only one additional commit merged to the stx.2.0 branch so far. Agreed that it's not worth building a load yet. - Ghada is reluctant to send a reminder to the mailing list for cherry-picks when the master branch is closed for repo restructuring - As per Saul, we hope to have master back open on Monday Sept 9

1 0