From ezpeerchen at gmail.com Fri Nov 1 02:09:48 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 10:09:48 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> Message-ID: Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Fri Nov 1 02:28:19 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 10:28:19 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> , Message-ID: Hi, Ezpeer I just followed "Install StarlingX Kubernetes on Virtual AIO-SX" (https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html). Below pasted from the guide, 1). the read one, "physnet0" and "physnet1", should I replace it using real interfaces in host? 2). do you have any material about "system datanetwork" -------------------------- DATA0IF=eth1000 DATA1IF=eth1001 export COMPUTE=controller-0 PHYSNET0='physnet0' PHYSNET1='physnet1' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list system host-port-list ${COMPUTE} --nowrap > ${SPL} system host-if-list -a ${COMPUTE} --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 datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system host-if-modify -m 1500 -n data1 -c data ${COMPUTE} ${DATA1IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} ${PHYSNET0} system interface-datanetwork-assign ${COMPUTE} ${DATA1IFUUID} ${PHYSNET1} -------------------------- ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss valid_lft forever preferred_lft forever 163: cali4b88ce Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Fri Nov 1 02:39:55 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 10:39:55 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> Message-ID: Dear QianJiang, Please reference the document https://wiki.openstack.org/wiki/StarlingX/Networking . The document has an example about configuring the flat network. - Configure the flat network. Thanks. BR 钱江 於 2019年11月1日 週五 上午10:28寫道: > Hi, Ezpeer > > I just followed "Install StarlingX Kubernetes on Virtual AIO-SX" ( > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html > ). > Below pasted from the guide, > 1). the read one, "physnet0" and "physnet1", should I replace it > using real interfaces in host? > 2). do you have any material about "system datanetwork" > > -------------------------- > DATA0IF=eth1000 > DATA1IF=eth1001 > export COMPUTE=controller-0 > PHYSNET0='physnet0' > PHYSNET1='physnet1' > SPL=/tmp/tmp-system-port-list > SPIL=/tmp/tmp-system-host-if-list > system host-port-list ${COMPUTE} --nowrap > ${SPL} > system host-if-list -a ${COMPUTE} --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 datanetwork-add ${PHYSNET0} vlan > system datanetwork-add ${PHYSNET1} vlan > > system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} > system host-if-modify -m 1500 -n data1 -c data ${COMPUTE} ${DATA1IFUUID} > system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} ${PHYSNET0} > system interface-datanetwork-assign ${COMPUTE} ${DATA1IFUUID} ${PHYSNET1} > -------------------------- > > > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > valid_lft forever preferred_lft forever > 163: cali4b88ce > Install StarlingX Kubernetes on Virtual AIO-SX > Install StarlingX Kubernetes on Virtual AIO-SX > Install StarlingX Kubernetes on Virtual AIO-SX > Install StarlingX Kubernetes on Virtual AIO-SX > -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Fri Nov 1 04:31:32 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 12:31:32 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> , Message-ID: <03480413-8d50-48ed-b661-c5e9f15b02bb.qianjiang@baicells.com> Hi, Ezpeer Thanks very much, however I am very confused with some starlingx network concepts. From the system command, we see, systen network list system interface-network list system datanetwork list system interface-datanetwork list Could you tell me concepts of these network/datanetwork/interface-network? Or any available materials about the system networks? ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:40 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Please reference the document https://wiki.openstack.org/wiki/StarlingX/Networking . The document has an example about configuring the flat network. Configure the flat network. Thanks. BR 钱江 於 2019年11月1日 週五 上午10:28寫道: Hi, Ezpeer I just followed "Install StarlingX Kubernetes on Virtual AIO-SX" (https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html). Below pasted from the guide, 1). the read one, "physnet0" and "physnet1", should I replace it using real interfaces in host? 2). do you have any material about "system datanetwork" -------------------------- DATA0IF=eth1000 DATA1IF=eth1001 export COMPUTE=controller-0 PHYSNET0='physnet0' PHYSNET1='physnet1' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list system host-port-list ${COMPUTE} --nowrap > ${SPL} system host-if-list -a ${COMPUTE} --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 datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system host-if-modify -m 1500 -n data1 -c data ${COMPUTE} ${DATA1IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} ${PHYSNET0} system interface-datanetwork-assign ${COMPUTE} ${DATA1IFUUID} ${PHYSNET1} -------------------------- ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss valid_lft forever preferred_lft forever 163: cali4b88ce Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Fri Nov 1 06:02:22 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 1 Nov 2019 06:02:22 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> Hi all, After using new image file (cirros-0.4.0-x86_64-disk.img), we can launch instance on standard external Storage (2+2+2) now. It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by Cristopher Lemus causes qemu-img detecting wrong format after format convert from qcow2to raw in Nova code. We are not sure how/where we got this image file. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 17:31 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, For remote storage configuration, we have overridden below configurations in helm/nova.py. if remote_storage: default_config.update({'force_raw_images': True}) libvirt_config.update({'images_type': 'rbd', 'images_rbd_pool': rbd_pool, 'images_rbd_ceph_conf': rbd_ceph_conf}) else: libvirt_config.update({'images_type': 'default'}) Next step: The only issue we need to figure out is why image format is still qcow2 after image format convert by qemu-img in nova code. I tried to reproduce it in my virtualized multi-node environment, but no issue found, VM created normally. (I copied yellow code block to else branch) In /var/lib/nova/instances/_base/ folder, I can see one qcow2 image and one raw image which should be converted by nova. [root at compute-1 _base]# ls 3cb926303b665709318d2c099722b914025023b4 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee [root at compute-1 _base]# qemu-img info 3cb926303b665709318d2c099722b914025023b4 image: 3cb926303b665709318d2c099722b914025023b4 file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false [root at compute-1 _base]# qemu-img info 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Any comment? Thanks! zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 10:15 To: Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Fri Nov 1 06:34:56 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 14:34:56 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> , Message-ID: <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> Hi, Ezpeer Below is the log of "system interface-datanetwork-list controller-0", any problem? [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | physnet0 | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Fri Nov 1 06:46:12 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 14:46:12 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> Message-ID: Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Your enp2s1 interface is not assigned to any data network? Thanks. BR 钱江 於 2019年11月1日 週五 下午2:35寫道: > Hi, Ezpeer > > Below is the log of "system interface-datanetwork-list controller-0", > any problem? > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | > physnet0 | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Fri Nov 1 07:17:01 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 15:17:01 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com>, Message-ID: <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> You see, "eth1000" and "eth1001" are assigned to datanetwork. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 14:46 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Your enp2s1 interface is not assigned to any data network? Thanks. BR 钱江 於 2019年11月1日 週五 下午2:35寫道: Hi, Ezpeer Below is the log of "system interface-datanetwork-list controller-0", any problem? [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | physnet0 | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Fri Nov 1 07:22:58 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 15:22:58 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> Message-ID: Your data0 and data1 are vlan type datanetwork. This is your configuration. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan 钱江 於 2019年11月1日 週五 下午3:17寫道: > You see, "eth1000" and "eth1001" are assigned to datanetwork. > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 14:46 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > Your enp2s1 interface is not assigned to any data network? > > > > Thanks. > > BR > > 钱江 於 2019年11月1日 週五 下午2:35寫道: > Hi, Ezpeer > > Below is the log of "system interface-datanetwork-list controller-0", > any problem? > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | > physnet0 | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Fri Nov 1 07:36:36 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 15:36:36 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com>, Message-ID: <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> But, still failure use type vlan controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 15:27 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Your data0 and data1 are vlan type datanetwork. This is your configuration. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan 钱江 於 2019年11月1日 週五 下午3:17寫道: You see, "eth1000" and "eth1001" are assigned to datanetwork. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 14:46 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Your enp2s1 interface is not assigned to any data network? Thanks. BR 钱江 於 2019年11月1日 週五 下午2:35寫道: Hi, Ezpeer Below is the log of "system interface-datanetwork-list controller-0", any problem? [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | physnet0 | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Fri Nov 1 07:50:33 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 15:50:33 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> Message-ID: Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking - Configure the flat network. 钱江 於 2019年11月1日 週五 下午3:36寫道: > But, still failure use type vlan > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 15:27 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Your data0 and data1 are vlan type datanetwork. > > > This is your configuration. > > system datanetwork-add ${PHYSNET0} vlan > system datanetwork-add ${PHYSNET1} vlan > > > 钱江 於 2019年11月1日 週五 下午3:17寫道: > You see, "eth1000" and "eth1001" are assigned to datanetwork. > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 14:46 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > Your enp2s1 interface is not assigned to any data network? > > > > Thanks. > > BR > > 钱江 於 2019年11月1日 週五 下午2:35寫道: > Hi, Ezpeer > > Below is the log of "system interface-datanetwork-list controller-0", > any problem? > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | > physnet0 | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Fri Nov 1 08:26:51 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Fri, 1 Nov 2019 16:26:51 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> Message-ID: controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. * --provider-physical-network provider * = > incorrect You don't have the physical network named as "provider". Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: > Please follow the document's example. > https://wiki.openstack.org/wiki/StarlingX/Networking > > > - Configure the flat network. > > > 钱江 於 2019年11月1日 週五 下午3:36寫道: > >> But, still failure use type vlan >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type vlan provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'provider' unknown for VLAN provider >> network. >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 15:27 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Your data0 and data1 are vlan type datanetwork. >> >> >> This is your configuration. >> >> system datanetwork-add ${PHYSNET0} vlan >> system datanetwork-add ${PHYSNET1} vlan >> >> >> 钱江 於 2019年11月1日 週五 下午3:17寫道: >> You see, "eth1000" and "eth1001" are assigned to datanetwork. >> [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list >> controller-0 >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | uuid | name | class | type | >> vlan id | ports | uses i/f | used by i/f | attributes >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | >> None | [] | [] | [] | MTU=1500 >> | >> | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | >> None | [u'enp2s1'] | [] | [] | MTU=1500 >> | >> | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | >> None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True >> | >> | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | >> None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 14:46 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Do you do the interface-datanetwork-assign ? >> >> #system interface-datanetwork-assign controller-0 >> >> >> >> Reference Doc: >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> >> Your enp2s1 interface is not assigned to any data network? >> >> >> >> Thanks. >> >> BR >> >> 钱江 於 2019年11月1日 週五 下午2:35寫道: >> Hi, Ezpeer >> >> Below is the log of "system interface-datanetwork-list controller-0", >> any problem? >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+--------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+--------+------------------+ >> | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | >> physnet0 | >> | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | >> physnet1 | >> >> +--------------+--------------------------------------+--------+------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list >> controller-0 >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | uuid | name | class | type | >> vlan id | ports | uses i/f | used by i/f | attributes >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | >> None | [] | [] | [] | MTU=1500 >> | >> | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | >> None | [u'enp2s1'] | [] | [] | MTU=1500 >> | >> | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | >> None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True >> | >> | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | >> None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 10:10 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Dear QianJiang, >> >> Your command is incorrect. >> >> Example: >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+-----------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+-----------+------------------+ >> | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | >> physnet-pci | >> | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | >> phy-flat | >> | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | >> physnet-sriov | >> >> +--------------+--------------------------------------+-----------+------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ >> >> >> >> 钱江 於 2019年10月31日 週四 下午7:23寫道: >> Hi, Ezpeer >> >> I checked and yes, >> [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list >> controller-0 >> >> +--------------+--------------------------------------+--------+--------------+ >> | hostname | uuid | ifname | >> network_name | >> >> +--------------+--------------------------------------+--------+--------------+ >> | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | >> oam | >> | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | >> mgmt | >> | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | >> cluster-host | >> >> +--------------+--------------------------------------+--------+--------------+ >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年10月31日(星期四) 18:12 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Dear , >> >> Do you do the interface-datanetwork-assign ? >> >> #system interface-datanetwork-assign controller-0 >> >> >> >> Reference Doc: >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> >> >> Thanks. >> >> BR >> >> 钱江 於 2019年10月31日 週四 下午5:28寫道: >> Hi, Austin >> >> I checked, the type_drivers field has no problem. Do you have more >> ideas? >> >> controller-0:~$ grep type_drivers -r >> /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml >> >> type_drivers: flat,vlan,vxlan >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Sun, Austin >> 发送时间:2019年10月31日(星期四) 16:42 >> 收件人:钱江 ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> Could you double check ? >> >> grep -r type_drivers >> /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml >> ? >> >> >> >> it comes out like ‘type_drivers: flat,vlan,vxlan’, >> >> if not , you have to use helm command to override to include flat >> network. >> >> >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> >> *From:* 钱江 >> *Sent:* Thursday, October 31, 2019 4:12 PM >> *To:* Sun, Austin ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: >> Flat provider networks are disabled >> >> >> >> Hi, Austin >> >> >> >> Thanks for your warmhearted. >> >> Follow your suggestion, but I still get the same issue. >> >> >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 >> flat >> +--------------+--------------------------------------+ >> | Property | Value | >> +--------------+--------------------------------------+ >> | id | 3 | >> | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | >> | name | enp2s1 | >> | network_type | flat | >> | mtu | 1500 | >> | description | None | >> +--------------+--------------------------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list >> +--------------------------------------+----------+--------------+------+ >> | uuid | name | network_type | mtu | >> +--------------------------------------+----------+--------------+------+ >> | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | >> | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | >> | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | >> +--------------------------------------+----------+--------------+------+ >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type flat provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: Flat provider networks are disabled. >> >> >> >> When I tried type vlan as following, it directed different issue. >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type vlan provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'provider' unknown for VLAN provider >> network. >> >> >> >> ------------------------------------------------------------------ >> >> 发件人:Sun, Austin >> >> 发送时间:2019年10月31日(星期四) 15:23 >> >> 收件人:钱江 ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> >> 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> Hi QianJiang: >> >> The default datanetwork in guide is vlan, you should change it to flat >> before openstack network create. >> >> >> >> system datanetwork-add ${PHYSNET0} flat >> >> >> >> Thanks. >> >> BR >> Austin Sun. >> >> From:钱江 >> *Sent:* Thursday, October 31, 2019 2:42 PM >> *To:* starlingx-discuss >> *Subject:* [Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> >> >> Hi, the community >> >> >> >> After installation of "Virtual All-in-one Simplex Installation R2.0 >> ", >> everything goes well except, >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type flat provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: Flat provider networks are disabled. >> >> >> >> Could anyone help to point out what's the issue, and how to fix it? >> >> >> >> Best Regard >> >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Nov 1 08:51:31 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 01 Nov 2019 02:51:31 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191101T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From qianjiang at baicells.com Fri Nov 1 09:31:20 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Fri, 01 Nov 2019 17:31:20 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> , Message-ID: <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> Hi, Ezpeer Just follow https://wiki.openstack.org/wiki/StarlingX/Networking --- Configure the flat network. controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print $2}'` controller-0:~$ echo $ADMINID 95794c0fbfe9427b908eedb823aba318 controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'phy-flat' unknown for flat provider network. controller-0:~$ and, [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 5c8391a3-be90-48dd-8df5-2c1118af979a | phy-flat | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ Please Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 16:31 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. --provider-physical-network provider = > incorrect You don't have the physical network named as "provider". Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking Configure the flat network. 钱江 於 2019年11月1日 週五 下午3:36寫道: But, still failure use type vlan controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 15:27 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Your data0 and data1 are vlan type datanetwork. This is your configuration. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan 钱江 於 2019年11月1日 週五 下午3:17寫道: You see, "eth1000" and "eth1001" are assigned to datanetwork. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 14:46 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Your enp2s1 interface is not assigned to any data network? Thanks. BR 钱江 於 2019年11月1日 週五 下午2:35寫道: Hi, Ezpeer Below is the log of "system interface-datanetwork-list controller-0", any problem? [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | physnet0 | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Venkata.Veldanda at windriver.com Fri Nov 1 09:34:18 2019 From: Venkata.Veldanda at windriver.com (Veldanda, Venkata) Date: Fri, 1 Nov 2019 09:34:18 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: <03480413-8d50-48ed-b661-c5e9f15b02bb.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> , <03480413-8d50-48ed-b661-c5e9f15b02bb.qianjiang@baicells.com> Message-ID: <1BF3FAD82348ED47AF7A9CDFCAB4C6E553594C99@ALA-MBD.corp.ad.wrs.com> Hi Qian, >> systen network list List of all the IP networks across your system. Like your host or pod networks. Basically each network here defines a network type that you would assign to interfaces below. For e.g. you can leverage this to separate networks etc. >> system interface-network list List of interfaces (logical interface names) like OAM/MGMT/CLUSTER on a specifc host. Each interface will be using a specifc network name (from your system network-list). To understand to what physical interface it is mapped on the host you can use with system host-if-list >> system datanetwork list List of datanetworks available on the system. Basically a data network type either you want to assign it as flat or vlan etc. >> system interface-datanetwork list List of data interfaces (logical data interface names) on a specific system/host and you can know how they are mapped to the above data networks. To understand to what physical interface it is mapped on the specific host you can use with system host-if-list Regards, Venkata Veldanda From: 钱江 Sent: Friday, November 01, 2019 10:02 AM To: Ezpeer Chen Cc: Sun, Austin ; starlingx-discuss Subject: [Starlingx-discuss] 回复: 回复:回复: openstack network creation failure: Flat provider networks are disabled Hi, Ezpeer Thanks very much, however I am very confused with some starlingx network concepts. From the system command, we see, systen network list system interface-network list system datanetwork list system interface-datanetwork list Could you tell me concepts of these network/datanetwork/interface-network? Or any available materials about the system networks? ------------------------------------------------------------------ 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:40 收件人:钱江 > 抄 送:"Sun, Austin" >; starlingx-discuss > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Please reference the document https://wiki.openstack.org/wiki/StarlingX/Networking . The document has an example about configuring the flat network. · Configure the flat network. Thanks. BR 钱江 > 於 2019年11月1日 週五 上午10:28寫道: Hi, Ezpeer I just followed "Install StarlingX Kubernetes on Virtual AIO-SX" (https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html). Below pasted from the guide, 1). the read one, "physnet0" and "physnet1", should I replace it using real interfaces in host? 2). do you have any material about "system datanetwork" -------------------------- DATA0IF=eth1000 DATA1IF=eth1001 export COMPUTE=controller-0 PHYSNET0='physnet0' PHYSNET1='physnet1' SPL=/tmp/tmp-system-port-list SPIL=/tmp/tmp-system-host-if-list system host-port-list ${COMPUTE} --nowrap > ${SPL} system host-if-list -a ${COMPUTE} --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 datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system host-if-modify -m 1500 -n data1 -c data ${COMPUTE} ${DATA1IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} ${PHYSNET0} system interface-datanetwork-assign ${COMPUTE} ${DATA1IFUUID} ${PHYSNET1} -------------------------- ------------------------------------------------------------------ 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 > 抄 送:"Sun, Austin" >; starlingx-discuss > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 > 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 > 抄 送:"Sun, Austin" >; starlingx-discuss > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 > 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 >; starlingx-discuss > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 > Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin >; starlingx-discuss > Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 >; starlingx-discuss > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 > Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss > Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss valid_lft forever preferred_lft forever 163: cali4b88ce Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX Install StarlingX Kubernetes on Virtual AIO-SX -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Nov 1 13:29:50 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 1 Nov 2019 13:29:50 +0000 Subject: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627CD67@CDSMSX102.ccr.corp.intel.com> Hi Angie & Tee Have you checked my proposal? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 29, 2019 3:18 PM To: Wang, Jing (Angie) ; Tee.Ngo at windriver.com Cc: Qi, Mingyuan ; Chen, Tingjie ; 'starlingx-discuss at lists.starlingx.io' Subject: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Currently decoupling sysinv-conductor with armada application, you introduce new class ArmadaManifestOperator. But I find currently this class only decouple application override. For image list, it still depends on declaration in values.yaml in application's charts. We work to ceph containerization, plan to introduce new charts to launch ceph service. https://review.opendev.org/#/c/681457/ The image declaration in values.yaml is not same as currently application This chart will pull images rook/ceph:v1.1.1, with such way to declare image. https://review.opendev.org/#/c/681457/5/stx-platform-helm/stx-platform-helm/helm-charts/rook-ceph/values.yaml image: prefix: rook repository: rook/ceph tag: v1.1.1 pullPolicy: IfNotPresent So prefer in sysinv-conductor, also use ArmadaManifestOperator to update image list file. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Fri Nov 1 13:39:26 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Fri, 1 Nov 2019 13:39:26 +0000 Subject: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627CD67@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85627CD67@CDSMSX102.ccr.corp.intel.com> Message-ID: Adding Bob as he may have feedback based on the decoupling spec. https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2006537-decoupling-container-apps.rst Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:30 AM To: Wang, Jing (Angie); Ngo, Tee Cc: Qi, Mingyuan; Chen, Tingjie; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Have you checked my proposal? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 29, 2019 3:18 PM To: Wang, Jing (Angie) ; Tee.Ngo at windriver.com Cc: Qi, Mingyuan ; Chen, Tingjie ; 'starlingx-discuss at lists.starlingx.io' Subject: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Currently decoupling sysinv-conductor with armada application, you introduce new class ArmadaManifestOperator. But I find currently this class only decouple application override. For image list, it still depends on declaration in values.yaml in application's charts. We work to ceph containerization, plan to introduce new charts to launch ceph service. https://review.opendev.org/#/c/681457/ The image declaration in values.yaml is not same as currently application This chart will pull images rook/ceph:v1.1.1, with such way to declare image. https://review.opendev.org/#/c/681457/5/stx-platform-helm/stx-platform-helm/helm-charts/rook-ceph/values.yaml image: prefix: rook repository: rook/ceph tag: v1.1.1 pullPolicy: IfNotPresent So prefer in sysinv-conductor, also use ArmadaManifestOperator to update image list file. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Nov 1 13:45:46 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 1 Nov 2019 13:45:46 +0000 Subject: [Starlingx-discuss] patch review for layered build Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 1 13:49:18 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 1 Nov 2019 13:49:18 +0000 Subject: [Starlingx-discuss] patch review for layered build In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> I don't think we need to create anything. In my opinion, we need to drop the "/git" from the paths for these repos in the manifest: https://opendev.org/starlingx/manifest/src/branch/master/default.xml ie. and move the build files from "upstream" to these repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:46 AM To: Miller, Frank; Little, Scott; Penney, Don; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: patch review for layered build Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Fri Nov 1 14:05:33 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 1 Nov 2019 14:05:33 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 Content Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC2736A02@ALA-MBD.corp.ad.wrs.com> Folks, A portion of the PTG meeting next week will be dedicated to discussing the content the community would like to tackle in the next release. This is scheduled for wed afternoon, Nov 6th . An initial set of ideas is captured in https://etherpad.openstack.org/p/stx.4.0-feature-candidates Please have a look and provide comments on the existing items. If you are in Shanghai, would be great if you can attend. An agenda for the StarlingX PTG will be sent later. Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Nov 1 14:09:11 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 1 Nov 2019 14:09:11 +0000 Subject: [Starlingx-discuss] patch review for layered build In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627CDA5@CDSMSX102.ccr.corp.intel.com> What about these two foler. To move distributecloud to flock layer, we should move to other folder. stx/upstream/openstack/distributedcloud stx/upstream/openstack/distributedcloud-client BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don Sent: Friday, November 1, 2019 9:49 PM To: Chen, Haochuan Z ; Miller, Frank ; Little, Scott ; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build I don't think we need to create anything. In my opinion, we need to drop the "/git" from the paths for these repos in the manifest: https://opendev.org/starlingx/manifest/src/branch/master/default.xml ie. and move the build files from "upstream" to these repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:46 AM To: Miller, Frank; Little, Scott; Penney, Don; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: patch review for layered build Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 1 14:20:41 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 1 Nov 2019 14:20:41 +0000 Subject: [Starlingx-discuss] patch review for layered build In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627CDA5@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85627CDA5@CDSMSX102.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B16E9@ALA-MBD.corp.ad.wrs.com> Yes, those contain the build files to which I'm referring. All that content would be moved to the dist cloud repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 10:09 AM To: Penney, Don; Miller, Frank; Little, Scott; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build What about these two foler. To move distributecloud to flock layer, we should move to other folder. stx/upstream/openstack/distributedcloud stx/upstream/openstack/distributedcloud-client BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don Sent: Friday, November 1, 2019 9:49 PM To: Chen, Haochuan Z ; Miller, Frank ; Little, Scott ; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build I don't think we need to create anything. In my opinion, we need to drop the "/git" from the paths for these repos in the manifest: https://opendev.org/starlingx/manifest/src/branch/master/default.xml ie. and move the build files from "upstream" to these repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:46 AM To: Miller, Frank; Little, Scott; Penney, Don; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: patch review for layered build Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 1 14:56:16 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 1 Nov 2019 14:56:16 +0000 Subject: [Starlingx-discuss] patch review for layered build In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15B16E9@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85627CDA5@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B16E9@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B1736@ALA-MBD.corp.ad.wrs.com> I'll add a task to the story and start working on relocating these repos. From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Friday, November 01, 2019 10:21 AM To: Chen, Haochuan Z; Miller, Frank; Little, Scott; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] patch review for layered build Yes, those contain the build files to which I'm referring. All that content would be moved to the dist cloud repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 10:09 AM To: Penney, Don; Miller, Frank; Little, Scott; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build What about these two foler. To move distributecloud to flock layer, we should move to other folder. stx/upstream/openstack/distributedcloud stx/upstream/openstack/distributedcloud-client BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don Sent: Friday, November 1, 2019 9:49 PM To: Chen, Haochuan Z ; Miller, Frank ; Little, Scott ; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build I don't think we need to create anything. In my opinion, we need to drop the "/git" from the paths for these repos in the manifest: https://opendev.org/starlingx/manifest/src/branch/master/default.xml ie. and move the build files from "upstream" to these repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:46 AM To: Miller, Frank; Little, Scott; Penney, Don; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: patch review for layered build Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Nov 1 14:59:40 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 1 Nov 2019 14:59:40 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 Content In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC2736A02@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EC2736A02@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BDFC04350@fmsmsx123.amr.corp.intel.com> Brent, thank you. I have added some comments, some new items and a new section for Industrial features. On our side we will be pushing hard over the next year enabling Industrial use cases in StarlingX. brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Friday, November 1, 2019 7:06 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 4.0 Content Folks, A portion of the PTG meeting next week will be dedicated to discussing the content the community would like to tackle in the next release. This is scheduled for wed afternoon, Nov 6th . An initial set of ideas is captured in https://etherpad.openstack.org/p/stx.4.0-feature-candidates Please have a look and provide comments on the existing items. If you are in Shanghai, would be great if you can attend. An agenda for the StarlingX PTG will be sent later. Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tee.Ngo at windriver.com Fri Nov 1 15:00:30 2019 From: Tee.Ngo at windriver.com (Ngo, Tee) Date: Fri, 1 Nov 2019 15:00:30 +0000 Subject: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85627CD67@CDSMSX102.ccr.corp.intel.com> Message-ID: <80ED4CE81E3D8F4099306648E95DAFE453AEA130@ALA-MBD.corp.ad.wrs.com> Martin, Bob designed and implemented the ArmadaManifestOperator and is also a Ceph SME. He's in the best position to provide you feedback on the proposed changes. Tee From: Bailey, Henry Albert (Al) Sent: November-01-19 9:39 AM To: Chen, Haochuan Z; Wang, Jing (Angie); Ngo, Tee; Church, Robert Cc: Qi, Mingyuan; Chen, Tingjie; 'starlingx-discuss at lists.starlingx.io' Subject: RE: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Adding Bob as he may have feedback based on the decoupling spec. https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2006537-decoupling-container-apps.rst Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:30 AM To: Wang, Jing (Angie); Ngo, Tee Cc: Qi, Mingyuan; Chen, Tingjie; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Have you checked my proposal? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 29, 2019 3:18 PM To: Wang, Jing (Angie) ; Tee.Ngo at windriver.com Cc: Qi, Mingyuan ; Chen, Tingjie ; 'starlingx-discuss at lists.starlingx.io' Subject: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Currently decoupling sysinv-conductor with armada application, you introduce new class ArmadaManifestOperator. But I find currently this class only decouple application override. For image list, it still depends on declaration in values.yaml in application's charts. We work to ceph containerization, plan to introduce new charts to launch ceph service. https://review.opendev.org/#/c/681457/ The image declaration in values.yaml is not same as currently application This chart will pull images rook/ceph:v1.1.1, with such way to declare image. https://review.opendev.org/#/c/681457/5/stx-platform-helm/stx-platform-helm/helm-charts/rook-ceph/values.yaml image: prefix: rook repository: rook/ceph tag: v1.1.1 pullPolicy: IfNotPresent So prefer in sysinv-conductor, also use ArmadaManifestOperator to update image list file. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Fri Nov 1 15:01:12 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 1 Nov 2019 15:01:12 +0000 Subject: [Starlingx-discuss] StarlingX 4.0 Content In-Reply-To: <9A85D2917C58154C960D95352B22818BDFC04350@fmsmsx123.amr.corp.intel.com> References: <2588653EBDFFA34B982FAF00F1B4844EC2736A02@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BDFC04350@fmsmsx123.amr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC2736E37@ALA-MBD.corp.ad.wrs.com> Thanks Bruce Brent From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Friday, November 1, 2019 11:00 AM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] StarlingX 4.0 Content Brent, thank you. I have added some comments, some new items and a new section for Industrial features. On our side we will be pushing hard over the next year enabling Industrial use cases in StarlingX. brucej From: Rowsell, Brent [mailto:Brent.Rowsell at windriver.com] Sent: Friday, November 1, 2019 7:06 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 4.0 Content Folks, A portion of the PTG meeting next week will be dedicated to discussing the content the community would like to tackle in the next release. This is scheduled for wed afternoon, Nov 6th . An initial set of ideas is captured in https://etherpad.openstack.org/p/stx.4.0-feature-candidates Please have a look and provide comments on the existing items. If you are in Shanghai, would be great if you can attend. An agenda for the StarlingX PTG will be sent later. Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Fri Nov 1 05:31:27 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Fri, 1 Nov 2019 05:31:27 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 10/31 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D643458@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Oct 31/2019 · stx.3.0 Features / Enhancements * TSN Support for VM workloads § Created new story:https://storyboard.openstack.org/#!/story/2006746 for TSN container support. SB https://storyboard.openstack.org/#!/story/2005516 can be closed. § Prime: Huifeng § Elio: * OVS collectd resource monitoring § Prime: Chenjie § https://storyboard.openstack.org/#!/story/2002948 / https://bugs.launchpad.net/starlingx/+bug/1834512 § Patch is in review: https://review.opendev.org/#/c/687025/: Ghada will follow up with Core reviewer * Openstack Rebase to Train § A network regression with an IPv6 only configuration required for validation § Elio: Will start regression test after the train patch available. · stx.4.0 Feature Proposals: * Tentative Release Milestones/Timeline: § https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 § Should aim to propose all features by milestone-1 ...which is Jan 24, 2020 § Features will also be discussed in the PTG in Shanghai. · The 3 features below are already on the list * OVS-DPDK Containerization (Defered from stx.3.0) § Prime: Cheng Li § story link: https://storyboard.openstack.org/#!/story/2005496 * Openstack Rebase to Ussuri * TSN Support for container: https://storyboard.openstack.org/#!/story/2006746, Will focus on Kata container (Kata container support will be ready in stx 4.0) * From Matt: · Baremetal Ingress Controllers · Contribute to the calico project since we are using it in stx · stx.2.0 Bugs * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.2.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * Current Count: 4 / In Progress: * https://bugs.launchpad.net/starlingx/+bug/1835807 - Joseph, on hold - no fix in sight after extensive investigation, not neutron issue, need to decide the next step * https://bugs.launchpad.net/starlingx/+bug/1836252 - Joseph, on hold, will be work in next 2 weeks * https://bugs.launchpad.net/starlingx/+bug/1839181 - Chenjie, on hold for another reproduction where more data may be gathered. not reproduced now. Ask Yan to follow up. * https://bugs.launchpad.net/starlingx/+bug/1841189 - Gongjun, Still investigating the cause. * https://bugs.launchpad.net/starlingx/+bug/1849655 - Marvin, Still investigating the cause. need more information from reporter. · stx.3.0 Bugs: to be scrubbed in next meeting. * Deadline for bug resolution: End of Nov * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * Current count: 13 / In Progress: 4 * Agreed to do a scrub on our next call _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Fri Nov 1 09:48:41 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Fri, 1 Nov 2019 09:48:41 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX non-OpenStack distro meeting Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360B0F32@SHSMSX104.ccr.corp.intel.com> Cancel this series due to US daylight saving time is finished. Austin Sun, our new PL will send out the meeting appointment from his calendar. Thanks all for the support. - cindy * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o 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 * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 19191 bytes Desc: not available URL: From bruce.e.jones at intel.com Fri Nov 1 17:38:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 1 Nov 2019 17:38:07 +0000 Subject: [Starlingx-discuss] Dev process document ready for review Message-ID: <9A85D2917C58154C960D95352B22818BDFC04500@fmsmsx123.amr.corp.intel.com> I've completed the first draft of this document and it is ready for review. Thank you to the folks who have already helped make it better! https://review.opendev.org/#/c/691740/ brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Nov 1 18:28:29 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 1 Nov 2019 11:28:29 -0700 Subject: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 In-Reply-To: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> References: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> Message-ID: <393877e4-b8d8-59b1-a634-7f405daf00bf@linux.intel.com> I think this message got stuck in the queue, I am just seeing it now. On 10/30/19 4:17 AM, zhao.shuai wrote: > Hi StarlingX Community: > > Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. > > Completed Task: > 1. GCC compiler version upgrade --> GCC version 8.2.1 > 2. Kernel 4.18 with starlingX patch compilation has been completed.(Patch40004,Patch40007,Patch40008) > Can you explain what you are referring to when you say Patch4000*, I don't know which ones they map to? > Doing Task: > 1. src rpm package el8 upgrade(if there is el8 version) Do you mean "Binary RPM" here? We should be trying to use the latest binary RPMs from CentOS-8 (el8). > 2. If there is no el8 version of SRPM compilation failed, we need to build a patch fix it. We want to fully understand what patches are changing or what additional patches you think you need to add. > 3. Configure kernel 4.18 config file with reference to STX kernel 3.10 config file (kernel-3.10.0-x86_64.config.tis_extra) > 4. For the el8 version SRPM package that fails to be compiled, the RPM package of the el8 version is preferentially searched for replacement. > > Please see the attachment for the results of the advancement > We need a better method to understand what changes are getting made between these spreadsheet changes. I am not understanding your actual changes. Thanks Sau! > Thank you! > > Best Regards > Wish you happy everyday! > -------------------------------- > Shuai - Neusoft > > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2019年10月18日 5:36 > 收件人: starlingx-discuss at lists.starlingx.io > 抄送: Rowsell, Brent > 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting > > > Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. > > As mentioned, most of the patches can be dropped, except for the Notification of Death patch. > > My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). > > Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. > > Sau! > > > > > On 10/16/19 6:53 AM, Xie, Cindy wrote: >> Agenda & notes for 10/16 meeting: >> >> . Ceph containerization update (Tingjie) >> https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. >> https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. >> verified in AIO and multi-node provision. >> configuration needs to be override according to STX parameters. >> Martin working on this for parameters to align w/ the native deployment. >> for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. >> test case development is in progress, Tingjie will sync with Fernando. >> for sysinv, still need to working on patches, not ready for upload/review. >> AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. >> >> . Debranding update (Saul) >> Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. >> https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. >> >> . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: >> https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. >> https://storyboard.openstack.org/#!/story/2006729 >> Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. >> AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. >> See >> https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu >> gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details >> https://github.com/xe1gyq/linux/commits/v4.19 >> https://github.com/xe1gyq/linux/commits/v4.18 >> AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX >> and in CentOS 8.0 >> >> . Opens - none >> _____________________________________________ >> From: Xie, Cindy >> Sent: Tuesday, October 15, 2019 9:39 PM >> To: Wold, Saul ; >> 'starlingx-discuss at lists.starlingx.io' >> ; 'Rowsell, Brent' >> >> Subject: RE: Weekly StarlingX non-OpenStack distro meeting >> >> >> Agenda: >> - Ceph containerization update (Tingjie) >> - Debranding update (Saul) >> - CentOS 8 upgrade planning (Cindy) >> - Opens >> >> Cindy Xie >> IAGS >> >> http://starlingx.io/ >> >> >> -----Original Appointment----- >> From: Xie, Cindy >> Sent: Thursday, April 25, 2019 5:42 PM >> To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' >> Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; >> 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, >> Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, >> Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W >> Subject: Weekly StarlingX non-OpenStack distro meeting >> When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. >> Where: https://zoom.us/j/342730236 >> >> >> . Cadence and time slot: >> o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . >> Call Details: >> o Zoom link: https://zoom.us/j/342730236 o 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 >> . Meeting Agenda and Minutes: >> o https://etherpad.openstack.org/p/stx-distro-other >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Ghada.Khalil at windriver.com Fri Nov 1 20:04:27 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 1 Nov 2019 20:04:27 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 31/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15E5E77@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - October 31 2019 stx.3.0 - Feature Status: - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Upversion to train - Sanity w/ train is working on AIO-SX, AIO-DX, and standard (non-storage) - Sanity w/ train on external storage is failing -- not able to launch VMs w/ qcow images - Zhipeng is unable to reproduce, so test team is working to give him access to system - This issue has been under investigation for the last week - Other features - Features completed this week - Backup & Restore with containers - Redfish Integration - Infrastructure & Cluster Monitoring << missing doc info - Features in Test In Progress - Distributed Cloud - Fault Containerization -- re-test after disabling the fm container - Features that need updates - Intel GPU support for K8s << missing doc info - Intel QAT support for K8s << missing doc info - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 44% (up from 39%) - Regression was halted waiting for train. Given the current issues, test team is re-working the plan - Options: - Continue with regression on master - This means openstack test-cases will have to be re-run after train is merged - Run regression with a designer build w/ train - This means that fixes from master will potentially not be picked up - Focus on test-cases which are unrelated to openstack first - Agreed to continue with test-cases unrelated to openstack - specifically around manual regression - Also Ada will determine when openstack train needs to merge to still finish regression first pass within a reasonable time-frame - Right now, regression finish date is Nov 22 - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 69% (up from 58%) - Remaining features are Openstack Train & Distributed Cloud - Expect Distributed Cloud to finish this week as per plan stx.4.0 - Tentative Dates - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Candidate List: ** for discussion in the PTG - https://etherpad.openstack.org/p/stx.4.0-feature-candidates From cristopher.j.lemus.contreras at intel.com Fri Nov 1 20:53:45 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Fri, 1 Nov 2019 20:53:45 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> Message-ID: Hello, Using the EB that Zhipeng provided, and replacing “cirros-0.4.0-x86_64-disk.qcow2” with “cirros-0.4.0-x86_64-disk.img”, Sanity status is Green. AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO – Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] Standard - 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 PASS ] =========================================== Just the cirros image was replaced. Centos file is still a .qcow2. Please, let me know if you need further details. Thanks & Regards, Cristopher Lemus From: "Liu, ZhipengS" Date: Friday, November 1, 2019 at 12:02 AM To: "Xie, Cindy" , "Lemus Contreras, Cristopher J" , '朱博祥' , "'starlingx-discuss at lists.starlingx.io'" Cc: "Alonso, Juan Carlos" , "Hu, Yong" , "Cabrales, Ada" , "Jones, Bruce E" , "Martinez Monroy, Elio" Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi all, After using new image file (cirros-0.4.0-x86_64-disk.img), we can launch instance on standard external Storage (2+2+2) now. It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by Cristopher Lemus causes qemu-img detecting wrong format after format convert from qcow2to raw in Nova code. We are not sure how/where we got this image file. Thanks! Zhipeng From: Liu, ZhipengS Sent: 2019年10月31日 17:31 To: Xie, Cindy ; Lemus Contreras, Cristopher J ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Hu, Yong ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, For remote storage configuration, we have overridden below configurations in helm/nova.py. if remote_storage: default_config.update({'force_raw_images': True}) libvirt_config.update({'images_type': 'rbd', 'images_rbd_pool': rbd_pool, 'images_rbd_ceph_conf': rbd_ceph_conf}) else: libvirt_config.update({'images_type': 'default'}) Next step: The only issue we need to figure out is why image format is still qcow2 after image format convert by qemu-img in nova code. I tried to reproduce it in my virtualized multi-node environment, but no issue found, VM created normally. (I copied yellow code block to else branch) In /var/lib/nova/instances/_base/ folder, I can see one qcow2 image and one raw image which should be converted by nova. [root at compute-1 _base]# ls 3cb926303b665709318d2c099722b914025023b4 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee [root at compute-1 _base]# qemu-img info 3cb926303b665709318d2c099722b914025023b4 image: 3cb926303b665709318d2c099722b914025023b4 file format: qcow2 virtual size: 44M (46137344 bytes) disk size: 12M cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false [root at compute-1 _base]# qemu-img info 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee file format: raw virtual size: 44M (46137344 bytes) disk size: 13M Any comment? Thanks! zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 10:15 To: Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang and all, In fetch_to_raw(), After force convert image from qcow2 to raw, the format is still not raw, then throw below error. It seems qemu-image convert image failed. Zhipeng From: Liu, ZhipengS > Sent: 2019年10月31日 9:35 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; '朱博祥' >; 'starlingx-discuss at lists.starlingx.io' > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade From: Liu, ZhipengS Sent: 2019年10月30日 23:24 To: Xie, Cindy >; Lemus Contreras, Cristopher J >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Boxiang, It should be an issue in nova train. Error log is below: build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, but format is now qcow2' You tried to fix this issue before in nova LP: https://bugs.launchpad.net/nova/+bug/1816686 In your patch: https://review.opendev.org/#/c/640271 (This patch is already in train release now) You added below commit message in the patch. “When we import image into rbd, check the format of cache images. If the format is not raw, remove it first and fetch it again. It will be raw format now.” However, it seems not work! Below code will throw error when image format is not raw and block the VM creation. In nova/virt/images.py def fetch_to_raw() ==> if data.file_format != "raw": raise exception.ImageUnacceptable(image_id=image_href, reason=_("Converted to raw, but format is now %s") Not sure if your patch fixed this issue or is there any regression introduced in nova code later. Any comment from you? I will check nova code further tomorrow and sync with you. We may need a patch for nova☹ Thanks! Zhipeng From: Xie, Cindy > Sent: 2019年10月30日 22:49 To: Lemus Contreras, Cristopher J >; Liu, ZhipengS >; 朱博祥 >; starlingx-discuss at lists.starlingx.io Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: RE: [Starlingx-discuss] About EB verification for openstack train upgrade + mailing list in case anybody can help on debug the issue. From: Lemus Contreras, Cristopher J > Sent: Wednesday, October 30, 2019 7:45 PM To: Liu, ZhipengS >; 朱博祥 > Cc: Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Zhipeng, The results are OK for Simplex, Duplex and Standard Local Storage, all Test Cases PASSED. For Standard External Storage (2+2+2) there is a high quantity of Test Cases failing because we cannot launch instances. Here’s a sample output: http://paste.openstack.org/show/785641/ with the error that matches what is described on the launchpad. Sanity summary for this specific configuration: http://paste.openstack.org/show/785655/ Please, let us know if you need additional details. Thanks & Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Nov 1 20:54:04 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 1 Nov 2019 20:54:04 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191101 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-01 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] Standard - 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 PASS ] =========================================== Sanity Test is executed in a Containers - 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] Standard - 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006758.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Fri Nov 1 21:07:58 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Fri, 1 Nov 2019 21:07:58 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 31/2019 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15E5E77@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15E5E77@ALA-MBD.corp.ad.wrs.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF01AB4@FMSMSX114.amr.corp.intel.com> Hello, I built a test plan for openstack only, and , if we can get help from Wind River to execute it, we would need 2 weeks for running this special test plan. In the other hand, Cristopher just sent the confirmation for the sanity tests ran in the Engineering Build with train integrated. It's green. Regards Ada > -----Original Message----- > From: Khalil, Ghada > Sent: Friday, November 1, 2019 2:04 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Oct 31/2019 > > Agenda/Minutes are posted at: > https://etherpad.openstack.org/p/stx-releases > > Release Team Meeting - October 31 2019 > stx.3.0 > - Feature Status: > - https://docs.google.com/spreadsheets/d/1ZFR-9- > riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 > > - Upversion to train > - Sanity w/ train is working on AIO-SX, AIO-DX, and standard (non-storage) > - Sanity w/ train on external storage is failing -- not able to launch VMs w/ > qcow images > - Zhipeng is unable to reproduce, so test team is working to give him access > to system > - This issue has been under investigation for the last week > > - Other features > - Features completed this week > - Backup & Restore with containers > - Redfish Integration > - Infrastructure & Cluster Monitoring << missing doc info > - Features in Test In Progress > - Distributed Cloud > - Fault Containerization -- re-test after disabling the fm container > - Features that need updates > - Intel GPU support for K8s << missing doc info > - Intel QAT support for K8s << missing doc info > > - Regression Test > - > https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG- > W1OeGuAJWnrAWI/edit#gid=1717644237 > - Completion Rate: 44% (up from 39%) > - Regression was halted waiting for train. Given the current issues, test team > is re-working the plan > - Options: > - Continue with regression on master > - This means openstack test-cases will have to be re-run after train > is merged > - Run regression with a designer build w/ train > - This means that fixes from master will potentially not be picked > up > - Focus on test-cases which are unrelated to openstack first > - Agreed to continue with test-cases unrelated to openstack - > specifically around manual regression > - Also Ada will determine when openstack train needs to merge to still > finish regression first pass within a reasonable time-frame > - Right now, regression finish date is Nov 22 > > - Feature Test > - > https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM > _q-cMfHcItJlY/edit#gid=968103774 > - Completion Rate: 69% (up from 58%) > - Remaining features are Openstack Train & Distributed Cloud > - Expect Distributed Cloud to finish this week as per plan > > stx.4.0 > - Tentative Dates > - > https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysK > VnHpbrEc17_yg/edit#gid=0 > - Candidate List: ** for discussion in the PTG > - https://etherpad.openstack.org/p/stx.4.0-feature-candidates > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From sgw at linux.intel.com Fri Nov 1 23:46:22 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 1 Nov 2019 16:46:22 -0700 Subject: [Starlingx-discuss] Git tagging and PBR versions Message-ID: <04cb4e4a-d848-aff1-034c-a0741ff29a0d@linux.intel.com> Scott, Dean: I have been digging into why we are getting some strange PBR versioning results from our StarlingX repos. As Bin started with fault, I did as well. There are a couple of observations, depending on which version of PBR, there are some different results, we need to be using the latest 5.4.3 if possible, but anything 4.2.0 and newer will work with our repos. The reason being is that the newer version recognizes the "v" prefix and is then preferred over our older datever format (2018.10). What Bin discovered when he ran the setup.py -q rpm_version was the PBR version going backwards in a way not expected, this is because PBR looks does some magic to account for RPM ordering. We have a v2.0.0.rc0 tag on master, this seems to match other OpenStack repos (I looked at nova and kolla). They have rc tags on master and then a final tag on the stable branch as appropriate. When Bin ran "python setup.py -q rpm_version" in fmclient the result was: 1.9999.9999.rc1.dev31 When I try to run the same command for Nova or Kolla, I get what I think is better version info. Nova: Current version: 20.0.0 PBR reports: 20.0.9999.dev198 Kolla:Current version: 8.0.0.0rc1 PBR reports: 8.0.9999.dev101 I have pinged folks in the Infra channel and of course many are traveling, I did hear from Monty and Jeremy and will try to connect with them in Shanghai. They did think there might be some subtle issue going on so it peaked their interest a little. In the meantime, I will also be spending flight time in the Python debugger trying to figure out why this is happening also. Sau! From ricardo.o.perez at intel.com Sat Nov 2 05:28:20 2019 From: ricardo.o.perez at intel.com (Perez, Ricardo O) Date: Sat, 2 Nov 2019 05:28:20 +0000 Subject: [Starlingx-discuss] CNCF first execution for STX Message-ID: Hi StarlingX team, We have started the CNCF test execution for StarlingX. This was the system configuration used: * Virtual environment 2+2 * BUILD_ID="20191101T013000Z" * BUILD_NUMBER="303" We have used the sonobuoy tool, running only the conformance tests for certification: ./sonobuoy run --mode=certified-conformance Here are the results: controller-0:~$ ./sonobuoy status PLUGIN STATUS RESULT COUNT e2e complete failed 1 systemd-logs complete passed 1 systemd-logs complete 3 If you require further information I can send you directly the output logs (~2.5 Mb .tar.gz file). Which isn't attached by now, to avoid to spam all e-mail list members. The attached file is a very short version of the log files structure. The next step will be to execute all of this in BM, however we are still working in our local infrastructure to solve some present issues. As soon as we have more information we will let you know. Regards -Ricardo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: CNCF_short_log.txt URL: From cristopher.j.lemus.contreras at intel.com Sat Nov 2 08:49:42 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 02 Nov 2019 02:49:42 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6sp4b8@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191102T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From ada.cabrales at intel.com Fri Nov 1 22:45:35 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Fri, 1 Nov 2019 22:45:35 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94@FMSMSX114.amr.corp.intel.com> Updates will be requested offline Weekly meetings on Tuesdays at 9am Pacific * Zoom link: https://zoom.us/j/342730236 o 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: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3486 bytes Desc: not available URL: From Anirudh.Gupta at hsc.com Sat Nov 2 21:04:08 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Sat, 2 Nov 2019 21:04:08 +0000 Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Message-ID: Hi Team, I am trying to integrate StarlingX 2.0 with Open Source Mano 6.0, but facing errors as the public endpoints for every services are not exposed. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#configure-helm-endpoint-domain I am getting error 503 code: 503\\n description: 'VIM Exception vimconnUnexpectedResponse EndpointNotFound: public\\n endpoint for image service not found However this was not the case with StarlingX previous release 2018.10. I had successfully integrated it. This is because now the openstack services are now containerized and URL is not publicly exposed. Can someone please update the steps in order to expose all services public endpoints outside StarlingX. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sun Nov 3 08:50:11 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 03 Nov 2019 02:50:11 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6t0227@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191103T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From sgw at linux.intel.com Sun Nov 3 14:09:40 2019 From: sgw at linux.intel.com (Saul Wold) Date: Sun, 3 Nov 2019 06:09:40 -0800 Subject: [Starlingx-discuss] Git tagging and PBR versions In-Reply-To: <04cb4e4a-d848-aff1-034c-a0741ff29a0d@linux.intel.com> References: <04cb4e4a-d848-aff1-034c-a0741ff29a0d@linux.intel.com> Message-ID: <43c06c98-88c9-1db4-995f-a9de2a2e0f8b@linux.intel.com> I think I worked it out. The difference in the OpenStack repos is they actually use the "Sem-Ver: feature" tag & info in commit messages and that causes the minor number bump internally in PBR to 20.1.0 or 8.1.0 and then decrements for the development version number with 9999.devX So we may want to consider adding in the Sem-Ver: tag on a master commit for the repos. Thoughts? Sau! On 11/1/19 4:46 PM, Saul Wold wrote: > > Scott, Dean: > > I have been digging into why we are getting some strange PBR versioning > results from our StarlingX repos.  As Bin started with fault, I did as > well.  There are a couple of observations, depending on which version of > PBR, there are some different results, we need to be using the latest > 5.4.3 if possible, but anything 4.2.0 and newer will work with our > repos.  The reason being is that the newer version recognizes the "v" > prefix and is then preferred over our older datever format (2018.10). > > What Bin discovered when he ran the setup.py -q rpm_version was the PBR > version going backwards in a way not expected, this is because PBR looks > does some magic to account for RPM ordering.  We have a v2.0.0.rc0 tag > on master, this seems to match other OpenStack repos (I looked at nova > and kolla). They have rc tags on master and then a final tag on the > stable branch as appropriate. > > When Bin ran "python setup.py -q rpm_version" in fmclient the result > was: 1.9999.9999.rc1.dev31 > > When I try to run the same command for Nova or Kolla, I get what I think > is better version info. > Nova: Current version: 20.0.0      PBR reports: 20.0.9999.dev198 > Kolla:Current version:  8.0.0.0rc1 PBR reports:  8.0.9999.dev101 > > I have pinged folks in the Infra channel and of course many are > traveling, I did hear from Monty and Jeremy and will try to connect with > them in Shanghai. They did think there might be some subtle issue going > on so it peaked their interest a little. > > In the meantime, I will also be spending flight time in the Python > debugger trying to figure out why this is happening also. > > Sau! > > > > > > From zhaos at neusoft.com Sun Nov 3 13:32:57 2019 From: zhaos at neusoft.com (zhao.shuai) Date: Sun, 3 Nov 2019 21:32:57 +0800 Subject: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 In-Reply-To: <393877e4-b8d8-59b1-a634-7f405daf00bf@linux.intel.com> References: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> <393877e4-b8d8-59b1-a634-7f405daf00bf@linux.intel.com> Message-ID: <000001d5924b$34b99e00$9e2cda00$@neusoft.com> Hi Saul, Haitao, Shuicheng, Thank you for your hard work and positive response. As you suggested in the last StarlingX non-OpenStack distro meeting, Our team should use Google Docs Or gitHub to show our progress and results in a more real-time way. Recently, we have moved our work and progress reports to Github. The StarlingX kernel version to CentOS 4.18 work path is as follows: https://github.com/StarlingX-Neusoft/Centos8 During the porting process, we will update our real-time Q&A information in the documents (StarlingX_CentOS8.0_Kernel_Upgrade_Q&A List.xls). We hope that the experts in the community can check the problems we have when you have time. If you can get your advice, we will be very honored. Thank you! ① >>Can you explain what you are referring to when you say Patch4000*, I >>don't know which ones they map to? Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx Sheet: [STX Kernel-std Patches Details] STD-Status = Patch ② >>Do you mean "Binary RPM" here? We should be trying to use the latest >>binary RPMs from CentOS-8 (el8). Yes, we hope to try this way. Please see: https://github.com/StarlingX-Neusoft/Centos8/tree/master/cgcs-root/stx ③ >>We want to fully understand what patches are changing or what additional >>patches you think you need to add. Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx Sheet: [srpm] Column E =【CentOS8 SRPM packages(El8)】 ④ >>We need a better method to understand what changes are getting made >>between these spreadsheet changes. I am not understanding your actual changes. we have moved our work and progress reports to Github. Please see: https://github.com/StarlingX-Neusoft/Centos8 Thank you very much! Best Regards Wish you happy everyday! -------------------------------- Shuai - Neusoft -----邮件原件----- 发件人: Saul Wold 发送时间: 2019年11月2日 2:28 收件人: starlingx-discuss at lists.starlingx.io 主题: Re: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 I think this message got stuck in the queue, I am just seeing it now. On 10/30/19 4:17 AM, zhao.shuai wrote: > Hi StarlingX Community: > > Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. > > Completed Task: > 1. GCC compiler version upgrade --> GCC version 8.2.1 > 2. Kernel 4.18 with starlingX patch compilation has been completed.(Patch40004,Patch40007,Patch40008) > Can you explain what you are referring to when you say Patch4000*, I don't know which ones they map to? > Doing Task: > 1. src rpm package el8 upgrade(if there is el8 version) Do you mean "Binary RPM" here? We should be trying to use the latest binary RPMs from CentOS-8 (el8). > 2. If there is no el8 version of SRPM compilation failed, we need to build a patch fix it. We want to fully understand what patches are changing or what additional patches you think you need to add. > 3. Configure kernel 4.18 config file with reference to STX kernel 3.10 config file (kernel-3.10.0-x86_64.config.tis_extra) > 4. For the el8 version SRPM package that fails to be compiled, the RPM package of the el8 version is preferentially searched for replacement. > > Please see the attachment for the results of the advancement > We need a better method to understand what changes are getting made between these spreadsheet changes. I am not understanding your actual changes. Thanks Sau! > Thank you! > > Best Regards > Wish you happy everyday! > -------------------------------- > Shuai - Neusoft > > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2019年10月18日 5:36 > 收件人: starlingx-discuss at lists.starlingx.io > 抄送: Rowsell, Brent > 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting > > > Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. > > As mentioned, most of the patches can be dropped, except for the Notification of Death patch. > > My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). > > Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. > > Sau! > > > > > On 10/16/19 6:53 AM, Xie, Cindy wrote: >> Agenda & notes for 10/16 meeting: >> >> . Ceph containerization update (Tingjie) >> https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. >> https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. >> verified in AIO and multi-node provision. >> configuration needs to be override according to STX parameters. >> Martin working on this for parameters to align w/ the native deployment. >> for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. >> test case development is in progress, Tingjie will sync with Fernando. >> for sysinv, still need to working on patches, not ready for upload/review. >> AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. >> >> . Debranding update (Saul) >> Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. >> https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. >> >> . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: >> https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. >> https://storyboard.openstack.org/#!/story/2006729 >> Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. >> AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. >> See >> https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu >> gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details >> https://github.com/xe1gyq/linux/commits/v4.19 >> https://github.com/xe1gyq/linux/commits/v4.18 >> AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX >> and in CentOS 8.0 >> >> . Opens - none >> _____________________________________________ >> From: Xie, Cindy >> Sent: Tuesday, October 15, 2019 9:39 PM >> To: Wold, Saul ; >> 'starlingx-discuss at lists.starlingx.io' >> ; 'Rowsell, Brent' >> >> Subject: RE: Weekly StarlingX non-OpenStack distro meeting >> >> >> Agenda: >> - Ceph containerization update (Tingjie) >> - Debranding update (Saul) >> - CentOS 8 upgrade planning (Cindy) >> - Opens >> >> Cindy Xie >> IAGS >> >> http://starlingx.io/ >> >> >> -----Original Appointment----- >> From: Xie, Cindy >> Sent: Thursday, April 25, 2019 5:42 PM >> To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' >> Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; >> 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, >> Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, >> Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W >> Subject: Weekly StarlingX non-OpenStack distro meeting >> When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. >> Where: https://zoom.us/j/342730236 >> >> >> . Cadence and time slot: >> o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . >> Call Details: >> o Zoom link: https://zoom.us/j/342730236 o 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 >> . Meeting Agenda and Minutes: >> o https://etherpad.openstack.org/p/stx-distro-other >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- From Brent.Rowsell at windriver.com Sun Nov 3 21:04:30 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Sun, 3 Nov 2019 21:04:30 +0000 Subject: [Starlingx-discuss] Shanghai PTG Agenda Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> Folks, The current agenda for the PTG meeting can be found here. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sun Nov 3 23:36:25 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sun, 3 Nov 2019 23:36:25 +0000 Subject: [Starlingx-discuss] Shanghai PTG Agenda In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> Brent, Welcome to Shanghai! Do we already have a venue for the PTG? I have several StarlingX China customers asking where they shall go. Thx. - cindy From: Rowsell, Brent Sent: Monday, November 4, 2019 5:05 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Shanghai PTG Agenda Folks, The current agenda for the PTG meeting can be found here. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Mon Nov 4 00:15:49 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 4 Nov 2019 00:15:49 +0000 Subject: [Starlingx-discuss] Shanghai PTG Agenda In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> References: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC273F4DC@ALA-MBD.corp.ad.wrs.com> Hi Cindy, Yes, see PTG schedule, https://www.openstack.org/ptg#tab_schedule Brent From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Sunday, November 3, 2019 6:36 PM To: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Shanghai PTG Agenda Brent, Welcome to Shanghai! Do we already have a venue for the PTG? I have several StarlingX China customers asking where they shall go. Thx. - cindy From: Rowsell, Brent > Sent: Monday, November 4, 2019 5:05 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Shanghai PTG Agenda Folks, The current agenda for the PTG meeting can be found here. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Thanks, Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 4 00:20:00 2019 From: sgw at linux.intel.com (Saul Wold) Date: Sun, 3 Nov 2019 16:20:00 -0800 Subject: [Starlingx-discuss] Shanghai PTG Agenda In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> References: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> Message-ID: <6bdce69e-0215-bd30-b080-4312fb0d9bfc@linux.intel.com> On 11/3/19 3:36 PM, Xie, Cindy wrote: > Brent, > > Welcome to Shanghai! > > Do we already have a venue for the PTG? I have several StarlingX China > customers asking where they shall go. > Cindy, yes, there is a schedule for the PTG, the main PTG site is openstack.org/ptg. We are in room 430 both Wednesday and Thursday morning. Sau! > Thx. - cindy > > *From:* Rowsell, Brent > *Sent:* Monday, November 4, 2019 5:05 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Shanghai PTG Agenda > > Folks, > > The current agenda for the PTG meeting can be found here. > > https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai > > Thanks, > > Brent > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From haochuan.z.chen at intel.com Mon Nov 4 02:07:31 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 4 Nov 2019 02:07:31 +0000 Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627D0FD@CDSMSX102.ccr.corp.intel.com> Hi Anirudh Maybe you can check in this way to ensure image service is ready firstly. $ export OS_CLOUD=openstack_helm $ openstack endpoint list BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Sunday, November 3, 2019 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 35 Send Starlingx-discuss mailing list submissions to starlingx-discuss at 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 at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time (Cabrales, Ada) 2. Starlingx 2.0 Service Endpoints not publicly accessed from External Entities (Anirudh Gupta) 3. StarlingX platform-integ-apps docker images (cristopher.j.lemus.contreras at intel.com) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Nov 2019 22:45:35 +0000 From: "Cabrales, Ada" To: "starlingx-discuss at lists.starlingx.io" Cc: "Martinez Monroy, Elio" , "'Seiler, Glenn'" , "Hernandez Gonzalez, Fernando" , "'Komiyama, Takeo'" , "Xu, YizhouX" , "Armstrong, Robert H" , "Martinez Landa, Hayde" , "Alonso, Juan Carlos" , 'Peng Tan' , "Gomez, Juan P" , "Sun, Austin" , Banszel Martin Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94 at FMSMSX114.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Updates will be requested offline Weekly meetings on Tuesdays at 9am Pacific * Zoom link: https://zoom.us/j/342730236 o 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: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3486 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Sat, 2 Nov 2019 21:04:08 +0000 From: Anirudh Gupta To: "starlingx-discuss at lists.starlingx.io" , "starlingx-discuss-owner at lists.starlingx.io" Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Message-ID: Content-Type: text/plain; charset="utf-8" Hi Team, I am trying to integrate StarlingX 2.0 with Open Source Mano 6.0, but facing errors as the public endpoints for every services are not exposed. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#configure-helm-endpoint-domain I am getting error 503 code: 503\\n description: 'VIM Exception vimconnUnexpectedResponse EndpointNotFound: public\\n endpoint for image service not found However this was not the case with StarlingX previous release 2018.10. I had successfully integrated it. This is because now the openstack services are now containerized and URL is not publicly exposed. Can someone please update the steps in order to expose all services public endpoints outside StarlingX. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Sun, 03 Nov 2019 02:50:11 -0600 From: cristopher.j.lemus.contreras at intel.com To: Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6t0227 at fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191103T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 35 ************************************************* From ezpeerchen at gmail.com Mon Nov 4 02:21:12 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 4 Nov 2019 10:21:12 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> Message-ID: Dear Qianjiang, >From document: #Create a flat datanetwork and bind it to the interface. system datanetwork-add phy-flat flat system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat system host-unlock ${COMPUTE} Do you do interface-datanetwork-assign for phy-flat? Check interface-datanetwork-list first. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年11月1日 週五 下午5:31寫道: > Hi, Ezpeer > Just follow https://wiki.openstack.org/wiki/StarlingX/Networking > --- Configure the flat network. > > controller-0:~$ export OS_CLOUD=openstack_helm > controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print > $2}'` > controller-0:~$ echo $ADMINID > 95794c0fbfe9427b908eedb823aba318 > controller-0:~$ openstack network create --project ${ADMINID} > --provider-network-type=flat --provider-physical-network=phy-flat netflat > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'phy-flat' unknown for flat provider network. > controller-0:~$ > > and, > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 5c8391a3-be90-48dd-8df5-2c1118af979a | phy-flat | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > Please > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 16:31 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > * --provider-physical-network provider * = > incorrect > > You don't have the physical network named as "provider". > > > Please follow the document's example. > https://wiki.openstack.org/wiki/StarlingX/Networking > > Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: > Please follow the document's example. > https://wiki.openstack.org/wiki/StarlingX/Networking > > > - Configure the flat network. > > > 钱江 於 2019年11月1日 週五 下午3:36寫道: > But, still failure use type vlan > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 15:27 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Your data0 and data1 are vlan type datanetwork. > > > This is your configuration. > > system datanetwork-add ${PHYSNET0} vlan > system datanetwork-add ${PHYSNET1} vlan > > > 钱江 於 2019年11月1日 週五 下午3:17寫道: > You see, "eth1000" and "eth1001" are assigned to datanetwork. > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 14:46 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > Your enp2s1 interface is not assigned to any data network? > > > > Thanks. > > BR > > 钱江 於 2019年11月1日 週五 下午2:35寫道: > Hi, Ezpeer > > Below is the log of "system interface-datanetwork-list controller-0", > any problem? > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | > physnet0 | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Nov 4 02:54:01 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 4 Nov 2019 02:54:01 +0000 Subject: [Starlingx-discuss] Layer Build Testing Issue Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627D126@CDSMSX102.ccr.corp.intel.com> Hi Saul When you begin to build distro layer, before downloading mirror for distro layer building, you firstly should add a local repo How to set up a local mirror in build container 1, ensure build output of compile layer, add to lighttpd service $ cd /www/root/htdocs/ $ ls localdisk/loadbuild/// 2, generate tis_pkg.lst in ls /localdisk/loadbuild///, which should be access $ cd /localdisk/loadbuild/// $ ls std/rpmbuild/RPMS/ rt/rpmbuild/RPMS/ -l | awk '/.*\.tis\..*/ {print $9}' > tis_pkg.lst Build distro layer 1, sync code for distro layer $ repo init -u https://opendev.org/starlingx/manifest.git -m distro.xml $ repo sync 2, update these file, because you setup a local repo Stx-tool/centos-mirror-tools/config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo Update this line with your user name and project name for compile layer baseurl=http://127.0.0.1:8088/localdisk/loadbuild///std/rpmbuild/RPMS/ 3, download mirror for distro layer $ download_mirror.sh -n -g -l distro -c config/centos/distro/yum.conf.sample -S Copy download mirror file to mirror folder $ generate-cgcs-centos-repo.sh --layer=distro /import/mirrors/distro $ populate_downloads.sh /import/mirrors/distro 4, Ensure compile built package, with tis named, in distro mirror martin at martin-ecust:~/workspace/starlingx/workspace/localdisk/designer/martin/distro/cgcs-root/cgcs-centos-repo/Binary/x86_64$ ls *.tis.* bash-4.2.46-31.el7.tis.4.x86_64.rpm python-debug-2.7.5-76.el7.tis.4.x86_64.rpm rpm-debuginfo-4.14.0-1.tis.1.x86_64.rpm bash-debuginfo-4.2.46-31.el7.tis.4.x86_64.rpm python-debuginfo-2.7.5-76.el7.tis.4.x86_64.rpm rpm-devel-4.14.0-1.tis.1.x86_64.rpm bash-doc-4.2.46-31.el7.tis.4.x86_64.rpm python-devel-2.7.5-76.el7.tis.4.x86_64.rpm rpm-libs-4.14.0-1.tis.1.x86_64.rpm golang-1.12.10-3.tis.1.x86_64.rpm python-libs-2.7.5-76.el7.tis.4.x86_64.rpm rpm-plugin-systemd-inhibit-4.14.0-1.tis.1.x86_64.rpm golang-bin-1.12.10-3.tis.1.x86_64.rpm python-test-2.7.5-76.el7.tis.4.x86_64.rpm rpm-python-4.14.0-1.tis.1.x86_64.rpm golang-dep-0.5.0-0.tis.x86_64.rpm python-tools-2.7.5-76.el7.tis.4.x86_64.rpm rpm-sign-4.14.0-1.tis.1.x86_64.rpm golang-race-1.12.10-3.tis.1.x86_64.rpm rpm-4.14.0-1.tis.1.x86_64.rpm tkinter-2.7.5-76.el7.tis.4.x86_64.rpm golang-shared-1.12.10-3.tis.1.x86_64.rpm rpm-build-4.14.0-1.tis.1.x86_64.rpm python-2.7.5-76.el7.tis.4.x86_64.rpm rpm-build-libs-4.14.0-1.tis.1.x86_64.rpm 5, build pkgs for distro layer $ build-pkgs For develop process, we have to setup a local repo to emulate cengn mirror change, which is task 35961 and task 35962 for this story. Also after all the patch merged for layer building. Scott and Penny should update cengn. And I currently comment setting in these file, request scott or Penney to update depending on their CENGA setting. cgcs-root/build-tools/build_iso/centos_required_build_layer.cfg stx-tools/centos-mirror-tools/config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo stx-tools/centos-mirror-tools/config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo stx-tools/centos-mirror-tools/config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Friday, November 1, 2019 11:48 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 26 Send Starlingx-discuss mailing list submissions to starlingx-discuss at 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 at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Layer Build Testing Issue (Saul Wold) ---------------------------------------------------------------------- Message: 1 Date: Thu, 31 Oct 2019 16:05:45 -0700 From: Saul Wold To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Layer Build Testing Issue Message-ID: <9685602e-c53f-8a99-1cbf-1d9d2b61c716 at linux.intel.com> Content-Type: text/plain; charset="utf-8"; Format="flowed" Hi Martin: I am continuing to test the layer'ed build, I was able to build compile standalone, and then attempted to build distro in the same build area, but I seem to get a failure in kubernetes package build. See the attached root.log. Thanks Sau! -------------- next part -------------- A non-text attachment was scrubbed... Name: root.log Type: text/x-log Size: 218642 bytes Desc: not available URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 26 ************************************************* From qianjiang at baicells.com Mon Nov 4 03:04:49 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Mon, 04 Nov 2019 11:04:49 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com>, Message-ID: Hi, Ezpeer Sure, did interface-datanetwork-assign for phy-flat, see, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 37e7595c-3d52-4fe0-bb26-12297155b87d | data0 | phy-flat | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月4日(星期一) 10:23 收件人:钱江 抄 送:starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear Qianjiang, From document: #Create a flat datanetwork and bind it to the interface. system datanetwork-add phy-flat flat system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat system host-unlock ${COMPUTE} Do you do interface-datanetwork-assign for phy-flat? Check interface-datanetwork-list first. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年11月1日 週五 下午5:31寫道: Hi, Ezpeer Just follow https://wiki.openstack.org/wiki/StarlingX/Networking --- Configure the flat network. controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print $2}'` controller-0:~$ echo $ADMINID 95794c0fbfe9427b908eedb823aba318 controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'phy-flat' unknown for flat provider network. controller-0:~$ and, [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 5c8391a3-be90-48dd-8df5-2c1118af979a | phy-flat | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ Please Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 16:31 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. --provider-physical-network provider = > incorrect You don't have the physical network named as "provider". Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: Please follow the document's example. https://wiki.openstack.org/wiki/StarlingX/Networking Configure the flat network. 钱江 於 2019年11月1日 週五 下午3:36寫道: But, still failure use type vlan controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 15:27 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Your data0 and data1 are vlan type datanetwork. This is your configuration. system datanetwork-add ${PHYSNET0} vlan system datanetwork-add ${PHYSNET1} vlan 钱江 於 2019年11月1日 週五 下午3:17寫道: You see, "eth1000" and "eth1001" are assigned to datanetwork. [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 14:46 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Your enp2s1 interface is not assigned to any data network? Thanks. BR 钱江 於 2019年11月1日 週五 下午2:35寫道: Hi, Ezpeer Below is the log of "system interface-datanetwork-list controller-0", any problem? [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+--------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+--------+------------------+ | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | physnet0 | | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | physnet1 | +--------------+--------------------------------------+--------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | None | [u'enp2s1'] | [] | [] | MTU=1500 | | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True | | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True | +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月1日(星期五) 10:10 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear QianJiang, Your command is incorrect. Example: [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ 钱江 於 2019年10月31日 週四 下午7:23寫道: Hi, Ezpeer I checked and yes, [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list controller-0 +--------------+--------------------------------------+--------+--------------+ | hostname | uuid | ifname | network_name | +--------------+--------------------------------------+--------+--------------+ | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | oam | | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | mgmt | | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | cluster-host | +--------------+--------------------------------------+--------+--------------+ Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年10月31日(星期四) 18:12 收件人:钱江 抄 送:"Sun, Austin" ; starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear , Do you do the interface-datanetwork-assign ? #system interface-datanetwork-assign controller-0 Reference Doc: https://wiki.openstack.org/wiki/StarlingX/Networking Thanks. BR 钱江 於 2019年10月31日 週四 下午5:28寫道: Hi, Austin I checked, the type_drivers field has no problem. Do you have more ideas? controller-0:~$ grep type_drivers -r /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml type_drivers: flat,vlan,vxlan Best Regard ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 16:42 收件人:钱江 ; starlingx-discuss 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Could you double check ? grep -r type_drivers /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml ? it comes out like ‘type_drivers: flat,vlan,vxlan’, if not , you have to use helm command to override to include flat network. Thanks. BR Austin Sun. From: 钱江 Sent: Thursday, October 31, 2019 4:12 PM To: Sun, Austin ; starlingx-discuss Subject: 回复:[Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, Austin Thanks for your warmhearted. Follow your suggestion, but I still get the same issue. [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 flat +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 3 | | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | | name | enp2s1 | | network_type | flat | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+----------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+----------+--------------+------+ | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | +--------------------------------------+----------+--------------+------+ controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. When I tried type vlan as following, it directed different issue. controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type vlan provider Error while executing command: BadRequestException: 400, Invalid input for operation: physical_network 'provider' unknown for VLAN provider network. ------------------------------------------------------------------ 发件人:Sun, Austin 发送时间:2019年10月31日(星期四) 15:23 收件人:钱江 ; starlingx-discuss 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi QianJiang: The default datanetwork in guide is vlan, you should change it to flat before openstack network create. system datanetwork-add ${PHYSNET0} flat Thanks. BR Austin Sun. From:钱江 Sent: Thursday, October 31, 2019 2:42 PM To: starlingx-discuss Subject: [Starlingx-discuss] openstack network creation failure: Flat provider networks are disabled Hi, the community After installation of "Virtual All-in-one Simplex Installation R2.0", everything goes well except, controller-0:~$ openstack network create --share --external --provider-physical-network provider --provider-network-type flat provider Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. Could anyone help to point out what's the issue, and how to fix it? Best Regard _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 4 03:31:11 2019 From: sgw at linux.intel.com (Saul Wold) Date: Sun, 3 Nov 2019 19:31:11 -0800 Subject: [Starlingx-discuss] Shanghai PTG Agenda In-Reply-To: <6bdce69e-0215-bd30-b080-4312fb0d9bfc@linux.intel.com> References: <2588653EBDFFA34B982FAF00F1B4844EC273E9A2@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F360B272A@SHSMSX104.ccr.corp.intel.com> <6bdce69e-0215-bd30-b080-4312fb0d9bfc@linux.intel.com> Message-ID: <1b97988c-3d36-5c3f-83e2-91e441586b3f@linux.intel.com> On 11/3/19 4:20 PM, Saul Wold wrote: > > > On 11/3/19 3:36 PM, Xie, Cindy wrote: >> Brent, >> >> Welcome to Shanghai! >> >> Do we already have a venue for the PTG? I have several StarlingX China >> customers asking where they shall go. >> > Cindy, yes, there is a schedule for the PTG, the main PTG site is > openstack.org/ptg. > > We are in room 430 both Wednesday and Thursday morning. > Just to clarify, it's ALL Day Wednesday and just Thursday morning Sau! > Sau! > >> Thx. - cindy >> >> *From:* Rowsell, Brent >> *Sent:* Monday, November 4, 2019 5:05 AM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] Shanghai PTG Agenda >> >> Folks, >> >> The current agenda for the PTG meeting can be found here. >> >> https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai >> >> Thanks, >> >> Brent >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From haochuan.z.chen at intel.com Mon Nov 4 05:13:39 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 4 Nov 2019 05:13:39 +0000 Subject: [Starlingx-discuss] patch review for layered build In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15B1736@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85627CD82@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B167F@ALA-MBD.corp.ad.wrs.com> <56829C2A36C2E542B0CCB9854828E4D85627CDA5@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B16E9@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B1736@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627D18A@CDSMSX102.ccr.corp.intel.com> Hi Penney Already find you add two new task, 37337 and 37338. I will update this patch, https://review.opendev.org/#/c/681914/, after your task done. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don Sent: Friday, November 1, 2019 10:56 PM To: Chen, Haochuan Z ; Miller, Frank ; Little, Scott ; Saul Wold ; Wensley, Barton Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build I'll add a task to the story and start working on relocating these repos. From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Friday, November 01, 2019 10:21 AM To: Chen, Haochuan Z; Miller, Frank; Little, Scott; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] patch review for layered build Yes, those contain the build files to which I'm referring. All that content would be moved to the dist cloud repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 10:09 AM To: Penney, Don; Miller, Frank; Little, Scott; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: RE: patch review for layered build What about these two foler. To move distributecloud to flock layer, we should move to other folder. stx/upstream/openstack/distributedcloud stx/upstream/openstack/distributedcloud-client BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don > Sent: Friday, November 1, 2019 9:49 PM To: Chen, Haochuan Z >; Miller, Frank >; Little, Scott >; Saul Wold > Cc: 'starlingx-discuss at lists.starlingx.io' > Subject: RE: patch review for layered build I don't think we need to create anything. In my opinion, we need to drop the "/git" from the paths for these repos in the manifest: https://opendev.org/starlingx/manifest/src/branch/master/default.xml ie. and move the build files from "upstream" to these repos. From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:46 AM To: Miller, Frank; Little, Scott; Penney, Don; Saul Wold Cc: 'starlingx-discuss at lists.starlingx.io' Subject: patch review for layered build Hi Last day on building meeting, I am not clear, for moving distrocloud and distrocloud-client to flock layer, we create a new project to place meta data for these projects or move to any project in flock layer? And you can add more feedback for my reply in patch review comment. https://review.opendev.org/#/c/681900/ https://review.opendev.org/#/c/681854/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/681821/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Nov 4 06:19:03 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 4 Nov 2019 06:19:03 +0000 Subject: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart In-Reply-To: <80ED4CE81E3D8F4099306648E95DAFE453AEA130@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85627B0C2@CDSMSX102.ccr.corp.intel.com> <56829C2A36C2E542B0CCB9854828E4D85627CD67@CDSMSX102.ccr.corp.intel.com> <80ED4CE81E3D8F4099306648E95DAFE453AEA130@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627D1EA@CDSMSX102.ccr.corp.intel.com> Thanks Tee. Hi Bob I think my suggestion will be accepted. And it is align with this item in the spec. Have the platform be application agnostic. It should not contain specific application knowledge Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Ngo, Tee Sent: Friday, November 1, 2019 11:01 PM To: Bailey, Henry Albert (Al) ; Chen, Haochuan Z ; Wang, Jing (Angie) ; Church, Robert Cc: Qi, Mingyuan ; Chen, Tingjie ; 'starlingx-discuss at lists.starlingx.io' Subject: RE: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Martin, Bob designed and implemented the ArmadaManifestOperator and is also a Ceph SME. He's in the best position to provide you feedback on the proposed changes. Tee From: Bailey, Henry Albert (Al) Sent: November-01-19 9:39 AM To: Chen, Haochuan Z; Wang, Jing (Angie); Ngo, Tee; Church, Robert Cc: Qi, Mingyuan; Chen, Tingjie; 'starlingx-discuss at lists.starlingx.io' Subject: RE: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Adding Bob as he may have feedback based on the decoupling spec. https://opendev.org/starlingx/specs/src/branch/master/doc/source/specs/stx-3.0/approved/containerization-2006537-decoupling-container-apps.rst Al From: Chen, Haochuan Z [mailto:haochuan.z.chen at intel.com] Sent: Friday, November 01, 2019 9:30 AM To: Wang, Jing (Angie); Ngo, Tee Cc: Qi, Mingyuan; Chen, Tingjie; 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Have you checked my proposal? Thanks! Martin, Chen SSP, Software Engineer 021-61164330 From: Chen, Haochuan Z Sent: Tuesday, October 29, 2019 3:18 PM To: Wang, Jing (Angie) >; Tee.Ngo at windriver.com Cc: Qi, Mingyuan >; Chen, Tingjie >; 'starlingx-discuss at lists.starlingx.io' > Subject: decouple sysinv-conductor with armada application, request to decouple the way to generate image file with armada chart Hi Angie & Tee Currently decoupling sysinv-conductor with armada application, you introduce new class ArmadaManifestOperator. But I find currently this class only decouple application override. For image list, it still depends on declaration in values.yaml in application's charts. We work to ceph containerization, plan to introduce new charts to launch ceph service. https://review.opendev.org/#/c/681457/ The image declaration in values.yaml is not same as currently application This chart will pull images rook/ceph:v1.1.1, with such way to declare image. https://review.opendev.org/#/c/681457/5/stx-platform-helm/stx-platform-helm/helm-charts/rook-ceph/values.yaml image: prefix: rook repository: rook/ceph tag: v1.1.1 pullPolicy: IfNotPresent So prefer in sysinv-conductor, also use ArmadaManifestOperator to update image list file. Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Mon Nov 4 08:12:37 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 4 Nov 2019 16:12:37 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> Message-ID: Dear Qianjiang, *system host-lock ${COMPUTE} #If the interface has been bound to other datanetwork, need to remove the binding. system interface-datanetwork-list ${COMPUTE} system interface-datanetwork-remove ${PHYSNETDATA0UUID}* #Create a flat datanetwork and bind it to the interface. system datanetwork-add phy-flat flat system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat system host-unlock ${COMPUTE} My Example: [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | uuid | name | class | type | vlan | ports | uses | used | attributes | | | | | | id | | i/f | by | | | | | | | | | | i/f | | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | 5e6ab3c1-ff01-4ca9-b8c3-98984c9ab403 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | a68ceee4-77d7-4ec1-a5f1-bf667b7fa7f7 | enp2s0 | platform | ethernet | None | [u'enp2s0'] | [] | [] | MTU=1500 | | e0b545f0-dc0d-4c6c-9327-0008191cf3e6 | enp3s0 | data | ethernet | None | [u'enp3s0'] | [] | [] | MTU=1500,accelerated= | | | | | | | | | | True | | | | | | | | | | | | fe0be665-6e66-4113-99b3-164374e40b17 | enp98s0f1 | pci-passthrough | ethernet | None | [u'enp98s0f1'] | [] | [] | MTU=1500 | | ffb39ada-ef0a-4a19-87df-9998c5a23e11 | enp98s0f0 | pci-sriov | ethernet | None | [u'enp98s0f0'] | [] | [] | MTU=1500 | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+---------------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+---------------+--------------+------+ | b42f45d1-a474-47cc-b603-8c3b4e50189b | phy-flat | flat | 1500 | | a772f2ee-4f45-4593-9aa2-e9d007b3ebb0 | physnet-pci | flat | 1500 | | 322d1ff6-7446-48b3-810f-47cdde3d8b4a | physnet-sriov | flat | 1500 | +--------------------------------------+---------------+--------------+------+ [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ ============================================================================= controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print $2}'` controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | | | created_at | 2019-11-04T03:22:36Z | | description | | | dns_domain | None | | id | 4916450b-f018-4065-ac7a-bfd1475afe17 | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | Munch({'project': Munch({'domain_name': 'default', 'domain_id': None, 'name': 'admin', 'id': u'9be757c8e5464416b41cd1bcdaca990e'}), 'cloud': 'openstack_helm', 'region_name': 'RegionOne', 'zone': None}) | | mtu | 1500 | | name | netflat | | port_security_enabled | True | | project_id | 9be757c8e5464416b41cd1bcdaca990e | | provider:network_type | flat | | provider:physical_network | phy-flat | | provider:segmentation_id | None | | qos_policy_id | None | | revision_number | 1 | | router:external | Internal | | segments | None | | shared | False | | status | ACTIVE | | subnets | | | tags | | | updated_at | 2019-11-04T03:22:36Z | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ controller-0:~$ >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Mon Nov 4 09:01:13 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 04 Nov 2019 03:01:13 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6t7pph@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191104T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From qianjiang at baicells.com Mon Nov 4 09:21:59 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Mon, 04 Nov 2019 17:21:59 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8muWbng==?= =?utf-8?q?=E5=A4=8D=EF=BC=9A_openstack_network_creation_failure=3A_Flat_p?= =?utf-8?q?rovider_networks_are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> , Message-ID: <8df11cca-69c2-42a8-8c95-b309f07431cf.qianjiang@baicells.com> Ezpeer, Thanks for your support such a long time. This morning, when I retry creating network just as what I did before, It works. Yes, It works!!! But I completely have no idea what I modified, even I suspect I changed nothing but it goes well now. I can not reproduce this issue, I just decided continue my starlingx trip. Anyway, thanks a lot. Best Regard ------------------------------------------------------------------ 发件人:Ezpeer Chen 发送时间:2019年11月4日(星期一) 16:15 收件人:钱江 抄 送:starlingx-discuss 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: Flat provider networks are disabled Dear Qianjiang, system host-lock ${COMPUTE} #If the interface has been bound to other datanetwork, need to remove the binding. system interface-datanetwork-list ${COMPUTE} system interface-datanetwork-remove ${PHYSNETDATA0UUID} #Create a flat datanetwork and bind it to the interface. system datanetwork-add phy-flat flat system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat system host-unlock ${COMPUTE} My Example: [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | uuid | name | class | type | vlan | ports | uses | used | attributes | | | | | | id | | i/f | by | | | | | | | | | | i/f | | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | 5e6ab3c1-ff01-4ca9-b8c3-98984c9ab403 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | a68ceee4-77d7-4ec1-a5f1-bf667b7fa7f7 | enp2s0 | platform | ethernet | None | [u'enp2s0'] | [] | [] | MTU=1500 | | e0b545f0-dc0d-4c6c-9327-0008191cf3e6 | enp3s0 | data | ethernet | None | [u'enp3s0'] | [] | [] | MTU=1500,accelerated= | | | | | | | | | | True | | | | | | | | | | | | fe0be665-6e66-4113-99b3-164374e40b17 | enp98s0f1 | pci-passthrough | ethernet | None | [u'enp98s0f1'] | [] | [] | MTU=1500 | | ffb39ada-ef0a-4a19-87df-9998c5a23e11 | enp98s0f0 | pci-sriov | ethernet | None | [u'enp98s0f0'] | [] | [] | MTU=1500 | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+---------------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+---------------+--------------+------+ | b42f45d1-a474-47cc-b603-8c3b4e50189b | phy-flat | flat | 1500 | | a772f2ee-4f45-4593-9aa2-e9d007b3ebb0 | physnet-pci | flat | 1500 | | 322d1ff6-7446-48b3-810f-47cdde3d8b4a | physnet-sriov | flat | 1500 | +--------------------------------------+---------------+--------------+------+ [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ ============================================================================= controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print $2}'` controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | | | created_at | 2019-11-04T03:22:36Z | | description | | | dns_domain | None | | id | 4916450b-f018-4065-ac7a-bfd1475afe17 | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | Munch({'project': Munch({'domain_name': 'default', 'domain_id': None, 'name': 'admin', 'id': u'9be757c8e5464416b41cd1bcdaca990e'}), 'cloud': 'openstack_helm', 'region_name': 'RegionOne', 'zone': None}) | | mtu | 1500 | | name | netflat | | port_security_enabled | True | | project_id | 9be757c8e5464416b41cd1bcdaca990e | | provider:network_type | flat | | provider:physical_network | phy-flat | | provider:segmentation_id | None | | qos_policy_id | None | | revision_number | 1 | | router:external | Internal | | segments | None | | shared | False | | status | ACTIVE | | subnets | | | tags | | | updated_at | 2019-11-04T03:22:36Z | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ controller-0:~$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Mon Nov 4 11:43:08 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Mon, 4 Nov 2019 17:13:08 +0530 Subject: [Starlingx-discuss] Reg. OpenStack components in StarlingX all-in-one simplex Message-ID: Hello all, I have installed StarlingX all-in-one simplex. When i open Horizon page, I didn't get compute, volumes,etc. in GUI page. and there is no option in " Add images/Vm's ". Can any one confirm, All-in-one simplex is supported with Compute and adding the images or not and Is this services are included in StarlingX all-in-one simplex architecture? -- Thanks & Regards Sai Chandu Behara From saichandu.behara at calsoftinc.com Mon Nov 4 11:43:38 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Mon, 4 Nov 2019 17:13:38 +0530 Subject: [Starlingx-discuss] Error while installing StarlingX Openstack on all-in-one simplex Message-ID: Hello all, I am trying to install StarlingX OpenStack on all-in-one simplex . When i am installing application manifest and helm-charts, getting some versioning error. I downloaded Package from " http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.0/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz " and "http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz " ( Both are getting errors ). I'm trying to upload the package by using command " system application-upload stx-openstack-1.0-17-centos-stable-latest.tgz " +---------------+----------------------------------+ | Property | Value | +---------------+----------------------------------+ | active | False | | app_version | 1.0-17-centos-stable-latest | | created_at | 2019-11-04T11:05:19.899672+00:00 | | manifest_file | stx-openstack.yaml | | manifest_name | armada-manifest | | name | stx-openstack | | progress | None | | status | uploading | | updated_at | None | +---------------+----------------------------------+ and when i checking the application list, getting upload failed. +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | *| stx-openstack | 1.0-17-centos-stable- | armada-manifest | stx-openstack. | **upload-failed**| Upload of application stx-openstack (1. |** **| | latest | | yaml | | 0-17-centos-stable-latest) failed: |** **| | | | | | Unsupported application version. * | | | | | | | | +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ If anyone is aware of this issue, please let us know. It would be a great help. -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezpeerchen at gmail.com Mon Nov 4 03:31:26 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 4 Nov 2019 11:31:26 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> Message-ID: Dear Qianjiang, My Example: [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list controller-0 +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | uuid | name | class | type | vlan | ports | uses | used | attributes | | | | | | id | | i/f | by | | | | | | | | | | i/f | | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ | 5e6ab3c1-ff01-4ca9-b8c3-98984c9ab403 | lo | platform | virtual | None | [] | [] | [] | MTU=1500 | | a68ceee4-77d7-4ec1-a5f1-bf667b7fa7f7 | enp2s0 | platform | ethernet | None | [u'enp2s0'] | [] | [] | MTU=1500 | | e0b545f0-dc0d-4c6c-9327-0008191cf3e6 | enp3s0 | data | ethernet | None | [u'enp3s0'] | [] | [] | MTU=1500,accelerated= | | | | | | | | | | True | | | | | | | | | | | | fe0be665-6e66-4113-99b3-164374e40b17 | enp98s0f1 | pci-passthrough | ethernet | None | [u'enp98s0f1'] | [] | [] | MTU=1500 | | ffb39ada-ef0a-4a19-87df-9998c5a23e11 | enp98s0f0 | pci-sriov | ethernet | None | [u'enp98s0f0'] | [] | [] | MTU=1500 | +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ [sysadmin at controller-0 ~(keystone_admin)]$ [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list +--------------------------------------+---------------+--------------+------+ | uuid | name | network_type | mtu | +--------------------------------------+---------------+--------------+------+ | b42f45d1-a474-47cc-b603-8c3b4e50189b | phy-flat | flat | 1500 | | a772f2ee-4f45-4593-9aa2-e9d007b3ebb0 | physnet-pci | flat | 1500 | | 322d1ff6-7446-48b3-810f-47cdde3d8b4a | physnet-sriov | flat | 1500 | +--------------------------------------+---------------+--------------+------+ [sysadmin at controller-0 ~(keystone_admin)]$ system interface-datanetwork-list controller-0 +--------------+--------------------------------------+-----------+------------------+ | hostname | uuid | ifname | datanetwork_name | +--------------+--------------------------------------+-----------+------------------+ | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | physnet-pci | | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | phy-flat | | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | physnet-sriov | +--------------+--------------------------------------+-----------+------------------+ ============================================================================= controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print $2}'` controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | admin_state_up | UP | | availability_zone_hints | | | availability_zones | | | created_at | 2019-11-04T03:22:36Z | | description | | | dns_domain | None | | id | 4916450b-f018-4065-ac7a-bfd1475afe17 | | ipv4_address_scope | None | | ipv6_address_scope | None | | is_default | False | | is_vlan_transparent | False | | location | Munch({'project': Munch({'domain_name': 'default', 'domain_id': None, 'name': 'admin', 'id': u'9be757c8e5464416b41cd1bcdaca990e'}), 'cloud': 'openstack_helm', 'region_name': 'RegionOne', 'zone': None}) | | mtu | 1500 | | name | netflat | | port_security_enabled | True | | project_id | 9be757c8e5464416b41cd1bcdaca990e | | provider:network_type | flat | | provider:physical_network | phy-flat | | provider:segmentation_id | None | | qos_policy_id | None | | revision_number | 1 | | router:external | Internal | | segments | None | | shared | False | | status | ACTIVE | | subnets | | | tags | | | updated_at | 2019-11-04T03:22:36Z | +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ controller-0:~$ 钱江 於 2019年11月4日 週一 上午11:04寫道: > Hi, Ezpeer > > Sure, did interface-datanetwork-assign for phy-flat, see, > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 37e7595c-3d52-4fe0-bb26-12297155b87d | data0 | > phy-flat | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月4日(星期一) 10:23 > 收件人:钱江 > 抄 送:starlingx-discuss > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear Qianjiang, > > From document: > > #Create a flat datanetwork and bind it to the interface. > system datanetwork-add phy-flat flat > system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} > system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat > system host-unlock ${COMPUTE} > > > > Do you do interface-datanetwork-assign for phy-flat? > > Check interface-datanetwork-list first. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > 钱江 於 2019年11月1日 週五 下午5:31寫道: > Hi, Ezpeer > Just follow https://wiki.openstack.org/wiki/StarlingX/Networking > --- Configure the flat network. > > controller-0:~$ export OS_CLOUD=openstack_helm > controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print > $2}'` > controller-0:~$ echo $ADMINID > 95794c0fbfe9427b908eedb823aba318 > controller-0:~$ openstack network create --project ${ADMINID} > --provider-network-type=flat --provider-physical-network=phy-flat netflat > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'phy-flat' unknown for flat provider network. > controller-0:~$ > > and, > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 5c8391a3-be90-48dd-8df5-2c1118af979a | phy-flat | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > Please > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 16:31 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > * --provider-physical-network provider * = > incorrect > > You don't have the physical network named as "provider". > > > Please follow the document's example. > https://wiki.openstack.org/wiki/StarlingX/Networking > > Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: > Please follow the document's example. > https://wiki.openstack.org/wiki/StarlingX/Networking > > > - Configure the flat network. > > > 钱江 於 2019年11月1日 週五 下午3:36寫道: > But, still failure use type vlan > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 15:27 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Your data0 and data1 are vlan type datanetwork. > > > This is your configuration. > > system datanetwork-add ${PHYSNET0} vlan > system datanetwork-add ${PHYSNET1} vlan > > > 钱江 於 2019年11月1日 週五 下午3:17寫道: > You see, "eth1000" and "eth1001" are assigned to datanetwork. > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 14:46 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > Your enp2s1 interface is not assigned to any data network? > > > > Thanks. > > BR > > 钱江 於 2019年11月1日 週五 下午2:35寫道: > Hi, Ezpeer > > Below is the log of "system interface-datanetwork-list controller-0", > any problem? > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+--------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+--------+------------------+ > | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | > physnet0 | > | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | > physnet1 | > > +--------------+--------------------------------------+--------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | uuid | name | class | type | > vlan id | ports | uses i/f | used by i/f | attributes > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | > None | [] | [] | [] | MTU=1500 > | > | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | > None | [u'enp2s1'] | [] | [] | MTU=1500 > | > | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | > None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True > | > | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | > None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True > | > > +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年11月1日(星期五) 10:10 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear QianJiang, > > Your command is incorrect. > > Example: > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > > 钱江 於 2019年10月31日 週四 下午7:23寫道: > Hi, Ezpeer > > I checked and yes, > [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list > controller-0 > > +--------------+--------------------------------------+--------+--------------+ > | hostname | uuid | ifname | > network_name | > > +--------------+--------------------------------------+--------+--------------+ > | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | > oam | > | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | > mgmt | > | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | > cluster-host | > > +--------------+--------------------------------------+--------+--------------+ > > Best Regard > > ------------------------------------------------------------------ > 发件人:Ezpeer Chen > 发送时间:2019年10月31日(星期四) 18:12 > 收件人:钱江 > 抄 送:"Sun, Austin" ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: > Flat provider networks are disabled > > Dear , > > Do you do the interface-datanetwork-assign ? > > #system interface-datanetwork-assign controller-0 > > > > Reference Doc: > https://wiki.openstack.org/wiki/StarlingX/Networking > > > > Thanks. > > BR > > 钱江 於 2019年10月31日 週四 下午5:28寫道: > Hi, Austin > > I checked, the type_drivers field has no problem. Do you have more > ideas? > > controller-0:~$ grep type_drivers -r > /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml > > type_drivers: flat,vlan,vxlan > > Best Regard > > ------------------------------------------------------------------ > 发件人:Sun, Austin > 发送时间:2019年10月31日(星期四) 16:42 > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Could you double check ? > > grep -r type_drivers > /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml > ? > > > > it comes out like ‘type_drivers: flat,vlan,vxlan’, > > if not , you have to use helm command to override to include flat network. > > > > Thanks. > > BR > Austin Sun. > > > > *From:* 钱江 > *Sent:* Thursday, October 31, 2019 4:12 PM > *To:* Sun, Austin ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: > Flat provider networks are disabled > > > > Hi, Austin > > > > Thanks for your warmhearted. > > Follow your suggestion, but I still get the same issue. > > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 > flat > +--------------+--------------------------------------+ > | Property | Value | > +--------------+--------------------------------------+ > | id | 3 | > | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | > | name | enp2s1 | > | network_type | flat | > | mtu | 1500 | > | description | None | > +--------------+--------------------------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > +--------------------------------------+----------+--------------+------+ > | uuid | name | network_type | mtu | > +--------------------------------------+----------+--------------+------+ > | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | > | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | > | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | > +--------------------------------------+----------+--------------+------+ > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > When I tried type vlan as following, it directed different issue. > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type vlan provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: physical_network 'provider' unknown for VLAN provider network. > > > > ------------------------------------------------------------------ > > 发件人:Sun, Austin > > 发送时间:2019年10月31日(星期四) 15:23 > > 收件人:钱江 ; starlingx-discuss < > starlingx-discuss at lists.starlingx.io> > > 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > Hi QianJiang: > > The default datanetwork in guide is vlan, you should change it to flat > before openstack network create. > > > > system datanetwork-add ${PHYSNET0} flat > > > > Thanks. > > BR > Austin Sun. > > From:钱江 > *Sent:* Thursday, October 31, 2019 2:42 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] openstack network creation failure: Flat > provider networks are disabled > > > > > > Hi, the community > > > > After installation of "Virtual All-in-one Simplex Installation R2.0 > ", > everything goes well except, > > > > controller-0:~$ openstack network create --share --external > --provider-physical-network provider --provider-network-type flat provider > Error while executing command: BadRequestException: 400, Invalid input for > operation: Flat provider networks are disabled. > > > > Could anyone help to point out what's the issue, and how to fix it? > > > > Best Regard > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Mon Nov 4 03:32:25 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 4 Nov 2019 03:32:25 +0000 Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627D0FD@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627D0FD@CDSMSX102.ccr.corp.intel.com> Message-ID: Hi, Image service is ready to use, but the issue is that it is installed inside docker container which I feel is not accessible from external source. controller-0:~$ openstack endpoint list | grep glance | 55b3d034819f4cecb8650779df6c543d | RegionOne | glance | image | True | internal | http://glance-api.openstack.svc.cluster.local:9292/ | | a40b33d549bb4cac96f00ceb820aabb5 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ | | c60c2fa05b94472d8c0e29aabced774b | RegionOne | glance | image | True | admin | http://glance-api.openstack.svc.cluster.local:9292/ I think that the public endpoint http://glance.openstack.svc.cluster.local:80 is not accessible from outside. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#configure-helm-endpoint-domain Similar is the case for every service. Regards Anirudh Gupta -----Original Message----- From: Chen, Haochuan Z Sent: 04 November 2019 07:38 To: Anirudh Gupta Cc: starlingx-discuss at lists.starlingx.io Subject: Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Hi Anirudh Maybe you can check in this way to ensure image service is ready firstly. $ export OS_CLOUD=openstack_helm $ openstack endpoint list BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Sunday, November 3, 2019 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 35 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=3eG1Ca5bMgCpxKGy%2F9Vk9kKvatId0xjqz6YkkeQOx8E%3D&reserved=0 or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Canceled: Weekly StarlingX Test meeting - 9:00Pacific time (Cabrales, Ada) 2. Starlingx 2.0 Service Endpoints not publicly accessed from External Entities (Anirudh Gupta) 3. StarlingX platform-integ-apps docker images (cristopher.j.lemus.contreras at intel.com) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Nov 2019 22:45:35 +0000 From: "Cabrales, Ada" To: "starlingx-discuss at lists.starlingx.io" Cc: "Martinez Monroy, Elio" , "'Seiler, Glenn'" , "Hernandez Gonzalez, Fernando" , "'Komiyama, Takeo'" , "Xu, YizhouX" , "Armstrong, Robert H" , "Martinez Landa, Hayde" , "Alonso, Juan Carlos" , 'Peng Tan' , "Gomez, Juan P" , "Sun, Austin" , Banszel Martin Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting - 9:00Pacific time Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94 at FMSMSX114.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Updates will be requested offline Weekly meetings on Tuesdays at 9am Pacific * Zoom link: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F342730236&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UqST7HL4GAjPpXlyt9Bx1uxTORAU945uMr%2F9VBuqwWM%3D&reserved=0 o 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://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fu%2Fed95sU7aQ&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=4ZjWIMiKjPTFOA%2BENxYwMDSCQbD64GbpXfC46LbalX0%3D&reserved=0 Agenda and meeting minutes: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fetherpad.openstack.org%2Fp%2Fstx-test&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UfJsFkKFIkGrcBDJBxn%2FXaUVNCLmlcwXXYMzf1a7YEQ%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3486 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Sat, 2 Nov 2019 21:04:08 +0000 From: Anirudh Gupta To: "starlingx-discuss at lists.starlingx.io" , "starlingx-discuss-owner at lists.starlingx.io" Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Message-ID: Content-Type: text/plain; charset="utf-8" Hi Team, I am trying to integrate StarlingX 2.0 with Open Source Mano 6.0, but facing errors as the public endpoints for every services are not exposed. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeploy_install_guides%2Fr2_release%2Fopenstack%2Faccess.html%23configure-helm-endpoint-domain&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=sWOsa5YN8H8Tpw%2FjAU%2FJqLNtdrsPlBR4kYt0szC3sak%3D&reserved=0 I am getting error 503 code: 503\\n description: 'VIM Exception vimconnUnexpectedResponse EndpointNotFound: public\\n endpoint for image service not found However this was not the case with StarlingX previous release 2018.10. I had successfully integrated it. This is because now the openstack services are now containerized and URL is not publicly exposed. Can someone please update the steps in order to expose all services public endpoints outside StarlingX. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Sun, 03 Nov 2019 02:50:11 -0600 From: cristopher.j.lemus.contreras at intel.com To: Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6t0227 at fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191103T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711498181&sdata=bEJTXZe41hnithU8mgFdzin57Q5fvOiNUjeNwSDiH8w%3D&reserved=0 ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 35 ************************************************* 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. From ezpeerchen at gmail.com Mon Nov 4 03:37:45 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Mon, 4 Nov 2019 11:37:45 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIG9wZW5z?= =?utf-8?q?tack_network_creation_failure=3A_Flat_provider_networks_?= =?utf-8?q?are_disabled?= In-Reply-To: References: <2983e363-d94e-4be4-b485-25dca51a043e.qianjiang@baicells.com> <8922b93d-517c-44a3-a2c6-52df0c49221d.qianjiang@baicells.com> <9f5f4b57-3501-476b-be58-d2cb6ab7c6dd.qianjiang@baicells.com> <4676ed27-458f-4f38-9b4c-869a1b97d323.qianjiang@baicells.com> <1180d1e3-c868-499b-ae7e-60de13fd2fb9.qianjiang@baicells.com> <98c86c89-0a1b-4644-84f8-b5cc2489ab09.qianjiang@baicells.com> Message-ID: Dear Qianjiang, *system host-lock ${COMPUTE} #If the interface has been bound to other datanetwork, need to remove the binding. system interface-datanetwork-list ${COMPUTE} system interface-datanetwork-remove ${PHYSNETDATA0UUID}* #Create a flat datanetwork and bind it to the interface. system datanetwork-add phy-flat flat system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat system host-unlock ${COMPUTE} Ezpeer Chen 於 2019年11月4日 週一 上午11:31寫道: > Dear Qianjiang, > > My Example: > > [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list > controller-0 > > +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ > | uuid | name | class | > type | vlan | ports | uses | used | attributes | > | | | | > | id | | i/f | by | | > | | | | > | | | | i/f | | > > +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ > | 5e6ab3c1-ff01-4ca9-b8c3-98984c9ab403 | lo | platform | > virtual | None | [] | [] | [] | MTU=1500 | > | a68ceee4-77d7-4ec1-a5f1-bf667b7fa7f7 | enp2s0 | platform | > ethernet | None | [u'enp2s0'] | [] | [] | MTU=1500 | > | e0b545f0-dc0d-4c6c-9327-0008191cf3e6 | enp3s0 | data | > ethernet | None | [u'enp3s0'] | [] | [] | MTU=1500,accelerated= | > | | | | > | | | | | True | > | | | | > | | | | | | > | fe0be665-6e66-4113-99b3-164374e40b17 | enp98s0f1 | pci-passthrough | > ethernet | None | [u'enp98s0f1'] | [] | [] | MTU=1500 | > | ffb39ada-ef0a-4a19-87df-9998c5a23e11 | enp98s0f0 | pci-sriov | > ethernet | None | [u'enp98s0f0'] | [] | [] | MTU=1500 | > > +--------------------------------------+-----------+-----------------+----------+------+----------------+------+------+-----------------------+ > [sysadmin at controller-0 ~(keystone_admin)]$ > > > [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list > > +--------------------------------------+---------------+--------------+------+ > | uuid | name | network_type | > mtu | > > +--------------------------------------+---------------+--------------+------+ > | b42f45d1-a474-47cc-b603-8c3b4e50189b | phy-flat | flat | > 1500 | > | a772f2ee-4f45-4593-9aa2-e9d007b3ebb0 | physnet-pci | flat | > 1500 | > | 322d1ff6-7446-48b3-810f-47cdde3d8b4a | physnet-sriov | flat | > 1500 | > > +--------------------------------------+---------------+--------------+------+ > > [sysadmin at controller-0 ~(keystone_admin)]$ system > interface-datanetwork-list controller-0 > > +--------------+--------------------------------------+-----------+------------------+ > | hostname | uuid | ifname | > datanetwork_name | > > +--------------+--------------------------------------+-----------+------------------+ > | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | > physnet-pci | > | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | > phy-flat | > | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | > physnet-sriov | > > +--------------+--------------------------------------+-----------+------------------+ > > > ============================================================================= > > > controller-0:~$ export OS_CLOUD=openstack_helm > controller-0:~$ ADMINID=`openstack project list | grep admin | awk '{print > $2}'` > controller-0:~$ openstack network create --project ${ADMINID} > --provider-network-type=flat --provider-physical-network=phy-flat netflat > > +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | Field | Value > > > | > > +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > | admin_state_up | UP > > > | > | availability_zone_hints | > > > | > | availability_zones | > > > | > | created_at | 2019-11-04T03:22:36Z > > > | > | description | > > > | > | dns_domain | None > > > | > | id | 4916450b-f018-4065-ac7a-bfd1475afe17 > > > | > | ipv4_address_scope | None > > > | > | ipv6_address_scope | None > > > | > | is_default | False > > > | > | is_vlan_transparent | False > > > | > | location | Munch({'project': Munch({'domain_name': > 'default', 'domain_id': None, 'name': 'admin', 'id': > u'9be757c8e5464416b41cd1bcdaca990e'}), 'cloud': 'openstack_helm', > 'region_name': 'RegionOne', 'zone': None}) | > | mtu | 1500 > > > | > | name | netflat > > > | > | port_security_enabled | True > > > | > | project_id | 9be757c8e5464416b41cd1bcdaca990e > > > | > | provider:network_type | flat > > > | > | provider:physical_network | phy-flat > > > | > | provider:segmentation_id | None > > > | > | qos_policy_id | None > > > | > | revision_number | 1 > > > | > | router:external | Internal > > > | > | segments | None > > > | > | shared | False > > > | > | status | ACTIVE > > > | > | subnets | > > > | > | tags | > > > | > | updated_at | 2019-11-04T03:22:36Z > > > | > > +---------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ > controller-0:~$ > > > 钱江 於 2019年11月4日 週一 上午11:04寫道: > >> Hi, Ezpeer >> >> Sure, did interface-datanetwork-assign for phy-flat, see, >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+--------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+--------+------------------+ >> | controller-0 | 37e7595c-3d52-4fe0-bb26-12297155b87d | data0 | >> phy-flat | >> | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | >> physnet1 | >> >> +--------------+--------------------------------------+--------+------------------+ >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list >> controller-0 >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | uuid | name | class | type | >> vlan id | ports | uses i/f | used by i/f | attributes >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | >> None | [] | [] | [] | MTU=1500 >> | >> | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | >> None | [u'enp2s1'] | [] | [] | MTU=1500 >> | >> | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | >> None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True >> | >> | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | >> None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月4日(星期一) 10:23 >> 收件人:钱江 >> 抄 送:starlingx-discuss >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Dear Qianjiang, >> >> From document: >> >> #Create a flat datanetwork and bind it to the interface. >> system datanetwork-add phy-flat flat >> system host-if-modify -m 1500 -n data0 -c data ${COMPUTE} ${DATA0IFUUID} >> system interface-datanetwork-assign ${COMPUTE} ${DATA0IFUUID} phy-flat >> system host-unlock ${COMPUTE} >> >> >> >> Do you do interface-datanetwork-assign for phy-flat? >> >> Check interface-datanetwork-list first. >> >> Example: >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+-----------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+-----------+------------------+ >> | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | >> physnet-pci | >> | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | >> phy-flat | >> | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | >> physnet-sriov | >> >> +--------------+--------------------------------------+-----------+------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ >> >> >> 钱江 於 2019年11月1日 週五 下午5:31寫道: >> Hi, Ezpeer >> Just follow https://wiki.openstack.org/wiki/StarlingX/Networking >> --- Configure the flat network. >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> controller-0:~$ ADMINID=`openstack project list | grep admin | awk >> '{print $2}'` >> controller-0:~$ echo $ADMINID >> 95794c0fbfe9427b908eedb823aba318 >> controller-0:~$ openstack network create --project ${ADMINID} >> --provider-network-type=flat --provider-physical-network=phy-flat netflat >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'phy-flat' unknown for flat provider >> network. >> controller-0:~$ >> >> and, >> [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list >> +--------------------------------------+----------+--------------+------+ >> | uuid | name | network_type | mtu | >> +--------------------------------------+----------+--------------+------+ >> | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | >> | 5c8391a3-be90-48dd-8df5-2c1118af979a | phy-flat | flat | 1500 | >> | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | >> | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | >> +--------------------------------------+----------+--------------+------+ >> >> Please >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 16:31 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type vlan provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'provider' unknown for VLAN provider >> network. >> >> >> * --provider-physical-network provider * = > incorrect >> >> You don't have the physical network named as "provider". >> >> >> Please follow the document's example. >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> Ezpeer Chen 於 2019年11月1日 週五 下午3:50寫道: >> Please follow the document's example. >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> >> - Configure the flat network. >> >> >> 钱江 於 2019年11月1日 週五 下午3:36寫道: >> But, still failure use type vlan >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type vlan provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'provider' unknown for VLAN provider >> network. >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 15:27 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Your data0 and data1 are vlan type datanetwork. >> >> >> This is your configuration. >> >> system datanetwork-add ${PHYSNET0} vlan >> system datanetwork-add ${PHYSNET1} vlan >> >> >> 钱江 於 2019年11月1日 週五 下午3:17寫道: >> You see, "eth1000" and "eth1001" are assigned to datanetwork. >> [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list >> controller-0 >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | uuid | name | class | type | >> vlan id | ports | uses i/f | used by i/f | attributes >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | >> None | [] | [] | [] | MTU=1500 >> | >> | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | >> None | [u'enp2s1'] | [] | [] | MTU=1500 >> | >> | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | >> None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True >> | >> | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | >> None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 14:46 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Do you do the interface-datanetwork-assign ? >> >> #system interface-datanetwork-assign controller-0 >> >> >> >> Reference Doc: >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> >> Your enp2s1 interface is not assigned to any data network? >> >> >> >> Thanks. >> >> BR >> >> 钱江 於 2019年11月1日 週五 下午2:35寫道: >> Hi, Ezpeer >> >> Below is the log of "system interface-datanetwork-list controller-0", >> any problem? >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+--------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+--------+------------------+ >> | controller-0 | 4dc1a3d0-cf0e-478e-b936-f8489d26ae69 | data0 | >> physnet0 | >> | controller-0 | 5a6763ae-0720-44b4-aa30-645974d9daa8 | data1 | >> physnet1 | >> >> +--------------+--------------------------------------+--------+------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ system host-if-list >> controller-0 >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | uuid | name | class | type | >> vlan id | ports | uses i/f | used by i/f | attributes >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> | 0531b618-2628-4545-9ea0-904e73047b8e | lo | platform | virtual | >> None | [] | [] | [] | MTU=1500 >> | >> | 9de81b86-afc6-4918-a8f9-d740c343232b | enp2s1 | platform | ethernet | >> None | [u'enp2s1'] | [] | [] | MTU=1500 >> | >> | cf96be60-b1aa-4669-87a8-90ca5c2ecb49 | data1 | data | ethernet | >> None | [u'eth1001'] | [] | [] | MTU=1500,accelerated=True >> | >> | db89ae12-c519-476f-a09a-2da262ac47eb | data0 | data | ethernet | >> None | [u'eth1000'] | [] | [] | MTU=1500,accelerated=True >> | >> >> +--------------------------------------+--------+----------+----------+---------+--------------+----------+-------------+---------------------------+ >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年11月1日(星期五) 10:10 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Dear QianJiang, >> >> Your command is incorrect. >> >> Example: >> [sysadmin at controller-0 ~(keystone_admin)]$ system >> interface-datanetwork-list controller-0 >> >> +--------------+--------------------------------------+-----------+------------------+ >> | hostname | uuid | ifname | >> datanetwork_name | >> >> +--------------+--------------------------------------+-----------+------------------+ >> | controller-0 | 13e47f32-e9a4-4a33-9bc0-63c96e32bfb0 | enp98s0f1 | >> physnet-pci | >> | controller-0 | 6be1d6c2-01c2-45de-a319-4a6337375f7b | enp3s0 | >> phy-flat | >> | controller-0 | f4d817b4-97ca-40e2-a1df-7ef8d0640937 | enp98s0f0 | >> physnet-sriov | >> >> +--------------+--------------------------------------+-----------+------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ >> >> >> >> 钱江 於 2019年10月31日 週四 下午7:23寫道: >> Hi, Ezpeer >> >> I checked and yes, >> [sysadmin at controller-0 ~(keystone_admin)]$ system interface-network-list >> controller-0 >> >> +--------------+--------------------------------------+--------+--------------+ >> | hostname | uuid | ifname | >> network_name | >> >> +--------------+--------------------------------------+--------+--------------+ >> | controller-0 | 2a17737a-bd4c-40fe-bbe7-163237109ed7 | enp2s1 | >> oam | >> | controller-0 | 33472810-e1b3-44fa-9a30-cda0d73bc296 | lo | >> mgmt | >> | controller-0 | 3ae75daf-b22f-47d9-bc48-5086f700563d | lo | >> cluster-host | >> >> +--------------+--------------------------------------+--------+--------------+ >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Ezpeer Chen >> 发送时间:2019年10月31日(星期四) 18:12 >> 收件人:钱江 >> 抄 送:"Sun, Austin" ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:Re: [Starlingx-discuss] 回复:回复: openstack network creation failure: >> Flat provider networks are disabled >> >> Dear , >> >> Do you do the interface-datanetwork-assign ? >> >> #system interface-datanetwork-assign controller-0 >> >> >> >> Reference Doc: >> https://wiki.openstack.org/wiki/StarlingX/Networking >> >> >> >> Thanks. >> >> BR >> >> 钱江 於 2019年10月31日 週四 下午5:28寫道: >> Hi, Austin >> >> I checked, the type_drivers field has no problem. Do you have more >> ideas? >> >> controller-0:~$ grep type_drivers -r >> /scratch/apps/stx-openstack/1.0-18-centos-stable-latest/charts/neutron/values.yaml >> >> type_drivers: flat,vlan,vxlan >> >> Best Regard >> >> ------------------------------------------------------------------ >> 发件人:Sun, Austin >> 发送时间:2019年10月31日(星期四) 16:42 >> 收件人:钱江 ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> 主 题:RE: 回复:[Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> Could you double check ? >> >> grep -r type_drivers >> /scratch/apps/stx-openstack/{app-version}-centos-stable-latest/charts/neutron/values.yaml >> ? >> >> >> >> it comes out like ‘type_drivers: flat,vlan,vxlan’, >> >> if not , you have to use helm command to override to include flat >> network. >> >> >> >> Thanks. >> >> BR >> Austin Sun. >> >> >> >> *From:* 钱江 >> *Sent:* Thursday, October 31, 2019 4:12 PM >> *To:* Sun, Austin ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> *Subject:* 回复:[Starlingx-discuss] openstack network creation failure: >> Flat provider networks are disabled >> >> >> >> Hi, Austin >> >> >> >> Thanks for your warmhearted. >> >> Follow your suggestion, but I still get the same issue. >> >> >> >> [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-add enp2s1 >> flat >> +--------------+--------------------------------------+ >> | Property | Value | >> +--------------+--------------------------------------+ >> | id | 3 | >> | uuid | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | >> | name | enp2s1 | >> | network_type | flat | >> | mtu | 1500 | >> | description | None | >> +--------------+--------------------------------------+ >> [sysadmin at controller-0 ~(keystone_admin)]$ system datanetwork-list >> +--------------------------------------+----------+--------------+------+ >> | uuid | name | network_type | mtu | >> +--------------------------------------+----------+--------------+------+ >> | 7b999f8b-05fe-4c44-9742-907e4551d9b7 | enp2s1 | flat | 1500 | >> | 15eeb861-6910-4254-bb79-847bcbd88ed7 | physnet0 | vlan | 1500 | >> | ad22c935-51a9-4823-9b55-f18df57e5982 | physnet1 | vlan | 1500 | >> +--------------------------------------+----------+--------------+------+ >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type flat provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: Flat provider networks are disabled. >> >> >> >> When I tried type vlan as following, it directed different issue. >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type vlan provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: physical_network 'provider' unknown for VLAN provider >> network. >> >> >> >> ------------------------------------------------------------------ >> >> 发件人:Sun, Austin >> >> 发送时间:2019年10月31日(星期四) 15:23 >> >> 收件人:钱江 ; starlingx-discuss < >> starlingx-discuss at lists.starlingx.io> >> >> 主 题:Re: [Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> Hi QianJiang: >> >> The default datanetwork in guide is vlan, you should change it to flat >> before openstack network create. >> >> >> >> system datanetwork-add ${PHYSNET0} flat >> >> >> >> Thanks. >> >> BR >> Austin Sun. >> >> From:钱江 >> *Sent:* Thursday, October 31, 2019 2:42 PM >> *To:* starlingx-discuss >> *Subject:* [Starlingx-discuss] openstack network creation failure: Flat >> provider networks are disabled >> >> >> >> >> >> Hi, the community >> >> >> >> After installation of "Virtual All-in-one Simplex Installation R2.0 >> ", >> everything goes well except, >> >> >> >> controller-0:~$ openstack network create --share --external >> --provider-physical-network provider --provider-network-type flat provider >> Error while executing command: BadRequestException: 400, Invalid input >> for operation: Flat provider networks are disabled. >> >> >> >> Could anyone help to point out what's the issue, and how to fix it? >> >> >> >> Best Regard >> >> >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> >> >> >> >> >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Nov 4 08:00:47 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 4 Nov 2019 00:00:47 -0800 Subject: [Starlingx-discuss] Slides for Update Message-ID: Folks, Particularly TSC and Release Planning folks, please do a once over on these slides, it would be great to get a few more words around the Distributed Cloud on slide 8. Shuquan and I will deliver this tomorrow morning at 9:00am in Shanghai, so most NA folks should have all day Monday to review this. Thanks Shuquan and Sau! -------------- next part -------------- A non-text attachment was scrubbed... Name: StarlingX Project Update_2019_11.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1469167 bytes Desc: not available URL: From Anirudh.Gupta at hsc.com Mon Nov 4 11:18:43 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 4 Nov 2019 11:18:43 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Message-ID: Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Nov 4 13:46:12 2019 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 4 Nov 2019 13:46:12 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Nov 4 13:46:56 2019 From: yong.hu at intel.com (Hu, Yong) Date: Mon, 4 Nov 2019 13:46:56 +0000 Subject: [Starlingx-discuss] StarlingX Distro-OpenStack: Bi-weekly Project Meeting Message-ID: When: Occurs on Tuesday every other week from 10:00 PM to 10:30 PM effective 11/5/2019 until 5/19/2020. (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi Where: https://zoom.us/j/342730236 *~*~*~*~*~*~*~*~*~* Hi folks, This is a new series of bi-weekly project meeting on StarlingX Distro-OpenStack. Your participation to this meeting and/or other offline contribution by all means are highly appreciated! Join the meeting: https://zoom.us/j/342730236 Project Team Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings PS: from now to next summer early, we are going to keep this time slot to accommodate US standard time (6:00 AM in the morning). regards, Yong Hu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2247 bytes Desc: not available URL: From yong.hu at intel.com Mon Nov 4 13:56:27 2019 From: yong.hu at intel.com (Yong Hu) Date: Mon, 4 Nov 2019 21:56:27 +0800 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> Message-ID: <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> Hi Christopher, A quick question, were we using this image "cirros-0.4.0-x86_64-disk.qcow2" for the previous versions of StarlingX? In addition, @Zhipeng, we might get this image to dig out the root-cause further. Regards, Yong On 2019/11/2 4:53 AM, Lemus Contreras, Cristopher J wrote: > Hello, > > Using the EB that Zhipeng provided, and replacing > “cirros-0.4.0-x86_64-disk.qcow2” with “cirros-0.4.0-x86_64-disk.img”, > Sanity status is Green. > > *AIO – Simplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  49 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 61 TCs PASS ] > > *AIO – Duplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  52 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 64 TCs PASS ] > > *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 PASS ] > > *Standard - 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 PASS ] > > =========================================== > > Just the cirros image was replaced. Centos file is still a .qcow2. > > Please, let me know if you need further details. > > Thanks & Regards, > > Cristopher Lemus > > *From: *"Liu, ZhipengS" > *Date: *Friday, November 1, 2019 at 12:02 AM > *To: *"Xie, Cindy" , "Lemus Contreras, Cristopher > J" , '朱博祥' > , "'starlingx-discuss at lists.starlingx.io'" > > *Cc: *"Alonso, Juan Carlos" , "Hu, Yong" > , "Cabrales, Ada" , "Jones, > Bruce E" , "Martinez Monroy, Elio" > > *Subject: *RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi all, > > After using new image file (cirros-0.4.0-x86_64-disk.img), we can launch > instance on standard external Storage (2+2+2) now. > > It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by > Cristopher Lemus causes qemu-img detecting wrong format after format > convert from qcow2to raw in Nova code.  We are not sure how/where we got > this image file. > > Thanks! > > Zhipeng > > *From:* Liu, ZhipengS > *Sent:* 2019年10月31日 17:31 > *To:* Xie, Cindy ; Lemus Contreras, Cristopher J > ; '朱博祥' > ; 'starlingx-discuss at lists.starlingx.io' > > *Cc:* Alonso, Juan Carlos ; Hu, Yong > ; Cabrales, Ada ; Jones, > Bruce E ; Martinez Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > For remote storage configuration,  we have overridden below > configurations in helm/nova.py. > >      if remote_storage: > > default_config.update({'force_raw_images': True}) > >             libvirt_config.update({'images_type': 'rbd', > >                                    'images_rbd_pool': rbd_pool, > >                                    'images_rbd_ceph_conf': rbd_ceph_conf}) > >         else: > >             libvirt_config.update({'images_type': 'default'}) > > Next step: > > The only issue we need to figure out is why image format is still qcow2 > after image format convert by qemu-img in nova code. > > I tried to reproduce it in my virtualized multi-node environment, but no > issue found, VM created normally. > > (I copied yellow code block to else branch) > > In /var/lib/nova/instances/_base/ folder, > > I can see one qcow2 image and one raw image which should be converted by > nova. > > [root at compute-1 _base]# ls > > 3cb926303b665709318d2c099722b914025023b4 > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > [root at compute-1 _base]# qemu-img info > 3cb926303b665709318d2c099722b914025023b4 > > image: 3cb926303b665709318d2c099722b914025023b4 > > file format: qcow2 > > virtual size: 44M (46137344 bytes) > > disk size: 12M > > cluster_size: 65536 > > Format specific information: > >     compat: 1.1 > >     lazy refcounts: false > >     refcount bits: 16 > >     corrupt: false > > [root at compute-1 _base]# qemu-img info > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > file format: raw > > virtual size: 44M (46137344 bytes) > > disk size: 13M > > Any comment? > > Thanks! > > zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 10:15 > *To:* Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J > >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > In fetch_to_raw(), > > After force convert image from qcow2 to raw,  the format is still not > raw,  then throw below error. > > It seems qemu-image convert image failed. > > Zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 9:35 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > *From:* Liu, ZhipengS > *Sent:* 2019年10月30日 23:24 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang, > > It should be an issue in nova train. > > Error log is below: > > build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image > 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to raw, > but format is now qcow2' > > You tried to fix this issue before in nova LP: > > https://bugs.launchpad.net/nova/+bug/1816686 > > In your patch: https://review.opendev.org/#/c/640271 (This patch is > already in train release now) > > You added below commit message in the patch. > > “When we import image into rbd, check the format of cache > > images. If the format is not raw, remove it first and > > fetch it again. It will be raw format now.” > > However, it seems not work!  Below code will throw error when image > format is not raw and block the VM creation. > > In nova/virt/images.py > > def fetch_to_raw() è > > if data.file_format != "raw": > >                       raise > exception.ImageUnacceptable(image_id=image_href, > >                         reason=_("Converted to raw, but format is now %s") > > Not sure if your patch fixed this issue or is there any regression > introduced in nova code later. > > Any comment from you? > > I will check nova code further tomorrow and sync with you. > > We may need a patch for nova☹ > > Thanks! > > Zhipeng > > *From:* Xie, Cindy > > *Sent:* 2019年10月30日 22:49 > *To:* Lemus Contreras, Cristopher J > >; Liu, ZhipengS > >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > + mailing list in case anybody can help on debug the issue. > > *From:* Lemus Contreras, Cristopher J > > > *Sent:* Wednesday, October 30, 2019 7:45 PM > *To:* Liu, ZhipengS >; 朱博祥 > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Zhipeng, > > The results are OK for Simplex, Duplex and Standard Local Storage, all > Test Cases PASSED. > > For Standard External Storage (2+2+2) there is a high quantity of Test > Cases failing because we cannot launch instances. Here’s a sample > output: http://paste.openstack.org/show/785641/ with the error that > matches what is described on the launchpad. > > Sanity summary for this specific configuration: > http://paste.openstack.org/show/785655/ > > Please, let us know if you need additional details. > > Thanks & Regards, > > Cristopher Lemus > From Frank.Miller at windriver.com Mon Nov 4 14:47:21 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 4 Nov 2019 14:47:21 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Due to the Shanghai summit this week, our next meeting for containerization will be on Tuesday November 12. The agenda will be sent out later. Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2350 bytes Desc: not available URL: From elio.martinez.monroy at intel.com Mon Nov 4 17:30:28 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Mon, 4 Nov 2019 17:30:28 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> Message-ID: Christopher is on vacations today. I Will provide the image ASAP. -----Original Message----- From: Hu, Yong Sent: Monday, November 4, 2019 7:56 AM To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; Xie, Cindy ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Christopher, A quick question, were we using this image "cirros-0.4.0-x86_64-disk.qcow2" for the previous versions of StarlingX? In addition, @Zhipeng, we might get this image to dig out the root-cause further. Regards, Yong On 2019/11/2 4:53 AM, Lemus Contreras, Cristopher J wrote: > Hello, > > Using the EB that Zhipeng provided, and replacing > “cirros-0.4.0-x86_64-disk.qcow2” with “cirros-0.4.0-x86_64-disk.img”, > Sanity status is Green. > > *AIO – Simplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  49 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 61 TCs PASS ] > > *AIO – Duplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  52 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 64 TCs PASS ] > > *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 PASS ] > > *Standard - 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 PASS ] > > =========================================== > > Just the cirros image was replaced. Centos file is still a .qcow2. > > Please, let me know if you need further details. > > Thanks & Regards, > > Cristopher Lemus > > *From: *"Liu, ZhipengS" > *Date: *Friday, November 1, 2019 at 12:02 AM > *To: *"Xie, Cindy" , "Lemus Contreras, Cristopher > J" , '朱博祥' > , "'starlingx-discuss at lists.starlingx.io'" > > *Cc: *"Alonso, Juan Carlos" , "Hu, Yong" > , "Cabrales, Ada" , "Jones, > Bruce E" , "Martinez Monroy, Elio" > > *Subject: *RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi all, > > After using new image file (cirros-0.4.0-x86_64-disk.img), we can > launch instance on standard external Storage (2+2+2) now. > > It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by > Cristopher Lemus causes qemu-img detecting wrong format after format > convert from qcow2to raw in Nova code.  We are not sure how/where we > got this image file. > > Thanks! > > Zhipeng > > *From:* Liu, ZhipengS > *Sent:* 2019年10月31日 17:31 > *To:* Xie, Cindy ; Lemus Contreras, Cristopher J > ; '朱博祥' > ; 'starlingx-discuss at lists.starlingx.io' > > *Cc:* Alonso, Juan Carlos ; Hu, Yong > ; Cabrales, Ada ; Jones, > Bruce E ; Martinez Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > For remote storage configuration,  we have overridden below > configurations in helm/nova.py. > >      if remote_storage: > > default_config.update({'force_raw_images': True}) > >             libvirt_config.update({'images_type': 'rbd', > >                                    'images_rbd_pool': rbd_pool, > >                                    'images_rbd_ceph_conf': > rbd_ceph_conf}) > >         else: > >             libvirt_config.update({'images_type': 'default'}) > > Next step: > > The only issue we need to figure out is why image format is still > qcow2 after image format convert by qemu-img in nova code. > > I tried to reproduce it in my virtualized multi-node environment, but > no issue found, VM created normally. > > (I copied yellow code block to else branch) > > In /var/lib/nova/instances/_base/ folder, > > I can see one qcow2 image and one raw image which should be converted > by nova. > > [root at compute-1 _base]# ls > > 3cb926303b665709318d2c099722b914025023b4 > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > [root at compute-1 _base]# qemu-img info > 3cb926303b665709318d2c099722b914025023b4 > > image: 3cb926303b665709318d2c099722b914025023b4 > > file format: qcow2 > > virtual size: 44M (46137344 bytes) > > disk size: 12M > > cluster_size: 65536 > > Format specific information: > >     compat: 1.1 > >     lazy refcounts: false > >     refcount bits: 16 > >     corrupt: false > > [root at compute-1 _base]# qemu-img info > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > file format: raw > > virtual size: 44M (46137344 bytes) > > disk size: 13M > > Any comment? > > Thanks! > > zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 10:15 > *To:* Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J > >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > In fetch_to_raw(), > > After force convert image from qcow2 to raw,  the format is still not > raw,  then throw below error. > > It seems qemu-image convert image failed. > > Zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 9:35 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > *From:* Liu, ZhipengS > *Sent:* 2019年10月30日 23:24 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang, > > It should be an issue in nova train. > > Error log is below: > > build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image > 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to > raw, but format is now qcow2' > > You tried to fix this issue before in nova LP: > > https://bugs.launchpad.net/nova/+bug/1816686 > > In your patch: https://review.opendev.org/#/c/640271 (This patch is > already in train release now) > > You added below commit message in the patch. > > “When we import image into rbd, check the format of cache > > images. If the format is not raw, remove it first and > > fetch it again. It will be raw format now.” > > However, it seems not work!  Below code will throw error when image > format is not raw and block the VM creation. > > In nova/virt/images.py > > def fetch_to_raw() è > > if data.file_format != "raw": > >                       raise > exception.ImageUnacceptable(image_id=image_href, > >                         reason=_("Converted to raw, but format is now > %s") > > Not sure if your patch fixed this issue or is there any regression > introduced in nova code later. > > Any comment from you? > > I will check nova code further tomorrow and sync with you. > > We may need a patch for nova☹ > > Thanks! > > Zhipeng > > *From:* Xie, Cindy > > *Sent:* 2019年10月30日 22:49 > *To:* Lemus Contreras, Cristopher J > >; Liu, ZhipengS > >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > + mailing list in case anybody can help on debug the issue. > > *From:* Lemus Contreras, Cristopher J > > > *Sent:* Wednesday, October 30, 2019 7:45 PM > *To:* Liu, ZhipengS >; 朱博祥 > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Zhipeng, > > The results are OK for Simplex, Duplex and Standard Local Storage, all > Test Cases PASSED. > > For Standard External Storage (2+2+2) there is a high quantity of Test > Cases failing because we cannot launch instances. Here’s a sample > output: http://paste.openstack.org/show/785641/ with the error that > matches what is described on the launchpad. > > Sanity summary for this specific configuration: > http://paste.openstack.org/show/785655/ > > Please, let us know if you need additional details. > > Thanks & Regards, > > Cristopher Lemus > From Don.Penney at windriver.com Mon Nov 4 19:46:31 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 4 Nov 2019 19:46:31 +0000 Subject: [Starlingx-discuss] relocating distcloud and distcloud-client repos from stx/git to stx Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B2108@ALA-MBD.corp.ad.wrs.com> Hi all, As part of the build layering work, we're moving the distcloud and distcloud-client repos from stx/git to stx, and moving the corresponding build and other associated files from stx/upstream to those repos. This will allow us to configure these repos as being in the flock layer, rather than distro, for the build layering feature. https://review.opendev.org/#/q/topic:move-distcloud+(status:open+OR+status:merged) The bulk of these reviews are basically cherry-picks - a reformatted patch of the historical patches to the files in stx/upstream, in order to maintain the history of these files after the move to the new repo. Please let me know if you have any questions. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Mon Nov 4 21:22:50 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Mon, 4 Nov 2019 15:22:50 -0600 Subject: [Starlingx-discuss] Slides for Update In-Reply-To: References: Message-ID: On 11/4/19 2:00 AM, Saul Wold wrote: > Particularly TSC and Release Planning folks, please do a once over on > these slides, it would be great to get a few more words around the > Distributed Cloud on slide 8. * Slide 4 - minor thing, maybe change the footnote to past-tense? We are no longer backporting things into Nova... * Slide 7 - It is not clear that the OpenStack services mentioned (Barbican, Horizon and Keystone) are for the platform support and not the regular OpenStack services that cloud users would see. Also the last sentence appears to be missing a word: "...updated that will need more testing." * Slides 5 & 6 - check capitalization of "OpenStack" dt -- Dean Troyer dtroyer at gmail.com From ada.cabrales at intel.com Mon Nov 4 23:28:31 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 4 Nov 2019 23:28:31 +0000 Subject: [Starlingx-discuss] [ Test ] meeting on 11/05 - cancelled Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF029DA@FMSMSX114.amr.corp.intel.com> Hello, Just a reminder: the test meeting won't be held tomorrow. Please send me your updates offline (the activities you're working on) or update the etherpad [0]. Thanks Ada [0] https://etherpad.openstack.org/p/stx-test From maria.g.perez.ibarra at intel.com Mon Nov 4 23:54:12 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 4 Nov 2019 23:54:12 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191104 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-04 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 49 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 61 TCs PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] Standard - 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 PASS ] =========================================== Sanity Test is executed in a Containers - 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 PASS ] AIO - Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 07 TCs [PASS] TOTAL: [ 64 TCs PASS ] 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 PASS ] Standard - 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 PASS ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006810.html Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Tue Nov 5 01:52:43 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Tue, 05 Nov 2019 09:52:43 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIFJlZy4gT3BlblN0YWNr?= =?utf-8?q?_components_in_StarlingX=09all-in-one_simplex?= In-Reply-To: References: Message-ID: <102141c4-39c4-49ee-bf36-b6dbbee5c6b3.qianjiang@baicells.com> Hi, Behara I was using StarlingX all-in-one simplex, and can upload image, create network, instance etc. Compute service is included. Maybe you can try using openstack command first, then dashboard. It will be more clear what's happened. For example, follow below links to launch instances. https://docs.openstack.org/install-guide/launch-instance.html https://docs.openstack.org/install-guide/launch-instance-provider.html Best Regard ------------------------------------------------------------------ 发件人:Saichandu Behara 发送时间:2019年11月4日(星期一) 19:45 收件人:starlingx-discuss at lists.starlingx.io 抄 送:Pavan Gupta 主 题:[Starlingx-discuss] Reg. OpenStack components in StarlingX all-in-one simplex Hello all, I have installed StarlingX all-in-one simplex. When i open Horizon page, I didn't get compute, volumes,etc. in GUI page. and there is no option in " Add images/Vm's ". Can any one confirm, All-in-one simplex is supported with Compute and adding the images or not and Is this services are included in StarlingX all-in-one simplex architecture? -- Thanks & Regards Sai Chandu Behara _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Tue Nov 5 02:28:09 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Tue, 5 Nov 2019 02:28:09 +0000 Subject: [Starlingx-discuss] IP is not being assigned Message-ID: Following the bug https://bugs.launchpad.net/starlingx/+bug/1849221 We fond that the instances are not working even if we force the ip, I just post the comment and logs on the mentioned bug. We are not able to continue with the testing. Not matter that we used the WA mentioned in the bug. Not able to ping between instances . It doesn't matter if we add security groups or even keypairs. No communication between instances, or from node to instance. This problem is affecting all configurations. [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From zhipengs.liu at intel.com Tue Nov 5 02:39:27 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 5 Nov 2019 02:39:27 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> Message-ID: <93814834B4855241994F290E959305C7530F5819@SHSMSX104.ccr.corp.intel.com> Hi Yong and all, The root cause should be below. Download image from https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img It is already qcow2, if we use below command to convert to qcow2 again, it will be added with an additional qcow2 header. This is the problem!!! controller-0:~$ qemu-img convert -f raw -O qcow2 cirros-0.4.0-x86_64-disk.img cirros-0.4.0-x86_64-disk.qcow2 So, if we run test case in nova train release. It will just like below. controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 cirros-0.4.0-x86_64-disk.qcow2 test controller-0:~$ qemu-img info test image: test file format: qcow2 //it is still qcow2, just removed additional qcow header. virtual size: 44M (46137344 bytes) controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 test test22 controller-0:~$ qemu-img info test22 image: test22 file format: raw //after second convert, it becomes raw!!! virtual size: 44M (46137344 bytes) That's why we use the cirros-0.4.0-x86_64-disk.img downloaded from official website can pass sanity test. Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月4日 21:56 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; Xie, Cindy ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Christopher, A quick question, were we using this image "cirros-0.4.0-x86_64-disk.qcow2" for the previous versions of StarlingX? In addition, @Zhipeng, we might get this image to dig out the root-cause further. Regards, Yong On 2019/11/2 4:53 AM, Lemus Contreras, Cristopher J wrote: > Hello, > > Using the EB that Zhipeng provided, and replacing > “cirros-0.4.0-x86_64-disk.qcow2” with “cirros-0.4.0-x86_64-disk.img”, > Sanity status is Green. > > *AIO – Simplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  49 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 61 TCs PASS ] > > *AIO – Duplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  52 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 64 TCs PASS ] > > *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 PASS ] > > *Standard - 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 PASS ] > > =========================================== > > Just the cirros image was replaced. Centos file is still a .qcow2. > > Please, let me know if you need further details. > > Thanks & Regards, > > Cristopher Lemus > > *From: *"Liu, ZhipengS" > *Date: *Friday, November 1, 2019 at 12:02 AM > *To: *"Xie, Cindy" , "Lemus Contreras, Cristopher > J" , '朱博祥' > , "'starlingx-discuss at lists.starlingx.io'" > > *Cc: *"Alonso, Juan Carlos" , "Hu, Yong" > , "Cabrales, Ada" , "Jones, > Bruce E" , "Martinez Monroy, Elio" > > *Subject: *RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi all, > > After using new image file (cirros-0.4.0-x86_64-disk.img), we can > launch instance on standard external Storage (2+2+2) now. > > It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by > Cristopher Lemus causes qemu-img detecting wrong format after format > convert from qcow2to raw in Nova code.  We are not sure how/where we > got this image file. > > Thanks! > > Zhipeng > > *From:* Liu, ZhipengS > *Sent:* 2019年10月31日 17:31 > *To:* Xie, Cindy ; Lemus Contreras, Cristopher J > ; '朱博祥' > ; 'starlingx-discuss at lists.starlingx.io' > > *Cc:* Alonso, Juan Carlos ; Hu, Yong > ; Cabrales, Ada ; Jones, > Bruce E ; Martinez Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > For remote storage configuration,  we have overridden below > configurations in helm/nova.py. > >      if remote_storage: > > default_config.update({'force_raw_images': True}) > >             libvirt_config.update({'images_type': 'rbd', > >                                    'images_rbd_pool': rbd_pool, > >                                    'images_rbd_ceph_conf': > rbd_ceph_conf}) > >         else: > >             libvirt_config.update({'images_type': 'default'}) > > Next step: > > The only issue we need to figure out is why image format is still > qcow2 after image format convert by qemu-img in nova code. > > I tried to reproduce it in my virtualized multi-node environment, but > no issue found, VM created normally. > > (I copied yellow code block to else branch) > > In /var/lib/nova/instances/_base/ folder, > > I can see one qcow2 image and one raw image which should be converted > by nova. > > [root at compute-1 _base]# ls > > 3cb926303b665709318d2c099722b914025023b4 > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > [root at compute-1 _base]# qemu-img info > 3cb926303b665709318d2c099722b914025023b4 > > image: 3cb926303b665709318d2c099722b914025023b4 > > file format: qcow2 > > virtual size: 44M (46137344 bytes) > > disk size: 12M > > cluster_size: 65536 > > Format specific information: > >     compat: 1.1 > >     lazy refcounts: false > >     refcount bits: 16 > >     corrupt: false > > [root at compute-1 _base]# qemu-img info > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > file format: raw > > virtual size: 44M (46137344 bytes) > > disk size: 13M > > Any comment? > > Thanks! > > zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 10:15 > *To:* Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J > >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > In fetch_to_raw(), > > After force convert image from qcow2 to raw,  the format is still not > raw,  then throw below error. > > It seems qemu-image convert image failed. > > Zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 9:35 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > *From:* Liu, ZhipengS > *Sent:* 2019年10月30日 23:24 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang, > > It should be an issue in nova train. > > Error log is below: > > build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image > 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to > raw, but format is now qcow2' > > You tried to fix this issue before in nova LP: > > https://bugs.launchpad.net/nova/+bug/1816686 > > In your patch: https://review.opendev.org/#/c/640271 (This patch is > already in train release now) > > You added below commit message in the patch. > > “When we import image into rbd, check the format of cache > > images. If the format is not raw, remove it first and > > fetch it again. It will be raw format now.” > > However, it seems not work!  Below code will throw error when image > format is not raw and block the VM creation. > > In nova/virt/images.py > > def fetch_to_raw() è > > if data.file_format != "raw": > >                       raise > exception.ImageUnacceptable(image_id=image_href, > >                         reason=_("Converted to raw, but format is now > %s") > > Not sure if your patch fixed this issue or is there any regression > introduced in nova code later. > > Any comment from you? > > I will check nova code further tomorrow and sync with you. > > We may need a patch for nova☹ > > Thanks! > > Zhipeng > > *From:* Xie, Cindy > > *Sent:* 2019年10月30日 22:49 > *To:* Lemus Contreras, Cristopher J > >; Liu, ZhipengS > >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > + mailing list in case anybody can help on debug the issue. > > *From:* Lemus Contreras, Cristopher J > > > *Sent:* Wednesday, October 30, 2019 7:45 PM > *To:* Liu, ZhipengS >; 朱博祥 > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Zhipeng, > > The results are OK for Simplex, Duplex and Standard Local Storage, all > Test Cases PASSED. > > For Standard External Storage (2+2+2) there is a high quantity of Test > Cases failing because we cannot launch instances. Here’s a sample > output: http://paste.openstack.org/show/785641/ with the error that > matches what is described on the launchpad. > > Sanity summary for this specific configuration: > http://paste.openstack.org/show/785655/ > > Please, let us know if you need additional details. > > Thanks & Regards, > > Cristopher Lemus > From austin.sun at intel.com Tue Nov 5 08:31:00 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Nov 2019 08:31:00 +0000 Subject: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting Message-ID: Hi All: New Series of non-Openstack disto meeting invitation , Agenda for each will be sent individual email. * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o 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 * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2262 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ATT20876 1.jpg Type: image/jpeg Size: 8269 bytes Desc: ATT20876 1.jpg URL: From austin.sun at intel.com Tue Nov 5 08:36:45 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Nov 2019 08:36:45 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Message-ID: Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Tue Nov 5 08:56:44 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 5 Nov 2019 08:56:44 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EC2747BF3@ALA-MBD.corp.ad.wrs.com> Hi Austin, Please refer to the PTG agenda that was published earlier. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 5, 2019 3:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Nov 5 09:04:13 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Nov 2019 09:04:13 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EC2747BF3@ALA-MBD.corp.ad.wrs.com> References: <2588653EBDFFA34B982FAF00F1B4844EC2747BF3@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Brent: Thanks. The item will be sharing the Openinfra summit and PTG information in non-Openstack distro meeting to whom do not join summit . 😊 Austin Sun. From: Rowsell, Brent Sent: Tuesday, November 5, 2019 4:57 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Hi Austin, Please refer to the PTG agenda that was published earlier. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 5, 2019 3:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Tue Nov 5 09:09:40 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 5 Nov 2019 09:09:40 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 In-Reply-To: References: Message-ID: <456FA3D2-5E47-416B-A3E8-1B8DBB4E28B8@windriver.com> My bad, sleep deprived. Brent Sent from my iPhone On Nov 5, 2019, at 5:04 PM, Sun, Austin wrote:  Hi Brent: Thanks. The item will be sharing the Openinfra summit and PTG information in non-Openstack distro meeting to whom do not join summit . 😊 Austin Sun. From: Rowsell, Brent Sent: Tuesday, November 5, 2019 4:57 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Hi Austin, Please refer to the PTG agenda that was published earlier. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 5, 2019 3:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Nov 5 09:30:36 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 5 Nov 2019 09:30:36 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 In-Reply-To: <456FA3D2-5E47-416B-A3E8-1B8DBB4E28B8@windriver.com> References: <456FA3D2-5E47-416B-A3E8-1B8DBB4E28B8@windriver.com> Message-ID: NP. Drink some QingDao Beer and have a good sleep , it will be long day tomorrow. From: Rowsell, Brent Sent: Tuesday, November 5, 2019 5:10 PM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 My bad, sleep deprived. Brent Sent from my iPhone On Nov 5, 2019, at 5:04 PM, Sun, Austin > wrote:  Hi Brent: Thanks. The item will be sharing the Openinfra summit and PTG information in non-Openstack distro meeting to whom do not join summit . 😊 Austin Sun. From: Rowsell, Brent > Sent: Tuesday, November 5, 2019 4:57 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Hi Austin, Please refer to the PTG agenda that was published earlier. https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai Brent From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 5, 2019 3:37 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Tue Nov 5 12:04:56 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 05 Nov 2019 06:04:56 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$5n5rep@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191105T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From yong.hu at intel.com Tue Nov 5 14:46:30 2019 From: yong.hu at intel.com (Yong Hu) Date: Tue, 5 Nov 2019 22:46:30 +0800 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Message-ID: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. From Barton.Wensley at windriver.com Tue Nov 5 15:11:48 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 5 Nov 2019 15:11:48 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> Yong, Has someone run the VIM automated testing against the new load? See attached email for details. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: November 5, 2019 9:47 AM To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An embedded message was scrubbed... From: "Wensley, Barton" Subject: Re: [Starlingx-discuss] openstack-distro meeting 10 29th 2019 minutes Date: Thu, 31 Oct 2019 17:55:23 +0000 Size: 32189 URL: From vm.rod25 at gmail.com Tue Nov 5 15:52:18 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 5 Nov 2019 09:52:18 -0600 Subject: [Starlingx-discuss] Performance test framework approved and next steps In-Reply-To: References: Message-ID: Hi team Here the first semi-automated test case: https://review.opendev.org/#/c/693012/ Author Mario Carrillo Any feedback more than welcome Regards Victor Rodriguez On Wed, Oct 23, 2019 at 2:49 PM Victor Rodriguez wrote: > > Hi StarlingX team > > I am pleased to announce that the specification for the performance > test suite framework has been accepted: > > https://review.opendev.org/#/c/677287/ > > The proposed change is to create a set of scripts and documentation under the > StarlingX testing repository (https://opendev.org/starlingx/test) that anyone > can use to measure the metric they need under their hardware and software > environment/configuration. > > The next step after the approval of the specification is to send the > Gerrit reviews for the test cases. We have a list of test cases for > R3.0 preparation, they are partially automated (thanks to all the > developers that help on this process): > > https://drive.google.com/open?id=1Nr12zDRXf34kpjiA0LsFLU8GIpMY8Y-H2zmiC96CD4A > > These partially automated tests will be uploaded for now into a > scripts/ directory at the same directory layer as > automated-pytest-suite, this until we have them fully automated and be > moved inside automated-pytest-suite directory. > > This mail is to call for volunteers willing to help to code. If anyone > is interested to develop or migrate an existing performance test, > please let us know and we will be more than happy to help you with the > development/migration. Any help is more than appreciated. > > Thanks > > Victor Rodriguez From Bill.Zvonar at windriver.com Tue Nov 5 15:54:02 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 5 Nov 2019 15:54:02 +0000 Subject: [Starlingx-discuss] Community Call (Nov 6, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B1FDD9@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Please note that with the time change, this call moves to 3pm UTC - see [2] for the start time where you are. Feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191106T1500 From elio.martinez.monroy at intel.com Tue Nov 5 17:33:37 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Tue, 5 Nov 2019 17:33:37 +0000 Subject: [Starlingx-discuss] Instances are not acquiring IP4 address Message-ID: Hi, I just decided to create a separate bug for the IP issue since the WR mentioned in https://bugs.launchpad.net/starlingx/+bug/1849221 doesn't work anymore. Please check the latest updates in : https://bugs.launchpad.net/starlingx/+bug/1851414 I put it as critical since it is blocking us. We are not able to continue with the testing. [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer. Open-source Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From maria.g.perez.ibarra at intel.com Tue Nov 5 23:27:50 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 5 Nov 2019 23:27:50 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191105 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-05 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006837.html BUGS * stx-openstack fails to apply - rabbitmq error https://bugs.launchpad.net/starlingx/+bug/1851419 * AIO - platform-integ-apps not applied https://bugs.launchpad.net/starlingx/+bug/1851424 Regards Maria G. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Nov 6 03:24:40 2019 From: yong.hu at intel.com (Yong Hu) Date: Wed, 6 Nov 2019 11:24:40 +0800 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> Message-ID: <90f7df72-202d-2558-c9e6-cc04fd7d6689@intel.com> Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote: > Yong, > > Has someone run the VIM automated testing against the new load? See attached email for details. > > Bart > > -----Original Message----- > From: Yong Hu [mailto:yong.hu at intel.com] > Sent: November 5, 2019 9:47 AM > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J > Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the > sanity, based on test results from testing team. (Thanks to @JC and > @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later Zhipeng > found the cause was from an non-standard test (cirros) image which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because > the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is > now enabled by default in Train. Recommendation: later for the testing, > we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or > other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the > inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate > new docker images for Openstack Train services and *upload them to > Docker Hub*. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From austin.sun at intel.com Wed Nov 6 04:04:58 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 6 Nov 2019 04:04:58 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Nov 6 09:01:45 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 06 Nov 2019 03:01:45 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6u07vd@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191106T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Barton.Wensley at windriver.com Wed Nov 6 12:47:16 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Wed, 6 Nov 2019 12:47:16 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <90f7df72-202d-2558-c9e6-cc04fd7d6689@intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> <90f7df72-202d-2558-c9e6-cc04fd7d6689@intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DF8B@ALA-MBD.corp.ad.wrs.com> Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote: > Yong, > > Has someone run the VIM automated testing against the new load? See attached email for details. > > Bart > > -----Original Message----- > From: Yong Hu [mailto:yong.hu at intel.com] > Sent: November 5, 2019 9:47 AM > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J > Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the > sanity, based on test results from testing team. (Thanks to @JC and > @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later Zhipeng > found the cause was from an non-standard test (cirros) image which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because > the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is > now enabled by default in Train. Recommendation: later for the testing, > we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or > other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the > inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate > new docker images for Openstack Train services and *upload them to > Docker Hub*. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Philip_Wang at alphanetworks.com Tue Nov 5 02:10:31 2019 From: Philip_Wang at alphanetworks.com (Philip_Wang at alphanetworks.com) Date: Tue, 5 Nov 2019 02:10:31 +0000 Subject: [Starlingx-discuss] How to configure compute note PTP as Master Message-ID: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> Hi Team, Below is PTP architecture in StarlingX. [cid:image003.png at 01D593C1.406FFD30] We need connect a host device that need PTP time sync on compute node. But in StarlingX compute node is slave. - How can we configure or modified PTP in StarlingX let compute node can be Master/Slave BC mode. - Or what architecture should be in StarlingX support host device need PTP time sync. Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 84291 bytes Desc: image003.png URL: From zhipengs.liu at intel.com Tue Nov 5 03:15:38 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 5 Nov 2019 03:15:38 +0000 Subject: [Starlingx-discuss] About EB verification for openstack train upgrade In-Reply-To: <93814834B4855241994F290E959305C7530F5819@SHSMSX104.ccr.corp.intel.com> References: <3B594C2B-E02A-4844-A3AA-0649C2885989@intel.com> <93814834B4855241994F290E959305C7530F1A5F@SHSMSX104.ccr.corp.intel.com> <45705CE3-2F92-43BB-9ADF-A5B17861DC71@intel.com> <2FD5DDB5A04D264C80D42CA35194914F360AB833@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F1C97@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D55@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2D84@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F2F73@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F31B3@SHSMSX104.ccr.corp.intel.com> <370ce7be-1777-299b-e27d-34f9a85d3485@intel.com> <93814834B4855241994F290E959305C7530F5819@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F582F@SHSMSX104.ccr.corp.intel.com> Hi Elio and JC, I found that in your test machine, there are both good and bad images. tester tester 13107200 Nov 4 03:58 ./Downloads/cirros-0.4.0-x86_64-disk.qcow2 is bad tester tester 12716032 May 20 08:24 ./elio/cirros-0.4.0-x86_64-disk.qcow2 is good So, I propose you to use image downloaded from official website directly, https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img This is already qcow2 format. Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月5日 10:39 To: Hu, Yong ; Lemus Contreras, Cristopher J ; Xie, Cindy ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Yong and all, The root cause should be below. Download image from https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img It is already qcow2, if we use below command to convert to qcow2 again, it will be added with an additional qcow2 header. This is the problem!!! controller-0:~$ qemu-img convert -f raw -O qcow2 cirros-0.4.0-x86_64-disk.img cirros-0.4.0-x86_64-disk.qcow2 So, if we run test case in nova train release. It will just like below. controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 cirros-0.4.0-x86_64-disk.qcow2 test controller-0:~$ qemu-img info test image: test file format: qcow2 //it is still qcow2, just removed additional qcow header. virtual size: 44M (46137344 bytes) controller-0:~$ qemu-img convert -t writeback -O raw -f qcow2 test test22 controller-0:~$ qemu-img info test22 image: test22 file format: raw //after second convert, it becomes raw!!! virtual size: 44M (46137344 bytes) That's why we use the cirros-0.4.0-x86_64-disk.img downloaded from official website can pass sanity test. Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月4日 21:56 To: Lemus Contreras, Cristopher J ; Liu, ZhipengS ; Xie, Cindy ; '朱博祥' ; 'starlingx-discuss at lists.starlingx.io' Cc: Alonso, Juan Carlos ; Cabrales, Ada ; Jones, Bruce E ; Martinez Monroy, Elio Subject: Re: [Starlingx-discuss] About EB verification for openstack train upgrade Hi Christopher, A quick question, were we using this image "cirros-0.4.0-x86_64-disk.qcow2" for the previous versions of StarlingX? In addition, @Zhipeng, we might get this image to dig out the root-cause further. Regards, Yong On 2019/11/2 4:53 AM, Lemus Contreras, Cristopher J wrote: > Hello, > > Using the EB that Zhipeng provided, and replacing > “cirros-0.4.0-x86_64-disk.qcow2” with “cirros-0.4.0-x86_64-disk.img”, > Sanity status is Green. > > *AIO – Simplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  49 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 61 TCs PASS ] > > *AIO – Duplex* > > ** > > Setup             04 TCs [PASS] > > Provisioning      01 TCs [PASS] > > Sanity OpenStack  52 TCs [PASS] > > Sanity Platform   07 TCs [PASS] > > TOTAL: [ 64 TCs PASS ] > > *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 PASS ] > > *Standard - 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 PASS ] > > =========================================== > > Just the cirros image was replaced. Centos file is still a .qcow2. > > Please, let me know if you need further details. > > Thanks & Regards, > > Cristopher Lemus > > *From: *"Liu, ZhipengS" > *Date: *Friday, November 1, 2019 at 12:02 AM > *To: *"Xie, Cindy" , "Lemus Contreras, Cristopher > J" , '朱博祥' > , "'starlingx-discuss at lists.starlingx.io'" > > *Cc: *"Alonso, Juan Carlos" , "Hu, Yong" > , "Cabrales, Ada" , "Jones, > Bruce E" , "Martinez Monroy, Elio" > > *Subject: *RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi all, > > After using new image file (cirros-0.4.0-x86_64-disk.img), we can > launch instance on standard external Storage (2+2+2) now. > > It seems the old image file (cirros-0.4.0-x86_64-disk.qcow2) used by > Cristopher Lemus causes qemu-img detecting wrong format after format > convert from qcow2to raw in Nova code.  We are not sure how/where we > got this image file. > > Thanks! > > Zhipeng > > *From:* Liu, ZhipengS > *Sent:* 2019年10月31日 17:31 > *To:* Xie, Cindy ; Lemus Contreras, Cristopher J > ; '朱博祥' > ; 'starlingx-discuss at lists.starlingx.io' > > *Cc:* Alonso, Juan Carlos ; Hu, Yong > ; Cabrales, Ada ; Jones, > Bruce E ; Martinez Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > For remote storage configuration,  we have overridden below > configurations in helm/nova.py. > >      if remote_storage: > > default_config.update({'force_raw_images': True}) > >             libvirt_config.update({'images_type': 'rbd', > >                                    'images_rbd_pool': rbd_pool, > >                                    'images_rbd_ceph_conf': > rbd_ceph_conf}) > >         else: > >             libvirt_config.update({'images_type': 'default'}) > > Next step: > > The only issue we need to figure out is why image format is still > qcow2 after image format convert by qemu-img in nova code. > > I tried to reproduce it in my virtualized multi-node environment, but > no issue found, VM created normally. > > (I copied yellow code block to else branch) > > In /var/lib/nova/instances/_base/ folder, > > I can see one qcow2 image and one raw image which should be converted > by nova. > > [root at compute-1 _base]# ls > > 3cb926303b665709318d2c099722b914025023b4 > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > [root at compute-1 _base]# qemu-img info > 3cb926303b665709318d2c099722b914025023b4 > > image: 3cb926303b665709318d2c099722b914025023b4 > > file format: qcow2 > > virtual size: 44M (46137344 bytes) > > disk size: 12M > > cluster_size: 65536 > > Format specific information: > >     compat: 1.1 > >     lazy refcounts: false > >     refcount bits: 16 > >     corrupt: false > > [root at compute-1 _base]# qemu-img info > 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > image: 6edc9bb94ba7363ae9d40d43c9d0eeaffdc0f2ee > > file format: raw > > virtual size: 44M (46137344 bytes) > > disk size: 13M > > Any comment? > > Thanks! > > zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 10:15 > *To:* Liu, ZhipengS >; Xie, Cindy >; Lemus Contreras, Cristopher J > >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang and all, > > In fetch_to_raw(), > > After force convert image from qcow2 to raw,  the format is still not > raw,  then throw below error. > > It seems qemu-image convert image failed. > > Zhipeng > > *From:* Liu, ZhipengS > > *Sent:* 2019年10月31日 9:35 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; '朱博祥' > >; > 'starlingx-discuss at lists.starlingx.io' > > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > *From:* Liu, ZhipengS > *Sent:* 2019年10月30日 23:24 > *To:* Xie, Cindy >; > Lemus Contreras, Cristopher J >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Boxiang, > > It should be an issue in nova train. > > Error log is below: > > build of instance 363dddce-7af6-4701-8cea-52630b91ebcf aborted: Image > 70f74018-24f6-4d7d-8f99-2194a4449cfd is unacceptable: Converted to > raw, but format is now qcow2' > > You tried to fix this issue before in nova LP: > > https://bugs.launchpad.net/nova/+bug/1816686 > > In your patch: https://review.opendev.org/#/c/640271 (This patch is > already in train release now) > > You added below commit message in the patch. > > “When we import image into rbd, check the format of cache > > images. If the format is not raw, remove it first and > > fetch it again. It will be raw format now.” > > However, it seems not work!  Below code will throw error when image > format is not raw and block the VM creation. > > In nova/virt/images.py > > def fetch_to_raw() è > > if data.file_format != "raw": > >                       raise > exception.ImageUnacceptable(image_id=image_href, > >                         reason=_("Converted to raw, but format is now > %s") > > Not sure if your patch fixed this issue or is there any regression > introduced in nova code later. > > Any comment from you? > > I will check nova code further tomorrow and sync with you. > > We may need a patch for nova☹ > > Thanks! > > Zhipeng > > *From:* Xie, Cindy > > *Sent:* 2019年10月30日 22:49 > *To:* Lemus Contreras, Cristopher J > >; Liu, ZhipengS > >; 朱博祥 > >; > starlingx-discuss at lists.starlingx.io > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Jones, Bruce E > >; Martinez > Monroy, Elio > > *Subject:* RE: [Starlingx-discuss] About EB verification for openstack > train upgrade > > + mailing list in case anybody can help on debug the issue. > > *From:* Lemus Contreras, Cristopher J > > > *Sent:* Wednesday, October 30, 2019 7:45 PM > *To:* Liu, ZhipengS >; 朱博祥 > > *Cc:* Alonso, Juan Carlos >; Hu, Yong >; Cabrales, Ada >; Xie, Cindy >; Jones, Bruce E >; Martinez Monroy, Elio > > > *Subject:* Re: [Starlingx-discuss] About EB verification for openstack > train upgrade > > Hi Zhipeng, > > The results are OK for Simplex, Duplex and Standard Local Storage, all > Test Cases PASSED. > > For Standard External Storage (2+2+2) there is a high quantity of Test > Cases failing because we cannot launch instances. Here’s a sample > output: http://paste.openstack.org/show/785641/ with the error that > matches what is described on the launchpad. > > Sanity summary for this specific configuration: > http://paste.openstack.org/show/785655/ > > Please, let us know if you need additional details. > > Thanks & Regards, > > Cristopher Lemus > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chiinting at gmail.com Tue Nov 5 03:17:07 2019 From: chiinting at gmail.com (Chiing-Ting Huang) Date: Tue, 5 Nov 2019 11:17:07 +0800 Subject: [Starlingx-discuss] sriov-network-device container issue Message-ID: Dear StarlingX Team I have installed StarlingX R2.0 in September, and kube-sriov-device-plugin can get VF at that time. I think the team updated starlingx/k8s-plugins-sriov-network-device docker image in October, so I cannot get VF now. So I roll back to starlingx/k8s-plugins-sriov-network-device:rc-2.0-centos-stable-20190826T233000Z.0 Best regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Nov 5 06:47:33 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 5 Nov 2019 06:47:33 +0000 Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D85627D0FD@CDSMSX102.ccr.corp.intel.com> Message-ID: Hi Team, The command to get tokens mentioned in the below link works locally on StarlingX setup. https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#rest-apis In order to get a token from a remote server, we need to add Host corresponding to each service in curl command curl -i -H "Content-Type: application/json" -H "Host: keystone.hsc-starlingx-company.com" -d '{ "auth": { "identity": { "methods": ["password"], "password": { "user": { "name": "admin", "domain": { "id": "default" }, "password": "Centos at 123" } } }, "scope": { "project": { "name": "admin", "domain": { "id": "default" } } } } }' http://192.168.121.141:80/v3/auth/tokens TOKEN= curl -i http://192.168.121.141:80/v2.1/flavors -X GET -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token:${TOKEN}" -H "Host: nova.hsc-starlingx-company.com" | tail -1 | python -m json.tool where 192.168.121.141 - OAM IP which is publicly accessible. Query: It is not practically possible to pass FQDN hostname for every service request in the URL. So, is there any way StarlingX automatically routes the ingress request internally ? Or Can we install all the Openstack Helm Chart services on Nodeport? Please suggest the best way to resolve the issue? Regards Anirudh Gupta -----Original Message----- From: Anirudh Gupta Sent: 04 November 2019 09:02 To: Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Hi, Image service is ready to use, but the issue is that it is installed inside docker container which I feel is not accessible from external source. controller-0:~$ openstack endpoint list | grep glance | 55b3d034819f4cecb8650779df6c543d | RegionOne | glance | image | True | internal | http://glance-api.openstack.svc.cluster.local:9292/ | | a40b33d549bb4cac96f00ceb820aabb5 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ | | c60c2fa05b94472d8c0e29aabced774b | RegionOne | glance | image | True | admin | http://glance-api.openstack.svc.cluster.local:9292/ I think that the public endpoint http://glance.openstack.svc.cluster.local:80 is not accessible from outside. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#configure-helm-endpoint-domain Similar is the case for every service. Regards Anirudh Gupta -----Original Message----- From: Chen, Haochuan Z > Sent: 04 November 2019 07:38 To: Anirudh Gupta > Cc: starlingx-discuss at lists.starlingx.io Subject: Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Hi Anirudh Maybe you can check in this way to ensure image service is ready firstly. $ export OS_CLOUD=openstack_helm $ openstack endpoint list BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io > Sent: Sunday, November 3, 2019 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 35 Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=3eG1Ca5bMgCpxKGy%2F9Vk9kKvatId0xjqz6YkkeQOx8E%3D&reserved=0 or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time (Cabrales, Ada) 2. Starlingx 2.0 Service Endpoints not publicly accessed from External Entities (Anirudh Gupta) 3. StarlingX platform-integ-apps docker images (cristopher.j.lemus.contreras at intel.com) ---------------------------------------------------------------------- Message: 1 Date: Fri, 1 Nov 2019 22:45:35 +0000 From: "Cabrales, Ada" > To: "starlingx-discuss at lists.starlingx.io" > Cc: "Martinez Monroy, Elio" >, "'Seiler, Glenn'" >, "Hernandez Gonzalez, Fernando" >, "'Komiyama, Takeo'" >, "Xu, YizhouX" >, "Armstrong, Robert H" >, "Martinez Landa, Hayde" >, "Alonso, Juan Carlos" >, 'Peng Tan' >, "Gomez, Juan P" >, "Sun, Austin" >, Banszel Martin > Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Test meeting - 9:00 Pacific time Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CF01B94 at FMSMSX114.amr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Updates will be requested offline Weekly meetings on Tuesdays at 9am Pacific * Zoom link: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F342730236&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UqST7HL4GAjPpXlyt9Bx1uxTORAU945uMr%2F9VBuqwWM%3D&reserved=0 o 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://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fu%2Fed95sU7aQ&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=4ZjWIMiKjPTFOA%2BENxYwMDSCQbD64GbpXfC46LbalX0%3D&reserved=0 Agenda and meeting minutes: https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fetherpad.openstack.org%2Fp%2Fstx-test&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=UfJsFkKFIkGrcBDJBxn%2FXaUVNCLmlcwXXYMzf1a7YEQ%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3486 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Sat, 2 Nov 2019 21:04:08 +0000 From: Anirudh Gupta > To: "starlingx-discuss at lists.starlingx.io" >, "starlingx-discuss-owner at lists.starlingx.io" > Subject: [Starlingx-discuss] Starlingx 2.0 Service Endpoints not publicly accessed from External Entities Message-ID: > Content-Type: text/plain; charset="utf-8" Hi Team, I am trying to integrate StarlingX 2.0 with Open Source Mano 6.0, but facing errors as the public endpoints for every services are not exposed. I have also configured helm endpoint domain from the below link and updated the wild card entry in dnsmasq.conf file on StarlingX machine https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.starlingx.io%2Fdeploy_install_guides%2Fr2_release%2Fopenstack%2Faccess.html%23configure-helm-endpoint-domain&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711488194&sdata=sWOsa5YN8H8Tpw%2FjAU%2FJqLNtdrsPlBR4kYt0szC3sak%3D&reserved=0 I am getting error 503 code: 503\\n description: 'VIM Exception vimconnUnexpectedResponse EndpointNotFound: public\\n endpoint for image service not found However this was not the case with StarlingX previous release 2018.10. I had successfully integrated it. This is because now the openstack services are now containerized and URL is not publicly exposed. Can someone please update the steps in order to expose all services public endpoints outside StarlingX. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Sun, 03 Nov 2019 02:50:11 -0600 From: cristopher.j.lemus.contreras at intel.com To: > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6t0227 at fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191103T013000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io https://ind01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=02%7C01%7C%7C83e1682fc6d546fbf66808d760cbc99c%7Ca65543b9ae9349b580f00b85821adc50%7C1%7C0%7C637084300711498181&sdata=bEJTXZe41hnithU8mgFdzin57Q5fvOiNUjeNwSDiH8w%3D&reserved=0 ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 35 ************************************************* 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Wed Nov 6 03:43:00 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Wed, 6 Nov 2019 03:43:00 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin Sent: 04 November 2019 19:16 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: stx-openstack-apply.log Type: application/octet-stream Size: 260507 bytes Desc: stx-openstack-apply.log URL: From austin.sun at intel.com Wed Nov 6 14:44:27 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 6 Nov 2019 14:44:27 +0000 Subject: [Starlingx-discuss] MoM Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Message-ID: Hi All: The MoM for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) https://etherpad.openstack.org/p/starlingX-ptg-agenda-shanghai https://etherpad.openstack.org/p/stx.4.0-feature-candidates feature related w/ non-OpenStack Distro CentOS 8 upgrade (Must) Python 2 to 3 (Must) Centos 8 upgrade and python2to3 might need one feature branch. Kata Support Flock Versioning. Ceph containerization Rook BlueStore - Ceph containerization update (Tingjie) [Martin] copy rook code into stx code . this is not correct way . using rook release tarball as base. After armada application Re-factor, update patches for rook. for BlueStore, it is request puppet ceph, but if containerization ceph, puppet-ceph should not be requested. BlueStore spec : https://review.opendev.org/#/c/692502/ - CentOS 8.0 upgrade planning (Shuai Zhao) 3 task is working *) kernel patches analysis . 9 patches should be maintained by code check. 8/9 upgraded successfully , 1 is still under debug. *) docker container builder, upgrade docker to centos8 docker (centos8 by disable some packages) is running successfully , but builder is still fail, some packages of centos8 is missing on centos8 repos. docker image for stx might still using python2 ,and might impact containerization for docker , bring this to container meetting . https://github.com/StarlingX-Neusoft/Centos8.git, the tools has already update docker builder script for centos8 *) srpm which patch need to be removed or update . srpm first anaysis has been done. there 3 status(patched, not srpm, drop). - CVE LP fixing (Shui Cheng) 3 CVE issues . first anaysis is done, several srpm/rpm are needed to be upgraded . work will be starting soon. Thanks. BR Austin Sun. From: Sun, Austin Sent: Tuesday, November 5, 2019 4:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/6/2019 Agenda for 11/6 meeting: - OpenInfra summit and Stx PTG update (Austin) - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Nov 6 15:18:13 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 6 Nov 2019 15:18:13 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: Message-ID: Hello, I hope also the community can help with this questions. @Chen, Yan Can you help me to verify if this feature is still disabled on Train version: Horizon/CSRF AngularJS Fixes ? On last test plan for Stein this feature was no longer required on Horizon and was disabled on SarlingX code. @Gerry.Kopec at windriver.com About the Live Migration bugs I mentioned on the last meeting, almost all of them are merged, except the last three. All those patches are related to live migration, so my question is if I perform live migrations such patches will be covered or should be tested in a different way? The last three were marked as Unlikely and was not merged on Stein. I don't have more info about such patches. Enable delete bound trunk for linux bridge agent: https://review.opendev.org/#/c/605589 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): https://review.opendev.org/#/c/623401 and https://review.opendev.org/#/c/626109 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): https://review.opendev.org/#/c/625134 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): https://review.opendev.org/#/c/628071 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): https://review.opendev.org/#/c/623415 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): https://review.opendev.org/#/c/621507/ Prevent DHCP from processing stale RPC messages: ?? 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Wed Nov 6 15:39:35 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Wed, 6 Nov 2019 15:39:35 +0000 Subject: [Starlingx-discuss] [TSC] No meeting this week in the regular slot as the PTG is underway? Message-ID: <9948C39F-D027-46B9-8B98-043E1C360CBC@windriver.com> Hi all; Since many of the TSC members are at the PTG, I suggest we cancel the regular timeslot tomorrow. Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Nov 6 17:01:37 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 6 Nov 2019 17:01:37 +0000 Subject: [Starlingx-discuss] Community Call (Nov 6, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B207EC@ALA-MBD.corp.ad.wrs.com> Notes from today's meeting... Standing Topics - Gerrit review that need attention - OpenStack Train Upgrade Patches; Yong's email http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006838.html - sanity - any reds since last call? - ISO 20191105: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006843.html - Simplex Issue: 1851424 - didn't happen today, maybe fixed? - Storage Issue: 1851419 - didn't get this far today, failed on integ-apps apply fail - any unanswered calls for assistance on the mailing list - Sai Chandu: "Upload of application stx-openstack (1.0-17-centos-stable-latest) failed: Unsupported application version" - http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.html - Christopher said this doesn't look like a recent sanity issue - Yong said it could be a version mismatch - will show Sai Chandu how to confirm if this is it MS3 Blocking Issues - Intel K8S plugins for GPU and QAT - have not reached closure on design direction. Can we discuss and resolve here? (brucej) - (Ghada) The code merged does not align with the architectural direction. Unfortunately, this was not caught by the original code reviewers, but it was caught later by two TLs (Brent & Matt); both very familiar with this code area andthe architecture of StarlingX. Matt has proposed two options for a resolution: - (1) Revert the code and align with how labels were handled previously - (2) Inventory the devices and add semantic checks when the user is adding the labels - So we need the developer to proceed with implemeting one of these options. - Agreed with Ran that she will revert the code for now and work further on option 2 as a future enhancement. - VIM testing of the Train merge - who has these tests, who can run them (brucej for Yong) - per Bart - they're available to be run, with instructions - re: VIM test if any of the VIM API tests fail, the fix would *always* be done in the VIM - VIM test needs a particular lab setup - would take up to a day, there are instructions - how much OpenStack Regression did we run on Train? - to help us understand the risk of committing w/out running the VIM test suite - Ada to send the OpenStack Regression tests - Bart to review - Ghada asked about the VM connectivity issue - is it also seen in Train? - Yong wasn't sure if this had been seen in Train - we agreed to go ahead & commit Train then deal with whatever issues come up - some reviews to complete, per Yong's email Sanity and Regression Blockers - Need help with https://bugs.launchpad.net/starlingx/+bug/1851414 blocking regression testing (brucejj) - This is under investigation by the networking team - Huifeng as PL / Joseph as a developer - The follow-up action here is to add a VM connectivity test to sanity. This is basic functionality. This was raised before in the stx.2.0 timeframe. - Christopher confirmed that they are working on this - Need help with 1851419 and 1851424 found in Tuesday's Sanity run (brucej) -----Original Message----- From: Zvonar, Bill Sent: Tuesday, November 5, 2019 10:54 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Community Call (Nov 6, 2019) Hi all, reminder of the Community call tomorrow. Please note that with the time change, this call moves to 3pm UTC - see [2] for the start time where you are. Feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191106T1500 From maria.g.perez.ibarra at intel.com Wed Nov 6 17:14:52 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 6 Nov 2019 17:14:52 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191106 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-06 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006846.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Nov 6 18:18:23 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 6 Nov 2019 18:18:23 +0000 Subject: [Starlingx-discuss] relocating distcloud and distcloud-client repos from stx/git to stx Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B94A5@ALA-MBD.corp.ad.wrs.com> These updates have now merged. Cheers, Don. From: Penney, Don Sent: Monday, November 04, 2019 2:47 PM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: relocating distcloud and distcloud-client repos from stx/git to stx Hi all, As part of the build layering work, we're moving the distcloud and distcloud-client repos from stx/git to stx, and moving the corresponding build and other associated files from stx/upstream to those repos. This will allow us to configure these repos as being in the flock layer, rather than distro, for the build layering feature. https://review.opendev.org/#/q/topic:move-distcloud+(status:open+OR+status:merged) The bulk of these reviews are basically cherry-picks - a reformatted patch of the historical patches to the files in stx/upstream, in order to maintain the history of these files after the move to the new repo. Please let me know if you have any questions. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Wed Nov 6 20:14:07 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 6 Nov 2019 20:14:07 +0000 Subject: [Starlingx-discuss] [Build] No Build Meeting this week Message-ID: Due to the summit/PTG this week, the Thursday Build meeting will not be held. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Nov 6 20:19:04 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 6 Nov 2019 20:19:04 +0000 Subject: [Starlingx-discuss] Patch Elimination Train version In-Reply-To: References: <9A85D2917C58154C960D95352B22818BED3606AF@fmsmsx121.amr.corp.intel.com> Message-ID: Hello Ya, I have an standard configuration local storage (2+2) baremetal environment, I can access to nova-compute service for both computes but I did not found a list of 'cpu_models', just found 'cpu_mode' and it is not set as 'custom' as documentation says: [libvirt] cpu_mode = host-model So, I executed: $ system helm-override-update --set livbirt.cpu_mode=custom stx-openstack nova openstack $ system helm-override-update --set cpu_models=SandyBridge,IvyBridge,Haswell,Broadwell stx-openstack nova openstack I check again /etc/nova/nova.conf inside pod, and still saw just 'cpu_mode = host-model' Is this configuration be modified? If yes, how can I do it? Also I could create flavors and instances with below configurations: trait:HW_CPU_X86_AVX='required' trait:HW_CPU_X86_AVX2='required' trait:HW_CPU_X86_AVX512F='required' One instance for each configuration and one instance with those three configuration in a same flavor. But, how can I check the CPU model in the instance? In the test cases I mention at the beginning of this threat it says that the instances with flavor property trait:HW_CPU_X86_AVX512F='required' should get ERROR, but it could be launched as ACTIVE. Regards. Juan Carlos Alonso -----Original Message----- From: wang.ya Sent: Monday, November 4, 2019 9:01 PM To: Hu, Yong ; Jones, Bruce E ; Alonso, Juan Carlos ; Troyer, Dean Cc: Cabrales, Ada Subject: Re: Patch Elimination Train version Hi, yong: *vCPU Models selection* feature has been completed in train release. The feature's workflow is as follow: 1. Configure the *cpu_models* option under [libvirt] module of nova-compute service. The *cpu_models* option is an ordered list of CPU models. It's sorted by CPU flags, from less to more. For example: kvm64, IvyBridge, Haswell In above example, kvm64 only has base flags, IvyBridge has flag *avx*, Haswell have both *avx* and *avx2*. Please note that the configured CPU models must compatible with compute node's host CPU. 2. Create/Set flavor with required traits. The nova compute will select the CPU model from [libvirt]/cpu_models which first meet the flavor's requested flags. For example: openstack flavor set 1 --property trait:HW_CPU_X86_AVX=required In above example, we mark the flavor request flag *avx*, if the CPU of compute node has flag *avx*, then the instance can be scheduled success and created with CPU model IvyBridge, otherwise the API call will get an error: "No valid host". Spec: http://specs.openstack.org/openstack/nova-specs/specs/train/approved/cpu-model-selection.html Code: https://review.opendev.org/#/q/status:merged+project:openstack/nova+branch:master+topic:bp/cpu-model-selection Hope the above info can help you. Also, I'll online in today's meeting :) Best Regards On 2019/11/5, 9:13 AM, "Yong Hu" wrote: + Wang Ya. Hi Ya, I remember your team has been upstreaming the related patches. Could you share some info with us here or in the meeting tonight? regards, Yong On 2019/11/5 6:37 AM, Jones, Bruce E wrote: > + Dean and Yong (the new PL for the OpenStack team) > > AFAIK the CPU model changes that went into Train are internal only and > don’t impact OpenStack operation. > > Suggest you bring all of this to the distro.openstack meeting tomorrow > where it can be discussed with the right people. > > brucej > > *From:* Alonso, Juan Carlos > *Sent:* Monday, November 4, 2019 2:30 PM > *To:* Jones, Bruce E > *Cc:* Cabrales, Ada > *Subject:* Patch Elimination Train version > > Hi Bruce, > > In last test plan for Patch Elimination Stein version, there was some > *vCPU Model (Nova)* feature test cases that was marked as Unlikely status: > > 1. Create a flavor without any extra specs. Launch instance using this > flavor. Check instance cpu_model is 'kvm64' > > 2. Create a flavor with extra specs: 'trait:HW_CPU_X86_AVX2=required'. > Launch instance using this flavor. Check instance is Haswell and is in > compute node 2. > > 3. Create a flavor with extra specs: > 'trait:HW_CPU_X86_AVX512F=required'. Launch instance using this flavor. > Check API call get an error because no compute node has property 'avx512F'. > > 4. Create a flavor with multiple extra specs: 'trait:xxx'. Launch > instance using this flavor. > > 5. Create a flavor and ignoring cpu_model. Launch instance using this > flavor. > > For Train version, is such *vCPU Model (Nova)* feature still out? > > Also, there was some Live Migration Bugs table related to Neutron: > > Enable delete bound trunk for linux bridge agent > > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00) > > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731) > > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911) > > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6) > > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7) > > Prevent DHCP from processing stale RPC messages > > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89) > > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491) > > I need to know if such features/tests are going to be testes or not, can > you help me to verify? > > Test Plan for Stein: > https://docs.google.com/spreadsheets/d/1jsTyzy1HT7VR4EUsbBRaTYvs0BlXeGWkhLD0pJmFChc/edit#gid=1511025137 > > Test Plan for Train: > https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?pli=1#gid=184151983 > > Regards. > > Juan Carlos Alonso > From yong.hu at intel.com Thu Nov 7 01:09:33 2019 From: yong.hu at intel.com (Yong Hu) Date: Thu, 7 Nov 2019 09:09:33 +0800 Subject: [Starlingx-discuss] Error while installing StarlingX Openstack on all-in-one simplex In-Reply-To: References: Message-ID: <72561858-760a-a7e4-fbe8-d0c246f7a191@intel.com> Hi Sai, Could you share the download URL for the installation image (.iso)? As well you can tell the build info by: cat /etc/build.info I wonder your issue was caused by a mismatch b/w StarlingX platform and this stx-openstack tarball. regards, Yong On 2019/11/4 7:43 PM, Saichandu Behara wrote: > Hello all, > > I am trying to install StarlingX OpenStack on all-in-one simplex . When > i am installing application manifest and helm-charts, getting some > versioning error. > > I downloaded Package from " > http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.0/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz > " and > "http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz > " ( Both are getting errors ). > > I'm trying to upload the package by using command  " system > application-upload stx-openstack-1.0-17-centos-stable-latest.tgz " > > +---------------+----------------------------------+ > | Property      | Value                            | > +---------------+----------------------------------+ > | active        | False                            | > | app_version   | 1.0-17-centos-stable-latest      | > | created_at    | 2019-11-04T11:05:19.899672+00:00 | > | manifest_file | stx-openstack.yaml               | > | manifest_name | armada-manifest                  | > | name          | stx-openstack                    | > | progress      | None                             | > | status        | uploading                        | > | updated_at    | None                             | > +---------------+----------------------------------+ > > > and when i checking the application list, getting upload failed. > +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ > | application         | version                   | manifest > name                 | manifest file  | status        | > progress                                  | > +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ > | platform-integ-apps | 1.0-7                     | > platform-integration-manifest | manifest.yaml  | applied       | > completed                                 | > *| stx-openstack       | 1.0-17-centos-stable-     | > armada-manifest               | stx-openstack. | **upload-failed**| > Upload of application stx-openstack (1.   |** > **|                     | latest |                               | > yaml           |               | 0-17-centos-stable-latest) > failed:        |** > **|                     | | > |                |               | Unsupported application version. *      | > |                     | |                               | > | |                                           | > +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ > > If anyone is aware of this issue, please let us know. It would be a > great help. > > -- > Thanks & Regards > Sai Chandu Behara > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From saichandu.behara at calsoftinc.com Thu Nov 7 05:31:07 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Thu, 7 Nov 2019 11:01:07 +0530 Subject: [Starlingx-discuss] Error while installing StarlingX Openstack on all-in-one simplex In-Reply-To: <72561858-760a-a7e4-fbe8-d0c246f7a191@intel.com> References: <72561858-760a-a7e4-fbe8-d0c246f7a191@intel.com> Message-ID: Hi yong, I have downloaded the StarlingX R2 iso image and dated as around sep 22,2019. At present i don't have exact link, because, the build dates are changed now. But, I have downloaded the .iso in " http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ " latest build. Build info ::: controller-0:~$ cat /etc/build.info ### ### StarlingX ### Built from master ### OS="centos" SW_VERSION="19.09" BUILD_TARGET="Host Installer" BUILD_TYPE="Formal" BUILD_ID="20190920T013000Z" JOB="STX_build_master_master" BUILD_BY="starlingx.build at cengn.ca" BUILD_NUMBER="256" BUILD_HOST="starlingx_mirror" BUILD_DATE="2019-09-20 01:30:00 +0000" Please let me know for future solution. It would be a great help. Thanks & Regards Sai Chandu Behara On 07-11-2019 06:39, Yong Hu wrote: > Hi Sai, > Could you share the download URL for the installation image (.iso)? > As well you can tell the build info by: > cat /etc/build.info > > I wonder your issue was caused by a mismatch b/w StarlingX platform > and this stx-openstack tarball. > > regards, > Yong > > On 2019/11/4 7:43 PM, Saichandu Behara wrote: >> Hello all, >> >> I am trying to install StarlingX OpenStack on all-in-one simplex . >> When i am installing application manifest and helm-charts, getting >> some versioning error. >> >> I downloaded Package from " >> http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.0/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >> " and >> "http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >> " ( Both are getting errors ). >> >> I'm trying to upload the package by using command " system >> application-upload stx-openstack-1.0-17-centos-stable-latest.tgz " >> >> +---------------+----------------------------------+ >> | Property | Value | >> +---------------+----------------------------------+ >> | active | False | >> | app_version | 1.0-17-centos-stable-latest | >> | created_at | 2019-11-04T11:05:19.899672+00:00 | >> | manifest_file | stx-openstack.yaml | >> | manifest_name | armada-manifest | >> | name | stx-openstack | >> | progress | None | >> | status | uploading | >> | updated_at | None | >> +---------------+----------------------------------+ >> >> >> and when i checking the application list, getting upload failed. >> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >> >> | application | version | manifest >> name | manifest file | status | >> progress | >> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >> >> | platform-integ-apps | 1.0-7 | >> platform-integration-manifest | manifest.yaml | applied | >> completed | >> *| stx-openstack | 1.0-17-centos-stable- | >> armada-manifest | stx-openstack. | **upload-failed**| >> Upload of application stx-openstack (1. |** >> **| | latest | | yaml | | >> 0-17-centos-stable-latest) failed: |** >> **| | | | | | >> Unsupported application version. * | >> | | | | | >> | | >> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >> >> >> If anyone is aware of this issue, please let us know. It would be a >> great help. >> >> -- >> Thanks & Regards >> Sai Chandu Behara >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > -- Thanks & Regards Sai Chandu Behara From yan.chen at intel.com Thu Nov 7 06:14:38 2019 From: yan.chen at intel.com (Chen, Yan) Date: Thu, 7 Nov 2019 06:14:38 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: Message-ID: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> Carlos, Please remove Horizon/CSRF AngularJS Fixes related cases in your test plan, which are originally planned for STX additional patches, as those patches are already removed from our project and not upstreamed. Yan From: Alonso, Juan Carlos Sent: Wednesday, November 6, 2019 23:18 To: Hu, Yong ; Chen, Yan ; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: RE: Train patch elimination Hello, I hope also the community can help with this questions. @Chen, Yan Can you help me to verify if this feature is still disabled on Train version: Horizon/CSRF AngularJS Fixes ? On last test plan for Stein this feature was no longer required on Horizon and was disabled on SarlingX code. @Gerry.Kopec at windriver.com About the Live Migration bugs I mentioned on the last meeting, almost all of them are merged, except the last three. All those patches are related to live migration, so my question is if I perform live migrations such patches will be covered or should be tested in a different way? The last three were marked as Unlikely and was not merged on Stein. I don't have more info about such patches. Enable delete bound trunk for linux bridge agent: https://review.opendev.org/#/c/605589 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): https://review.opendev.org/#/c/623401 and https://review.opendev.org/#/c/626109 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): https://review.opendev.org/#/c/625134 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): https://review.opendev.org/#/c/628071 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): https://review.opendev.org/#/c/623415 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): https://review.opendev.org/#/c/621507/ Prevent DHCP from processing stale RPC messages: ?? 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Nov 7 06:46:54 2019 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 6 Nov 2019 22:46:54 -0800 Subject: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 In-Reply-To: <000001d5924b$34b99e00$9e2cda00$@neusoft.com> References: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> <393877e4-b8d8-59b1-a634-7f405daf00bf@linux.intel.com> <000001d5924b$34b99e00$9e2cda00$@neusoft.com> Message-ID: <32e63a7d-b7b5-8746-d902-bfe9ed4ffb37@linux.intel.com> On 11/3/19 5:32 AM, zhao.shuai wrote: > Hi Saul, Haitao, Shuicheng, > Thank you for your hard work and positive response. > As you suggested in the last StarlingX non-OpenStack distro meeting, > Our team should use Google Docs Or gitHub to show our progress and results in a more real-time way. > Recently, we have moved our work and progress reports to Github. > The StarlingX kernel version to CentOS 4.18 work path is as follows: > https://github.com/StarlingX-Neusoft/Centos8 > I would like to see this work moved to a feature branch in gerrit, so that reviews can happen regularly. This will also allow for builds to be done from that branch once it's futher along. It require an occasional re-base, but we should not have too many conflicts in the integ, compile or utilities repos. > During the porting process, we will update our real-time Q&A information in the documents (StarlingX_CentOS8.0_Kernel_Upgrade_Q&A List.xls). > We hope that the experts in the community can check the problems we have when you have time. > If you can get your advice, we will be very honored. Thank you! > > ① >>Can you explain what you are referring to when you say Patch4000*, I > >>don't know which ones they map to? > Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx > Sheet: [STX Kernel-std Patches Details] STD-Status = Patch > Ok, I found the Excel sheet, but I am still not seeing any mapping to Patch4000* numbering. > ② >>Do you mean "Binary RPM" here? We should be trying to use the latest > >>binary RPMs from CentOS-8 (el8). > Yes, we hope to try this way. > Please see: https://github.com/StarlingX-Neusoft/Centos8/tree/master/cgcs-root/stx > It will take some time to review what you have there, but as suggested above we should create a feature branch for this work to occur in. This will allow your changes to be reviewed via gerrit. One very quick observation is that you should not remove the older Signed-off-by: tags when you rebase the patches. You should add yours to the existing ones, that preserves the identity of who has worked on the patch. > ③ >>We want to fully understand what patches are changing or what additional > >>patches you think you need to add. > Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx > Sheet: [srpm] Column E =【CentOS8 SRPM packages(El8)】 Looking at the missing list, it looks like alot of Puppet and OpenStack related python, have you look at puppetlabs for their el8 based repo here: https://yum.puppetlabs.com and https://yum.puppetlabs.com/puppet-release-el-8.noarch.rpm will help setup the repo on a target system. The OpenStack package will come later. Sau! > > ④ >>We need a better method to understand what changes are getting made > >>between these spreadsheet changes. I am not understanding your actual changes. > we have moved our work and progress reports to Github. > Please see: https://github.com/StarlingX-Neusoft/Centos8 > Thanks I have downloaded this repo and will review the history there also. > Thank you very much! > > Best Regards > Wish you happy everyday! > -------------------------------- > Shuai - Neusoft > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2019年11月2日 2:28 > 收件人: starlingx-discuss at lists.starlingx.io > 主题: Re: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 > > I think this message got stuck in the queue, I am just seeing it now. > > On 10/30/19 4:17 AM, zhao.shuai wrote: >> Hi StarlingX Community: >> >> Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. >> >> Completed Task: >> 1. GCC compiler version upgrade --> GCC version 8.2.1 >> 2. Kernel 4.18 with starlingX patch compilation has been completed.(Patch40004,Patch40007,Patch40008) >> > Can you explain what you are referring to when you say Patch4000*, I > don't know which ones they map to? > >> Doing Task: >> 1. src rpm package el8 upgrade(if there is el8 version) > Do you mean "Binary RPM" here? We should be trying to use the latest > binary RPMs from CentOS-8 (el8). > >> 2. If there is no el8 version of SRPM compilation failed, we need to build a patch fix it. > We want to fully understand what patches are changing or what additional > patches you think you need to add. > >> 3. Configure kernel 4.18 config file with reference to STX kernel 3.10 config file (kernel-3.10.0-x86_64.config.tis_extra) > >> 4. For the el8 version SRPM package that fails to be compiled, the RPM package of the el8 version is preferentially searched for replacement. >> >> Please see the attachment for the results of the advancement >> > We need a better method to understand what changes are getting made > between these spreadsheet changes. I am not understanding your actual > changes. > > Thanks > Sau! > > >> Thank you! >> >> Best Regards >> Wish you happy everyday! >> -------------------------------- >> Shuai - Neusoft >> >> >> -----邮件原件----- >> 发件人: Saul Wold >> 发送时间: 2019年10月18日 5:36 >> 收件人: starlingx-discuss at lists.starlingx.io >> 抄送: Rowsell, Brent >> 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting >> >> >> Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. >> >> As mentioned, most of the patches can be dropped, except for the Notification of Death patch. >> >> My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). >> >> Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. >> >> Sau! >> >> >> >> >> On 10/16/19 6:53 AM, Xie, Cindy wrote: >>> Agenda & notes for 10/16 meeting: >>> >>> . Ceph containerization update (Tingjie) >>> https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. >>> https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. >>> verified in AIO and multi-node provision. >>> configuration needs to be override according to STX parameters. >>> Martin working on this for parameters to align w/ the native deployment. >>> for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. >>> test case development is in progress, Tingjie will sync with Fernando. >>> for sysinv, still need to working on patches, not ready for upload/review. >>> AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. >>> >>> . Debranding update (Saul) >>> Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. >>> https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. >>> >>> . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: >>> https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. >>> https://storyboard.openstack.org/#!/story/2006729 >>> Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. >>> AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. >>> See >>> https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu >>> gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details >>> https://github.com/xe1gyq/linux/commits/v4.19 >>> https://github.com/xe1gyq/linux/commits/v4.18 >>> AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX >>> and in CentOS 8.0 >>> >>> . Opens - none >>> _____________________________________________ >>> From: Xie, Cindy >>> Sent: Tuesday, October 15, 2019 9:39 PM >>> To: Wold, Saul ; >>> 'starlingx-discuss at lists.starlingx.io' >>> ; 'Rowsell, Brent' >>> >>> Subject: RE: Weekly StarlingX non-OpenStack distro meeting >>> >>> >>> Agenda: >>> - Ceph containerization update (Tingjie) >>> - Debranding update (Saul) >>> - CentOS 8 upgrade planning (Cindy) >>> - Opens >>> >>> Cindy Xie >>> IAGS >>> >>> http://starlingx.io/ >>> >>> >>> -----Original Appointment----- >>> From: Xie, Cindy >>> Sent: Thursday, April 25, 2019 5:42 PM >>> To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' >>> Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; >>> 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, >>> Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, >>> Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W >>> Subject: Weekly StarlingX non-OpenStack distro meeting >>> When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. >>> Where: https://zoom.us/j/342730236 >>> >>> >>> . Cadence and time slot: >>> o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . >>> Call Details: >>> o Zoom link: https://zoom.us/j/342730236 o 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 >>> . Meeting Agenda and Minutes: >>> o https://etherpad.openstack.org/p/stx-distro-other >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> >> --------------------------------------------------------------------------------------------------- >> Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) >> is intended only for the use of the intended recipient and may be confidential and/or privileged of >> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is >> not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying >> is strictly prohibited, and may be unlawful.If you have received this communication in error,please >> immediately notify the sender by return e-mail, and delete the original message and all copies from >> your system. Thank you. >> --------------------------------------------------------------------------------------------------- >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > From zhipengs.liu at intel.com Thu Nov 7 08:53:51 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 7 Nov 2019 08:53:51 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DF8B@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> <90f7df72-202d-2558-c9e6-cc04fd7d6689@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DF8B@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C7530F60D5@SHSMSX104.ccr.corp.intel.com> Hi Barton, I have tested it with train engineering build today and pass! 2019-11-07 02:33:46.114 Test Instance-Pause ........................................ [OKAY] (2019-11-07 02:34:03.143 Δ=0:00:15.705) 2019-11-07 02:34:22.461 Test Instance-Unpause ...................................... [OKAY] (2019-11-07 02:34:29.069 Δ=0:00:05.879) 2019-11-07 02:34:43.772 Test Instance-Suspend ...................................... [OKAY] (2019-11-07 02:34:50.718 Δ=0:00:05.979) 2019-11-07 02:35:05.504 Test Instance-Resume ....................................... [OKAY] (2019-11-07 02:35:13.117 Δ=0:00:06.686) 2019-11-07 02:35:27.728 Test Instance-Reboot (soft) ................................ [OKAY] (2019-11-07 02:37:38.259 Δ=0:02:09.730) 2019-11-07 02:37:56.491 Test Instance-Reboot (hard) ................................ [OKAY] (2019-11-07 02:38:10.572 Δ=0:00:13.240) 2019-11-07 02:38:30.390 Test Instance-Stop ......................................... [OKAY] (2019-11-07 02:39:44.231 Δ=0:01:12.920) 2019-11-07 02:40:02.574 Test Instance-Start ........................................ [OKAY] (2019-11-07 02:40:09.293 Δ=0:00:05.941) 2019-11-07 02:40:24.714 Test Instance-Live-Migrate ................................. [OKAY] (2019-11-07 02:40:51.549 Δ=0:00:26.019) 2019-11-07 02:41:10.837 Test Instance-Cold-Migrate ................................. [OKAY] (2019-11-07 02:42:39.383 Δ=0:01:27.523) 2019-11-07 02:42:57.811 Test Instance-Cold-Migrate-Confirm ......................... [OKAY] (2019-11-07 02:43:04.873 Δ=0:00:06.199) 2019-11-07 02:43:20.031 Test Instance-Cold-Migrate-Revert .......................... [OKAY] (2019-11-07 02:45:06.808 Δ=0:00:25.094) 2019-11-07 02:45:26.019 Test Instance-Resize ....................................... [OKAY] (2019-11-07 02:46:54.315 Δ=0:01:26.712) 2019-11-07 02:47:13.467 Test Instance-Resize-Confirm ............................... [OKAY] (2019-11-07 02:47:20.348 Δ=0:00:06.114) 2019-11-07 02:47:35.183 Test Instance-Resize-Revert ................................ [OKAY] (2019-11-07 02:49:23.016 Δ=0:00:25.547) 2019-11-07 02:49:41.797 Test Instance-Rebuild ...................................... [OKAY] (2019-11-07 02:50:55.560 Δ=0:01:13.040) Total-Tests: 16 Execution-Time: 0:17:27.933 Thanks! Zhipeng -----Original Message----- From: Wensley, Barton Sent: 2019年11月6日 20:47 To: Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote: > Yong, > > Has someone run the VIM automated testing against the new load? See attached email for details. > > Bart > > -----Original Message----- > From: Yong Hu [mailto:yong.hu at intel.com] > Sent: November 5, 2019 9:47 AM > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, > ZhipengS; Lemus Contreras, Cristopher J > Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the > sanity, based on test results from testing team. (Thanks to @JC and > @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later > Zhipeng found the cause was from an non-standard test (cirros) image > which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > to RAW format. Why wasn't this issue seen with OpenStack Stein? > Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, > but it is now enabled by default in Train. Recommendation: later for > the testing, we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, > or other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the > inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate > new docker images for Openstack Train services and *upload them to > Docker Hub*. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cristopher.j.lemus.contreras at intel.com Thu Nov 7 09:05:09 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 07 Nov 2019 03:05:09 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$5rci77@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191107T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Barton.Wensley at windriver.com Thu Nov 7 12:39:15 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 7 Nov 2019 12:39:15 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <93814834B4855241994F290E959305C7530F60D5@SHSMSX104.ccr.corp.intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DD24@ALA-MBD.corp.ad.wrs.com> <90f7df72-202d-2558-c9e6-cc04fd7d6689@intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9DF8B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F60D5@SHSMSX104.ccr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58C1B9E750@ALA-MBD.corp.ad.wrs.com> Thanks Zhipeng - that is great news. Bart -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: November 7, 2019 3:54 AM To: Wensley, Barton; Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Barton, I have tested it with train engineering build today and pass! 2019-11-07 02:33:46.114 Test Instance-Pause ........................................ [OKAY] (2019-11-07 02:34:03.143 Δ=0:00:15.705) 2019-11-07 02:34:22.461 Test Instance-Unpause ...................................... [OKAY] (2019-11-07 02:34:29.069 Δ=0:00:05.879) 2019-11-07 02:34:43.772 Test Instance-Suspend ...................................... [OKAY] (2019-11-07 02:34:50.718 Δ=0:00:05.979) 2019-11-07 02:35:05.504 Test Instance-Resume ....................................... [OKAY] (2019-11-07 02:35:13.117 Δ=0:00:06.686) 2019-11-07 02:35:27.728 Test Instance-Reboot (soft) ................................ [OKAY] (2019-11-07 02:37:38.259 Δ=0:02:09.730) 2019-11-07 02:37:56.491 Test Instance-Reboot (hard) ................................ [OKAY] (2019-11-07 02:38:10.572 Δ=0:00:13.240) 2019-11-07 02:38:30.390 Test Instance-Stop ......................................... [OKAY] (2019-11-07 02:39:44.231 Δ=0:01:12.920) 2019-11-07 02:40:02.574 Test Instance-Start ........................................ [OKAY] (2019-11-07 02:40:09.293 Δ=0:00:05.941) 2019-11-07 02:40:24.714 Test Instance-Live-Migrate ................................. [OKAY] (2019-11-07 02:40:51.549 Δ=0:00:26.019) 2019-11-07 02:41:10.837 Test Instance-Cold-Migrate ................................. [OKAY] (2019-11-07 02:42:39.383 Δ=0:01:27.523) 2019-11-07 02:42:57.811 Test Instance-Cold-Migrate-Confirm ......................... [OKAY] (2019-11-07 02:43:04.873 Δ=0:00:06.199) 2019-11-07 02:43:20.031 Test Instance-Cold-Migrate-Revert .......................... [OKAY] (2019-11-07 02:45:06.808 Δ=0:00:25.094) 2019-11-07 02:45:26.019 Test Instance-Resize ....................................... [OKAY] (2019-11-07 02:46:54.315 Δ=0:01:26.712) 2019-11-07 02:47:13.467 Test Instance-Resize-Confirm ............................... [OKAY] (2019-11-07 02:47:20.348 Δ=0:00:06.114) 2019-11-07 02:47:35.183 Test Instance-Resize-Revert ................................ [OKAY] (2019-11-07 02:49:23.016 Δ=0:00:25.547) 2019-11-07 02:49:41.797 Test Instance-Rebuild ...................................... [OKAY] (2019-11-07 02:50:55.560 Δ=0:01:13.040) Total-Tests: 16 Execution-Time: 0:17:27.933 Thanks! Zhipeng -----Original Message----- From: Wensley, Barton Sent: 2019年11月6日 20:47 To: Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: RE: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Yong, To reply to your comments: 1). we don't upgrade Openstack clients at this time as agreed previously. The VIM doesn't use the OpenStack clients - it uses the OpenStack REST APIs directly. Often we find that when OpenStack is upversioned there can be things deprecated in the OpenStack REST APIs that break the VIM's use of these APIs. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. The fixes would be in StarlingX - not upstream. We would need to update the VIM to use the modified REST APIs. I prefer that we do this testing ahead of time instead of waiting for things to break and fixing the problems after the fact. Bart -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: November 5, 2019 10:25 PM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, ZhipengS; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Bart, It's a fair requirement, and I would suggest to run this test on the build image from Cengn after these patches merged, because: 1). we don't upgrade Openstack clients at this time as agreed previously. 2). in case we detect some issues caused by Openstack API changes, we can either fix them in StarlingX or get resolution from OpenStack upstream. regards, Yong On 2019/11/5 11:11 PM, Wensley, Barton wrote: > Yong, > > Has someone run the VIM automated testing against the new load? See attached email for details. > > Bart > > -----Original Message----- > From: Yong Hu [mailto:yong.hu at intel.com] > Sent: November 5, 2019 9:47 AM > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Liu, > ZhipengS; Lemus Contreras, Cristopher J > Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the > sanity, based on test results from testing team. (Thanks to @JC and > @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later > Zhipeng found the cause was from an non-standard test (cirros) image > which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > to RAW format. Why wasn't this issue seen with OpenStack Stein? > Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, > but it is now enabled by default in Train. Recommendation: later for > the testing, we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, > or other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the > inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate > new docker images for Openstack Train services and *upload them to > Docker Hub*. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From juan.carlos.alonso at intel.com Thu Nov 7 15:56:09 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 7 Nov 2019 15:56:09 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> Message-ID: Hello Yan, Thank you for your response. Same question now for: Horizon/Custom Confirmation Messages : Custom confirmation message for Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor. I added the bmc_ip, bmc_type, bmc_username and bmc_password for each node, but I cannot display any sensors on Horizon nor CLI. $ system host-update compute-0 bm_username= bm_password= bm_type=bmc bm_ip= $ system host-lock compute-0 $ system host-sensor-list compute-0 $ system host-unlock compute-0 $ system host-sensor-list compute-0 Is there any other configuration needed or is this feature not supported anymore? Regards. Juan Carlos Alonso From: Chen, Yan Sent: Thursday, November 7, 2019 12:15 AM To: Alonso, Juan Carlos ; Hu, Yong ; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: RE: Train patch elimination Carlos, Please remove Horizon/CSRF AngularJS Fixes related cases in your test plan, which are originally planned for STX additional patches, as those patches are already removed from our project and not upstreamed. Yan From: Alonso, Juan Carlos > Sent: Wednesday, November 6, 2019 23:18 To: Hu, Yong >; Chen, Yan >; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada > Subject: RE: Train patch elimination Hello, I hope also the community can help with this questions. @Chen, Yan Can you help me to verify if this feature is still disabled on Train version: Horizon/CSRF AngularJS Fixes ? On last test plan for Stein this feature was no longer required on Horizon and was disabled on SarlingX code. @Gerry.Kopec at windriver.com About the Live Migration bugs I mentioned on the last meeting, almost all of them are merged, except the last three. All those patches are related to live migration, so my question is if I perform live migrations such patches will be covered or should be tested in a different way? The last three were marked as Unlikely and was not merged on Stein. I don't have more info about such patches. Enable delete bound trunk for linux bridge agent: https://review.opendev.org/#/c/605589 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): https://review.opendev.org/#/c/623401 and https://review.opendev.org/#/c/626109 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): https://review.opendev.org/#/c/625134 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): https://review.opendev.org/#/c/628071 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): https://review.opendev.org/#/c/623415 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): https://review.opendev.org/#/c/621507/ Prevent DHCP from processing stale RPC messages: ?? 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Nov 7 18:40:55 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 7 Nov 2019 18:40:55 +0000 Subject: [Starlingx-discuss] Subject: [docs][meetings] docs team meeting minutes 2019-11-06 Message-ID: <43F963BD1517044B90CF82FB2F3CA71622081608@ORSMSX121.amr.corp.intel.com> Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2019-11-06 * All -- reviews in progress and recent merges -- ? See summary at https://review.opendev.org/#/q/project:starlingx/docs. ? Recent merges: * https://review.opendev.org/#/c/692237/ * https://review.opendev.org/#/c/684820/ ? 4 open: * https://review.opendev.org/#/c/691804/ - good discussion. Ready for editorial? Needs formatting clean up + misc to bring inline w/ standard. (Mary) * https://review.opendev.org/#/c/692202/ - first draft STX in a box, needs review (Abraham) * https://review.opendev.org/#/c/689847/ - STX dist cloud. Ongoing activity and review - should be ready for review by end of week. Abraham will notify Kris. * https://review.opendev.org/#/c/691740/ - docs process doc * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs ? https://bugs.launchpad.net/starlingx/+bug/1849336 -- Not a bug (see comment) - closed ? https://bugs.launchpad.net/starlingx/+bug/1849341 -- Review submitted to fix -- https://review.opendev.org/#/c/692237/ - closed ? https://bugs.launchpad.net/starlingx/+bug/1835207 - ongoing (Abraham) ? https://bugs.launchpad.net/starlingx/+bug/1837931 - Reopened (log new?) - will need Greg/Abraham re content * Kris - R2.0.2 EOY ? Do we need to create a branch off R2.0 docs? no. This update is for bug fixes. ? This will require release notes. ? R3 is not delayed. * Kris -- Open tasks for R3: ? http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.html * This may impact all general install instructions (making sure versions align across all needed files/packages) ? Ansible: - Create new Story w/ tasks for tracking * ansible - refactor param: https://drive.google.com/open?id=17T90sQcGkQ2OH0Jorar-pbIE1j-piYQ1 * ansible - install time config: https://drive.google.com/open?id=1UZCN3_Q_siHrcwccBTAsIc6iPg7pPnCx (is this R3 only?). Need to ID best place to include this info. ? TSN contribution is in progress: (subtask 36405 in https://storyboard.openstack.org/#!/story/2006289) * https://drive.google.com/file/d/1IQZVTEHRra72wNOHiIXD5Y-DKiFkl7yZ * Le, Huifeng is working on this ? STX in a box: (https://storyboard.openstack.org/#!/story/2006622) * Draft in review https://review.opendev.org/#/c/692202/ * **Kris sent initial contact to Scott re hosting - Bill has AR to find long term home for Calsoft image - dup to what I asked? * Can Calsoft provide info re how they built the qcow2 images? (Bruce). - Bruce got a initial drop of content * https://drive.google.com/open?id=1c2WzC3E_FnoJMfFwADFj1FWOn4Fx8jvW * Long term: release specific images (Bruce) ** We have the instructions, now we need to figure out who is going to own building (Scott/cyngen) * Kris -- Structure for new config guide ? Do we want to draft this or wait for further review from Greg? ? Proceed with mapping exisitng to outline, plus draft new pages. (AR Kris) * Kris -- R3 Stories: http s://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 ? Target release in early Dec ? R3 release is currently planned for early December. ? https://storyboard.openstack.org/#!/story/2006576 - closed with previous review: https://review.opendev.org/#/c/687689/ ? The community team is tracking top stories. I submitted these two for the doc team -- https://drive.google.com/file/d/1dXFLc6f4d5MA2l7rRBMnfyk4X6wZ07wX ? R3.0 updates (new features, changes, etc.) - discuss with Greg on his return (WW46) - outline R3 features and changes that may impact docs. (Kris to prep) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gerry.Kopec at windriver.com Thu Nov 7 20:04:26 2019 From: Gerry.Kopec at windriver.com (Kopec, Gerald (Gerry)) Date: Thu, 7 Nov 2019 20:04:26 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: Message-ID: <58CF5BABC9A76946A638A0E8AE48D17378915A92@ALA-MBD.corp.ad.wrs.com> Hi, The patches you listed below are not live migration related and I'm not familiar with them. As they're in the networking area maybe check with Huifeng Le who's PL. Gerry From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Wednesday, November 06, 2019 10:18 AM To: Hu, Yong; Chen, Yan; Kopec, Gerald (Gerry); starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: RE: Train patch elimination Hello, I hope also the community can help with this questions. @Chen, Yan Can you help me to verify if this feature is still disabled on Train version: Horizon/CSRF AngularJS Fixes ? On last test plan for Stein this feature was no longer required on Horizon and was disabled on SarlingX code. @Gerry.Kopec at windriver.com About the Live Migration bugs I mentioned on the last meeting, almost all of them are merged, except the last three. All those patches are related to live migration, so my question is if I perform live migrations such patches will be covered or should be tested in a different way? The last three were marked as Unlikely and was not merged on Stein. I don't have more info about such patches. Enable delete bound trunk for linux bridge agent: https://review.opendev.org/#/c/605589 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): https://review.opendev.org/#/c/623401 and https://review.opendev.org/#/c/626109 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): https://review.opendev.org/#/c/625134 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): https://review.opendev.org/#/c/628071 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): https://review.opendev.org/#/c/623415 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): https://review.opendev.org/#/c/621507/ Prevent DHCP from processing stale RPC messages: ?? 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Nov 7 22:05:07 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 7 Nov 2019 22:05:07 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 11/07/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 199 Fail = 6 Blocked = 9 Not Run = 58 Obsolete = 2 Deferred = 0 Total executed = 205 Pass Rate = 97% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 154 Fail = 9 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 163 Pass Rate = 94% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon https://bugs.launchpad.net/starlingx/+bug/1849221 --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Nov 7 22:28:27 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 7 Nov 2019 22:28:27 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Nov 7/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15EC708@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - November 7 2019 stx.3.0 - Feature Status - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Upversion to train - Sanity passed for all configs. - VIM unit tests passed. Thanks Zhipeng! - Code under review: https://review.opendev.org/#/q/topic:train_upgrade+(status:open+OR+status:merged) - Can we try to get this in by Monday? - Openstack Regression Test Plan ready - Automated regression using robot & pyTest - 70 Manual test-cases - Expect 2wks for execution. Will start once code is merged in master - Feature testing is already in progress on Engineering Build - Distributed Cloud - As per Yang, testing will finish this week - Fault Containerization: - Need a re-test. Expect to be done by Nov 14 - Intel GPU support for K8s - Closed on incremental changes. One commit already merged and other is under review. - Needs a re-test (subset of TCs). Procedure slightly changed: user has to add the label explicitly. - Suggest to wait until https://review.opendev.org/#/c/691801/ is merged - Need doc info - Intel QAT support for K8s - Need a re-test (subset of TCs). Procedure slightly changed: user has to add the label explicitly. - Can use any build on or after Nov 7 - Need doc info - Infrastructure & Cluster Monitoring - Need doc info. Expect to send this next week. - MS-3 - Expect to declare myself by Nov 12 once train reviews are ready to merge - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 44% (no change) - Currently trying to hold date of Nov 22 - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 85% (up from 69%) - stx.3.0 Bugs - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 - Current Count: 87 - Call to all PLs to start focusing on bug resolution / triage stx.4.0 - Expect readout from PTG next week - Etherpad updated based on PTG discussions - https://etherpad.openstack.org/p/stx.4.0-feature-candidates From maria.g.perez.ibarra at intel.com Thu Nov 7 23:43:25 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 7 Nov 2019 23:43:25 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191107 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-07 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006866.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Nov 7 23:45:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 7 Nov 2019 23:45:07 +0000 Subject: [Starlingx-discuss] How to configure compute note PTP as Master In-Reply-To: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> References: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> Message-ID: <9A85D2917C58154C960D95352B22818BED36388A@fmsmsx121.amr.corp.intel.com> Huifeng, Forrest? Can you answer this please? brucej From: Philip_Wang at alphanetworks.com [mailto:Philip_Wang at alphanetworks.com] Sent: Monday, November 4, 2019 6:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to configure compute note PTP as Master Hi Team, Below is PTP architecture in StarlingX. [cid:image002.png at 01D59582.378B49A0] We need connect a host device that need PTP time sync on compute node. But in StarlingX compute node is slave. - How can we configure or modified PTP in StarlingX let compute node can be Master/Slave BC mode. - Or what architecture should be in StarlingX support host device need PTP time sync. Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 64801 bytes Desc: image002.png URL: From huifeng.le at intel.com Fri Nov 8 01:54:50 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Fri, 8 Nov 2019 01:54:50 +0000 Subject: [Starlingx-discuss] How to configure compute note PTP as Master In-Reply-To: <9A85D2917C58154C960D95352B22818BED36388A@fmsmsx121.amr.corp.intel.com> References: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> <9A85D2917C58154C960D95352B22818BED36388A@fmsmsx121.amr.corp.intel.com> Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D645C9D@SHSMSX104.ccr.corp.intel.com> Matt, Could you please share your insight on this question for STX PTP support? Thanks much! Best Regards, Le, Huifeng From: Jones, Bruce E Sent: Friday, November 8, 2019 7:45 AM To: Le, Huifeng ; Zhao, Forrest Cc: Philip_Wang at alphanetworks.com; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] How to configure compute note PTP as Master Huifeng, Forrest? Can you answer this please? brucej From: Philip_Wang at alphanetworks.com [mailto:Philip_Wang at alphanetworks.com] Sent: Monday, November 4, 2019 6:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to configure compute note PTP as Master Hi Team, Below is PTP architecture in StarlingX. [cid:image001.png at 01D59619.E8F0C660] We need connect a host device that need PTP time sync on compute node. But in StarlingX compute node is slave. * How can we configure or modified PTP in StarlingX let compute node can be Master/Slave BC mode. * Or what architecture should be in StarlingX support host device need PTP time sync. Best Reagrds, * Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 64801 bytes Desc: image001.png URL: From zhipengs.liu at intel.com Fri Nov 8 01:55:15 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 8 Nov 2019 01:55:15 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> Message-ID: <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. From zhang.kunpeng at 99cloud.net Fri Nov 8 04:34:49 2019 From: zhang.kunpeng at 99cloud.net (=?UTF-8?B?5byg6bKy6bmP?=) Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) Subject: [Starlingx-discuss] =?utf-8?q?=5Bstarlingx-discuss=5D=5Bdistcloud?= =?utf-8?q?=5D_Some_questions_about_how_do_subclouds_use_central_cl?= =?utf-8?q?oud=27s_local_registry=2E?= Message-ID: Hi Tao, Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Nov 8 09:01:31 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 08 Nov 2019 03:01:31 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6uns3q@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191108T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From saichandu.behara at calsoftinc.com Fri Nov 8 12:08:25 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Fri, 8 Nov 2019 17:38:25 +0530 Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX all-in-one Simplex EdgeX with Openstack Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6@calsoftinc.com> Hello all, We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. We have two images. StarlingX without Openstack and StarlingX with Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one EdgeX simplex. We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. -- Thanks & Regards Sai Chandu Behara From kris at inuits.eu Fri Nov 8 12:15:44 2019 From: kris at inuits.eu (Kris Buytaert) Date: Fri, 08 Nov 2019 13:15:44 +0100 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph Message-ID: I`m working my way trough https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html but on step 5. Add an OSD on controller-0 for ceph: the host-stor-add controllor0 command returns with the following error. [root at controller-0 etc(keystone_admin)]# system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. Any ideas how to fix this ? greetings Kris From ran1.an at intel.com Fri Nov 8 12:50:19 2019 From: ran1.an at intel.com (An, Ran1) Date: Fri, 8 Nov 2019 12:50:19 +0000 Subject: [Starlingx-discuss] summary of discussions in China StarlingX WeChat Group Message-ID: <9BAB5B7CAF57C3459E4636391F1071CE0534D680@shsmsx102.ccr.corp.intel.com> Hi all: The China StarlingX WeChat group was created during the StarlingX 2.0 Meetup (Beijing) on 24th Sept. Currently there are 135 members from Intel, 99cloud, WindRiver, China Unicom, China Telecom, Fiberhome, ZTE and other companies. (Maybe someone from China Mobile) The hottest topic in the WeChat group is about deployment. The discussions covered all versions of starlingX (stx1.0, stx 2.0 and master branch). Customer configuration is also frequently discussed/asked there. Other topics such as openstack domain name (service name), bluestore of ceph, raid card supported were mentioned. In addition, we are glad to see some contributors share their experiences in the group, like: 1. an offline deployment tutorial of stx 2.0[1] from KunpengZhang at 99cloud. 2. an docker registry for Chinese users is built by bin.yang at intel and contributors from Neusoft. The tutorial can be got from [2] Specifically, these topics were discussed in the past week: Deploy problems (all solved in the WeChat group): 1. some pods kept on pending status (from ZTE, version 2.0) Solution: the Kubernetes worker node on compute nodes were not ready, solved by adding network for compute node manually. 2. ansible processing was blocked at docker images download stage. (master branch) Solution: local registry did not take effect. Format of ansible file was incorrect (there are codes changes recently). 3. some pods of openstack failed to start for the request resource was larger than default limitation. (version 2.0) Solution: use cmd "system helm-override-update modify pod.resources. XXX" Questions: 1. does starlingX support real time kernel? (answered, yes) 2. how to transfer instances from old system to new one. (answered, use snapshot) 3. is there an efficient way to check the system status and find the key point during deployment processing. (request a proper answer) [1] https://github.com/zhangkunpeng/starlingx/blob/master/host-unlock/stx-2.0/deployment.md [2] https://pan.baidu.com/s/1EEk6j17NC8uc5zhKzW-hlw fetch code: t2ix Thanks for your attention Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Nov 8 13:13:00 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 8 Nov 2019 13:13:00 +0000 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> Hi Kris Before you run this command, are you sure "system mode: simplex" in localhost.yml $ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml You can check this in your system $ cat /etc/platform/platform.conf BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Friday, November 8, 2019 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 70 Send Starlingx-discuss mailing list submissions to starlingx-discuss at 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 at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. (Liu, ZhipengS) 2. [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. (张鲲鹏) 3. StarlingX platform-integ-apps docker images (cristopher.j.lemus.contreras at intel.com) 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX with Openstack (Saichandu Behara) 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) ---------------------------------------------------------------------- Message: 1 Date: Fri, 8 Nov 2019 01:55:15 +0000 From: "Liu, ZhipengS" To: "Hu, Yong" , "starlingx-discuss at lists.starlingx.io" , "Alonso, Juan Carlos" , "Lemus Contreras, Cristopher J" Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Message-ID: <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com> Content-Type: text/plain; charset="utf-8" Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. ------------------------------ Message: 2 Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) From: 张鲲鹏 To: tao.liu at windriver.com Cc: starlingx-discuss , "greg.waines" Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Message-ID: Content-Type: text/plain; charset="utf-8" Hi Tao, Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Fri, 08 Nov 2019 03:01:31 -0600 From: cristopher.j.lemus.contreras at intel.com To: Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191108T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 ------------------------------ Message: 4 Date: Fri, 8 Nov 2019 17:38:25 +0530 From: Saichandu Behara To: "Bill.Zvonar at windriver.com" , "starlingx-discuss at lists.starlingx.io" , bruce.e.jones at intel.com, cindy.xie at intel.com, sgw at linux.intel.com Cc: Pavan Gupta Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX all-in-one Simplex EdgeX with Openstack Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> Content-Type: text/plain; charset=utf-8; format=flowed Hello all, We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. We have two images. StarlingX without Openstack and StarlingX with Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one EdgeX simplex. We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. -- Thanks & Regards Sai Chandu Behara ------------------------------ Message: 5 Date: Fri, 08 Nov 2019 13:15:44 +0100 From: Kris Buytaert To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph Message-ID: Content-Type: text/plain; charset="UTF-8" I`m working my way trough https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html but on step 5. Add an OSD on controller-0 for ceph: the host-stor-add controllor0 command returns with the following error. [root at controller-0 etc(keystone_admin)]# system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. Any ideas how to fix this ? greetings Kris ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 70 ************************************************* From kris at inuits.eu Fri Nov 8 13:41:11 2019 From: kris at inuits.eu (Kris Buytaert) Date: Fri, 08 Nov 2019 14:41:11 +0100 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> Message-ID: <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote: > Hi Kris > > Before you run this command, are you sure "system mode: simplex" in localhost.yml > $ ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml > The localhost.yaml indeed does contain system_mode: simplex The platform.conf however not , so I updated that .. After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex I regtriggered the ansible run to be sure .. and even during that run with the config i noticed TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** changed: [localhost] => (item=prev_system_mode: duplex) changed: [localhost] => (item=prev_timezone: UTC) So somewhere it looks like it is taking in the wrong parameter .. I`ll dig deeper .. but if you have any hints on where to search ? greetings Kris > You can check this in your system > $ cat /etc/platform/platform.conf > > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io > Sent: Friday, November 8, 2019 8:30 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 18, Issue 70 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at 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 at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train > Upgrade Patches. (Liu, ZhipengS) > 2. [starlingx-discuss][distcloud] Some questions about how do > subclouds use central cloud's local registry. (张鲲鹏) > 3. StarlingX platform-integ-apps docker images > (cristopher.j.lemus.contreras at intel.com) > 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX > with Openstack (Saichandu Behara) > 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Nov 2019 01:55:15 +0000 > From: "Liu, ZhipengS" > To: "Hu, Yong" , > "starlingx-discuss at lists.starlingx.io" > , "Alonso, Juan Carlos" > , "Lemus Contreras, Cristopher J" > > Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for > review on OpenStack Train Upgrade Patches. > Message-ID: > <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com> > > Content-Type: text/plain; charset="utf-8" > > Hi all, > > So far I have not got new more comments. > I'd like to push this 6 patches get merged soon since fully sanity test pass! > > Could core reviewers final check them before adding review+2 for below 3 patches. > https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app > https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app > https://review.opendev.org/#/c/688105/ starlingx/root > > Thanks! > Zhipeng > -----Original Message----- > From: Hu, Yong > Sent: 2019年11月5日 22:47 > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J < > cristopher.j.lemus.contreras at intel.com> > Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of > Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. > > ------------------------------ > > Message: 2 > Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) > From: 张鲲鹏 > To: tao.liu at windriver.com > Cc: starlingx-discuss , > "greg.waines" > Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some > questions about how do subclouds use central cloud's local registry. > Message-ID: > > > Content-Type: text/plain; charset="utf-8" > > Hi Tao, Distributed Cloud team, > > > The distributed cloud feature is very cool, and I am concerned about its development always. > There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > > > Thanks > Kunpeng > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 3 > Date: Fri, 08 Nov 2019 03:01:31 -0600 > From: cristopher.j.lemus.contreras at intel.com > To: > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker > images > Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> > > List of docker images required for "platform-integ-apps": > > BUILD_ID="20191108T023000Z" > > rabbitmq:3.7-management > k8s.gcr.io/kube-proxy:v1.16.2 > k8s.gcr.io/kube-apiserver:v1.16.2 > k8s.gcr.io/kube-controller-manager:v1.16.2 > k8s.gcr.io/kube-scheduler:v1.16.2 > k8s.gcr.io/etcd:3.3.15-0 > k8s.gcr.io/coredns:1.6.2 > quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic > quay.io/calico/node:v3.6.2 > quay.io/calico/cni:v3.6.2 > quay.io/calico/kube-controllers:v3.6.2 > rabbitmq:3.7.13-management > rabbitmq:3.7.13 > gcr.io/kubernetes-helm/tiller:v2.13.1 > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 > openstackhelm/mariadb:10.2.18 > quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 > quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 > mariadb:10.2.13 > memcached:1.5.5 > k8s.gcr.io/pause:3.1 > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 > nginx:1.13.3 > gcr.io/google_containers/defaultbackend:1.0 > > > > > ------------------------------ > > Message: 4 > Date: Fri, 8 Nov 2019 17:38:25 +0530 > From: Saichandu Behara > To: "Bill.Zvonar at windriver.com" , > "starlingx-discuss at lists.starlingx.io" > , bruce.e.jones at intel.com, > cindy.xie at intel.com, sgw at linux.intel.com > Cc: Pavan Gupta > Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX > all-in-one Simplex EdgeX with Openstack > Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello all, > > We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. > > We have two images. StarlingX without Openstack and StarlingX with Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which > contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one EdgeX simplex. > > We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. > > -- > Thanks & Regards > Sai Chandu Behara > > > > > ------------------------------ > > Message: 5 > Date: Fri, 08 Nov 2019 13:15:44 +0100 > From: Kris Buytaert > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for > ceph > Message-ID: > Content-Type: text/plain; charset="UTF-8" > > > I`m working my way trough https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html > > but on step 5. Add an OSD on controller-0 for ceph: > > the host-stor-add controllor0 command returns with the following error. > > > [root at controller-0 etc(keystone_admin)]# system host-disk-list controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} > Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > > > Any ideas how to fix this ? > > greetings > > Kris > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 18, Issue 70 > ************************************************* From haochuan.z.chen at intel.com Fri Nov 8 14:08:08 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 8 Nov 2019 14:08:08 +0000 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph In-Reply-To: <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> References: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627E339@CDSMSX102.ccr.corp.intel.com> Current For your error " Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices." You could find this log in this file /usr/lib64/python2.7/site-packages/sysinv/api/controllers/v1/storage.py It check the stor_model. And this value is return from function in this file /usr/lib64/python2.7/site-packages/sysinv/common/ceph.py In ceph.py, it decide stor_model, by check system mode. For your provision guide, system mode should be simplex. And system mode in system database, it write by ansible command in this folder. /usr/share/ansible/stx-ansible/playbooks/bootstrap/roles/ You can check why you system mode is not correct. One attention is "localhost.yml" not "localhost.yaml" Double check in this linke https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html you can rename and run ansible playbook again to check. BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: Kris Buytaert Sent: Friday, November 8, 2019 9:41 PM To: Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: Failing to add an OSD on controller-0 for ceph On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote: > Hi Kris > > Before you run this command, are you sure "system mode: simplex" in > localhost.yml $ ansible-playbook > /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml > The localhost.yaml indeed does contain system_mode: simplex The platform.conf however not , so I updated that .. After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex I regtriggered the ansible run to be sure .. and even during that run with the config i noticed TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** changed: [localhost] => (item=prev_system_mode: duplex) changed: [localhost] => (item=prev_timezone: UTC) So somewhere it looks like it is taking in the wrong parameter .. I`ll dig deeper .. but if you have any hints on where to search ? greetings Kris > You can check this in your system > $ cat /etc/platform/platform.conf > > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: starlingx-discuss-request at lists.starlingx.io > > Sent: Friday, November 8, 2019 8:30 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Starlingx-discuss Digest, Vol 18, Issue 70 > > Send Starlingx-discuss mailing list submissions to > starlingx-discuss at 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 at lists.starlingx.io > > You can reach the person managing the list at > starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train > Upgrade Patches. (Liu, ZhipengS) > 2. [starlingx-discuss][distcloud] Some questions about how do > subclouds use central cloud's local registry. (张鲲鹏) > 3. StarlingX platform-integ-apps docker images > (cristopher.j.lemus.contreras at intel.com) > 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX > with Openstack (Saichandu Behara) > 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Nov 2019 01:55:15 +0000 > From: "Liu, ZhipengS" > To: "Hu, Yong" , > "starlingx-discuss at lists.starlingx.io" > , "Alonso, Juan Carlos" > , "Lemus Contreras, Cristopher J" > > Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for > review on OpenStack Train Upgrade Patches. > Message-ID: > > <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com > > > > Content-Type: text/plain; charset="utf-8" > > Hi all, > > So far I have not got new more comments. > I'd like to push this 6 patches get merged soon since fully sanity test pass! > > Could core reviewers final check them before adding review+2 for below 3 patches. > https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app > https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app > https://review.opendev.org/#/c/688105/ starlingx/root > > Thanks! > Zhipeng > -----Original Message----- > From: Hu, Yong > Sent: 2019年11月5日 22:47 > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos > ; Liu, ZhipengS > ; Lemus Contreras, Cristopher J < > cristopher.j.lemus.contreras at intel.com> > Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > Hi Core reviewers in Stx.distro.openstack: > > The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > https://review.opendev.org/#/c/683886/ > https://review.opendev.org/#/c/683910/ > https://review.opendev.org/#/c/684166/ > https://review.opendev.org/#/c/687441/ > https://review.opendev.org/#/c/687197/ > https://review.opendev.org/#/c/688105/ > > In addition, some background info related to this upgrade: > > 1). Originally there was a test failure in the sanity, but later > Zhipeng found the cause was from an non-standard test (cirros) image > which had 2 > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. > > 2). these patches have to be merged *in one batch* due to the inter-dependencies. > > 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. > > ------------------------------ > > Message: 2 > Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) > From: 张鲲鹏 > To: tao.liu at windriver.com > Cc: starlingx-discuss , > "greg.waines" > Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some > questions about how do subclouds use central cloud's local registry. > Message-ID: > > net> > > Content-Type: text/plain; charset="utf-8" > > Hi Tao, Distributed Cloud team, > > > The distributed cloud feature is very cool, and I am concerned about its development always. > There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > > > Thanks > Kunpeng > > > > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > 91108/ae122f8c/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Fri, 08 Nov 2019 03:01:31 -0600 > From: cristopher.j.lemus.contreras at intel.com > To: > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker > images > Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> > > List of docker images required for "platform-integ-apps": > > BUILD_ID="20191108T023000Z" > > rabbitmq:3.7-management > k8s.gcr.io/kube-proxy:v1.16.2 > k8s.gcr.io/kube-apiserver:v1.16.2 > k8s.gcr.io/kube-controller-manager:v1.16.2 > k8s.gcr.io/kube-scheduler:v1.16.2 > k8s.gcr.io/etcd:3.3.15-0 > k8s.gcr.io/coredns:1.6.2 > quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubun > tu_bionic > quay.io/calico/node:v3.6.2 > quay.io/calico/cni:v3.6.2 > quay.io/calico/kube-controllers:v3.6.2 > rabbitmq:3.7.13-management > rabbitmq:3.7.13 > gcr.io/kubernetes-helm/tiller:v2.13.1 > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 > openstackhelm/mariadb:10.2.18 > quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 > quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 > mariadb:10.2.13 > memcached:1.5.5 > k8s.gcr.io/pause:3.1 > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 > nginx:1.13.3 > gcr.io/google_containers/defaultbackend:1.0 > > > > > ------------------------------ > > Message: 4 > Date: Fri, 8 Nov 2019 17:38:25 +0530 > From: Saichandu Behara > To: "Bill.Zvonar at windriver.com" , > "starlingx-discuss at lists.starlingx.io" > , bruce.e.jones at intel.com, > cindy.xie at intel.com, sgw at linux.intel.com > Cc: Pavan Gupta > Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX > all-in-one Simplex EdgeX with Openstack > Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello all, > > We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. > > We have two images. StarlingX without Openstack and StarlingX with > Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one EdgeX simplex. > > We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. > > -- > Thanks & Regards > Sai Chandu Behara > > > > > ------------------------------ > > Message: 5 > Date: Fri, 08 Nov 2019 13:15:44 +0100 > From: Kris Buytaert > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for > ceph > Message-ID: > Content-Type: text/plain; charset="UTF-8" > > > I`m working my way trough > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio > _simplex_install_kubernetes.html > > but on step 5. Add an OSD on controller-0 for ceph: > > the host-stor-add controllor0 command returns with the following error. > > > [root at controller-0 etc(keystone_admin)]# system host-disk-list > controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > > > Any ideas how to fix this ? > > greetings > > Kris > > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > ------------------------------ > > End of Starlingx-discuss Digest, Vol 18, Issue 70 > ************************************************* From kris at inuits.eu Fri Nov 8 14:12:09 2019 From: kris at inuits.eu (Kris Buytaert) Date: Fri, 08 Nov 2019 15:12:09 +0100 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph In-Reply-To: <56829C2A36C2E542B0CCB9854828E4D85627E339@CDSMSX102.ccr.corp.intel.com> References: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> <56829C2A36C2E542B0CCB9854828E4D85627E339@CDSMSX102.ccr.corp.intel.com> Message-ID: > One attention is > "localhost.yml" not "localhost.yaml" that was a typo on my side .. > > Double check in this linke > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html > > you can rename and run ansible playbook again to check. > I just cleared the ansible.log and retriggered it again .. The log multiple times mentions duplex grep duplex ansible.log "msg": "System type is Standard, system mode will be set to duplex." 2019-11-05 20:53:28,995 p=13902 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ************************************************************************************************************************************************************************ 2019-11-05 20:53:32,967 p=13902 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-05 21:10:48,604 p=13902 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) "msg": "System type is Standard, system mode will be set to duplex." 2019-11-08 13:21:19,806 p=4110538 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* 2019-11-08 13:21:23,636 p=4110538 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-08 13:26:09,883 p=4110538 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) "msg": "System type is Standard, system mode will be set to duplex." 2019-11-08 13:30:38,866 p=4130039 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* 2019-11-08 13:30:42,673 p=4130039 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-08 13:34:33,158 p=4130039 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) I`m going to look closer at the ansible playbooks to see where this goes wrong. greetings Kris > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Kris Buytaert > Sent: Friday, November 8, 2019 9:41 PM > To: Chen, Haochuan Z > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: Failing to add an OSD on controller-0 for ceph > > On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote: > > Hi Kris > > > > Before you run this command, are you sure "system mode: simplex" in > > localhost.yml $ ansible-playbook > > /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml > > > > The localhost.yaml indeed does contain > > system_mode: simplex > > > The platform.conf however not , so I updated that .. > > After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex > > > > I regtriggered the ansible run to be sure .. and even during that run with the config i noticed > > TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** > changed: [localhost] => (item=prev_system_mode: duplex) > changed: [localhost] => (item=prev_timezone: UTC) > > So somewhere it looks like it is taking in the wrong parameter .. > > I`ll dig deeper .. but if you have any hints on where to search ? > > > greetings > > Kris > > > > > > > > > You can check this in your system > > $ cat /etc/platform/platform.conf > > > > BR! > > > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > > > -----Original Message----- > > From: starlingx-discuss-request at lists.starlingx.io > > > > Sent: Friday, November 8, 2019 8:30 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: Starlingx-discuss Digest, Vol 18, Issue 70 > > > > Send Starlingx-discuss mailing list submissions to > > starlingx-discuss at 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 at lists.starlingx.io > > > > You can reach the person managing the list at > > starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train > > Upgrade Patches. (Liu, ZhipengS) > > 2. [starlingx-discuss][distcloud] Some questions about how do > > subclouds use central cloud's local registry. (张鲲鹏) > > 3. StarlingX platform-integ-apps docker images > > (cristopher.j.lemus.contreras at intel.com) > > 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX > > with Openstack (Saichandu Behara) > > 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 8 Nov 2019 01:55:15 +0000 > > From: "Liu, ZhipengS" > > To: "Hu, Yong" , > > "starlingx-discuss at lists.starlingx.io" > > , "Alonso, Juan Carlos" > > , "Lemus Contreras, Cristopher J" > > > > Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for > > review on OpenStack Train Upgrade Patches. > > Message-ID: > > > > <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi all, > > > > So far I have not got new more comments. > > I'd like to push this 6 patches get merged soon since fully sanity test pass! > > > > Could core reviewers final check them before adding review+2 for below 3 patches. > > https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app > > https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app > > https://review.opendev.org/#/c/688105/ starlingx/root > > > > Thanks! > > Zhipeng > > -----Original Message----- > > From: Hu, Yong > > Sent: 2019年11月5日 22:47 > > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos > > ; Liu, ZhipengS > > ; Lemus Contreras, Cristopher J < > > cristopher.j.lemus.contreras at intel.com> > > Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > > > Hi Core reviewers in Stx.distro.openstack: > > > > The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). > > > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > > > https://review.opendev.org/#/c/683886/ > > https://review.opendev.org/#/c/683910/ > > https://review.opendev.org/#/c/684166/ > > https://review.opendev.org/#/c/687441/ > > https://review.opendev.org/#/c/687197/ > > https://review.opendev.org/#/c/688105/ > > > > In addition, some background info related to this upgrade: > > > > 1). Originally there was a test failure in the sanity, but later > > Zhipeng found the cause was from an non-standard test (cirros) image > > which had 2 > > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: > > later for the testing, we advise to use this cirros image: > > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. > > > > 2). these patches have to be merged *in one batch* due to the inter-dependencies. > > > > 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. > > > > ------------------------------ > > > > Message: 2 > > Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) > > From: 张鲲鹏 > > To: tao.liu at windriver.com > > Cc: starlingx-discuss , > > "greg.waines" > > Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some > > questions about how do subclouds use central cloud's local registry. > > Message-ID: > > > > > net> > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi Tao, Distributed Cloud team, > > > > > > The distributed cloud feature is very cool, and I am concerned about its development always. > > There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. > > > > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > > > > > > Thanks > > Kunpeng > > > > > > > > > > -------------- next part -------------- An HTML attachment was > > scrubbed... > > URL: > > > 91108/ae122f8c/attachment-0001.html> > > > > ------------------------------ > > > > Message: 3 > > Date: Fri, 08 Nov 2019 03:01:31 -0600 > > From: cristopher.j.lemus.contreras at intel.com > > To: > > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker > > images > > Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> > > > > List of docker images required for "platform-integ-apps": > > > > BUILD_ID="20191108T023000Z" > > > > rabbitmq:3.7-management > > k8s.gcr.io/kube-proxy:v1.16.2 > > k8s.gcr.io/kube-apiserver:v1.16.2 > > k8s.gcr.io/kube-controller-manager:v1.16.2 > > k8s.gcr.io/kube-scheduler:v1.16.2 > > k8s.gcr.io/etcd:3.3.15-0 > > k8s.gcr.io/coredns:1.6.2 > > quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubun > > tu_bionic > > quay.io/calico/node:v3.6.2 > > quay.io/calico/cni:v3.6.2 > > quay.io/calico/kube-controllers:v3.6.2 > > rabbitmq:3.7.13-management > > rabbitmq:3.7.13 > > gcr.io/kubernetes-helm/tiller:v2.13.1 > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 > > openstackhelm/mariadb:10.2.18 > > quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 > > quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 > > mariadb:10.2.13 > > memcached:1.5.5 > > k8s.gcr.io/pause:3.1 > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 > > nginx:1.13.3 > > gcr.io/google_containers/defaultbackend:1.0 > > > > > > > > > > ------------------------------ > > > > Message: 4 > > Date: Fri, 8 Nov 2019 17:38:25 +0530 > > From: Saichandu Behara > > To: "Bill.Zvonar at windriver.com" , > > "starlingx-discuss at lists.starlingx.io" > > , bruce.e.jones at intel.com, > > cindy.xie at intel.com, sgw at linux.intel.com > > Cc: Pavan Gupta > > Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX > > all-in-one Simplex EdgeX with Openstack > > Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Hello all, > > > > We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. > > > > We have two images. StarlingX without Openstack and StarlingX with > > Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one > > EdgeX simplex. > > > > We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. > > > > -- > > Thanks & Regards > > Sai Chandu Behara > > > > > > > > > > ------------------------------ > > > > Message: 5 > > Date: Fri, 08 Nov 2019 13:15:44 +0100 > > From: Kris Buytaert > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for > > ceph > > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > > > > > I`m working my way trough > > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio > > _simplex_install_kubernetes.html > > > > but on step 5. Add an OSD on controller-0 for ceph: > > > > the host-stor-add controllor0 command returns with the following error. > > > > > > [root at controller-0 etc(keystone_admin)]# system host-disk-list > > controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > > > > > > Any ideas how to fix this ? > > > > greetings > > > > Kris > > > > > > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > ------------------------------ > > > > End of Starlingx-discuss Digest, Vol 18, Issue 70 > > ************************************************* From juan.carlos.alonso at intel.com Fri Nov 8 15:29:42 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 8 Nov 2019 15:29:42 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> Message-ID: Hello Yan/community, Any update on this? (: Regards. Juan Carlos Alonso From: Alonso, Juan Carlos Sent: Thursday, November 7, 2019 9:56 AM To: Chen, Yan ; Hu, Yong ; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: RE: Train patch elimination Hello Yan, Thank you for your response. Same question now for: Horizon/Custom Confirmation Messages : Custom confirmation message for Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor. I added the bmc_ip, bmc_type, bmc_username and bmc_password for each node, but I cannot display any sensors on Horizon nor CLI. $ system host-update compute-0 bm_username= bm_password= bm_type=bmc bm_ip= $ system host-lock compute-0 $ system host-sensor-list compute-0 $ system host-unlock compute-0 $ system host-sensor-list compute-0 Is there any other configuration needed or is this feature not supported anymore? Regards. Juan Carlos Alonso From: Chen, Yan > Sent: Thursday, November 7, 2019 12:15 AM To: Alonso, Juan Carlos >; Hu, Yong >; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada > Subject: RE: Train patch elimination Carlos, Please remove Horizon/CSRF AngularJS Fixes related cases in your test plan, which are originally planned for STX additional patches, as those patches are already removed from our project and not upstreamed. Yan From: Alonso, Juan Carlos > Sent: Wednesday, November 6, 2019 23:18 To: Hu, Yong >; Chen, Yan >; Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada > Subject: RE: Train patch elimination Hello, I hope also the community can help with this questions. @Chen, Yan Can you help me to verify if this feature is still disabled on Train version: Horizon/CSRF AngularJS Fixes ? On last test plan for Stein this feature was no longer required on Horizon and was disabled on SarlingX code. @Gerry.Kopec at windriver.com About the Live Migration bugs I mentioned on the last meeting, almost all of them are merged, except the last three. All those patches are related to live migration, so my question is if I perform live migrations such patches will be covered or should be tested in a different way? The last three were marked as Unlikely and was not merged on Stein. I don't have more info about such patches. Enable delete bound trunk for linux bridge agent: https://review.opendev.org/#/c/605589 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): https://review.opendev.org/#/c/623401 and https://review.opendev.org/#/c/626109 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): https://review.opendev.org/#/c/625134 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): https://review.opendev.org/#/c/628071 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): https://review.opendev.org/#/c/623415 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): https://review.opendev.org/#/c/621507/ Prevent DHCP from processing stale RPC messages: ?? 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 8 15:56:54 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 8 Nov 2019 15:56:54 +0000 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph In-Reply-To: References: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> <56829C2A36C2E542B0CCB9854828E4D85627E339@CDSMSX102.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15B9C53@ALA-MBD.corp.ad.wrs.com> At the time of installation, the ISO boot menu provides options to install "Standard" vs "All-in-one". The system must be initially installed as All-in-one in order to support a simplex setup. Cheers, Don. -----Original Message----- From: Kris Buytaert [mailto:kris at inuits.eu] Sent: Friday, November 08, 2019 9:12 AM To: Chen, Haochuan Z Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph > One attention is > "localhost.yml" not "localhost.yaml" that was a typo on my side .. > > Double check in this linke > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html > > you can rename and run ansible playbook again to check. > I just cleared the ansible.log and retriggered it again .. The log multiple times mentions duplex grep duplex ansible.log "msg": "System type is Standard, system mode will be set to duplex." 2019-11-05 20:53:28,995 p=13902 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ************************************************************************************************************************************************************************ 2019-11-05 20:53:32,967 p=13902 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-05 21:10:48,604 p=13902 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) "msg": "System type is Standard, system mode will be set to duplex." 2019-11-08 13:21:19,806 p=4110538 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* 2019-11-08 13:21:23,636 p=4110538 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-08 13:26:09,883 p=4110538 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) "msg": "System type is Standard, system mode will be set to duplex." 2019-11-08 13:30:38,866 p=4130039 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* 2019-11-08 13:30:42,673 p=4130039 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) 2019-11-08 13:34:33,158 p=4130039 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) I`m going to look closer at the ansible playbooks to see where this goes wrong. greetings Kris > BR! > > Martin, Chen > SSP, Software Engineer > 021-61164330 > > -----Original Message----- > From: Kris Buytaert > Sent: Friday, November 8, 2019 9:41 PM > To: Chen, Haochuan Z > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: Failing to add an OSD on controller-0 for ceph > > On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote: > > Hi Kris > > > > Before you run this command, are you sure "system mode: simplex" in > > localhost.yml $ ansible-playbook > > /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml > > > > The localhost.yaml indeed does contain > > system_mode: simplex > > > The platform.conf however not , so I updated that .. > > After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex > > > > I regtriggered the ansible run to be sure .. and even during that run with the config i noticed > > TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** > changed: [localhost] => (item=prev_system_mode: duplex) > changed: [localhost] => (item=prev_timezone: UTC) > > So somewhere it looks like it is taking in the wrong parameter .. > > I`ll dig deeper .. but if you have any hints on where to search ? > > > greetings > > Kris > > > > > > > > > You can check this in your system > > $ cat /etc/platform/platform.conf > > > > BR! > > > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > > > -----Original Message----- > > From: starlingx-discuss-request at lists.starlingx.io > > > > Sent: Friday, November 8, 2019 8:30 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: Starlingx-discuss Digest, Vol 18, Issue 70 > > > > Send Starlingx-discuss mailing list submissions to > > starlingx-discuss at 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 at lists.starlingx.io > > > > You can reach the person managing the list at > > starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train > > Upgrade Patches. (Liu, ZhipengS) > > 2. [starlingx-discuss][distcloud] Some questions about how do > > subclouds use central cloud's local registry. (张鲲鹏) > > 3. StarlingX platform-integ-apps docker images > > (cristopher.j.lemus.contreras at intel.com) > > 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX > > with Openstack (Saichandu Behara) > > 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Fri, 8 Nov 2019 01:55:15 +0000 > > From: "Liu, ZhipengS" > > To: "Hu, Yong" , > > "starlingx-discuss at lists.starlingx.io" > > , "Alonso, Juan Carlos" > > , "Lemus Contreras, Cristopher J" > > > > Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for > > review on OpenStack Train Upgrade Patches. > > Message-ID: > > > > <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi all, > > > > So far I have not got new more comments. > > I'd like to push this 6 patches get merged soon since fully sanity test pass! > > > > Could core reviewers final check them before adding review+2 for below 3 patches. > > https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app > > https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app > > https://review.opendev.org/#/c/688105/ starlingx/root > > > > Thanks! > > Zhipeng > > -----Original Message----- > > From: Hu, Yong > > Sent: 2019年11月5日 22:47 > > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos > > ; Liu, ZhipengS > > ; Lemus Contreras, Cristopher J < > > cristopher.j.lemus.contreras at intel.com> > > Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > > > Hi Core reviewers in Stx.distro.openstack: > > > > The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). > > > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > > > https://review.opendev.org/#/c/683886/ > > https://review.opendev.org/#/c/683910/ > > https://review.opendev.org/#/c/684166/ > > https://review.opendev.org/#/c/687441/ > > https://review.opendev.org/#/c/687197/ > > https://review.opendev.org/#/c/688105/ > > > > In addition, some background info related to this upgrade: > > > > 1). Originally there was a test failure in the sanity, but later > > Zhipeng found the cause was from an non-standard test (cirros) image > > which had 2 > > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: > > later for the testing, we advise to use this cirros image: > > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. > > > > 2). these patches have to be merged *in one batch* due to the inter-dependencies. > > > > 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. > > > > ------------------------------ > > > > Message: 2 > > Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) > > From: 张鲲鹏 > > To: tao.liu at windriver.com > > Cc: starlingx-discuss , > > "greg.waines" > > Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some > > questions about how do subclouds use central cloud's local registry. > > Message-ID: > > > > > net> > > > > Content-Type: text/plain; charset="utf-8" > > > > Hi Tao, Distributed Cloud team, > > > > > > The distributed cloud feature is very cool, and I am concerned about its development always. > > There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. > > > > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > > > > > > Thanks > > Kunpeng > > > > > > > > > > -------------- next part -------------- An HTML attachment was > > scrubbed... > > URL: > > > 91108/ae122f8c/attachment-0001.html> > > > > ------------------------------ > > > > Message: 3 > > Date: Fri, 08 Nov 2019 03:01:31 -0600 > > From: cristopher.j.lemus.contreras at intel.com > > To: > > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker > > images > > Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> > > > > List of docker images required for "platform-integ-apps": > > > > BUILD_ID="20191108T023000Z" > > > > rabbitmq:3.7-management > > k8s.gcr.io/kube-proxy:v1.16.2 > > k8s.gcr.io/kube-apiserver:v1.16.2 > > k8s.gcr.io/kube-controller-manager:v1.16.2 > > k8s.gcr.io/kube-scheduler:v1.16.2 > > k8s.gcr.io/etcd:3.3.15-0 > > k8s.gcr.io/coredns:1.6.2 > > quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubun > > tu_bionic > > quay.io/calico/node:v3.6.2 > > quay.io/calico/cni:v3.6.2 > > quay.io/calico/kube-controllers:v3.6.2 > > rabbitmq:3.7.13-management > > rabbitmq:3.7.13 > > gcr.io/kubernetes-helm/tiller:v2.13.1 > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 > > openstackhelm/mariadb:10.2.18 > > quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 > > quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 > > mariadb:10.2.13 > > memcached:1.5.5 > > k8s.gcr.io/pause:3.1 > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 > > nginx:1.13.3 > > gcr.io/google_containers/defaultbackend:1.0 > > > > > > > > > > ------------------------------ > > > > Message: 4 > > Date: Fri, 8 Nov 2019 17:38:25 +0530 > > From: Saichandu Behara > > To: "Bill.Zvonar at windriver.com" , > > "starlingx-discuss at lists.starlingx.io" > > , bruce.e.jones at intel.com, > > cindy.xie at intel.com, sgw at linux.intel.com > > Cc: Pavan Gupta > > Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX > > all-in-one Simplex EdgeX with Openstack > > Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > Hello all, > > > > We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. > > > > We have two images. StarlingX without Openstack and StarlingX with > > Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in-one > > EdgeX simplex. > > > > We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. > > > > -- > > Thanks & Regards > > Sai Chandu Behara > > > > > > > > > > ------------------------------ > > > > Message: 5 > > Date: Fri, 08 Nov 2019 13:15:44 +0100 > > From: Kris Buytaert > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for > > ceph > > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > > > > > I`m working my way trough > > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio > > _simplex_install_kubernetes.html > > > > but on step 5. Add an OSD on controller-0 for ceph: > > > > the host-stor-add controllor0 command returns with the following error. > > > > > > [root at controller-0 etc(keystone_admin)]# system host-disk-list > > controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > > > > > > Any ideas how to fix this ? > > > > greetings > > > > Kris > > > > > > > > > > > > ------------------------------ > > > > Subject: Digest Footer > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > ------------------------------ > > > > End of Starlingx-discuss Digest, Vol 18, Issue 70 > > ************************************************* _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kris at inuits.eu Fri Nov 8 17:50:45 2019 From: kris at inuits.eu (Kris Buytaert) Date: Fri, 08 Nov 2019 18:50:45 +0100 Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15B9C53@ALA-MBD.corp.ad.wrs.com> References: <56829C2A36C2E542B0CCB9854828E4D85627E302@CDSMSX102.ccr.corp.intel.com> <8c2fddf6f76c4578c7178465b5ccde25c9c87a7b.camel@inuits.eu> <56829C2A36C2E542B0CCB9854828E4D85627E339@CDSMSX102.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15B9C53@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, 2019-11-08 at 15:56 +0000, Penney, Don wrote: > At the time of installation, the ISO boot menu provides options to install "Standard" vs "All-in-one". The system must be initially installed as All-in-one in order to support a simplex setup. > Thnx that actually was the case ... I must have overlooked this step ! greetings Kris > Cheers, > Don. > > -----Original Message----- > From: Kris Buytaert [mailto:kris at inuits.eu] > Sent: Friday, November 08, 2019 9:12 AM > To: Chen, Haochuan Z > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Failing to add an OSD on controller-0 for ceph > > > > One attention is > > "localhost.yml" not "localhost.yaml" > > that was a typo on my side .. > > > Double check in this linke > > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio_simplex_install_kubernetes.html > > > > you can rename and run ansible playbook again to check. > > > > I just cleared the ansible.log and retriggered it again .. > > > The log multiple times mentions duplex > > grep duplex ansible.log > "msg": "System type is Standard, system mode will be set to duplex." > 2019-11-05 20:53:28,995 p=13902 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] > ************************************************************************************************************************************************************************ > 2019-11-05 20:53:32,967 p=13902 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) > 2019-11-05 21:10:48,604 p=13902 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) > "msg": "System type is Standard, system mode will be set to duplex." > 2019-11-08 13:21:19,806 p=4110538 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* > 2019-11-08 13:21:23,636 p=4110538 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) > 2019-11-08 13:26:09,883 p=4110538 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) > "msg": "System type is Standard, system mode will be set to duplex." > 2019-11-08 13:30:38,866 p=4130039 u=sysadmin | TASK [validate-config : Set system mode to duplex for Standard system] ********* > 2019-11-08 13:30:42,673 p=4130039 u=sysadmin | changed: [localhost] => (item=SYSTEM_MODE=duplex) > 2019-11-08 13:34:33,158 p=4130039 u=sysadmin | changed: [localhost] => (item=prev_system_mode: duplex) > > > > I`m going to look closer at the ansible playbooks to see where this goes wrong. > > greetings > > Kris > > > > > BR! > > > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > > > -----Original Message----- > > From: Kris Buytaert > > Sent: Friday, November 8, 2019 9:41 PM > > To: Chen, Haochuan Z > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: Failing to add an OSD on controller-0 for ceph > > > > On Fri, 2019-11-08 at 13:13 +0000, Chen, Haochuan Z wrote: > > > Hi Kris > > > > > > Before you run this command, are you sure "system mode: simplex" in > > > localhost.yml $ ansible-playbook > > > /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml > > > > > > > The localhost.yaml indeed does contain > > > > system_mode: simplex > > > > > > The platform.conf however not , so I updated that .. > > > > After the chnage it seemed to ingnore that change .. the command still has the same error There also is an empty file in /etc/platform called simplex > > > > > > > > I regtriggered the ansible run to be sure .. and even during that run with the config i noticed > > > > TASK [bringup-essential-services : Save the current system and network config for reference in subsequent replays] *** > > changed: [localhost] => (item=prev_system_mode: duplex) > > changed: [localhost] => (item=prev_timezone: UTC) > > > > So somewhere it looks like it is taking in the wrong parameter .. > > > > I`ll dig deeper .. but if you have any hints on where to search ? > > > > > > greetings > > > > Kris > > > > > > > > > > > > > > > > > You can check this in your system > > > $ cat /etc/platform/platform.conf > > > > > > BR! > > > > > > Martin, Chen > > > SSP, Software Engineer > > > 021-61164330 > > > > > > -----Original Message----- > > > From: starlingx-discuss-request at lists.starlingx.io > > > > > > Sent: Friday, November 8, 2019 8:30 PM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: Starlingx-discuss Digest, Vol 18, Issue 70 > > > > > > Send Starlingx-discuss mailing list submissions to > > > starlingx-discuss at 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 at lists.starlingx.io > > > > > > You can reach the person managing the list at > > > starlingx-discuss-owner at 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. Re: [Stx.distro.openstack] Call for review on OpenStack Train > > > Upgrade Patches. (Liu, ZhipengS) > > > 2. [starlingx-discuss][distcloud] Some questions about how do > > > subclouds use central cloud's local registry. (张鲲鹏) > > > 3. StarlingX platform-integ-apps docker images > > > (cristopher.j.lemus.contreras at intel.com) > > > 4. Calsoft's Contribution StarlingX all-in-one Simplex EdgeX > > > with Openstack (Saichandu Behara) > > > 5. Failing to add an OSD on controller-0 for ceph (Kris Buytaert) > > > > > > > > > ---------------------------------------------------------------------- > > > > > > Message: 1 > > > Date: Fri, 8 Nov 2019 01:55:15 +0000 > > > From: "Liu, ZhipengS" > > > To: "Hu, Yong" , > > > "starlingx-discuss at lists.starlingx.io" > > > , "Alonso, Juan Carlos" > > > , "Lemus Contreras, Cristopher J" > > > > > > Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for > > > review on OpenStack Train Upgrade Patches. > > > Message-ID: > > > > > > <93814834B4855241994F290E959305C7530F61C3 at SHSMSX104.ccr.corp.intel.com > > > > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi all, > > > > > > So far I have not got new more comments. > > > I'd like to push this 6 patches get merged soon since fully sanity test pass! > > > > > > Could core reviewers final check them before adding review+2 for below 3 patches. > > > https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app > > > https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app > > > https://review.opendev.org/#/c/688105/ starlingx/root > > > > > > Thanks! > > > Zhipeng > > > -----Original Message----- > > > From: Hu, Yong > > > Sent: 2019年11月5日 22:47 > > > To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos > > > ; Liu, ZhipengS > > > ; Lemus Contreras, Cristopher J < > > > cristopher.j.lemus.contreras at intel.com> > > > Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. > > > > > > Hi Core reviewers in Stx.distro.openstack: > > > > > > The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). > > > > > > So to unblock stx.3.0 MS-3, please review the following patches in time: > > > > > > https://review.opendev.org/#/c/683886/ > > > https://review.opendev.org/#/c/683910/ > > > https://review.opendev.org/#/c/684166/ > > > https://review.opendev.org/#/c/687441/ > > > https://review.opendev.org/#/c/687197/ > > > https://review.opendev.org/#/c/688105/ > > > > > > In addition, some background info related to this upgrade: > > > > > > 1). Originally there was a test failure in the sanity, but later > > > Zhipeng found the cause was from an non-standard test (cirros) image > > > which had 2 > > > QCOW2 headers unexpectedly and failed during the conversion from QCOW2 > > > to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: > > > later for the testing, we advise to use this cirros image: > > > https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. > > > > > > 2). these patches have to be merged *in one batch* due to the inter-dependencies. > > > > > > 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. > > > > > > ------------------------------ > > > > > > Message: 2 > > > Date: Fri, 8 Nov 2019 12:34:49 +0800 (GMT+08:00) > > > From: 张鲲鹏 > > > To: tao.liu at windriver.com > > > Cc: starlingx-discuss , > > > "greg.waines" > > > Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some > > > questions about how do subclouds use central cloud's local registry. > > > Message-ID: > > > > > > > > net> > > > > > > Content-Type: text/plain; charset="utf-8" > > > > > > Hi Tao, Distributed Cloud team, > > > > > > > > > The distributed cloud feature is very cool, and I am concerned about its development always. > > > There are some questions about subclouds access the central cloud's local reigistry. This is the bug link[1]. > > > > > > > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > > > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > > > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > > > > > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > > > > > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > > > > > > > > > Thanks > > > Kunpeng > > > > > > > > > > > > > > > -------------- next part -------------- An HTML attachment was > > > scrubbed... > > > URL: > > > > > 91108/ae122f8c/attachment-0001.html> > > > > > > ------------------------------ > > > > > > Message: 3 > > > Date: Fri, 08 Nov 2019 03:01:31 -0600 > > > From: cristopher.j.lemus.contreras at intel.com > > > To: > > > Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker > > > images > > > Message-ID: <3cea8d$6uns3q at fmsmga002.fm.intel.com> > > > > > > List of docker images required for "platform-integ-apps": > > > > > > BUILD_ID="20191108T023000Z" > > > > > > rabbitmq:3.7-management > > > k8s.gcr.io/kube-proxy:v1.16.2 > > > k8s.gcr.io/kube-apiserver:v1.16.2 > > > k8s.gcr.io/kube-controller-manager:v1.16.2 > > > k8s.gcr.io/kube-scheduler:v1.16.2 > > > k8s.gcr.io/etcd:3.3.15-0 > > > k8s.gcr.io/coredns:1.6.2 > > > quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubun > > > tu_bionic > > > quay.io/calico/node:v3.6.2 > > > quay.io/calico/cni:v3.6.2 > > > quay.io/calico/kube-controllers:v3.6.2 > > > rabbitmq:3.7.13-management > > > rabbitmq:3.7.13 > > > gcr.io/kubernetes-helm/tiller:v2.13.1 > > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 > > > openstackhelm/mariadb:10.2.18 > > > quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 > > > quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 > > > mariadb:10.2.13 > > > memcached:1.5.5 > > > k8s.gcr.io/pause:3.1 > > > quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 > > > nginx:1.13.3 > > > gcr.io/google_containers/defaultbackend:1.0 > > > > > > > > > > > > > > > ------------------------------ > > > > > > Message: 4 > > > Date: Fri, 8 Nov 2019 17:38:25 +0530 > > > From: Saichandu Behara > > > To: "Bill.Zvonar at windriver.com" , > > > "starlingx-discuss at lists.starlingx.io" > > > , bruce.e.jones at intel.com, > > > cindy.xie at intel.com, sgw at linux.intel.com > > > Cc: Pavan Gupta > > > Subject: [Starlingx-discuss] Calsoft's Contribution StarlingX > > > all-in-one Simplex EdgeX with Openstack > > > Message-ID: <6bfa5d34-c128-9a9f-2f94-73c42a18e0e6 at calsoftinc.com> > > > Content-Type: text/plain; charset=utf-8; format=flowed > > > > > > Hello all, > > > > > > We ready with StarlingX All-In-a-one with containing StarlingX, K8s, EdgeX and Openstack. > > > > > > We have two images. StarlingX without Openstack and StarlingX with > > > Openstack. we already shared StarlingX without Openstack image. Now we are looking to contribute StarlingX all-in-one. Which contain StarlingX, K8s, EdgeX and Openstack. It is StarlingX all-in- > > > one > > > EdgeX simplex. > > > > > > We will share this image in couple of days. So, any one can experience how the things working with All-in-a-one setup with Openstack. > > > > > > -- > > > Thanks & Regards > > > Sai Chandu Behara > > > > > > > > > > > > > > > ------------------------------ > > > > > > Message: 5 > > > Date: Fri, 08 Nov 2019 13:15:44 +0100 > > > From: Kris Buytaert > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Failing to add an OSD on controller-0 for > > > ceph > > > Message-ID: > > > Content-Type: text/plain; charset="UTF-8" > > > > > > > > > I`m working my way trough > > > https://docs.starlingx.io/deploy_install_guides/r2_release/virtual/aio > > > _simplex_install_kubernetes.html > > > > > > but on step 5. Add an OSD on controller-0 for ceph: > > > > > > the host-stor-add controllor0 command returns with the following error. > > > > > > > > > [root at controller-0 etc(keystone_admin)]# system host-disk-list > > > controller-0 | awk '/\/dev\/sdb/{print $2}' | xargs -i system host-stor-add controller-0 {} Please install storage-0 or configure a Ceph monitor on a worker node before adding storage devices. > > > > > > > > > Any ideas how to fix this ? > > > > > > greetings > > > > > > Kris > > > > > > > > > > > > > > > > > > ------------------------------ > > > > > > Subject: Digest Footer > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > > ------------------------------ > > > > > > End of Starlingx-discuss Digest, Vol 18, Issue 70 > > > ************************************************* > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Fri Nov 8 18:02:55 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Fri, 8 Nov 2019 18:02:55 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191108 Message-ID: <088B54F0-5FA8-4AAD-A742-6B67E92F6C75@intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-08 (link) Status: GREEN =========================================== Sanity Test executed Bare Metal 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 - 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 - 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 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 - 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 - 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 ] List of docker images: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006878.html BUG (Not appeared today, still open, intermittent) platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sat Nov 9 09:00:55 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 09 Nov 2019 03:00:55 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$5s0fln@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191109T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From cristopher.j.lemus.contreras at intel.com Sun Nov 10 09:00:50 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 10 Nov 2019 03:00:50 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6v8gm0@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191110T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From yong.hu at intel.com Mon Nov 11 01:27:15 2019 From: yong.hu at intel.com (Yong Hu) Date: Mon, 11 Nov 2019 09:27:15 +0800 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> Message-ID: JC, Have you enabled BMC config in your test servers and BIOS? If so, please use "ipmitool" utility to have a try to read sensor info. regards, Yong On 2019/11/8 11:29 PM, Alonso, Juan Carlos wrote: > Hello Yan/community, > > Any update on this? (: > > Regards. > > Juan Carlos Alonso > > *From:* Alonso, Juan Carlos > *Sent:* Thursday, November 7, 2019 9:56 AM > *To:* Chen, Yan ; Hu, Yong ; > Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io > *Cc:* Cabrales, Ada > *Subject:* RE: Train patch elimination > > Hello Yan, > > Thank you for your response. > > Same question now for: > > _Horizon/Custom Confirmation Messages : Custom confirmation message for > Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor._ > > I added the bmc_ip, bmc_type, bmc_username and bmc_password for each > node, but I cannot display any sensors on Horizon nor CLI. > > $ system host-update compute-0 bm_username= > bm_password= bm_type=bmc bm_ip= > > $ system host-lock compute-0 > > $ system host-sensor-list compute-0 > > > > $ system host-unlock compute-0 > > $ system host-sensor-list compute-0 > > > > Is there any other configuration needed or is this feature not supported > anymore? > > Regards. > > Juan Carlos Alonso > > *From:* Chen, Yan > > *Sent:* Thursday, November 7, 2019 12:15 AM > *To:* Alonso, Juan Carlos >; Hu, Yong >; Gerry.Kopec at windriver.com > ; starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Carlos, > > Please remove _Horizon/CSRF AngularJS Fixes_ related cases in your test > plan, which are originally planned for STX additional patches, as those > patches are already removed from our project and not upstreamed. > > Yan > > *From:* Alonso, Juan Carlos > > *Sent:* Wednesday, November 6, 2019 23:18 > *To:* Hu, Yong >; Chen, Yan > >; > Gerry.Kopec at windriver.com ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Hello, > > I hope also the community can help with this questions. > > @Chen, Yan > > Can you help me to verify if this feature is still disabled on Train > version: _Horizon/CSRF AngularJS Fixes_? > > On last test plan for Stein this feature was no longer required on > Horizon and was disabled on SarlingX code. > > @Gerry.Kopec at windriver.com > > About the Live Migration bugs I mentioned on the last meeting, almost > all of them are merged, except the last three. > > All those patches are related to live migration, so my question is if I > perform live migrations such patches will be covered or should be tested > in a different way? > > The last three were marked as Unlikely and was not merged on Stein. I > don’t have more info about such patches. > > Enable delete bound trunk for linux bridge agent: > https://review.opendev.org/#/c/605589 > > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): > https://review.opendev.org/#/c/623401 and > https://review.opendev.org/#/c/626109 > > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): > https://review.opendev.org/#/c/625134 > > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): > https://review.opendev.org/#/c/628071 > > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): > https://review.opendev.org/#/c/623415 > > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): > _https://review.opendev.org/#/c/621507/_ > > Prevent DHCP from processing stale RPC messages: ?? > > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? > > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? > > Regards. > > Juan Carlos Alonso > From wang.ya at 99cloud.net Mon Nov 11 05:18:19 2019 From: wang.ya at 99cloud.net (wang.ya) Date: Mon, 11 Nov 2019 13:18:19 +0800 Subject: [Starlingx-discuss] Patch Elimination Train version Message-ID: Hi, Alonso: I'm not sure that the configuration had been changed. You can check the nova compute's log (you need enable debug mode), search 'cpu_models', you'll see a record similar as below(the record should printed when service start): " 2019-11-08 18:21:58.966 6 DEBUG oslo_service.service [req-16a54cb4-1d45-4119-9fd4-6d84f471ebb0 - - - - -] libvirt.cpu_models = [SandyBridge,IvyBridge,Haswell,Broadwell] log_opt_values /var/lib/kolla/venv/lib/python2.7/site-packages/oslo_config/cfg.py:2585" Please check the list, if it’s same as you set, then the configuration changed success. Best Regards On 2019/11/7, 4:19 AM, "Alonso, Juan Carlos" wrote:     Hello Ya,         I have an standard configuration local storage (2+2) baremetal environment, I can access to nova-compute service for both computes but I did not found a list of 'cpu_models', just found 'cpu_mode' and it is not set as 'custom' as documentation says:     [libvirt]     cpu_mode = host-model         So, I executed:     $ system helm-override-update --set livbirt.cpu_mode=custom stx-openstack nova openstack     $ system helm-override-update --set cpu_models=SandyBridge,IvyBridge,Haswell,Broadwell stx-openstack nova openstack         I check again /etc/nova/nova.conf inside pod, and still saw just 'cpu_mode = host-model'     Is this configuration be modified? If yes, how can I do it?         Also I could create flavors and instances with below configurations:     trait:HW_CPU_X86_AVX='required'     trait:HW_CPU_X86_AVX2='required'     trait:HW_CPU_X86_AVX512F='required'         One instance for each configuration and one instance with those three configuration in a same flavor.     But, how can I check the CPU model in the instance?         In the test cases I mention at the beginning of this threat it says that the instances with flavor property trait:HW_CPU_X86_AVX512F='required' should get ERROR, but it could be launched as ACTIVE.         Regards.     Juan Carlos Alonso         -----Original Message-----     From: wang.ya     Sent: Monday, November 4, 2019 9:01 PM     To: Hu, Yong ; Jones, Bruce E ; Alonso, Juan Carlos ; Troyer, Dean     Cc: Cabrales, Ada     Subject: Re: Patch Elimination Train version         Hi, yong:         *vCPU Models selection* feature has been completed in train release.         The feature's workflow is as follow:         1. Configure the *cpu_models* option under [libvirt] module of nova-compute service.          The *cpu_models* option is an ordered list of CPU models. It's sorted by CPU flags, from less to more. For example:                kvm64, IvyBridge, Haswell          In above example, kvm64 only has base flags, IvyBridge has flag *avx*, Haswell have both *avx* and *avx2*.          Please note that the configured CPU models must compatible with compute node's host CPU.         2. Create/Set flavor with required traits. The nova compute will select the CPU model from [libvirt]/cpu_models which first meet the flavor's requested flags. For example:                openstack flavor set 1 --property trait:HW_CPU_X86_AVX=required          In above example, we mark the flavor request flag *avx*, if the CPU of compute node has flag *avx*, then the instance can be scheduled success and created with CPU model IvyBridge, otherwise the API call will get an error: "No valid host".          Spec: http://specs.openstack.org/openstack/nova-specs/specs/train/approved/cpu-model-selection.html     Code: https://review.opendev.org/#/q/status:merged+project:openstack/nova+branch:master+topic:bp/cpu-model-selection         Hope the above info can help you. Also, I'll online in today's meeting :)         Best Regards              On 2019/11/5, 9:13 AM, "Yong Hu" wrote:             + Wang Ya.                 Hi Ya,         I remember your team has been upstreaming the related patches.         Could you share some info with us here or in the meeting tonight?                 regards,         Yong                 On 2019/11/5 6:37 AM, Jones, Bruce E wrote:         > + Dean and Yong (the new PL for the OpenStack team)         >         > AFAIK the CPU model changes that went into Train are internal only and         > don’t impact OpenStack operation.         >         > Suggest you bring all of this to the distro.openstack meeting tomorrow         > where it can be discussed with the right people.         >         >       brucej         >         > *From:* Alonso, Juan Carlos         > *Sent:* Monday, November 4, 2019 2:30 PM         > *To:* Jones, Bruce E         > *Cc:* Cabrales, Ada         > *Subject:* Patch Elimination Train version         >         > Hi Bruce,         >         > In last test plan for Patch Elimination Stein version, there was some         > *vCPU Model (Nova)* feature test cases that was marked as Unlikely status:         >         > 1. Create a flavor without any extra specs. Launch instance using this         > flavor. Check instance cpu_model is 'kvm64'         >         > 2. Create a flavor with extra specs: 'trait:HW_CPU_X86_AVX2=required'.         > Launch instance using this flavor. Check instance is Haswell and is in         > compute node 2.         >         > 3. Create a flavor with extra specs:         > 'trait:HW_CPU_X86_AVX512F=required'. Launch instance using this flavor.         > Check API call get an error because no compute node has property 'avx512F'.         >         > 4. Create a flavor with multiple extra specs: 'trait:xxx'. Launch         > instance using this flavor.         >         > 5. Create a flavor and ignoring cpu_model. Launch instance using this         > flavor.         >         > For Train version, is such *vCPU Model (Nova)* feature still out?         >         > Also, there was some Live Migration Bugs table related to Neutron:         >         > Enable delete bound trunk for linux bridge agent         >         > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00)         >         > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731)         >         > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911)         >         > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6)         >         > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7)         >         > Prevent DHCP from processing stale RPC messages         >         > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89)         >         > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491)         >         > I need to know if such features/tests are going to be testes or not, can         > you help me to verify?         >         > Test Plan for Stein:         > https://docs.google.com/spreadsheets/d/1jsTyzy1HT7VR4EUsbBRaTYvs0BlXeGWkhLD0pJmFChc/edit#gid=1511025137         >         > Test Plan for Train:         > https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit?pli=1#gid=184151983         >         > Regards.         >         > Juan Carlos Alonso         >                                 _______________________________________________     Starlingx-discuss mailing list     Starlingx-discuss at lists.starlingx.io     http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss     -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Mon Nov 11 09:00:00 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 11 Nov 2019 03:00:00 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$6vhinj@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191111T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From sgw at linux.intel.com Mon Nov 11 10:51:29 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 11 Nov 2019 02:51:29 -0800 Subject: [Starlingx-discuss] Feature Branch for CentOS 8 Update work Message-ID: <5563f7a9-413e-f660-d4a6-394ef4b1b24e@linux.intel.com> Folks, I created a feature branch called f/centos8 for stx-tools, root, manifest, integ and compile repos. I have also updated the .gitreview in those branches. The reviews are pending here: https://review.opendev.org/#/q/status:open++branch:f/centos8+topic:centos8 We had a discussion about this in the PTG meeting and unless there are loud protests, I will also be adding 1-2 people as Core reviewers to only review feature branch commits. If there is any issue with this please let me know. Hai Tao and Shuicheng will be added as they have participated in the past CentOS upgrade work. I will be mentoring both them and the folks now doing the CentOS8 update work, so we might have a few first bumpy commits, please bear with us. Sau! From Eric.MacDonald at windriver.com Mon Nov 11 14:33:07 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Mon, 11 Nov 2019 14:33:07 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> Message-ID: <210898B96CA058408C55992CCAD98676C10AC4EF@ALA-MBD.corp.ad.wrs.com> Yong's suggestion to check the server's BMC settings is good. Some servers such as Dell, have an 'Enable IPMI over LAN setting. Do you see a BMC access alarm ? > fm alarm-list Try to ping the target server BMC. If that works then I suggest you try and read the sensors manually using ipmitool. ipmitool -I lanplus -H -U -P sensor list If a list of sensors is displayed and you can't see the sensor list with 'system host-sensor-list' then 1. Inspect recent logs in /var/log/mtcAgent.log and var/log/hwmond.log looking for logs that pertain to BMC accesses. 2. Check that your provisioned username, ip address and password are correct. Try deprovisioning and reprovisioning the BMC. > system host-update bm_type=none And then provision again ensuring the credentials are correct. Wait 5-10 minutes Tail mtcAgent and hwmond.log files. If there is a failure the logs will help us narrow in on the issue. 3. Provide output of the following commands cat /var/run/bmc/* ls -r /var/run/bmc/* 4. Ideally compress and attach the mtcAgent.log file Eric. -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: Sunday, November 10, 2019 8:27 PM To: Alonso, Juan Carlos; Chen, Yan; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: Re: [Starlingx-discuss] Train patch elimination JC, Have you enabled BMC config in your test servers and BIOS? If so, please use "ipmitool" utility to have a try to read sensor info. regards, Yong On 2019/11/8 11:29 PM, Alonso, Juan Carlos wrote: > Hello Yan/community, > > Any update on this? (: > > Regards. > > Juan Carlos Alonso > > *From:* Alonso, Juan Carlos > *Sent:* Thursday, November 7, 2019 9:56 AM > *To:* Chen, Yan ; Hu, Yong ; > Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io > *Cc:* Cabrales, Ada > *Subject:* RE: Train patch elimination > > Hello Yan, > > Thank you for your response. > > Same question now for: > > _Horizon/Custom Confirmation Messages : Custom confirmation message for > Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor._ > > I added the bmc_ip, bmc_type, bmc_username and bmc_password for each > node, but I cannot display any sensors on Horizon nor CLI. > > $ system host-update compute-0 bm_username= > bm_password= bm_type=bmc bm_ip= > > $ system host-lock compute-0 > > $ system host-sensor-list compute-0 > > > > $ system host-unlock compute-0 > > $ system host-sensor-list compute-0 > > > > Is there any other configuration needed or is this feature not supported > anymore? > > Regards. > > Juan Carlos Alonso > > *From:* Chen, Yan > > *Sent:* Thursday, November 7, 2019 12:15 AM > *To:* Alonso, Juan Carlos >; Hu, Yong >; Gerry.Kopec at windriver.com > ; starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Carlos, > > Please remove _Horizon/CSRF AngularJS Fixes_ related cases in your test > plan, which are originally planned for STX additional patches, as those > patches are already removed from our project and not upstreamed. > > Yan > > *From:* Alonso, Juan Carlos > > *Sent:* Wednesday, November 6, 2019 23:18 > *To:* Hu, Yong >; Chen, Yan > >; > Gerry.Kopec at windriver.com ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Hello, > > I hope also the community can help with this questions. > > @Chen, Yan > > Can you help me to verify if this feature is still disabled on Train > version: _Horizon/CSRF AngularJS Fixes_? > > On last test plan for Stein this feature was no longer required on > Horizon and was disabled on SarlingX code. > > @Gerry.Kopec at windriver.com > > About the Live Migration bugs I mentioned on the last meeting, almost > all of them are merged, except the last three. > > All those patches are related to live migration, so my question is if I > perform live migrations such patches will be covered or should be tested > in a different way? > > The last three were marked as Unlikely and was not merged on Stein. I > don’t have more info about such patches. > > Enable delete bound trunk for linux bridge agent: > https://review.opendev.org/#/c/605589 > > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): > https://review.opendev.org/#/c/623401 and > https://review.opendev.org/#/c/626109 > > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): > https://review.opendev.org/#/c/625134 > > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): > https://review.opendev.org/#/c/628071 > > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): > https://review.opendev.org/#/c/623415 > > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): > _https://review.opendev.org/#/c/621507/_ > > Prevent DHCP from processing stale RPC messages: ?? > > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? > > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? > > Regards. > > Juan Carlos Alonso > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From elio.martinez.monroy at intel.com Mon Nov 11 17:12:29 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Mon, 11 Nov 2019 17:12:29 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: <210898B96CA058408C55992CCAD98676C10AC4EF@ALA-MBD.corp.ad.wrs.com> References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676C10AC4EF@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi guys, i checked everything in the way that you suggested. MtcAgent.log is showing, im working in a Duplex configuration locked and trying to get sensors from controller-0: p ( 601) redfishUtil_get_bmc_info: Info : controller-0 has 2 Processors ; Ena bled and OK:OK 2019-11-11T10:38:49.554 [1945193.00281] controller-1 mtcAgent --- redfishUtil.cp p ( 624) redfishUtil_get_bmc_info: Info : controller-0 has 96 GiB Memory ; Ena bled and OK:OK 2019-11-11T10:38:49.554 [1945193.00282] controller-1 mtcAgent |-| mtcNodeHdlrs.c pp (6492) bmc_handler : Info : controller-0 bmc audit timer started (120 secs) 2019-11-11T10:38:49.554 [1945193.00283] controller-1 mtcAgent |-| mtcNodeHdlrs.c pp (6507) bmc_handler : Info : controller-0 bmc is accessible using cd /var/run/bmc/ [sysadmin at controller-1 bmc(keystone_admin)]$ ls controller-0 controller-1 ipmitool redfishtool cat /var/run/bmc/ cat controller-0 {"protocol":"redfishtool","power_state":"on"} cat controller-1 {"protocol":"redfishtool","power_state":"on"} cd ipmitool controller-1:/var/run/bmc/ipmitool$ controller-1:/var/run/bmc/ipmitool$ controller-1:/var/run/bmc/ipmitool$ ls controller-1:/var/run/bmc/ipmitool$ edfishtool$ ls hwmond_controller-0_power_sensor_data hwmond_controller-1_power_sensor_data mtcAgent_controller-0_bmc_info mtcAgent_controller-1_bmc_info hwmond_controller-0_thermal_sensor_data hwmond_controller-1_thermal_sensor_data mtcAgent_controller-0_root_query mtcAgent_controller-1_root_query If I check any of the files I got this: cat hwmond_controller-0_power_sensor_data redfishtool:Transport: Fatal timeout waiting for response from rhostTraceback (most recent call last): File "/usr/bin/redfishtool", line 18, in main(sys.argv) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolMain.py", line 372, in main rc,r,j,d=runSubCmd(rft) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolMain.py", line 449, in runSubCmd rc,r,j,d=subCmdTable[rft.subcommand](rft,cmdTop=True) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 157, in ChassisMain rc,r,j,d = self.runOperation(rft) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 113, in runOperation rc,r,j,d=operationTable[self.operation](self, op, rft, cmdTop=True) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 428, in getPower rc,r,j,d=op.get(sc, op, rft, cmdTop, resName) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 234, in get sysPath,rc,r,j,d=rft.getPathBy(rft, r, d, prop) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolTransport.py", line 885, in getPathBy rc, r, j, d = rft.listCollection(rft, r, coll, prop) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolTransport.py", line 1025, in listCollection rc,r,j,d=rft.rftSendRecvRequest(rft.AUTHENTICATED_API, 'GET', r.url, relPath=path) AttributeError: 'NoneType' object has no attribute 'url' So , my question should be, is the redfishtool blocking ipmitool to show the values? Because impitool is showing sensors by itself. BR Elio -----Original Message----- From: MacDonald, Eric Sent: Monday, November 11, 2019 8:33 AM To: Hu, Yong ; Alonso, Juan Carlos ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: Re: [Starlingx-discuss] Train patch elimination Yong's suggestion to check the server's BMC settings is good. Some servers such as Dell, have an 'Enable IPMI over LAN setting. Do you see a BMC access alarm ? > fm alarm-list Try to ping the target server BMC. If that works then I suggest you try and read the sensors manually using ipmitool. ipmitool -I lanplus -H -U -P sensor list If a list of sensors is displayed and you can't see the sensor list with 'system host-sensor-list' then 1. Inspect recent logs in /var/log/mtcAgent.log and var/log/hwmond.log looking for logs that pertain to BMC accesses. 2. Check that your provisioned username, ip address and password are correct. Try deprovisioning and reprovisioning the BMC. > system host-update bm_type=none And then provision again ensuring the credentials are correct. Wait 5-10 minutes Tail mtcAgent and hwmond.log files. If there is a failure the logs will help us narrow in on the issue. 3. Provide output of the following commands cat /var/run/bmc/* ls -r /var/run/bmc/* 4. Ideally compress and attach the mtcAgent.log file Eric. -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: Sunday, November 10, 2019 8:27 PM To: Alonso, Juan Carlos; Chen, Yan; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: Re: [Starlingx-discuss] Train patch elimination JC, Have you enabled BMC config in your test servers and BIOS? If so, please use "ipmitool" utility to have a try to read sensor info. regards, Yong On 2019/11/8 11:29 PM, Alonso, Juan Carlos wrote: > Hello Yan/community, > > Any update on this? (: > > Regards. > > Juan Carlos Alonso > > *From:* Alonso, Juan Carlos > *Sent:* Thursday, November 7, 2019 9:56 AM > *To:* Chen, Yan ; Hu, Yong ; > Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io > *Cc:* Cabrales, Ada > *Subject:* RE: Train patch elimination > > Hello Yan, > > Thank you for your response. > > Same question now for: > > _Horizon/Custom Confirmation Messages : Custom confirmation message > for Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor._ > > I added the bmc_ip, bmc_type, bmc_username and bmc_password for each > node, but I cannot display any sensors on Horizon nor CLI. > > $ system host-update compute-0 bm_username= > bm_password= bm_type=bmc bm_ip= > > $ system host-lock compute-0 > > $ system host-sensor-list compute-0 > > > > $ system host-unlock compute-0 > > $ system host-sensor-list compute-0 > > > > Is there any other configuration needed or is this feature not > supported anymore? > > Regards. > > Juan Carlos Alonso > > *From:* Chen, Yan > > *Sent:* Thursday, November 7, 2019 12:15 AM > *To:* Alonso, Juan Carlos >; Hu, Yong >; Gerry.Kopec at windriver.com > ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Carlos, > > Please remove _Horizon/CSRF AngularJS Fixes_ related cases in your > test plan, which are originally planned for STX additional patches, as > those patches are already removed from our project and not upstreamed. > > Yan > > *From:* Alonso, Juan Carlos > > *Sent:* Wednesday, November 6, 2019 23:18 > *To:* Hu, Yong >; Chen, > Yan >; > Gerry.Kopec at windriver.com ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Hello, > > I hope also the community can help with this questions. > > @Chen, Yan > > Can you help me to verify if this feature is still disabled on Train > version: _Horizon/CSRF AngularJS Fixes_? > > On last test plan for Stein this feature was no longer required on > Horizon and was disabled on SarlingX code. > > @Gerry.Kopec at windriver.com > > About the Live Migration bugs I mentioned on the last meeting, almost > all of them are merged, except the last three. > > All those patches are related to live migration, so my question is if > I perform live migrations such patches will be covered or should be > tested in a different way? > > The last three were marked as Unlikely and was not merged on Stein. I > don’t have more info about such patches. > > Enable delete bound trunk for linux bridge agent: > https://review.opendev.org/#/c/605589 > > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): > https://review.opendev.org/#/c/623401 and > https://review.opendev.org/#/c/626109 > > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): > https://review.opendev.org/#/c/625134 > > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): > https://review.opendev.org/#/c/628071 > > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): > https://review.opendev.org/#/c/623415 > > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): > _https://review.opendev.org/#/c/621507/_ > > Prevent DHCP from processing stale RPC messages: ?? > > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? > > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? > > Regards. > > Juan Carlos Alonso > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Mon Nov 11 17:17:21 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 11 Nov 2019 17:17:21 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Mon Nov 11 19:52:34 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Mon, 11 Nov 2019 19:52:34 +0000 Subject: [Starlingx-discuss] Train patch elimination In-Reply-To: References: <72AD03D27224C74982BE13246D75B39739A7563A@SHSMSX103.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676C10AC4EF@ALA-MBD.corp.ad.wrs.com> Message-ID: <210898B96CA058408C55992CCAD98676C10AC6DA@ALA-MBD.corp.ad.wrs.com> Do you see the same kind of traceback in hwmond_controller-0_thermal_sensor_data ? Your issue looks like mtcAgent selected RedFish as the BMC access protocol after getting a good response but when the hardware monitor queries sensors from this server it gets a redfishtool python exception. Please send me the group of logs for controller-0 from mtcAgent containing the 'redfishUtil_get_bmc_info' label so that I can understand more about the server you have. If you like you can execute the following 2 commands to force the system to use ipmitool instead of redfish. system service-parameter-modify platform maintenance bmc_access_method=ipmi system service-parameter-apply platform Wait a few minutes and then try and read your sensors with the system-sensor-list controller-0 I'd be interested in seeing the raw result of the sensor read commands against this server using redfishtool. time redfishtool -r -u -p Chassis Thermal time redfishtool -r -u -p Chassis Power Basically the same thing but outside daemon control. Eric. -----Original Message----- From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com] Sent: Monday, November 11, 2019 12:12 PM To: MacDonald, Eric; Hu, Yong; Alonso, Juan Carlos; Chen, Yan; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: RE: [Starlingx-discuss] Train patch elimination Importance: High Hi guys, i checked everything in the way that you suggested. MtcAgent.log is showing, im working in a Duplex configuration locked and trying to get sensors from controller-0: p ( 601) redfishUtil_get_bmc_info: Info : controller-0 has 2 Processors ; Ena bled and OK:OK 2019-11-11T10:38:49.554 [1945193.00281] controller-1 mtcAgent --- redfishUtil.cp p ( 624) redfishUtil_get_bmc_info: Info : controller-0 has 96 GiB Memory ; Ena bled and OK:OK 2019-11-11T10:38:49.554 [1945193.00282] controller-1 mtcAgent |-| mtcNodeHdlrs.c pp (6492) bmc_handler : Info : controller-0 bmc audit timer started (120 secs) 2019-11-11T10:38:49.554 [1945193.00283] controller-1 mtcAgent |-| mtcNodeHdlrs.c pp (6507) bmc_handler : Info : controller-0 bmc is accessible using cd /var/run/bmc/ [sysadmin at controller-1 bmc(keystone_admin)]$ ls controller-0 controller-1 ipmitool redfishtool cat /var/run/bmc/ cat controller-0 {"protocol":"redfishtool","power_state":"on"} cat controller-1 {"protocol":"redfishtool","power_state":"on"} cd ipmitool controller-1:/var/run/bmc/ipmitool$ controller-1:/var/run/bmc/ipmitool$ controller-1:/var/run/bmc/ipmitool$ ls controller-1:/var/run/bmc/ipmitool$ edfishtool$ ls hwmond_controller-0_power_sensor_data hwmond_controller-1_power_sensor_data mtcAgent_controller-0_bmc_info mtcAgent_controller-1_bmc_info hwmond_controller-0_thermal_sensor_data hwmond_controller-1_thermal_sensor_data mtcAgent_controller-0_root_query mtcAgent_controller-1_root_query If I check any of the files I got this: cat hwmond_controller-0_power_sensor_data redfishtool:Transport: Fatal timeout waiting for response from rhostTraceback (most recent call last): File "/usr/bin/redfishtool", line 18, in main(sys.argv) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolMain.py", line 372, in main rc,r,j,d=runSubCmd(rft) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolMain.py", line 449, in runSubCmd rc,r,j,d=subCmdTable[rft.subcommand](rft,cmdTop=True) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 157, in ChassisMain rc,r,j,d = self.runOperation(rft) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 113, in runOperation rc,r,j,d=operationTable[self.operation](self, op, rft, cmdTop=True) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 428, in getPower rc,r,j,d=op.get(sc, op, rft, cmdTop, resName) File "/usr/lib64/python2.7/site-packages/redfishtool/Chassis.py", line 234, in get sysPath,rc,r,j,d=rft.getPathBy(rft, r, d, prop) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolTransport.py", line 885, in getPathBy rc, r, j, d = rft.listCollection(rft, r, coll, prop) File "/usr/lib64/python2.7/site-packages/redfishtool/redfishtoolTransport.py", line 1025, in listCollection rc,r,j,d=rft.rftSendRecvRequest(rft.AUTHENTICATED_API, 'GET', r.url, relPath=path) AttributeError: 'NoneType' object has no attribute 'url' So , my question should be, is the redfishtool blocking ipmitool to show the values? Because impitool is showing sensors by itself. BR Elio -----Original Message----- From: MacDonald, Eric Sent: Monday, November 11, 2019 8:33 AM To: Hu, Yong ; Alonso, Juan Carlos ; Chen, Yan ; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: Re: [Starlingx-discuss] Train patch elimination Yong's suggestion to check the server's BMC settings is good. Some servers such as Dell, have an 'Enable IPMI over LAN setting. Do you see a BMC access alarm ? > fm alarm-list Try to ping the target server BMC. If that works then I suggest you try and read the sensors manually using ipmitool. ipmitool -I lanplus -H -U -P sensor list If a list of sensors is displayed and you can't see the sensor list with 'system host-sensor-list' then 1. Inspect recent logs in /var/log/mtcAgent.log and var/log/hwmond.log looking for logs that pertain to BMC accesses. 2. Check that your provisioned username, ip address and password are correct. Try deprovisioning and reprovisioning the BMC. > system host-update bm_type=none And then provision again ensuring the credentials are correct. Wait 5-10 minutes Tail mtcAgent and hwmond.log files. If there is a failure the logs will help us narrow in on the issue. 3. Provide output of the following commands cat /var/run/bmc/* ls -r /var/run/bmc/* 4. Ideally compress and attach the mtcAgent.log file Eric. -----Original Message----- From: Yong Hu [mailto:yong.hu at intel.com] Sent: Sunday, November 10, 2019 8:27 PM To: Alonso, Juan Carlos; Chen, Yan; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada Subject: Re: [Starlingx-discuss] Train patch elimination JC, Have you enabled BMC config in your test servers and BIOS? If so, please use "ipmitool" utility to have a try to read sensor info. regards, Yong On 2019/11/8 11:29 PM, Alonso, Juan Carlos wrote: > Hello Yan/community, > > Any update on this? (: > > Regards. > > Juan Carlos Alonso > > *From:* Alonso, Juan Carlos > *Sent:* Thursday, November 7, 2019 9:56 AM > *To:* Chen, Yan ; Hu, Yong ; > Gerry.Kopec at windriver.com; starlingx-discuss at lists.starlingx.io > *Cc:* Cabrales, Ada > *Subject:* RE: Train patch elimination > > Hello Yan, > > Thank you for your response. > > Same question now for: > > _Horizon/Custom Confirmation Messages : Custom confirmation message > for Suppress Sensor Group, Relearn Sensor Model and Suppress Sensor._ > > I added the bmc_ip, bmc_type, bmc_username and bmc_password for each > node, but I cannot display any sensors on Horizon nor CLI. > > $ system host-update compute-0 bm_username= > bm_password= bm_type=bmc bm_ip= > > $ system host-lock compute-0 > > $ system host-sensor-list compute-0 > > > > $ system host-unlock compute-0 > > $ system host-sensor-list compute-0 > > > > Is there any other configuration needed or is this feature not > supported anymore? > > Regards. > > Juan Carlos Alonso > > *From:* Chen, Yan > > *Sent:* Thursday, November 7, 2019 12:15 AM > *To:* Alonso, Juan Carlos >; Hu, Yong >; Gerry.Kopec at windriver.com > ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Carlos, > > Please remove _Horizon/CSRF AngularJS Fixes_ related cases in your > test plan, which are originally planned for STX additional patches, as > those patches are already removed from our project and not upstreamed. > > Yan > > *From:* Alonso, Juan Carlos > > *Sent:* Wednesday, November 6, 2019 23:18 > *To:* Hu, Yong >; Chen, > Yan >; > Gerry.Kopec at windriver.com ; > starlingx-discuss at lists.starlingx.io > > *Cc:* Cabrales, Ada > > *Subject:* RE: Train patch elimination > > Hello, > > I hope also the community can help with this questions. > > @Chen, Yan > > Can you help me to verify if this feature is still disabled on Train > version: _Horizon/CSRF AngularJS Fixes_? > > On last test plan for Stein this feature was no longer required on > Horizon and was disabled on SarlingX code. > > @Gerry.Kopec at windriver.com > > About the Live Migration bugs I mentioned on the last meeting, almost > all of them are merged, except the last three. > > All those patches are related to live migration, so my question is if > I perform live migrations such patches will be covered or should be > tested in a different way? > > The last three were marked as Unlikely and was not merged on Stein. I > don’t have more info about such patches. > > Enable delete bound trunk for linux bridge agent: > https://review.opendev.org/#/c/605589 > > 0040-rpc-removing-timeout-backoff-multiplier.patch (2e4ca00): > https://review.opendev.org/#/c/623401 and > https://review.opendev.org/#/c/626109 > > 0062-dvr-force-admin-state-update-before-distri.patch (edf9731): > https://review.opendev.org/#/c/625134 > > 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911): > https://review.opendev.org/#/c/628071 > > 0077-api-reject-routes-with-invalid-network-val.patch (6ed8fe6): > https://review.opendev.org/#/c/623415 > > 0014-add-support-for-querying-quotas-with-usage.patch (71c07d7): > _https://review.opendev.org/#/c/621507/_ > > Prevent DHCP from processing stale RPC messages: ?? > > 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89): ?? > > 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491): ?? > > Regards. > > Juan Carlos Alonso > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Nov 11 22:30:26 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 11 Nov 2019 22:30:26 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Updated with Nov 12 Agenda: 1. Updates on container features. Four stx.3.0 features not yet fully merged/completed: 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] 2005514: QAT K8S device plugin support in StarlingX [Mingyuan Qi[ 2004766: Integrate Distributed Cloud with containers --> only item left is to complete feature test - Peng Peng: is this now complete? 2006274: Support authenticated registry for bootstrap and application apply --> only item left is to complete feature test - Chris Winnicki: is this now complete? 2. Updates on subset of stx.4.0 features: 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] 2006145: Kata container support [Shuicheng Lin] 3. Updates on gating LPs - focus on 6 high priority ones in stx.2.0 and stx.3.0 Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3073 bytes Desc: not available URL: From sgw at linux.intel.com Tue Nov 12 02:06:38 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 11 Nov 2019 18:06:38 -0800 Subject: [Starlingx-discuss] Removing 'pike' from mirror in stx-tools and docs Message-ID: <5491a8b0-ef13-29f8-ee89-b9623b6b1e5c@linux.intel.com> Hi Scott, Don: I have a pair of patches pending to remove the OpenStack pike release name from the mirror tools and docs. https://review.opendev.org/#/q/topic:remove_pike+status:open Can you let me know what affect this will have on the Cengn Jenkins jobs and when we can coordinate this change? Thanks Sau! From austin.sun at intel.com Tue Nov 12 06:54:12 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 12 Nov 2019 06:54:12 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/13/2019 Message-ID: Agenda for 11/13 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Nov 12 09:01:45 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 12 Nov 2019 09:01:45 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: Message-ID: Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Nov 12 15:25:37 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Nov 2019 15:25:37 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Nov 12 15:54:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 12 Nov 2019 15:54:07 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 12 15:54:17 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Nov 2019 15:54:17 +0000 Subject: [Starlingx-discuss] Removing 'pike' from mirror in stx-tools and docs In-Reply-To: <5491a8b0-ef13-29f8-ee89-b9623b6b1e5c@linux.intel.com> References: <5491a8b0-ef13-29f8-ee89-b9623b6b1e5c@linux.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA255@ALA-MBD.corp.ad.wrs.com> Maybe there's some conditional that could be added, as prep for the update: $ grep pike */config.xml STX_BUILD_container_setup/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $STX_INSTALLER_DIR/initrd.img STX_BUILD_container_setup/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $STX_INSTALLER_DIR/vmlinuz STX_BUILD_container_setup/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $STX_INSTALLER_DIR/squashfs.img STX_build_docker_flock_images/config.xml:dev-centos-pike-${TIMESTAMP} STX_build_installer/config.xml:echo '$MY_REPO_ROOT_DIR/stx-tools/toCOPY/generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/' | $DOCKER_CMD STX_build_installer/config.xml:echo '$MY_REPO_ROOT_DIR/stx-tools/toCOPY/populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/' | $DOCKER_CMD STX_build_master_pike/config.xml:export OPENSTACK_RELEASE=pike STX_build_pre_installer/config.xml:echo '$MY_REPO_ROOT_DIR/stx-tools/toCOPY/generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/' | $DOCKER_CMD STX_build_pre_installer/config.xml:echo '$MY_REPO_ROOT_DIR/stx-tools/toCOPY/populate_downloads.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/' | $DOCKER_CMD STX_download_mirror/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $STX_INSTALLER_DIR/initrd.img STX_download_mirror/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $STX_INSTALLER_DIR/vmlinuz STX_download_mirror/config.xml: cp centos-mirror-tools/output/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $STX_INSTALLER_DIR/squashfs.img STX_retag_docker_images/config.xml:dev-centos-pike-${TIMESTAMP} For STX_BUILD_container_setup and STX_download_mirror, this could just be an existence check. For STX_build_installer and STX_build_pre_installer, maybe something like: grep -q 'ORIGIN=.*pike' $MY_REPO_ROOT_DIR/stx-tools/toCOPY/generate-cgcs-tis-repo -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Monday, November 11, 2019 9:07 PM To: Little, Scott; Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Removing 'pike' from mirror in stx-tools and docs Hi Scott, Don: I have a pair of patches pending to remove the OpenStack pike release name from the mirror tools and docs. https://review.opendev.org/#/q/topic:remove_pike+status:open Can you let me know what affect this will have on the Cengn Jenkins jobs and when we can coordinate this change? Thanks Sau! From Bin.Qian at windriver.com Tue Nov 12 16:26:10 2019 From: Bin.Qian at windriver.com (Qian, Bin) Date: Tue, 12 Nov 2019 16:26:10 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com>, <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> Message-ID: The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Tue Nov 12 16:38:29 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 12 Nov 2019 16:38:29 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Message-ID: Note: We will now meet on Tuesdays (usually bi-weekly) - the next meeting will be Tuesday Nov 26 Minutes from today's meeting: 1. Updates on container features. Four stx.3.0 features not yet fully merged/completed: 2005937: Intel GPU K8s device plugin support in StarlingX [An Ran] 2005514: QAT K8S device plugin support in StarlingX [Mingyuan Qi[ - Main patches for GPU & QAT are in. - Remaining tasks are not gating stx.3.0: - Final work item is an enhancement for validation when adding labels - This is tracked via: https://review.opendev.org/#/c/691699/ - Mingyuan will also have 1 commit to merge that will depend on this commit from Ran. 2004766: Integrate Distributed Cloud with containers --> only item left is to complete feature test - Peng Peng: what is the forecast? - Answer: Test is complete; this SB will be marked complete today 2006274: Support authenticated registry for bootstrap and application apply --> only item left is to complete feature test - Chris Winnicki: what is the forecast? - Answer: Test is complete; this SB will be marked complete today 2. Updates on subset of stx.4.0 features: 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Spec is approved; - Currently have 11 commits in review; these need to be re-based this week and then the "8" base commits can merge this week 2006145: Kata container support [Shuicheng Lin] - Request offline update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) - Note: plan is to deliver to stx.4.0 once it opens (which should be in 2 weeks) 3. Updates on gating LPs - focus on 6 high priority ones in stx.2.0 and stx.3.0 (only 2 of 6 discussed during meeting): https://bugs.launchpad.net/starlingx/+bug/1851533/ platform-integ-apps apply failed - tiller on Crash [Austin Sun & Bob Church] - Bob's analysis indicates tiller uses fixes grpc ports 44134 & 44135 which have a conflict with ceph-mgr/ceph-mon using those ports - Austin's analysis indicates the issues was introduced by 2 of Bin Qian's commits https://review.opendev.org/#/c/691714 and https://review.opendev.org/#/c/692439 - Austin tested by reverting these and that prevented the issue from occurring. - Next step: Will need Bin to revert and work with Bob to identify a solution. https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Kevin Smith] - Lock can fail if stx-monitor applied and lock is issued on the standby controller shortly after a controller swact - Issue is the pod terminate fails due to the pod volume mount not being there - Kevin to add a comment to the LP with what he has learned so far and options to address (eg: adding more knowledge in VIM when a lock can proceed or needs to be rejected) 4. Reminder that there are 26 stx.3.0 gating containers bugs and RC1 milestone forecast is Nov 20. Request LP primes work on their LPs and address as many as possible before the end of the stx.3.0 release. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bin.Qian at windriver.com Tue Nov 12 17:34:58 2019 From: Bin.Qian at windriver.com (Qian, Bin) Date: Tue, 12 Nov 2019 17:34:58 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com>, <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com>, Message-ID: While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Tue Nov 12 17:56:10 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Tue, 12 Nov 2019 17:56:10 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> Message-ID: <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Tue Nov 12 17:56:01 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 12 Nov 2019 17:56:01 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191112 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-12 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - Local Storage (2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 08 TCs [BLOCKED] TOTAL: [ 65 TCs ] Standard - 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 ] BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bin.Qian at windriver.com Tue Nov 12 18:10:48 2019 From: Bin.Qian at windriver.com (Qian, Bin) Date: Tue, 12 Nov 2019 18:10:48 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> , <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> Message-ID: Thanks Cristopher, I found the same on latest build as well. I further look into the sys config, I found that recently the config-files/initscripts-config/files/sysctl.conf was altered, and the following was removed. # Limit local port range net.ipv4.ip_local_port_range = 49216 61000 net.ipv4.tcp_tw_reuse = 1 The file is deployed to /etc/sysctl.conf, the setting is the range of local port. Probably some changes that messed up? Thanks, Bin ________________________________ From: Lemus Contreras, Cristopher J [cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, November 12, 2019 9:56 AM To: Qian, Bin; Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 12 18:14:48 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Nov 2019 18:14:48 +0000 Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> Hi all, Please be careful when adding dependencies to your commit messages to ensure the formatting is correct. If it is not, then Gerrit/Zuul may not properly handle the dependency and allow a commit to merge before the dependency is merged. It appears that a space is mandatory after the "Depends-On:" tag. Proper formatting: Depends-On: https://review.opendev.org/XXXXXX Improper: Depends-On:https://review.opendev.org/XXXXXX We saw updates merge this morning prematurely, apparently due to a commit message that was missing this space after the Depends-On tag. As a side note, I believe the syntax of "Depends-On: CHANGE-ID" is deprecated, maybe due to the potential for CHANGE-ID matching multiple reviews. The suggested syntax is to use the Gerrit review URL. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Tue Nov 12 18:15:54 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 12 Nov 2019 18:15:54 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> Message-ID: <9A296723-316C-4D65-A82C-DEBDB670694A@windriver.com> I think this is commit: https://opendev.org/starlingx/config-files/commit/fbc09b8db8a14fbf24976a0f7d8924af7a330f85 Bob From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 12:12 PM To: "Lemus Contreras, Cristopher J" , "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Thanks Cristopher, I found the same on latest build as well. I further look into the sys config, I found that recently the config-files/initscripts-config/files/sysctl.conf was altered, and the following was removed. # Limit local port range net.ipv4.ip_local_port_range = 49216 61000 net.ipv4.tcp_tw_reuse = 1 The file is deployed to /etc/sysctl.conf, the setting is the range of local port. Probably some changes that messed up? Thanks, Bin ________________________________ From: Lemus Contreras, Cristopher J [cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, November 12, 2019 9:56 AM To: Qian, Bin; Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Tue Nov 12 18:27:31 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 12 Nov 2019 18:27:31 +0000 Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> Message-ID: <20191112182731.t76y7ce4ar4a4nws@yuggoth.org> On 2019-11-12 18:14:48 +0000 (+0000), Penney, Don wrote: [...] > As a side note, I believe the syntax of "Depends-On: CHANGE-ID" is > deprecated, maybe due to the potential for CHANGE-ID matching > multiple reviews. The suggested syntax is to use the Gerrit review > URL. The reason using the Change-Id for Depends-On is deprecated is that Zuul v3 added the ability to have multiple connections to different code review systems, so a raw Change-Id is insufficient for locating the review if it's accessed through a different connection. GitHub doesn't even have anything analogous to Gerrit's Change-Id, so Zuul needed to adopt a more generic solution to support it anyway. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Tue Nov 12 18:37:44 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 12 Nov 2019 18:37:44 +0000 Subject: [Starlingx-discuss] Request for docker image build >> OpenStack Train Patches Merged Message-ID: <151EE31B9FCCA54397A757BC674650F0C15EDDFF@ALA-MBD.corp.ad.wrs.com> All train patches have merged: https://review.opendev.org/#/q/topic:train_upgrade+(status:open+OR+status:merged) Scott, As per below, please trigger a docker image build in addition to the regular ISO build. Thanks, Ghada -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Dariush.Eslimi at windriver.com Tue Nov 12 18:41:59 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 12 Nov 2019 18:41:59 +0000 Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> Message-ID: Is it possible to add a zuul check to look for this malformed tag ? and also warn the committer about use of deprecated tags? Dariush From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: November-12-19 1:15 PM To: 'starlingx-discuss at lists.starlingx.io' (starlingx-discuss at lists.starlingx.io) Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge Hi all, Please be careful when adding dependencies to your commit messages to ensure the formatting is correct. If it is not, then Gerrit/Zuul may not properly handle the dependency and allow a commit to merge before the dependency is merged. It appears that a space is mandatory after the "Depends-On:" tag. Proper formatting: Depends-On: https://review.opendev.org/XXXXXX Improper: Depends-On:https://review.opendev.org/XXXXXX We saw updates merge this morning prematurely, apparently due to a commit message that was missing this space after the Depends-On tag. As a side note, I believe the syntax of "Depends-On: CHANGE-ID" is deprecated, maybe due to the potential for CHANGE-ID matching multiple reviews. The suggested syntax is to use the Gerrit review URL. Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Tue Nov 12 18:49:45 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Tue, 12 Nov 2019 18:49:45 +0000 Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> Message-ID: <20191112184945.oo3kkdc4mxnubtap@yuggoth.org> On 2019-11-12 18:41:59 +0000 (+0000), Eslimi, Dariush wrote: > Is it possible to add a zuul check to look for this malformed tag > ? and also warn the committer about use of deprecated tags? [...] You could add some sort of job to look for the mistyped version with the missing space, I suppose, but that wouldn't catch the myriad of other ways you could also mistype it. Another common example is folks using review.openstack.org instead of review.opendev.org in the hyperlink text (this will similarly cause it not to be used), but you could just as easily type Depend-On without the "s" or forget the ":" or use "_" instead of "-" or any of a number of other possibilities. There is no substitute for attention to detail. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From Dariush.Eslimi at windriver.com Tue Nov 12 18:54:46 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 12 Nov 2019 18:54:46 +0000 Subject: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge In-Reply-To: <20191112184945.oo3kkdc4mxnubtap@yuggoth.org> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA3A4@ALA-MBD.corp.ad.wrs.com> <20191112184945.oo3kkdc4mxnubtap@yuggoth.org> Message-ID: I agree that there are no substitutes for attention to detail, but space is easy to overlook and has happened more than once. Dariush -----Original Message----- From: Jeremy Stanley [mailto:fungi at yuggoth.org] Sent: November-12-19 1:50 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Malformed Depends-On tag can cause unexpected merge On 2019-11-12 18:41:59 +0000 (+0000), Eslimi, Dariush wrote: > Is it possible to add a zuul check to look for this malformed tag ? > and also warn the committer about use of deprecated tags? [...] You could add some sort of job to look for the mistyped version with the missing space, I suppose, but that wouldn't catch the myriad of other ways you could also mistype it. Another common example is folks using review.openstack.org instead of review.opendev.org in the hyperlink text (this will similarly cause it not to be used), but you could just as easily type Depend-On without the "s" or forget the ":" or use "_" instead of "-" or any of a number of other possibilities. There is no substitute for attention to detail. -- Jeremy Stanley From maria.g.perez.ibarra at intel.com Tue Nov 12 20:53:40 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 12 Nov 2019 20:53:40 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 11/12/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 203 Fail = 6 Blocked = 8 Not Run = 55 Obsolete = 2 Deferred = 0 Total executed = 209 Pass Rate = 97% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 154 Fail = 9 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 163 Pass Rate = 94% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 0 Fail = 0 Blocked = 0 Not Run = 467 Obsolete = 0 Deferred = 0 Total executed = 0 Pass Rate = Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon https://bugs.launchpad.net/starlingx/+bug/1849221 --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 12 21:22:04 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Nov 2019 21:22:04 +0000 Subject: [Starlingx-discuss] wheel tarball build broken by train upgrade - review needed in stx/root Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA561@ALA-MBD.corp.ad.wrs.com> Hi all, I hit a failure after rebasing when trying to build the updated wheels tarball, and have opened a review for the fix: https://review.opendev.org/693938 The update for the train upgrade (https://review.opendev.org/688105) added a misconfigured entry in the stable-wheels.cfg file, resulting in the following error: ############################################################ Building rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl ############################################################ Running: wget https://files.pythonhosted.org/packages/c3/8e/079b7cc3a0fc9934ab05d868a00183c7aafd90b5d6138313d98ac2b9f666/rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl --2019-11-12 20:42:05-- https://files.pythonhosted.org/packages/c3/8e/079b7cc3a0fc9934ab05d868a00183c7aafd90b5d6138313d98ac2b9f666/rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl Resolving files.pythonhosted.org (files.pythonhosted.org)... 151.101.125.63, 2a04:4e42:1e::319 Connecting to files.pythonhosted.org (files.pythonhosted.org)|151.101.125.63|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 22303 (22K) [binary/octet-stream] Saving to: 'rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl' 0K .......... .......... . 100% 2.98M=0.007s 2019-11-12 20:42:05 (2.98 MB/s) - 'rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl' saved [22303/22303] tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors Failure running: tar xf rjsmin-1.1.0-cp27-cp27mu-manylinux1_x86_64.whl Once this fix is merged, we can launch a CENGN build with docker images. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Tue Nov 12 21:53:39 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Nov 2019 21:53:39 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Tue Nov 12 23:37:17 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Tue, 12 Nov 2019 23:37:17 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA5C6@ALA-MBD.corp.ad.wrs.com> I've posted an update to align the wheels.cfg with the train upper-constraints and to address this build failure: https://review.opendev.org/693949 I've set W-1 while I test building all the images, in case there are other issues to be uncovered. Cheers, Don. -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 4:54 PM To: 'Liu, ZhipengS'; Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Bill.Zvonar at windriver.com Wed Nov 13 01:27:54 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Nov 2019 01:27:54 +0000 Subject: [Starlingx-discuss] Community Call (Nov 13, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B2409F@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191113T1500 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Nov 13 02:08:32 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 13 Nov 2019 02:08:32 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cristopher.j.lemus.contreras at intel.com Wed Nov 13 02:37:03 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Wed, 13 Nov 2019 02:37:03 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: <9A296723-316C-4D65-A82C-DEBDB670694A@windriver.com> References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> <9A296723-316C-4D65-A82C-DEBDB670694A@windriver.com> Message-ID: <072358F2-62FB-4447-B63C-62B1968B5AE8@intel.com> Hi Austin, An update about the EB that you sent us (http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs), in summary: * A full sanity was executed for all configs once. All TC passed. * An Standard with external storage was installed 3 times (because this is where the issue appeared more times), tiller pod was running fine. * Port range is also like this: controller-0:~$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 If I understood, we had good luck the three times and tiller port was not in use. Please, let me know if you need additional details. Thanks & Regards Cristopher Lemus From: "Church, Robert" Date: Tuesday, November 12, 2019 at 12:15 PM To: "Qian, Bin" , "Lemus Contreras, Cristopher J" , "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 I think this is commit: https://opendev.org/starlingx/config-files/commit/fbc09b8db8a14fbf24976a0f7d8924af7a330f85 Bob From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 12:12 PM To: "Lemus Contreras, Cristopher J" , "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Thanks Cristopher, I found the same on latest build as well. I further look into the sys config, I found that recently the config-files/initscripts-config/files/sysctl.conf was altered, and the following was removed. # Limit local port range net.ipv4.ip_local_port_range = 49216 61000 net.ipv4.tcp_tw_reuse = 1 The file is deployed to /etc/sysctl.conf, the setting is the range of local port. Probably some changes that messed up? Thanks, Bin ________________________________ From: Lemus Contreras, Cristopher J [cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, November 12, 2019 9:56 AM To: Qian, Bin; Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" , "Khalil, Ghada" , "Sun, Austin" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Qian, Bin Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Wed Nov 13 03:18:07 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 13 Nov 2019 03:18:07 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> Message-ID: <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Wed Nov 13 03:48:53 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Nov 2019 03:48:53 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA6FC@ALA-MBD.corp.ad.wrs.com> 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Wed Nov 13 04:30:24 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Nov 2019 04:30:24 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From zhipengs.liu at intel.com Wed Nov 13 05:28:33 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 13 Nov 2019 05:28:33 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA6FC@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA6FC@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C7530F6CE9@SHSMSX104.ccr.corp.intel.com> Hi Don, See my inline comment. Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 11:49 To: Liu, ZhipengS ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' ; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? Zhipeng: Yes, I updated this patch VERY later with my comment, as I saw some incompatible error though they do not impact pod start/stop and sanity test. 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. Zhipeng: Yes, we thought it will be OK with a clean build without workaround. We found the root cause but not used a right Method, we should have consult you earlier. Sorry for that! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From build.starlingx at gmail.com Wed Nov 13 08:33:09 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 03:33:09 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_wheels - Build # 145 - Failure! Message-ID: <381659171.376.1573633990650.JavaMail.javamailuser@localhost> Project: STX_build_wheels Build #: 145 Status: Failure Timestamp: 20191113T082001Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T051926Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T051926Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T051926Z/logs OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T051926Z/logs From build.starlingx at gmail.com Wed Nov 13 08:33:13 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 03:33:13 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 144 - Failure! Message-ID: <581501518.379.1573633993866.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 144 Status: Failure Timestamp: 20191113T081547Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T051926Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T051926Z 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/20191113T051926Z/logs MASTER_BUILD_NUMBER: 316 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T051926Z/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: 20191113T051926Z DOCKER_BUILD_ID: jenkins-master-20191113T051926Z-builder TIMESTAMP: 20191113T051926Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T051926Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T051926Z/outputs From build.starlingx at gmail.com Wed Nov 13 08:33:16 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 03:33:16 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 316 - Failure! Message-ID: <1282138817.382.1573633997307.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 316 Status: Failure Timestamp: 20191113T051926Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T051926Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From austin.sun at intel.com Wed Nov 13 08:54:22 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 13 Nov 2019 08:54:22 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: <072358F2-62FB-4447-B63C-62B1968B5AE8@intel.com> References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> <9A296723-316C-4D65-A82C-DEBDB670694A@windriver.com> <072358F2-62FB-4447-B63C-62B1968B5AE8@intel.com> Message-ID: Thanks a lot Cristopher. The commit fbc09b8db8a14fbf24976a0f7d8924af7a330f85 was merged two months ago. LP# 1851533 was reported since 11/05, and never reported before 11/05. I cannot understand this part. Thanks. BR Austin Sun. From: Lemus Contreras, Cristopher J Sent: Wednesday, November 13, 2019 10:37 AM To: Church, Robert ; Qian, Bin ; Jones, Bruce E ; Khalil, Ghada ; Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Austin, An update about the EB that you sent us (http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs), in summary: * A full sanity was executed for all configs once. All TC passed. * An Standard with external storage was installed 3 times (because this is where the issue appeared more times), tiller pod was running fine. * Port range is also like this: controller-0:~$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 If I understood, we had good luck the three times and tiller port was not in use. Please, let me know if you need additional details. Thanks & Regards Cristopher Lemus From: "Church, Robert" > Date: Tuesday, November 12, 2019 at 12:15 PM To: "Qian, Bin" >, "Lemus Contreras, Cristopher J" >, "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 I think this is commit: https://opendev.org/starlingx/config-files/commit/fbc09b8db8a14fbf24976a0f7d8924af7a330f85 Bob From: "Qian, Bin" > Date: Tuesday, November 12, 2019 at 12:12 PM To: "Lemus Contreras, Cristopher J" >, "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Thanks Cristopher, I found the same on latest build as well. I further look into the sys config, I found that recently the config-files/initscripts-config/files/sysctl.conf was altered, and the following was removed. # Limit local port range net.ipv4.ip_local_port_range = 49216 61000 net.ipv4.tcp_tw_reuse = 1 The file is deployed to /etc/sysctl.conf, the setting is the range of local port. Probably some changes that messed up? Thanks, Bin ________________________________ From: Lemus Contreras, Cristopher J [cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, November 12, 2019 9:56 AM To: Qian, Bin; Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" > Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin >; Perez Ibarra, Maria G >; starlingx-discuss at lists.starlingx.io; Cabrales, Ada >; Qian, Bin > Cc: Eslimi, Dariush > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Nov 13 09:05:46 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 13 Nov 2019 03:05:46 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$709pr6@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191113T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From austin.sun at intel.com Wed Nov 13 14:46:26 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 13 Nov 2019 14:46:26 +0000 Subject: [Starlingx-discuss] MoM Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/13/2019 Message-ID: Hi All: Thanks join this meeting. Mom for 11/13 meeting: - Ceph containerization update (Tingjie/martin) Please review the BP of Enable BlueStore based on containerized Ceph: https://review.opendev.org/#/c/692502/ SB of Ceph containerization: https://storyboard.openstack.org/#!/story/2005527 Current active subtask: 36443: Rook application integration. Ongoing OTA: Nov 22th Martin 36444: mapping ceph.pp setting to yaml override. Ongoing OTA: Dec 6th Martin might still depends on puppet. still under anlysis , update for detail next week. 37432: Rook plugin implementation with common infrastructure. Ongoing OTA: Dec 6th Tingjie - CentOS 8.0 upgrade planning (Shuai Zhao) 1) container builder env and mock env ( bash package was successfully built in this env, kernel is still under building) will build other srpm packages to verify this env. 2) kernel patches , 9 patches was built successfully on CentOS 8 bare metal env (need double confirm dropped patches) will build kernel w/ stx patches on centos8 container build env. kernel config difference between centos7 and centos8 ? make defoldconfig or make silentoldconfig (maybe make syncconfig [for 4.19]) complex part, and need more review once done. 3) el8 srpm 51 puppet/openstack srpm are not available yet, Steps should be 1) build iso, 2) boot (anaconda and kickstart etc) 3) ansible/puppet config host. 4) enable application such as ceph, openstack. feature branch has been created , --- pending review. - CVE LP fixing (Shui Cheng) 3 issues , 1 is under review. 2nd should be under review by end of this week, 3rd should be kernel upgrade. 1st under review and other packages were tested by RedHat together. will discuss on security meeting more. - Opens (all) Thanks. BR Austin Sun. From: Sun, Austin Sent: Tuesday, November 12, 2019 2:54 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/13/2019 Agenda for 11/13 meeting: - Ceph containerization update (Tingjie) - CentOS 8.0 upgrade planning (Shuai Zhao) - CVE LP fixing (Shui Cheng) - Opens (all) Thanks. BR Austin Sun. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Nov 13 16:24:20 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 13 Nov 2019 16:24:20 +0000 Subject: [Starlingx-discuss] Community Call (Nov 13, 2019) In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B2409F@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B2409F@ALA-MBD.corp.ad.wrs.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B244C2@ALA-MBD.corp.ad.wrs.com> >From today's call... - Gerrit reviews that need attention - Saul: PSA / review request - feature branches set up for the CentOS 8 work that's beginning - CentOS 8 was released in October, our plan is to get it in in stx.4.0; work starting now in the side branches - Saul's mail: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006895.html - the reviews: https://review.opendev.org/#/q/status:open++branch:f/centos8+topic:centos8 - Reviews to enable train images to build - Need review by Saul (+2/W+1) - done! - https://review.opendev.org/#/c/693949/ - https://review.opendev.org/#/c/693938/ - this is per http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006921.html - 2 issues - failure to build the wheels tarball and failure due to Train updates - Don has sorted these out, per the reviews just above - Zhipeng to provide a root cause analysis for next week's call - sanity - any reds since last call? - yes, several - Docker image builds are failing after train upgrade patches merged on Nov 12 - https://bugs.launchpad.net/starlingx/+bug/1851533 (platform-integ-apps apply failed - tiller on Crash) - related to tiller - Bob looking at workaround, pulling this out - potential side effects? - any unanswered calls for assistance on the mailing list - Chiing-Ting Huang: sriov-network-device container issue http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006850.html - Don will send an update on the mailing list - Philip Wang: How to configure compute note PTP as Master http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006848.html - per Brent, this isn't supported, Bill to send a response to Philip - Wecome to JITStack - Cherish Cao & Linda Jia - welcome! - Sai Chandu / Pavan (Calsoft): AIO-SX with OpenStack - We are ready with StarlingX all-in-one simplex edgex with Openstack. We will share latest images and doc. - Earlier we shared without open stack , now we are ready with Openstack. - Kris: has started discussion with Scott about hosting these files on CENGN - Scott/Saul - would make sense to get CENGN to build these post-release - stx.3.0 Update - Milestone-3 to be declared this week once issues above related to train are addressed. Other features are done or wrapping up testing. - Feature Testing is at 100% execution - Regression Testing is at 44% execution - Need community to focus on scrubbing and addressing bugs. Request PLs/TLs to start driving the backlog down. - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 - Current count is high at 89 -- 21 are critical/high (a fair # of CVEs which are only visible to the security team - Current date for creating the RC1 branch is Nov 20 - Is this too early? Should we hold off until the bug backlog is reduced? - Agreed to push RC1 branch creation to Nov 25 for now Open AR Updates - Oct 23, 2019 -- Bill -- CalSoft Image - Bill to raise AR to find a long term home for this - Nov 13: will look at the possibility of storing this at CENGN once we get the "big files" capability - consider the questions that Scott has about this e.g. retention policy - Oct 9, 2019 -- Frank -- see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done - Nov 13: Saul & Bin Yang are being added - Build team will discuss the timing. - Sep 11, 2019 -- Bruce -- identify the feature documentation gaps - Nov 13: Kris - let's leave it here for now, will update in next week's meeting - July 31, 2019 -- Ada/Yang -- combine sanity runs/reports - Nov 13: per Ada, still working through some issues with Pytest, will set a new date this week - June 26, 2019 -- Yang -- arrange an automation framework info session for the Community - Nov 13: per Ada, this will be addressed once they sort out the Pytest issues (per last AR) - May 8, 2019 -- Frank -- follow up with CENGN on storage for really large files for reference in Launchpads - Nov 13: CENGN had to delay setting this up - plan is for this to be setup next week and a small trial with a few people will be done before opening this up to the community. From: Zvonar, Bill Sent: Tuesday, November 12, 2019 8:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Community Call (Nov 13, 2019) Hi all, reminder of the Community call tomorrow. Feel free to add new topics to the agenda at [0]. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191113T1500 From Don.Penney at windriver.com Wed Nov 13 18:12:54 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Nov 2019 18:12:54 +0000 Subject: [Starlingx-discuss] sriov-network-device container issue In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAA74@ALA-MBD.corp.ad.wrs.com> There are two references in r/stx.2.0 that configure the image tag to be used for the k8s-plugins-sriov-network-device image: https://opendev.org/starlingx/ansible-playbooks/src/branch/r/stx.2.0/playbookconfig/src/playbooks/bootstrap/roles/bringup-essential-services/templates/sriov-plugin.yaml.j2#L43 https://opendev.org/starlingx/config/src/branch/r/stx.2.0/puppet-manifests/src/modules/platform/templates/sriovdp-daemonset.yaml.erb#L43 It may only be the ansible-playbooks reference that has any effect, as the puppet-manifests reference may be stale code. The k8s-cni-sriov and k8s-plugins-sriov-network-device images are built as part of the regular build, and tagged with a versioned tag and a latest tag, as with the other stx images. However, these are loaded as part of the built-in platform-integ-app and therefore uses the static image tag that’s in the repo. What this means is that every load is referencing the master-stable-centos-latest tag when you initially bring up the system, which would be the latest weekly build at that time. This may not always work, if there is something incompatible in the new image. This is presumably what’s happened here with 2.0. My suggestion would be to treat these images, built from upstream sources, specially and manually tag them with versions as needed, updating the static references to those tags. In r/stx.2.0, we could update these static tags to the appropriate tag for that build - presumably the one referenced below by Ting. Going forward, we can manually tag the image in docker hub with whatever format we choose - such as 1.0.0, or maybe whatever version corresponds to the upstream repo at that time (ie. v3.0.0). Once we’ve manually tagged the image, we push an update into the repo to update the static reference to use the new tag. So for example: k8s-cni-sriov: Currently building from https://github.com/intel/sriov-cni/commit/365c8f8cc1204df84f3e976ea30f113e733ca665, which looks like it’s tagged as v2.2. We could retag the current build as starlingx/k8s-cni-sriov:v2.2, then update ansible-playbooks with the new tag. k8s-plugins-sriov-network-device: Building from: https://github.com/intel/sriov-network-device-plugin/commit/000db15405f3ce3b7c2f9feb180c3051aa3f7aea, tagged as v3.1. We could retag the current build as starlingx/k8s-plugins-sriov-network-device:v3.1, then update ansible-playbooks with the new tag. Whenever there’s new content in these images we want to pick up, we retag the new build, and push updates to the static references. From: Chiing-Ting Huang [mailto:chiinting at gmail.com] Sent: Monday, November 04, 2019 10:17 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] sriov-network-device container issue Dear StarlingX Team I have installed StarlingX R2.0 in September, and kube-sriov-device-plugin can get VF at that time. I think the team updated starlingx/k8s-plugins-sriov-network-device docker image in October, so I cannot get VF now. So I roll back to starlingx/k8s-plugins-sriov-network-device:rc-2.0-centos-stable-20190826T233000Z.0 Best regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Wed Nov 13 18:47:53 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 13 Nov 2019 12:47:53 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$70f2s9@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191113T051926Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From build.starlingx at gmail.com Wed Nov 13 21:32:05 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 16:32:05 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! Message-ID: <1844546305.386.1573680726555.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 138 Status: Failure Timestamp: 20191113T185330Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T154115Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20191113T154115Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/logs PUBLISH_TIMESTAMP: 20191113T154115Z FLOCK_VERSION: master-centos-stable-20191113T154115Z PREFIX: master TIMESTAMP: 20191113T154115Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Nov 13 21:32:08 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 16:32:08 -0500 (EST) Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_images - Build # 145 - Still Failing! In-Reply-To: <1789914341.377.1573633991493.JavaMail.javamailuser@localhost> References: <1789914341.377.1573633991493.JavaMail.javamailuser@localhost> Message-ID: <1096524042.389.1573680729659.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 145 Status: Still Failing Timestamp: 20191113T183633Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T154115Z 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/20191113T154115Z/logs MASTER_BUILD_NUMBER: 317 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/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: 20191113T154115Z DOCKER_BUILD_ID: jenkins-master-20191113T154115Z-builder TIMESTAMP: 20191113T154115Z OS_VERSION: 7.5.1804 BUILD_STREAM: stable PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/outputs From build.starlingx at gmail.com Wed Nov 13 21:32:13 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Nov 2019 16:32:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_master - Build # 317 - Still Failing! In-Reply-To: <424668327.380.1573633994718.JavaMail.javamailuser@localhost> References: <424668327.380.1573633994718.JavaMail.javamailuser@localhost> Message-ID: <378220387.392.1573680733741.JavaMail.javamailuser@localhost> Project: STX_build_master_master Build #: 317 Status: Still Failing Timestamp: 20191113T154115Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From maria.g.perez.ibarra at intel.com Wed Nov 13 23:49:25 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 13 Nov 2019 23:49:25 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191113 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-13 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - 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 - 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 ] BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Nov 14 00:27:59 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 14 Nov 2019 00:27:59 +0000 Subject: [Starlingx-discuss] [Build] No Build Meeting this week Message-ID: As neither Saul nor I can attend this week, the usual Thursday Build meeting will not be held this week. Our next Build meeting will be Thursday Nov 21. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Nov 14 03:33:19 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 14 Nov 2019 03:33:19 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! In-Reply-To: <1844546305.386.1573680726555.JavaMail.javamailuser@localhost> References: <1844546305.386.1573680726555.JavaMail.javamailuser@localhost> Message-ID: Hi All: >From log : http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs/jenkins-STX_build_docker_flock_images-138.log.html python-cephclient can not be found in upper-constraints.txt https://review.opendev.org/#/c/694192/ will fix this issue. Stx-horizon image can be built successfully w/ this patch in local env. Thanks. BR Austin Sun. -----Original Message----- From: build.starlingx at gmail.com Sent: Thursday, November 14, 2019 5:32 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! Project: STX_build_docker_flock_images Build #: 138 Status: Failure Timestamp: 20191113T185330Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T154115Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20191113T154115Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/logs PUBLISH_TIMESTAMP: 20191113T154115Z FLOCK_VERSION: master-centos-stable-20191113T154115Z PREFIX: master TIMESTAMP: 20191113T154115Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/outputs REGISTRY: docker.io From zhipengs.liu at intel.com Thu Nov 14 03:44:17 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Thu, 14 Nov 2019 03:44:17 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C7530F6EDA@SHSMSX104.ccr.corp.intel.com> Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 12:30 To: Liu, ZhipengS ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' ; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An embedded message was scrubbed... From: "Sun, Austin" Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! Date: Thu, 14 Nov 2019 03:33:19 +0000 Size: 6194 URL: From sgw at linux.intel.com Thu Nov 7 05:39:31 2019 From: sgw at linux.intel.com (Saul Wold) Date: Wed, 6 Nov 2019 21:39:31 -0800 Subject: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 In-Reply-To: <000001d5924b$34b99e00$9e2cda00$@neusoft.com> References: <001701d58f13$989ffcb0$c9dff610$@neusoft.com> <393877e4-b8d8-59b1-a634-7f405daf00bf@linux.intel.com> <000001d5924b$34b99e00$9e2cda00$@neusoft.com> Message-ID: On 11/3/19 5:32 AM, zhao.shuai wrote: > Hi Saul, Haitao, Shuicheng, > Thank you for your hard work and positive response. > As you suggested in the last StarlingX non-OpenStack distro meeting, > Our team should use Google Docs Or gitHub to show our progress and results in a more real-time way. > Recently, we have moved our work and progress reports to Github. > The StarlingX kernel version to CentOS 4.18 work path is as follows: > https://github.com/StarlingX-Neusoft/Centos8 > I would like to see this work moved to a feature branch in gerrit, so that reviews can happen regularly. This will also allow for builds to be done from that branch once it's futher along. It require an occasional re-base, but we should not have too many conflicts in the integ, compile or utilities repos. > During the porting process, we will update our real-time Q&A information in the documents (StarlingX_CentOS8.0_Kernel_Upgrade_Q&A List.xls). > We hope that the experts in the community can check the problems we have when you have time. > If you can get your advice, we will be very honored. Thank you! > > ① >>Can you explain what you are referring to when you say Patch4000*, I > >>don't know which ones they map to? > Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx > Sheet: [STX Kernel-std Patches Details] STD-Status = Patch > Ok, I found the Excel sheet, but I am still not seeing any mapping to Patch4000* numbering. > ② >>Do you mean "Binary RPM" here? We should be trying to use the latest > >>binary RPMs from CentOS-8 (el8). > Yes, we hope to try this way. > Please see: https://github.com/StarlingX-Neusoft/Centos8/tree/master/cgcs-root/stx > It will take some time to review what you have there, but as suggested above we should create a feature branch for this work to occur in. This will allow your changes to be reviewed via gerrit. One very quick observation is that you should not remove the older Signed-off-by: tags when you rebase the patches. You should add yours to the existing ones, that preserves the identity of who has worked on the patch. > ③ >>We want to fully understand what patches are changing or what additional > >>patches you think you need to add. > Please see:https://github.com/StarlingX-Neusoft/Centos8/blob/master/Kernel_Upgrade_to_4.18-CentOS8_Analysis_2019-10-31.xlsx > Sheet: [srpm] Column E =【CentOS8 SRPM packages(El8)】 Looking at the missing list, it looks like alot of Puppet and OpenStack related python, have you look at puppetlabs for their el8 based repo here: https://yum.puppetlabs.com and https://yum.puppetlabs.com/puppet-release-el-8.noarch.rpm will help setup the repo on a target system. The OpenStack package will come later. Sau! > > ④ >>We need a better method to understand what changes are getting made > >>between these spreadsheet changes. I am not understanding your actual changes. > we have moved our work and progress reports to Github. > Please see: https://github.com/StarlingX-Neusoft/Centos8 > Thanks I have downloaded this repo and will review the history there also. > Thank you very much! > > Best Regards > Wish you happy everyday! > -------------------------------- > Shuai - Neusoft > > -----邮件原件----- > 发件人: Saul Wold > 发送时间: 2019年11月2日 2:28 > 收件人: starlingx-discuss at lists.starlingx.io > 主题: Re: [Starlingx-discuss] Upgrading the StarlingX kernel version to CentOS 4.18 > > I think this message got stuck in the queue, I am just seeing it now. > > On 10/30/19 4:17 AM, zhao.shuai wrote: >> Hi StarlingX Community: >> >> Regarding the task of upgrading the StarlingX kernel version to CentOS 4.18. >> >> Completed Task: >> 1. GCC compiler version upgrade --> GCC version 8.2.1 >> 2. Kernel 4.18 with starlingX patch compilation has been completed.(Patch40004,Patch40007,Patch40008) >> > Can you explain what you are referring to when you say Patch4000*, I > don't know which ones they map to? > >> Doing Task: >> 1. src rpm package el8 upgrade(if there is el8 version) > Do you mean "Binary RPM" here? We should be trying to use the latest > binary RPMs from CentOS-8 (el8). > >> 2. If there is no el8 version of SRPM compilation failed, we need to build a patch fix it. > We want to fully understand what patches are changing or what additional > patches you think you need to add. > >> 3. Configure kernel 4.18 config file with reference to STX kernel 3.10 config file (kernel-3.10.0-x86_64.config.tis_extra) > >> 4. For the el8 version SRPM package that fails to be compiled, the RPM package of the el8 version is preferentially searched for replacement. >> >> Please see the attachment for the results of the advancement >> > We need a better method to understand what changes are getting made > between these spreadsheet changes. I am not understanding your actual > changes. > > Thanks > Sau! > > >> Thank you! >> >> Best Regards >> Wish you happy everyday! >> -------------------------------- >> Shuai - Neusoft >> >> >> -----邮件原件----- >> 发件人: Saul Wold >> 发送时间: 2019年10月18日 5:36 >> 收件人: starlingx-discuss at lists.starlingx.io >> 抄送: Rowsell, Brent >> 主题: Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting >> >> >> Please find attached the spreadsheet analyzing the Kernel patches to the existing CentOS 3.10 kernel. >> >> As mentioned, most of the patches can be dropped, except for the Notification of Death patch. >> >> My understanding is that changes have been made to StarlingX to support the Workqueue CPU affinity model with isolcpus instead of the kthread model that is in the 3.10 kernel. If this is actually the case then we can drop the cpu affinity related patches also. (this would be a good thing). >> >> Don't hesitate to reach out and ask for help with the kernel and/or CentOS 8 User space updates. >> >> Sau! >> >> >> >> >> On 10/16/19 6:53 AM, Xie, Cindy wrote: >>> Agenda & notes for 10/16 meeting: >>> >>> . Ceph containerization update (Tingjie) >>> https://review.opendev.org/#/c/681457/ this is for Helm chart definition, can be review now. >>> https://review.opendev.org/#/c/687340/ for Helm overrides framework, need to extend later. >>> verified in AIO and multi-node provision. >>> configuration needs to be override according to STX parameters. >>> Martin working on this for parameters to align w/ the native deployment. >>> for stx.3.0: only to merge the implantation for Helm chart and override framework. and rook-plugin which support sysinv, this can co-exist w/ current native ceph deployment. >>> test case development is in progress, Tingjie will sync with Fernando. >>> for sysinv, still need to working on patches, not ready for upload/review. >>> AR: Tingjie to send email to the mailing list for the current status & planning for include partial implementation without impacting the native Ceph functionality. >>> >>> . Debranding update (Saul) >>> Starting from the tools repo, the tools in the build area to debrand the mirroring process. Part of this is for ease of use for build steps. Very early stage. Not fit in stx.3.0 scope. >>> https://storyboard.openstack.org/#!/story/2006387, call volunteer from the community. >>> >>> . CentOS 8 upgrade planning (Cindy) CentOS 8.0 2 stories created: >>> https://storyboard.openstack.org/#!/story/2006728, the kernel inside CentOS 8 is 4.18, there is no RT kernel. >>> https://storyboard.openstack.org/#!/story/2006729 >>> Shuai is working on new kernel onto build system. Need to understand each patches. there was an earlier analysis for kernel patches available. >>> AR: Saul please share this analysis to Shuai. against 4.19 kernel some long time ago. >>> See >>> https://docs.google.com/spreadsheets/d/1nKnkweuxcqvVOoRcpnTYMVUUv1RoAu >>> gOWXMjB7VIrfc/edit#gid=311578025 Tab Kernel Patches Details >>> https://github.com/xe1gyq/linux/commits/v4.19 >>> https://github.com/xe1gyq/linux/commits/v4.18 >>> AR: Shuai to provide an Excel sheet to compare RPM/sRPM in StarlingX >>> and in CentOS 8.0 >>> >>> . Opens - none >>> _____________________________________________ >>> From: Xie, Cindy >>> Sent: Tuesday, October 15, 2019 9:39 PM >>> To: Wold, Saul ; >>> 'starlingx-discuss at lists.starlingx.io' >>> ; 'Rowsell, Brent' >>> >>> Subject: RE: Weekly StarlingX non-OpenStack distro meeting >>> >>> >>> Agenda: >>> - Ceph containerization update (Tingjie) >>> - Debranding update (Saul) >>> - CentOS 8 upgrade planning (Cindy) >>> - Opens >>> >>> Cindy Xie >>> IAGS >>> >>> http://starlingx.io/ >>> >>> >>> -----Original Appointment----- >>> From: Xie, Cindy >>> Sent: Thursday, April 25, 2019 5:42 PM >>> To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss at lists.starlingx.io'; 'Rowsell, Brent' >>> Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; >>> 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, >>> Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, >>> Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W >>> Subject: Weekly StarlingX non-OpenStack distro meeting >>> When: Wednesday, October 16, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. >>> Where: https://zoom.us/j/342730236 >>> >>> >>> . Cadence and time slot: >>> o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) . >>> Call Details: >>> o Zoom link: https://zoom.us/j/342730236 o 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 >>> . Meeting Agenda and Minutes: >>> o https://etherpad.openstack.org/p/stx-distro-other >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> >> --------------------------------------------------------------------------------------------------- >> Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) >> is intended only for the use of the intended recipient and may be confidential and/or privileged of >> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is >> not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying >> is strictly prohibited, and may be unlawful.If you have received this communication in error,please >> immediately notify the sender by return e-mail, and delete the original message and all copies from >> your system. Thank you. >> --------------------------------------------------------------------------------------------------- >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > --------------------------------------------------------------------------------------------------- > Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) > is intended only for the use of the intended recipient and may be confidential and/or privileged of > Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is > not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying > is strictly prohibited, and may be unlawful.If you have received this communication in error,please > immediately notify the sender by return e-mail, and delete the original message and all copies from > your system. Thank you. > --------------------------------------------------------------------------------------------------- > From Anirudh.Gupta at hsc.com Mon Nov 11 08:46:54 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 11 Nov 2019 08:46:54 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Message-ID: Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiinting at gmail.com Wed Nov 13 02:25:20 2019 From: chiinting at gmail.com (Chiing-Ting Huang) Date: Wed, 13 Nov 2019 10:25:20 +0800 Subject: [Starlingx-discuss] Alx driver Message-ID: Dear StalingX team I think StarlingX R2.0 didn't module alx driver I can't get Qualcomm Atheros Ar8161 network interface Best Regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Nov 7 07:39:15 2019 From: yong.hu at intel.com (Yong Hu) Date: Thu, 7 Nov 2019 15:39:15 +0800 Subject: [Starlingx-discuss] Error while installing StarlingX Openstack on all-in-one simplex In-Reply-To: References: <72561858-760a-a7e4-fbe8-d0c246f7a191@intel.com> Message-ID: <86eed2ce-593c-7f54-3f80-ed1046a93160@intel.com> According this build info: > BUILD_ID="20190920T013000Z" > > JOB="STX_build_master_master" Your platform ISO was the Cengn build on *master branch* on 0920, whereas your openstack (stx-openstack-1.0-17-centos-stable-latest.tgz ) was from *2.0 RC branch*. That led to the mismatch very likely. Have a try with the attached stx-openstack helm chart tarball, which was originally downloaded from 0920 master build in Cengn. On 2019/11/7 1:31 PM, Saichandu Behara wrote: > Hi yong, > > I have downloaded the StarlingX R2 iso image and dated as around sep > 22,2019. At present i don't have exact link, because, the build dates > are changed now. > > But, I have downloaded the .iso in " > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ " > latest build. > > > Build info ::: > controller-0:~$ cat /etc/build.info > ### > ### StarlingX > ###     Built from master > ### > > OS="centos" > SW_VERSION="19.09" > BUILD_TARGET="Host Installer" > BUILD_TYPE="Formal" > BUILD_ID="20190920T013000Z" > > JOB="STX_build_master_master" > BUILD_BY="starlingx.build at cengn.ca" > BUILD_NUMBER="256" > BUILD_HOST="starlingx_mirror" > BUILD_DATE="2019-09-20 01:30:00 +0000" > > > Please let me know for future solution. It would be a great help. > > > Thanks & Regards > > Sai Chandu Behara > > > > On 07-11-2019 06:39, Yong Hu wrote: >> Hi Sai, >> Could you share the download URL for the installation image (.iso)? >> As well you can tell the build info by: >> cat /etc/build.info >> >> I wonder your issue was caused by a mismatch b/w StarlingX platform >> and this stx-openstack tarball. >> >> regards, >> Yong >> >> On 2019/11/4 7:43 PM, Saichandu Behara wrote: >>> Hello all, >>> >>> I am trying to install StarlingX OpenStack on all-in-one simplex . >>> When i am installing application manifest and helm-charts, getting >>> some versioning error. >>> >>> I downloaded Package from " >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.0/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >>> " and >>> "http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >>> " ( Both are getting errors ). >>> >>> I'm trying to upload the package by using command  " system >>> application-upload stx-openstack-1.0-17-centos-stable-latest.tgz " >>> >>> +---------------+----------------------------------+ >>> | Property      | Value                            | >>> +---------------+----------------------------------+ >>> | active        | False                            | >>> | app_version   | 1.0-17-centos-stable-latest      | >>> | created_at    | 2019-11-04T11:05:19.899672+00:00 | >>> | manifest_file | stx-openstack.yaml               | >>> | manifest_name | armada-manifest                  | >>> | name          | stx-openstack                    | >>> | progress      | None                             | >>> | status        | uploading                        | >>> | updated_at    | None                             | >>> +---------------+----------------------------------+ >>> >>> >>> and when i checking the application list, getting upload failed. >>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>> >>> | application         | version                   | manifest >>> name                 | manifest file  | status        | >>> progress                                  | >>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>> >>> | platform-integ-apps | 1.0-7                     | >>> platform-integration-manifest | manifest.yaml  | applied       | >>> completed                                 | >>> *| stx-openstack       | 1.0-17-centos-stable-     | >>> armada-manifest               | stx-openstack. | **upload-failed**| >>> Upload of application stx-openstack (1.   |** >>> **|                     | latest | | yaml           |               | >>> 0-17-centos-stable-latest) failed:        |** >>> **|                     | | |                |               | >>> Unsupported application version. *      | >>> |                     | | |                | >>> |                                           | >>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>> >>> >>> If anyone is aware of this issue, please let us know. It would be a >>> great help. >>> >>> -- >>> Thanks & Regards >>> Sai Chandu Behara >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> > -------------- next part -------------- A non-text attachment was scrubbed... Name: stx-openstack-1.0-18-centos-stable-latest.tgz Type: application/x-gzip Size: 1186898 bytes Desc: not available URL: From Matt.Peters at windriver.com Fri Nov 8 13:11:35 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 8 Nov 2019 13:11:35 +0000 Subject: [Starlingx-discuss] How to configure compute note PTP as Master In-Reply-To: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> References: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> Message-ID: <411095ED-BF20-46DA-ADFC-B85BB97323D9@windriver.com> Hi Philip, There is currently no mechanism to configure a specific compute host to be a PTP master. That would require enhancements to the current PTP configuration since the current default state is to set up only the internal management network as a PTP slave, and currently that configuration cannot be overridden by the user. We are looking at adding per-interface PTP configuration in the future but depending on the specific device on the compute that you want to configure as a PTP master, it may not specifically address this scenario. To help clarify the use case: Can you describe the clocking architecture in more detail? What is the device that will be on the compute host that will bring in the clocking source? Are you looking to redistribute the clock from the compute, so that it behaves as a boundary clock or will it be a grand master? From: "Philip_Wang at alphanetworks.com" Date: Wednesday, November 6, 2019 at 9:04 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] How to configure compute note PTP as Master Hi Team, Below is PTP architecture in StarlingX. [cid:image003.png at 01D593C1.406FFD30] We need connect a host device that need PTP time sync on compute node. But in StarlingX compute node is slave. * How can we configure or modified PTP in StarlingX let compute node can be Master/Slave BC mode. * Or what architecture should be in StarlingX support host device need PTP time sync. Best Reagrds, * Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 84292 bytes Desc: image001.png URL: From Philip_Wang at alphanetworks.com Mon Nov 11 03:09:12 2019 From: Philip_Wang at alphanetworks.com (Philip_Wang at alphanetworks.com) Date: Mon, 11 Nov 2019 03:09:12 +0000 Subject: [Starlingx-discuss] How to configure compute note PTP as Master In-Reply-To: <411095ED-BF20-46DA-ADFC-B85BB97323D9@windriver.com> References: <9ec243f4e7e2469c9a883e71599ca451@HQMBS2.alphanetworks.com> <411095ED-BF20-46DA-ADFC-B85BB97323D9@windriver.com> Message-ID: <299501eea52d44d19c79e9063c339026@HQMBS2.alphanetworks.com> Dear Peter, The host device may be a RRH for 4G or 5G solution, and compute node is act as MEC. So each RRHs need bring in clock source. In this scenario StarlingX has suggest configure or topologic?? Below is scenario: GM <----> All-In-One(Duplex) <----> RRHs | (SRIOV interface) è All-In-One(Duplex) <----> RRHs Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 From: Peters, Matt Sent: Friday, November 8, 2019 9:12 PM To: Philip_Wang 王季培 (HQ) ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] How to configure compute note PTP as Master Hi Philip, There is currently no mechanism to configure a specific compute host to be a PTP master. That would require enhancements to the current PTP configuration since the current default state is to set up only the internal management network as a PTP slave, and currently that configuration cannot be overridden by the user. We are looking at adding per-interface PTP configuration in the future but depending on the specific device on the compute that you want to configure as a PTP master, it may not specifically address this scenario. To help clarify the use case: Can you describe the clocking architecture in more detail? What is the device that will be on the compute host that will bring in the clocking source? Are you looking to redistribute the clock from the compute, so that it behaves as a boundary clock or will it be a grand master? From: "Philip_Wang at alphanetworks.com" > Date: Wednesday, November 6, 2019 at 9:04 AM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] How to configure compute note PTP as Master Hi Team, Below is PTP architecture in StarlingX. [cid:image003.png at 01D593C1.406FFD30] We need connect a host device that need PTP time sync on compute node. But in StarlingX compute node is slave. - How can we configure or modified PTP in StarlingX let compute node can be Master/Slave BC mode. - Or what architecture should be in StarlingX support host device need PTP time sync. Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 89810 bytes Desc: image003.png URL: From kristal.dale at intel.com Wed Nov 13 23:53:26 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 13 Nov 2019 23:53:26 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-11-13 Message-ID: <43F963BD1517044B90CF82FB2F3CA7162209CA7D@ORSMSX121.amr.corp.intel.com> Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris 2019-11-13 * All -- reviews in progress and recent merges -- ? See summary at https://review.opendev.org/#/q/project:starlingx/docs. ? 7 open: * https://review.opendev.org/#/c/691804/ - * Editorial first pass. More needed before merge? (Mary will do final pass then ready to merge.) * https://review.opendev.org/#/c/693761/ - depends on failed change (TBD) * https://review.opendev.org/#/c/693601/ - DRAFT org for ops guides (needs group review, see agenda item below) * https://review.opendev.org/#/c/692202/ - First draft STX in a box, needs review (Abraham). Needs hosting of image confirmed (see agenda item below) * https://review.opendev.org/#/c/691740/ - * Dev process doc. Once we have Dean's review, ready to merge. * https://review.opendev.org/#/c/689847/ - * STX dist cloud. Ready for editorial (AR: Kris/Mary) * https://review.opendev.org/#/c/694123/ - * Updated ansible param. Needs confirmation of update. Confirmed. (Greg/Abraham) * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs ? https://bugs.launchpad.net/starlingx/+bug/1835207 - fix released! * Closed, three pending reviews are now merged.\ * http://lists.starlingx.io/pipermail/starlingx-discuss/2019-October/006621.html ? https://bugs.launchpad.net/starlingx/+bug/1852352 - new - AR: Greg/Abraham, please confirm steps needed in the docs and pass back to Kris. * Kris -- R3.0 - Target release in early Dec ? RC1 branch creation Nov 25 ? R3 Stories: http s://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 ? The community team is tracking top stories. These two submitted for the doc team -- https://drive.google.com/file/d/1dXFLc6f4d5MA2l7rRBMnfyk4X6wZ07wX ? Open: * Operations Guides (Config guides): https://storyboard.openstack.org/#!/story/2006289 // https://docs.google.com/document/d/1mu2rgLvaA_7HYoCwXEG51I_vdMA6S_KAyzTMgKRZT-Y/edit?usp=sharing o 1) Need to settle on a starting org of new content: https://review.opendev.org/#/c/693601/ ? Division of new content into sections: * Configuration * Administration - consolidate with user and rename "Operation Guides" * User Guides (whats the diff between Admin and User Guides?) o 2) Need to settle on which subset of the newly expanded content will be for R3: ? Items from original story? Other? o 3) Once 1 and 2 are decided, Kris will update/add stories/tasks in StoryBoard to reflect decisionsAR: KRIS to make a proposal for final set of R3 content - team to decide by EOD Tuesday, report to community ? - dist cloud - PRIORITY ? - gen updates ? - TSN ? - Backup/restore w/ containers (this would be Operation Guide) KRIS: add to list ? - stx in a box? Pending infrastructure o 4) Need to provide update on final target content for R3 to community mtg next week. * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) o Draft in review https://review.opendev.org/#/c/692202/ o Hosting qcow2 images: ? Kris sent initial contact to Scott re hosting on cengn. * From community mtg: o Build frequency: Update image post release, update at dot dot release o Retention policy? Dont need to store beyond that - b/c they are targeted. If they are once per release then maybe 1 or 1 + previous? o Continue convo off line (scott/saul) * Scott has asked: https://drive.google.com/open?id=1715IJtx1BmXQuR_Ffdjxs4S-Tk8-60MH o Is the qcow2 image to be created by the cengn build? I and cengn would prefer that to allowing binary uploads. * --> o Where are the instructions for it's creation? * --> * https://drive.google.com/open?id=1c2WzC3E_FnoJMfFwADFj1FWOn4Fx8jvW o How often do we need to build it? * --> o For what branches? * --> Release branch o What is the retention policy? * --> o How big are the files? * --> * Kris send answers by EOW * Expanded Ansible content: https://storyboard.openstack.org/#!/story/2006843 o in progress * Misc: o http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.html * This may impact all general install instructions (making sure versions align across all needed files/packages) o TSN contribution is in progress: (subtask 36405 in https://storyboard.openstack.org/#!/story/2006289) ? https://drive.google.com/file/d/1IQZVTEHRra72wNOHiIXD5Y-DKiFkl7yZ ? Le, Huifeng is working on this * R2.0.2 EOY - Will require release notes (no impact to R3) * Possible guide for deploying on packet.com? (AR: Greg will explore this - Abraham will help) ? https://wiki.openstack.org/wiki/StarlingX/Packet_SIG ? Explore this as content for a new guide * Greg -- Summary of DOC discussions @ STX PTG * DOC Process ... for 'new' content ? Need to work with PLs and COREs of STX Project Teams to enforce 'code contributors' to include doc updates in their commits ? with DOC Team providing 'editor' type role o PROPOSALS on how we do this ? * DOC Process ... for 'existing' content related to STX 3.0 DOC Work ? Approach PLs of STX Project Teams to get them to provide doc updates (with DOC Team providing 'editor' type role) o ( or minimally raw input for doc updates ) * DOC Team ? Would it be beneficial to provide packet.com resources to DOC Team in order to give them "hands on" access to StarlingX system ? * General Comments ? quick start links ? o need quick start link for first time visitor ... i.e. that goes directly to virtual AIO simplex installation o ? add a quick start video of installing and using starlingx ? o ? add a quick start link to a public packet.com starlingx deployment ? ? should starlingx intro pages under doc point to intro material under starlingx.io ? ? various workshop scripts brought up as having simple robust install procedures o general input I had was that we need to look at these scripts, and o understand how these are any different (if at all) than what we have doc'd in docs.starlingx.io o docs.starlingx.io should be the best source of simple robust install procedures. ? Yong mentioned that he thought virtualized environment setup needs to be enhanced to include the scenario that you are operating behind a firewall o need to followup with Yong Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 * -- -- * 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * Work in progress * We took one example, the compute personality/subfunction renamed to 'worker', we find several ocurrences for both of them. * 2019-10-02 -- Kris and Mary -- Update the contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html to reflect our current doc schema and incorporate elements of the "cheat sheet." (low priority) * 2019-11-13 -- Kris -- * Ping Dean to review: https://review.opendev.org/#/c/691740/ * Ready for editorial: https://review.opendev.org/#/c/689847/ * Make a proposal for final set of R3 content - team to decide by EOD Tuesday, report to community * Send answers to Scott re hosting image on cengn * 2019-11-13 -- Greg -- https://bugs.launchpad.net/starlingx/+bug/1852352 - please confirm steps needed in the docs and pass back to Kris. -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Nov 14 05:36:51 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 14 Nov 2019 05:36:51 +0000 Subject: [Starlingx-discuss] Alx driver In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608E6CEF@SHSMSX105.ccr.corp.intel.com> Hi Ting, ALX driver is not supported yet in StarlingX’s kernel. Please file a LP issue if you need it. Here is the LP link: https://bugs.launchpad.net/starlingx Best Regards Shuicheng From: Chiing-Ting Huang Sent: Wednesday, November 13, 2019 10:25 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Alx driver Dear StalingX team I think StarlingX R2.0 didn't module alx driver I can't get Qualcomm Atheros Ar8161 network interface Best Regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Thu Nov 14 09:06:44 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 14 Nov 2019 03:06:44 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$5thcs4@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191114T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Ghada.Khalil at windriver.com Thu Nov 14 13:39:17 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Nov 2019 13:39:17 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191113 In-Reply-To: References: Message-ID: <151EE31B9FCCA54397A757BC674650F0C15EEA9C@ALA-MBD.corp.ad.wrs.com> Hi Maria, Can you confirm if this sanity was using openstack train images? Thanks, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Wednesday, November 13, 2019 6:49 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191113 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-13 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - 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 - 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 ] BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Nov 14 14:48:39 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Nov 2019 14:48:39 +0000 Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! In-Reply-To: References: <1844546305.386.1573680726555.JavaMail.javamailuser@localhost> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAD2E@ALA-MBD.corp.ad.wrs.com> Thanks Austin. Looks like an update merged yesterday just before I kicked off this CENGN build which updated the requirements.txt of the starlingx-dashboard module, which in turn added this new dependency on python-cephclient. Once this update merges, I'll kick off a new build. -----Original Message----- From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, November 13, 2019 10:33 PM To: build.starlingx at gmail.com; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! Hi All: From log : http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs/jenkins-STX_build_docker_flock_images-138.log.html python-cephclient can not be found in upper-constraints.txt https://review.opendev.org/#/c/694192/ will fix this issue. Stx-horizon image can be built successfully w/ this patch in local env. Thanks. BR Austin Sun. -----Original Message----- From: build.starlingx at gmail.com Sent: Thursday, November 14, 2019 5:32 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [stable] [build-report] STX_build_docker_flock_images - Build # 138 - Failure! Project: STX_build_docker_flock_images Build #: 138 Status: Failure Timestamp: 20191113T185330Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20191113T154115Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root BASE_VERSION: master-stable-20191113T154115Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191113T154115Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: master PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/logs PUBLISH_TIMESTAMP: 20191113T154115Z FLOCK_VERSION: master-centos-stable-20191113T154115Z PREFIX: master TIMESTAMP: 20191113T154115Z BUILD_STREAM: stable REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20191113T154115Z/outputs REGISTRY: docker.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Don.Penney at windriver.com Thu Nov 14 14:58:38 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Nov 2019 14:58:38 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <93814834B4855241994F290E959305C7530F6EDA@SHSMSX104.ccr.corp.intel.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6EDA@SHSMSX104.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAD61@ALA-MBD.corp.ad.wrs.com> Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 12:30 To: Liu, ZhipengS ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' ; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Nov 14 15:09:02 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Nov 2019 15:09:02 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191113 References: Message-ID: <151EE31B9FCCA54397A757BC674650F0C15EEBD9@ALA-MBD.corp.ad.wrs.com> Based on the email thread with Don/Austin/Zhipeng, the sanity below was still using the stein docker images as the train build failed. Fixes are in progress and we expect to trigger another build shortly. From: Khalil, Ghada Sent: Thursday, November 14, 2019 8:39 AM To: 'Perez Ibarra, Maria G'; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191113 Hi Maria, Can you confirm if this sanity was using openstack train images? Thanks, Ghada From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra at intel.com] Sent: Wednesday, November 13, 2019 6:49 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191113 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-13 (link) Status: RED =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - Dedicated Storage (2+2+2) Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [BLOCKED] Sanity Platform 09 TCs [BLOCKED] TOTAL: [ 66 TCs ] =========================================== Sanity Test is executed in a Containers - 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 - 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 - 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 ] BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Nov 14 15:49:53 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 14 Nov 2019 15:49:53 +0000 Subject: [Starlingx-discuss] [TSC] No meeting was held today Message-ID: <91EF349D-F6B4-4C0A-A0C2-6E2FFDAE45F4@windriver.com> Hi all; With the summit/PTG last week we didn't have quorum on the call this morning. We will restart next week. One item that was raised in the PTG last week was to determine if there was community interest in a mid-cycle meet-up. Please let us know if there is interest in holding something like we did in February 2019. Regards; Ian From Don.Penney at windriver.com Thu Nov 14 16:05:59 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Nov 2019 16:05:59 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAD61@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6EDA@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BAD61@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAE3A@ALA-MBD.corp.ad.wrs.com> I hit a few additional issues trying to build stx-horizon and have posted reviews. Once these additional updates merge, I can kick off a build: https://review.opendev.org/#/q/projects:starlingx+branch:master+topic:fix-stx-horizon-build -----Original Message----- From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, November 14, 2019 9:59 AM To: Liu, ZhipengS; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 12:30 To: Liu, ZhipengS ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' ; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Thu Nov 14 16:48:57 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 14 Nov 2019 16:48:57 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C15EEDC0@ALA-MBD.corp.ad.wrs.com> I will not be able to chair the meeting today and Bruce is also not available, so I'll cancel. Please provide updates on the etherpad. Ada, I'm looking for a view of how test is going. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1860 bytes Desc: not available URL: From maria.g.perez.ibarra at intel.com Thu Nov 14 17:41:35 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 14 Nov 2019 17:41:35 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191114 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-14 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006955.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Thu Nov 14 19:23:17 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Thu, 14 Nov 2019 19:23:17 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 In-Reply-To: References: <151EE31B9FCCA54397A757BC674650F0C15ED9CC@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BED370F66@fmsmsx123.amr.corp.intel.com> <3DF080BB-CA87-4C98-989A-D3BC87DE9FE9@intel.com> <9A296723-316C-4D65-A82C-DEBDB670694A@windriver.com> <072358F2-62FB-4447-B63C-62B1968B5AE8@intel.com> Message-ID: <4F6FE2C9-B927-4B95-98C8-A734C7E7FAA3@windriver.com> Fix for this up for review: https://review.opendev.org/#/c/694355/. Regards, Bob From: "Sun, Austin" Date: Wednesday, November 13, 2019 at 2:54 AM To: "Lemus Contreras, Cristopher J" , Robert Church , "Qian, Bin" , "Jones, Bruce E" , "Khalil, Ghada" , "Perez Ibarra, Maria G" , "starlingx-discuss at lists.starlingx.io" , "Cabrales, Ada" Cc: "Eslimi, Dariush" Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Thanks a lot Cristopher. The commit fbc09b8db8a14fbf24976a0f7d8924af7a330f85 was merged two months ago. LP# 1851533 was reported since 11/05, and never reported before 11/05. I cannot understand this part. Thanks. BR Austin Sun. From: Lemus Contreras, Cristopher J Sent: Wednesday, November 13, 2019 10:37 AM To: Church, Robert ; Qian, Bin ; Jones, Bruce E ; Khalil, Ghada ; Sun, Austin ; Perez Ibarra, Maria G ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Austin, An update about the EB that you sent us (http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs), in summary: * A full sanity was executed for all configs once. All TC passed. * An Standard with external storage was installed 3 times (because this is where the issue appeared more times), tiller pod was running fine. * Port range is also like this: controller-0:~$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 If I understood, we had good luck the three times and tiller port was not in use. Please, let me know if you need additional details. Thanks & Regards Cristopher Lemus From: "Church, Robert" > Date: Tuesday, November 12, 2019 at 12:15 PM To: "Qian, Bin" >, "Lemus Contreras, Cristopher J" >, "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 I think this is commit: https://opendev.org/starlingx/config-files/commit/fbc09b8db8a14fbf24976a0f7d8924af7a330f85 Bob From: "Qian, Bin" > Date: Tuesday, November 12, 2019 at 12:12 PM To: "Lemus Contreras, Cristopher J" >, "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Thanks Cristopher, I found the same on latest build as well. I further look into the sys config, I found that recently the config-files/initscripts-config/files/sysctl.conf was altered, and the following was removed. # Limit local port range net.ipv4.ip_local_port_range = 49216 61000 net.ipv4.tcp_tw_reuse = 1 The file is deployed to /etc/sysctl.conf, the setting is the range of local port. Probably some changes that messed up? Thanks, Bin ________________________________ From: Lemus Contreras, Cristopher J [cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, November 12, 2019 9:56 AM To: Qian, Bin; Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi Bin, I checked on the configs that failed with today’s build (BUILD_ID="20191112T000000Z"), and I got this output on both: [sysadmin at controller-0 ~(keystone_admin)]$ cat /proc/sys/net/ipv4/ip_local_port_range 32768 60999 Which I think, causes the conflict with port 44134. With this build, the two configs that failed are Standard with Dedicated Storage (2+2+2), virtual and baremetal environments. Please, let me know if you need further details. Thanks & Regards Cristopher Lemus From: "Qian, Bin" > Date: Tuesday, November 12, 2019 at 11:38 AM To: "Jones, Bruce E" >, "Khalil, Ghada" >, "Sun, Austin" >, "Perez Ibarra, Maria G" >, "starlingx-discuss at lists.starlingx.io" >, "Cabrales, Ada" > Cc: "Eslimi, Dariush" > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 While the lab is still being installed, I check the collected logs. From system inventory's point of view, all nodes provisioned successfully. The impact of my commits ends after controller-0 being provisioned (unlocked successfully the 1s time). As Bob brought up in the comment, the port 44134 was taken by other process (as client port). it could be the rage setting of ephemeral port incorrect. I check a couple of our existing lab, I got: cat /proc/sys/net/ipv4/ip_local_port_range 49216 61000 which excludes target port 44134 from being randomly assigned as client port. I think it might be a good start that someone have access to the labs that failed the sanity to check the same settings? Thanks, Bin ________________________________ From: Qian, Bin [Bin.Qian at windriver.com] Sent: Tuesday, November 12, 2019 8:26 AM To: Jones, Bruce E; Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Cc: Eslimi, Dariush Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 The 2 commits are inter related, taking one out will fail. I am trying to reproduce the issue. Not sure what exactly causes the issue yet. The commits work no difference on virtual or baremetal. Bin ________________________________ From: Jones, Bruce E [bruce.e.jones at intel.com] Sent: Tuesday, November 12, 2019 7:54 AM To: Khalil, Ghada; Sun, Austin; Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Qian, Bin Cc: Eslimi, Dariush Subject: RE: [Starlingx-discuss] Sanity Test - ISO 20191111 Is it possible to bisect the two suspicious commits, or otherwise figure out which parts of the commits are the root cause? brucej From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Tuesday, November 12, 2019 7:26 AM To: Sun, Austin >; Perez Ibarra, Maria G >; starlingx-discuss at lists.starlingx.io; Cabrales, Ada >; Qian, Bin > Cc: Eslimi, Dariush > Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Adding Bin explicitly to the email thread From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, November 12, 2019 4:02 AM To: Perez Ibarra, Maria G; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] Sanity Test - ISO 20191111 Hi All: About this https://bugs.launchpad.net/starlingx/+bug/1851533, after triage , this issue should be caused by https://review.opendev.org/#/c/691714/ and https://review.opendev.org/#/c/692439 after revert this commit , AIO on virtual environment can be deployed successfully @Cabrales, Ada and Maria : would you like to verify this by EB which reverts 691714/692439 ? EB is available on http://dcp-dev.intel.com/pub/starlingx/stx-eng-build/314/outputs This change 691714 will cause https://bugs.launchpad.net/starlingx/+bug/1852155 issue too. @Qianbin : would you double check these two issues caused by 691714/692439 gerrit ? Thanks. BR Austin Sun. From: Perez Ibarra, Maria G > Sent: Tuesday, November 12, 2019 1:17 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Sanity Test - ISO 20191111 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-11 (link) Status: RED =========================================== Sanity Test is executed in a Containers – Bare Metal Environment AIO – Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [BLOCKED] Sanity Platform 07 TCs [BLOCKED] 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 - 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 is executed in a Containers – 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006894.html BUG platform-integ-apps apply failed - tiller on Crash https://bugs.launchpad.net/starlingx/+bug/1851533 regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Nov 14 19:56:42 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Nov 2019 19:56:42 +0000 Subject: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAE3A@ALA-MBD.corp.ad.wrs.com> References: <434bdab0-fd74-26a4-571a-bc4e9dad6a9e@intel.com> <93814834B4855241994F290E959305C7530F61C3@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA59B@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6C29@SHSMSX104.ccr.corp.intel.com> <93814834B4855241994F290E959305C7530F6CB1@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BA72E@ALA-MBD.corp.ad.wrs.com> <93814834B4855241994F290E959305C7530F6EDA@SHSMSX104.ccr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BAD61@ALA-MBD.corp.ad.wrs.com> <6703202FD9FDFF4A8DA9ACF104AE129FC15BAE3A@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BAFE3@ALA-MBD.corp.ad.wrs.com> The updates have all merged, so I've launched a new build with images. -----Original Message----- From: Penney, Don Sent: Thursday, November 14, 2019 11:06 AM To: Penney, Don; Liu, ZhipengS; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I hit a few additional issues trying to build stx-horizon and have posted reviews. Once these additional updates merge, I can kick off a build: https://review.opendev.org/#/q/projects:starlingx+branch:master+topic:fix-stx-horizon-build -----Original Message----- From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, November 14, 2019 9:59 AM To: Liu, ZhipengS; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Thanks Zhipeng. Once your update is merged, along with Austin's, I'll kick off a new build. The image build failed yesterday because of new dependencies that were added to a module less than an hour before I kicked off the build, unfortunately. Bad timing! -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Wednesday, November 13, 2019 10:44 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, I have submitted another patch for the issue of communication between horizon and cinderclient. This is a known issue during my upgrade work(In my test image, it was downgraded to 4.3.0). However, upstream still not fix it by now. https://review.opendev.org/#/c/694193/ Fix bug of communication between Horizon and cinderclient. We have to downgrade python-cinderclient from 5.0.0(specified inupper-constraints) to 4.3.0. Otherwise, we will meet some error during operating in horizon gui. Related upstream bug and patch list as below. FYI. https://review.opendev.org/#/c/643405/ https://bugs.launchpad.net/horizon/+bug/1815635 https://review.opendev.org/#/c/675891/ BTW, Austin fixed another build issue that we have not met before during building image. Attached his email for detail. We still not sure why it can pass build before? Any idea? Have you met this issue during your own build for horizon? Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 12:30 To: Liu, ZhipengS ; Hu, Yong ; 'starlingx-discuss at lists.starlingx.io' ; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. I updated my review with a couple more python modules, and the wheels and images are now building fine for me: https://review.opendev.org/693949 -----Original Message----- From: Penney, Don Sent: Tuesday, November 12, 2019 10:49 PM To: 'Liu, ZhipengS'; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. 1. Given the misconfiguration in stable-wheels.cfg, your last patchset to https://review.opendev.org/688105 would fail to build the tarball. Perhaps you made an update after the last time you successfully built the wheels tarball and forgot to rebuild? 2. A failure to build images that is overcome with a manual tweak in your workspace is still a failure to build. Anyone without your workaround, like CENGN, would hit this failure. We cannot launch a CENGN image build until I work through all the build issues, which I'm working on - I've got most of the images building, but still have a couple of failures that I should soon have resolved. -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Tuesday, November 12, 2019 10:18 PM To: Penney, Don; Hu, Yong; 'starlingx-discuss at lists.starlingx.io'; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, From your patch, we learnt that we just need to change the entry in stable-wheels.cfg instread of our workaround. Change pypi to tar in the second section of this line. pyrsistent-0.15.4-cp27-cp27mu-linux_x86_64.whl|tar|https://files.pythonhosted.org/packages/b9/66/b2638d96a2d128b168d0dba60fdc77b7800a9b4a5340cefcc5fc4eae6295/pyrsistent-0.15.4.tar.gz|pyrsistent-0.15.4 Thanks! Zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2019年11月13日 10:09 To: Penney, Don ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Don, Yes, I built wheels, as you can see in my patch https://review.opendev.org/#/c/688105/ I have changed stable-wheels.cfg when I debug neutron pod. When I was doing integration test with train, upstream was also doing integration test as I can see the upper-constraints.txt was changing day by day. BTW, we met the same issue you had. ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/whee ls/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.tx t (line 566)) We have a WR below as pip can only find tar , no .whl can be found for pyrsistent. ================================================================ /home/wrsroot/starlingx/workspace/localdisk/loadbuild/wrsroot/starlingx/std/build-images/loci/scripts/pip_install.sh #!/bin/bash set -ex packages=$@ #pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS}${packages} pip install --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ pyrsistent pip install --no-cache-dir --only-binary :all: --no-compile -c /tmp/wheels/upper-constraints.txt --find-links /tmp/wheels/ ${PIP_ARGS} ${packages} ====================================================================== Thanks! Zhipeng -----Original Message----- From: Penney, Don Sent: 2019年11月13日 5:54 To: Liu, ZhipengS ; Hu, Yong ; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Lemus Contreras, Cristopher J Subject: RE: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Did you build wheels and docker images as part of testing? In addition to the wheel tarball build failure I hit earlier this afternoon (see email: " wheel tarball build broken by train upgrade - review needed in stx/root"), I decided to try building stx-ironic (an arbitrary choice), and hit a failure: ERROR: Could not find a version that satisfies the requirement pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) (from versions: none) ERROR: No matching distribution found for pyrsistent===0.15.4 (from -c /tmp/wheels/upper-constraints.txt (line 566)) -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: Thursday, November 07, 2019 8:55 PM To: Hu, Yong; starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos; Lemus Contreras, Cristopher J Subject: Re: [Starlingx-discuss] [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi all, So far I have not got new more comments. I'd like to push this 6 patches get merged soon since fully sanity test pass! Could core reviewers final check them before adding review+2 for below 3 patches. https://review.opendev.org/#/c/683886/ starlingx/openstack-armada-app https://review.opendev.org/#/c/684166/ starlingx/openstack-armada-app https://review.opendev.org/#/c/688105/ starlingx/root Thanks! Zhipeng -----Original Message----- From: Hu, Yong Sent: 2019年11月5日 22:47 To: starlingx-discuss at lists.starlingx.io; Alonso, Juan Carlos ; Liu, ZhipengS ; Lemus Contreras, Cristopher J Subject: [Stx.distro.openstack] Call for review on OpenStack Train Upgrade Patches. Hi Core reviewers in Stx.distro.openstack: The EB with containerized Train OpenStack services has *passed* the sanity, based on test results from testing team. (Thanks to @JC and @Chirstopher). So to unblock stx.3.0 MS-3, please review the following patches in time: https://review.opendev.org/#/c/683886/ https://review.opendev.org/#/c/683910/ https://review.opendev.org/#/c/684166/ https://review.opendev.org/#/c/687441/ https://review.opendev.org/#/c/687197/ https://review.opendev.org/#/c/688105/ In addition, some background info related to this upgrade: 1). Originally there was a test failure in the sanity, but later Zhipeng found the cause was from an non-standard test (cirros) image which had 2 QCOW2 headers unexpectedly and failed during the conversion from QCOW2 to RAW format. Why wasn't this issue seen with OpenStack Stein? Because the QCOW2 to RAW conversion wasn't enabled in Nova of Stein, but it is now enabled by default in Train. Recommendation: later for the testing, we advise to use this cirros image: https://download.cirros-cloud.net/0.4.0/cirros-0.4.0-x86_64-disk.img, or other QCOW2 image which we assure it is with correct header. 2). these patches have to be merged *in one batch* due to the inter-dependencies. 3). after these patches are merged, need *stx.build team* to generate new docker images for Openstack Train services and *upload them to Docker Hub*. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Thu Nov 14 23:53:25 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 14 Nov 2019 23:53:25 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 11/14/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 218 Fail = 6 Blocked = 8 Not Run = 40 Obsolete = 2 Deferred = 0 Total executed = 224 Pass Rate = 97% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 154 Fail = 9 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 163 Pass Rate = 94% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 14 Fail = 2 Blocked = 0 Not Run = 451 Obsolete = 0 Deferred = 0 Total executed = 16 Pass Rate = 87% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 15 01:49:02 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 15 Nov 2019 01:49:02 +0000 Subject: [Starlingx-discuss] Train images available Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BB0C0@ALA-MBD.corp.ad.wrs.com> The build this afternoon was successful, including the updated train docker images: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20191114T195617Z/outputs/ Cheers, Don. Don Penney, Developer, Wind River -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 15 14:16:45 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 15 Nov 2019 14:16:45 +0000 Subject: [Starlingx-discuss] RC2.0 - Change install device Message-ID: Hi, how can i change the install device. My storage-node have some disks, but /dev/sda should not be my primary boot device. I want to install stx stuff at /dev/sdk, how can I change the destination install device for some hosts ? greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Nov 15 14:30:02 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 15 Nov 2019 14:30:02 +0000 Subject: [Starlingx-discuss] RC2.0 - Change install device In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BB1DC@ALA-MBD.corp.ad.wrs.com> For nodes installing after the initial controller configuration, there are installation parameters for the host you can set, boot_device and rootfs_device. For example, from the CLI: system host-update 3 \ boot_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 \ rootfs_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 This can also be done via browser, by editing the host. For initial installation of controller-0 from ISO, you can edit the boot cmdline by hitting tab on your selection, and modify these parameters. In stx-3.0, we've introduced a utility called update-iso.sh that you can use to create a modified copy of the installation ISO with modified boot parameters: https://opendev.org/starlingx/utilities/src/branch/master/utilities/platform-util/scripts/update-iso.sh Example: update-iso.sh -i bootimage.iso -o updated-bootimage.iso \ -p boot_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 \ -p rootfs_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 Hope this helps! From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Friday, November 15, 2019 9:17 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] RC2.0 - Change install device Hi, how can i change the install device. My storage-node have some disks, but /dev/sda should not be my primary boot device. I want to install stx stuff at /dev/sdk, how can I change the destination install device for some hosts ? greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 15 15:39:58 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 15 Nov 2019 15:39:58 +0000 Subject: [Starlingx-discuss] RC2.0 - Change install device In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FC15BB1DC@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FC15BB1DC@ALA-MBD.corp.ad.wrs.com> Message-ID: Thats fine! Cool, thx!!!! Von: Penney, Don [mailto:Don.Penney at windriver.com] Gesendet: Freitag, 15. November 2019 15:30 An: von Hoesslin, Volker; 'starlingx-discuss at lists.starlingx.io' Betreff: Re: [Starlingx-discuss] RC2.0 - Change install device For nodes installing after the initial controller configuration, there are installation parameters for the host you can set, boot_device and rootfs_device. For example, from the CLI: system host-update 3 \ boot_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 \ rootfs_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 This can also be done via browser, by editing the host. For initial installation of controller-0 from ISO, you can edit the boot cmdline by hitting tab on your selection, and modify these parameters. In stx-3.0, we've introduced a utility called update-iso.sh that you can use to create a modified copy of the installation ISO with modified boot parameters: https://opendev.org/starlingx/utilities/src/branch/master/utilities/platform-util/scripts/update-iso.sh Example: update-iso.sh -i bootimage.iso -o updated-bootimage.iso \ -p boot_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 \ -p rootfs_device=/dev/disk/by-path/pci-0000:00:0d.0-ata-1.0 Hope this helps! From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Friday, November 15, 2019 9:17 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] RC2.0 - Change install device Hi, how can i change the install device. My storage-node have some disks, but /dev/sda should not be my primary boot device. I want to install stx stuff at /dev/sdk, how can I change the destination install device for some hosts ? greez & thx, Volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From John.Kung at windriver.com Fri Nov 15 17:03:12 2019 From: John.Kung at windriver.com (Kung, John) Date: Fri, 15 Nov 2019 17:03:12 +0000 Subject: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Message-ID: System Monitor - Cluster and Infrastructure Monitoring Deployment Story: https://storyboard.openstack.org/#!/story/2005733 The Infrastructure and Cluster Monitor in stx3.0 allows for the deployment of a monitoring solution for the infrastructure and Kubernetes cluster and its services. The following describes the deployment of stx-monitor. Steps to Deploy stx-monitor: * Obtain the stx-monitor application (e.g. stx-monitor-1.0-1.tgz) stx-monitor may be obtained from the CENGN mirror: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/helm-charts/ Alternatively, the stx-monitor application may be built from source: $MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh --verbose --app stx-monitor * Upload stx-monitor $ system application-upload stx-monitor-1.0-1.tgz * Assign host labels for stx-monitor $ system host-label-assign controller-0 elastic-data=enabled elastic-controller=enabled elastic-client=enabled elastic-master=enabled $ system host-label-assign controller-1 elastic-data=enabled elastic-controller=enabled elastic-client=enabled elastic-master=enabled If there are worker hosts provisioned, one worker host must have the following label assigned: e.g. $ system host-label-assign compute-0 elastic-master=enabled * Update helm-overrides, if required There are default pod resource limits (e.g. cpu, memory, storage) for the pods that may be tuned via helm-overrides for your deployment scenario. Optionally, the stx-monitor may also be configured via helm-overrides for sending to an external elasticsearch cluster. In such case, please refer to and execute the steps at "NOTE: External Elastic Server Case" before continuing to the next step of apply stx-monitor. * Apply stx-monitor $ system application-apply stx-monitor * Refer to Elastic documentation (references below) for usage guidelines e.g. Elastic Kibana interface may be accessible by pointing a web browser at: :31001 * NOTE: External Elastic Server Case For sending to an external Elastic server. Note that the external Elasticsearch cluster must be up and reachable. * Set a unique system name for this cluster $ system modify --name < system-name > * Setup helm-overrides for the services to access external server IP which is running the Elastic cluster. * Refer to the auth and ssl options for setting up logstash for sending to a secure authenticated Elasticsearch cluster: https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticsearch.html # The external server IP is the external elastic cluster reachable from this server's OAM or management network. # The following parameters should be set according to the server running Elasticsearch: ES_CLIENT_IP_ADDR= ES_CLIENT_PATH=mon-elasticsearch-client ES_CLIENT_PORT=31001 cat < ./logstash.yml elasticsearch: host: http://$ES_CLIENT_IP_ADDR port: $ES_CLIENT_PORT config: elasticsearch.path: "/$ES_CLIENT_PATH" EOF cat < ./filebeat.yml config: output.elasticsearch: hosts: - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" setup.dashboards: enabled: false EOF cat < ./metricbeat.yml daemonset: config: output.elasticsearch: hosts: - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" setup.dashboards: enabled: false deployment: config: output.elasticsearch: hosts: - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" setup.dashboards: enabled: false EOF Use the above generated files to set the overrides for metricbeat, filebeat, and logstash, using the following commands: $ system helm-override-update stx-monitor metricbeat monitor --values ./metricbeat.yml --reuse-values $ system helm-override-update stx-monitor filebeat monitor --values ./filebeat.yml --reuse-values $ system helm-override-update stx-monitor logstash monitor --values ./logstash.yml --reuse-values * Disable appropriate charts, as these components will be running external elastic database server: $ system helm-chart-attribute-modify stx-monitor elasticsearch-client monitor --enabled false $ system helm-chart-attribute-modify stx-monitor elasticsearch-data monitor --enabled false $ system helm-chart-attribute-modify stx-monitor elasticsearch-master monitor --enabled false $ system helm-chart-attribute-modify stx-monitor elasticsearch-curator monitor --enabled false $ system helm-chart-attribute-modify stx-monitor kibana monitor --enabled false $ system helm-chart-attribute-modify stx-monitor nginx-ingress monitor --enabled false * References: Spec: https://docs.starlingx.io/specs/specs/stx-3.0/approved/stx-monitor_2005733_infrastructure_and_cluster_monitoring.html References: * Elasticsearch documentation https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html * Elasticsearch-curator: https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html * FileBeat https://www.elastic.co/guide/en/beats/filebeat/current/index.html * MetricBeat https://www.elastic.co/guide/en/beats/metricbeat/current/index.html * Kibana https://www.elastic.co/guide/en/kibana/current/index.html * Logstash https://www.elastic.co/guide/en/logstash/current/index.html * Logstash https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticsearch.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Nov 15 18:11:36 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 15 Nov 2019 12:11:36 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$716u2u@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191115T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From maria.g.perez.ibarra at intel.com Fri Nov 15 20:41:14 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 15 Nov 2019 20:41:14 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191115 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-15 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006972.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Nov 15 22:49:11 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 15 Nov 2019 14:49:11 -0800 Subject: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring In-Reply-To: References: Message-ID: <8152db41-bb7d-f3bb-ace6-bc1682efc1cb@linux.intel.com> Hi John, If this is intended to be a documentation submission, you should really re-work this into RST and submit it to the starlingx/docs repo. It should contain the content and descriptions of what the service is intended to be and how to use it. This is what was discussed at the PTG in Shanghai a week ago. Thanks Sau! On 11/15/19 9:03 AM, Kung, John wrote: > *System Monitor - Cluster and Infrastructure Monitoring Deployment* > > ** > > *Story: *https://storyboard.openstack.org/#!/story/2005733 > > The Infrastructure and Cluster Monitor in stx3.0 allows for the > deployment of a monitoring solution for the infrastructure and > Kubernetes cluster and its services. > > The following describes the deployment of stx-monitor. > > *_Steps to Deploy stx-monitor_**:* > > * *Obtain the stx-monitor application (e.g. stx-monitor-1.0-1.tgz) * > > ** > > *stx-monitor  may be obtained from the CENGN  mirror:* > > *http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_green_build/outputs/helm-charts/* > > * > Alternatively, the stx-monitor application may be built from source:* > > $MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh  --verbose > --app stx-monitor > > * *Upload stx-monitor* > > *$ system application-upload *stx-monitor-1.0-1.tgz > > * *Assign host labels for stx-monitor* > > $ *system host-label-assign *controller-0 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled elastic-master=enabled > > $ *system host-label-assign* controller-1 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled  elastic-master=enabled > > If there are worker hosts provisioned, one worker host must have the > following label assigned: > > e.g.   $ *system host-label-assign* compute-0 elastic-master=enabled > > * *Update helm-overrides, if required* > > There are default pod resource limits (e.g. cpu, memory, storage) for > the pods that may be tuned via helm-overrides for your deployment scenario. > > Optionally, the stx-monitor may also be configured via helm-overrides > for sending to an external elasticsearch cluster. In such case, please > refer to and execute the steps at  “*NOTE: External Elastic Server Case” > before continuing to the next step of apply stx-monitor.* > > * *Apply stx-monitor* > > *$ system application-apply stx-monitor* > > * *Refer to Elastic documentation (references below) for usage guidelines* > > *e.g. Elastic Kibana interface may be accessible by pointing a web > browser at:* > > :31001 > > * *_NOTE: External Elastic Server Case_*__ > > *For sending to an external Elastic server.  Note that the external > Elasticsearch cluster must be* > > *up and reachable.* > > o *Set a unique system name for this cluster* > > *$ system modify --name < system-name >* > > ·*Setup helm-overrides for the services to access external server IP > which is running the Elastic cluster.* > > ·Refer to the auth and ssl options for setting up logstash for sending > to a secure authenticated Elasticsearch cluster: > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticsearch.html > > >                           # The external server IP is the external > elastic cluster reachable from this server’s OAM or management network. > >                           # The following parameters should be set > according to the server running Elasticsearch: > >                              ES_CLIENT_IP_ADDR= > >                              ES_CLIENT_PATH=mon-elasticsearch-client > >                              ES_CLIENT_PORT=31001 > > cat <  ./logstash.yml > > elasticsearch: > >   host: http://$ES_CLIENT_IP_ADDR > >   port: $ES_CLIENT_PORT > > config: > >   elasticsearch.path: "/$ES_CLIENT_PATH" > > EOF > > cat <  ./filebeat.yml > > config: > >   output.elasticsearch: > >     hosts: > >     - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >   setup.dashboards: > >     enabled: false > > EOF > > cat < ./metricbeat.yml > > daemonset: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > deployment: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > EOF > > *Use the above generated files to set the overrides for metricbeat, > filebeat, and logstash,* > > *using the following commands:* > > *$ system helm-override-update stx-monitor metricbeat monitor  --values > ./metricbeat.yml  --reuse-values* > > *$ system helm-override-update stx-monitor filebeat monitor --values > ./filebeat.yml --reuse-values* > > *$ system helm-override-update stx-monitor logstash monitor --values > ./logstash.yml  --reuse-values* > > ·* Disable appropriate charts, as these components will be running > external elastic database server: * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**client monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor elasticsearch**-**data > monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**master monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**curator monitor --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor kibana monitor > --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor nginx-ingress monitor > --enabled false* > > * *References**:* > > *Spec: > *https://docs.starlingx.io/specs/specs/stx-3.0/approved/stx-monitor_2005733_infrastructure_and_cluster_monitoring.html > > *References:* > > ** Elasticsearch documentation > *https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html > > ** Elasticsearch-curator: > *https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html > > > * FileBeat https://www.elastic.co/guide/en/beats/filebeat/current/index.html > > * MetricBeat > https://www.elastic.co/guide/en/beats/metricbeat/current/index.html > > * Kibana https://www.elastic.co/guide/en/kibana/current/index.html > > * Logstash https://www.elastic.co/guide/en/logstash/current/index.html > > * Logstash > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticsearch.html > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Volker.Hoesslin at swsn.de Sat Nov 16 20:04:48 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Sat, 16 Nov 2019 20:04:48 +0000 Subject: [Starlingx-discuss] Issues Message-ID: So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :( 2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ? greez & thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sun Nov 17 09:01:45 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sun, 17 Nov 2019 03:01:45 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$5qo3sr@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191117T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From yong.hu at intel.com Mon Nov 18 01:18:36 2019 From: yong.hu at intel.com (Yong Hu) Date: Mon, 18 Nov 2019 09:18:36 +0800 Subject: [Starlingx-discuss] meeting agenda for stx.distro.openstack project - WW47 Message-ID: Hi folks, Here is the agenda for the project meeting on Tuesday (10:00 PM China time, and 6:00 AM US PST). Welcome join us. Agenda (details in Etherpad): 1. Stx.3.0: 1). Openstack Train upgrade status and review - Zhipeng 2). Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Totally we are having 3 HIGH and 11 medium issues - need show progress. 2. Stx.4.0 planning: 1). Openstack Ussuri upgrade from Train: - Upgrade containerized services - owner: 99Cloud team - containerize OpenStack clients and upgrade them - Owner: Intel team - Upgrade horizon, keystone and barbican on Stx platfrom - Owner: TBD - OpenStack live upgrade by K8S - Owner: TBD 3. Misc: 1). patch back-port on Nova from train to stein for CVE fix - Shuicheng. 2). other topics? 4. Opens Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings From cristopher.j.lemus.contreras at intel.com Mon Nov 18 09:04:44 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Mon, 18 Nov 2019 03:04:44 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191118T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Dariush.Eslimi at windriver.com Mon Nov 18 14:07:51 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 18 Nov 2019 14:07:51 +0000 Subject: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring In-Reply-To: <8152db41-bb7d-f3bb-ace6-bc1682efc1cb@linux.intel.com> References: <8152db41-bb7d-f3bb-ace6-bc1682efc1cb@linux.intel.com> Message-ID: Hi Saul, I do not believe this Is part of new approved development process yet. I understand that you have discussed it, but this is not part of current release/development process for STX-3.0. Thanks, Dariush -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: November-15-19 5:49 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Hi John, If this is intended to be a documentation submission, you should really re-work this into RST and submit it to the starlingx/docs repo. It should contain the content and descriptions of what the service is intended to be and how to use it. This is what was discussed at the PTG in Shanghai a week ago. Thanks Sau! On 11/15/19 9:03 AM, Kung, John wrote: > *System Monitor - Cluster and Infrastructure Monitoring Deployment* > > ** > > *Story: *https://storyboard.openstack.org/#!/story/2005733 > > The Infrastructure and Cluster Monitor in stx3.0 allows for the > deployment of a monitoring solution for the infrastructure and > Kubernetes cluster and its services. > > The following describes the deployment of stx-monitor. > > *_Steps to Deploy stx-monitor_**:* > > * *Obtain the stx-monitor application (e.g. stx-monitor-1.0-1.tgz) * > > ** > > *stx-monitor  may be obtained from the CENGN  mirror:* > > *http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/lates > t_green_build/outputs/helm-charts/* > > * > Alternatively, the stx-monitor application may be built from source:* > > $MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh  > --verbose --app stx-monitor > > * *Upload stx-monitor* > > *$ system application-upload *stx-monitor-1.0-1.tgz > > * *Assign host labels for stx-monitor* > > $ *system host-label-assign *controller-0 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled > elastic-master=enabled > > $ *system host-label-assign* controller-1 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled  > elastic-master=enabled > > If there are worker hosts provisioned, one worker host must have the > following label assigned: > > e.g.   $ *system host-label-assign* compute-0 elastic-master=enabled > > * *Update helm-overrides, if required* > > There are default pod resource limits (e.g. cpu, memory, storage) for > the pods that may be tuned via helm-overrides for your deployment scenario. > > Optionally, the stx-monitor may also be configured via helm-overrides > for sending to an external elasticsearch cluster. In such case, please > refer to and execute the steps at  “*NOTE: External Elastic Server Case” > before continuing to the next step of apply stx-monitor.* > > * *Apply stx-monitor* > > *$ system application-apply stx-monitor* > > * *Refer to Elastic documentation (references below) for usage > guidelines* > > *e.g. Elastic Kibana interface may be accessible by pointing a web > browser at:* > > :31001 > > * *_NOTE: External Elastic Server Case_*__ > > *For sending to an external Elastic server.  Note that the external > Elasticsearch cluster must be* > > *up and reachable.* > > o *Set a unique system name for this cluster* > > *$ system modify --name < system-name >* > > ·*Setup helm-overrides for the services to access external server IP > which is running the Elastic cluster.* > > ·Refer to the auth and ssl options for setting up logstash for sending > to a secure authenticated Elasticsearch cluster: > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > >                           # The external server IP is the external > elastic cluster reachable from this server’s OAM or management network. > >                           # The following parameters should be set > according to the server running Elasticsearch: > >                              ES_CLIENT_IP_ADDR= > >                              ES_CLIENT_PATH=mon-elasticsearch-client > >                              ES_CLIENT_PORT=31001 > > cat <  ./logstash.yml > > elasticsearch: > >   host: http://$ES_CLIENT_IP_ADDR > >   port: $ES_CLIENT_PORT > > config: > >   elasticsearch.path: "/$ES_CLIENT_PATH" > > EOF > > cat <  ./filebeat.yml > > config: > >   output.elasticsearch: > >     hosts: > >     - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >   setup.dashboards: > >     enabled: false > > EOF > > cat < ./metricbeat.yml > > daemonset: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > deployment: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > EOF > > *Use the above generated files to set the overrides for metricbeat, > filebeat, and logstash,* > > *using the following commands:* > > *$ system helm-override-update stx-monitor metricbeat monitor  > --values ./metricbeat.yml  --reuse-values* > > *$ system helm-override-update stx-monitor filebeat monitor --values > ./filebeat.yml --reuse-values* > > *$ system helm-override-update stx-monitor logstash monitor --values > ./logstash.yml  --reuse-values* > > ·* Disable appropriate charts, as these components will be running > external elastic database server: * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**client monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**data monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**master monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**curator monitor --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor kibana monitor > --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor nginx-ingress > monitor --enabled false* > > * *References**:* > > *Spec: > *https://docs.starlingx.io/specs/specs/stx-3.0/approved/stx-monitor_20 > 05733_infrastructure_and_cluster_monitoring.html > > *References:* > > ** Elasticsearch documentation > *https://www.elastic.co/guide/en/elasticsearch/reference/current/index > .html > > ** Elasticsearch-curator: > *https://www.elastic.co/guide/en/elasticsearch/client/curator/current/ > index.html > > > * FileBeat > https://www.elastic.co/guide/en/beats/filebeat/current/index.html > > * MetricBeat > https://www.elastic.co/guide/en/beats/metricbeat/current/index.html > > * Kibana https://www.elastic.co/guide/en/kibana/current/index.html > > * Logstash https://www.elastic.co/guide/en/logstash/current/index.html > > * Logstash > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Mon Nov 18 17:12:44 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 18 Nov 2019 17:12:44 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Nov 14/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F185B@ALA-MBD.corp.ad.wrs.com> ** There was no meeting on Nov 14. However, offline comments were added to the etherpad. Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - November 14 2019 ** Meeting is cancelled. Request for offline updates are per below ** stx.3.0 - Feature Status - https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Upversion to train - Still working thru docker image issues >> Addressed as of Nov 15 - Wait until official sanity with train is done to declare Milestone-3 - Distributed Cloud - Testing is complete - Fault Containerization - Ada to confirm that the re-test is done - Ada: Testing is complete, will investigate extra task https requested by Yang - Intel GPU support for K8s - Feature is done. Ran working on one enhancement that is not considered gating. - Cindy/Frank to ask developer to send doc info - Ada to provide an update on the re-test as discussed - Ada: This feature is going to be retested along with Train upgrade testing - Intel QAT support for K8s - Feature is done. - Cindy/Frank to ask developer to send doc into - Ada to provide an update on the re-test as discussed - Ada: This feature is going to be retested along with Train upgrade testing - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 49% (up from 44%) - Ada to update with status, completion date, any risks, etc - Since we are waiting for the Train ISO. we are going to execute all the TC planned in : https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1691167242 - This testing includes 100 Pytest TC + 100 Robot TC + 75 Test cases from feature testing (manual execution), and will try to cover fixed bugs. Goal , to be completed on 11/29 - Once that we got the RC ISO we are going to start with a new Test Plan that Elio and Yang will provide + Remaining TC from first cycle that weren't executed. To be compeleted on 12/13 - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 100% (up from 85%) From Ghada.Khalil at windriver.com Tue Nov 19 01:28:18 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 19 Nov 2019 01:28:18 +0000 Subject: [Starlingx-discuss] stx.3.0 milestone-3 declared Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F1AEC@ALA-MBD.corp.ad.wrs.com> Hello all, This is to let you know that stx.3.0 milestone-3 has been declared as of Friday Nov 15, 2019. Code for all features have been merged and the feature testing is complete (with an exception for re-running a subset of test-cases for GPU and QAT k8s plugin support). Containerized Openstack has been rebased to train and a Green sanity was achieved on Nov 15: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006973.html Feature Status: https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 Feature Testing Status: https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 Regards, Ghada & the release team From bruce.e.jones at intel.com Tue Nov 19 02:11:31 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 19 Nov 2019 02:11:31 +0000 Subject: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring In-Reply-To: References: <8152db41-bb7d-f3bb-ace6-bc1682efc1cb@linux.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BED3766BF@fmsmsx123.amr.corp.intel.com> Good documentation is very important to our project, and the Docs team is small and cannot create all of the content. We need the community to pitch in and help. We have to make a culture change and get into the mode of developers submitting Doc updates along with code submissions. I'd be happy to give a tutorial on the doc process and file format next week at the community meeting, or any time needed. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Monday, November 18, 2019 6:08 AM To: Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Hi Saul, I do not believe this Is part of new approved development process yet. I understand that you have discussed it, but this is not part of current release/development process for STX-3.0. Thanks, Dariush -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: November-15-19 5:49 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Hi John, If this is intended to be a documentation submission, you should really re-work this into RST and submit it to the starlingx/docs repo. It should contain the content and descriptions of what the service is intended to be and how to use it. This is what was discussed at the PTG in Shanghai a week ago. Thanks Sau! On 11/15/19 9:03 AM, Kung, John wrote: > *System Monitor - Cluster and Infrastructure Monitoring Deployment* > > ** > > *Story: *https://storyboard.openstack.org/#!/story/2005733 > > The Infrastructure and Cluster Monitor in stx3.0 allows for the > deployment of a monitoring solution for the infrastructure and > Kubernetes cluster and its services. > > The following describes the deployment of stx-monitor. > > *_Steps to Deploy stx-monitor_**:* > > * *Obtain the stx-monitor application (e.g. stx-monitor-1.0-1.tgz) * > > ** > > *stx-monitor  may be obtained from the CENGN  mirror:* > > *http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/lates > t_green_build/outputs/helm-charts/* > > * > Alternatively, the stx-monitor application may be built from source:* > > $MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh > --verbose --app stx-monitor > > * *Upload stx-monitor* > > *$ system application-upload *stx-monitor-1.0-1.tgz > > * *Assign host labels for stx-monitor* > > $ *system host-label-assign *controller-0 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled > elastic-master=enabled > > $ *system host-label-assign* controller-1 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled > elastic-master=enabled > > If there are worker hosts provisioned, one worker host must have the > following label assigned: > > e.g.   $ *system host-label-assign* compute-0 elastic-master=enabled > > * *Update helm-overrides, if required* > > There are default pod resource limits (e.g. cpu, memory, storage) for > the pods that may be tuned via helm-overrides for your deployment scenario. > > Optionally, the stx-monitor may also be configured via helm-overrides > for sending to an external elasticsearch cluster. In such case, please > refer to and execute the steps at  “*NOTE: External Elastic Server Case” > before continuing to the next step of apply stx-monitor.* > > * *Apply stx-monitor* > > *$ system application-apply stx-monitor* > > * *Refer to Elastic documentation (references below) for usage > guidelines* > > *e.g. Elastic Kibana interface may be accessible by pointing a web > browser at:* > > :31001 > > * *_NOTE: External Elastic Server Case_*__ > > *For sending to an external Elastic server.  Note that the external > Elasticsearch cluster must be* > > *up and reachable.* > > o *Set a unique system name for this cluster* > > *$ system modify --name < system-name >* > > ·*Setup helm-overrides for the services to access external server IP > which is running the Elastic cluster.* > > ·Refer to the auth and ssl options for setting up logstash for sending > to a secure authenticated Elasticsearch cluster: > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > >                           # The external server IP is the external > elastic cluster reachable from this server’s OAM or management network. > >                           # The following parameters should be set > according to the server running Elasticsearch: > >                              ES_CLIENT_IP_ADDR= > >                              ES_CLIENT_PATH=mon-elasticsearch-client > >                              ES_CLIENT_PORT=31001 > > cat <  ./logstash.yml > > elasticsearch: > >   host: http://$ES_CLIENT_IP_ADDR > >   port: $ES_CLIENT_PORT > > config: > >   elasticsearch.path: "/$ES_CLIENT_PATH" > > EOF > > cat <  ./filebeat.yml > > config: > >   output.elasticsearch: > >     hosts: > >     - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >   setup.dashboards: > >     enabled: false > > EOF > > cat < ./metricbeat.yml > > daemonset: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > deployment: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > EOF > > *Use the above generated files to set the overrides for metricbeat, > filebeat, and logstash,* > > *using the following commands:* > > *$ system helm-override-update stx-monitor metricbeat monitor --values > ./metricbeat.yml  --reuse-values* > > *$ system helm-override-update stx-monitor filebeat monitor --values > ./filebeat.yml --reuse-values* > > *$ system helm-override-update stx-monitor logstash monitor --values > ./logstash.yml  --reuse-values* > > ·* Disable appropriate charts, as these components will be running > external elastic database server: * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**client monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**data monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**master monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**curator monitor --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor kibana monitor > --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor nginx-ingress > monitor --enabled false* > > * *References**:* > > *Spec: > *https://docs.starlingx.io/specs/specs/stx-3.0/approved/stx-monitor_20 > 05733_infrastructure_and_cluster_monitoring.html > > *References:* > > ** Elasticsearch documentation > *https://www.elastic.co/guide/en/elasticsearch/reference/current/index > .html > > ** Elasticsearch-curator: > *https://www.elastic.co/guide/en/elasticsearch/client/curator/current/ > index.html > > > * FileBeat > https://www.elastic.co/guide/en/beats/filebeat/current/index.html > > * MetricBeat > https://www.elastic.co/guide/en/beats/metricbeat/current/index.html > > * Kibana https://www.elastic.co/guide/en/kibana/current/index.html > > * Logstash https://www.elastic.co/guide/en/logstash/current/index.html > > * Logstash > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From austin.sun at intel.com Tue Nov 19 07:12:56 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 19 Nov 2019 07:12:56 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/20/2019 Message-ID: Agenda for 11/20 meeting:     * stx.4.0 feature       - Ceph containerization update (Tingjie/martin)      - CentOS 8.0 upgrade planning (Shuai Zhao)      - CVE LP fixing (Shui Cheng)      - Standardize Flock Package Versioning (Yang Bin)      *)  Bugs Status Check          Medium           #LP1828262 Worker node reporting failed after host re-install post ceph-mon fs resizing(TingJie)           #LP1847335 DMAR initialization errors with newer Intel BIOSes(Jim)          #LP1851857 Cannot list sensors on host nodes(zhipeng)          #LP1851585 Replacing OSD hard disk on controller node  fails(Ovidiu) Stx.4.0     *)  Opens(all)  Update the agenda if needed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From cristopher.j.lemus.contreras at intel.com Tue Nov 19 09:00:43 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 19 Nov 2019 03:00:43 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$5rai1o@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191119T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Dariush.Eslimi at windriver.com Tue Nov 19 13:36:08 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 19 Nov 2019 13:36:08 +0000 Subject: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring In-Reply-To: <9A85D2917C58154C960D95352B22818BED3766BF@fmsmsx123.amr.corp.intel.com> References: <8152db41-bb7d-f3bb-ace6-bc1682efc1cb@linux.intel.com> <9A85D2917C58154C960D95352B22818BED3766BF@fmsmsx123.amr.corp.intel.com> Message-ID: File format change by itself does not create good documentation, as I said in my previous email I understand this was discussed in PTG and I believe it is a topic that needs to be discussed in community meeting and TSC, and as everything else should be voted on to become part of development process. Philosophically I am not in favour of developers doing the final documentation as they are not trained to do product documentation, and you will end up with different style and not consistent quality. They should provide raw input. Also their time is better spent in what they are trained to do, software design and coding. But if community decides to go ahead as whole, I will oblige. Thanks, Dariush -----Original Message----- From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: November-18-19 9:12 PM To: Eslimi, Dariush ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Good documentation is very important to our project, and the Docs team is small and cannot create all of the content. We need the community to pitch in and help. We have to make a culture change and get into the mode of developers submitting Doc updates along with code submissions. I'd be happy to give a tutorial on the doc process and file format next week at the community meeting, or any time needed. brucej -----Original Message----- From: Eslimi, Dariush [mailto:Dariush.Eslimi at windriver.com] Sent: Monday, November 18, 2019 6:08 AM To: Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Hi Saul, I do not believe this Is part of new approved development process yet. I understand that you have discussed it, but this is not part of current release/development process for STX-3.0. Thanks, Dariush -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: November-15-19 5:49 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] System Monitor Deployment (stx-monitor) - Cluster and Infrastructure Monitoring Hi John, If this is intended to be a documentation submission, you should really re-work this into RST and submit it to the starlingx/docs repo. It should contain the content and descriptions of what the service is intended to be and how to use it. This is what was discussed at the PTG in Shanghai a week ago. Thanks Sau! On 11/15/19 9:03 AM, Kung, John wrote: > *System Monitor - Cluster and Infrastructure Monitoring Deployment* > > ** > > *Story: *https://storyboard.openstack.org/#!/story/2005733 > > The Infrastructure and Cluster Monitor in stx3.0 allows for the > deployment of a monitoring solution for the infrastructure and > Kubernetes cluster and its services. > > The following describes the deployment of stx-monitor. > > *_Steps to Deploy stx-monitor_**:* > > * *Obtain the stx-monitor application (e.g. stx-monitor-1.0-1.tgz) * > > ** > > *stx-monitor  may be obtained from the CENGN  mirror:* > > *http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/lates > t_green_build/outputs/helm-charts/* > > * > Alternatively, the stx-monitor application may be built from source:* > > $MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh > --verbose --app stx-monitor > > * *Upload stx-monitor* > > *$ system application-upload *stx-monitor-1.0-1.tgz > > * *Assign host labels for stx-monitor* > > $ *system host-label-assign *controller-0 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled > elastic-master=enabled > > $ *system host-label-assign* controller-1 elastic-data=enabled > elastic-controller=enabled elastic-client=enabled > elastic-master=enabled > > If there are worker hosts provisioned, one worker host must have the > following label assigned: > > e.g.   $ *system host-label-assign* compute-0 elastic-master=enabled > > * *Update helm-overrides, if required* > > There are default pod resource limits (e.g. cpu, memory, storage) for > the pods that may be tuned via helm-overrides for your deployment scenario. > > Optionally, the stx-monitor may also be configured via helm-overrides > for sending to an external elasticsearch cluster. In such case, please > refer to and execute the steps at  “*NOTE: External Elastic Server Case” > before continuing to the next step of apply stx-monitor.* > > * *Apply stx-monitor* > > *$ system application-apply stx-monitor* > > * *Refer to Elastic documentation (references below) for usage > guidelines* > > *e.g. Elastic Kibana interface may be accessible by pointing a web > browser at:* > > :31001 > > * *_NOTE: External Elastic Server Case_*__ > > *For sending to an external Elastic server.  Note that the external > Elasticsearch cluster must be* > > *up and reachable.* > > o *Set a unique system name for this cluster* > > *$ system modify --name < system-name >* > > ·*Setup helm-overrides for the services to access external server IP > which is running the Elastic cluster.* > > ·Refer to the auth and ssl options for setting up logstash for sending > to a secure authenticated Elasticsearch cluster: > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > >                           # The external server IP is the external > elastic cluster reachable from this server’s OAM or management network. > >                           # The following parameters should be set > according to the server running Elasticsearch: > >                              ES_CLIENT_IP_ADDR= > >                              ES_CLIENT_PATH=mon-elasticsearch-client > >                              ES_CLIENT_PORT=31001 > > cat <  ./logstash.yml > > elasticsearch: > >   host: http://$ES_CLIENT_IP_ADDR > >   port: $ES_CLIENT_PORT > > config: > >   elasticsearch.path: "/$ES_CLIENT_PATH" > > EOF > > cat <  ./filebeat.yml > > config: > >   output.elasticsearch: > >     hosts: > >     - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >   setup.dashboards: > >     enabled: false > > EOF > > cat < ./metricbeat.yml > > daemonset: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > deployment: > >   config: > >     output.elasticsearch: > >       hosts: > >       - "$ES_CLIENT_IP_ADDR:$ES_CLIENT_PORT/$ES_CLIENT_PATH" > >     setup.dashboards: > >       enabled: false > > EOF > > *Use the above generated files to set the overrides for metricbeat, > filebeat, and logstash,* > > *using the following commands:* > > *$ system helm-override-update stx-monitor metricbeat monitor --values > ./metricbeat.yml  --reuse-values* > > *$ system helm-override-update stx-monitor filebeat monitor --values > ./filebeat.yml --reuse-values* > > *$ system helm-override-update stx-monitor logstash monitor --values > ./logstash.yml  --reuse-values* > > ·* Disable appropriate charts, as these components will be running > external elastic database server: * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**client monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**data monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**master monitor --enabled false * > > *$ system helm-chart-attribute-modify stx-monitor > elasticsearch**-**curator monitor --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor kibana monitor > --enabled false* > > *$ system helm-chart-attribute-modify stx-monitor nginx-ingress > monitor --enabled false* > > * *References**:* > > *Spec: > *https://docs.starlingx.io/specs/specs/stx-3.0/approved/stx-monitor_20 > 05733_infrastructure_and_cluster_monitoring.html > > *References:* > > ** Elasticsearch documentation > *https://www.elastic.co/guide/en/elasticsearch/reference/current/index > .html > > ** Elasticsearch-curator: > *https://www.elastic.co/guide/en/elasticsearch/client/curator/current/ > index.html > > > * FileBeat > https://www.elastic.co/guide/en/beats/filebeat/current/index.html > > * MetricBeat > https://www.elastic.co/guide/en/beats/metricbeat/current/index.html > > * Kibana https://www.elastic.co/guide/en/kibana/current/index.html > > * Logstash https://www.elastic.co/guide/en/logstash/current/index.html > > * Logstash > https://www.elastic.co/guide/en/logstash/7.4/plugins-outputs-elasticse > arch.html > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From saichandu.behara at calsoftinc.com Tue Nov 19 14:13:15 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Tue, 19 Nov 2019 19:43:15 +0530 Subject: [Starlingx-discuss] Error while installing StarlingX Openstack on all-in-one simplex In-Reply-To: <6d0c6e04-33ca-1392-6231-6e1f35c29e42@intel.com> References: <72561858-760a-a7e4-fbe8-d0c246f7a191@intel.com> <86eed2ce-593c-7f54-3f80-ed1046a93160@intel.com> <6d0c6e04-33ca-1392-6231-6e1f35c29e42@intel.com> Message-ID: <1274c183-33d7-f35c-66ff-2f51fb2607ce@calsoftinc.com> Hi all, I installed Openstack on StarlingX. Some times, The Openstack web page is opened some times Openstack webpage is not opened. It's getting " Timed out ". Is there any way to troubleshoot the issue. I'm wondering the issue because some times it's not opened the webpage. If any one aware the issue, Please let us know. On 07-11-2019 13:17, Yong Hu wrote: > the mailing list blocked my attachment, so here I sent it again. > > > On 2019/11/7 3:39 PM, Yong Hu wrote: >> According this build info: >> > BUILD_ID="20190920T013000Z" >> > >> > JOB="STX_build_master_master" >> >> Your platform ISO was the Cengn build on *master branch* on 0920, >> whereas your openstack (stx-openstack-1.0-17-centos-stable-latest.tgz >> ) was from *2.0 RC branch*. That led to the mismatch very likely. >> >> Have a try with the attached stx-openstack helm chart tarball, which >> was originally downloaded from 0920 master build in Cengn. >> >> >> >> On 2019/11/7 1:31 PM, Saichandu Behara wrote: >>> Hi yong, >>> >>> I have downloaded the StarlingX R2 iso image and dated as around sep >>> 22,2019. At present i don't have exact link, because, the build >>> dates are changed now. >>> >>> But, I have downloaded the .iso in " >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ " >>> latest build. >>> >>> >>> Build info ::: >>> controller-0:~$ cat /etc/build.info >>> ### >>> ### StarlingX >>> ### Built from master >>> ### >>> >>> OS="centos" >>> SW_VERSION="19.09" >>> BUILD_TARGET="Host Installer" >>> BUILD_TYPE="Formal" >>> BUILD_ID="20190920T013000Z" >>> >>> JOB="STX_build_master_master" >>> BUILD_BY="starlingx.build at cengn.ca" >>> BUILD_NUMBER="256" >>> BUILD_HOST="starlingx_mirror" >>> BUILD_DATE="2019-09-20 01:30:00 +0000" >>> >>> >>> Please let me know for future solution. It would be a great help. >>> >>> >>> Thanks & Regards >>> >>> Sai Chandu Behara >>> >>> >>> >>> On 07-11-2019 06:39, Yong Hu wrote: >>>> Hi Sai, >>>> Could you share the download URL for the installation image (.iso)? >>>> As well you can tell the build info by: >>>> cat /etc/build.info >>>> >>>> I wonder your issue was caused by a mismatch b/w StarlingX platform >>>> and this stx-openstack tarball. >>>> >>>> regards, >>>> Yong >>>> >>>> On 2019/11/4 7:43 PM, Saichandu Behara wrote: >>>>> Hello all, >>>>> >>>>> I am trying to install StarlingX OpenStack on all-in-one simplex . >>>>> When i am installing application manifest and helm-charts, getting >>>>> some versioning error. >>>>> >>>>> I downloaded Package from " >>>>> http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.0/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >>>>> " and >>>>> "http://mirror.starlingx.cengn.ca/mirror/starlingx/release/2.0.1/centos/outputs/helm-charts/stx-openstack-1.0-17-centos-stable-latest.tgz >>>>> " ( Both are getting errors ). >>>>> >>>>> I'm trying to upload the package by using command " system >>>>> application-upload stx-openstack-1.0-17-centos-stable-latest.tgz " >>>>> >>>>> +---------------+----------------------------------+ >>>>> | Property | Value | >>>>> +---------------+----------------------------------+ >>>>> | active | False | >>>>> | app_version | 1.0-17-centos-stable-latest | >>>>> | created_at | 2019-11-04T11:05:19.899672+00:00 | >>>>> | manifest_file | stx-openstack.yaml | >>>>> | manifest_name | armada-manifest | >>>>> | name | stx-openstack | >>>>> | progress | None | >>>>> | status | uploading | >>>>> | updated_at | None | >>>>> +---------------+----------------------------------+ >>>>> >>>>> >>>>> and when i checking the application list, getting upload failed. >>>>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>>>> >>>>> | application | version | manifest >>>>> name | manifest file | status | progress | >>>>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>>>> >>>>> | platform-integ-apps | 1.0-7 | >>>>> platform-integration-manifest | manifest.yaml | applied | >>>>> completed | >>>>> *| stx-openstack | 1.0-17-centos-stable- | >>>>> armada-manifest | stx-openstack. | >>>>> **upload-failed**| Upload of application stx-openstack (1. |** >>>>> **| | latest | | yaml | | >>>>> 0-17-centos-stable-latest) failed: |** >>>>> **| | | | | | Unsupported >>>>> application version. * | >>>>> | | | | | >>>>> | | >>>>> +---------------------+---------------------------+-------------------------------+----------------+---------------+-------------------------------------------+ >>>>> >>>>> >>>>> If anyone is aware of this issue, please let us know. It would be >>>>> a great help. >>>>> >>>>> -- >>>>> Thanks & Regards >>>>> Sai Chandu Behara >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>>>> >>>> >>> -- Thanks & Regards Sai Chandu Behara From haochuan.z.chen at intel.com Tue Nov 19 16:02:26 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Tue, 19 Nov 2019 16:02:26 +0000 Subject: [Starlingx-discuss] layer build patch review Message-ID: <56829C2A36C2E542B0CCB9854828E4D85627F89A@CDSMSX102.ccr.corp.intel.com> Hi I have update layer build patch again, please review. And we request a doc for this feature. https://review.opendev.org/#/c/688598/ https://review.opendev.org/#/c/693458/ https://review.opendev.org/#/c/693459/ https://review.opendev.org/#/c/695010/ https://review.opendev.org/#/c/681821/ https://review.opendev.org/#/c/681914/ https://review.opendev.org/#/c/681892/ BR! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Nov 19 20:40:01 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 19 Nov 2019 20:40:01 +0000 Subject: [Starlingx-discuss] Community Call (Nov 20, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B2B51C@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call tomorrow. Feel free to add new topics to the agenda at [0]... currently we just have the standing topics and a look ahead to stx.4.0. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191120T1500 From maria.g.perez.ibarra at intel.com Tue Nov 19 23:19:01 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 19 Nov 2019 23:19:01 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191119 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-19 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006984.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Tue Nov 19 23:48:15 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 19 Nov 2019 23:48:15 +0000 Subject: [Starlingx-discuss] [ Regression testing - stx3.0 ] Report for 11/19/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191018T013000Z" from (link) ---------------------------------------------------------------------- MANUAL EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 274 Pass = 252 Fail = 7 Blocked = 8 Not Run = 5 Obsolete = 2 Deferred = 0 Total executed = 259 Pass Rate = 97% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT - INTEL --------------------------------------------------------------------------- Overall Results: Total = 202 Pass = 154 Fail = 9 Blocked = 38 Obsolete = 0 Deferred = 0 Not Valid = 1 Total executed = 163 Pass Rate = 94% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST - WR --------------------------------------------------------------------------- Overall Results: Total = 467 Pass = 15 Fail = 2 Blocked = 0 Not Run = 450 Obsolete = 0 Deferred = 0 Total executed = 17 Pass Rate = 88% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 NOTE: * The train testing is in progress and results will be detailed in the next report. Regards! Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Nov 20 02:38:50 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 20 Nov 2019 02:38:50 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Message-ID: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don't know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of "everyone can see everything" is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Nov 20 05:35:07 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 20 Nov 2019 05:35:07 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F360C65E7@SHSMSX104.ccr.corp.intel.com> Forrest, Huifeng, Do you understand the issue below and if we have any plan to address it? Cindy Xie IAGS [One Intel Champion Badge] From: Jones, Bruce E Sent: Wednesday, November 20, 2019 10:39 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don't know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of "everyone can see everything" is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 17704 bytes Desc: image003.png URL: From forrest.zhao at intel.com Wed Nov 20 05:44:53 2019 From: forrest.zhao at intel.com (Zhao, Forrest) Date: Wed, 20 Nov 2019 05:44:53 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F360C65E7@SHSMSX104.ccr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> <2FD5DDB5A04D264C80D42CA35194914F360C65E7@SHSMSX104.ccr.corp.intel.com> Message-ID: <6345119E91D5C843A93D64F498ACFA1374F2DACA@shsmsx102.ccr.corp.intel.com> These are the known issues in off-the-shelf Kubernetes. A CNCF SIG was formed to address the issue of "no isolation among multi-tenant"; data path performance is being addressed by other open-source projects, such as Cilium. The slogan in Cilium's kubecon booth is "Liberating Kubernetes from kube-proxy and iptables". Thanks, Forrest From: Xie, Cindy Sent: Tuesday, November 19, 2019 9:35 PM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io; Zhao, Forrest ; Le, Huifeng Subject: RE: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Forrest, Huifeng, Do you understand the issue below and if we have any plan to address it? Cindy Xie IAGS [One Intel Champion Badge] From: Jones, Bruce E > Sent: Wednesday, November 20, 2019 10:39 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don't know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of "everyone can see everything" is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 13722 bytes Desc: image002.png URL: From qianjiang at baicells.com Wed Nov 20 07:50:51 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Wed, 20 Nov 2019 15:50:51 +0800 Subject: [Starlingx-discuss] =?utf-8?q?Does_StarlingX_support_NFV=3F_Is_th?= =?utf-8?q?ere_any_guide_about_operating_NFV=3F?= Message-ID: Hi, Community As I know from NFV plugtest paper, the StarlingX provides NFVI. But, are there any materials about how to operate NFV, for example, deploy a VNF FG? I am using "Virtual All-in-one Simplex Installation R2.0". Thanks Advance. Best Regard -------------- next part -------------- An HTML attachment was scrubbed... URL: From qianjiang at baicells.com Wed Nov 20 08:33:12 2019 From: qianjiang at baicells.com (=?UTF-8?B?6ZKx5rGf?=) Date: Wed, 20 Nov 2019 16:33:12 +0800 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIElzc3Vlcw==?= In-Reply-To: References: Message-ID: <85e75079-ecfb-4641-aa43-0bc1ba2e0896.qianjiang@baicells.com> just some suggestions inside your mail, ------------------------------------------------------------------ 发件人:von Hoesslin, Volker 发送时间:2019年11月17日(星期日) 04:06 收件人:starlingx-discuss at lists.starlingx.io 主 题:[Starlingx-discuss] Issues So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :( > Is your installation virtual type? If so, you can redirect the startup message to virsh console, I forget how to, you can ask from google. 2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ? > Before use Horizon, you can try commands using "system" and "openstack", for example, $ source /etc/platform/openrc $ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-18-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | | systemtestapp1 | 1.0-7 | systemtestapp1-manifest | manifest.yaml | remove-failed | operation aborted, check logs for detail | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ and use openstack, controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor list +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | 0 | m1.nano | 64 | 1 | 0 | 1 | True | | 02c7efd7-747f-42a1-9106-584541717745 | m1.medium | 4096 | 40 | 0 | 2 | True | | 2103aa07-e42a-4b65-a74c-bb0d960889c2 | m1.small | 2048 | 20 | 0 | 1 | True | | 5a99dcae-6a6f-434d-a11f-d7578462eb86 | m1.xlarge | 16384 | 160 | 0 | 8 | True | | 8e3f6810-e872-4aac-8a40-acf44d8077dc | m1.tiny | 512 | 1 | 0 | 1 | True | | f469dbc7-e09d-40c3-97dd-95f4447a7998 | m1.large | 8192 | 80 | 0 | 4 | True | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ Besides, you can check helm, kubernetes use their commands. As for log, it depends your command, for example, the "system" command log is in /var/log/sysinv.log. greez & thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From zheng.ma at intel.com Wed Nov 20 08:40:18 2019 From: zheng.ma at intel.com (Ma, Zheng) Date: Wed, 20 Nov 2019 08:40:18 +0000 Subject: [Starlingx-discuss] [openstack-train] Is openstack-train feature available in latest stx-build? Message-ID: Hi team, I noticed that openstack train code merge is completed. But I don't know if it is built into the latest iso. We have setup with latest iso [link] and openstack tar file [link], but the openstack version is not train I think. We have tried to apply the "dev-latest" application with "system application-apply" but failed on uploading stage with error info "unsupported version" So could I know how to get the train-version-integrated iso or we have to upgrade to train version ourselves? Thanks! BR, Zheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Wed Nov 20 08:55:25 2019 From: yong.hu at intel.com (Yong Hu) Date: Wed, 20 Nov 2019 16:55:25 +0800 Subject: [Starlingx-discuss] [openstack-train] Is openstack-train feature available in latest stx-build? In-Reply-To: References: Message-ID: <14973a76-8dab-fd33-e31d-252e119c6305@intel.com> Since 11/16, OpenStack services should be Train version. Here is some info I got from my deployment (based on Cengn build yesterday). You can see it nova's version is 20.0.2 already. --------------------------------------------------------------------- controller-0:~$ kubectl exec -it nova-conductor-55b4c68cd-cvxtd -n openstack sh sh-4.2# nova- nova-api nova-api-wsgi nova-console nova-metadata-wsgi nova-policy nova-scheduler nova-status nova-api-metadata nova-compute nova-dhcpbridge nova-network nova-rootwrap nova-serialproxy nova-xvpvncproxy nova-api-os-compute nova-conductor nova-manage nova-novncproxy nova-rootwrap-daemon nova-spicehtml5proxy sh-4.2# nova-manage version Deprecated: Option "idle_timeout" from group "database" is deprecated. Use option "connection_recycle_time" from group "database". Deprecated: Option "idle_timeout" from group "api_database" is deprecated. Use option "connection_recycle_time" from group "api_database". 20.0.2 On 2019/11/20 4:40 PM, Ma, Zheng wrote: > Hi team, > > I noticed that openstack train code merge is completed. > > But I don’t know if it is built into the latest iso. > > We have setup with latest iso [link > ] > and openstack tar file [link > ], > but the openstack version is not train I think. > > We have tried to apply the “dev-latest” application with “system > application-apply” but failed on uploading stage with error info > “unsupported version” > > So could I know how to get the train-version-integrated iso or we have > to upgrade to train version ourselves? > > Thanks! > > BR, > > Zheng > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cristopher.j.lemus.contreras at intel.com Wed Nov 20 09:01:36 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 20 Nov 2019 03:01:36 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <86d0ec$6dndsv@fmsmga001.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191120T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Volker.Hoesslin at swsn.de Wed Nov 20 10:06:49 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Wed, 20 Nov 2019 10:06:49 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIElzc3Vlcw==?= In-Reply-To: <85e75079-ecfb-4641-aa43-0bc1ba2e0896.qianjiang@baicells.com> References: <85e75079-ecfb-4641-aa43-0bc1ba2e0896.qianjiang@baicells.com> Message-ID: Great, thx! The graphical install bug is not my prio problem, just a report agains the STX team. The network issue can also fixed by my own (I should thinking befor posting ;)), my VLAN based setup hadnt any segmentation ranges. After study the STX network FAQ, I could fix this. Btw, the STX horizon backend do not show any network segmentation ranges in GUI and also it isnt possible to config the segmentation via horizon GUI. Thx, volker. Von: 钱江 [mailto:qianjiang at baicells.com] Gesendet: Mittwoch, 20. November 2019 09:33 An: von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io Betreff: [Starlingx-discuss] 回复: Issues just some suggestions inside your mail, ------------------------------------------------------------------ 发件人:von Hoesslin, Volker 发送时间:2019年11月17日(星期日) 04:06 收件人:starlingx-discuss at lists.starlingx.io 主 题:[Starlingx-discuss] Issues So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :( > Is your installation virtual type? If so, you can redirect the startup message to virsh console, I forget how to, you can ask from google. 2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ? > Before use Horizon, you can try commands using "system" and "openstack", for example, $ source /etc/platform/openrc $ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-18-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | | systemtestapp1 | 1.0-7 | systemtestapp1-manifest | manifest.yaml | remove-failed | operation aborted, check logs for detail | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ and use openstack, controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor list +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | 0 | m1.nano | 64 | 1 | 0 | 1 | True | | 02c7efd7-747f-42a1-9106-584541717745 | m1.medium | 4096 | 40 | 0 | 2 | True | | 2103aa07-e42a-4b65-a74c-bb0d960889c2 | m1.small | 2048 | 20 | 0 | 1 | True | | 5a99dcae-6a6f-434d-a11f-d7578462eb86 | m1.xlarge | 16384 | 160 | 0 | 8 | True | | 8e3f6810-e872-4aac-8a40-acf44d8077dc | m1.tiny | 512 | 1 | 0 | 1 | True | | f469dbc7-e09d-40c3-97dd-95f4447a7998 | m1.large | 8192 | 80 | 0 | 4 | True | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ Besides, you can check helm, kubernetes use their commands. As for log, it depends your command, for example, the "system" command log is in /var/log/sysinv.log. greez & thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Wed Nov 20 12:08:51 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Wed, 20 Nov 2019 12:08:51 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Bruce, StarlingX container networking leverages Calico [1] as the default CNI for K8s. Calico implements Pod networking and provides an implementation for K8s Network Policies [2]. The Calico network policies gives the end-user full control over inter-pod communication by defining service level and pod level access controls for micro-segmentation of the network communication. In addition, StarlingX provides the Multus and SRIOV CNI plugins as part of the standard deployment. Together, these permit container workloads to terminate high-bandwidth network interfaces directly into a container. This configuration can be leveraged for latency sensitive applications that require raw access to network payloads. Finally, K8s networking is on an evolution path to provide higher performance Linux networking capabilities through Linux projects such as XDP [3]. XDP is starting to be leveraged by many K8s networking CNI solutions, including Calico [4]. [1] https://www.projectcalico.org/ [2] https://docs.projectcalico.org/v3.8/security/kubernetes-network-policy [3] https://www.iovisor.org/technology/xdp [4] https://www.projectcalico.org/introducing-xdp-optimized-denial-of-service-mitigation/ From: "Jones, Bruce E" Date: Tuesday, November 19, 2019 at 9:40 PM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don’t know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Nov 20 13:57:19 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Nov 2019 13:57:19 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality In-Reply-To: References: Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> Hi Anirudh, don't know if you got an answer directly, but this is not supported. Bill... From: Anirudh Gupta Sent: Monday, November 11, 2019 3:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Wed Nov 20 15:25:35 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Wed, 20 Nov 2019 15:25:35 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIElzc3Vlcw==?= In-Reply-To: <79s9vu01dm39gued@shdsegapp2> References: <85e75079-ecfb-4641-aa43-0bc1ba2e0896.qianjiang@baicells.com> <79s9vu01dm39gued@shdsegapp2> Message-ID: Ok, the graphical install_output needs also to remove all console parameter, if they empty the graphical parameter will work. Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Mittwoch, 20. November 2019 11:07 An: '??'; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] 回复: Issues Great, thx! The graphical install bug is not my prio problem, just a report agains the STX team. The network issue can also fixed by my own (I should thinking befor posting ;)), my VLAN based setup hadnt any segmentation ranges. After study the STX network FAQ, I could fix this. Btw, the STX horizon backend do not show any network segmentation ranges in GUI and also it isnt possible to config the segmentation via horizon GUI. Thx, volker. Von: 钱江 [mailto:qianjiang at baicells.com] Gesendet: Mittwoch, 20. November 2019 09:33 An: von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io Betreff: [Starlingx-discuss] 回复: Issues just some suggestions inside your mail, ------------------------------------------------------------------ 发件人:von Hoesslin, Volker 发送时间:2019年11月17日(星期日) 04:06 收件人:starlingx-discuss at lists.starlingx.io 主 题:[Starlingx-discuss] Issues So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :( > Is your installation virtual type? If so, you can redirect the startup message to virsh console, I forget how to, you can ask from google. 2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ? > Before use Horizon, you can try commands using "system" and "openstack", for example, $ source /etc/platform/openrc $ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-18-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | | systemtestapp1 | 1.0-7 | systemtestapp1-manifest | manifest.yaml | remove-failed | operation aborted, check logs for detail | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ and use openstack, controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor list +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | 0 | m1.nano | 64 | 1 | 0 | 1 | True | | 02c7efd7-747f-42a1-9106-584541717745 | m1.medium | 4096 | 40 | 0 | 2 | True | | 2103aa07-e42a-4b65-a74c-bb0d960889c2 | m1.small | 2048 | 20 | 0 | 1 | True | | 5a99dcae-6a6f-434d-a11f-d7578462eb86 | m1.xlarge | 16384 | 160 | 0 | 8 | True | | 8e3f6810-e872-4aac-8a40-acf44d8077dc | m1.tiny | 512 | 1 | 0 | 1 | True | | f469dbc7-e09d-40c3-97dd-95f4447a7998 | m1.large | 8192 | 80 | 0 | 4 | True | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ Besides, you can check helm, kubernetes use their commands. As for log, it depends your command, for example, the "system" command log is in /var/log/sysinv.log. greez & thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Nov 20 15:30:36 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 20 Nov 2019 15:30:36 +0000 Subject: [Starlingx-discuss] MoM Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/20/2019 Message-ID: Hi All: Thanks join the call. Here is MoM of today's meeting: Agenda for 11/20 meeting: Stx.3.0 MS3 announcement http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006981.html baseline is 20191115T023000Z * stx.4.0 feature - Standardize Flock Package Versioning (Yang Bin) Story: https://storyboard.openstack.org/#!/story/2006703 https://review.opendev.org/#/c/691632/ https://review.opendev.org/#/c/691647 - Ceph containerization update (Tingjie/martin) BP for BlueStore:https://review.opendev.org/#/c/692502/ : Tingjie updated, and need more comments and review. Story: https://storyboard.openstack.org/#!/story/2005527 36443: Rook application integration. Martin. update patch: https://review.opendev.org/#/c/681457/ and wait for review. should be closed by this week. 36444: mapping ceph.pp setting to yaml override. Martin. breakdown the ceph config class and mapping to overrides. in-progress 37432: Rook plugin implementation with common infrastructure: Tingjie. create and work on github: https://github.com/silverhandy/python-rookclient in-progress should be ready for Dec 7th. Currently Martin and Tingjie have some efforts on Bug fixing on STX 3.0, so will have impact on the progress of Ceph containerization. - CentOS 8.0 upgrade planning (Shuai Zhao) *builder container and mock upgrade to centos 8.0 patches are uploaded, under review. * kernel upgrade https://review.opendev.org/#/c/695134/ 1) kernel patch ananlysis status 1st round is done . 2) kernel config diff between 3.10/4.18 analysis starlingx 3.10 config was remained same as 4.18 3) kernel module upgrade drbd 8.4.11 package built failed , download new 9.0.21 tarball and build pass. qat and drbd ko signature built failure. 3.10/4.18 signature is different * srpm upgrade * tarball upgrade analysis. all uploaded patches link: https://review.opendev.org/#/q/topic:centos8+branch:f/centos8 upstream repo need f/centos8 branch. *) CVE LP fixing (Shui Cheng) for stx.3.0/2.0 OVMF https://github.com/starlingx-staging/stx-nova/pull/27 for Stx.2.0 CR+1, wait CR+2 Stx.3.0 is not need staging. https://review.opendev.org/#/c/693759/ libx11 https://review.opendev.org/#/c/693297/ kernel change is under test. will upload patch by this week. *) Bugs Status Check (will check offline) *) Opens. Thanks. BR Austin Sun. -----Original Message----- From: Sun, Austin Sent: Tuesday, November 19, 2019 3:13 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/20/2019 Agenda for 11/20 meeting:     * stx.4.0 feature       - Ceph containerization update (Tingjie/martin)      - CentOS 8.0 upgrade planning (Shuai Zhao)      - CVE LP fixing (Shui Cheng)      - Standardize Flock Package Versioning (Yang Bin)      *)  Bugs Status Check          Medium           #LP1828262 Worker node reporting failed after host re-install post ceph-mon fs resizing(TingJie)           #LP1847335 DMAR initialization errors with newer Intel BIOSes(Jim)          #LP1851857 Cannot list sensors on host nodes(zhipeng)          #LP1851585 Replacing OSD hard disk on controller node  fails(Ovidiu) Stx.4.0     *)  Opens(all)  Update the agenda if needed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From Don.Penney at windriver.com Wed Nov 20 15:32:19 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 20 Nov 2019 15:32:19 +0000 Subject: [Starlingx-discuss] =?utf-8?b?5Zue5aSN77yaIElzc3Vlcw==?= In-Reply-To: References: <85e75079-ecfb-4641-aa43-0bc1ba2e0896.qianjiang@baicells.com> <79s9vu01dm39gued@shdsegapp2> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FC15BD414@ALA-MBD.corp.ad.wrs.com> There is also a “console” parameter you can use in host-add or host-update that allows you to set the console parameter. Leaving this blank, or just “console=” on the CLI, will remove the console parameter from the boot cmdline. You could also explicitly set the console like “console=tty0”, “console=tty1”, “console=ttyS0,115200”, etc From: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Sent: Wednesday, November 20, 2019 10:26 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] 回复: Issues Ok, the graphical install_output needs also to remove all console parameter, if they empty the graphical parameter will work. Von: von Hoesslin, Volker [mailto:Volker.Hoesslin at swsn.de] Gesendet: Mittwoch, 20. November 2019 11:07 An: '??'; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] 回复: Issues Great, thx! The graphical install bug is not my prio problem, just a report agains the STX team. The network issue can also fixed by my own (I should thinking befor posting ;)), my VLAN based setup hadnt any segmentation ranges. After study the STX network FAQ, I could fix this. Btw, the STX horizon backend do not show any network segmentation ranges in GUI and also it isnt possible to config the segmentation via horizon GUI. Thx, volker. Von: 钱江 [mailto:qianjiang at baicells.com] Gesendet: Mittwoch, 20. November 2019 09:33 An: von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io Betreff: [Starlingx-discuss] 回复: Issues just some suggestions inside your mail, ------------------------------------------------------------------ 发件人:von Hoesslin, Volker 发送时间:2019年11月17日(星期日) 04:06 收件人:starlingx-discuss at lists.starlingx.io 主 题:[Starlingx-discuss] Issues So, my first report after first try to install STX 2.0: 1. by add a new host i have add the parameter "install_output=graphical", but the complete install will run behind a black screen like text mode :( > Is your installation virtual type? If so, you can redirect the startup message to virsh console, I forget how to, you can ask from google. 2. after complete the install (duplex+dedicated storage (3 replication)) i can not add a new network, horizon did not do the job, just say "can not create"... how do i get more info/reports/logs ? > Before use Horizon, you can try commands using "system" and "openstack", for example, $ source /etc/platform/openrc $ system application-list +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | application | version | manifest name | manifest file | status | progress | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ | platform-integ-apps | 1.0-7 | platform-integration-manifest | manifest.yaml | applied | completed | | stx-openstack | 1.0-18-centos-stable-latest | armada-manifest | stx-openstack.yaml | applied | completed | | systemtestapp1 | 1.0-7 | systemtestapp1-manifest | manifest.yaml | remove-failed | operation aborted, check logs for detail | +---------------------+-----------------------------+-------------------------------+--------------------+---------------+------------------------------------------+ and use openstack, controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack flavor list +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ | 0 | m1.nano | 64 | 1 | 0 | 1 | True | | 02c7efd7-747f-42a1-9106-584541717745 | m1.medium | 4096 | 40 | 0 | 2 | True | | 2103aa07-e42a-4b65-a74c-bb0d960889c2 | m1.small | 2048 | 20 | 0 | 1 | True | | 5a99dcae-6a6f-434d-a11f-d7578462eb86 | m1.xlarge | 16384 | 160 | 0 | 8 | True | | 8e3f6810-e872-4aac-8a40-acf44d8077dc | m1.tiny | 512 | 1 | 0 | 1 | True | | f469dbc7-e09d-40c3-97dd-95f4447a7998 | m1.large | 8192 | 80 | 0 | 4 | True | +--------------------------------------+-----------+-------+------+-----------+-------+-----------+ Besides, you can check helm, kubernetes use their commands. As for log, it depends your command, for example, the "system" command log is in /var/log/sysinv.log. greez & thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Nov 20 16:31:21 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Nov 2019 16:31:21 +0000 Subject: [Starlingx-discuss] Community Call (Nov 20, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B2BB63@ALA-MBD.corp.ad.wrs.com> Notes & actions from today's meeting... Standing Topics - stx.3.0 Gating Bugs - total critical/high/medium: 80 https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0 - distro.openstack: 15 - per Yong, focus is on these now - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.openstack - security: 14 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.security - config: 11 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.config - containers: 24 - per Frank, looking to get forecasts from the assignees - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers - containers/networking: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers+stx.networking - networking: 5 - per Huifeng, looking at the high priority bugs now - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.networking - storage: 5 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage - distcloud: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distcloud - metal: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.metal - fault: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.fault - update: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.update - Elio - can we get queries for these to see which bugs require testing / re-testing? - Ghada to put the queries here - stx.3.0 Opens: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 - stx.3.0 Fixed & Retest Needed: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=FIXRELEASED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.3.0+stx.retestneeded&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search - Gerrit Reviews in Need of Attention - nothing this week - Sanity: any RED since last week? - not since the issue we discussed last week - last week's issue was ultimately due to a Day 1, intermittent, tiller issue that Bob was able to fix - it was intermittent *and* only seen with certain configs - Unanswered Requests for Help on Mailing List - Anirudh Gupta: StarlingX 2.0 Release Upgrade Functionality http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006948.html - answered now - this is not supported - Kris noted that the Doc team is working on a "developer resource" for upversioning from Stein to Train - - Sai Chandu Behara: not posted yet on mailing list, but... - We are facing some issues on Openstack. Openstack is running fine. - But, The Main VM is asking for password Change. I have changed the password. - After that, Openstack webpage is not accessing. It's getting " Timed out " - And when i revert the old snapshot, then openstack webpage is working fine. - Is there any connection between VM password and Openstack/openstack webpage. VM also not able to shutdown. - Sai Chandu to raise a Launchpad for this issue - no one on the call was able to say what the issue might be. This Week's Topics - stx.3.0 - Chris L - asked that the 3.0 RC builds are built *before* master --> Scott - Doc update: Kristal Dale - looking for technical input on some areas, per https://etherpad.openstack.org/p/stx-documentation - Kris will send the list out to the mailing list - stx.4.0 content planning next steps. - Items reviewed at PTG can be found here: https://etherpad.openstack.org/p/stx.4.0-feature-candidates - release team will build a matrix of features vs. sub-projects/repos to help project review workload AR Updates - Oct 9, 2019 -- Frank -- see if the CENGN access can be opened up to other folks besides Scott & Don so we've got more options to get stuff like this done - Nov 30: the access has been granted - Sep 11, 2019 -- Bruce -- identify the feature documentation gaps - Nov 30: as per Kris' update on the call today - July 31, 2019 -- Ada/Yang -- combine sanity runs/reports - Nov 30: per Jose, they sorted out their Pytest issues & are now reviewing the results with Yang - May 8, 2019 -- Frank -- follow up with CENGN on storage for really large files for reference in Launchpads - Nov 20: trial is happening now through next week -----Original Message----- From: Zvonar, Bill Sent: Tuesday, November 19, 2019 3:40 PM To: starlingx-discuss at lists.starlingx.io Subject: Community Call (Nov 20, 2019) Hi all, reminder of the Community call tomorrow. Feel free to add new topics to the agenda at [0]... currently we just have the standing topics and a look ahead to stx.4.0. Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191120T1500 From maria.g.perez.ibarra at intel.com Wed Nov 20 17:35:36 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Wed, 20 Nov 2019 17:35:36 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191120 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-20 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006998.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Nov 20 19:34:26 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 20 Nov 2019 19:34:26 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> Hello All, The StarlingX docs team is preparing new documentation for the R3 release and we need community help. Specifically, we are looking for people to contribute content for the following topics: * New Config Guide: Certificate Configuration & Management Sub topics: * Kubernetes platform cert configs, task 37478: o REST APIs (starlingx, keystone, barbican) & Horizon o Kubernetes API Root CA o Docker Registry (Kubernetes) o Configuring a trusted CA (Kubernetes) * OpenStack app configs, task 37508: o REST APIs and Horizon Story: https://storyboard.openstack.org/#!/story/2006866 Content to go here: https://docs.starlingx.io/configuration/cert_config.html * New Config Guide: System Configuration Sub topics: * DNS servers, task 37502 * OAM Firewall, task 37504 Story: https://storyboard.openstack.org/#!/story/2006862 Content to go here: https://docs.starlingx.io/configuration/system_config.html If you have experience or content for any of these topics and can contribute (or if you know someone who has info), please contact me to coordinate. The docs team will help with the formatting/reST markup - we need your help with the content! And - we now have multiple new stub pages for specific topics added to the docs. * Configuration section (https://docs.starlingx.io/configuration/index.html) * Operation Guides section (https://docs.starlingx.io/operations/index.html) If you have experience or content for any of these topics, we would love your contribution! Cheers, Kris and the StarlingX docs team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Nov 20 20:13:22 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 20 Nov 2019 20:13:22 +0000 Subject: [Starlingx-discuss] neutron networking not working with openstack train Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F2FC4@ALA-MBD.corp.ad.wrs.com> We have discovered an issue with neutron networking with openstack train. After deploying the stx-openstack application, neutron ports are not enabled. This prevents connectivity to VMs. [sysadmin at controller-0 ~(keystone_admin)]$ openstack port list --router=tenant1-router +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ | ID | Name | MAC Address | Fixed IP Addresses | Status | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ | 103533f0-ce1b-4b99-afc9-86340a2b960a | | fa:16:3e:30:9a:73 | ip_address='192.168.113.65', subnet_id='67598367-e38f-4025-ae9c-f297ab339bfb' | DOWN | | 95d298c5-a22f-43f7-a853-d3144099235e | | fa:16:3e:4e:10:9d | ip_address='192.168.113.33', subnet_id='a90bf1c0-2685-49b8-b5ae-1547c412a1b4' | DOWN | | 9d2d676a-e788-48ea-b910-95c85f5e4037 | | fa:16:3e:af:52:f1 | ip_address='192.168.113.1', subnet_id='c782fd8c-41eb-48c3-9ac7-aa70f665351a' | DOWN | | e934d6e5-bd11-4af7-b531-70f4ef500771 | | fa:16:3e:ca:60:9d | ip_address='192.168.13.2', subnet_id='de81659f-28bd-46ef-ba8a-3eef4bdfeff9' | DOWN | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ This is tracked via: https://bugs.launchpad.net/starlingx/+bug/1841660 The following workaround can be used until a fix is merged: system helm-override-update stx-openstack neutron openstack --set conf.neutron.oslo_concurrency.lock_path=/var/run/neutron/lock Regards, Ghada From bruce.e.jones at intel.com Wed Nov 20 20:40:33 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 20 Nov 2019 20:40:33 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BED37731F@fmsmsx123.amr.corp.intel.com> Matt (and Forrest) – thank for the prompt replies! Are we looking into the Cilium project [1]? In talking to them here at the conference it looks like they have a very good solution. Brucej [1] https://cilium.io/ From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, November 20, 2019 4:09 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Hi Bruce, StarlingX container networking leverages Calico [1] as the default CNI for K8s. Calico implements Pod networking and provides an implementation for K8s Network Policies [2]. The Calico network policies gives the end-user full control over inter-pod communication by defining service level and pod level access controls for micro-segmentation of the network communication. In addition, StarlingX provides the Multus and SRIOV CNI plugins as part of the standard deployment. Together, these permit container workloads to terminate high-bandwidth network interfaces directly into a container. This configuration can be leveraged for latency sensitive applications that require raw access to network payloads. Finally, K8s networking is on an evolution path to provide higher performance Linux networking capabilities through Linux projects such as XDP [3]. XDP is starting to be leveraged by many K8s networking CNI solutions, including Calico [4]. [1] https://www.projectcalico.org/ [2] https://docs.projectcalico.org/v3.8/security/kubernetes-network-policy [3] https://www.iovisor.org/technology/xdp [4] https://www.projectcalico.org/introducing-xdp-optimized-denial-of-service-mitigation/ From: "Jones, Bruce E" > Date: Tuesday, November 19, 2019 at 9:40 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don’t know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Thu Nov 21 00:59:05 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Thu, 21 Nov 2019 00:59:05 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2019-11-20 Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A2899@ORSMSX121.amr.corp.intel.com> Hello All, Here are this week's docs team meeting minutes. Join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Cheers, Kris Current agenda and notes 2019-11-20 * All -- reviews in progress and recent merges -- ? 7 merged since last week ? 3 open: * https://review.opendev.org/#/c/693761/ - depends on failed change (TBD) * https://review.opendev.org/#/c/689847/ - * STX dist cloud. Ready for editorial (AR: Kris/Mary) * https://review.opendev.org/#/c/692202/ - First draft STX in a box, needs review (Abraham). Needs hosting of image confirmed. * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs ? Logged and resolved: https://bugs.launchpad.net/starlingx/+bug/1852840 ? https://bugs.launchpad.net/starlingx/+bug/1852352 - new - AR: Greg/Abraham, please confirm steps needed in the docs and pass back to Kris. * Please see note on bug - this may be related to Erich's abandoned review. * Kris -- Releases ? R2.0.2 EOY - Will require release notes (no impact to R3) ? R3.0 - Target release in early Dec * RC1 branch creation Nov 25 * R3 Stories: http s://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 * Starting org of new content merged: https://review.opendev.org/#/c/693601/ o Delete the sub tasks captured in new stories?? https://storyboard.openstack.org/#!/story/2006289 * R3: Target content for release: https://etherpad.openstack.org/p/stx-r3-target-content * Requested community help * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Provided initial answers to Scott Little (see previous meeting notes). Scott/Saul continuing convo offline. * TSN contribution is in progress: (subtask 36405 in https://storyboard.openstack.org/#!/story/2006289) * https://drive.google.com/file/d/1IQZVTEHRra72wNOHiIXD5Y-DKiFkl7yZ * Le, Huifeng is working on this * Misc: ? (new) Upgrade STX doc - Zhipeng Liu. * Request from community meeting to not call it "Upgrade" but instead to use "up-version" or "up-rev" - Thoughts? What about "migrate" or "update"? "How to move to a different version of StarlingX" ? http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.html * This may impact all general install instructions (making sure versions align across all needed files/packages) ? Possible guide for deploying on packet.com? (AR: Greg will explore this - Abraham will help) * https://wiki.openstack.org/wiki/StarlingX/Packet_SIG * Explore this as content for a new guide * Neat: Used StoryBoard API when GUI was having issues - more features available than in the GUI! https://docs.openstack.org/infra/storyboard/webapi/v1.html Action required (AR) summary Completed ARs are archived here: https://etherpad.openstack.org/p/stx-documentation-files-003 * -- -- * 2019-05-15 -- Abraham -- Review these code and terminology changes impacting user docs -- https://drive.google.com/file/d/1sCB-lrWhDIJLNAGWBt7wJ1_JxY21m71p -- and report back on specific actions required. * Work in progress * We took one example, the compute personality/subfunction renamed to 'worker', we find several ocurrences for both of them. * 2019-10-02 -- Kris and Mary -- Update the contributor guide at https://docs.starlingx.io/contributor/doc_contribute_guide.html to reflect our current doc schema and incorporate elements of the "cheat sheet." (low priority) * 2019-11-13 -- Greg -- https://bugs.launchpad.net/starlingx/+bug/1852352 - please confirm steps needed in the docs and pass back to Kris -------------- next part -------------- An HTML attachment was scrubbed... URL: From zheng.ma at intel.com Thu Nov 21 02:12:18 2019 From: zheng.ma at intel.com (Ma, Zheng) Date: Thu, 21 Nov 2019 02:12:18 +0000 Subject: [Starlingx-discuss] [openstack-train] Is openstack-train feature available in latest stx-build? In-Reply-To: <14973a76-8dab-fd33-e31d-252e119c6305@intel.com> References: <14973a76-8dab-fd33-e31d-252e119c6305@intel.com> Message-ID: Hi, Yong, Thanks a lot for your help! We setup with the latest helm again and recheck the version. Train version is as expected. Thanks! BR, Zheng -----Original Message----- From: Yong Hu Sent: Wednesday, November 20, 2019 4:55 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [openstack-train] Is openstack-train feature available in latest stx-build? Since 11/16, OpenStack services should be Train version. Here is some info I got from my deployment (based on Cengn build yesterday). You can see it nova's version is 20.0.2 already. --------------------------------------------------------------------- controller-0:~$ kubectl exec -it nova-conductor-55b4c68cd-cvxtd -n openstack sh sh-4.2# nova- nova-api nova-api-wsgi nova-console nova-metadata-wsgi nova-policy nova-scheduler nova-status nova-api-metadata nova-compute nova-dhcpbridge nova-network nova-rootwrap nova-serialproxy nova-xvpvncproxy nova-api-os-compute nova-conductor nova-manage nova-novncproxy nova-rootwrap-daemon nova-spicehtml5proxy sh-4.2# nova-manage version Deprecated: Option "idle_timeout" from group "database" is deprecated. Use option "connection_recycle_time" from group "database". Deprecated: Option "idle_timeout" from group "api_database" is deprecated. Use option "connection_recycle_time" from group "api_database". 20.0.2 On 2019/11/20 4:40 PM, Ma, Zheng wrote: > Hi team, > > I noticed that openstack train code merge is completed. > > But I don’t know if it is built into the latest iso. > > We have setup with latest iso [link > 119T000000Z/outputs/iso/bootimage.iso>] > and openstack tar file [link > 119T000000Z/outputs/helm-charts/helm-charts-stx-openstack-centos-stabl > e-latest.tgz>], but the openstack version is not train I think. > > We have tried to apply the “dev-latest” application with “system > application-apply” but failed on uploading stage with error info > “unsupported version” > > So could I know how to get the train-version-integrated iso or we have > to upgrade to train version ourselves? > > Thanks! > > BR, > > Zheng > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mingyuan.qi at intel.com Thu Nov 21 08:29:37 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Thu, 21 Nov 2019 08:29:37 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation In-Reply-To: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> References: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> Message-ID: Hi Kristal, I'm writing a doc for "Kubernetes QAT device plugin configuration", I believe it's under Kubernetes Operation section. I didn't find a story for this section, could you please create a story or task so that I could submit the rst for review? Mingyuan From: Dale, Kristal Sent: Thursday, November 21, 2019 3:34 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Hello All, The StarlingX docs team is preparing new documentation for the R3 release and we need community help. Specifically, we are looking for people to contribute content for the following topics: * New Config Guide: Certificate Configuration & Management Sub topics: * Kubernetes platform cert configs, task 37478: o REST APIs (starlingx, keystone, barbican) & Horizon o Kubernetes API Root CA o Docker Registry (Kubernetes) o Configuring a trusted CA (Kubernetes) * OpenStack app configs, task 37508: o REST APIs and Horizon Story: https://storyboard.openstack.org/#!/story/2006866 Content to go here: https://docs.starlingx.io/configuration/cert_config.html * New Config Guide: System Configuration Sub topics: * DNS servers, task 37502 * OAM Firewall, task 37504 Story: https://storyboard.openstack.org/#!/story/2006862 Content to go here: https://docs.starlingx.io/configuration/system_config.html If you have experience or content for any of these topics and can contribute (or if you know someone who has info), please contact me to coordinate. The docs team will help with the formatting/reST markup - we need your help with the content! And - we now have multiple new stub pages for specific topics added to the docs. * Configuration section (https://docs.starlingx.io/configuration/index.html) * Operation Guides section (https://docs.starlingx.io/operations/index.html) If you have experience or content for any of these topics, we would love your contribution! Cheers, Kris and the StarlingX docs team -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Thu Nov 21 08:55:05 2019 From: yong.hu at intel.com (Yong Hu) Date: Thu, 21 Nov 2019 16:55:05 +0800 Subject: [Starlingx-discuss] Does StarlingX support NFV? Is there any guide about operating NFV? In-Reply-To: References: Message-ID: <0ac3f877-6969-b31b-2fdf-94a876ee21e0@intel.com> StarlingX is compatible with NFV and here is a brief introduction about its VIM APIs: https://docs.starlingx.io/api-ref/stx-nfv/ As well, you can see its code at: https://opendev.org/starlingx/nfv.git On 2019/11/20 3:50 PM, 钱江 wrote: > > Hi, Community >      As I know from NFV plugtest paper, the StarlingX provides NFVI. >      But, are there any materials about how to operate NFV, for > example, deploy a VNF FG? >      I am using "Virtual All-in-one Simplex Installation R2.0 > ". >      Thanks Advance. > Best Regard > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From cristopher.j.lemus.contreras at intel.com Thu Nov 21 09:06:16 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Thu, 21 Nov 2019 03:06:16 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <029d15$5vnmki@orsmga008.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191121T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From saichandu.behara at calsoftinc.com Thu Nov 21 09:16:15 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Thu, 21 Nov 2019 14:46:15 +0530 Subject: [Starlingx-discuss] StarlingX Openstack error after changing the password - Update Message-ID: <172f79f6-580c-ca31-c579-39ddc7d8f7ce@calsoftinc.com> Hi, As we discussed yesterday call, I have raise a bug on Launchpad. I solved the issue for temporarily on my VM. Now it's working fine. Actually, VM size is getting very large. So, we are trying to reduce the image size and we are preparing the document for how to use the image. We will share the Image and Document in 2 days. By using this image, Any one/newbie can experience the How StarlingX all-in-one simplex Openstack working and It's containing StarlingX with edgex, K8s and Openstack. It's like StarlingX in a box with k8s and Openstack. Bug Launchpad Link: https://bugs.launchpad.net/starlingx/+bug/1853428 -- Thanks & Regards Sai Chandu Behara From Volker.Hoesslin at swsn.de Thu Nov 21 13:20:23 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 21 Nov 2019 13:20:23 +0000 Subject: [Starlingx-discuss] controller filesystem Message-ID: hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: Error: backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 2019-11-21 14_17_22-System Config - StarlingX.png Type: image/png Size: 29536 bytes Desc: 2019-11-21 14_17_22-System Config - StarlingX.png URL: From austin.sun at intel.com Thu Nov 21 14:20:00 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 21 Nov 2019 14:20:00 +0000 Subject: [Starlingx-discuss] controller filesystem In-Reply-To: References: Message-ID: Hi Volker: >From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. From: von Hoesslin, Volker Sent: Thursday, November 21, 2019 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: Error: backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Nov 21 15:12:56 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 21 Nov 2019 15:12:56 +0000 Subject: [Starlingx-discuss] controller filesystem In-Reply-To: References: , Message-ID: incredible !!! thats the point i have search! big thx! ________________________________ Von: Sun, Austin [austin.sun at intel.com] Gesendet: Donnerstag, 21. November 2019 15:20 An: von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io Betreff: Re: [Starlingx-discuss] controller filesystem Hi Volker: >From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. From: von Hoesslin, Volker Sent: Thursday, November 21, 2019 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: Error: backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Thu Nov 21 15:42:22 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 21 Nov 2019 15:42:22 +0000 Subject: [Starlingx-discuss] Agenda for today's StarlingX Build meeting Message-ID: FYI: We will hold a StarlingX build meeting today. Here is the proposed agenda: 1. Build layering: * Martin's commits * Status of building each layer independently? * Documentation task 2. CENGN Access: * Update on access for Saul & Bin 3. Getting ready for stx.3.0 RC1 4. Other topics? Etherpad: https://etherpad.openstack.org/p/stx-build Meeting invite: https://zoom.us/j/342730236 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Nov 21 16:57:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 21 Nov 2019 16:57:07 +0000 Subject: [Starlingx-discuss] Dev process document Message-ID: <9A85D2917C58154C960D95352B22818BED3777A5@fmsmsx123.amr.corp.intel.com> We now have a formal development process [1]. Many thanks to all the reviewers. If there are any questions or changes needed, please let me know. Once I get home I'll be updating the wiki content on processes. The content in the docs tree is canon, some of the wiki content is obsolete. Brucej [1] https://docs.starlingx.io/contributor/development_process.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Nov 21 17:11:54 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 21 Nov 2019 09:11:54 -0800 Subject: [Starlingx-discuss] controller filesystem In-Reply-To: References: Message-ID: <7acae15c-0c7d-77e7-9f27-b8156b516819@linux.intel.com> Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: > incredible !!! thats the point i have search! big thx! > ------------------------------------------------------------------------ > *Von:* Sun, Austin [austin.sun at intel.com] > *Gesendet:* Donnerstag, 21. November 2019 15:20 > *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io > *Betreff:* Re: [Starlingx-discuss] controller filesystem > > Hi Volker: > > From the email chain, > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html > > > You can probably the command line to change the size of docker lv > > Thanks. > > BR > Austin Sun. > > *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] controller filesystem > > hi, > > i trying to import some existing qcow2 images into my new installed STX 2.0. > > openstack image create --file /media/foobar.qcow2 --private > --unprotected --disk-format qcow2 "foobar" > > all works fine, the image are available. > > now, i'm trying to create an new volume based on this images. if the > images are <=6GB all works fine, but some images are very huge > (10-200GB) and then it ends in an error. after some research i can see > on controller the mount point > > /dev/mapper/cgts--vg-docker--lv      30G   11G   20G  35% /var/lib/docker > > increase the used storage. after fail "volume create" it goes back to > given value 35%. in my oppinion, this mount point should resize to some > value about 300-400GB, but how? in STX horizon backend > (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) > there is an "docker-distribution", but no docker-mount-point itself? > > btw, if i try to change the "docker-distribution" value to some other > value (eg. 500GB via horizon backend), i got this error: > > *Error: *backup size of 60 is insufficient for host controller-1. > Minimum backup size of 100 is required based upon glance size 20 and > database size 20. Rejecting modification request. > > - see attachment - > > how can i increase the backup size to handle this error?! > > greez & thx, volker... > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From maria.g.perez.ibarra at intel.com Thu Nov 21 17:18:20 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 21 Nov 2019 17:18:20 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191121 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-21 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007014.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Nov 21 20:56:33 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Nov 2019 20:56:33 +0000 Subject: [Starlingx-discuss] Plan for stx.3.0 branch creation Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F37B6@ALA-MBD.corp.ad.wrs.com> The current plan is to create the stx.3.0 release branch (r/stx.3.0) on Nov 28. This is a request to developers and core reviwers to give priority to stx.3.0 gating bugs so that as many as possible can merge before the branch creation. Once the branch is created, any bugs that are gating stx.3.0 will need to be sourced in master and cherrypicked to the release branch. A list of stx.3.0 gating bugs is available from this query: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.3.0 However, please note that security bugs related to CVEs are only visible to the security team. If you see a review for a CVE, please consider it gating for stx.3.0 even if you don't see the LP on the above list due to acccess permisisons. Thanks, Ghada From Ghada.Khalil at windriver.com Thu Nov 21 21:14:34 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Nov 2019 21:14:34 +0000 Subject: [Starlingx-discuss] neutron networking not working with openstack train In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15F2FC4@ALA-MBD.corp.ad.wrs.com> References: <151EE31B9FCCA54397A757BC674650F0C15F2FC4@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F37F5@ALA-MBD.corp.ad.wrs.com> This issue has been addressed by: https://review.opendev.org/#/c/695342/ The fix will be in tonight's cengn build. -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, November 20, 2019 3:13 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] neutron networking not working with openstack train We have discovered an issue with neutron networking with openstack train. After deploying the stx-openstack application, neutron ports are not enabled. This prevents connectivity to VMs. [sysadmin at controller-0 ~(keystone_admin)]$ openstack port list --router=tenant1-router +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ | ID | Name | MAC Address | Fixed IP Addresses | Status | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ | 103533f0-ce1b-4b99-afc9-86340a2b960a | | fa:16:3e:30:9a:73 | | ip_address='192.168.113.65', | subnet_id='67598367-e38f-4025-ae9c-f297ab339bfb' | DOWN | | 95d298c5-a22f-43f7-a853-d3144099235e | | fa:16:3e:4e:10:9d | | ip_address='192.168.113.33', | subnet_id='a90bf1c0-2685-49b8-b5ae-1547c412a1b4' | DOWN | | 9d2d676a-e788-48ea-b910-95c85f5e4037 | | fa:16:3e:af:52:f1 | | ip_address='192.168.113.1', | subnet_id='c782fd8c-41eb-48c3-9ac7-aa70f665351a' | DOWN | | e934d6e5-bd11-4af7-b531-70f4ef500771 | | fa:16:3e:ca:60:9d | | ip_address='192.168.13.2', | subnet_id='de81659f-28bd-46ef-ba8a-3eef4bdfeff9' | DOWN | +--------------------------------------+------+-------------------+-------------------------------------------------------------------------------+--------+ This is tracked via: https://bugs.launchpad.net/starlingx/+bug/1841660 The following workaround can be used until a fix is merged: system helm-override-update stx-openstack neutron openstack --set conf.neutron.oslo_concurrency.lock_path=/var/run/neutron/lock Regards, Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Greg.Waines at windriver.com Thu Nov 21 22:06:30 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 21 Nov 2019 22:06:30 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <9A85D2917C58154C960D95352B22818BED37731F@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BED37731F@fmsmsx123.amr.corp.intel.com> Message-ID: <3DFF68EA-A215-4FA1-96E0-C099C8A8B857@windriver.com> I attended their talk on: Liberating Kubernetes from kube-Proxy and iptables. My quick view (possibly inaccurate) was: * Yet another CNI, * basically built on linux's eBPF ... the evolution from iptables ... designed for higher performance, * but the performance improvement doesn’t appear to kick in until you are way over 1,000s of services, etc. * also unclear whether it has all the rich routing capabilities of Calico. ... but like I said, just a very initial view from their talk. Greg. From: "Jones, Bruce E" Date: Wednesday, November 20, 2019 at 12:42 PM To: "Peters, Matt" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Matt (and Forrest) – thank for the prompt replies! Are we looking into the Cilium project [1]? In talking to them here at the conference it looks like they have a very good solution. Brucej [1] https://cilium.io/ From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, November 20, 2019 4:09 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Hi Bruce, StarlingX container networking leverages Calico [1] as the default CNI for K8s. Calico implements Pod networking and provides an implementation for K8s Network Policies [2]. The Calico network policies gives the end-user full control over inter-pod communication by defining service level and pod level access controls for micro-segmentation of the network communication. In addition, StarlingX provides the Multus and SRIOV CNI plugins as part of the standard deployment. Together, these permit container workloads to terminate high-bandwidth network interfaces directly into a container. This configuration can be leveraged for latency sensitive applications that require raw access to network payloads. Finally, K8s networking is on an evolution path to provide higher performance Linux networking capabilities through Linux projects such as XDP [3]. XDP is starting to be leveraged by many K8s networking CNI solutions, including Calico [4]. [1] https://www.projectcalico.org/ [2] https://docs.projectcalico.org/v3.8/security/kubernetes-network-policy [3] https://www.iovisor.org/technology/xdp [4] https://www.projectcalico.org/introducing-xdp-optimized-denial-of-service-mitigation/ From: "Jones, Bruce E" > Date: Tuesday, November 19, 2019 at 9:40 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don’t know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Nov 21 22:09:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 21 Nov 2019 22:09:07 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <3DFF68EA-A215-4FA1-96E0-C099C8A8B857@windriver.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BED37731F@fmsmsx123.amr.corp.intel.com> <3DFF68EA-A215-4FA1-96E0-C099C8A8B857@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BED377D96@fmsmsx123.amr.corp.intel.com> Glad you went to the talk, Greg. Thanks for the update! Have we done any network performance tests for containers on the current StarlingX solution? Maybe we are already in good shape…. brucej From: Waines, Greg [mailto:Greg.Waines at windriver.com] Sent: Thursday, November 21, 2019 2:07 PM To: Jones, Bruce E ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I attended their talk on: Liberating Kubernetes from kube-Proxy and iptables. My quick view (possibly inaccurate) was: - Yet another CNI, - basically built on linux's eBPF ... the evolution from iptables ... designed for higher performance, - but the performance improvement doesn’t appear to kick in until you are way over 1,000s of services, etc. - also unclear whether it has all the rich routing capabilities of Calico. ... but like I said, just a very initial view from their talk. Greg. From: "Jones, Bruce E" > Date: Wednesday, November 20, 2019 at 12:42 PM To: "Peters, Matt" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Matt (and Forrest) – thank for the prompt replies! Are we looking into the Cilium project [1]? In talking to them here at the conference it looks like they have a very good solution. Brucej [1] https://cilium.io/ From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, November 20, 2019 4:09 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Hi Bruce, StarlingX container networking leverages Calico [1] as the default CNI for K8s. Calico implements Pod networking and provides an implementation for K8s Network Policies [2]. The Calico network policies gives the end-user full control over inter-pod communication by defining service level and pod level access controls for micro-segmentation of the network communication. In addition, StarlingX provides the Multus and SRIOV CNI plugins as part of the standard deployment. Together, these permit container workloads to terminate high-bandwidth network interfaces directly into a container. This configuration can be leveraged for latency sensitive applications that require raw access to network payloads. Finally, K8s networking is on an evolution path to provide higher performance Linux networking capabilities through Linux projects such as XDP [3]. XDP is starting to be leveraged by many K8s networking CNI solutions, including Calico [4]. [1] https://www.projectcalico.org/ [2] https://docs.projectcalico.org/v3.8/security/kubernetes-network-policy [3] https://www.iovisor.org/technology/xdp [4] https://www.projectcalico.org/introducing-xdp-optimized-denial-of-service-mitigation/ From: "Jones, Bruce E" > Date: Tuesday, November 19, 2019 at 9:40 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don’t know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Nov 21 22:57:06 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Nov 2019 22:57:06 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Release Meeting - Nov 21/2019 Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F38BA@ALA-MBD.corp.ad.wrs.com> Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases Release Team Meeting - November 21 2019 General Need to add VM connectivity tests to sanity serious neutron issue with openstack train not found in sanity As per Elio, team have been working on this. Action: Ada to provide forecast date stx.3.0 - milestone-3 declared last week - Release Plan https://docs.google.com/spreadsheets/d/1ZFR-9-riwhIwiBYBmWmi1qOVyHtgJ8Xk_FaF2jp5rY0/edit#gid=1010323020 - Feature Test - https://docs.google.com/spreadsheets/d/1n9P7as4iqO55DytIRuIGdyc7x0n2WM_q-cMfHcItJlY/edit#gid=968103774 - Completion Rate: 100% (up from 85%) - Re-test for GPU at 75% and QAT at 50%. Expect to complete by 11/22 - Regression Test - https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 - Completion Rate: 52% (up from 49%) << excluding openstack? - Forecast: 11/29 - Clarification from Elio: By 11/29, the manual openstack test-cases and the automated test-cases (robot & pytest) will be run - Also want to re-run another 100 manual test-cases between 11/29 & 12/13 << Is this the final regression? - It will be too late to run test-cases up to 12/13 as that is the release date. Need to bring this in to 12/6 as per the initial plan - Need Elio, Ada & Yang to look at the minimal set to be run - Request an update on this by EOD 11/22 - RC1 Branch Creation - Current date to start 11/28 - No concerns doing this over Thanksgiving. Saul agreed to look at the manifest review. - Gating Bugs - Bill will follow up with the different PLs on their plans. Would like a view from all PLs by the next community call - 11/27 - Total critical/high/medium: 79 -- https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0 Critical / High: 20 - distro.openstack: 15 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.openstack - security: 14 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.security - per Ghada, 8 CVEs in progress and expected to be merged before end of next week - config: 11 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.config - containers: 24 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers - per Frank, looking to get forecasts from the assignees - containers/networking: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.containers+stx.networking - per Ghada, expect 1 bug to be fixed. The other will likely be re-gated to stx.4.0 - networking: 5 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.networking - per Huifeng, looking at the high priority bugs now - storage: 5 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage - distcloud: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distcloud - metal: 2 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.metal - fault: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.fault - update: 1 - https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.update stx.4.0 - Feature Candidate Etherpad: - https://etherpad.openstack.org/p/stx.4.0-feature-candidates - Release Plan: - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 - Next steps - Features marked as "Propose for stx.4.0" - Ghada to copy features to the release plan spreadsheet to start tracking progress and milestones. - Project/Feature Lead to confirm intent to work on feature and resourcing - Project/Feature Lead to start identifying repos and code areas the feature will impact with an approximate size impact (S / M / L) - This is intended to help the core reviewers plan their time - Test & CI/CD initiatives - Need to determine how best to track this at the release level. - Unit test & Functional (API) tests - Agreed that each subproject team/PL needs to drive these initiatives for their domain(s) - Would like to have every PL define their targets for improvement within the stx.4.0 time-frame; measureable milestones - Bill will bring this up in the next community meeting and set expectations with the PLs - Regression Test Automation - Ask Ada to prime this - Performance Test Automation - Ask Ada to prime this - Code scans using Bandit & Coverity - Ask security team to prime and determine if there are resources to take this on From maria.g.perez.ibarra at intel.com Thu Nov 21 23:36:18 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 21 Nov 2019 23:36:18 +0000 Subject: [Starlingx-discuss] [ Regression TRAIN testing - stx3.0 ] Report for 11/21/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID="20191115T023000Z" from (link) ---------------------------------------------------------------------- MANUAL TRAIN EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 55 Pass = 39 Fail = 5 Blocked = 0 Not Run = 11 Obsolete = 1 Deferred = 0 Total executed = 44 Pass Rate = 88.6% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED TRAIN EXECUTION --------------------------------------------------------------------------- Overall Results: Total = 105 Pass = 85 Fail = 20 Blocked = 0 Obsolete = 0 Deferred = 0 Not Valid = 0 Total executed = 105 Pass Rate = 80.9% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- BUGS --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1JNln3k4b_g8_xXv-9JHwYWq-njP_OwjOrYmzKEbyPao/edit#gid=878023737 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Fri Nov 22 00:21:31 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Fri, 22 Nov 2019 00:21:31 +0000 Subject: [Starlingx-discuss] stx.4.0 Planning Message-ID: <151EE31B9FCCA54397A757BC674650F0C15F3917@ALA-MBD.corp.ad.wrs.com> As per the minutes from the release meeting today, I'm sending this out to initiate the next steps for the stx.4.0 release planning. We have a tentative set of dates that were reviewed in the PTG: Milestone-1 1/24/2020 Milestone-2 3/27/2020 Milestone-3 5/15/2020 Feature Test 5/29/2020 Regression Test TBD RC1 6/12/2020 Final Regression TBD Release 7/3/2020 And a set of candidate features: https://etherpad.openstack.org/p/stx.4.0-feature-candidates I have started a sheet for the release plan based on the above features (look at the Release Candidates tab): https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 (Features marked as Must or Propose for stx.4.0 have been included so far) I'd like to ask PLs, TLs and community members to review and help with the next steps of planning. PLs/Feature Primes, Please confirm intent to work on your features and confirm resourcing status. Use column E - Resourced (y/n) to indicate resourcing. If possible, also update column F - Status (not started, spec in progress, dev in progress, etc). Developers/Community members, If there is a feature on the release plan you want to contribute to, please reach out. There's also time to propose new features or take on one from the etherpad. Note: There is a request from TLs and core reviewers, for feature developers to identify the repos impacted by their features as well as a rough churn size (Large/Medium/Small). This will help core reviewers plan their time. Regards, Ghada (on behalf of the release planning team) From Philip_Wang at alphanetworks.com Fri Nov 22 04:01:35 2019 From: Philip_Wang at alphanetworks.com (Philip_Wang at alphanetworks.com) Date: Fri, 22 Nov 2019 04:01:35 +0000 Subject: [Starlingx-discuss] PTP slave send delay request packet fail Message-ID: Dear group, I use starlingx 2.0 to test PTP slave at AIO-SX. I check log then find error messages as below: 2019-11-21T14:38:25.000 controller-0 ptp4l: notice [77834.645] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] reconfiguring after port state change 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] selecting CLOCK_REALTIME for synchronization 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] selecting enp0s25 as the master clock 2019-11-21T14:38:53.000 controller-0 ptp4l: info [77862.895] rms 4917165483502 max 70368744178111 freq -74459 +/- 2613 delay 14401 +/- 230 2019-11-21T14:38:54.000 controller-0 phc2sys: info [77863.871] rms 2218 max 15666 freq -73519 +/- 175 delay 1669 +/- 115 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] timed out while polling for tx timestamp 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] port 1: send delay request failed 2019-11-21T14:39:06.000 controller-0 ptp4l: notice [77875.993] port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] reconfiguring after port state change 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] selecting enp0s25 for synchronization 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] nothing to synchronize Is it a driver bug?? OAM NIC is Intel I210. Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Fri Nov 22 06:44:42 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Fri, 22 Nov 2019 12:14:42 +0530 Subject: [Starlingx-discuss] StarlingX VM size getting very large Message-ID: <8c346c40-a490-0fa9-c5e8-5fd2cb0f1f89@calsoftinc.com> Hello all, We are installed Openstack on StarlingX ( It's containing EdgeX, k8s and Openstack ). After that, The VM size incresed to 145 GB. We converted to Qcow2 images and the size is 45 GB and after that, compression also, Its getting around 13 GB. So, upload and transferring is bit of tough. So, Is there any way to reduce the VM size / performing some cleanup operations. So that, The VM size is decreased something. If any one aware on this issue, Please let us know. It's a great help. -- Thanks & Regards Sai Chandu Behara From Volker.Hoesslin at swsn.de Fri Nov 22 09:16:43 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 22 Nov 2019 09:16:43 +0000 Subject: [Starlingx-discuss] ceph objects Message-ID: hi, my ceph have an health warning: [sysadmin at controller-0 ~(keystone_admin)]$ ceph -s cluster: id: 2d6cb518-420e-4a97-919a-f42b808f2049 health: HEALTH_WARN 2 pools have many more objects per pg than average services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 30 osds: 30 up, 30 in data: pools: 5 pools, 600 pgs objects: 97.12 k objects, 596 GiB usage: 1.7 TiB used, 107 TiB / 109 TiB avail pgs: 600 active+clean io: client: 25 MiB/s rd, 36 MiB/s wr, 169 op/s rd, 104 op/s wr after checkout "ceph df", i can see an huge number of objects: [sysadmin at controller-0 ~(keystone_admin)]$ ceph df GLOBAL: SIZE AVAIL RAW USED %RAW USED 109 TiB 107 TiB 1.7 TiB 1.58 POOLS: NAME ID USED %USED MAX AVAIL OBJECTS kube-rbd 1 1.5 GiB 0 33 TiB 451 images 2 437 GiB 1.28 33 TiB 55950 cinder.backups 3 0 B 0 33 TiB 0 cinder-volumes 4 151 GiB 0.45 33 TiB 39780 ephemeral 5 0 B 0 33 TiB 0 is this a normal value for round about 12 images and 8 values ? maybe there is some thrash inside this pools, how can i run an cleanup? greez & thx, volker. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 22 12:48:35 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 22 Nov 2019 12:48:35 +0000 Subject: [Starlingx-discuss] create 1000GB Volume by image Message-ID: hi, i'm trying to create an new VM volume, based on an ~200GB image. the volume should be a size of 1000GB. while creating the new volume, on controller the docker vg is growing up to round about 120GB. but after some time (i think an houre) the creating stopped and volume image switched to "error". i do not know why? how can i check details about this error? volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 22 13:46:04 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 22 Nov 2019 13:46:04 +0000 Subject: [Starlingx-discuss] create 1000GB Volume by image In-Reply-To: <79s9vu01dm39gujj@shdsegapp2> References: <79s9vu01dm39gujj@shdsegapp2> Message-ID: oh, it seems it is my fault again :( sry... after checkout the logs (huray, i found it!) i seen this line: tail /var/log/containers/cinder-volume-5cf6d84d77-5xn65_openstack_cinder-volume-699b965af5d3f4294478c86714bf35107942d1bc1fae37b77dd6d383510aea40.log {"log":"2019-11-22 12:28:55.990 17 ERROR oslo_messaging.rpc.server ImageUnacceptable: Image 8cf1d853-d09e-4342-8691-d25874b489b4 is unacceptable: Image virtual size is 2048GB and doesn't fit in a volume of size 1000GB.\n","stream":"stdout","time":"2019-11-22T12:28:56.026088581Z"} so i missed the destination volume size by 1000GB to 2048GB! currently it is running again, hope this will fix my problem! i will give you an sign if this is my fault... greez & thx, volker... ------------------------------------------------------ hi, i'm trying to create an new VM volume, based on an ~200GB image. the volume should be a size of 1000GB. while creating the new volume, on controller the docker vg is growing up to round about 120GB. but after some time (i think an houre) the creating stopped and volume image switched to "error". i do not know why? how can i check details about this error? volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Fri Nov 22 14:14:15 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Fri, 22 Nov 2019 14:14:15 +0000 Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Thu Nov 14 15:22:12 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Thu, 14 Nov 2019 15:22:12 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 11/14 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D6474CC@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Nov 14/2019 · stx.3.0 Bugs: All open issues should try with latest daily build with train patch (to confirm with Don which daily build is ok to use) * Deadline for bug resolution: End of Nov * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * High: § https://bugs.launchpad.net/starlingx/+bug/1834512 Merged https://review.opendev.org/#/c/687025 - Chenjie § https://bugs.launchpad.net/starlingx/+bug/1841189 ping to vm fails in live migration test - Gongjun · I can't reproduce this bug in the virtual machine, I am trying to reproduce this bug in Bare metal now. - § https://bugs.launchpad.net/starlingx/+bug/1841660 neutron router external gateways unreachable - YaoLe - to check offline § https://bugs.launchpad.net/starlingx/+bug/1844579 After DOR Test calico-node pods crashLoopBackoff never recovered - Joseph · Code review posted: https://review.opendev.org/#/c/692606/ * Medium: § https://bugs.launchpad.net/starlingx/+bug/1818118 Containers: vm unreachable for minutes after live migration or vm reboot - Joseph - retested with train § https://bugs.launchpad.net/starlingx/+bug/1821026 Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - fupingxie - To check the status offline § https://bugs.launchpad.net/starlingx/+bug/1833463 armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Cheng · The patch is still in review by openstack-helm community. There are several +1, but no +2 there. The community cores are not so active. I am going to ping them - if no response from the community, move to 4.0 § https://bugs.launchpad.net/starlingx/+bug/1839585 ovs-vswitchd cpu hog on cpu0 of standby controller after swact - Cheng · As no response from the bug reporter for 2 months, I sugguest to close this bug - add notes as discussed with Ghada, close the bug for now § https://bugs.launchpad.net/starlingx/+bug/1841448 compute-0 host lock failed vim_progress_status is services-disable-failed - Yaole - Check with Le offline § https://bugs.launchpad.net/starlingx/+bug/1848773 calico-kube-controllers pod sometimes moves to worker nodestx.3.0 Features / Enhancements - Joseph § https://bugs.launchpad.net/starlingx/+bug/1849221 SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon - YaoLe · The issue is solved but may be a broken functionality, need further investigation - As discussed with Matt and Ghada, ssh connection is not supported and Elio will help to refine the test case § https://bugs.launchpad.net/starlingx/+bug/1850438 The sriov device plugin pod may start before it's config manifest is written - Steven - maynot be done in 3.0, move to 4.0 if no enough time · stx 3.0 features * OVS collectd resource monitoring: Done § Prime: Chenjie § https://storyboard.openstack.org/#!/story/2002948 / https://bugs.launchpad.net/starlingx/+bug/1834512 § Merged: https://review.opendev.org/#/c/687025/:. § will discuss other features in the SB later * Openstack Rebase to Train § Can not finish final regression test in 2 week, Elio will start a mail thread to discuss the regression test plan · stx.2.0 Bugs * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.2.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * https://bugs.launchpad.net/starlingx/+bug/1835807 - Joseph, on hold - no fix in sight after extensive investigation, not neutron issue, need to decide the next step - retest with train * https://bugs.launchpad.net/starlingx/+bug/1836252 - Joseph, on hold, will be work in next 2 weeks - time out issue, fixed in train patch, close * https://bugs.launchpad.net/starlingx/+bug/1839181 - Chenjie, on hold for another reproduction where more data may be gathered. Closed after confirming with Yang that this issue is not reproducible * https://bugs.launchpad.net/starlingx/+bug/1849655 - Marvin, Still investigating the cause. As feedback from the reporter, this bug have not show up in other tests. It`s seems to be an occasional bug. · stx.4.0 Feature Proposals: * Tentative Release Milestones/Timeline: § https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 § Should aim to propose all features by milestone-1 ...which is Jan 24, 2020 § Features will also be discussed in the PTG in Shanghai: https://etherpad.openstack.org/p/stx.4.0-feature-candidates * Containerize OVS-DPDK (cheng): propose for 4.0 § https://review.opendev.org/#/c/694188 , this patch is in progress * TSN Support for container apps: to check Is this supported in the centos 4.18 kernel § TSN support in Kata container (Huifeng): propose for 4.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Nov 19 04:46:52 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 19 Nov 2019 04:46:52 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality In-Reply-To: References: Message-ID: Hi Team, Can anyone please provide any update to my Query: I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Regards Anirudh Gupta From: Anirudh Gupta Sent: 11 November 2019 14:17 To: starlingx-discuss at lists.starlingx.io Subject: StarlingX 2.0 Release Upgrade Functionality Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Tue Nov 19 07:22:06 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Tue, 19 Nov 2019 07:22:06 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 11/14 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D64813B@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Nov 14/2019 * stx.3.0 Bugs: All open issues should try with latest daily build with train patch (ISO 20191115: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006973.html) * Deadline for bug resolution: End of Nov * High: ? https://bugs.launchpad.net/starlingx/+bug/1834512 Merged https://review.opendev.org/#/c/687025 - Chenjie ? https://bugs.launchpad.net/starlingx/+bug/1841189 ping to vm fails in live migration test - Gongjun * I can't reproduce this bug in the virtual machine, I am trying to reproduce this bug in Bare metal now. - ? https://bugs.launchpad.net/starlingx/+bug/1841660 neutron router external gateways unreachable - YaoLe - to check offline ? https://bugs.launchpad.net/starlingx/+bug/1844579 After DOR Test calico-node pods crashLoopBackoff never recovered - Joseph * Code review posted: https://review.opendev.org/#/c/692606/ * Medium: ? https://bugs.launchpad.net/starlingx/+bug/1818118 Containers: vm unreachable for minutes after live migration or vm reboot - Joseph - retested with train ? https://bugs.launchpad.net/starlingx/+bug/1821026 Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - fupingxie - To check the status offline ? https://bugs.launchpad.net/starlingx/+bug/1833463 armada-manifest upload failed when configuring bond with OVS container (vswitch-type=none) - Cheng * The patch is still in review by openstack-helm community. There are several +1, but no +2 there. The community cores are not so active. I am going to ping them - if no response from the community, move to 4.0 ? https://bugs.launchpad.net/starlingx/+bug/1839585 ovs-vswitchd cpu hog on cpu0 of standby controller after swact - Cheng * As no response from the bug reporter for 2 months, I sugguest to close this bug - add notes as discussed with Ghada, close the bug for now ? https://bugs.launchpad.net/starlingx/+bug/1841448 compute-0 host lock failed vim_progress_status is services-disable-failed - Yaole - Check with Le offline ? https://bugs.launchpad.net/starlingx/+bug/1848773 calico-kube-controllers pod sometimes moves to worker nodestx.3.0 Features / Enhancements - Joseph ? https://bugs.launchpad.net/starlingx/+bug/1849221 SSH / SCP to VM failed using NAMESPACE while IP is assigned by Horizon - YaoLe * The issue is solved but may be a broken functionality, need further investigation - As discussed with Matt and Ghada, ssh connection is not supported and Elio will help to refine the test case ? https://bugs.launchpad.net/starlingx/+bug/1850438 The sriov device plugin pod may start before it's config manifest is written - Steven - maynot be done in 3.0, move to 4.0 if no enough time * stx 3.0 features * OVS collectd resource monitoring: Done ? Prime: Chenjie ? https://storyboard.openstack.org/#!/story/2002948 / https://bugs.launchpad.net/starlingx/+bug/1834512 ? Merged: https://review.opendev.org/#/c/687025/:. ? will discuss other features in the SB later * Openstack Rebase to Train ? Cannot finish final regression test in 2 week, Elio will start a mail thread to discuss the regression test plan * stx.2.0 Bugs * https://bugs.launchpad.net/starlingx/+bug/1835807 - Joseph, on hold - no fix in sight after extensive investigation, not neutron issue, need to decide the next step - retest with train * https://bugs.launchpad.net/starlingx/+bug/1836252 - Joseph, on hold, will be work in next 2 weeks - time out issue, fixed in train patch, close * https://bugs.launchpad.net/starlingx/+bug/1839181 - Chenjie, on hold for another reproduction where more data may be gathered. Closed after confirming with Yang that this issue is not reproducible * https://bugs.launchpad.net/starlingx/+bug/1849655 - Marvin, Still investigating the cause. As feedback from the reporter, this bug have not show up in other tests. It`s seems to be an occasional bug. * stx.4.0 Feature Proposals: * Tentative Release Milestones/Timeline: ? https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0 ? Should aim to propose all features by milestone-1 ...which is Jan 24, 2020 ? Features will also be discussed in the PTG in Shanghai: https://etherpad.openstack.org/p/stx.4.0-feature-candidates * Containerize OVS-DPDK (cheng): propose for 4.0 ? https://review.opendev.org/#/c/694188 , this patch is in progress * TSN Support for container apps: to check Is this supported in the centos 4.18 kernel ? TSN support in Kata container (Huifeng): propose for 4.0 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Nov 19 10:06:54 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 19 Nov 2019 10:06:54 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: Hi Team, I have installed StarlingX 2.0 Duplex Bare Metal. I am trying to create 2 VM's and repeating this cycle a number of times. After using the setup for around half and hour, I am not longer able to access the GUI. Ever though I type correct Username/Password, it gives an error of Invalid Credentials. Then, I thought to use the CLI commands by following LOAD CLI section given in link https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#local-cli But with this also, I am facing the same error controller-0:~$ export OS_CLOUD=openstack_helm controller-0:~$ openstack endpoint list The account is locked for user: 230578cde382430a8adac399afab1230. (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) Earlier this automatically started working after 5-7 mins. But this time, I am completely Blocked. I have also raised a bug regarding the same https://bugs.launchpad.net/starlingx/+bug/1853093 Please suggest some pointers, so that I can unblock and resume my activities. Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Thu Nov 21 08:40:01 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Thu, 21 Nov 2019 08:40:01 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks Bill for your response. Without taking into account ZTD, Does Stx provides stx-openstack* application which can be used on Stx 2.0 deployment to upgrade it from Stein to Train release? Regards Anirudh Gupta From: Zvonar, Bill Sent: 20 November 2019 19:27 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io Subject: RE: StarlingX 2.0 Release Upgrade Functionality Hi Anirudh, don't know if you got an answer directly, but this is not supported. Bill... From: Anirudh Gupta > Sent: Monday, November 11, 2019 3:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Fri Nov 22 15:41:17 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Fri, 22 Nov 2019 15:41:17 +0000 Subject: [Starlingx-discuss] Weekly StarlingX Test meeting - 9:00 Pacific time Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A30D2964A@FMSMSX125.amr.corp.intel.com> When: Tuesday, November 26, 2019 11:00 AM-12:00 PM. (UTC-06:00) Guadalajara, Mexico City, Monterrey *~*~*~*~*~*~*~*~*~* Weekly meetings on Tuesdays at 9am Pacific · Zoom link: https://zoom.us/j/342730236 · Dialing in from phone: · Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 · Meeting ID: 342 730 236 · International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes: https://etherpad.openstack.org/p/stx-test -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2052 bytes Desc: not available URL: From Gerry.Kopec at windriver.com Fri Nov 22 20:01:41 2019 From: Gerry.Kopec at windriver.com (Kopec, Gerald (Gerry)) Date: Fri, 22 Nov 2019 20:01:41 +0000 Subject: [Starlingx-discuss] PTP slave send delay request packet fail In-Reply-To: References: Message-ID: <58CF5BABC9A76946A638A0E8AE48D1737891AC31@ALA-MBD.corp.ad.wrs.com> I was seeing that error occasionally on different nics at steady state. In the cases I saw, ptp4l would recover within about a minute. I did push a fix to starlingx 3.0 to increase tx_timestamp_timeout which seems to have stopped the issue from happening in my setups. https://review.opendev.org/#/c/691113/ Of course, it was a bit unpredictable so it's hard to be sure it's completely gone. Gerry From: Philip_Wang at alphanetworks.com [mailto:Philip_Wang at alphanetworks.com] Sent: Thursday, November 21, 2019 11:02 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] PTP slave send delay request packet fail Dear group, I use starlingx 2.0 to test PTP slave at AIO-SX. I check log then find error messages as below: 2019-11-21T14:38:25.000 controller-0 ptp4l: notice [77834.645] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] reconfiguring after port state change 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] selecting CLOCK_REALTIME for synchronization 2019-11-21T14:38:25.000 controller-0 phc2sys: info [77834.868] selecting enp0s25 as the master clock 2019-11-21T14:38:53.000 controller-0 ptp4l: info [77862.895] rms 4917165483502 max 70368744178111 freq -74459 +/- 2613 delay 14401 +/- 230 2019-11-21T14:38:54.000 controller-0 phc2sys: info [77863.871] rms 2218 max 15666 freq -73519 +/- 175 delay 1669 +/- 115 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] timed out while polling for tx timestamp 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug 2019-11-21T14:39:06.000 controller-0 ptp4l: err [77875.993] port 1: send delay request failed 2019-11-21T14:39:06.000 controller-0 ptp4l: notice [77875.993] port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED) 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] port 0015b2.fffe.a92e24-1 changed state 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] reconfiguring after port state change 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] selecting enp0s25 for synchronization 2019-11-21T14:39:07.000 controller-0 phc2sys: info [77876.872] nothing to synchronize Is it a driver bug?? OAM NIC is Intel I210. Best Reagrds, - Philip Wang --- Alpha Networks Inc. TEL: 886-3-5636666 EXT:6403 This electronic mail transmission is intended only for the named recipient. It contains information which may be privileged,confidential and exempt from disclosure under applicable law. Dissemination, distribution, or copying of this communication by anyone other than the recipient or the recipient's agent is strictly prohibited. If this electronic mail transmission is received in error, Please notify us immediately and delete the message and all attachments of it from your computer system. Thank you for your cooperation. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.ning at windriver.com Fri Nov 22 20:59:50 2019 From: andy.ning at windriver.com (Andy Ning) Date: Fri, 22 Nov 2019 15:59:50 -0500 Subject: [Starlingx-discuss] [docs][distcloud] docker registry certificate need to have "registry.local" in SAN list Message-ID: Hi, With change https://review.opendev.org/#/c/695308/, new docker registry certificate to be installed in subcloud need to have "registry.local" in the certificate's SAN DNS name list, including docker registry certificate installed in Central Cloud and get synced to Subcloud. Thanks, Andy Ning From maria.g.perez.ibarra at intel.com Fri Nov 22 22:09:51 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 22 Nov 2019 22:09:51 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191122 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-22 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Mon Nov 25 01:23:20 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 25 Nov 2019 01:23:20 +0000 Subject: [Starlingx-discuss] ceph objects Message-ID: <56829C2A36C2E542B0CCB9854828E4D8562815D1@CDSMSX102.ccr.corp.intel.com> Hi Von This is incorrect ceph conf setting for openstack. http://tkannadhasan.blogspot.com/2018/04/ceph-pool-rbd-has-many-more-objects-per.html https://bugs.launchpad.net/charm-ceph-mon/+bug/1804846 1, you can google to find ceph command to update this config item, "mon pg warn max object skew" 2, Or submit a launchpad issue, maybe we should update ceph config item, to change puppet setting in starlingx for ceph. BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Friday, November 22, 2019 8:30 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 139 Send Starlingx-discuss mailing list submissions to starlingx-discuss at 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 at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. StarlingX VM size getting very large (Saichandu Behara) 2. ceph objects (von Hoesslin, Volker) ---------------------------------------------------------------------- Message: 1 Date: Fri, 22 Nov 2019 12:14:42 +0530 From: Saichandu Behara To: "starlingx-discuss at lists.starlingx.io" Cc: Pavan Gupta Subject: [Starlingx-discuss] StarlingX VM size getting very large Message-ID: <8c346c40-a490-0fa9-c5e8-5fd2cb0f1f89 at calsoftinc.com> Content-Type: text/plain; charset=utf-8; format=flowed Hello all, We are installed Openstack on StarlingX ( It's containing EdgeX, k8s and Openstack ). After that, The VM size incresed to 145 GB. We converted to Qcow2 images and the size is 45 GB and after that, compression also, Its getting around 13 GB. So, upload and transferring is bit of tough. So, Is there any way to reduce the VM size / performing some cleanup operations. So that, The VM size is decreased something. If any one aware on this issue, Please let us know. It's a great help. -- Thanks & Regards Sai Chandu Behara ------------------------------ Message: 2 Date: Fri, 22 Nov 2019 09:16:43 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] ceph objects Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, my ceph have an health warning: [sysadmin at controller-0 ~(keystone_admin)]$ ceph -s cluster: id: 2d6cb518-420e-4a97-919a-f42b808f2049 health: HEALTH_WARN 2 pools have many more objects per pg than average services: mon: 3 daemons, quorum controller-0,controller-1,storage-0 mgr: controller-0(active), standbys: controller-1 osd: 30 osds: 30 up, 30 in data: pools: 5 pools, 600 pgs objects: 97.12 k objects, 596 GiB usage: 1.7 TiB used, 107 TiB / 109 TiB avail pgs: 600 active+clean io: client: 25 MiB/s rd, 36 MiB/s wr, 169 op/s rd, 104 op/s wr after checkout "ceph df", i can see an huge number of objects: [sysadmin at controller-0 ~(keystone_admin)]$ ceph df GLOBAL: SIZE AVAIL RAW USED %RAW USED 109 TiB 107 TiB 1.7 TiB 1.58 POOLS: NAME ID USED %USED MAX AVAIL OBJECTS kube-rbd 1 1.5 GiB 0 33 TiB 451 images 2 437 GiB 1.28 33 TiB 55950 cinder.backups 3 0 B 0 33 TiB 0 cinder-volumes 4 151 GiB 0.45 33 TiB 39780 ephemeral 5 0 B 0 33 TiB 0 is this a normal value for round about 12 images and 8 values ? maybe there is some thrash inside this pools, how can i run an cleanup? greez & thx, volker. -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 139 ************************************************** From bin.yang at intel.com Mon Nov 25 02:11:36 2019 From: bin.yang at intel.com (Yang, Bin) Date: Mon, 25 Nov 2019 02:11:36 +0000 Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question In-Reply-To: <9A85D2917C58154C960D95352B22818BED377D96@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BED376DDA@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BED37731F@fmsmsx123.amr.corp.intel.com> <3DFF68EA-A215-4FA1-96E0-C099C8A8B857@windriver.com> <9A85D2917C58154C960D95352B22818BED377D96@fmsmsx123.amr.corp.intel.com> Message-ID: Except for the k8s network performance enhancement, do we plan to connect the network between VM and containers? e.g. like kuryr [1] to run both openstack VMs and K8S pods on the same Neutron network. [1]: https://github.com/openstack/kuryr-kubernetes Thanks, Bin From: Jones, Bruce E Sent: Friday, November 22, 2019 06:09 To: Waines, Greg ; Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Glad you went to the talk, Greg. Thanks for the update! Have we done any network performance tests for containers on the current StarlingX solution? Maybe we are already in good shape…. brucej From: Waines, Greg [mailto:Greg.Waines at windriver.com] Sent: Thursday, November 21, 2019 2:07 PM To: Jones, Bruce E >; Peters, Matt >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I attended their talk on: Liberating Kubernetes from kube-Proxy and iptables. My quick view (possibly inaccurate) was: * Yet another CNI, * basically built on linux's eBPF ... the evolution from iptables ... designed for higher performance, * but the performance improvement doesn’t appear to kick in until you are way over 1,000s of services, etc. * also unclear whether it has all the rich routing capabilities of Calico. ... but like I said, just a very initial view from their talk. Greg. From: "Jones, Bruce E" > Date: Wednesday, November 20, 2019 at 12:42 PM To: "Peters, Matt" >, "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Matt (and Forrest) – thank for the prompt replies! Are we looking into the Cilium project [1]? In talking to them here at the conference it looks like they have a very good solution. Brucej [1] https://cilium.io/ From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: Wednesday, November 20, 2019 4:09 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question Hi Bruce, StarlingX container networking leverages Calico [1] as the default CNI for K8s. Calico implements Pod networking and provides an implementation for K8s Network Policies [2]. The Calico network policies gives the end-user full control over inter-pod communication by defining service level and pod level access controls for micro-segmentation of the network communication. In addition, StarlingX provides the Multus and SRIOV CNI plugins as part of the standard deployment. Together, these permit container workloads to terminate high-bandwidth network interfaces directly into a container. This configuration can be leveraged for latency sensitive applications that require raw access to network payloads. Finally, K8s networking is on an evolution path to provide higher performance Linux networking capabilities through Linux projects such as XDP [3]. XDP is starting to be leveraged by many K8s networking CNI solutions, including Calico [4]. [1] https://www.projectcalico.org/ [2] https://docs.projectcalico.org/v3.8/security/kubernetes-network-policy [3] https://www.iovisor.org/technology/xdp [4] https://www.projectcalico.org/introducing-xdp-optimized-denial-of-service-mitigation/ From: "Jones, Bruce E" > Date: Tuesday, November 19, 2019 at 9:40 PM To: "starlingx-discuss at lists.starlingx.io" > Subject: [Starlingx-discuss] [Networking] StarlingX vs K8S networking question I am at Kubecon this week and met with a potential partner who is interested in StarlingX. He is very concerned about networking in off-the-shelf Kubernetes and is hopeful that StarlingX has addressed the issues. I don’t know enough about Networking to answer his questions. In particular, the partner is concerned about how IP addresses are assigned to nodes and thus to pods, and is very concerned about network data path performance in K8S. He believes that the default model of “everyone can see everything” is not acceptable for enterprises where isolation of applications is important. If someone who knows StarlingX networking could send me a write up on how StarlingX improves on K8S networking, that would be very helpful for me in further discussions with the potential partner. Thank you! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Mon Nov 25 05:00:19 2019 From: yong.hu at intel.com (Yong Hu) Date: Mon, 25 Nov 2019 13:00:19 +0800 Subject: [Starlingx-discuss] StarlingX 2.0 Account Locked for User In-Reply-To: References: Message-ID: Hi Anirudh, This issue is similar to this LP#1853017 [0], which was triggered the account locking if the password of Openstack user "admin" was changed. In this LP, for unknown reason, "registry-token-server" daemon kept accessing "keystone" on host (not the instance in containers) with obsolete token and led to "admin" account locked after 5 attempts. Right now, I am debugging this issue. Good thing is Cengn build 11/16 seemed not to have such a problem (LP#1853017). You might have a try with this version? BTW: which cengn build were you using? [0] https://bugs.launchpad.net/starlingx/+bug/1853017 regards, Yong On 2019/11/19 6:06 PM, Anirudh Gupta wrote: > Hi Team, > > I have installed StarlingX 2.0 Duplex Bare Metal. > > I am trying to create 2 VM’s and repeating this cycle a number of times. > > After using the setup for around half and hour, I am not longer able to > access the GUI. > > Ever though I type correct Username/Password, it gives an error of > Invalid Credentials. > > Then, I thought to use the CLI commands by following LOAD CLI section > given in link > > https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#local-cli > > But with this also, I am facing the same error > > controller-0:~$ export OS_CLOUD=openstack_helm > > controller-0:~$ openstack endpoint list > > The account is locked for user: 230578cde382430a8adac399afab1230. (HTTP > 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) > > Earlier this automatically started working after 5-7 mins. > > But this time, I am completely Blocked. > > I have also raised a bug regarding the same > > https://bugs.launchpad.net/starlingx/+bug/1853093 > > Please suggest some pointers, so that I can unblock and resume my > activities. > > Regards > > Anirudh Gupta > > 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. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From mingyuan.qi at intel.com Mon Nov 25 08:08:27 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Mon, 25 Nov 2019 08:08:27 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation In-Reply-To: References: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> Message-ID: Hi Kristal, I've created a task in the qat device plugin SB[0] to add the doc and submitted a commit[1] for docs team review. [0] https://storyboard.openstack.org/#!/story/2005514 [1] https://review.opendev.org/#/c/695849/ Mingyuan From: Qi, Mingyuan Sent: Thursday, November 21, 2019 16:30 To: Dale, Kristal ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Hi Kristal, I'm writing a doc for "Kubernetes QAT device plugin configuration", I believe it's under Kubernetes Operation section. I didn't find a story for this section, could you please create a story or task so that I could submit the rst for review? Mingyuan From: Dale, Kristal > Sent: Thursday, November 21, 2019 3:34 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Hello All, The StarlingX docs team is preparing new documentation for the R3 release and we need community help. Specifically, we are looking for people to contribute content for the following topics: * New Config Guide: Certificate Configuration & Management Sub topics: * Kubernetes platform cert configs, task 37478: o REST APIs (starlingx, keystone, barbican) & Horizon o Kubernetes API Root CA o Docker Registry (Kubernetes) o Configuring a trusted CA (Kubernetes) * OpenStack app configs, task 37508: o REST APIs and Horizon Story: https://storyboard.openstack.org/#!/story/2006866 Content to go here: https://docs.starlingx.io/configuration/cert_config.html * New Config Guide: System Configuration Sub topics: * DNS servers, task 37502 * OAM Firewall, task 37504 Story: https://storyboard.openstack.org/#!/story/2006862 Content to go here: https://docs.starlingx.io/configuration/system_config.html If you have experience or content for any of these topics and can contribute (or if you know someone who has info), please contact me to coordinate. The docs team will help with the formatting/reST markup - we need your help with the content! And - we now have multiple new stub pages for specific topics added to the docs. * Configuration section (https://docs.starlingx.io/configuration/index.html) * Operation Guides section (https://docs.starlingx.io/operations/index.html) If you have experience or content for any of these topics, we would love your contribution! Cheers, Kris and the StarlingX docs team -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Nov 25 09:00:01 2019 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 25 Nov 2019 09:00:01 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Gupta: >From your log, it seems gnocchi is still searching local endpoint. Would you like run "gnocchi -endpoint " ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mingyuan.qi at intel.com Mon Nov 25 10:51:13 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Mon, 25 Nov 2019 10:51:13 +0000 Subject: [Starlingx-discuss] [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Anirudh, I don't think the gnocchi client got the right api url(localhost:8041), if you check the openstack endpoints, gnocchi internal interface should be http://gnocchi-api.openstack.svc.cluster.local:8041/ Could you check the openstack client for gnocchi which is "openstack metric list/openstack metric resource list ", to verify that gnocchi is in-service? Mingyuan From: Sun, Austin Sent: Monday, November 25, 2019 17:00 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: Re: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: >From your log, it seems gnocchi is still searching local endpoint. Would you like run "gnocchi -endpoint " ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Mon Nov 25 13:14:44 2019 From: austin.sun at intel.com (Sun, Austin) Date: Mon, 25 Nov 2019 13:14:44 +0000 Subject: [Starlingx-discuss] [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Gupta: >From reference[1], cpu_util is deprecated from openstack stein version which is stx.2.0 using. [1] https://github.com/openstack/ceilometer/blob/4ae919c96e4116ab83e5d83f2b726ed44d165278/releasenotes/notes/save-rate-in-gnocchi-66244262bc4b7842.yaml Thanks. BR Austin Sun. From: Anirudh Gupta Sent: Monday, November 25, 2019 6:55 PM To: Qi, Mingyuan ; Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Mingyuan, Thanks for your response. I am able to access it using "openstack metric list/openstack metric resource list ". There is no "cpu_util" metric available in the list. How can I enable that parameter in StarlingX 2.0? Regards Anirudh Gupta From: Qi, Mingyuan > Sent: 25 November 2019 16:21 To: Sun, Austin >; Anirudh Gupta >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Anirudh, I don't think the gnocchi client got the right api url(localhost:8041), if you check the openstack endpoints, gnocchi internal interface should be http://gnocchi-api.openstack.svc.cluster.local:8041/ Could you check the openstack client for gnocchi which is "openstack metric list/openstack metric resource list ", to verify that gnocchi is in-service? Mingyuan From: Sun, Austin > Sent: Monday, November 25, 2019 17:00 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: Re: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: >From your log, it seems gnocchi is still searching local endpoint. Would you like run "gnocchi -endpoint " ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Nov 25 13:26:31 2019 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 25 Nov 2019 13:26:31 +0000 Subject: [Starlingx-discuss] controller filesystem In-Reply-To: <7acae15c-0c7d-77e7-9f27-b8156b516819@linux.intel.com> References: <7acae15c-0c7d-77e7-9f27-b8156b516819@linux.intel.com> Message-ID: Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ji at sibyl.li Mon Nov 25 13:53:31 2019 From: ji at sibyl.li (joji vlogs) Date: Mon, 25 Nov 2019 07:53:31 -0600 Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy.ning at windriver.com Mon Nov 25 16:05:19 2019 From: andy.ning at windriver.com (Andy Ning) Date: Mon, 25 Nov 2019 11:05:19 -0500 Subject: [Starlingx-discuss] StarlingX 2.0 Account Locked for User In-Reply-To: References: Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad@windriver.com> On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> 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. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr From juan.carlos.alonso at intel.com Mon Nov 25 16:13:09 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 25 Nov 2019 16:13:09 +0000 Subject: [Starlingx-discuss] How to edit /etc/nova/nova.conf? Message-ID: Hello, I want to edit /etc/nova/nova.conf on nova-compute pods. I want to enable debug on it: [DEFUALT] debug = true ... Then, I want to write: ... [libvirt] cpu-mode = custom cpu_models = SandyBridge,IvyBridge,Haswell,Broadwell ... I was trying to use system helm-override-update command, but it is not working. Do you know the correct way to edit /etc/nova/nova.conf? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Mon Nov 25 20:02:57 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Mon, 25 Nov 2019 20:02:57 +0000 Subject: [Starlingx-discuss] StarlingX Containerization Meeting Message-ID: Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): o https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] o https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): o Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] o Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? o 2006770: Backup & Restore - openstack [Ovidiu Poncea] o 2005312: Containerize Openstack clients o 2004008: Fault Containerization o TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4288 bytes Desc: not available URL: From Jerry.Sun at windriver.com Mon Nov 25 20:52:44 2019 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Mon, 25 Nov 2019 20:52:44 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Account Locked for User In-Reply-To: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad@windriver.com> References: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad@windriver.com> Message-ID: Hi All, Looking at the tarball for the logs attached by Peng, it looks like after the password was changed in bash.log, there is no more activity from registry-token-server in daemon.log. This leads me to believe that something else must be triggering the locking of the account. There are some activity from token server in daemon.log but that was before the password change. I also tried authenticating to the token server with incorrect credentials on a system without changing the password. This is to try and create an environment where the registry/token server holds incorrect keystone credentials. The admin account did not get locked which means token server does not spam requests at keystone with incorrect credentials until it locks. Thanks, Jerry -----Original Message----- From: Andy Ning Sent: Monday, November 25, 2019 11:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> 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. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Ghada.Khalil at windriver.com Mon Nov 25 23:05:20 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 25 Nov 2019 23:05:20 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0C15FD011@ALA-MBD.corp.ad.wrs.com> Hi Anirudh, We are in the planning phase for stx.4.0 and are looking for developers from the community to look at implementing openstack upgrades with minimal down time. If this is something your team is interested in taking on, I invite you to participate in the distro.openstack meeting to discuss next steps. Thanks, Ghada From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, November 20, 2019 8:57 AM To: Anirudh Gupta; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Anirudh, don't know if you got an answer directly, but this is not supported. Bill... From: Anirudh Gupta > Sent: Monday, November 11, 2019 3:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Mon Nov 25 23:38:03 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Mon, 25 Nov 2019 23:38:03 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191125 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-25 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 ] =========================================== Sanity Test is executed in a Containers - 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 - 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 ] ----------------------------------------------------------------------------------- External Bare Metal and Standar virtual were not executed due to internal infrastructure problems. regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Tue Nov 26 01:24:43 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Tue, 26 Nov 2019 01:24:43 +0000 Subject: [Starlingx-discuss] How to edit /etc/nova/nova.conf? In-Reply-To: References: Message-ID: <93814834B4855241994F290E959305C7530F85FE@SHSMSX104.ccr.corp.intel.com> Hi JC, You can try below System helm-override-update nova openstack --set conf.nova.DEFAULT.debug=true System application-apply stx-openstack. Zhipeng From: Alonso, Juan Carlos Sent: 2019年11月26日 0:13 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] How to edit /etc/nova/nova.conf? Hello, I want to edit /etc/nova/nova.conf on nova-compute pods. I want to enable debug on it: [DEFUALT] debug = true … Then, I want to write: … [libvirt] cpu-mode = custom cpu_models = SandyBridge,IvyBridge,Haswell,Broadwell ... I was trying to use system helm-override-update command, but it is not working. Do you know the correct way to edit /etc/nova/nova.conf? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From ran1.an at intel.com Tue Nov 26 02:18:33 2019 From: ran1.an at intel.com (An, Ran1) Date: Tue, 26 Nov 2019 02:18:33 +0000 Subject: [Starlingx-discuss] summary of discussions in China StarlingX WeChat Group (WW46-WW47) Message-ID: <9BAB5B7CAF57C3459E4636391F1071CE05350C92@shsmsx102.ccr.corp.intel.com> So glad to see there are 11 more developers join us, and now there are 146 members in the China StarlingX WeChat. Welcome! These topics were discussed in last two weeks: Knowledge share: 1. Workshop: How-To upgrade OpenStack in StarlingX (shared by @Liu, ZhipengS) 2. Hands-on: another starlingx docker images registry for Chinese contributor (share by 张鲲鹏 ) Deploy problems (all solved in the WeChat group): None Questions: 1. what’s the password of official ubuntu vm image? (answered, could use libguestfs-tools to edit passwords.) Thanks for your attention Ran From: An, Ran1 Sent: Friday, November 8, 2019 8:50 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss]summary of discussions in China StarlingX WeChat Group Hi all: The China StarlingX WeChat group was created during the StarlingX 2.0 Meetup (Beijing) on 24th Sept. Currently there are 135 members from Intel, 99cloud, WindRiver, China Unicom, China Telecom, Fiberhome, ZTE and other companies. (Maybe someone from China Mobile) The hottest topic in the WeChat group is about deployment. The discussions covered all versions of starlingX (stx1.0, stx 2.0 and master branch). Customer configuration is also frequently discussed/asked there. Other topics such as openstack domain name (service name), bluestore of ceph, raid card supported were mentioned. In addition, we are glad to see some contributors share their experiences in the group, like: 1. an offline deployment tutorial of stx 2.0[1] from KunpengZhang at 99cloud. 2. an docker registry for Chinese users is built by bin.yang at intel and contributors from Neusoft. The tutorial can be got from [2] Specifically, these topics were discussed in the past week: Deploy problems (all solved in the WeChat group): 1. some pods kept on pending status (from ZTE, version 2.0) Solution: the Kubernetes worker node on compute nodes were not ready, solved by adding network for compute node manually. 2. ansible processing was blocked at docker images download stage. (master branch) Solution: local registry did not take effect. Format of ansible file was incorrect (there are codes changes recently). 3. some pods of openstack failed to start for the request resource was larger than default limitation. (version 2.0) Solution: use cmd "system helm-override-update modify pod.resources. XXX" Questions: 1. does starlingX support real time kernel? (answered, yes) 2. how to transfer instances from old system to new one. (answered, use snapshot) 3. is there an efficient way to check the system status and find the key point during deployment processing. (request a proper answer) [1] https://github.com/zhangkunpeng/starlingx/blob/master/host-unlock/stx-2.0/deployment.md [2] https://pan.baidu.com/s/1EEk6j17NC8uc5zhKzW-hlw fetch code: t2ix Thanks for your attention Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Tue Nov 26 09:19:22 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Tue, 26 Nov 2019 03:19:22 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$74o0ok@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191126T000000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From ezpeerchen at gmail.com Tue Nov 26 10:01:32 2019 From: ezpeerchen at gmail.com (Ezpeer Chen) Date: Tue, 26 Nov 2019 18:01:32 +0800 Subject: [Starlingx-discuss] StarlingX support dpdk with VPP ? Message-ID: Dear all, How could i configure StarlingX to enable dpdk + VPP (Vector Packet Processing) ? Or It is not supported now ? Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From saichandu.behara at calsoftinc.com Tue Nov 26 11:33:05 2019 From: saichandu.behara at calsoftinc.com (Saichandu Behara) Date: Tue, 26 Nov 2019 17:03:05 +0530 Subject: [Starlingx-discuss] Calsoft's Contribution- StarlingX simplex All-in-one Openstack Deployment Message-ID: <6a578ed9-2090-4891-1078-5f44323e7976@calsoftinc.com> Hello all, We are ready with one more contribution. The deployment of Openstack in StarlingX all-in-one Simplex is done successfully. It is containing StarlingX with k8s, EdgeX and Openstack. But we faced some challenges during whole process. Thus, to ease the process for a newbie, we have created ready-to-use qcow2 images. One can simply use this image to deploy the VM /(containing StarlingX with //K8//S, EdgeX//and Openstack)/. Below are the links for StarlingX_all-in-one_Edgex_with_Openstack setup Document and Image link. Setup Document: https://drive.google.com/open?id=110kbsRoBFZQ3J99hobu0QGxC_xchYwKk Image: https://drive.google.com/open?id=14jxBWnB5ydCk2sf_jc7I2B_e0aTC-rc6 Please let us know where can we upload these images and documents -- Thanks & Regards Sai Chandu Behara -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Nov 26 13:16:33 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 26 Nov 2019 13:16:33 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/27/2019 Message-ID: Hi All: Agenda for 11/27 meeting: * stx.4.0 feature - Standardize Flock Package Versioning (Yang Bin) - Ceph containerization update (Tingjie/martin) - CentOS 8.0 upgrade planning (Shuai Zhao) - Kata Container (Shuicheng) * stx 3.0 bugs fix - CVE issue tracking (Shuicheng) * OVMF * libX11 * kernel change upgrade 1062 - Storage issue tracking (Tingjie) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage - Others issue tracking (Austin) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.other *Opens(All) Update the agenda if other topic to be discussed : https://etherpad.openstack.org/p/stx-distro-other Thanks. BR Austin Sun. From yong.hu at intel.com Tue Nov 26 13:31:23 2019 From: yong.hu at intel.com (Yong Hu) Date: Tue, 26 Nov 2019 21:31:23 +0800 Subject: [Starlingx-discuss] [stx.distro.openstack] call for action: update the LP for incoming Stx.3.0 RC1 Message-ID: <2d0f93ab-7ef9-4173-c67a-0a9fbe100811@intel.com> Hi community friends, As we are approaching StarlingX 3.0 RC1 day by day, you will be much appreciated if you can timely make the updates (such as follow-up actions, debugging progress, or/and estimation of resolving the issue) on those LPs under your name. FYI: distro.openstack LP query: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.distro.openstack Should you have any questions or concerns, please also make feedback inside. thanks in advance! regards, Yong From Frank.Miller at windriver.com Tue Nov 26 15:37:09 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Tue, 26 Nov 2019 15:37:09 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Message-ID: Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: o 4 LPs are expected to land for stx.3.0 including the 2 Highs o 2 LPs to be marked invalid/not reproducible o 11 LPs to be re-gated to stx.4.0 o 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * 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 << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Tue Nov 26 17:48:09 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 26 Nov 2019 17:48:09 +0000 Subject: [Starlingx-discuss] [ Test ] meeting notes for 11/26 Message-ID: Agenda for 11/26 Attendees: JoseP, Bruce, JC, Richo, Cris, Fernado, Yang 1. Sanity status - Green since last week, today is green as well - No critical bugs found recently - Yang - Today's seems to be green, still waiting for multinode results 2. stx.3.0 testing updates - SRIOV Status --> Not started yet, will review activities with Elio - Re testing of the bug - Help form WR to re test below bugs just to verify are not reproducible on Train - https://bugs.launchpad.net/starlingx/+bug/1851247 - https://bugs.launchpad.net/starlingx/+bug/1849181 3. Final Regression TP approval - Test Plan approved by Yang, Elio to present on the next release meeting 4. Unified Sanity - Need to review our infrastructure and double check if is possible to adapt to test L3. Still working on this. - Another round of pytest should be done after updates. 5. Opens - Bruce Request for Sanity - New LP on neutron router https://bugs.launchpad.net/starlingx/+bug/1853907 Regards Jose -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Nov 26 18:34:21 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Nov 2019 19:34:21 +0100 Subject: [Starlingx-discuss] Community Marketing Planning call tomorrow Message-ID: Hi, It is a friendly reminder that we have the next Community Marketing Planning call tomorrow (November 27). We will discuss feedback from recent events, start 2020 planning and continue discussing the overview slide deck and diagram proposals. For further details about the call please see this etherpad: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans For the latest proposals of the overview slide and diagram please see this GitHub issue: https://github.com/StarlingXWeb/starlingx-website/issues/39 Please let me know if you have any feedback to the slides/diagram or if you have any questions. Thanks, Ildikó From jim.somerville at windriver.com Tue Nov 26 18:48:47 2019 From: jim.somerville at windriver.com (Jim Somerville) Date: Tue, 26 Nov 2019 13:48:47 -0500 Subject: [Starlingx-discuss] Proposed rules regarding patch files Message-ID: <6ab7536b-dcd5-783c-89d6-cd9078bd41e1@windriver.com> Hi Folks, I'm tired of tripping over the same nonsense again and again regarding patch files in our source repos. Can we consider getting this captured in our StarlingX developer how-to documentation/training materials? Also the build-pkgs tool should have an alternate "--edit" option that applies patches via "git am", making the actual source it produces in a git repo useful, instead of the mangled commit headers it creates currently. -Jim Patch files should always be generated via git format-patch and contain a meaningful commit header, thus being "git am friendly". Patches are not to be generated via quick and dirty diff commands. The commit header should also contain your sign off if you've done more than just a context refresh or simple rebase of the patch. Patch files should never be directly edited. The temptation may be there for you to be lazy and just edit a patch file directly. Do not do this, work in git to correct the patch and then regenerate it. The name of a patch file is generated automatically by git format-patch from the shortlog ie. first line of the commit header. The shortlog is very important in the grand scheme of the commit header, put a lot of thought into writing that one line to make it *meaningful*. Many developers use "git log --oneline" to display lists of commits, and that displays the shortlog only. Again, make it succinct and meaningful, I cannot emphasize this enough. Patch files should never be renamed eg. via the mv command, after they are generated. If you don't like the name of the generated patch file, change the commit shortlog and regenerate it. Do NOT do this crime (example): git format-patch produces fix-some-problem-description.patch mv fix-some-problem-description.patch some-description-i-prefer.patch From vm.rod25 at gmail.com Tue Nov 26 19:03:21 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 26 Nov 2019 13:03:21 -0600 Subject: [Starlingx-discuss] Proposed rules regarding patch files In-Reply-To: <6ab7536b-dcd5-783c-89d6-cd9078bd41e1@windriver.com> References: <6ab7536b-dcd5-783c-89d6-cd9078bd41e1@windriver.com> Message-ID: On Tue, Nov 26, 2019 at 12:49 PM Jim Somerville wrote: > > Hi Folks, > > I'm tired of tripping over the same nonsense again and again regarding > patch files in our source repos. Can we consider getting this captured > in our StarlingX developer how-to documentation/training materials? > > Also the build-pkgs tool should have an alternate "--edit" option that > applies patches via "git am", making the actual source it produces in a > git repo useful, instead of the mangled commit headers it creates currently. > > -Jim > > Patch files should always be generated via git format-patch and contain > a meaningful commit header, thus being "git am friendly". Patches are > not to be generated via quick and dirty diff commands. The commit > header should also contain your sign off if you've done more than just a > context refresh or simple rebase of the patch. > > Patch files should never be directly edited. The temptation may be > there for you to be lazy and just edit a patch file directly. Do not do > this, work in git to correct the patch and then regenerate it. > > The name of a patch file is generated automatically by git format-patch > from the shortlog ie. first line of the commit header. The shortlog is > very important in the grand scheme of the commit header, put a lot of > thought into writing that one line to make it *meaningful*. Many > developers use "git log --oneline" to display lists of commits, and that > displays the shortlog only. Again, make it succinct and meaningful, I > cannot emphasize this enough. +1 In addition to this I would like to share a presentation from last week kubecon: https://speakerdeck.com/thockin/how-to-be-a-bad-ass-code-reviewer The commit-msg should answer 2 questions: what /why: What are the changes listed on the patch why you want to do the changes Other good points are highlighted in the presentation Hope it helps to improve the quality of our commit msgs Regards Victor R > > Patch files should never be renamed eg. via the mv command, after they > are generated. If you don't like the name of the generated patch file, > change the commit shortlog and regenerate it. > > Do NOT do this crime (example): > > git format-patch > produces > fix-some-problem-description.patch > mv fix-some-problem-description.patch some-description-i-prefer.patch > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From maria.g.perez.ibarra at intel.com Tue Nov 26 22:31:31 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 26 Nov 2019 22:31:31 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191126 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-26 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007062.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Tue Nov 26 22:56:01 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Tue, 26 Nov 2019 22:56:01 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation In-Reply-To: References: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A4BB3@ORSMSX121.amr.corp.intel.com> Hi Mingyuan, Thank you - confirmed that I have seen the task and that the new content has been reviewed. Thanks for the contribution! Cheers, Kris From: Qi, Mingyuan Sent: Monday, November 25, 2019 12:08 AM To: Dale, Kristal ; starlingx-discuss at lists.starlingx.io Subject: RE: [docs] Help with StarlingX R3 documentation Hi Kristal, I've created a task in the qat device plugin SB[0] to add the doc and submitted a commit[1] for docs team review. [0] https://storyboard.openstack.org/#!/story/2005514 [1] https://review.opendev.org/#/c/695849/ Mingyuan From: Qi, Mingyuan > Sent: Thursday, November 21, 2019 16:30 To: Dale, Kristal >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Hi Kristal, I'm writing a doc for "Kubernetes QAT device plugin configuration", I believe it's under Kubernetes Operation section. I didn't find a story for this section, could you please create a story or task so that I could submit the rst for review? Mingyuan From: Dale, Kristal > Sent: Thursday, November 21, 2019 3:34 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation Hello All, The StarlingX docs team is preparing new documentation for the R3 release and we need community help. Specifically, we are looking for people to contribute content for the following topics: * New Config Guide: Certificate Configuration & Management Sub topics: * Kubernetes platform cert configs, task 37478: o REST APIs (starlingx, keystone, barbican) & Horizon o Kubernetes API Root CA o Docker Registry (Kubernetes) o Configuring a trusted CA (Kubernetes) * OpenStack app configs, task 37508: o REST APIs and Horizon Story: https://storyboard.openstack.org/#!/story/2006866 Content to go here: https://docs.starlingx.io/configuration/cert_config.html * New Config Guide: System Configuration Sub topics: * DNS servers, task 37502 * OAM Firewall, task 37504 Story: https://storyboard.openstack.org/#!/story/2006862 Content to go here: https://docs.starlingx.io/configuration/system_config.html If you have experience or content for any of these topics and can contribute (or if you know someone who has info), please contact me to coordinate. The docs team will help with the formatting/reST markup - we need your help with the content! And - we now have multiple new stub pages for specific topics added to the docs. * Configuration section (https://docs.starlingx.io/configuration/index.html) * Operation Guides section (https://docs.starlingx.io/operations/index.html) If you have experience or content for any of these topics, we would love your contribution! Cheers, Kris and the StarlingX docs team -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Tue Nov 26 23:07:13 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Tue, 26 Nov 2019 23:07:13 +0000 Subject: [Starlingx-discuss] controller filesystem In-Reply-To: References: <7acae15c-0c7d-77e7-9f27-b8156b516819@linux.intel.com> Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A4BD6@ORSMSX121.amr.corp.intel.com> Saul – Addition of host-fs content is captured in this story: https://storyboard.openstack.org/#!/story/2006888 Greg and I planned to address a subset of content for this new page (Certificate Management, Local docker reg) in the first pass. I will be working on this page next week and will welcome any host-fs content! Cheers, Kris From: Waines, Greg Sent: Monday, November 25, 2019 5:27 AM To: Saul Wold ; von Hoesslin, Volker ; Sun, Austin ; starlingx-discuss at lists.starlingx.io; Dale, Kristal Subject: Re: [Starlingx-discuss] controller filesystem Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold > Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" >, "Sun, Austin" >, "starlingx-discuss at lists.starlingx.io" >, "Dale, Kristal" > Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Tue Nov 26 23:42:40 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Tue, 26 Nov 2019 23:42:40 +0000 Subject: [Starlingx-discuss] [ Regression TRAIN testing - stx3.0 ] Report for 11/26/2019 Message-ID: StarlingX 3.0 Release Status: ISO: BUILD_ID=" 20191122T023000Z" from (link) ---------------------------------------------------------------------- MANUAL TRAIN EXECUTION ---------------------------------------------------------------------- Overall Results: Total = 73 Pass = 60 Fail = 3 Blocked = 0 Not Run = 9 Obsolete = 1 Deferred = 0 Total executed = 63 Pass Rate = 95% Formula used : Pass Rate = (pass * 100) / (pass + fail) --------------------------------------------------------------------------- AUTOMATED ROBOT TRAIN EXECUTION --------------------------------------------------------------------------- Overall Results: Total = 105 Pass = 91 Fail = 14 Blocked = 0 Obsolete = 0 Deferred = 0 Not Valid = 0 Total executed = 105 Pass Rate = 86.6% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- AUTOMATED PYTEST TRAIN EXECUTION --------------------------------------------------------------------------- Overall Results: Total = 191 Pass = 78 Fail = 7 Blocked = 7 Obsolete = 49 Not Run = 50 Deferred = 0 Not Valid = 0 Total executed = 85 Pass Rate = 91.7% Formula used : Pass Rate = pass * 100 / (pass + fail) --------------------------------------------------------------------------- For more detail of the tests: https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit#gid=1717644237 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ran1.an at intel.com Wed Nov 27 08:33:03 2019 From: ran1.an at intel.com (An, Ran1) Date: Wed, 27 Nov 2019 08:33:03 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation In-Reply-To: References: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> Message-ID: <9BAB5B7CAF57C3459E4636391F1071CE0535106C@shsmsx102.ccr.corp.intel.com> Hi Kristal, I've created a task in the Intel GPU device plugin SB[0] to add the doc and submitted a commit[1] for docs team review. [0] https://storyboard.openstack.org/#!/story/2005937 [1] https://review.opendev.org/#/c/696241/ Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhang.kunpeng at 99cloud.net Wed Nov 27 09:39:36 2019 From: zhang.kunpeng at 99cloud.net (=?gb2312?B?1cX278X0?=) Date: Wed, 27 Nov 2019 17:39:36 +0800 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Message-ID: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> Hi Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Nov 27 12:40:21 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 27 Nov 2019 12:40:21 +0000 Subject: [Starlingx-discuss] Community Call (Nov 27, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC007B34939@ALA-MBD.corp.ad.wrs.com> Hi all, reminder of the Community call later today. We have many topics on the agenda [0], so we'll likely have to prune it a bit... - standing topics - Gerrit review in need of attention - none so far - Sanity: any RED since last week? - not so far - Unanswered Requests for Help on Mailing List - 4 this week - this week's topics - stx.3.0 update, including gating bugs - PSA re: deployment of OpenStack in StarlingX AIO Simplex - Doc Process - Unit Test - Proposed rules regarding patch files - Dev Process - what's the process for modifying the process Bill... [0] etherpad: https://etherpad.openstack.org/p/stx-status [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1400_UTC_-_Community_Call [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191127T1500 From Tao.Liu at windriver.com Wed Nov 27 15:06:05 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 27 Nov 2019 15:06:05 +0000 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> Hi Kunpeng, We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry docker_registries: k8s.gcr.io: url: registry.central:9001/k8s.gcr.io gcr.io: url: registry.central:9001/gcr.io quay.io: url: registry.central:9001/quay.io docker.io: url: registry.central:9001/docker.io docker.elastic.co: url: registry.central:9001/docker.elastic.co defaults: type: docker username: admin password: Li69nux* additional_local_registry_images: - registry.central:9001/addition_image_name Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 4:40 AM To: starlingx-discuss at lists.starlingx.io; Liu, Tao Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Nov 27 15:18:33 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 27 Nov 2019 15:18:33 +0000 Subject: [Starlingx-discuss] MoM/Agenda: Weekly StarlingX non-OpenStack distro meeting, 11/27/2019 Message-ID: Thanks join the meeting . MoM for 11/27 meeting: * stx.4.0 feature - Ceph containerization update (Tingjie/martin) review BP https://review.opendev.org/#/c/692502/ ongoing no other update due to bug fixing - Standardize Flock Package Versioning (Yang Bin) https://review.opendev.org/#/c/691647 --> Don's review comments should be valid. Bin will share how to handle such comments in hand-on workshop for JitStack JitStack Daniel will get familar with Stx and be involved this task soon. - CentOS 8.0 upgrade planning (Shuai Zhao) *) Kernel upgrade kernel package uploaded , driver sign issue is fixed. config files and several drivers packages are uploaded too . fpga driver code for centos8 can not be found. *) SRPM el8 sram uploaded task is finished . pkg el7 only : due to mirror upgraded el8 , the depends rpm can not find in mirror el7 only: * some adding patch and uploaded to gerrit * some other only need to fix the dependence , and updated to excel sheet. are there replacement for some el7 in el8 ? *) Tarball this task kicks off. 6 tarball is compiled. *) build container https://review.opendev.org/#/c/694761/10 is needed to split to 4 patches This should be at least 4 new patches. Container related changes (Dockerfile/tb.sh), mirror scripts changes (centos-mirror-tools/), yum related changes and then the centos lst files. *) centos8 mirror is updating day by day . investigate *_0.src.rpm package. --- Shuai will describe it and send to mail list. - Kata Container (Shuicheng) code is under review , and some tests are on-going. * stx 3.0 bugs fix - CVE issue tracking (Shuicheng) * OVMF ---> still under review. master is good , stx.2.0 nova is not merged yet. * libX11 ---> merged * kernel change upgrade 1062 --> RT performance test is needed and under test. should be finished by End of week. - Storage issue tracking (Tingjie) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.storage https://bugs.launchpad.net/starlingx/+bug/1844363: confirm w/ owner, the issue is gone. remove the stx3.0 tag https://bugs.launchpad.net/starlingx/+bug/1826886: wait pengpeng's feedback https://bugs.launchpad.net/starlingx/+bug/1831635: wait pengpeng's feedback https://bugs.launchpad.net/starlingx/+bug/1844164: ??? https://bugs.launchpad.net/starlingx/+bug/1847336: the issue is still reproduced w/ fix https://review.opendev.org/#/c/689730/, need further investigate https://bugs.launchpad.net/starlingx/+bug/1848198: need Stefan update https://bugs.launchpad.net/starlingx/+bug/1853642: need Stefan update - Others issue tracking (Austin) https://bugs.launchpad.net/starlingx/+bugs?search=Search&field.tags_combinator=ALL&field.tag=stx.3.0+stx.distro.other https://bugs.launchpad.net/starlingx/+bug/1847335 under discuss , need some more info and try. *Opens(All) Proposed rules regarding patch files from community --- pay more attention to patch quality. Austin Sun. From zhang.kunpeng at 99cloud.net Wed Nov 27 16:38:00 2019 From: zhang.kunpeng at 99cloud.net (=?gb2312?B?1cX278X0?=) Date: Thu, 28 Nov 2019 00:38:00 +0800 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> Message-ID: <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> Hi Tao, Thanks for your reply. But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud? > 1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 > 在 2019年11月27日,23:06,Liu, Tao 写道: > > Hi Kunpeng, > > We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: > 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process > 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud > > Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry > docker_registries: > k8s.gcr.io : > url: registry.central:9001/k8s.gcr.io > gcr.io : > url: registry.central:9001/gcr.io > quay.io : > url: registry.central:9001/quay.io > docker.io : > url: registry.central:9001/docker.io > docker.elastic.co : > url: registry.central:9001/docker.elastic.co > defaults: > type: docker > username: admin > password: Li69nux* > > additional_local_registry_images: > - registry.central:9001/addition_image_name > > Tao > > From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] > Sent: Wednesday, November 27, 2019 4:40 AM > To: starlingx-discuss at lists.starlingx.io; Liu, Tao > Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. > > Hi Distributed Cloud team, > > > The distributed cloud feature is very cool, and I am concerned about its development always. > There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 > > Thanks > Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Wed Nov 27 17:13:31 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 27 Nov 2019 17:13:31 +0000 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4ED50B0@ALA-MBD.corp.ad.wrs.com> Hi Kunpeng, As I stated previously, the Central Cloud’s Local Registry is exposed on the OAM interface. This is required to allow pushing images from a remote workstation to the Central Cloud, in addition to support bootstrapping via the OAM interface. As the document in the link below states, ”Using the management interface requires the creation of an additional temporary IP address/subnet on the management interface for bootstrapping”. This is a recommended method. Using the OAM interface for bootstrapping means that OAM IP Subnets need to be routable between Central Cloud and Subclouds, and it does not require a direct physical connection. P.S. The MGMT IP subnets between Central Cloud and Subclouds are interconnected over Layer 3, not as part of an Layer 2 MGMT network. Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 11:38 AM To: Liu, Tao Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Tao, Thanks for your reply. But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud? 1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 在 2019年11月27日,23:06,Liu, Tao > 写道: Hi Kunpeng, We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry docker_registries: k8s.gcr.io: url: registry.central:9001/k8s.gcr.io gcr.io: url: registry.central:9001/gcr.io quay.io: url: registry.central:9001/quay.io docker.io: url: registry.central:9001/docker.io docker.elastic.co: url: registry.central:9001/docker.elastic.co defaults: type: docker username: admin password: Li69nux* additional_local_registry_images: - registry.central:9001/addition_image_name Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 4:40 AM To: starlingx-discuss at lists.starlingx.io; Liu, Tao Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Wed Nov 27 17:22:28 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Wed, 27 Nov 2019 17:22:28 +0000 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4ED50B0@ALA-MBD.corp.ad.wrs.com> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED50B0@ALA-MBD.corp.ad.wrs.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4ED50C9@ALA-MBD.corp.ad.wrs.com> A typo in the previous email: “This is a recommended method”. => This is not a recommended method. Tao From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Wednesday, November 27, 2019 12:14 PM To: 张鲲鹏 Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Kunpeng, As I stated previously, the Central Cloud’s Local Registry is exposed on the OAM interface. This is required to allow pushing images from a remote workstation to the Central Cloud, in addition to support bootstrapping via the OAM interface. As the document in the link below states, ”Using the management interface requires the creation of an additional temporary IP address/subnet on the management interface for bootstrapping”. This is not a recommended method. Using the OAM interface for bootstrapping means that OAM IP Subnets need to be routable between Central Cloud and Subclouds, and it does not require a direct physical connection. P.S. The MGMT IP subnets between Central Cloud and Subclouds are interconnected over Layer 3, not as part of an Layer 2 MGMT network. Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 11:38 AM To: Liu, Tao Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Tao, Thanks for your reply. But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud? 1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 在 2019年11月27日,23:06,Liu, Tao > 写道: Hi Kunpeng, We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry docker_registries: k8s.gcr.io: url: registry.central:9001/k8s.gcr.io gcr.io: url: registry.central:9001/gcr.io quay.io: url: registry.central:9001/quay.io docker.io: url: registry.central:9001/docker.io docker.elastic.co: url: registry.central:9001/docker.elastic.co defaults: type: docker username: admin password: Li69nux* additional_local_registry_images: - registry.central:9001/addition_image_name Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 4:40 AM To: starlingx-discuss at lists.starlingx.io; Liu, Tao Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 Thanks Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Nov 27 17:29:48 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 27 Nov 2019 17:29:48 +0000 Subject: [Starlingx-discuss] [docs] Help with StarlingX R3 documentation In-Reply-To: <9BAB5B7CAF57C3459E4636391F1071CE0535106C@shsmsx102.ccr.corp.intel.com> References: <43F963BD1517044B90CF82FB2F3CA716220A164F@ORSMSX121.amr.corp.intel.com> <9BAB5B7CAF57C3459E4636391F1071CE0535106C@shsmsx102.ccr.corp.intel.com> Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A4F24@ORSMSX121.amr.corp.intel.com> Thanks for the contribution Ran! We'll get it reviewed and into the docs. Best, Kris From: An, Ran1 Sent: Wednesday, November 27, 2019 12:33 AM To: Dale, Kristal Cc: starlingx-discuss at lists.starlingx.io Subject: [docs] Help with StarlingX R3 documentation Hi Kristal, I've created a task in the Intel GPU device plugin SB[0] to add the doc and submitted a commit[1] for docs team review. [0] https://storyboard.openstack.org/#!/story/2005937 [1] https://review.opendev.org/#/c/696241/ Thanks Ran -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristal.dale at intel.com Wed Nov 27 18:29:56 2019 From: kristal.dale at intel.com (Dale, Kristal) Date: Wed, 27 Nov 2019 18:29:56 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team status 2019-11-27 Message-ID: <43F963BD1517044B90CF82FB2F3CA716220A4F83@ORSMSX121.amr.corp.intel.com> Hello All, I am cancelling today's STX docs meeting due to conflicts. If anyone has any questions, topics to discuss, or concerns, please contact me directly. A two quick notes: 1. We still need help with the following R3 documentation topics: * Certificate Configuration & Management -- https://storyboard.openstack.org/#!/story/2006866 * System Config Guide -- https://storyboard.openstack.org/#!/story/2006862 o Topics: ? DNS Servers, task 37502 ? OAM Firewall, task 37504 --> If anyone can contribute technical content for these topics, please let me know! The docs team will gladly do the reST/formatting work, if we can get the technical content from an expert! 1. If there is a topic that is important for the upcoming R3 release that is not included in our current target content list (https://etherpad.openstack.org/p/stx-r3-target-content) please let us know what that topic is, and who can provide the needed content. We'll do our best to get it in for R3! And lastly, weekly docs status is below. As always, join us if you have interest in StarlingX docs! We meet Wednesdays 12:30 PST. * Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings * Our tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Best, Kris Current agenda and notes 2019-11-27 * All -- reviews in progress and recent merges -- ? 8 merged since last week ? 6 open: * https://review.opendev.org/#/c/696201/ - Ansible new OpenID Connect config info * https://review.opendev.org/#/c/696198/ - Ansible updated Docker registry info * https://review.opendev.org/#/c/695811/ - TSN guide - in editorial review (Mary) * https://review.opendev.org/#/c/695627/ - Move to new version of STX guide - in editorial review (Kris) * https://review.opendev.org/#/c/692202/ - First draft STX in a box, needs review (Abraham). Needs hosting of image confirmed. * https://review.opendev.org/#/c/693761/ - depends on failed change (TBD) * Abraham and all -- bug status -- https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs * Kris -- Releases ? R2.0.2 EOY - Will require release notes (no impact to R3) ? R3.0 - Target release in early Dec * The current plan is to create the stx.3.0 release branch (r/stx.3.0) on Nov 28. * R3 Stories: http s://storyboard.openstack.org/#!/story/list?tags=stx.docs&tags=stx.3.0 * R3: Target content for release: https://etherpad.openstack.org/p/stx-r3-target-content o What is the status on ? Kubernetes Cluster Guide (Greg?) ? CLI Ref - Kris will start Monday * Requested community help - still needed! * STX in a box: (https://storyboard.openstack.org/#!/story/2006622) ? Draft in review https://review.opendev.org/#/c/692202/ ? Hosting qcow2 images: Provided initial answers to Scott Little (see previous meeting notes). Scott/Saul continuing convo offline. * Misc: ? (new) Upgrade STX doc - Zhipeng Liu. * Request from community meeting to not call it "Upgrade" but instead to use "up-version" or "up-rev" - Thoughts? What about "migrate" or "update"? "How to move to a different version of StarlingX" ? http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006813.html * This may impact all general install instructions (making sure versions align across all needed files/packages) ? Possible guide for deploying on packet.com? (AR: Greg will explore this - Abraham will help) * https://wiki.openstack.org/wiki/StarlingX/Packet_SIG * Explore this as content for a new guide -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Nov 27 18:41:17 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 27 Nov 2019 13:41:17 -0500 Subject: [Starlingx-discuss] r/stx.3.0 Message-ID: The StarlingX 3.0 release branch (r/stx.3.0) will be created tomorrow (Nov 28) based on tonights 20191128T023000Z CENGN build context (assuming a successful build). Code review primes can expect to see a small code inspection that will modify .gitreview to reflect the new branch an all StarlingX repos.  There will also be a review for the new repo manifest. Please process these reviews quickly. For the master branch, no code freeze is required.  Continue to work as normal.  However I would request that feature content intended for 4.0 be held back a day or two until we have a successful CENGN build of 3.0. Please treat the r/stx.3.0 branch as frozen until I have a successful CENGN build on the new branch.  No gerrit reviews should be approved except for my manifest and .gitreview changes.   I'll send a follow up e-mail to lift the freeze. Fixes for 3.0 gating issues should continue to be delivered to the master branch, and subsequently cherry-picked into the r/stx.3.0 branch. Thanks for your cooperation. Scott Little From cristopher.j.lemus.contreras at intel.com Wed Nov 27 20:25:48 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Wed, 27 Nov 2019 14:25:48 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <3cea8d$75aagi@fmsmga002.fm.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191127T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From Ghada.Khalil at windriver.com Wed Nov 27 20:55:34 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 27 Nov 2019 20:55:34 +0000 Subject: [Starlingx-discuss] Canceled: Weekly StarlingX Release meeting Message-ID: <151EE31B9FCCA54397A757BC674650F0C15FEE84@ALA-MBD.corp.ad.wrs.com> As discussed in the community call today, there will be no release meeting tomorrow due to American Thanksgiving and other conflicts. Weekly meeting on Thursday 11AM PT / 1900 UTC Zoom Link: https://zoom.us/j/342730236 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1798 bytes Desc: not available URL: From maria.g.perez.ibarra at intel.com Thu Nov 28 00:35:12 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 28 Nov 2019 00:35:12 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191127 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-27 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007087.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Thu Nov 28 02:11:33 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Thu, 28 Nov 2019 02:11:33 +0000 Subject: [Starlingx-discuss] swift enabling Message-ID: <56829C2A36C2E542B0CCB9854828E4D856281F18@CDSMSX102.ccr.corp.intel.com> Hi I find there is voice to enable swift, why it was removed? Thanks! Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Message: 3 Date: Fri, 22 Nov 2019 14:14:15 +0000 From: "von Hoesslin, Volker" To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] STX 2.0: swift? Message-ID: Content-Type: text/plain; charset="iso-8859-1" hi, how can i add the object storage (swift) feature to my current STX2.0 openstack? BR! Martin, Chen SSP, Software Engineer 021-61164330 -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Tuesday, November 26, 2019 12:05 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 18, Issue 150 Send Starlingx-discuss mailing list submissions to starlingx-discuss at 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 at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at 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. Re: controller filesystem (Waines, Greg) 2. Enabling Object Storage (joji vlogs) 3. Re: StarlingX 2.0 Account Locked for User (Andy Ning) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Nov 2019 13:26:31 +0000 From: "Waines, Greg" To: Saul Wold , "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Message-ID: Content-Type: text/plain; charset="utf-8" Actually a section on managing filesystems on the controllers is planned for STX 3.0 ... based on the proposed TOC for the new Operations Guide. Greg From: Saul Wold Date: Thursday, November 21, 2019 at 12:13 PM To: "von Hoesslin, Volker" , "Sun, Austin" , "starlingx-discuss at lists.starlingx.io" , "Dale, Kristal" Subject: Re: [Starlingx-discuss] controller filesystem Kristal: We probably need a Story/Task added to the documentation to get the documentation of host-fs added in the right place. This helps with filesystem re-sizing. Maybe it's already there. Sau! On 11/21/19 7:12 AM, von Hoesslin, Volker wrote: incredible !!! thats the point i have search! big thx! ------------------------------------------------------------------------ *Von:* Sun, Austin [austin.sun at intel.com] *Gesendet:* Donnerstag, 21. November 2019 15:20 *An:* von Hoesslin, Volker; starlingx-discuss at lists.starlingx.io *Betreff:* Re: [Starlingx-discuss] controller filesystem Hi Volker: From the email chain, http://lists.starlingx.io/pipermail/starlingx-discuss/2019-August/005656.html You can probably the command line to change the size of docker lv Thanks. BR Austin Sun. *From:* von Hoesslin, Volker > *Sent:* Thursday, November 21, 2019 9:20 PM *To:* starlingx-discuss at lists.starlingx.io *Subject:* [Starlingx-discuss] controller filesystem hi, i trying to import some existing qcow2 images into my new installed STX 2.0. openstack image create --file /media/foobar.qcow2 --private --unprotected --disk-format qcow2 "foobar" all works fine, the image are available. now, i'm trying to create an new volume based on this images. if the images are <=6GB all works fine, but some images are very huge (10-200GB) and then it ends in an error. after some research i can see on controller the mount point /dev/mapper/cgts--vg-docker--lv 30G 11G 20G 35% /var/lib/docker increase the used storage. after fail "volume create" it goes back to given value 35%. in my oppinion, this mount point should resize to some value about 300-400GB, but how? in STX horizon backend (http://10.10.10.2:8080/admin/system_config/?tab=system_config_tab__storage_table) there is an "docker-distribution", but no docker-mount-point itself? btw, if i try to change the "docker-distribution" value to some other value (eg. 500GB via horizon backend), i got this error: *Error: *backup size of 60 is insufficient for host controller-1. Minimum backup size of 100 is required based upon glance size 20 and database size 20. Rejecting modification request. - see attachment - how can i increase the backup size to handle this error?! greez & thx, volker... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Mon, 25 Nov 2019 07:53:31 -0600 From: joji vlogs To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Enabling Object Storage Message-ID: Content-Type: text/plain; charset="utf-8" Hi all, I recently did a test deployment based on a 2+2+2 setup with one minor difference being I only have one storage server on hand. My question is how would I go about enabling object storage? I saw a reference to it in the helm charts and attempted to set an override but the APIs would not be listening for requests and a "unable to get swift service info" error. Thank you and have a great day! Austin Gillmann -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 3 Date: Mon, 25 Nov 2019 11:05:19 -0500 From: Andy Ning To: Subject: Re: [Starlingx-discuss] StarlingX 2.0 Account Locked for User Message-ID: <8f8e6cad-0ad7-4be4-6693-a25e6cec93ad at windriver.com> Content-Type: text/plain; charset="utf-8"; format=flowed On 2019-11-25 12:00 AM, Yong Hu wrote: > Hi Anirudh, > > This issue is similar to this LP#1853017 [0], which was triggered the > account locking if the password of Openstack user "admin" was changed. > In this LP, for unknown reason, "registry-token-server" daemon kept > accessing "keystone" on host (not the instance in containers) with > obsolete token and led to "admin" account locked after 5 attempts. > If registry token server keeps on accessing keystone with obsolete token, this could be a bug in the token server. Normally if a keystone client get a failed authentication, it should try to retrieve a new token by using username/password. Andy > Right now, I am debugging this issue. > Good thing is Cengn build 11/16 seemed not to have such a problem > (LP#1853017). > > You might have a try with this version? > BTW: which cengn build were you using? > > > [0] https://bugs.launchpad.net/starlingx/+bug/1853017 > > regards, > Yong > > On 2019/11/19 6:06 PM, Anirudh Gupta wrote: >> Hi Team, >> >> I have installed StarlingX 2.0 Duplex Bare Metal. >> >> I am trying to create 2 VM’s and repeating this cycle a number of times. >> >> After using the setup for around half and hour, I am not longer able >> to access the GUI. >> >> Ever though I type correct Username/Password, it gives an error of >> Invalid Credentials. >> >> Then, I thought to use the CLI commands by following LOAD CLI section >> given in link >> >> https://docs.starlingx.io/deploy_install_guides/r2_release/openstack/ >> access.html#local-cli >> >> >> But with this also, I am facing the same error >> >> controller-0:~$ export OS_CLOUD=openstack_helm >> >> controller-0:~$ openstack endpoint list >> >> The account is locked for user: 230578cde382430a8adac399afab1230. >> (HTTP 401) (Request-ID: req-6da6d59a-2edd-4f2b-a8bf-f13f2e423a77) >> >> Earlier this automatically started working after 5-7 mins. >> >> But this time, I am completely Blocked. >> >> I have also raised a bug regarding the same >> >> https://bugs.launchpad.net/starlingx/+bug/1853093 >> >> Please suggest some pointers, so that I can unblock and resume my >> activities. >> >> Regards >> >> Anirudh Gupta >> >> 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. >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Andy Ning Cube: 3071 Tel: 613-9631408 (int: 4408) Skype: andy.ning.wr ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ End of Starlingx-discuss Digest, Vol 18, Issue 150 ************************************************** From zhang.kunpeng at 99cloud.net Thu Nov 28 02:31:46 2019 From: zhang.kunpeng at 99cloud.net (=?gb2312?B?1cX278X0?=) Date: Thu, 28 Nov 2019 10:31:46 +0800 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <7242A3DC72E453498E3D783BBB134C3EA4ED50C9@ALA-MBD.corp.ad.wrs.com> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED50B0@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3EA4ED50C9@ALA-MBD.corp.ad.wrs.com> Message-ID: <4D7B8A1C-54B4-4535-8F04-505CF1B1D04A@99cloud.net> Hi Tao, I see, and I think connecting all in one network interface between central and subclouds possibility reduces network topology. I will keep eye on this feature, and hope to contribute something I can do. In addition, do you have or plan to make these yaml files about deploy_playbook and deploy_values? I have wrote a simple playbook to deploy and it work well in simplex, I think I can do this job, if you don’t have a plan for it. Kunpeng > 在 2019年11月28日,01:22,Liu, Tao 写道: > > A typo in the previous email: > > “This is a recommended method”. => This is not a recommended method. > > Tao > From: Liu, Tao [mailto:Tao.Liu at windriver.com ] > Sent: Wednesday, November 27, 2019 12:14 PM > To: 张鲲鹏 > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. > > Hi Kunpeng, > > As I stated previously, the Central Cloud’s Local Registry is exposed on the OAM interface. This is required to allow pushing images from a remote workstation to the Central Cloud, in addition to support bootstrapping via the OAM interface. > > As the document in the link below states, ”Using the management interface requires the creation of an additional temporary IP address/subnet on the management interface for bootstrapping”. This is not a recommended method. > > Using the OAM interface for bootstrapping means that OAM IP Subnets need to be routable between Central Cloud and Subclouds, and it does not require a direct physical connection. > > P.S. The MGMT IP subnets between Central Cloud and Subclouds are interconnected over Layer 3, not as part of an Layer 2 MGMT network. > > Tao > > From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] > Sent: Wednesday, November 27, 2019 11:38 AM > To: Liu, Tao > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. > > Hi Tao, > > Thanks for your reply. > But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud? > > > 1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 > > > 在 2019年11月27日,23:06,Liu, Tao > 写道: > > Hi Kunpeng, > > We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: > 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process > 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud > > Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry > docker_registries: > k8s.gcr.io : > url: registry.central:9001/k8s.gcr.io > gcr.io : > url: registry.central:9001/gcr.io > quay.io : > url: registry.central:9001/quay.io > docker.io : > url: registry.central:9001/docker.io > docker.elastic.co : > url: registry.central:9001/docker.elastic.co > defaults: > type: docker > username: admin > password: Li69nux* > > additional_local_registry_images: > - registry.central:9001/addition_image_name > > Tao > > From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net ] > Sent: Wednesday, November 27, 2019 4:40 AM > To: starlingx-discuss at lists.starlingx.io ; Liu, Tao > Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. > > Hi Distributed Cloud team, > > > > The distributed cloud feature is very cool, and I am concerned about its development always. > There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. > > > > As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. > But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. > I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. > > > > Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? > > > > Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? > > > > 1. https://bugs.launchpad.net/starlingx/+bug/1846799 > 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 > > Thanks > Kunpeng > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From fuyong at neusoft.com Thu Nov 28 03:40:45 2019 From: fuyong at neusoft.com (=?utf-8?B?5LuY5YuH?=) Date: Thu, 28 Nov 2019 11:40:45 +0800 Subject: [Starlingx-discuss] Problems downloading mirror in centos8 environment Message-ID: <000501d5a59d$9e154420$da3fcc60$@neusoft.com> Hi StarlingX team I’m upgrading starlingx to centos8 and have a question to ask for help. problem: I cannot download the specified version of srpm through the dnf download --source command. Eg: About two weeks ago, I was able to download the bash-4.4.19-7.el8.src.rpm file through the “dnf download --source bash-4.4.19-7.el8” command in centos8. But now I cannot download the bash-4.4.19-7.el8.src.rpm file with this command, even if I can download it at http://vault.centos.org/8.0.1905/BaseOS/Source/SPackages/ . Error info: No package bash-4.4.19-7.el8.src available. Exiting due to strict setting. Error: No package bash-4.4.19-7.el8.src available. please contact me, If you have any good suggestions. Thank you Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From weifei.yu at intel.com Thu Nov 28 08:41:28 2019 From: weifei.yu at intel.com (Yu, Weifei) Date: Thu, 28 Nov 2019 08:41:28 +0000 Subject: [Starlingx-discuss] How to enable IPv6 on stx-openstack? Message-ID: Hi All, I`m trying to deploy VM with IPv6 on stx-openstack, so I create the subnet by below command and I`ve tried both slaac and dhcpv6-stateful, but the VM didn`t get correct IPv6 address inside. neutron subnet-create --tenant-id ${ADMINID} --name ${PUBLICSUBNET} --enable-dhcp --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac ${PUBLICNET} 2019::/64 I am able to see the IP on command show but VM actually doesn't gets correct IP. controller-0:/home/sysadmin# openstack server list +--------------------------------------+------+--------+---------------------------------------+--------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+------+--------+---------------------------------------+--------+----------+ | fe009153-49a0-49a8-95cb-302418016ca4 | vm1 | ACTIVE | public-net0=2019::f816:3eff:fe09:d386 | cirros | m1.tinny | | 8ac10f9c-ce7f-41c1-be91-c7c2a1675d38 | vm0 | ACTIVE | public-net0=2019::f816:3eff:fef8:a856 | cirros | m1.tinny | +--------------------------------------+------+--------+---------------------------------------+--------+----------+ The instance console log show some info: Starting network... udhcpc (v1.23.2) started Sending discover... Sending discover... Sending discover... Usage: /sbin/cirros-dhcpc No lease, failing WARN: /etc/rc3.d/S40-network failed controller-0:/home/sysadmin# openstack subnet show cec4c9fe-3550-4305-af47-07cce8733bb8 +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | allocation_pools | 2019::2-2019::ffff:ffff:ffff:ffff | | cidr | 2019::/64 | | created_at | 2019-11-28T07:13:11Z | | description | | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 2019::1 | | host_routes | | | id | cec4c9fe-3550-4305-af47-07cce8733bb8 | | ip_version | 6 | | ipv6_address_mode | slaac | | ipv6_ra_mode | slaac | | location | Munch({'project': Munch({'domain_name': 'default', 'domain_id': None, 'name': 'admin', 'id': u'76a69c24405a4ac1a98502219d674c48'}), 'cloud': 'openstack_helm', 'region_name': 'RegionOne', 'zone': None}) | | name | public-subnet0 | | network_id | f1b35934-b266-4768-b3e4-f043e7c282c3 | | prefix_length | None | | project_id | 76a69c24405a4ac1a98502219d674c48 | | revision_number | 0 | | segment_id | None | | service_types | | | subnetpool_id | None | | tags | | | updated_at | 2019-11-28T07:13:11Z | +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ is there any documents for reference? Or some advice? B&R weifei -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Thu Nov 28 12:11:50 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Thu, 28 Nov 2019 12:11:50 +0000 Subject: [Starlingx-discuss] How to enable IPv6 on stx-openstack? In-Reply-To: References: Message-ID: <4B312286-EF65-4C9E-A98F-0EB92C81AE5A@windriver.com> Hello, You will need to use a guest image that supports SLAAC and/or DHCPv6. As you can see from the message below, the DHCP failed because it was attempting to retrieve an address via IPv4. Also note that many cloud images only enable IPv4 by default, so you may need to create a custom image with IPv6 enabled for your testing. Alternatively, you could use config-drive to do early initialization of IPv6 network settings. -Matt From: "Yu, Weifei" Date: Thursday, November 28, 2019 at 3:41 AM To: "starlingx-discuss at lists.starlingx.io" Cc: "Zhao, Forrest" , "Xu, Chenjie" , "Peters, Matt" Subject: [Starlingx-discuss] How to enable IPv6 on stx-openstack? Hi All, I`m trying to deploy VM with IPv6 on stx-openstack, so I create the subnet by below command and I`ve tried both slaac and dhcpv6-stateful, but the VM didn`t get correct IPv6 address inside. neutron subnet-create --tenant-id ${ADMINID} --name ${PUBLICSUBNET} --enable-dhcp --ip-version 6 --ipv6-ra-mode slaac --ipv6-address-mode slaac ${PUBLICNET} 2019::/64 I am able to see the IP on command show but VM actually doesn't gets correct IP. controller-0:/home/sysadmin# openstack server list +--------------------------------------+------+--------+---------------------------------------+--------+----------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+------+--------+---------------------------------------+--------+----------+ | fe009153-49a0-49a8-95cb-302418016ca4 | vm1 | ACTIVE | public-net0=2019::f816:3eff:fe09:d386 | cirros | m1.tinny | | 8ac10f9c-ce7f-41c1-be91-c7c2a1675d38 | vm0 | ACTIVE | public-net0=2019::f816:3eff:fef8:a856 | cirros | m1.tinny | +--------------------------------------+------+--------+---------------------------------------+--------+----------+ The instance console log show some info: Starting network... udhcpc (v1.23.2) started Sending discover... Sending discover... Sending discover... Usage: /sbin/cirros-dhcpc No lease, failing WARN: /etc/rc3.d/S40-network failed controller-0:/home/sysadmin# openstack subnet show cec4c9fe-3550-4305-af47-07cce8733bb8 +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | allocation_pools | 2019::2-2019::ffff:ffff:ffff:ffff | | cidr | 2019::/64 | | created_at | 2019-11-28T07:13:11Z | | description | | | dns_nameservers | | | enable_dhcp | True | | gateway_ip | 2019::1 | | host_routes | | | id | cec4c9fe-3550-4305-af47-07cce8733bb8 | | ip_version | 6 | | ipv6_address_mode | slaac | | ipv6_ra_mode | slaac | | location | Munch({'project': Munch({'domain_name': 'default', 'domain_id': None, 'name': 'admin', 'id': u'76a69c24405a4ac1a98502219d674c48'}), 'cloud': 'openstack_helm', 'region_name': 'RegionOne', 'zone': None}) | | name | public-subnet0 | | network_id | f1b35934-b266-4768-b3e4-f043e7c282c3 | | prefix_length | None | | project_id | 76a69c24405a4ac1a98502219d674c48 | | revision_number | 0 | | segment_id | None | | service_types | | | subnetpool_id | None | | tags | | | updated_at | 2019-11-28T07:13:11Z | +-------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ is there any documents for reference? Or some advice? B&R weifei -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Nov 28 13:55:52 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Nov 2019 08:55:52 -0500 Subject: [Starlingx-discuss] r/stx.3.0 In-Reply-To: References: Message-ID: <31b882e3-9c06-69b8-919a-c1bd7cbfe313@windriver.com> All git reviews for creation of branch r/stx.3.0 have been posted. Scott On 2019-11-27 1:41 p.m., Scott Little wrote: > The StarlingX 3.0 release branch (r/stx.3.0) will be created tomorrow > (Nov 28) based on tonights 20191128T023000Z CENGN build context > (assuming a successful build). > > Code review primes can expect to see a small code inspection that will > modify .gitreview to reflect the new branch an all StarlingX repos.  > There will also be a review for the new repo manifest. Please process > these reviews quickly. > > For the master branch, no code freeze is required.  Continue to work > as normal.  However I would request that feature content intended for > 4.0 be held back a day or two until we have a successful CENGN build > of 3.0. > > Please treat the r/stx.3.0 branch as frozen until I have a successful > CENGN build on the new branch.  No gerrit reviews should be approved > except for my manifest and .gitreview changes.   I'll send a follow up > e-mail to lift the freeze. > > Fixes for 3.0 gating issues should continue to be delivered to the > master branch, and subsequently cherry-picked into the r/stx.3.0 branch. > > Thanks for your cooperation. > > Scott Little > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From scott.little at windriver.com Thu Nov 28 14:05:30 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Nov 2019 09:05:30 -0500 Subject: [Starlingx-discuss] r/stx.3.0 In-Reply-To: <31b882e3-9c06-69b8-919a-c1bd7cbfe313@windriver.com> References: <31b882e3-9c06-69b8-919a-c1bd7cbfe313@windriver.com> Message-ID: It would help if I included a link to all the review wouldn't it. https://review.opendev.org/#/q/topic:create-r/stx.3.0+(status:open+OR+status:merged) Scott On 2019-11-28 8:55 a.m., Scott Little wrote: > All git reviews for creation of branch r/stx.3.0 have been posted. > > Scott > > > On 2019-11-27 1:41 p.m., Scott Little wrote: >> The StarlingX 3.0 release branch (r/stx.3.0) will be created tomorrow >> (Nov 28) based on tonights 20191128T023000Z CENGN build context >> (assuming a successful build). >> >> Code review primes can expect to see a small code inspection that >> will modify .gitreview to reflect the new branch an all StarlingX >> repos.  There will also be a review for the new repo manifest. Please >> process these reviews quickly. >> >> For the master branch, no code freeze is required.  Continue to work >> as normal.  However I would request that feature content intended for >> 4.0 be held back a day or two until we have a successful CENGN build >> of 3.0. >> >> Please treat the r/stx.3.0 branch as frozen until I have a successful >> CENGN build on the new branch.  No gerrit reviews should be approved >> except for my manifest and .gitreview changes.   I'll send a follow >> up e-mail to lift the freeze. >> >> Fixes for 3.0 gating issues should continue to be delivered to the >> master branch, and subsequently cherry-picked into the r/stx.3.0 branch. >> >> Thanks for your cooperation. >> >> Scott Little >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Frank.Miller at windriver.com Thu Nov 28 14:28:07 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 28 Nov 2019 14:28:07 +0000 Subject: [Starlingx-discuss] No Build meeting this week Message-ID: Please note there will not be a StarlingX build meeting. The next meeting is planned for Thursday Dec 5th. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Thu Nov 28 15:14:14 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 28 Nov 2019 15:14:14 +0000 Subject: [Starlingx-discuss] Problems downloading mirror in centos8 environment In-Reply-To: <000501d5a59d$9e154420$da3fcc60$@neusoft.com> References: <000501d5a59d$9e154420$da3fcc60$@neusoft.com> Message-ID: I am not familiar with those dnf commands. Normally the steps are: 1) Update the lst file in https://opendev.org/starlingx/tools that corresponds to the component you want to update. In your case, it sounds like changing the src rpm (and rpm) lines in: https://opendev.org/starlingx/tools/src/branch/master/centos-mirror-tools/rpms_centos.lst#L61 2) Perform a mirror update. This might be those dnf commands, but mainly you need to get that src rpm downloaded. In my env, it downloads to a mirror called /import/mirror/starlingx 3) Link the updated mirror files to your build env. This is what processes the lst files to know that you are using the newer bash src rpm, since the older version may also exist in your mirror folder. I think that is these steps: https://docs.starlingx.io/contributor/build_guide.html#build-the-centos-mirror-repository I typically run these 2 commands: $MY_REPO_ROOT_DIR/stx-tools/toCOPY/generate-cgcs-centos-repo.sh /import/mirrors/starlingx $MY_REPO_ROOT_DIR/stx-tools/toCOPY/populate_downloads.sh /import/mirrors/starlingx 4) Now you are ready to adjust the contents of the https://opendev.org/starlingx/compile/src/branch/master/languages/bash/centos/srpm_path 5) Probably the existing patches and metapatches we have for bash are invalid. You can try “build-srpms –edit bash” . If it does work, there is likely ‘fuzz’ in the patches that will need to be cleaned up. Al From: 付勇 [mailto:fuyong at neusoft.com] Sent: Wednesday, November 27, 2019 10:41 PM To: starlingx-discuss at lists.starlingx.io Cc: zhaos at neusoft.com; lilong-neu; cindy.xie at intel.com; shuicheng.lin at intel.com; austin.sun at intel.com; '张志国' Subject: [Starlingx-discuss] Problems downloading mirror in centos8 environment Hi StarlingX team I’m upgrading starlingx to centos8 and have a question to ask for help. problem: I cannot download the specified version of srpm through the dnf download --source command. Eg: About two weeks ago, I was able to download the bash-4.4.19-7.el8.src.rpm file through the “dnf download --source bash-4.4.19-7.el8” command in centos8. But now I cannot download the bash-4.4.19-7.el8.src.rpm file with this command, even if I can download it at http://vault.centos.org/8.0.1905/BaseOS/Source/SPackages/ . Error info: No package bash-4.4.19-7.el8.src available. Exiting due to strict setting. Error: No package bash-4.4.19-7.el8.src available. please contact me, If you have any good suggestions. Thank you Best Regards Wish you happy everyday! -------------------------------- Yong.Fu- Neusoft --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. --------------------------------------------------------------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Thu Nov 28 16:51:23 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Thu, 28 Nov 2019 16:51:23 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191128 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-28 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 ] --------------------------------------------------------- External and standar virtual were not executed due to network problems. regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Nov 28 17:20:02 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 28 Nov 2019 18:20:02 +0100 (CET) Subject: [Starlingx-discuss] StarlingX 2.0.1: Message-ID: <144012367.1530278.1574961602766@communicator.strato.com> Hi, I am trying to install StarlingX 2.0.1 bare metal. The run of the Ansible bootstrap playbook fails with error message below. Any idea what causes this problem? Thanks Marcel 2019-11-28 17:11:18,631 p=17901 u=root | fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/usr/local/bin/puppet-manifest-apply.sh", "/tmp/hieradata", "192.168.204.3", "controller", "ansible_bootstrap", ">", "/tmp/apply_manifest.log"], "delta": "0:04:52.704737", "end": "2019-11-28 17:11:18.619345", "msg": "non-zero return code", "rc": 1, "start": "2019-11-28 17:06:25.914608", "stderr": "cp: cannot stat ‘/tmp/hieradata/192.168.204.3.yaml’: No such file or directory\ncp: cannot stat ‘/tmp/hieradata/system.yaml’: No such file or directory\ncp: cannot stat ‘/tmp/hieradata/secure_system.yaml’: No such file or directory\ncp: cannot stat ‘>’: No such file or directory", "stderr_lines": ["cp: cannot stat ‘/tmp/hieradata/192.168.204.3.yaml’: No such file or directory", "cp: cannot stat ‘/tmp/hieradata/system.yaml’: No such file or directory", "cp: cannot stat ‘/tmp/hieradata/secure_system.yaml’: No such file or directory", "cp: cannot stat ‘>’: No such file or directory"], "stdout": "Applying puppet ansible_bootstrap manifest...\n[WARNING]\nWarnings found. See /var/log/puppet/2019-11-28-17-06-25_controller/puppet.log for details", "stdout_lines": ["Applying puppet ansible_bootstrap manifest...", "[WARNING]", "Warnings found. See /var/log/puppet/2019-11-28-17-06-25_controller/puppet.log for details"]} 2019-11-28 17:11:18,632 p=17901 u=root | PLAY RECAP ********************************************************************* 2019-11-28 17:11:18,632 p=17901 u=root | localhost : ok=75 changed=17 unreachable=0 failed=1 From elio.martinez.monroy at intel.com Thu Nov 28 17:44:39 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Thu, 28 Nov 2019 17:44:39 +0000 Subject: [Starlingx-discuss] Final Regression Cycle Message-ID: Hello guys, We were working in the Final regression TP, Please check the "Final Regression" tab https://docs.google.com/spreadsheets/d/1X085xI96M6PIeum87w6IEF11G-TG-W1OeGuAJWnrAWI/edit?usp=sharing Having a total of 69 manual TC + 93 automated TC. Please let us know if you have any comment. [cid:image001.png at 01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4914 bytes Desc: image001.png URL: From build.starlingx at gmail.com Thu Nov 28 21:05:02 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Nov 2019 16:05:02 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_container_setup - Build # 545 - Failure! Message-ID: <1730084239.398.1574975106139.JavaMail.javamailuser@localhost> Project: STX_BUILD_container_setup Build #: 545 Status: Failure Timestamp: 20191128T210459Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191128T210322Z/logs -------------------------------------------------------------------------------- Parameters PROJECT: rc-3.0 MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20191128T210322Z DOCKER_BUILD_ID: jenkins-rc-3.0-20191128T210322Z-builder PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191128T210322Z/logs DOCKER_BUILD_TAG: rc-3.0-20191128T210322Z-builder-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20191128T210322Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 From build.starlingx at gmail.com Thu Nov 28 21:05:08 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Nov 2019 16:05:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 1 - Failure! Message-ID: <237593909.401.1574975109446.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 1 Status: Failure Timestamp: 20191128T210322Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191128T210322Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: true From austin.sun at intel.com Fri Nov 29 00:56:13 2019 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 29 Nov 2019 00:56:13 +0000 Subject: [Starlingx-discuss] StarlingX 2.0.1: In-Reply-To: <144012367.1530278.1574961602766@communicator.strato.com> References: <144012367.1530278.1574961602766@communicator.strato.com> Message-ID: Hi Marcel: Would you like to check if any warning is in /var/log/puppet/2019-11-28-17-06-25_controller/puppet.log ? BTW: Are you deploying AIO or multi ? What's type Hardware are you using bare metal ? CPU: The Model of CPU ? Disk: how many disk ? NIC: The Model of NIC Memory : how large it is ? Thanks. BR Austin Sun. -----Original Message----- From: Marcel Schaible Sent: Friday, November 29, 2019 1:20 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 2.0.1: Hi, I am trying to install StarlingX 2.0.1 bare metal. The run of the Ansible bootstrap playbook fails with error message below. Any idea what causes this problem? Thanks Marcel 2019-11-28 17:11:18,631 p=17901 u=root | fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["/usr/local/bin/puppet-manifest-apply.sh", "/tmp/hieradata", "192.168.204.3", "controller", "ansible_bootstrap", ">", "/tmp/apply_manifest.log"], "delta": "0:04:52.704737", "end": "2019-11-28 17:11:18.619345", "msg": "non-zero return code", "rc": 1, "start": "2019-11-28 17:06:25.914608", "stderr": "cp: cannot stat ‘/tmp/hieradata/192.168.204.3.yaml’: No such file or directory\ncp: cannot stat ‘/tmp/hieradata/system.yaml’: No such file or directory\ncp: cannot stat ‘/tmp/hieradata/secure_system.yaml’: No such file or directory\ncp: cannot stat ‘>’: No such file or directory", "stderr_lines": ["cp: cannot stat ‘/tmp/hieradata/192.168.204.3.yaml’: No such file or directory", "cp: cannot stat ‘/tmp/hieradata/system.yaml’: No such file or directory", "cp: cannot stat ‘/tmp/hieradata/secure_system.yaml’: No such file or directory", "cp: cannot stat ‘>’: No such file or directory"], "stdout": "Applying puppet ansible_bootstrap manifest...\n[WARNING]\nWarnings found. See /var/log/puppet/2019-11-28-17-06-25_controller/puppet.log for details", "stdout_lines": ["Applying puppet ansible_bootstrap manifest...", "[WARNING]", "Warnings found. See /var/log/puppet/2019-11-28-17-06-25_controller/puppet.log for details"]} 2019-11-28 17:11:18,632 p=17901 u=root | PLAY RECAP ********************************************************************* 2019-11-28 17:11:18,632 p=17901 u=root | localhost : ok=75 changed=17 unreachable=0 failed=1 _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Tao.Liu at windriver.com Fri Nov 29 01:07:22 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Fri, 29 Nov 2019 01:07:22 +0000 Subject: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. In-Reply-To: <4D7B8A1C-54B4-4535-8F04-505CF1B1D04A@99cloud.net> References: <29920834-BBA9-4DF0-83E6-8C0F8A1A9BDA@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED3FA6@ALA-MBD.corp.ad.wrs.com> <8688068F-A7DB-43F4-A0C0-D8A1D7776994@99cloud.net> <7242A3DC72E453498E3D783BBB134C3EA4ED50B0@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3EA4ED50C9@ALA-MBD.corp.ad.wrs.com> <4D7B8A1C-54B4-4535-8F04-505CF1B1D04A@99cloud.net> Message-ID: <7242A3DC72E453498E3D783BBB134C3EA4ED5502@ALA-MBD.corp.ad.wrs.com> Hi Kunpeng, Thank you for your initiative. Any feature request should be directed to Dariush Eslimi. Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 9:32 PM To: Liu, Tao Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Tao, I see, and I think connecting all in one network interface between central and subclouds possibility reduces network topology. I will keep eye on this feature, and hope to contribute something I can do. In addition, do you have or plan to make these yaml files about deploy_playbook and deploy_values? I have wrote a simple playbook to deploy and it work well in simplex, I think I can do this job, if you don’t have a plan for it. Kunpeng 在 2019年11月28日,01:22,Liu, Tao > 写道: A typo in the previous email: “This is a recommended method”. => This is not a recommended method. Tao From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Wednesday, November 27, 2019 12:14 PM To: 张鲲鹏 Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Kunpeng, As I stated previously, the Central Cloud’s Local Registry is exposed on the OAM interface. This is required to allow pushing images from a remote workstation to the Central Cloud, in addition to support bootstrapping via the OAM interface. As the document in the link below states, ”Using the management interface requires the creation of an additional temporary IP address/subnet on the management interface for bootstrapping”. This is not a recommended method. Using the OAM interface for bootstrapping means that OAM IP Subnets need to be routable between Central Cloud and Subclouds, and it does not require a direct physical connection. P.S. The MGMT IP subnets between Central Cloud and Subclouds are interconnected over Layer 3, not as part of an Layer 2 MGMT network. Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 11:38 AM To: Liu, Tao Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Tao, Thanks for your reply. But I haven’t understood why it is certral oam interface rather than mgmt interface to access registry.central. This guide[1] says the mgmt interface is okay to bootstrap in the section "install a subcloud" step 5. So if the registry.local can be accessed by mgmt network, wo don’t have to access the OAMs between central and subcloud. In addition, there is may only one interface that could be connected between central and subcloud in some case, and how to handle these cases with distributed cloud? 1. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 在 2019年11月27日,23:06,Liu, Tao > 写道: Hi Kunpeng, We made the decision to expose the Central Cloud’s Local Docker Registry on the OAM Interface for the following: 1. The OAM Interface and IP address are required to bootstrap the subcloud, and the default images can be pulled from the Central Cloud during the bootstrapping process 2. The OAM access to the Central Cloud’s Local Registry is required, to push images from a remote workstation to the Central Cloud Add the following override to pull the default images or any additional images from registry.central and store them to the subcloud’s local registry docker_registries: k8s.gcr.io: url: registry.central:9001/k8s.gcr.io gcr.io: url: registry.central:9001/gcr.io quay.io: url: registry.central:9001/quay.io docker.io: url: registry.central:9001/docker.io docker.elastic.co: url: registry.central:9001/docker.elastic.co defaults: type: docker username: admin password: Li69nux* additional_local_registry_images: - registry.central:9001/addition_image_name Tao From: 张鲲鹏 [mailto:zhang.kunpeng at 99cloud.net] Sent: Wednesday, November 27, 2019 4:40 AM To: starlingx-discuss at lists.starlingx.io; Liu, Tao Subject: [starlingx-discuss][distcloud] Some questions about how do subclouds use central cloud's local registry. Hi Distributed Cloud team, The distributed cloud feature is very cool, and I am concerned about its development always. There are some questions about subclouds access the central cloud's local reigistry. This is the lp link[1]. As we know, MGMT is the data synchronous network between central and subcloud, so subcloud's mgmt net must be connected with central's. But OAM network is used when subcloud to access the central's registry, so there are two networks or interfaces that subcloud should both access to central. I think it isn't appropriate to the distributed cases and the network will be complicated when to deploy the subcloud far away in geography. Why not use the mgmt network for subcloud to access central's local registry? I think you have your own consideration, can you share it? Another question, how to set bootstrap-values.yml[2] when to bootstrap subcloud with registry.central? 1. https://bugs.launchpad.net/starlingx/+bug/1846799 2. https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html#id8 Thanks Kunpeng _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From wei.w.hu at intel.com Fri Nov 29 04:59:09 2019 From: wei.w.hu at intel.com (Hu, Wei W) Date: Fri, 29 Nov 2019 04:59:09 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi, Distributed cloud team, May I know the current distributed cloud feature status? We want to set up this in our local lab as well. And I find the attached guide. Is there any best known method that we need be aware of before we start? From: Arce Moreno, Abraham Sent: Thursday, October 17, 2019 12:05 AM To: Liu, Tao ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Tao for sharing, We are taking this guide to replicate the setup in our labs and translate to RST format. We will add you as reviewer, feel free to add as many people as required. Best Regards Docs Team From: Liu, Tao > Sent: Wednesday, October 16, 2019 10:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Docs Team, Please add Distributed Cloud Configuration Guide to StarlingX R3.0 Installation. Regards, Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Distributed Cloud Configuration Guide_V2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 25456 bytes Desc: Distributed Cloud Configuration Guide_V2.docx URL: From austin.sun at intel.com Fri Nov 29 05:33:36 2019 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 29 Nov 2019 05:33:36 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Wei: The distributed cloud doc has been public to [1]. [1] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Hu, Wei W Sent: Friday, November 29, 2019 12:59 PM To: Arce Moreno, Abraham ; Liu, Tao ; starlingx-discuss at lists.starlingx.io Cc: Sun, Austin ; She, MinX ; Ren, YaruX Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi, Distributed cloud team, May I know the current distributed cloud feature status? We want to set up this in our local lab as well. And I find the attached guide. Is there any best known method that we need be aware of before we start? From: Arce Moreno, Abraham > Sent: Thursday, October 17, 2019 12:05 AM To: Liu, Tao >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Tao for sharing, We are taking this guide to replicate the setup in our labs and translate to RST format. We will add you as reviewer, feel free to add as many people as required. Best Regards Docs Team From: Liu, Tao > Sent: Wednesday, October 16, 2019 10:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Docs Team, Please add Distributed Cloud Configuration Guide to StarlingX R3.0 Installation. Regards, Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Nov 29 05:47:59 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 29 Nov 2019 05:47:59 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * 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 << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From wei.w.hu at intel.com Fri Nov 29 05:55:00 2019 From: wei.w.hu at intel.com (Hu, Wei W) Date: Fri, 29 Nov 2019 05:55:00 +0000 Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 In-Reply-To: References: <7242A3DC72E453498E3D783BBB134C3EA4EAFB8F@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks, Austin. We will give it a try. From: Sun, Austin Sent: Friday, November 29, 2019 1:34 PM To: Hu, Wei W ; Arce Moreno, Abraham ; Liu, Tao ; starlingx-discuss at lists.starlingx.io Cc: She, MinX ; Ren, YaruX Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Wei: The distributed cloud doc has been public to [1]. [1] https://docs.starlingx.io/deploy_install_guides/r3_release/distributed_cloud/index.html Thanks. BR Austin Sun. From: Hu, Wei W > Sent: Friday, November 29, 2019 12:59 PM To: Arce Moreno, Abraham >; Liu, Tao >; starlingx-discuss at lists.starlingx.io Cc: Sun, Austin >; She, MinX >; Ren, YaruX > Subject: RE: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi, Distributed cloud team, May I know the current distributed cloud feature status? We want to set up this in our local lab as well. And I find the attached guide. Is there any best known method that we need be aware of before we start? From: Arce Moreno, Abraham > Sent: Thursday, October 17, 2019 12:05 AM To: Liu, Tao >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Thanks Tao for sharing, We are taking this guide to replicate the setup in our labs and translate to RST format. We will add you as reviewer, feel free to add as many people as required. Best Regards Docs Team From: Liu, Tao > Sent: Wednesday, October 16, 2019 10:27 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX distributed cloud documentation for R3.0 Hi Docs Team, Please add Distributed Cloud Configuration Guide to StarlingX R3.0 Installation. Regards, Tao Liu, Member of Technical Staff, Engineering,, Wind River direct 613.963.1413 fax: 613.492.7870 skype: tao_at_home 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Fri Nov 29 06:41:53 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 29 Nov 2019 01:41:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 519 - Failure! Message-ID: <10922116.405.1575009714724.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 519 Status: Failure Timestamp: 20191129T063805Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20191129T023000Z DOCKER_BUILD_ID: jenkins-rc-3.0-20191129T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs MASTER_JOB_NAME: STX_BUILD_3.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 From build.starlingx at gmail.com Fri Nov 29 06:41:57 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 29 Nov 2019 01:41:57 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 2 - Still Failing! In-Reply-To: <1928842254.399.1574975106932.JavaMail.javamailuser@localhost> References: <1928842254.399.1574975106932.JavaMail.javamailuser@localhost> Message-ID: <1379660491.408.1575009718395.JavaMail.javamailuser@localhost> Project: STX_BUILD_3.0 Build #: 2 Status: Still Failing Timestamp: 20191129T023000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS_DEV: false BUILD_CONTAINERS_STABLE: false From build.starlingx at gmail.com Fri Nov 29 06:42:18 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 29 Nov 2019 01:42:18 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_lst_audit - Build # 202 - Failure! Message-ID: <713293217.411.1575009739354.JavaMail.javamailuser@localhost> Project: STX_build_lst_audit Build #: 202 Status: Failure Timestamp: 20191129T063810Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/rc-3.0/20191129T023000Z DOCKER_BUILD_ID: jenkins-rc-3.0-20191129T023000Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/rc-3.0/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/rc/3.0/centos/20191129T023000Z/logs MASTER_JOB_NAME: STX_BUILD_3.0 MY_REPO_ROOT: /localdisk/designer/jenkins/rc-3.0 PUBLISH_DISTRO_BASE: /export/mirror/starlingx/rc/3.0/centos From chengxubein at gmail.com Fri Nov 29 07:44:03 2019 From: chengxubein at gmail.com (xuebin) Date: Fri, 29 Nov 2019 15:44:03 +0800 Subject: [Starlingx-discuss] About the ceph network Message-ID: <5de0cc47.1c69fb81.cd91d.7c13@mx.google.com> Hi All, I have installed starlingx in the Aio-DX mode. when i configured the ceph, i find the public network and the cluster network of ceph share the mgmt network of starlingx. i want to know if starlingx provides the method to split the public network and cluster network into different physical network . 发送自 Windows 10 版邮件应用 -------------- next part -------------- An HTML attachment was scrubbed... URL: From teshan at vizuamatix.com Fri Nov 29 08:54:17 2019 From: teshan at vizuamatix.com (Teshan Senaratne) Date: Fri, 29 Nov 2019 14:24:17 +0530 Subject: [Starlingx-discuss] StarlingX installation Error Message-ID: Hi All, I tried installing starlingX simplex baremetal version on a Dell PowerEdge R810 server. It has more than the specs required, except for the SSDs. It only has 6 x 500GB SATA disks which I configured into 3 arrays of raid 2. Once I started the installation by selecting the bootable pendrive it gives me the following error. Warning: dracut-initqueue timeout - starting timeout scripts ----> (this repeats for a while, and then) Warning: Could not boot. Starting Dracut Emergency Shell... Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. dracut:/# Any idea on how to mitigate this? -- Thanks & Regards, *Teshan Senaratne* Systems Engineer - Enterprise Support *Head office : 60 School Lane, Nawala, Rajagiriya, Sri Lanka.* *Mobile : +94 71 06 999 06 | Tel : +94 112 889 321* *Email : teshan at vizuamatix.com **Web : **www.vizuamatix.com * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Fri Nov 29 09:09:19 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Fri, 29 Nov 2019 03:09:19 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: <412985$5ug2ck@orsmga007.jf.intel.com> List of docker images required for "platform-integ-apps": BUILD_ID="20191129T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From shuicheng.lin at intel.com Fri Nov 29 12:13:20 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 29 Nov 2019 12:13:20 +0000 Subject: [Starlingx-discuss] StarlingX installation Error In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608E9E83@SHSMSX105.ccr.corp.intel.com> Hi Teshan, It should be relate to the pendrive creation. Please follow instruction in below link to create the bootable pendrive image. https://docs.starlingx.io/deploy_install_guides/bootable_usb.html I also find a history mail with similar issue for you reference: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002499.html Best Regards Shuicheng From: Teshan Senaratne Sent: Friday, November 29, 2019 4:54 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX installation Error Hi All, I tried installing starlingX simplex baremetal version on a Dell PowerEdge R810 server. It has more than the specs required, except for the SSDs. It only has 6 x 500GB SATA disks which I configured into 3 arrays of raid 2. Once I started the installation by selecting the bootable pendrive it gives me the following error. Warning: dracut-initqueue timeout - starting timeout scripts ----> (this repeats for a while, and then) Warning: Could not boot. Starting Dracut Emergency Shell... Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. dracut:/# Any idea on how to mitigate this? -- Thanks & Regards, Teshan Senaratne Systems Engineer - Enterprise Support [https://drive.google.com/a/vizuamatix.com/uc?id=1CKg2nrXcBAw9LuE5TLkOO408juMDLy6N&export=download] Head office : 60 School Lane, Nawala, Rajagiriya, Sri Lanka. Mobile : +94 71 06 999 06 | Tel : +94 112 889 321 Email : teshan at vizuamatix.com Web : www.vizuamatix.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Nov 29 15:56:49 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 29 Nov 2019 10:56:49 -0500 Subject: [Starlingx-discuss] [build-report] STX_BUILD_3.0 - Build # 1 - Failure! In-Reply-To: <237593909.401.1574975109446.JavaMail.javamailuser@localhost> References: <237593909.401.1574975109446.JavaMail.javamailuser@localhost> Message-ID: <50230d76-0760-f20f-cde4-c9d9fe6743e3@windriver.com> Cengn had two build issues on the new 3.0 branch. Root cause is a couple steps relating to the installer were out of order. It only impacts the first build when we have no internally built installer, and must use the stock Centos installer temporarily.  I've corrected the issue. Build 3 is underway. Scott On 2019-11-28 4:05 p.m., build.starlingx at gmail.com wrote: > Project: STX_BUILD_3.0 > Build #: 1 > Status: Failure > Timestamp: 20191128T210322Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/3.0/centos/20191128T210322Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS_DEV: false > BUILD_CONTAINERS_STABLE: true > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank.Miller at windriver.com Fri Nov 29 20:03:22 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 29 Nov 2019 20:03:22 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting In-Reply-To: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608E9D6B@SHSMSX105.ccr.corp.intel.com> Message-ID: Shuicheng: Thanks for the update. It looks like stx-openstack has not yet been tested with IPv6. But we have been testing IPv6 with kubernetes platform only and simple k8s apps. Can you confirm kata containers is working with IPv6 when stx-openstack is not applied/not used? Frank From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Friday, November 29, 2019 12:48 AM To: Miller, Frank ; starlingx-discuss at lists.starlingx.io Subject: RE: Minutes: StarlingX Containerization Meeting Hi Frank, I created below LP for the IPv6 deployment issue I meet. Could you help check whether IPv6 deployment is verfied before and share me the BKM for it if there is? Thanks. https://bugs.launchpad.net/starlingx/+bug/1854316 Best Regards Shuicheng From: Miller, Frank > Sent: Tuesday, November 26, 2019 11:37 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Minutes: StarlingX Containerization Meeting Abbreviated minutes: Next meeting: Tuesday Dec 10 Minutes: 1. Stx.3.0 gating LPs: * Plan for the current 18 gating LPs: * 4 LPs are expected to land for stx.3.0 including the 2 Highs * 2 LPs to be marked invalid/not reproducible * 11 LPs to be re-gated to stx.4.0 * 1 LP TBD (Erich Cordoba to update 1824881) 2. Stx.4.0 features: In features: * 2006145: Kata container support [Shuicheng Lin] --> resourced and In for stx.4.0 * 2006537: Decouple Container Applications from Platform [Bob Church] --> resourced and In for stx.4.0 * 2006770: Backup & Restore - openstack [Ovidiu Poncea] --> resourced and In for stx.4.0 * 2005312: Containerize Openstack clients --> In for now but requires plan * TBD: Upversion Kubernetes and container platform components --> haven't create SB yet but will be required during stx.4.0 NOT In features: * 2006787: Smaller memory node support [Austin Sun] --> not committed for stx.4.0 but being worked on for stx.4.0 (ie: prep) * 2004008: Fault Containerization --> not In because it requires splitting GUI plugin into 2: one with shared panels, the other with the platform panels which is not resourced Etherpad with full minutes: https://etherpad.openstack.org/p/stx-containerization Frank -----Original Appointment----- From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Monday, November 25, 2019 3:03 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX Containerization Meeting When: Tuesday, November 26, 2019 9:30 AM-10:00 AM (UTC-05:00) Eastern Time (US & Canada). Where: https://zoom.us/j/342730236 Please join me for the bi-weekly containers meeting. Agenda for November 26 meeting: 1. stx.3.0 gating work items: 18 gating LPs (down from 26 at our last meeting) * Status update for high priority LPs (2): * https://bugs.launchpad.net/starlingx/+bug/1838659 kubernetes apiserver certificate needs rotation [Mingyuan Qi] * https://bugs.launchpad.net/starlingx/+bug/1851287 Controller failed to lock following a failover due to elastic pod failure to shutdown [Dan Voiculeasa] * Medium priority LPs (16): * Status for the 4 LPs < 50 days old: * https://bugs.launchpad.net/starlingx/+bug/1851294 [Angie Wang] * https://bugs.launchpad.net/starlingx/+bug/1850438 [Steve Webster] * https://bugs.launchpad.net/starlingx/+bug/1850189 [Stefan Dinescu] * https://bugs.launchpad.net/starlingx/+bug/1846829 [David Sullivan] * Status update for the 12 LPs that >100 days old. [Al, Angie, Bart, Erich, JimG, Ran, Shuicheng, Tao] * Can any be closed as not reproducible or won't fix? * Which ones are being actively worked on? Which ones do the owners have a plan to fix? 2. stx.4.0 planning: * 2006145: Kata container support [Shuicheng Lin] - Request update from Shuicheng if final 2 test scenarios are done (IPv6 testing + external registry with username/pwd authentication) * 2006787: Smaller memory node support, aka containerize flock services [Austin Sun] - Request feature approach & spec update * 2006537: Decouple Container Applications from Platform (stx.4.0 feature) [Bob Church] - Feature status update * Other potential stx.4.0 features --> which are resourced/have plans to address in stx.4.0? * 2006770: Backup & Restore - openstack [Ovidiu Poncea] * 2005312: Containerize Openstack clients * 2004008: Fault Containerization * TBD: Upversion Kubernetes and container platform components Etherpad: https://etherpad.openstack.org/p/stx-containerization Timeslot: 9:30am EST / 6:30am PDT / 1430 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: * Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 * Meeting ID: 342 730 236 * 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 << File: ATT00002.txt >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From maria.g.perez.ibarra at intel.com Fri Nov 29 21:32:24 2019 From: maria.g.perez.ibarra at intel.com (Perez Ibarra, Maria G) Date: Fri, 29 Nov 2019 21:32:24 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20191129 Message-ID: Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-November-29 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal 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 - 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 - 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 is executed in a Containers - 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 - 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 - 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 ] List of docker images : http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/007115.html regards Maria G -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Mon Nov 25 08:32:15 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 25 Nov 2019 08:32:15 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin Sent: 06 November 2019 09:35 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Mon Nov 25 09:04:23 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 25 Nov 2019 09:04:23 +0000 Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi, This is also throwing error. I have run this command with -debug controller-0:~$ gnocchi --debug --endpoint gnocchi.openstack.svc.cluster.local metric list REQ: curl -g -i -X GET gnocchi.openstack.svc.cluster.local/v1/metric? -H "Accept: application/json, */*" -H "Authorization: {SHA256}c4af6d2f99d2fcbb0e1c144c75c64623d2b00ce78fbf0b06a9201e9b0019f287" -H "User-Agent: gnocchi keystoneauth1/0.0.0 python-requests/2.21.0 CPython/2.7.5" Unexpected exception for gnocchi.openstack.svc.cluster.local/v1/metric?: Invalid URL 'gnocchi.openstack.svc.cluster.local/v1/metric?': No schema supplied. Perhaps you meant http://gnocchi.openstack.svc.cluster.local/v1/metric?? Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/cliff/app.py", line 402, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python2.7/site-packages/cliff/display.py", line 116, in run column_names, data = self.take_action(parsed_args) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/metric_cli.py", line 58, in take_action **utils.get_pagination_options(parsed_args)) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/metric.py", line 51, in list page = self._get(page_url) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/base.py", line 37, in _get return self.client.api.get(*args, **kwargs) File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 375, in get return self.request(url, 'GET', **kwargs) File "/usr/lib/python2.7/site-packages/gnocchiclient/client.py", line 44, in request message=str(e), url=url, method=method) UnknownConnectionError: Unexpected exception for gnocchi.openstack.svc.cluster.local/v1/metric?: Invalid URL 'gnocchi.openstack.svc.cluster.local/v1/metric?': No schema supplied. Perhaps you meant http://gnocchi.openstack.svc.cluster.local/v1/metric?? Traceback (most recent call last): File "/usr/bin/gnocchi", line 10, in sys.exit(main()) File "/usr/lib/python2.7/site-packages/gnocchiclient/shell.py", line 252, in main return GnocchiShell().run(args) File "/usr/lib/python2.7/site-packages/cliff/app.py", line 281, in run result = self.run_subcommand(remainder) File "/usr/lib/python2.7/site-packages/cliff/app.py", line 402, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python2.7/site-packages/cliff/display.py", line 116, in run column_names, data = self.take_action(parsed_args) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/metric_cli.py", line 58, in take_action **utils.get_pagination_options(parsed_args)) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/metric.py", line 51, in list page = self._get(page_url) File "/usr/lib/python2.7/site-packages/gnocchiclient/v1/base.py", line 37, in _get return self.client.api.get(*args, **kwargs) File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 375, in get return self.request(url, 'GET', **kwargs) File "/usr/lib/python2.7/site-packages/gnocchiclient/client.py", line 44, in request message=str(e), url=url, method=method) gnocchiclient.exceptions.UnknownConnectionError: Unexpected exception for gnocchi.openstack.svc.cluster.local/v1/metric?: Invalid URL 'gnocchi.openstack.svc.cluster.local/v1/metric?': No schema supplied. Perhaps you meant http://gnocchi.openstack.svc.cluster.local/v1/metric?? From: Sun, Austin Sent: 25 November 2019 14:30 To: Anirudh Gupta ; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: >From your log, it seems gnocchi is still searching local endpoint. Would you like run "gnocchi -endpoint " ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Mon Nov 25 10:54:58 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Mon, 25 Nov 2019 10:54:58 +0000 Subject: [Starlingx-discuss] [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Hi Mingyuan, Thanks for your response. I am able to access it using "openstack metric list/openstack metric resource list ". There is no "cpu_util" metric available in the list. How can I enable that parameter in StarlingX 2.0? Regards Anirudh Gupta From: Qi, Mingyuan Sent: 25 November 2019 16:21 To: Sun, Austin ; Anirudh Gupta ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Anirudh, I don't think the gnocchi client got the right api url(localhost:8041), if you check the openstack endpoints, gnocchi internal interface should be http://gnocchi-api.openstack.svc.cluster.local:8041/ Could you check the openstack client for gnocchi which is "openstack metric list/openstack metric resource list ", to verify that gnocchi is in-service? Mingyuan From: Sun, Austin > Sent: Monday, November 25, 2019 17:00 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: Re: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: >From your log, it seems gnocchi is still searching local endpoint. Would you like run "gnocchi -endpoint " ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of "kubectl describe po ceilometer-xxxx -n openstack" Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command "system helm-chart-attribute-modify" to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn't have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM's being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM's spawned. It is a must requirement for my setup as I need to Auto scale my VNF's based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Nov 26 03:01:53 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 26 Nov 2019 03:01:53 +0000 Subject: [Starlingx-discuss] [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 In-Reply-To: References: Message-ID: Thanks for your help 😊 From: Sun, Austin Sent: 25 November 2019 18:45 To: Anirudh Gupta ; Qi, Mingyuan ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: From reference[1], cpu_util is deprecated from openstack stein version which is stx.2.0 using. [1] https://github.com/openstack/ceilometer/blob/4ae919c96e4116ab83e5d83f2b726ed44d165278/releasenotes/notes/save-rate-in-gnocchi-66244262bc4b7842.yaml Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 6:55 PM To: Qi, Mingyuan >; Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Mingyuan, Thanks for your response. I am able to access it using “openstack metric list/openstack metric resource list ”. There is no “cpu_util” metric available in the list. How can I enable that parameter in StarlingX 2.0? Regards Anirudh Gupta From: Qi, Mingyuan > Sent: 25 November 2019 16:21 To: Sun, Austin >; Anirudh Gupta >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Anirudh, I don’t think the gnocchi client got the right api url(localhost:8041), if you check the openstack endpoints, gnocchi internal interface should be http://gnocchi-api.openstack.svc.cluster.local:8041/ Could you check the openstack client for gnocchi which is “openstack metric list/openstack metric resource list ”, to verify that gnocchi is in-service? Mingyuan From: Sun, Austin > Sent: Monday, November 25, 2019 17:00 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: Re: [Starlingx-announce] No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: From your log, it seems gnocchi is still searching local endpoint. Would you like run “gnocchi –endpoint ” ? to check if it can work. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 25, 2019 4:32 PM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin, I have successfully installed the Telemetry Services (ceilometer, aodh, gnocchi, panko) in StarlingX 2.0. controller-0:~$ openstack endpoint list | grep -i public | 0bda50532d44492dbf5b863b141ffaba | RegionOne | panko | event | True | public | http://panko.openstack.svc.cluster.local:80/ | | 14d6afd669a64875b6f0b2f05381ad6d | RegionOne | heat-cfn | cloudformation | True | public | http://cloudformation.openstack.svc.cluster.local:80/v1 | | 1715c6801ba441859bc29f7d628e94af | RegionOne | heat | orchestration | True | public | http://heat.openstack.svc.cluster.local:80/v1/%(project_id)s | | 273b56c7201d471785b880490b4eaedb | RegionOne | gnocchi | metric | True | public | http://gnocchi.openstack.svc.cluster.local:80/ | | 3e64a4a8cc1e46df94a6926eb3927c2b | RegionOne | cinderv3 | volumev3 | True | public | http://cinder.openstack.svc.cluster.local:80/v3/%(tenant_id)s | | 5139fb770acc40e2b7d31c36e835ae4f | RegionOne | neutron | network | True | public | http://neutron.openstack.svc.cluster.local:80/ | | 66eac8f208494e50b8b669ce34ad89f1 | RegionOne | aodh | alarming | True | public | http://aodh.openstack.svc.cluster.local:80/ | | 69087f47c5fd4f8bac32615a1a10b988 | RegionOne | placement | placement | True | public | http://placement.openstack.svc.cluster.local:80/ | | 7e116069695247d0bcd3d105831a4c13 | RegionOne | cinderv2 | volumev2 | True | public | http://cinder.openstack.svc.cluster.local:80/v2/%(tenant_id)s | | a52a66881fa74faaa1cf216359782331 | RegionOne | nova | compute | True | public | http://nova.openstack.svc.cluster.local:80/v2.1/%(tenant_id)s | | a7f8817df669449ca831d92ef2c491d4 | RegionOne | cinder | volume | True | public | http://cinder.openstack.svc.cluster.local:80/v1/%(tenant_id)s | | abbfef67633440d3a97d42cce0e99282 | RegionOne | keystone | identity | True | public | http://keystone.openstack.svc.cluster.local:80/v3 | | ed3bb30c2e4f44018dbe5ae9ee3d7e02 | RegionOne | glance | image | True | public | http://glance.openstack.svc.cluster.local:80/ When I am trying to access gnocchi metrics or running any gnocchi command, I am facing the below error controller-0:~$ gnocchi metric list Unable to establish connection to http://localhost:8041/v1/metric?: HTTPConnectionPool(host='localhost', port=8041): Max retries exceeded with url: /v1/metric (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) Can you please suggest some pointers to resolve this issue Regards Anirudh Gupta From: Sun, Austin > Sent: 06 November 2019 09:35 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: OK. could you check why some pods is not running ? kubectl get po -n openstack | grep ceilometer if some pods are still Init or failed ? you can check the dependence or events of the output of “kubectl describe po ceilometer-xxxx -n openstack” Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Wednesday, November 6, 2019 11:43 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Austin I have enabled Ceilometer, Gnocchi and Aodh helm charts using the command suggested and then applied stx-openstack. But now I am facing exception in deploying ceilometer chart. There is timeout error in Ceilometer Pod. Timed out waiting for pods (namespace=openstack, labels=(release_group=osh-openstack-ceilometer)). These pods were not ready=['ceilometer-notification-7548b6db79-fhzfq'] armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['openstack-ceilometer'] I am also attaching the logs for your reference. Please suggest the alternative to resolve the issue. Regards Anirudh Gupta From: Sun, Austin > Sent: 04 November 2019 19:16 To: Anirudh Gupta >; starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: RE: No Telemetry Service Installed in StarlingX 2.0 Hi Gupta: By default , telemetry services are disabled (chart is not enabled) , but you can enable it by command “system helm-chart-attribute-modify” to enable it. Thanks. BR Austin Sun. From: Anirudh Gupta > Sent: Monday, November 4, 2019 7:19 PM To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: [Starlingx-discuss] No Telemetry Service Installed in StarlingX 2.0 Hi Team, StarlingX 2.0 release doesn’t have any endpoint for any Telemetry services like Ceilometer, Gnocchi and Aodh, because of which we are unable to get the metric values corresponding to the VM’s being spawned of StarlingX. However this was not the case with StarlingX 2018.10 release. It had all the support for Telemetry Services, from which I was able to get CPU_Util and Mem_util of the VM’s spawned. It is a must requirement for my setup as I need to Auto scale my VNF’s based on the metric values. Please suggest the ways to install it. Regards Anirudh Gupta 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. 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. 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Tue Nov 26 05:00:13 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Tue, 26 Nov 2019 05:00:13 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA Message-ID: Hi Team, I need to install StarlingX 2.0 Duplex Bare Metal. As per the document, there can be 2 modes in which HA controllers can be configure i.e. either "active/active" or "active/standby" https://docs.starlingx.io/deploy_install_guides/r2_release/bare_metal/aio_duplex.html Can someone please suggest the steps to configure Active-Active state? And, what difference it would have on my deployment in terms of functionality? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Wed Nov 27 10:18:16 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Wed, 27 Nov 2019 10:18:16 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality In-Reply-To: <151EE31B9FCCA54397A757BC674650F0C15FD011@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC007B2BA68@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0C15FD011@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Ghada, I can discuss with my team members for contributing towards StarlingX development. Can you please respond below to my queries : * What would be the plan of execution? * What would be the scope of work for us? Regards Anirudh Gupta From: Khalil, Ghada Sent: 26 November 2019 04:35 To: Zvonar, Bill ; Anirudh Gupta ; starlingx-discuss at lists.starlingx.io Cc: Hu, Yong Subject: RE: StarlingX 2.0 Release Upgrade Functionality Hi Anirudh, We are in the planning phase for stx.4.0 and are looking for developers from the community to look at implementing openstack upgrades with minimal down time. If this is something your team is interested in taking on, I invite you to participate in the distro.openstack meeting to discuss next steps. Thanks, Ghada From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Wednesday, November 20, 2019 8:57 AM To: Anirudh Gupta; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Anirudh, don't know if you got an answer directly, but this is not supported. Bill... From: Anirudh Gupta > Sent: Monday, November 11, 2019 3:47 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX 2.0 Release Upgrade Functionality Hi Team, I have installed StarlingX 2.0 on Bare metal. It is based on Openstack Stein Release. Is there any option in StarlingX to upgrade the existing Stein Release to latest Train Release with zero down time? Please suggest the steps to do so? Regards Anirudh Gupta 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Anirudh.Gupta at hsc.com Thu Nov 28 03:45:14 2019 From: Anirudh.Gupta at hsc.com (Anirudh Gupta) Date: Thu, 28 Nov 2019 03:45:14 +0000 Subject: [Starlingx-discuss] StarlingX 2.0 Duplex Controller in Active/Active HA In-Reply-To: References: Message-ID: Hi Team, Can someone please give me any update on my Query: I need to install StarlingX 2.0 Duplex Bare Metal. As per the document, there can be 2 modes in which HA controllers can be configure i.e. either "active/active" or "active/standby" https://docs.starlingx.io/deploy_install_guides/r2_release/bare_metal/aio_duplex.html * Can someone please suggest the steps to configure Active-Active state? * I have 2 kubernetes pods corresponding to each Openstack Service in Duplex Setup and when I spawn any VM, it goes on any of the two controllers. So, is this the standard implementation in StarlingX? What needs to be done in Active-Standby configuration? * And, what difference it would have on my deployment in terms of functionality? Regards Anirudh Gupta From: Anirudh Gupta Sent: 26 November 2019 10:30 To: starlingx-discuss at lists.starlingx.io; starlingx-announce at lists.starlingx.io Subject: StarlingX 2.0 Duplex Controller in Active/Active HA Hi Team, I need to install StarlingX 2.0 Duplex Bare Metal. As per the document, there can be 2 modes in which HA controllers can be configure i.e. either "active/active" or "active/standby" https://docs.starlingx.io/deploy_install_guides/r2_release/bare_metal/aio_duplex.html Can someone please suggest the steps to configure Active-Active state? And, what difference it would have on my deployment in terms of functionality? Regards Anirudh Gupta 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiinting at gmail.com Thu Nov 28 03:58:49 2019 From: chiinting at gmail.com (Chiing-Ting Huang) Date: Thu, 28 Nov 2019 11:58:49 +0800 Subject: [Starlingx-discuss] Yum CentOS-Base.repo Message-ID: Dear StarlingX team I need yum install and I find out that StarlingX R2.0 lost /etc/yum.repos.d/CentOS-Base.repo I add the CentOS-Base.repo, and yum work. But it make system unstable. When I reboot system, watchdog will reboot again and again. How can I use yum resource? Best regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From huifeng.le at intel.com Thu Nov 28 15:02:24 2019 From: huifeng.le at intel.com (Le, Huifeng) Date: Thu, 28 Nov 2019 15:02:24 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 11/28 Message-ID: <76647BD697F40748B1FA4F56DA02AA0B4D64BF03@SHSMSX104.ccr.corp.intel.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Nov 28/2019 * stx.3.0 Bugs: All open issues should try with latest daily build with train patch (ISO 20191115: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-November/006973.html) * Deadline for bug resolution: End of Nov * Query: https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=stx.networking+stx.3.0&field.tags_combinator=ALL&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search * High: ? https://bugs.launchpad.net/starlingx/+bug/1841189 ping to vm fails in live migration test - Gongjun * Need sync on the detail test steps, steven will help to get more detail from WR'a team ? https://bugs.launchpad.net/starlingx/+bug/1853907 Router interfaces down and VM unreachable after changing neutron router to DVR then back to centralized - Marvin * can`t reproduce, need check test steps with reporter. do the test on multiple node system again. * Medium: ? https://bugs.launchpad.net/starlingx/+bug/1818118 Containers: vm unreachable for minutes after live migration or vm reboot - Joseph - retested with train ? https://bugs.launchpad.net/starlingx/+bug/1821026 Containers: Resolving hostname fails within nova containers leading to config_drive VM migration failures - retested with train - fupingxie ? https://bugs.launchpad.net/starlingx/+bug/1841448 compute-0 host lock failed vim_progress_status is services-disable-failed - Yaole * This bug cannot be reproduced in the 1125 built image. Marked as invalid. * stx 3.0 features * Openstack Rebase to Train ? on track from the release meeting update * stx.4.0 Feature Proposals: https://etherpad.openstack.org/p/stx.4.0-feature-candidates * Milestones: https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=1107209846 ? Milestone-1 1/24/2020 ? Milestone-2 3/27/2020 ? Milestone-3 5/15/2020 ? Feature Test 5/29/2020 ? Regression Test TBD ? RC1 6/12/2020 ? Final Regression TBD ? Release 7/3/2020 * Tentative Release Milestones/Timeline: ? Depend on Kata container support * Containerize OVS-DPDK (cheng): propose for 4.0 ? https://review.opendev.org/#/c/694188 , ovs chart patch, this patch is in progress ? https://review.opendev.org/#/c/696437/ , import OVS-DPDK patches, cherry-pick latest ovs-dpdk feature patch from openstack-helm-infra into STX, Can we consider to upgrade the openstack-helm version in 4.0? - Check with Frank on the 4.0 plan * IPv6 PXE boot network support: https://storyboard.openstack.org/#!/story/2006442 - Huang, XiangDong * OVS collectd resource monitoring: Chenjie ? https://storyboard.openstack.org/#!/story/2002948 - Monitor other features besides interface/port * Monitor datanetwork for non openstack worker node by link monitor Marvin o Patch submitted: https://review.opendev.org/#/c/695390/, https://review.opendev.org/#/c/695391/, https://review.opendev.org/#/c/694940/, https://review.opendev.org/#/c/694927/ * Open from Neusoft (Shuai) have issue for ping connectivity, will sync by mail offline _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From chiinting at gmail.com Fri Nov 29 09:29:44 2019 From: chiinting at gmail.com (Chiing-Ting Huang) Date: Fri, 29 Nov 2019 17:29:44 +0800 Subject: [Starlingx-discuss] create network issue Message-ID: Dear StarlingX team When I create openstack as below. controller-0:~$ openstack network create --project ${ADMINID} --provider-network-type=flat --provider-physical-network=phy-flat netflat Error while executing command: BadRequestException: 400, Invalid input for operation: Flat provider networks are disabled. I get "Flat provider networks are disabled" message, so I check neutron server pod log message. I cant understand " it is either malformed or otherwise incorrect " message. ------------------------------neutron server log message----------------------------------- 2019-11-29 09:10:01.840 15 INFO neutron.pecan_wsgi.hooks.translation [req-11f095b7-3785-4f2d-b686-63fa8be8894e 13a0469767aa4b3898fc617ca48dc17f 5dc1e20a2d4f41718169b48b3dc47f91 - default default] POST failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. 2019-11-29 09:10:01.840 15 INFO neutron.pecan_wsgi.hooks.translation [req-11f095b7-3785-4f2d-b686-63fa8be8894e 13a0469767aa4b3898fc617ca48dc17f 5dc1e20a2d4f41718169b48b3dc47f91 - default default] POST failed (client error): The server could not comply with the request since it is either malformed or otherwise incorrect. 2019-11-29 09:10:01.861 15 INFO neutron.wsgi [req-11f095b7-3785-4f2d-b686-63fa8be8894e 13a0469767aa4b3898fc617ca48dc17f 5dc1e20a2d4f41718169b48b3dc47f91 - default default] 10.100.37.32 "POST /v2.0/networks HTTP/1.1" status: 400 len: 344 time: 0.1304631 2019-11-29 09:10:01.861 15 INFO neutron.wsgi [req-11f095b7-3785-4f2d-b686-63fa8be8894e 13a0469767aa4b3898fc617ca48dc17f 5dc1e20a2d4f41718169b48b3dc47f91 - default default] 10.100.37.32 "POST /v2.0/networks HTTP/1.1" status: 400 len: 344 time: 0.1304631 --------------------------------------------------------------------------------------------------------- Best Regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Sat Nov 30 09:09:58 2019 From: cristopher.j.lemus.contreras at intel.com (cristopher.j.lemus.contreras at intel.com) Date: Sat, 30 Nov 2019 03:09:58 -0600 Subject: [Starlingx-discuss] StarlingX platform-integ-apps docker images Message-ID: List of docker images required for "platform-integ-apps": BUILD_ID="20191130T023000Z" rabbitmq:3.7-management k8s.gcr.io/kube-proxy:v1.16.2 k8s.gcr.io/kube-apiserver:v1.16.2 k8s.gcr.io/kube-scheduler:v1.16.2 k8s.gcr.io/kube-controller-manager:v1.16.2 k8s.gcr.io/etcd:3.3.15-0 k8s.gcr.io/coredns:1.6.2 quay.io/airshipit/armada:8a1638098f88d92bf799ef4934abe569789b885e-ubuntu_bionic quay.io/calico/node:v3.6.2 quay.io/calico/cni:v3.6.2 quay.io/calico/kube-controllers:v3.6.2 rabbitmq:3.7.13-management rabbitmq:3.7.13 gcr.io/kubernetes-helm/tiller:v2.13.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.23.0 openstackhelm/mariadb:10.2.18 quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11 quay.io/stackanetes/kubernetes-entrypoint:v0.3.1 mariadb:10.2.13 memcached:1.5.5 k8s.gcr.io/pause:3.1 quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.9.0 nginx:1.13.3 gcr.io/google_containers/defaultbackend:1.0 From shuicheng.lin at intel.com Sat Nov 30 11:52:24 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Sat, 30 Nov 2019 11:52:24 +0000 Subject: [Starlingx-discuss] Yum CentOS-Base.repo In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C76608EA08E@SHSMSX105.ccr.corp.intel.com> Hi Ting, Do you try to update or upgrade some RPMs with repo? Some packages are customized in STX, and should not be switched to CentOS version. You should use yum to install specific RPM only, not try to update/upgrade OS or generic RPMs. Best Regards Shuicheng From: Chiing-Ting Huang Sent: Thursday, November 28, 2019 11:59 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Yum CentOS-Base.repo Dear StarlingX team I need yum install and I find out that StarlingX R2.0 lost /etc/yum.repos.d/CentOS-Base.repo I add the CentOS-Base.repo, and yum work. But it make system unstable. When I reboot system, watchdog will reboot again and again. How can I use yum resource? Best regards Ting -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Sat Nov 30 13:27:28 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Sat, 30 Nov 2019 07:27:28 -0600 Subject: [Starlingx-discuss] Yum CentOS-Base.repo In-Reply-To: <9700A18779F35F49AF027300A49E7C76608EA08E@SHSMSX105.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C76608EA08E@SHSMSX105.ccr.corp.intel.com> Message-ID: Agree I had to install some extra RPMs a few weeks ago and the system keeps working of me but I did not update the system Regards On Sat, Nov 30, 2019 at 5:53 AM Lin, Shuicheng wrote: > > Hi Ting, > > Do you try to update or upgrade some RPMs with repo? > > Some packages are customized in STX, and should not be switched to CentOS version. > > You should use yum to install specific RPM only, not try to update/upgrade OS or generic RPMs. > > > > Best Regards > > Shuicheng > > > > From: Chiing-Ting Huang > Sent: Thursday, November 28, 2019 11:59 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Yum CentOS-Base.repo > > > > Dear StarlingX team > > > > I need yum install and I find out that StarlingX R2.0 lost /etc/yum.repos.d/CentOS-Base.repo > > I add the CentOS-Base.repo, and yum work. > > > > But it make system unstable. When I reboot system, watchdog will reboot again and again. > > > > How can I use yum resource? > > > > Best regards > > Ting > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss