From build.starlingx at gmail.com Fri Feb 1 06:00:37 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Feb 2019 01:00:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 149 - Failure! Message-ID: <1220202081.354.1549000838276.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 149 Status: Failure Timestamp: 20190201T060034Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190201T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190201T060000Z DOCKER_DL_ID: jenkins-master-20190201T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190201T060000Z/logs DOCKER_DL_TAG: master-20190201T060000Z-downloader-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190201T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Fri Feb 1 06:00:40 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Feb 2019 01:00:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 124 - Failure! Message-ID: <729108415.357.1549000841725.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 124 Status: Failure Timestamp: 20190201T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190201T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From mingyuan.qi at intel.com Fri Feb 1 07:10:50 2019 From: mingyuan.qi at intel.com (Qi, Mingyuan) Date: Fri, 1 Feb 2019 07:10:50 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A936853@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A936603@fmsmsx101.amr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A936853@fmsmsx101.amr.corp.intel.com> Message-ID: Jose, Looking into your log, it seems that coredns is not ready. Here is the workaround for it: 1. kubectl -n kube-system edit configmap coredns 2. remove "loop" line and save 3. kubectl -n kube-system delete rs {your-coredns-replicaset-name} Bart & Al, It's seems to be a real issue for users behind a proxy which I guess coredns is not able to access external nameserver and falls in loop. Could user specified nameserver to be updated to coredns? Mingyuan -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: Friday, February 1, 2019 1:31 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Deployment status Hi, I did some tests with the most recent ISO (01/31) that has already the changes to add a proxy on config_controller, still facing the below mentioned issues, I created a Launchpad [1] to track this. https://bugs.launchpad.net/starlingx/+bug/1814142 Regards, José > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: Wednesday, January 30, 2019 4:31 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Containers] Deployment status > > Hi All > > ** Virtual Environment ** > > I'm working on setting up a StarlingX deployment with containers as > described on [1] using proxies but I have faces some issues described below: > > - I have successfully completed all the steps until "system > application-apply stx-openstack" when the system becomes unstable, the > application-apply gets freezed in random pods until timeout of 30 min > is reached, I discovered that killing armada process and start again the "system application-apply" > the application advance until again is freezed in a random pod. > After some cycles the application is successfully completed. > > Here is a log [2] of one point when the process is freeze, the error > is always the same, the only element that changes is the pod and its > random, not always is the same pod. > > ===== > 019-01-30 17:24:13.364 11824 ERROR sysinv.conductor.kube_app [-] > Received a false positive response from Docker/Armada. Failed to apply > application manifest /manifests/stx-openstack-manifest-no-tests.yaml: > 2019- > 01-30 16:54:07.367 20554 DEBUG armada.handlers.document [-] Resolving > reference /manifests/stx-openstack-manifest-no-tests.yaml. > resolve_reference /usr/local/lib/python3.5/site- > packages/armada/handlers/document.py:49 > ===== > > -After is completed correctly I'm receiving failures on "Verify the > cluster endpoints" when running `openstack endpoint list`, I updated > the .yml file with the correct password but connection is not > established correctly. Here is the output [3]. > > ====== > controller-0:~$ openstack endpoint list Failed to discover available > identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. > Attempting to parse version from URL. > Unable to establish connection to > http://keystone.openstack.svc.cluster.local/v3/auth/tokens: > HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): > Max retries exceeded with url: /v3/auth/tokens (Caused by > NewConnectionError(' o n object at 0x7fe65ffb90d0>: Failed to establish a new connection: > [Errno -3] Temporary failure in name resolution',)) ====== > > 1. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > 2. http://paste.openstack.org/show/744277 > 3. http://paste.openstack.org/show/744281 > > Regards, > José > > > > _______________________________________________ > 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 build.starlingx at gmail.com Fri Feb 1 09:00:36 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Feb 2019 04:00:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 150 - Still Failing! In-Reply-To: <1630216181.352.1549000834781.JavaMail.javamailuser@localhost> References: <1630216181.352.1549000834781.JavaMail.javamailuser@localhost> Message-ID: <1680742667.360.1549011637136.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 150 Status: Still Failing Timestamp: 20190201T090033Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190201T090000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190201T090000Z DOCKER_DL_ID: jenkins-f-stein-20190201T090000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190201T090000Z/logs DOCKER_DL_TAG: f-stein-20190201T090000Z-downloader-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190201T090000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein From build.starlingx at gmail.com Fri Feb 1 09:00:40 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Fri, 1 Feb 2019 04:00:40 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_stein_master - Build # 38 - Failure! Message-ID: <1617447486.363.1549011641029.JavaMail.javamailuser@localhost> Project: STX_build_stein_master Build #: 38 Status: Failure Timestamp: 20190201T090000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190201T090000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From Barton.Wensley at windriver.com Fri Feb 1 13:31:53 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 1 Feb 2019 13:31:53 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A936603@fmsmsx101.amr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A936853@fmsmsx101.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA60E38@ALA-MBD.corp.ad.wrs.com> This is likely happening due to a bug in coredns when an upstream DNS server is not reachable (see https://github.com/coredns/coredns/pull/2255). We don't have this fix yet, so for now, the user must only configure nameservers that are reachable from the system being installed. Bart -----Original Message----- From: Qi, Mingyuan [mailto:mingyuan.qi at intel.com] Sent: February 1, 2019 2:11 AM To: Perez Carranza, Jose; starlingx-discuss at lists.starlingx.io; Bailey, Henry Albert (Al); Wensley, Barton Subject: RE: [Starlingx-discuss] [Containers] Deployment status Jose, Looking into your log, it seems that coredns is not ready. Here is the workaround for it: 1. kubectl -n kube-system edit configmap coredns 2. remove "loop" line and save 3. kubectl -n kube-system delete rs {your-coredns-replicaset-name} Bart & Al, It's seems to be a real issue for users behind a proxy which I guess coredns is not able to access external nameserver and falls in loop. Could user specified nameserver to be updated to coredns? Mingyuan -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: Friday, February 1, 2019 1:31 To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Deployment status Hi, I did some tests with the most recent ISO (01/31) that has already the changes to add a proxy on config_controller, still facing the below mentioned issues, I created a Launchpad [1] to track this. https://bugs.launchpad.net/starlingx/+bug/1814142 Regards, José > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: Wednesday, January 30, 2019 4:31 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Containers] Deployment status > > Hi All > > ** Virtual Environment ** > > I'm working on setting up a StarlingX deployment with containers as > described on [1] using proxies but I have faces some issues described below: > > - I have successfully completed all the steps until "system > application-apply stx-openstack" when the system becomes unstable, the > application-apply gets freezed in random pods until timeout of 30 min > is reached, I discovered that killing armada process and start again the "system application-apply" > the application advance until again is freezed in a random pod. > After some cycles the application is successfully completed. > > Here is a log [2] of one point when the process is freeze, the error > is always the same, the only element that changes is the pod and its > random, not always is the same pod. > > ===== > 019-01-30 17:24:13.364 11824 ERROR sysinv.conductor.kube_app [-] > Received a false positive response from Docker/Armada. Failed to apply > application manifest /manifests/stx-openstack-manifest-no-tests.yaml: > 2019- > 01-30 16:54:07.367 20554 DEBUG armada.handlers.document [-] Resolving > reference /manifests/stx-openstack-manifest-no-tests.yaml. > resolve_reference /usr/local/lib/python3.5/site- > packages/armada/handlers/document.py:49 > ===== > > -After is completed correctly I'm receiving failures on "Verify the > cluster endpoints" when running `openstack endpoint list`, I updated > the .yml file with the correct password but connection is not > established correctly. Here is the output [3]. > > ====== > controller-0:~$ openstack endpoint list Failed to discover available > identity versions when contacting http://keystone.openstack.svc.cluster.local/v3. > Attempting to parse version from URL. > Unable to establish connection to > http://keystone.openstack.svc.cluster.local/v3/auth/tokens: > HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): > Max retries exceeded with url: /v3/auth/tokens (Caused by > NewConnectionError(' o n object at 0x7fe65ffb90d0>: Failed to establish a new connection: > [Errno -3] Temporary failure in name resolution',)) ====== > > 1. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > 2. http://paste.openstack.org/show/744277 > 3. http://paste.openstack.org/show/744281 > > Regards, > José > > > > _______________________________________________ > 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 scott.little at windriver.com Fri Feb 1 14:49:32 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Feb 2019 09:49:32 -0500 Subject: [Starlingx-discuss] [build-report] STX_retag_docker_images - Build # 1 - Failure! In-Reply-To: <2011582452.350.1548970828277.JavaMail.javamailuser@localhost> References: <2011582452.350.1548970828277.JavaMail.javamailuser@localhost> Message-ID: <04a5aeab-17e5-eb7b-2cb7-70997c725c62@windriver.com> script fixed and rerun successfully. f-stein build at timestamp 20190131T182613Z is now complete. Scott On 2019-01-31 4:40 p.m., build.starlingx at gmail.com wrote: > Project: STX_retag_docker_images > Build #: 1 > Status: Failure > Timestamp: 20190131T214007Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190131T182613Z/logs > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > OLD_LATEST_PREFIX: dev > MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190131T182613Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root > BASE_VERSION: f-stein-20190131T182613Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190131T182613Z/logs > REGISTRY_USERID: slittlewrs > HOST: build.starlingx.cengn.ca > LATEST_PREFIX: f-stein > PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190131T182613Z/logs > RETAG_IMAGE_LIST: stx-libvirt > FLOCK_VERSION: f-stein-centos-master-20190131T182613Z > PREFIX: f-stein > OPENSTACK_RELEASE: master > TIMESTAMP: 20190131T182613Z > REGISTRY_ORG: starlingx > OLD_OPENSTACK_RELEASE: pike > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190131T182613Z/outputs > REGISTRY: docker.io > > _______________________________________________ > 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 scott.little at windriver.com Fri Feb 1 14:55:43 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 1 Feb 2019 09:55:43 -0500 Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 149 - Failure! In-Reply-To: <1220202081.354.1549000838276.JavaMail.javamailuser@localhost> References: <1220202081.354.1549000838276.JavaMail.javamailuser@localhost> Message-ID: Apologies for the noise.  This was a result of the previously mentioned experiment to double the retries and timeouts used by yum during docker build on cengn. Somehow a '}' became ')' during the cut-n-paste from my test script into jenkins. Scott On 2019-02-01 1:00 a.m., build.starlingx at gmail.com wrote: > Project: STX_DL_container_setup > Build #: 149 > Status: Failure > Timestamp: 20190201T060034Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190201T060000Z/logs > -------------------------------------------------------------------------------- > Parameters > > MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190201T060000Z > DOCKER_DL_ID: jenkins-master-20190201T060000Z-downloader > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190201T060000Z/logs > DOCKER_DL_TAG: master-20190201T060000Z-downloader-image > PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190201T060000Z/logs > MY_REPO_ROOT: /localdisk/designer/jenkins/master > > _______________________________________________ > 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 marcel at schaible-consulting.de Fri Feb 1 15:31:35 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 1 Feb 2019 16:31:35 +0100 (CET) Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration Message-ID: <1484346064.187533.1549035095571@communicator.strato.com> Hi, during installation when appling the configuration I'll get an error message from hiera: Configuration failed: Failed to update hiera configuration Configuration log and apply_manifet.log is attached below. Any idea or hint? Thanks Marcel localhost:~# config_controller System Configuration ==================== Enter Q at any prompt to abort... System date and time: --------------------- The system date and time must be set now. Note that UTC time must be used and that the date and time must be set as accurately as possible, even if NTP/PTP is to be configured later. Current system date and time (UTC): 2019-02-01 15:15:25 Is the current date and time correct? [y/n]: y Current system date and time will be used. System timezone: ---------------- The system timezone must be set now. The timezone must be a valid timezone from /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) Please input the timezone[UTC]:Europe/Berlin System Configuration: --------------------- System mode. Available options are: 1) duplex-direct - two node redundant configuration. Management and infrastructure networks are directly connected to peer ports 2) duplex - two node redundant configuration. 3) simplex - single node non-redundant configuration. System mode [duplex-direct]: PXEBoot Network: ---------------- The PXEBoot network is used for initial booting and installation of each node. IP addresses on this network are reachable only within the data center. The default configuration combines the PXEBoot network and the management network. If a separate PXEBoot network is used, it will share the management interface, which requires the management network to be placed on a VLAN. Configure a separate PXEBoot network [y/N]: Aborting configuration localhost:~# config_controller System Configuration ==================== Enter Q at any prompt to abort... System date and time: --------------------- The system date and time must be set now. Note that UTC time must be used and that the date and time must be set as accurately as possible, even if NTP/PTP is to be configured later. Current system date and time (UTC): 2019-02-01 15:15:40 Is the current date and time correct? [y/n]: y Current system date and time will be used. System timezone: ---------------- The system timezone must be set now. The timezone must be a valid timezone from /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) Please input the timezone[UTC]:Europe/Berlin System Configuration: --------------------- System mode. Available options are: 1) duplex-direct - two node redundant configuration. Management and infrastructure networks are directly connected to peer ports 2) duplex - two node redundant configuration. 3) simplex - single node non-redundant configuration. System mode [duplex-direct]: 1 PXEBoot Network: ---------------- The PXEBoot network is used for initial booting and installation of each node. IP addresses on this network are reachable only within the data center. The default configuration combines the PXEBoot network and the management network. If a separate PXEBoot network is used, it will share the management interface, which requires the management network to be placed on a VLAN. Configure a separate PXEBoot network [y/N]: N Management Network: ------------------- The management network is used for internal communication between platform components. IP addresses on this network are reachable only within the data center. A management bond interface provides redundant connections for the management network. It is strongly recommended to configure Management interface link aggregation, for All-in-one duplex-direct. Management interface link aggregation [y/N]: y Management interface [bond0]: Management interface MTU [1500]: Specify one of the bonding policies. Possible values are: 1) 802.3ad (LACP) policy 2) Active-backup policy Management interface bonding policy [802.3ad]: A maximum of 2 physical interfaces can be attached to the management interface. First management interface member [enp3s0f1]: enp8s20f4 Second management interface member []: enp8s20f5 Management subnet [192.168.204.0/24]: 172.27.1.0/24 Use entire management subnet [Y/n]: Y IP addresses can be assigned to hosts dynamically or a static IP address can be specified for each host. This choice applies to both the management network and infrastructure network (if configured). Warning: Selecting 'N', or static IP address allocation, disables automatic provisioning of new hosts in System Inventory, requiring the user to manually provision using the 'system host-add' command. Dynamic IP address allocation [Y/n]: Y Management Network Multicast subnet [239.1.1.0/28]: Infrastructure Network: ----------------------- The infrastructure network is used for internal communication between platform components to offload the management network of high bandwidth services. IP addresses on this network are reachable only within the data center. If a separate infrastructure interface is not configured the management network will be used. It is NOT recommended to configure infrastructure network for All-in- one duplex-direct. Configure an infrastructure interface [y/N]: N External OAM Network: --------------------- The external OAM network is used for management of the cloud. It also provides access to the platform APIs. IP addresses on this network are reachable outside the data center. An external OAM bond interface provides redundant connections for the OAM network. External OAM interface link aggregation [y/N]: y External OAM interface [bond1]: Configure an external OAM VLAN [y/N]: External OAM interface MTU [1500]: Specify one of the bonding policies. Possible values are: 1) Active-backup policy 2) Balanced XOR policy 3) 802.3ad (LACP) policy External OAM interface bonding policy [active-backup]: A maximum of 2 physical interfaces can be attached to the external OAM interface. First external OAM interface member [enp3s0f0]: enp7s16f1 Second external oam interface member []: enp7s16f7 External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 External OAM gateway address [10.62.150.1]: External OAM floating address [10.62.150.2]: External OAM address for first controller node [10.62.150.3]: 10.62.150.210 External OAM address for second controller node [10.62.150.211]: Cloud Authentication: ------------------------------- Configure a password for the Cloud admin user The Password must have a minimum length of 7 character, and conform to password complexity rules Create admin user password: Repeat admin user password: The following configuration will be applied: System Configuration -------------------- Time Zone: Europe/Berlin System mode: duplex-direct PXEBoot Network Configuration ----------------------------- Separate PXEBoot network not configured PXEBoot Controller floating hostname: pxecontroller Management Network Configuration -------------------------------- Management interface name: bond0 Management interface: bond0 Management interface MTU: 1500 Management ae member 0: enp8s20f4 Management ae member 1: enp8s20f5 Management ae policy : 802.3ad Management subnet: 172.27.1.0/24 Controller floating address: 172.27.1.2 Controller 0 address: 172.27.1.3 Controller 1 address: 172.27.1.4 NFS Management Address 1: 172.27.1.5 NFS Management Address 2: 172.27.1.6 Controller floating hostname: controller Controller hostname prefix: controller- OAM Controller floating hostname: oamcontroller Dynamic IP address allocation is selected Management multicast subnet: 239.1.1.0/28 Infrastructure Network Configuration ------------------------------------ Infrastructure interface not configured External OAM Network Configuration ---------------------------------- External OAM interface name: bond1 External OAM interface: bond1 External OAM interface MTU: 1500 External OAM ae member 0: enp7s16f1 External OAM ae member 1: enp7s16f7 External OAM ae policy : active-backup External OAM subnet: 10.62.150.0/24 External OAM gateway address: 10.62.150.1 External OAM floating address: 10.62.150.2 External OAM 0 address: 10.62.150.210 External OAM 1 address: 10.62.150.211 Apply the above configuration? [y/n]: y Applying configuration (this will take several minutes): 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... DONE 03/08: Persisting local configuration ... DONE 04/08: Populating initial system inventory ... DONE 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 2019-02-01 15:20:44.053 25508 TRACE sysinv Failed to update puppet hiera host config Configuration failed: Failed to update hiera configuration localhost:~# /tmp/apply_manifest.log: ======================== cp: cannot stat ‘/tmp/hieradata/172.27.1.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 Applying puppet bootstrap manifest... [DONE] ls /tmp/puppet/hieradata/ ========================= global.yaml personality.yaml secure_static.yaml static.yaml localhost:~# From serverascode at gmail.com Fri Feb 1 15:32:20 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 1 Feb 2019 10:32:20 -0500 Subject: [Starlingx-discuss] Contribution to the project. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BBFD18EB2@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD18F0D@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Javier, This doesn't help you much right now, but just to let you know we are in the process of trying to set up some tagging for our issues and work items that will show if they are good for new contributors and such, like what many other open source projects do. Watch the list for updates related to that project. Thanks, Curtis On Thu, Jan 31, 2019 at 6:04 PM Javier Romero wrote: > Hi Bruce, > > Thanks for your information. > > Will join the weekly call next Wednesday, now I'm checking the wiki and > docs of the project. > > I can use a VM with KVM hypervisor to run StarlingX, it has 8 cores and > 16 GB of RAM, but seens that 32 GB are needed at least. Will have to find > something else... > > > > > El jueves, 31 de enero de 2019, Jones, Bruce E > escribió: > >> Javier, thank you. I’m going to suggest a couple of things for you to >> try out, to get started. >> >> >> >> You can join our weekly community call. It’s on Wednesdays at 1400 UTC. >> Details are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. >> StarlingX is a big project so we’ve divided it up into sub-projects – each >> has a call of their own, listed on that page, that you could join as well. >> >> >> >> You should check out our wiki: https://wiki.openstack.org/wiki/StarlingX >> and our documentation https://docs.starlingx.io/ >> >> >> >> You can download and run a pre-built StarlingX image from here: >> http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ >> >> >> >> You can find some instructions on how to install the image here: >> https://docs.starlingx.io/installation_guide/index.html. The document >> needs some changes, which we are working on as part of the Documentation >> sub-project. You will need a VM on a machine with lots of memory and/or a >> dedicated system to boot the image on – the image installs an OS and all of >> StarlingX. >> >> >> >> Myself and the community will be happy to answer any questions you have. >> >> >> >> brucej >> >> >> >> *From:* Javier Romero [mailto:xavinux at gmail.com] >> *Sent:* Thursday, January 31, 2019 1:41 PM >> *To:* Jones, Bruce E >> *Cc:* starlingx-discuss at lists.starlingx.io >> *Subject:* Re: Contribution to the project. >> >> >> >> Thanks for your answer. >> >> >> >> Well maybe testing but please, let me know those parts where you need >> more help to see if I can be useful in any of them. >> >> >> >> Best Regards, >> >> >> >> >> >> El jueves, 31 de enero de 2019, Jones, Bruce E >> escribió: >> >> We’d love to have your help! What part of the project are you interested >> in? >> >> >> >> brucej >> >> >> >> *From:* Javier Romero [mailto:xavinux at gmail.com] >> *Sent:* Thursday, January 31, 2019 12:42 PM >> *To:* starlingx-discuss at lists.starlingx.io >> *Subject:* [Starlingx-discuss] Contribution to the project. >> >> Hi Team, >> >> >> >> My name is Javier and live in Buenos Aires, Argentina. >> >> >> >> Work in the Network Operations Center of an Internet Service Provider >> where I deploy and manage mission critical Linux Servers. >> >> >> >> Would like to know if there is something I can help with on the StarlingX >> project . >> >> >> >> Thanks for your attention. >> >> >> >> Best Regards, >> >> >> >> >> >> >> >> -- >> >> *Javier Romero* >> >> >> >> >> >> >> >> >> >> -- >> >> *Javier Romero* >> >> >> >> >> >> >> > > > -- > *Javier Romero* > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matt.Peters at windriver.com Fri Feb 1 16:07:31 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 1 Feb 2019 16:07:31 +0000 Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <1484346064.187533.1549035095571@communicator.strato.com> References: <1484346064.187533.1549035095571@communicator.strato.com> Message-ID: <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> Hell Marcel, If your system is still in that state, can you run the following commands? source /etc/nova/openrc system host-ethernet-port-list controller-0 system host-if-list -a controller-0 On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: Hi, during installation when appling the configuration I'll get an error message from hiera: Configuration failed: Failed to update hiera configuration Configuration log and apply_manifet.log is attached below. Any idea or hint? Thanks Marcel localhost:~# config_controller System Configuration ==================== Enter Q at any prompt to abort... System date and time: --------------------- The system date and time must be set now. Note that UTC time must be used and that the date and time must be set as accurately as possible, even if NTP/PTP is to be configured later. Current system date and time (UTC): 2019-02-01 15:15:25 Is the current date and time correct? [y/n]: y Current system date and time will be used. System timezone: ---------------- The system timezone must be set now. The timezone must be a valid timezone from /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) Please input the timezone[UTC]:Europe/Berlin System Configuration: --------------------- System mode. Available options are: 1) duplex-direct - two node redundant configuration. Management and infrastructure networks are directly connected to peer ports 2) duplex - two node redundant configuration. 3) simplex - single node non-redundant configuration. System mode [duplex-direct]: PXEBoot Network: ---------------- The PXEBoot network is used for initial booting and installation of each node. IP addresses on this network are reachable only within the data center. The default configuration combines the PXEBoot network and the management network. If a separate PXEBoot network is used, it will share the management interface, which requires the management network to be placed on a VLAN. Configure a separate PXEBoot network [y/N]: Aborting configuration localhost:~# config_controller System Configuration ==================== Enter Q at any prompt to abort... System date and time: --------------------- The system date and time must be set now. Note that UTC time must be used and that the date and time must be set as accurately as possible, even if NTP/PTP is to be configured later. Current system date and time (UTC): 2019-02-01 15:15:40 Is the current date and time correct? [y/n]: y Current system date and time will be used. System timezone: ---------------- The system timezone must be set now. The timezone must be a valid timezone from /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) Please input the timezone[UTC]:Europe/Berlin System Configuration: --------------------- System mode. Available options are: 1) duplex-direct - two node redundant configuration. Management and infrastructure networks are directly connected to peer ports 2) duplex - two node redundant configuration. 3) simplex - single node non-redundant configuration. System mode [duplex-direct]: 1 PXEBoot Network: ---------------- The PXEBoot network is used for initial booting and installation of each node. IP addresses on this network are reachable only within the data center. The default configuration combines the PXEBoot network and the management network. If a separate PXEBoot network is used, it will share the management interface, which requires the management network to be placed on a VLAN. Configure a separate PXEBoot network [y/N]: N Management Network: ------------------- The management network is used for internal communication between platform components. IP addresses on this network are reachable only within the data center. A management bond interface provides redundant connections for the management network. It is strongly recommended to configure Management interface link aggregation, for All-in-one duplex-direct. Management interface link aggregation [y/N]: y Management interface [bond0]: Management interface MTU [1500]: Specify one of the bonding policies. Possible values are: 1) 802.3ad (LACP) policy 2) Active-backup policy Management interface bonding policy [802.3ad]: A maximum of 2 physical interfaces can be attached to the management interface. First management interface member [enp3s0f1]: enp8s20f4 Second management interface member []: enp8s20f5 Management subnet [192.168.204.0/24]: 172.27.1.0/24 Use entire management subnet [Y/n]: Y IP addresses can be assigned to hosts dynamically or a static IP address can be specified for each host. This choice applies to both the management network and infrastructure network (if configured). Warning: Selecting 'N', or static IP address allocation, disables automatic provisioning of new hosts in System Inventory, requiring the user to manually provision using the 'system host-add' command. Dynamic IP address allocation [Y/n]: Y Management Network Multicast subnet [239.1.1.0/28]: Infrastructure Network: ----------------------- The infrastructure network is used for internal communication between platform components to offload the management network of high bandwidth services. IP addresses on this network are reachable only within the data center. If a separate infrastructure interface is not configured the management network will be used. It is NOT recommended to configure infrastructure network for All-in- one duplex-direct. Configure an infrastructure interface [y/N]: N External OAM Network: --------------------- The external OAM network is used for management of the cloud. It also provides access to the platform APIs. IP addresses on this network are reachable outside the data center. An external OAM bond interface provides redundant connections for the OAM network. External OAM interface link aggregation [y/N]: y External OAM interface [bond1]: Configure an external OAM VLAN [y/N]: External OAM interface MTU [1500]: Specify one of the bonding policies. Possible values are: 1) Active-backup policy 2) Balanced XOR policy 3) 802.3ad (LACP) policy External OAM interface bonding policy [active-backup]: A maximum of 2 physical interfaces can be attached to the external OAM interface. First external OAM interface member [enp3s0f0]: enp7s16f1 Second external oam interface member []: enp7s16f7 External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 External OAM gateway address [10.62.150.1]: External OAM floating address [10.62.150.2]: External OAM address for first controller node [10.62.150.3]: 10.62.150.210 External OAM address for second controller node [10.62.150.211]: Cloud Authentication: ------------------------------- Configure a password for the Cloud admin user The Password must have a minimum length of 7 character, and conform to password complexity rules Create admin user password: Repeat admin user password: The following configuration will be applied: System Configuration -------------------- Time Zone: Europe/Berlin System mode: duplex-direct PXEBoot Network Configuration ----------------------------- Separate PXEBoot network not configured PXEBoot Controller floating hostname: pxecontroller Management Network Configuration -------------------------------- Management interface name: bond0 Management interface: bond0 Management interface MTU: 1500 Management ae member 0: enp8s20f4 Management ae member 1: enp8s20f5 Management ae policy : 802.3ad Management subnet: 172.27.1.0/24 Controller floating address: 172.27.1.2 Controller 0 address: 172.27.1.3 Controller 1 address: 172.27.1.4 NFS Management Address 1: 172.27.1.5 NFS Management Address 2: 172.27.1.6 Controller floating hostname: controller Controller hostname prefix: controller- OAM Controller floating hostname: oamcontroller Dynamic IP address allocation is selected Management multicast subnet: 239.1.1.0/28 Infrastructure Network Configuration ------------------------------------ Infrastructure interface not configured External OAM Network Configuration ---------------------------------- External OAM interface name: bond1 External OAM interface: bond1 External OAM interface MTU: 1500 External OAM ae member 0: enp7s16f1 External OAM ae member 1: enp7s16f7 External OAM ae policy : active-backup External OAM subnet: 10.62.150.0/24 External OAM gateway address: 10.62.150.1 External OAM floating address: 10.62.150.2 External OAM 0 address: 10.62.150.210 External OAM 1 address: 10.62.150.211 Apply the above configuration? [y/n]: y Applying configuration (this will take several minutes): 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... DONE 03/08: Persisting local configuration ... DONE 04/08: Populating initial system inventory ... DONE 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 2019-02-01 15:20:44.053 25508 TRACE sysinv Failed to update puppet hiera host config Configuration failed: Failed to update hiera configuration localhost:~# /tmp/apply_manifest.log: ======================== cp: cannot stat ‘/tmp/hieradata/172.27.1.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 Applying puppet bootstrap manifest... [DONE] ls /tmp/puppet/hieradata/ ========================= global.yaml personality.yaml secure_static.yaml static.yaml localhost:~# _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Fri Feb 1 16:13:26 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 1 Feb 2019 17:13:26 +0100 (CET) Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: References: Message-ID: <373798617.189988.1549037606760@communicator.strato.com> Additional information: We are using the following iso: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190109T162801Z/outputs/iso/bootimage.iso Marcel > ------------------------------ > > Message: 2 > Date: Fri, 1 Feb 2019 16:31:35 +0100 (CET) > From: Marcel Schaible > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Installation problem: Configuration > failed: Failed to update hiera configuration > Message-ID: <1484346064.187533.1549035095571 at communicator.strato.com> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > during installation when appling the configuration I'll get an error message from hiera: > > Configuration failed: Failed to update hiera configuration > > Configuration log and apply_manifet.log is attached below. > > Any idea or hint? > > Thanks > > Marcel > > > > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:25 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: > Aborting configuration > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:40 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: 1 > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: N > > Management Network: > ------------------- > > The management network is used for internal communication between platform > components. IP addresses on this network are reachable only within the data > center. > > A management bond interface provides redundant connections for the management > network. > It is strongly recommended to configure Management interface link > aggregation, for All-in-one duplex-direct. > > Management interface link aggregation [y/N]: y > Management interface [bond0]: > Management interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) 802.3ad (LACP) policy > 2) Active-backup policy > > Management interface bonding policy [802.3ad]: > A maximum of 2 physical interfaces can be attached to the management interface. > > First management interface member [enp3s0f1]: enp8s20f4 > Second management interface member []: enp8s20f5 > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > Use entire management subnet [Y/n]: Y > > IP addresses can be assigned to hosts dynamically or a static IP address can be > specified for each host. This choice applies to both the management network and > infrastructure network (if configured). > Warning: Selecting 'N', or static IP address allocation, disables automatic > provisioning of new hosts in System Inventory, requiring the user to manually > provision using the 'system host-add' command. > Dynamic IP address allocation [Y/n]: Y > Management Network Multicast subnet [239.1.1.0/28]: > > Infrastructure Network: > ----------------------- > > The infrastructure network is used for internal communication between platform > components to offload the management network of high bandwidth services. IP > addresses on this network are reachable only within the data center. > > If a separate infrastructure interface is not configured the management network > will be used. > > It is NOT recommended to configure infrastructure network for All-in- > one duplex-direct. > Configure an infrastructure interface [y/N]: N > > External OAM Network: > --------------------- > > The external OAM network is used for management of the cloud. It also provides > access to the platform APIs. IP addresses on this network are reachable outside > the data center. > > An external OAM bond interface provides redundant connections for the OAM > network. > > External OAM interface link aggregation [y/N]: y > External OAM interface [bond1]: > Configure an external OAM VLAN [y/N]: > External OAM interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) Active-backup policy > 2) Balanced XOR policy > 3) 802.3ad (LACP) policy > > External OAM interface bonding policy [active-backup]: > A maximum of 2 physical interfaces can be attached to the external OAM > interface. > > First external OAM interface member [enp3s0f0]: enp7s16f1 > Second external oam interface member []: enp7s16f7 > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > External OAM gateway address [10.62.150.1]: > External OAM floating address [10.62.150.2]: > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > External OAM address for second controller node [10.62.150.211]: > > Cloud Authentication: > ------------------------------- > > Configure a password for the Cloud admin user The Password must have a minimum > length of 7 character, and conform to password complexity rules > Create admin user password: > Repeat admin user password: > > > > The following configuration will be applied: > > System Configuration > -------------------- > Time Zone: Europe/Berlin > System mode: duplex-direct > > PXEBoot Network Configuration > ----------------------------- > Separate PXEBoot network not configured > PXEBoot Controller floating hostname: pxecontroller > > Management Network Configuration > -------------------------------- > Management interface name: bond0 > Management interface: bond0 > Management interface MTU: 1500 > Management ae member 0: enp8s20f4 > Management ae member 1: enp8s20f5 > Management ae policy : 802.3ad > Management subnet: 172.27.1.0/24 > Controller floating address: 172.27.1.2 > Controller 0 address: 172.27.1.3 > Controller 1 address: 172.27.1.4 > NFS Management Address 1: 172.27.1.5 > NFS Management Address 2: 172.27.1.6 > Controller floating hostname: controller > Controller hostname prefix: controller- > OAM Controller floating hostname: oamcontroller > Dynamic IP address allocation is selected > Management multicast subnet: 239.1.1.0/28 > > Infrastructure Network Configuration > ------------------------------------ > Infrastructure interface not configured > > External OAM Network Configuration > ---------------------------------- > External OAM interface name: bond1 > External OAM interface: bond1 > External OAM interface MTU: 1500 > External OAM ae member 0: enp7s16f1 > External OAM ae member 1: enp7s16f7 > External OAM ae policy : active-backup > External OAM subnet: 10.62.150.0/24 > External OAM gateway address: 10.62.150.1 > External OAM floating address: 10.62.150.2 > External OAM 0 address: 10.62.150.210 > External OAM 1 address: 10.62.150.211 > > Apply the above configuration? [y/n]: y > > Applying configuration (this will take several minutes): > > 01/08: Creating bootstrap configuration ... DONE > 02/08: Applying bootstrap manifest ... DONE > 03/08: Persisting local configuration ... DONE > 04/08: Populating initial system inventory ... DONE > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv > Failed to update puppet hiera host config > > Configuration failed: Failed to update hiera configuration > localhost:~# > > /tmp/apply_manifest.log: > ======================== > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > Applying puppet bootstrap manifest... > [DONE] > > > ls /tmp/puppet/hieradata/ > ========================= > global.yaml personality.yaml secure_static.yaml static.yaml > localhost:~# > > > > From marcel at schaible-consulting.de Fri Feb 1 16:19:21 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 1 Feb 2019 17:19:21 +0100 (CET) Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> References: <1484346064.187533.1549035095571@communicator.strato.com> <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> Message-ID: <1883615762.190291.1549037961751@communicator.strato.com> Hi Matt, thanks for your response. controller-0:~# source /etc/nova/openrc -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller internalURL endpoint for smapi service in RegionOne region not found [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0 internalURL endpoint for smapi service in RegionOne region not found [root at controller-0 ~(keystone_admin)]# Any idea what "RegionOne" mean? Thanks Marcel > "Peters, Matt" hat am 1. Februar 2019 um 17:07 geschrieben: > > > Hell Marcel, > If your system is still in that state, can you run the following commands? > > source /etc/nova/openrc > system host-ethernet-port-list controller-0 > system host-if-list -a controller-0 > > > On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: > > Hi, > > during installation when appling the configuration I'll get an error message from hiera: > > Configuration failed: Failed to update hiera configuration > > Configuration log and apply_manifet.log is attached below. > > Any idea or hint? > > Thanks > > Marcel > > > > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:25 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: > Aborting configuration > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:40 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: 1 > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: N > > Management Network: > ------------------- > > The management network is used for internal communication between platform > components. IP addresses on this network are reachable only within the data > center. > > A management bond interface provides redundant connections for the management > network. > It is strongly recommended to configure Management interface link > aggregation, for All-in-one duplex-direct. > > Management interface link aggregation [y/N]: y > Management interface [bond0]: > Management interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) 802.3ad (LACP) policy > 2) Active-backup policy > > Management interface bonding policy [802.3ad]: > A maximum of 2 physical interfaces can be attached to the management interface. > > First management interface member [enp3s0f1]: enp8s20f4 > Second management interface member []: enp8s20f5 > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > Use entire management subnet [Y/n]: Y > > IP addresses can be assigned to hosts dynamically or a static IP address can be > specified for each host. This choice applies to both the management network and > infrastructure network (if configured). > Warning: Selecting 'N', or static IP address allocation, disables automatic > provisioning of new hosts in System Inventory, requiring the user to manually > provision using the 'system host-add' command. > Dynamic IP address allocation [Y/n]: Y > Management Network Multicast subnet [239.1.1.0/28]: > > Infrastructure Network: > ----------------------- > > The infrastructure network is used for internal communication between platform > components to offload the management network of high bandwidth services. IP > addresses on this network are reachable only within the data center. > > If a separate infrastructure interface is not configured the management network > will be used. > > It is NOT recommended to configure infrastructure network for All-in- > one duplex-direct. > Configure an infrastructure interface [y/N]: N > > External OAM Network: > --------------------- > > The external OAM network is used for management of the cloud. It also provides > access to the platform APIs. IP addresses on this network are reachable outside > the data center. > > An external OAM bond interface provides redundant connections for the OAM > network. > > External OAM interface link aggregation [y/N]: y > External OAM interface [bond1]: > Configure an external OAM VLAN [y/N]: > External OAM interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) Active-backup policy > 2) Balanced XOR policy > 3) 802.3ad (LACP) policy > > External OAM interface bonding policy [active-backup]: > A maximum of 2 physical interfaces can be attached to the external OAM > interface. > > First external OAM interface member [enp3s0f0]: enp7s16f1 > Second external oam interface member []: enp7s16f7 > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > External OAM gateway address [10.62.150.1]: > External OAM floating address [10.62.150.2]: > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > External OAM address for second controller node [10.62.150.211]: > > Cloud Authentication: > ------------------------------- > > Configure a password for the Cloud admin user The Password must have a minimum > length of 7 character, and conform to password complexity rules > Create admin user password: > Repeat admin user password: > > > > The following configuration will be applied: > > System Configuration > -------------------- > Time Zone: Europe/Berlin > System mode: duplex-direct > > PXEBoot Network Configuration > ----------------------------- > Separate PXEBoot network not configured > PXEBoot Controller floating hostname: pxecontroller > > Management Network Configuration > -------------------------------- > Management interface name: bond0 > Management interface: bond0 > Management interface MTU: 1500 > Management ae member 0: enp8s20f4 > Management ae member 1: enp8s20f5 > Management ae policy : 802.3ad > Management subnet: 172.27.1.0/24 > Controller floating address: 172.27.1.2 > Controller 0 address: 172.27.1.3 > Controller 1 address: 172.27.1.4 > NFS Management Address 1: 172.27.1.5 > NFS Management Address 2: 172.27.1.6 > Controller floating hostname: controller > Controller hostname prefix: controller- > OAM Controller floating hostname: oamcontroller > Dynamic IP address allocation is selected > Management multicast subnet: 239.1.1.0/28 > > Infrastructure Network Configuration > ------------------------------------ > Infrastructure interface not configured > > External OAM Network Configuration > ---------------------------------- > External OAM interface name: bond1 > External OAM interface: bond1 > External OAM interface MTU: 1500 > External OAM ae member 0: enp7s16f1 > External OAM ae member 1: enp7s16f7 > External OAM ae policy : active-backup > External OAM subnet: 10.62.150.0/24 > External OAM gateway address: 10.62.150.1 > External OAM floating address: 10.62.150.2 > External OAM 0 address: 10.62.150.210 > External OAM 1 address: 10.62.150.211 > > Apply the above configuration? [y/n]: y > > Applying configuration (this will take several minutes): > > 01/08: Creating bootstrap configuration ... DONE > 02/08: Applying bootstrap manifest ... DONE > 03/08: Persisting local configuration ... DONE > 04/08: Populating initial system inventory ... DONE > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv > Failed to update puppet hiera host config > > Configuration failed: Failed to update hiera configuration > localhost:~# > > /tmp/apply_manifest.log: > ======================== > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > Applying puppet bootstrap manifest... > [DONE] > > > ls /tmp/puppet/hieradata/ > ========================= > global.yaml personality.yaml secure_static.yaml static.yaml > localhost:~# > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From erich.cordoba.malibran at intel.com Fri Feb 1 16:22:56 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 1 Feb 2019 16:22:56 +0000 Subject: [Starlingx-discuss] [Containers] Minimum memory requirements for containerized environment. Message-ID: Hi, After two days of having a containerized system up (without running any edge application, just the steps in the wiki) I started to see some Out of Memory errors like this: Out of memory: Kill process 17906 (kube-apiserver) score 1017 or sacrifice child Killed process 17906 (kube-apiserver) total-vm:460684kB, anon-rss:335088kB, file-rss:0kB, shmem-rss:0kB I have in my 16 GB in my virtual environment as the wiki says, but I'm wondering if that should be enough and this behavior could be some kind of memory leak or the minimum requirement would be a higher memory. Thanks! -Erich Here is some additional information: controller-0:~$ uptime 16:01:40 up 2 days, 22:30, 2 users, load average: 93.28, 45.36, 36.84 controller-0:~$ free -h total used free shared buff/cache available Mem: 17G 12G 206M 62M 4.8G 1.8G Swap: 0B 0B 0B controller-0:~$ top top - 16:00:10 up 2 days, 22:28, 2 users, load average: 12.57, 22.80, 29.58 Tasks: 705 total, 2 running, 703 sleeping, 0 stopped, 0 zombie %Cpu(s): 30.3 us, 18.3 sy, 0.1 ni, 27.6 id, 16.5 wa, 0.0 hi, 4.8 si, 2.4 st KiB Mem : 18330568 total, 247252 free, 13073324 used, 5009992 buff/cache KiB Swap: 0 total, 0 free, 0 used. 1925172 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18306 root 10 -10 2333224 185064 13216 S 100.3 1.0 4222:53 ovs-vswitchd 71 root 20 0 0 0 0 D 26.8 0.0 18:57.26 kswapd0 7202 root 20 0 1657284 311532 3400 S 19.9 1.7 335:52.58 kubelet 16311 root 20 0 460276 330576 2884 S 12.6 1.8 0:40.81 kube-apiserver 4291 root 20 0 66832 12224 2024 R 12.3 0.1 0:00.37 heat-manage 1116 root 20 0 1362488 151664 1728 S 11.6 0.8 265:32.20 dockerd 3 root 20 0 0 0 0 S 9.9 0.0 12:20.95 ksoftirqd/0 1 root 20 0 542540 354140 1436 S 7.9 1.9 12:23.91 systemd 21081 42424 20 0 626124 122172 1476 S 7.3 0.7 2:28.49 apache2 3795 999 20 0 5168964 258240 0 S 5.3 1.4 17:06.77 mysqld 26085 999 20 0 4965476 153132 0 S 4.6 0.8 54:16.75 beam.smp 16717 root 20 0 47140 13592 0 S 4.0 0.1 0:16.91 calico-felix 673 root 20 0 50868 12528 512 S 3.6 0.1 0:01.02 kube-scheduler 20893 root 20 0 1049800 201616 0 S 3.3 1.1 40:30.02 ceph-osd 10666 root 20 0 10.7g 112996 868 S 3.0 0.6 46:28.91 etcd 14146 root 20 0 45972 11968 0 S 3.0 0.1 10:09.31 kube-proxy 3435 root 20 0 142216 9708 0 S 2.3 0.1 8:28.87 coredns 19481 root 20 0 324232 112556 1404 S 2.3 0.6 13:20.23 nova-conductor 1162 influxdb 20 0 674068 9604 1020 S 2.0 0.1 8:44.77 influxd 1358 root 20 0 3469568 25344 0 S 2.0 0.1 13:21.31 docker-containe 13365 42424 20 0 2642820 104684 0 S 2.0 0.6 91:03.49 cinder-volume 16108 root 20 0 41044 12812 0 S 2.0 0.1 6:22.57 confd 18862 root 20 0 321820 109656 832 S 2.0 0.6 4:51.59 nova-scheduler 22478 root 20 0 248220 84272 608 S 2.0 0.5 82:31.64 neutron-dhcp-ag 402 root 20 0 60372 29536 32 S 1.7 0.2 0:45.64 nginx-ingress-c 12942 42424 20 0 892092 94848 572 S 1.7 0.5 86:12.08 cinder-backup 7367 root 18 -2 480460 9792 2436 S 1.3 0.1 18:51.83 sm 10762 root 20 0 2297792 116944 0 S 1.3 0.6 11:23.95 nova-compute 12122 root 20 0 142216 10148 296 S 1.3 0.1 8:23.28 coredns 15942 root 20 0 388912 61312 2716 S 1.3 0.3 28:51.34 fm-api 19825 root 19 -1 3313564 52676 1432 S 1.3 0.3 0:05.07 beam.smp 20357 sysinv 19 -1 382232 79644 2948 S 1.3 0.4 0:08.44 sysinv-api 313 root 0 -20 0 0 0 S 1.0 0.0 1:03.17 kworker/0:1H 720 dbus 20 0 60452 1696 896 S 1.0 0.0 3:50.63 dbus-daemon 4073 root 20 0 113788 1684 1092 S 1.0 0.0 0:00.03 ceph 4245 root 20 0 11828 776 440 S 1.0 0.0 0:00.03 heat-engine-cle 4991 root 20 0 408012 39660 304 S 1.0 0.2 5:57.15 ceph-mon 9171 root 20 0 0 0 0 S 1.0 0.0 0:01.48 kworker/0:47 12036 42424 20 0 666056 97616 448 S 1.0 0.5 26:53.04 cinder-volume 14554 root 20 0 59324 31316 0 S 1.0 0.2 7:19.50 nginx-ingress-c 18727 wrsroot 20 0 160588 2428 1100 S 1.0 0.0 0:02.46 top 20515 42424 20 0 678900 110492 428 S 1.0 0.6 26:26.14 cinder-api 20571 42424 20 0 627436 94572 312 S 1.0 0.5 26:41.77 glance-api 8 root 20 0 0 0 0 S 0.7 0.0 9:28.58 rcu_preempt 4429 snmpd 19 -1 245388 4620 480 S 0.7 0.0 0:08.51 snmpd From Matt.Peters at windriver.com Fri Feb 1 16:38:15 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 1 Feb 2019 16:38:15 +0000 Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <1883615762.190291.1549037961751@communicator.strato.com> References: <1484346064.187533.1549035095571@communicator.strato.com> <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> <1883615762.190291.1549037961751@communicator.strato.com> Message-ID: <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> Hello, I'm not sure why it is giving that error response. Are you able to run the following? openstack endpoint list On 2019-02-01, 11:19 AM, "Marcel Schaible" wrote: Hi Matt, thanks for your response. controller-0:~# source /etc/nova/openrc -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller internalURL endpoint for smapi service in RegionOne region not found [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0 internalURL endpoint for smapi service in RegionOne region not found [root at controller-0 ~(keystone_admin)]# Any idea what "RegionOne" mean? Thanks Marcel > "Peters, Matt" hat am 1. Februar 2019 um 17:07 geschrieben: > > > Hell Marcel, > If your system is still in that state, can you run the following commands? > > source /etc/nova/openrc > system host-ethernet-port-list controller-0 > system host-if-list -a controller-0 > > > On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: > > Hi, > > during installation when appling the configuration I'll get an error message from hiera: > > Configuration failed: Failed to update hiera configuration > > Configuration log and apply_manifet.log is attached below. > > Any idea or hint? > > Thanks > > Marcel > > > > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:25 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: > Aborting configuration > localhost:~# config_controller > System Configuration > ==================== > Enter Q at any prompt to abort... > > System date and time: > --------------------- > > The system date and time must be set now. Note that UTC time must be used and > that the date and time must be set as accurately as possible, even if NTP/PTP is > to be configured later. > > Current system date and time (UTC): 2019-02-01 15:15:40 > > Is the current date and time correct? [y/n]: y > Current system date and time will be used. > > System timezone: > ---------------- > > The system timezone must be set now. The timezone must be a valid timezone from > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > Please input the timezone[UTC]:Europe/Berlin > > System Configuration: > --------------------- > > System mode. Available options are: > > 1) duplex-direct - two node redundant configuration. Management and > infrastructure networks are directly connected to peer ports > 2) duplex - two node redundant configuration. > 3) simplex - single node non-redundant configuration. > System mode [duplex-direct]: 1 > > PXEBoot Network: > ---------------- > > The PXEBoot network is used for initial booting and installation of each node. > IP addresses on this network are reachable only within the data center. > > The default configuration combines the PXEBoot network and the management > network. If a separate PXEBoot network is used, it will share the management > interface, which requires the management network to be placed on a VLAN. > > Configure a separate PXEBoot network [y/N]: N > > Management Network: > ------------------- > > The management network is used for internal communication between platform > components. IP addresses on this network are reachable only within the data > center. > > A management bond interface provides redundant connections for the management > network. > It is strongly recommended to configure Management interface link > aggregation, for All-in-one duplex-direct. > > Management interface link aggregation [y/N]: y > Management interface [bond0]: > Management interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) 802.3ad (LACP) policy > 2) Active-backup policy > > Management interface bonding policy [802.3ad]: > A maximum of 2 physical interfaces can be attached to the management interface. > > First management interface member [enp3s0f1]: enp8s20f4 > Second management interface member []: enp8s20f5 > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > Use entire management subnet [Y/n]: Y > > IP addresses can be assigned to hosts dynamically or a static IP address can be > specified for each host. This choice applies to both the management network and > infrastructure network (if configured). > Warning: Selecting 'N', or static IP address allocation, disables automatic > provisioning of new hosts in System Inventory, requiring the user to manually > provision using the 'system host-add' command. > Dynamic IP address allocation [Y/n]: Y > Management Network Multicast subnet [239.1.1.0/28]: > > Infrastructure Network: > ----------------------- > > The infrastructure network is used for internal communication between platform > components to offload the management network of high bandwidth services. IP > addresses on this network are reachable only within the data center. > > If a separate infrastructure interface is not configured the management network > will be used. > > It is NOT recommended to configure infrastructure network for All-in- > one duplex-direct. > Configure an infrastructure interface [y/N]: N > > External OAM Network: > --------------------- > > The external OAM network is used for management of the cloud. It also provides > access to the platform APIs. IP addresses on this network are reachable outside > the data center. > > An external OAM bond interface provides redundant connections for the OAM > network. > > External OAM interface link aggregation [y/N]: y > External OAM interface [bond1]: > Configure an external OAM VLAN [y/N]: > External OAM interface MTU [1500]: > > Specify one of the bonding policies. Possible values are: > 1) Active-backup policy > 2) Balanced XOR policy > 3) 802.3ad (LACP) policy > > External OAM interface bonding policy [active-backup]: > A maximum of 2 physical interfaces can be attached to the external OAM > interface. > > First external OAM interface member [enp3s0f0]: enp7s16f1 > Second external oam interface member []: enp7s16f7 > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > External OAM gateway address [10.62.150.1]: > External OAM floating address [10.62.150.2]: > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > External OAM address for second controller node [10.62.150.211]: > > Cloud Authentication: > ------------------------------- > > Configure a password for the Cloud admin user The Password must have a minimum > length of 7 character, and conform to password complexity rules > Create admin user password: > Repeat admin user password: > > > > The following configuration will be applied: > > System Configuration > -------------------- > Time Zone: Europe/Berlin > System mode: duplex-direct > > PXEBoot Network Configuration > ----------------------------- > Separate PXEBoot network not configured > PXEBoot Controller floating hostname: pxecontroller > > Management Network Configuration > -------------------------------- > Management interface name: bond0 > Management interface: bond0 > Management interface MTU: 1500 > Management ae member 0: enp8s20f4 > Management ae member 1: enp8s20f5 > Management ae policy : 802.3ad > Management subnet: 172.27.1.0/24 > Controller floating address: 172.27.1.2 > Controller 0 address: 172.27.1.3 > Controller 1 address: 172.27.1.4 > NFS Management Address 1: 172.27.1.5 > NFS Management Address 2: 172.27.1.6 > Controller floating hostname: controller > Controller hostname prefix: controller- > OAM Controller floating hostname: oamcontroller > Dynamic IP address allocation is selected > Management multicast subnet: 239.1.1.0/28 > > Infrastructure Network Configuration > ------------------------------------ > Infrastructure interface not configured > > External OAM Network Configuration > ---------------------------------- > External OAM interface name: bond1 > External OAM interface: bond1 > External OAM interface MTU: 1500 > External OAM ae member 0: enp7s16f1 > External OAM ae member 1: enp7s16f7 > External OAM ae policy : active-backup > External OAM subnet: 10.62.150.0/24 > External OAM gateway address: 10.62.150.1 > External OAM floating address: 10.62.150.2 > External OAM 0 address: 10.62.150.210 > External OAM 1 address: 10.62.150.211 > > Apply the above configuration? [y/n]: y > > Applying configuration (this will take several minutes): > > 01/08: Creating bootstrap configuration ... DONE > 02/08: Applying bootstrap manifest ... DONE > 03/08: Persisting local configuration ... DONE > 04/08: Populating initial system inventory ... DONE > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > 2019-02-01 15:20:44.053 25508 TRACE sysinv > Failed to update puppet hiera host config > > Configuration failed: Failed to update hiera configuration > localhost:~# > > /tmp/apply_manifest.log: > ======================== > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > Applying puppet bootstrap manifest... > [DONE] > > > ls /tmp/puppet/hieradata/ > ========================= > global.yaml personality.yaml secure_static.yaml static.yaml > localhost:~# > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From marcel at schaible-consulting.de Fri Feb 1 16:47:54 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 1 Feb 2019 17:47:54 +0100 (CET) Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> References: <1484346064.187533.1549035095571@communicator.strato.com> <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> <1883615762.190291.1549037961751@communicator.strato.com> <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> Message-ID: <420746737.191750.1549039674257@communicator.strato.com> [root at controller-0 ~(keystone_admin)]# openstack endpoint list +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | 8bca85c075e74635a4c81c978da9434c | RegionOne | keystone | identity | True | admin | http://127.0.0.1:5000/v3 | | edc1d5eb056744adba859c0d4630ba5b | RegionOne | keystone | identity | True | internal | http://127.0.0.1:5000/v3 | | 73e43933bd6744d7ae37bb938194be88 | RegionOne | keystone | identity | True | public | http://127.0.0.1:5000/v3 | | f5b6a70a9a3a42b99230462fd72188e1 | RegionOne | sysinv | platform | True | admin | http://127.0.0.1:6385/v1 | | 99c8461427b54839a0ca647815e0a469 | RegionOne | sysinv | platform | True | internal | http://127.0.0.1:6385/v1 | | a8a78b29d3054189bd734261c442ad4e | RegionOne | sysinv | platform | True | public | http://127.0.0.1:6385/v1 | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ > "Peters, Matt" hat am 1. Februar 2019 um 17:38 geschrieben: > > > Hello, > I'm not sure why it is giving that error response. > > Are you able to run the following? > openstack endpoint list > > > On 2019-02-01, 11:19 AM, "Marcel Schaible" wrote: > > Hi Matt, > > thanks for your response. > > controller-0:~# source /etc/nova/openrc > -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0 > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# > > Any idea what "RegionOne" mean? > Thanks > Marcel > > > > "Peters, Matt" hat am 1. Februar 2019 um 17:07 geschrieben: > > > > > > Hell Marcel, > > If your system is still in that state, can you run the following commands? > > > > source /etc/nova/openrc > > system host-ethernet-port-list controller-0 > > system host-if-list -a controller-0 > > > > > > On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: > > > > Hi, > > > > during installation when appling the configuration I'll get an error message from hiera: > > > > Configuration failed: Failed to update hiera configuration > > > > Configuration log and apply_manifet.log is attached below. > > > > Any idea or hint? > > > > Thanks > > > > Marcel > > > > > > > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:25 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: > > Aborting configuration > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:40 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: 1 > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: N > > > > Management Network: > > ------------------- > > > > The management network is used for internal communication between platform > > components. IP addresses on this network are reachable only within the data > > center. > > > > A management bond interface provides redundant connections for the management > > network. > > It is strongly recommended to configure Management interface link > > aggregation, for All-in-one duplex-direct. > > > > Management interface link aggregation [y/N]: y > > Management interface [bond0]: > > Management interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) 802.3ad (LACP) policy > > 2) Active-backup policy > > > > Management interface bonding policy [802.3ad]: > > A maximum of 2 physical interfaces can be attached to the management interface. > > > > First management interface member [enp3s0f1]: enp8s20f4 > > Second management interface member []: enp8s20f5 > > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > > Use entire management subnet [Y/n]: Y > > > > IP addresses can be assigned to hosts dynamically or a static IP address can be > > specified for each host. This choice applies to both the management network and > > infrastructure network (if configured). > > Warning: Selecting 'N', or static IP address allocation, disables automatic > > provisioning of new hosts in System Inventory, requiring the user to manually > > provision using the 'system host-add' command. > > Dynamic IP address allocation [Y/n]: Y > > Management Network Multicast subnet [239.1.1.0/28]: > > > > Infrastructure Network: > > ----------------------- > > > > The infrastructure network is used for internal communication between platform > > components to offload the management network of high bandwidth services. IP > > addresses on this network are reachable only within the data center. > > > > If a separate infrastructure interface is not configured the management network > > will be used. > > > > It is NOT recommended to configure infrastructure network for All-in- > > one duplex-direct. > > Configure an infrastructure interface [y/N]: N > > > > External OAM Network: > > --------------------- > > > > The external OAM network is used for management of the cloud. It also provides > > access to the platform APIs. IP addresses on this network are reachable outside > > the data center. > > > > An external OAM bond interface provides redundant connections for the OAM > > network. > > > > External OAM interface link aggregation [y/N]: y > > External OAM interface [bond1]: > > Configure an external OAM VLAN [y/N]: > > External OAM interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) Active-backup policy > > 2) Balanced XOR policy > > 3) 802.3ad (LACP) policy > > > > External OAM interface bonding policy [active-backup]: > > A maximum of 2 physical interfaces can be attached to the external OAM > > interface. > > > > First external OAM interface member [enp3s0f0]: enp7s16f1 > > Second external oam interface member []: enp7s16f7 > > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > > External OAM gateway address [10.62.150.1]: > > External OAM floating address [10.62.150.2]: > > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > > External OAM address for second controller node [10.62.150.211]: > > > > Cloud Authentication: > > ------------------------------- > > > > Configure a password for the Cloud admin user The Password must have a minimum > > length of 7 character, and conform to password complexity rules > > Create admin user password: > > Repeat admin user password: > > > > > > > > The following configuration will be applied: > > > > System Configuration > > -------------------- > > Time Zone: Europe/Berlin > > System mode: duplex-direct > > > > PXEBoot Network Configuration > > ----------------------------- > > Separate PXEBoot network not configured > > PXEBoot Controller floating hostname: pxecontroller > > > > Management Network Configuration > > -------------------------------- > > Management interface name: bond0 > > Management interface: bond0 > > Management interface MTU: 1500 > > Management ae member 0: enp8s20f4 > > Management ae member 1: enp8s20f5 > > Management ae policy : 802.3ad > > Management subnet: 172.27.1.0/24 > > Controller floating address: 172.27.1.2 > > Controller 0 address: 172.27.1.3 > > Controller 1 address: 172.27.1.4 > > NFS Management Address 1: 172.27.1.5 > > NFS Management Address 2: 172.27.1.6 > > Controller floating hostname: controller > > Controller hostname prefix: controller- > > OAM Controller floating hostname: oamcontroller > > Dynamic IP address allocation is selected > > Management multicast subnet: 239.1.1.0/28 > > > > Infrastructure Network Configuration > > ------------------------------------ > > Infrastructure interface not configured > > > > External OAM Network Configuration > > ---------------------------------- > > External OAM interface name: bond1 > > External OAM interface: bond1 > > External OAM interface MTU: 1500 > > External OAM ae member 0: enp7s16f1 > > External OAM ae member 1: enp7s16f7 > > External OAM ae policy : active-backup > > External OAM subnet: 10.62.150.0/24 > > External OAM gateway address: 10.62.150.1 > > External OAM floating address: 10.62.150.2 > > External OAM 0 address: 10.62.150.210 > > External OAM 1 address: 10.62.150.211 > > > > Apply the above configuration? [y/n]: y > > > > Applying configuration (this will take several minutes): > > > > 01/08: Creating bootstrap configuration ... DONE > > 02/08: Applying bootstrap manifest ... DONE > > 03/08: Persisting local configuration ... DONE > > 04/08: Populating initial system inventory ... DONE > > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv > > Failed to update puppet hiera host config > > > > Configuration failed: Failed to update hiera configuration > > localhost:~# > > > > /tmp/apply_manifest.log: > > ======================== > > > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > > Applying puppet bootstrap manifest... > > [DONE] > > > > > > ls /tmp/puppet/hieradata/ > > ========================= > > global.yaml personality.yaml secure_static.yaml static.yaml > > localhost:~# > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > From Matt.Peters at windriver.com Fri Feb 1 16:57:12 2019 From: Matt.Peters at windriver.com (Peters, Matt) Date: Fri, 1 Feb 2019 16:57:12 +0000 Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <420746737.191750.1549039674257@communicator.strato.com> References: <1484346064.187533.1549035095571@communicator.strato.com> <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> <1883615762.190291.1549037961751@communicator.strato.com> <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> <420746737.191750.1549039674257@communicator.strato.com> Message-ID: Hello Marcel, Ok, so apparently the client was updated to try and retrieve the smapi endpoint as part of all system requests (not sure why), so you will need to add the following so that the system commands against inventory will work. Can you try running the following and then reexecuting the system commands below. openstack endpoint create --region RegionOne smapi internal http://127.0.0.1:7777 On 2019-02-01, 11:48 AM, "Marcel Schaible" wrote: [root at controller-0 ~(keystone_admin)]# openstack endpoint list +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | 8bca85c075e74635a4c81c978da9434c | RegionOne | keystone | identity | True | admin | http://127.0.0.1:5000/v3 | | edc1d5eb056744adba859c0d4630ba5b | RegionOne | keystone | identity | True | internal | http://127.0.0.1:5000/v3 | | 73e43933bd6744d7ae37bb938194be88 | RegionOne | keystone | identity | True | public | http://127.0.0.1:5000/v3 | | f5b6a70a9a3a42b99230462fd72188e1 | RegionOne | sysinv | platform | True | admin | http://127.0.0.1:6385/v1 | | 99c8461427b54839a0ca647815e0a469 | RegionOne | sysinv | platform | True | internal | http://127.0.0.1:6385/v1 | | a8a78b29d3054189bd734261c442ad4e | RegionOne | sysinv | platform | True | public | http://127.0.0.1:6385/v1 | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ > "Peters, Matt" hat am 1. Februar 2019 um 17:38 geschrieben: > > > Hello, > I'm not sure why it is giving that error response. > > Are you able to run the following? > openstack endpoint list > > > On 2019-02-01, 11:19 AM, "Marcel Schaible" wrote: > > Hi Matt, > > thanks for your response. > > controller-0:~# source /etc/nova/openrc > -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0 > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# > > Any idea what "RegionOne" mean? > Thanks > Marcel > > > > "Peters, Matt" hat am 1. Februar 2019 um 17:07 geschrieben: > > > > > > Hell Marcel, > > If your system is still in that state, can you run the following commands? > > > > source /etc/nova/openrc > > system host-ethernet-port-list controller-0 > > system host-if-list -a controller-0 > > > > > > On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: > > > > Hi, > > > > during installation when appling the configuration I'll get an error message from hiera: > > > > Configuration failed: Failed to update hiera configuration > > > > Configuration log and apply_manifet.log is attached below. > > > > Any idea or hint? > > > > Thanks > > > > Marcel > > > > > > > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:25 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: > > Aborting configuration > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:40 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: 1 > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: N > > > > Management Network: > > ------------------- > > > > The management network is used for internal communication between platform > > components. IP addresses on this network are reachable only within the data > > center. > > > > A management bond interface provides redundant connections for the management > > network. > > It is strongly recommended to configure Management interface link > > aggregation, for All-in-one duplex-direct. > > > > Management interface link aggregation [y/N]: y > > Management interface [bond0]: > > Management interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) 802.3ad (LACP) policy > > 2) Active-backup policy > > > > Management interface bonding policy [802.3ad]: > > A maximum of 2 physical interfaces can be attached to the management interface. > > > > First management interface member [enp3s0f1]: enp8s20f4 > > Second management interface member []: enp8s20f5 > > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > > Use entire management subnet [Y/n]: Y > > > > IP addresses can be assigned to hosts dynamically or a static IP address can be > > specified for each host. This choice applies to both the management network and > > infrastructure network (if configured). > > Warning: Selecting 'N', or static IP address allocation, disables automatic > > provisioning of new hosts in System Inventory, requiring the user to manually > > provision using the 'system host-add' command. > > Dynamic IP address allocation [Y/n]: Y > > Management Network Multicast subnet [239.1.1.0/28]: > > > > Infrastructure Network: > > ----------------------- > > > > The infrastructure network is used for internal communication between platform > > components to offload the management network of high bandwidth services. IP > > addresses on this network are reachable only within the data center. > > > > If a separate infrastructure interface is not configured the management network > > will be used. > > > > It is NOT recommended to configure infrastructure network for All-in- > > one duplex-direct. > > Configure an infrastructure interface [y/N]: N > > > > External OAM Network: > > --------------------- > > > > The external OAM network is used for management of the cloud. It also provides > > access to the platform APIs. IP addresses on this network are reachable outside > > the data center. > > > > An external OAM bond interface provides redundant connections for the OAM > > network. > > > > External OAM interface link aggregation [y/N]: y > > External OAM interface [bond1]: > > Configure an external OAM VLAN [y/N]: > > External OAM interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) Active-backup policy > > 2) Balanced XOR policy > > 3) 802.3ad (LACP) policy > > > > External OAM interface bonding policy [active-backup]: > > A maximum of 2 physical interfaces can be attached to the external OAM > > interface. > > > > First external OAM interface member [enp3s0f0]: enp7s16f1 > > Second external oam interface member []: enp7s16f7 > > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > > External OAM gateway address [10.62.150.1]: > > External OAM floating address [10.62.150.2]: > > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > > External OAM address for second controller node [10.62.150.211]: > > > > Cloud Authentication: > > ------------------------------- > > > > Configure a password for the Cloud admin user The Password must have a minimum > > length of 7 character, and conform to password complexity rules > > Create admin user password: > > Repeat admin user password: > > > > > > > > The following configuration will be applied: > > > > System Configuration > > -------------------- > > Time Zone: Europe/Berlin > > System mode: duplex-direct > > > > PXEBoot Network Configuration > > ----------------------------- > > Separate PXEBoot network not configured > > PXEBoot Controller floating hostname: pxecontroller > > > > Management Network Configuration > > -------------------------------- > > Management interface name: bond0 > > Management interface: bond0 > > Management interface MTU: 1500 > > Management ae member 0: enp8s20f4 > > Management ae member 1: enp8s20f5 > > Management ae policy : 802.3ad > > Management subnet: 172.27.1.0/24 > > Controller floating address: 172.27.1.2 > > Controller 0 address: 172.27.1.3 > > Controller 1 address: 172.27.1.4 > > NFS Management Address 1: 172.27.1.5 > > NFS Management Address 2: 172.27.1.6 > > Controller floating hostname: controller > > Controller hostname prefix: controller- > > OAM Controller floating hostname: oamcontroller > > Dynamic IP address allocation is selected > > Management multicast subnet: 239.1.1.0/28 > > > > Infrastructure Network Configuration > > ------------------------------------ > > Infrastructure interface not configured > > > > External OAM Network Configuration > > ---------------------------------- > > External OAM interface name: bond1 > > External OAM interface: bond1 > > External OAM interface MTU: 1500 > > External OAM ae member 0: enp7s16f1 > > External OAM ae member 1: enp7s16f7 > > External OAM ae policy : active-backup > > External OAM subnet: 10.62.150.0/24 > > External OAM gateway address: 10.62.150.1 > > External OAM floating address: 10.62.150.2 > > External OAM 0 address: 10.62.150.210 > > External OAM 1 address: 10.62.150.211 > > > > Apply the above configuration? [y/n]: y > > > > Applying configuration (this will take several minutes): > > > > 01/08: Creating bootstrap configuration ... DONE > > 02/08: Applying bootstrap manifest ... DONE > > 03/08: Persisting local configuration ... DONE > > 04/08: Populating initial system inventory ... DONE > > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv > > Failed to update puppet hiera host config > > > > Configuration failed: Failed to update hiera configuration > > localhost:~# > > > > /tmp/apply_manifest.log: > > ======================== > > > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > > Applying puppet bootstrap manifest... > > [DONE] > > > > > > ls /tmp/puppet/hieradata/ > > ========================= > > global.yaml personality.yaml secure_static.yaml static.yaml > > localhost:~# > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > From xavinux at gmail.com Fri Feb 1 17:02:58 2019 From: xavinux at gmail.com (Javier Romero) Date: Fri, 1 Feb 2019 14:02:58 -0300 Subject: [Starlingx-discuss] Contribution to the project. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BBFD18EB2@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD18F0D@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Curtis, Thank you very much for your answer, will take a look at that list too. Best Regards, *Javier Romero* El vie., 1 feb. 2019 a las 12:32, Curtis () escribió: > Hi Javier, > > This doesn't help you much right now, but just to let you know we are in > the process of trying to set up some tagging for our issues and work items > that will show if they are good for new contributors and such, like what > many other open source projects do. Watch the list for updates related to > that project. > > Thanks, > Curtis > > On Thu, Jan 31, 2019 at 6:04 PM Javier Romero wrote: > >> Hi Bruce, >> >> Thanks for your information. >> >> Will join the weekly call next Wednesday, now I'm checking the wiki and >> docs of the project. >> >> I can use a VM with KVM hypervisor to run StarlingX, it has 8 cores and >> 16 GB of RAM, but seens that 32 GB are needed at least. Will have to find >> something else... >> >> >> >> >> El jueves, 31 de enero de 2019, Jones, Bruce E >> escribió: >> >>> Javier, thank you. I’m going to suggest a couple of things for you to >>> try out, to get started. >>> >>> >>> >>> You can join our weekly community call. It’s on Wednesdays at 1400 >>> UTC. Details are here: >>> https://wiki.openstack.org/wiki/Starlingx/Meetings. StarlingX is a big >>> project so we’ve divided it up into sub-projects – each has a call of their >>> own, listed on that page, that you could join as well. >>> >>> >>> >>> You should check out our wiki: https://wiki.openstack.org/wiki/StarlingX >>> and our documentation https://docs.starlingx.io/ >>> >>> >>> >>> You can download and run a pre-built StarlingX image from here: >>> http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/outputs/iso/ >>> >>> >>> >>> You can find some instructions on how to install the image here: >>> https://docs.starlingx.io/installation_guide/index.html. The document >>> needs some changes, which we are working on as part of the Documentation >>> sub-project. You will need a VM on a machine with lots of memory and/or a >>> dedicated system to boot the image on – the image installs an OS and all of >>> StarlingX. >>> >>> >>> >>> Myself and the community will be happy to answer any questions you have. >>> >>> >>> >>> brucej >>> >>> >>> >>> *From:* Javier Romero [mailto:xavinux at gmail.com] >>> *Sent:* Thursday, January 31, 2019 1:41 PM >>> *To:* Jones, Bruce E >>> *Cc:* starlingx-discuss at lists.starlingx.io >>> *Subject:* Re: Contribution to the project. >>> >>> >>> >>> Thanks for your answer. >>> >>> >>> >>> Well maybe testing but please, let me know those parts where you need >>> more help to see if I can be useful in any of them. >>> >>> >>> >>> Best Regards, >>> >>> >>> >>> >>> >>> El jueves, 31 de enero de 2019, Jones, Bruce E >>> escribió: >>> >>> We’d love to have your help! What part of the project are you >>> interested in? >>> >>> >>> >>> brucej >>> >>> >>> >>> *From:* Javier Romero [mailto:xavinux at gmail.com] >>> *Sent:* Thursday, January 31, 2019 12:42 PM >>> *To:* starlingx-discuss at lists.starlingx.io >>> *Subject:* [Starlingx-discuss] Contribution to the project. >>> >>> Hi Team, >>> >>> >>> >>> My name is Javier and live in Buenos Aires, Argentina. >>> >>> >>> >>> Work in the Network Operations Center of an Internet Service Provider >>> where I deploy and manage mission critical Linux Servers. >>> >>> >>> >>> Would like to know if there is something I can help with on the >>> StarlingX project . >>> >>> >>> >>> Thanks for your attention. >>> >>> >>> >>> Best Regards, >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> *Javier Romero* >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> *Javier Romero* >>> >>> >>> >>> >>> >>> >>> >> >> >> -- >> *Javier Romero* >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > -- > Blog: serverascode.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tyler.smith at windriver.com Fri Feb 1 17:16:21 2019 From: tyler.smith at windriver.com (Smith, Tyler) Date: Fri, 1 Feb 2019 17:16:21 +0000 Subject: [Starlingx-discuss] [Containers] Change to container install process Message-ID: Hello, A change I've made which got merged this morning affects the install process for containerized systems, you must now add host labels to controllers and computes before unlocking them. I have updated the wikis accordingly. Thanks, Tyler -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Fri Feb 1 20:53:52 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Fri, 1 Feb 2019 20:53:52 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes 1/31/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105CF462@fmsmsx104.amr.corp.intel.com> Build team meeting Attendees Marce, Erich, Pipo, Memo, Luis, Abraham, Saul, Victor, Bruce, Ken, Jason Agenda for 1/31/2019 - Review stories for next release - Explore build mechanism for feature branches - Cengn update - Opens Notes Review stories for next release: We reviewed the stories committed for next release out of the build team, after a brief overview for these, (2004011-13 ) we realize that the activities are linked to task under 2004043, so we decided to do some housekeeping and get rid of the duplicated ones. AR Cesar to send Ghada an email about this. Explore build mechanism for feature branches: we have the capacity to deliver these on demand, overall mechanism works the same as our release builds, so in case there are a requirement to build a custom ISO file, based on any given branch, we have the resources to do it. Cengn update: Build system running stable, a lot of effort to get builds based on the new architecture, we do have email notifications ready for build failures. Still pending the migration of hosted mirror to K8 clusters inside Cengn. Opens: There was a proposal for two new user experience features: - Provide a way to check requirements before starting a build. - Improve build system logs. The ask was about if these new features will need to follow the spec process to get accepted and the answer was yes, so, Erich will start putting something together to follow up on this. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Fri Feb 1 21:27:17 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Fri, 1 Feb 2019 21:27:17 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A936603@fmsmsx101.amr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A936853@fmsmsx101.amr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A936C1F@fmsmsx101.amr.corp.intel.com> Mingyuan After applying workaround you mentioned I only see the freeze one time, on glance pod 30%, after timeout expired I ran again the apply and everything worked correctly without any freeze until completed successfully. Regards, José > -----Original Message----- > From: Qi, Mingyuan > Sent: Friday, February 1, 2019 1:11 AM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io; Al.Bailey at windriver.com; Wensley, Barton > > Subject: RE: [Starlingx-discuss] [Containers] Deployment status > > Jose, > > Looking into your log, it seems that coredns is not ready. > Here is the workaround for it: > 1. kubectl -n kube-system edit configmap coredns 2. remove "loop" line and > save 3. kubectl -n kube-system delete rs {your-coredns-replicaset-name} > > Bart & Al, > > It's seems to be a real issue for users behind a proxy which I guess coredns is > not able to access external nameserver and falls in loop. > Could user specified nameserver to be updated to coredns? > > Mingyuan > > > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: Friday, February 1, 2019 1:31 > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Containers] Deployment status > > Hi, > > I did some tests with the most recent ISO (01/31) that has already the > changes to add a proxy on config_controller, still facing the below > mentioned issues, I created a Launchpad [1] to track this. > > https://bugs.launchpad.net/starlingx/+bug/1814142 > > Regards, > José > > > -----Original Message----- > > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > > Sent: Wednesday, January 30, 2019 4:31 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] [Containers] Deployment status > > > > Hi All > > > > ** Virtual Environment ** > > > > I'm working on setting up a StarlingX deployment with containers as > > described on [1] using proxies but I have faces some issues described > below: > > > > - I have successfully completed all the steps until "system > > application-apply stx-openstack" when the system becomes unstable, the > > application-apply gets freezed in random pods until timeout of 30 min > > is reached, I discovered that killing armada process and start again the > "system application-apply" > > the application advance until again is freezed in a random pod. > > After some cycles the application is successfully completed. > > > > Here is a log [2] of one point when the process is freeze, the error > > is always the same, the only element that changes is the pod and its > > random, not always is the same pod. > > > > ===== > > 019-01-30 17:24:13.364 11824 ERROR sysinv.conductor.kube_app [-] > > Received a false positive response from Docker/Armada. Failed to apply > > application manifest /manifests/stx-openstack-manifest-no-tests.yaml: > > 2019- > > 01-30 16:54:07.367 20554 DEBUG armada.handlers.document [-] Resolving > > reference /manifests/stx-openstack-manifest-no-tests.yaml. > > resolve_reference /usr/local/lib/python3.5/site- > > packages/armada/handlers/document.py:49 > > ===== > > > > -After is completed correctly I'm receiving failures on "Verify the > > cluster endpoints" when running `openstack endpoint list`, I updated > > the .yml file with the correct password but connection is not > > established correctly. Here is the output [3]. > > > > ====== > > controller-0:~$ openstack endpoint list Failed to discover available > > identity versions when contacting > http://keystone.openstack.svc.cluster.local/v3. > > Attempting to parse version from URL. > > Unable to establish connection to > > http://keystone.openstack.svc.cluster.local/v3/auth/tokens: > > HTTPConnectionPool(host='keystone.openstack.svc.cluster.local', port=80): > > Max retries exceeded with url: /v3/auth/tokens (Caused by > > NewConnectionError(' > o n object at 0x7fe65ffb90d0>: Failed to establish a new connection: > > [Errno -3] Temporary failure in name resolution',)) ====== > > > > 1. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > > 2. http://paste.openstack.org/show/744277 > > 3. http://paste.openstack.org/show/744281 > > > > Regards, > > José > > > > > > > > _______________________________________________ > > 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 xavinux at gmail.com Sat Feb 2 02:54:12 2019 From: xavinux at gmail.com (Javier Romero) Date: Fri, 1 Feb 2019 23:54:12 -0300 Subject: [Starlingx-discuss] Contribution to the project. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BBFD18EB2@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD18F0D@fmsmsx123.amr.corp.intel.com> Message-ID: Hi Abraham, Thanks for your attentiion and I can help on the documentation team if you need help there. Have a good day! Best Regards, El jueves, 31 de enero de 2019, Arce Moreno, Abraham < abraham.arce.moreno at intel.com> escribió: > Javier, > > > > Well maybe testing but please, let me know those parts where you need > > more help to see if I can be useful in any of them. > > Please consider the invitation to join us at the Documentation Team [0] > > Right now we have activities around you area of expertise, creating the > documentation > to deploy and manage the different StarlingX configurations and its > services. > > Please let me know so we can have a call with you. > > [0] https://etherpad.openstack.org/p/stx-documentation > -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Sat Feb 2 03:54:05 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Sat, 2 Feb 2019 03:54:05 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> ,<6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com> Message-ID: <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm From xiongzhiwei at baicells.com Sat Feb 2 04:38:10 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Sat, 2 Feb 2019 12:38:10 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Message-ID: <20190202123809273461136@baicells.com> Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sat Feb 2 05:00:04 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 2 Feb 2019 05:00:04 +0000 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server In-Reply-To: <20190202123809273461136@baicells.com> References: <20190202123809273461136@baicells.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E75C28@SHSMSX104.ccr.corp.intel.com> HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiongzhiwei at baicells.com Sat Feb 2 06:16:21 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Sat, 2 Feb 2019 14:16:21 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server References: <20190202123809273461136@baicells.com>, <2FD5DDB5A04D264C80D42CA35194914F35E75C28@SHSMSX104.ccr.corp.intel.com> Message-ID: <20190202141620901159145@baicells.com> Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Sat Feb 2 06:27:30 2019 From: yong.hu at intel.com (Hu, Yong) Date: Sat, 2 Feb 2019 06:27:30 +0000 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server In-Reply-To: <20190202141620901159145@baicells.com> References: <20190202123809273461136@baicells.com> <2FD5DDB5A04D264C80D42CA35194914F35E75C28@SHSMSX104.ccr.corp.intel.com> <20190202141620901159145@baicells.com> Message-ID: <6392F92B-138A-42D9-ABB2-6D5EAD30B2E8@intel.com> If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiongzhiwei at baicells.com Sat Feb 2 06:34:57 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Sat, 2 Feb 2019 14:34:57 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server References: <20190202123809273461136@baicells.com>, <2FD5DDB5A04D264C80D42CA35194914F35E75C28@SHSMSX104.ccr.corp.intel.com>, <20190202141620901159145@baicells.com>, <6392F92B-138A-42D9-ABB2-6D5EAD30B2E8@intel.com> Message-ID: <20190202143457151410149@baicells.com> Thanks Hu Yong and Cindy, I am trying to again after remove these two SATA HD. Will tell you once successed. Regards Tim From: Hu, Yong Date: 2019-02-02 14:27 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiongzhiwei at baicells.com Sat Feb 2 07:07:15 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Sat, 2 Feb 2019 15:07:15 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server References: <20190202123809273461136@baicells.com>, <2FD5DDB5A04D264C80D42CA35194914F35E75C28@SHSMSX104.ccr.corp.intel.com>, <20190202141620901159145@baicells.com>, <6392F92B-138A-42D9-ABB2-6D5EAD30B2E8@intel.com>, <20190202143457151410149@baicells.com> Message-ID: <20190202150714722222153@baicells.com> Hi Yong and Cindy, The same error appeared after removed these two sata disks. Thanks Tim From: xiongzhiwei at baicells.com Date: 2019-02-02 14:34 To: Hu, Yong; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Thanks Hu Yong and Cindy, I am trying to again after remove these two SATA HD. Will tell you once successed. Regards Tim From: Hu, Yong Date: 2019-02-02 14:27 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Sat Feb 2 07:10:11 2019 From: yong.hu at intel.com (Hu, Yong) Date: Sat, 2 Feb 2019 07:10:11 +0000 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Message-ID: Pls share us your /var/log/puppet/latest/puppet.log. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 3:07 PM To: "xiongzhiwei at baicells.com" , "Hu, Yong" , "Xie, Cindy" , starlingx-discuss Subject: Re: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Yong and Cindy, The same error appeared after removed these two sata disks. Thanks Tim From: xiongzhiwei at baicells.com Date: 2019-02-02 14:34 To: Hu, Yong; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Thanks Hu Yong and Cindy, I am trying to again after remove these two SATA HD. Will tell you once successed. Regards Tim From: Hu, Yong Date: 2019-02-02 14:27 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavinux at gmail.com Sat Feb 2 14:20:21 2019 From: xavinux at gmail.com (Javier Romero) Date: Sat, 2 Feb 2019 11:20:21 -0300 Subject: [Starlingx-discuss] Hypervisor requrements. Message-ID: Hi Team, I've at disposal a Proxmox VM. The Server where Proxmox is running which uses KVM as hypevisor, has 8 cores intel E5 and 32 GB of memory Have someone test StarlingX with Proxmox or it only works with QEMU/libvirt and VirtualBox? Best Regards, -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavinux at gmail.com Sat Feb 2 17:07:07 2019 From: xavinux at gmail.com (Javier Romero) Date: Sat, 2 Feb 2019 14:07:07 -0300 Subject: [Starlingx-discuss] Vagrant StarlingX VM. Message-ID: Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Sat Feb 2 17:42:57 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Sat, 2 Feb 2019 17:42:57 +0000 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: References: Message-ID: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> Yes we are exploring a few possibilities for StarlingX in a bottle, vagrant in one of them. Feel free to throw some ideas at it Regards Cesar Lara Sent from my mobile phone ________________________________ From: Javier Romero Sent: Saturday, February 2, 2019 11:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Vagrant StarlingX VM. Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- Javier Romero -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavinux at gmail.com Sat Feb 2 20:50:50 2019 From: xavinux at gmail.com (Javier Romero) Date: Sat, 2 Feb 2019 17:50:50 -0300 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> Message-ID: Cesar, Thank you for your time to answer. Will let you know if I have some ideas. Regards, El sábado, 2 de febrero de 2019, Lara, Cesar escribió: > Yes we are exploring a few possibilities for StarlingX in a bottle, > vagrant in one of them. Feel free to throw some ideas at it > > Regards > Cesar Lara > Sent from my mobile phone > ------------------------------ > *From:* Javier Romero > *Sent:* Saturday, February 2, 2019 11:07 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Vagrant StarlingX VM. > > Hi Team, > > Think that perhaps may be useful for new users to have a Vagrant > preconfigured AIO VM to use StarlingX for the fiirst time. > > https://www.vagrantup.com > > If this can be useful I can help with that. > > Vagrant use VirtualBox by default to star the preconfigured VM and can > also be set to be used with QEMU. > > Best Regards, > > > > > > -- > *Javier Romero* > > > > -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Sun Feb 3 08:15:50 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sun, 3 Feb 2019 08:15:50 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> ,<6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com> <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E770BD@SHSMSX104.ccr.corp.intel.com> Thanks Mario. If you below 2 patches can close the tasks you've taken from storyboard 2004008, please go ahead to assign other tasks from that story. Thanks. - cindy -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Saturday, February 2, 2019 11:54 AM To: Penney, Don ; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From himanshugoyal500 at gmail.com Mon Feb 4 12:08:03 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Mon, 4 Feb 2019 17:38:03 +0530 Subject: [Starlingx-discuss] VCPU scheduler priority Message-ID: Hi, Please suggest how to set VCPU Scheduler policy in flavor, Not able to found that in flavor metadata. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Mon Feb 4 13:25:32 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Mon, 4 Feb 2019 13:25:32 +0000 Subject: [Starlingx-discuss] VCPU scheduler priority In-Reply-To: References: Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3B9685@ALA-MBD.corp.ad.wrs.com> Hi, There is no VCPU Scheduler policy extra spec. CPU policy/topology related extra specs can be found here, https://docs.openstack.org/nova/pike/admin/flavors.html Brent From: Himanshu Goyal [mailto:himanshugoyal500 at gmail.com] Sent: Monday, February 4, 2019 7:08 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] VCPU scheduler priority Hi, Please suggest how to set in flavor, Not able to found that in flavor metadata. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Mon Feb 4 14:18:24 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 4 Feb 2019 09:18:24 -0500 Subject: [Starlingx-discuss] Hypervisor requrements. In-Reply-To: References: Message-ID: <1549289904.21474.6.camel@windriver.com> Hi Javier, Proxmox is also Qemu based, correct?  I am reading this Proxmox wiki: https://pve.proxmox.com/wiki/Main_Page If it is qemu then you may be able to select similar cpu and hardware options as are presented in the stx-tools/deployment/libvirt/*.xml files. M On Sat, 2019-02-02 at 11:20 -0300, Javier Romero wrote: > Hi Team, > > I've at disposal a Proxmox VM. The Server where Proxmox is running > which uses KVM as hypevisor, has 8 cores intel E5 and 32 GB of memory > > Have someone test StarlingX with Proxmox or it only works with > QEMU/libvirt and VirtualBox? > > Best Regards, > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From xavinux at gmail.com Mon Feb 4 14:55:11 2019 From: xavinux at gmail.com (Javier Romero) Date: Mon, 4 Feb 2019 11:55:11 -0300 Subject: [Starlingx-discuss] Hypervisor requrements. In-Reply-To: <1549289904.21474.6.camel@windriver.com> References: <1549289904.21474.6.camel@windriver.com> Message-ID: Hi Michel, I'll create a VM with Proxmox and try to run StarlingX in it. Will come back to let you know if it is workkng. Regards, El lunes, 4 de febrero de 2019, Michel Thebeau escribió: > Hi Javier, > > Proxmox is also Qemu based, correct? I am reading this Proxmox wiki: > > https://pve.proxmox.com/wiki/Main_Page > > If it is qemu then you may be able to select similar cpu and hardware > options as are presented in the stx-tools/deployment/libvirt/*.xml > files. > > M > > > > On Sat, 2019-02-02 at 11:20 -0300, Javier Romero wrote: > > Hi Team, > > > > I've at disposal a Proxmox VM. The Server where Proxmox is running > > which uses KVM as hypevisor, has 8 cores intel E5 and 32 GB of memory > > > > Have someone test StarlingX with Proxmox or it only works with > > QEMU/libvirt and VirtualBox? > > > > Best Regards, > > > > > > > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Mon Feb 4 14:59:45 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 4 Feb 2019 14:59:45 +0000 Subject: [Starlingx-discuss] CentOS 7.6 rebase feature testing In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE8137E@SHSMSX101.ccr.corp.intel.com> References: <151EE31B9FCCA54397A757BC674650F0BA4A9F22@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E4F339@SHSMSX103.ccr.corp.intel.com> <151EE31B9FCCA54397A757BC674650F0BA4A9F40@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE80761@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE80937@SHSMSX101.ccr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE48266B36@ALA-MBD.corp.ad.wrs.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CD6394D@FMSMSX114.amr.corp.intel.com> <3CAA827B7A79BA46B15B280EC82088FE4826C03E@ALA-MBD.corp.ad.wrs.com> <151EE31B9FCCA54397A757BC674650F0BA4B7290@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE81334@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE8137E@SHSMSX101.ccr.corp.intel.com> Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4B840B@ALA-MBD.corp.ad.wrs.com> Thanks Shuicheng. Is there a need to actually upversion the qat drivers? Are there new features or bug fixes that are of interest to StarlingX? I suggest you review the release notes and make a decision with the distro.other team leads before proceeding with this item. Ghada From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, January 30, 2019 7:34 PM To: Khalil, Ghada; Waheed, Numan; Perez, Ricardo O; Xie, Cindy; Cabrales, Ada Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Hi all, Story is created to track this task: https://storyboard.openstack.org/#!/story/2004901 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, January 31, 2019 7:56 AM To: Khalil, Ghada >; Waheed, Numan >; Perez, Ricardo O >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.6 rebase feature testing Hi Ghada, QAT driver is not upgraded yet, since there is no build failure with CentOS 7.6. I will have a check with it after Chinese New Year's holiday, and plan to do the upgrade in master. Best Regards Shuicheng From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, January 30, 2019 11:01 PM To: Waheed, Numan >; Perez, Ricardo O >; Lin, Shuicheng >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Shuicheng, Can you confirm if the qat17 driver was updated? I didn't see it on the task list. To the test team, I suggest you look at the summary of changes highlighted by Shuicheng below as well as the tasks in the stories (as they show the packages that have changed) and choose the test-cases and test configurations accordingly. Based on the changes listed in https://storyboard.openstack.org/#!/story/2004521 - Sanity/Basic Regression on standard and low-latency profile o Install/lock/unlock all node types (controller/compute/storage) o VM operations - Niantic NIC tested as a mgmt/infra and data interface - Fortville NIC tested as a mgmt/infra and data interface - Mellanox NIC tested as a mgmt/infra interface, but not a data interface (as mlx driver DPDK support is disabled) o Include cable pulls for all NIC types - Hardware TPM - IMA/Integrity - DRBD sync - should be covered by duplex/multi-node test-cases (lock/unlock/reinstall controller-1) Based on the changes listed in https://storyboard.openstack.org/#!/story/2004521 - https config (changes in haxproxy) - snmp traps (changes in net-snmp) - ldap user password changes (changes in openldap) - efi pxe install (changes to grub2) - The remaining packages are covered by the normal install and basic system operations I think the above would make a good regression suite for an OS upgrade in the future as well. I encourage others on the mailing list to review/comment as well. Regards, Ghada PS: The TCs below are heavily geared towards neutron. They don't provide sufficient coverage given the areas of churn. From: Waheed, Numan Sent: Wednesday, January 30, 2019 9:08 AM To: Perez, Ricardo O; Lin, Shuicheng; Khalil, Ghada; Xie, Cindy; Cabrales, Ada Subject: RE: CentOS 7.6 rebase feature testing Hi Ricardo, Thanks for providing the list of test cases. These are mostly networking related test cases. Can you please let me know which NICs you are using in your labs? I would also suggest to add some tests that are specific to OS e.g. password related tests, Backup and Restore etc. Are you also going to do any low-latency setup? I would also suggest to add some Nova related tests. Thanks, Numan. From: Perez, Ricardo O > Sent: January-29-19 6:08 PM To: Waheed, Numan >; Lin, Shuicheng >; Khalil, Ghada >; Xie, Cindy >; Cabrales, Ada > Subject: RE: CentOS 7.6 rebase feature testing Hi Numan, These are the tests that we are planning to run on CentOS 7.6 Testing: Live-migration: Instance is Scheduling on socket where vswitch is running (on destination host) Lock & Unlock the compute Off-line static configuration for "External OAM" Interface On-line Static configuration validation: swact controllers should be rejected until controller-0 config for "External OAM" Inter Provider network Down Alarm Reject changing interface MTU size to values smaller than MTU of provider network Verify administrator is able to set alter and query System name Via CLI and GUI Verify alarm generation for neutron L3 agent scheduling states Verify alarm generation for neutron provider network state Verify appropriate values should be used for modifying of interfaces (CLI, GUI) Verify ethernet MGMT interface is updated successfully on controller. Verify ethernet OAM interface is updated successfully on controller. Verify that all providernettypes can be shown via Neutron REST API Verify that associating provider network with an interface is rejected if MTU of the interface is smaller than MTU of provider n Verify that changing the physical interface of MGMT network is permitted Verify that changing the physical interface of OAM network is permitted Verify that hosts can be shown via Neutron REST API Verify that interfaces parameters can be modified via API reques Verify that interfaces ports data can be modified via API. Verify that providernet can be created/updated/deleted via Neutron REST API Verify that providernetranges can be created/updated/deleted via Neutron REST API Verify that subnet can be created and subnet attributes can be modified via Neutron REST API Verify that System name can be modified via CLI and GUI Verify that the MTU size is displayed correctly for the infra interface after it is changed. Verify that unlocked powered off host can not be deleted (CLI, GUI) The configurations that we are pretending to use are: P1 - 2+2+2 (External Storage) P2 - Duplex If someone has any other test that we have to consider or add to this list, just let us know. Regards -Ricardo From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Monday, January 28, 2019 7:49 AM To: Lin, Shuicheng >; Khalil, Ghada >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Hi Ada, Which tests you are planning to run for CentOS 7.6 testing? Which configs you are using? Thanks, Numan. From: Lin, Shuicheng > Sent: January-28-19 1:28 AM To: Khalil, Ghada >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.6 rebase feature testing Hi Ghada/Numan, 1 more patch is added for feature branch. https://review.openstack.org/633431 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, January 28, 2019 10:20 AM To: Khalil, Ghada >; Xie, Cindy >; Cabrales, Ada > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.6 rebase feature testing Hi Ghada/Numan, All code for CentOS 7.6 upgrade has been merged to centos76 feature branch. Please have a try with it, and notify me if there is any problem. Manifest file I used is attached, it is with last week's master code + feature branch code for stx-integ/stx-upstream/stx-tools/stx-root. Here is a simple summary for CentOS 7.6 upgrade: 30 srpm & 650+ rpm upgraded. Kernel version upgraded to 3.10.0-957.1.3 for both std and rt kernel. Out of tree driver upgraded/updated: i40e/i40evf/ixgbe/ixgbevf/tpm/integrity/mellanox/rdma-core/libibverbs. Mellanox driver support in DPDK is disabled. (DPDK/OpenVswitch need be upgraded later to support Mellanox driver again.) You could get more info from below stories: Kenrel upgrade story: https://storyboard.openstack.org/#!/story/2004521 Srpm & rpm upgrade story: https://storyboard.openstack.org/#!/story/2004522 Mellanox driver support: https://storyboard.openstack.org/#!/story/2004743 Best Regards Shuicheng From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Thursday, January 24, 2019 3:15 AM To: Xie, Cindy >; Cabrales, Ada >; Lin, Shuicheng > Cc: Waheed, Numan >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Sorry for the confusion. Yes Numan will wait until all the pending patches are merged in the feature branch. Is this planned for the end of next week (before Chinese New Year holidays)? From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, January 23, 2019 2:10 PM To: Khalil, Ghada; Cabrales, Ada; Lin, Shuicheng Cc: Waheed, Numan; Jones, Bruce E; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS 7.6 rebase feature testing Ghada, In today's meeting, Ken mentioned that he'd like to see all pending patches merged to f/CentOS7.6 for Numan to start. But if Numan wants to start earlier, that's fine. @Shuicheng should be able to send out the build instructions. Thx. - cindy From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com] Sent: Wednesday, January 23, 2019 11:05 AM To: Xie, Cindy >; Cabrales, Ada > Cc: Waheed, Numan >; Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: CentOS 7.6 rebase feature testing Hi Cindy, My understanding from the F2F meeting last week that you already discussed with Ada testing the CentOS 7.6 rebase image (feature branch) starting Feb 1 while your team is off for Chinese New Year's. Can you please send the instructions for building the feature branch to the stx mailing list? Numan will try to have an image built to try it out in one of the WR labs (time-permitting). I expect the feature branch is rebased to the latest from master. Hi Ada, Given that there are driver upgrades for i40e & ixgbe, I assume you are planning to test on baremetal hardware, not just in the virtual env. Are your baremetal labs setup now? What NIC types do you have covered in your labs? Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.thebeau at windriver.com Mon Feb 4 15:03:04 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 4 Feb 2019 10:03:04 -0500 Subject: [Starlingx-discuss] Hypervisor requrements. In-Reply-To: References: <1549289904.21474.6.camel@windriver.com> Message-ID: <1549292584.21474.12.camel@windriver.com> Cool, and if there's a way export the VM definition in a human readable form like XML please send it along to the list for insight. M On Mon, 2019-02-04 at 11:55 -0300, Javier Romero wrote: > Hi Michel, > > I'll create a VM with Proxmox and try to run StarlingX in it. Will > come back to let  you know if it is workkng. > > Regards, > > > El lunes, 4 de febrero de 2019, Michel Thebeau ver.com> escribió: > > Hi Javier, > > > > Proxmox is also Qemu based, correct?  I am reading this Proxmox > > wiki: > > > > https://pve.proxmox.com/wiki/Main_Page > > > > If it is qemu then you may be able to select similar cpu and > > hardware > > options as are presented in the stx-tools/deployment/libvirt/*.xml > > files. > > > > M > > > > > > > > On Sat, 2019-02-02 at 11:20 -0300, Javier Romero wrote: > > > Hi Team, > > >  > > > I've at disposal a Proxmox VM. The Server where Proxmox is > > running > > > which uses KVM as hypevisor, has 8 cores intel E5 and 32 GB of > > memory > > >  > > > Have someone test StarlingX with Proxmox or it only works with > > > QEMU/libvirt and VirtualBox? > > >  > > > Best Regards, > > >  > > >  > > >  > > >  > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > uss > > > From xavinux at gmail.com Mon Feb 4 15:24:55 2019 From: xavinux at gmail.com (Javier Romero) Date: Mon, 4 Feb 2019 12:24:55 -0300 Subject: [Starlingx-discuss] Hypervisor requrements. In-Reply-To: <1549292584.21474.12.camel@windriver.com> References: <1549289904.21474.6.camel@windriver.com> <1549292584.21474.12.camel@windriver.com> Message-ID: Of course I'll do it if everything works fine. Regards, El lunes, 4 de febrero de 2019, Michel Thebeau escribió: > Cool, and if there's a way export the VM definition in a human readable > form like XML please send it along to the list for insight. > > M > > > On Mon, 2019-02-04 at 11:55 -0300, Javier Romero wrote: > > Hi Michel, > > > > I'll create a VM with Proxmox and try to run StarlingX in it. Will > > come back to let you know if it is workkng. > > > > Regards, > > > > > > El lunes, 4 de febrero de 2019, Michel Thebeau > ver.com> escribió: > > > Hi Javier, > > > > > > Proxmox is also Qemu based, correct? I am reading this Proxmox > > > wiki: > > > > > > https://pve.proxmox.com/wiki/Main_Page > > > > > > If it is qemu then you may be able to select similar cpu and > > > hardware > > > options as are presented in the stx-tools/deployment/libvirt/*.xml > > > files. > > > > > > M > > > > > > > > > > > > On Sat, 2019-02-02 at 11:20 -0300, Javier Romero wrote: > > > > Hi Team, > > > > > > > > I've at disposal a Proxmox VM. The Server where Proxmox is > > > running > > > > which uses KVM as hypevisor, has 8 cores intel E5 and 32 GB of > > > memory > > > > > > > > Have someone test StarlingX with Proxmox or it only works with > > > > QEMU/libvirt and VirtualBox? > > > > > > > > Best Regards, > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > > > > -- *Javier Romero* -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Mon Feb 4 15:25:08 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Mon, 4 Feb 2019 15:25:08 +0000 Subject: [Starlingx-discuss] STX CentOS7.6 Nova Test Report - YELLOW Message-ID: <19C65A6E92EA384D809B1772130CD7F8621810EA@ALA-MBD.corp.ad.wrs.com> Hi All, Here's the results and analysis for nova regressions with centos7.6 load. 7 test cases failed due to two new issues (reproducible) and rest of the failures were caused by existing issues. Issues: 1. Existing host mempage config issue. https://bugs.launchpad.net/starlingx/+bug/1813325  -> failed 39 mempage testcases which require reconfig the host mempage as a pre-condition. 2. Existing intermittent swact issue. https://bugs.launchpad.net/starlingx/+bug/1812108  -> failed 2 testcases, passed in rerun. 3. [new issue] #1814336 CentOS7.6: Unable to launch vm directly from virsh -> failed 1 test 4. [new issue] #1814335 CentOS7.6: Unable to launch vm with UEFI boot -> failed 6 test Note that this is only the results for nova regressions. Testing in other domains are still in progress. Thanks, yang ========================================= Node Config: 2+8+2 Software Version: 19.01 Overall Status: YELLOW Automated Test Results Summary: ------------------------------------------------------ Passed: 179 (78.85%) Failed: 48 (21.15%) Total Executed: 227 List of Test Cases: ------------------------------ PASS    20190131 14:04:04      test_vm_with_config_drive PASS    20190131 14:16:28      test_boot_vm_cpu_policy_image[3-None-shared-image-None] PASS    20190131 14:19:35     test_boot_vm_cpu_policy_image[4-dedicated-dedicated-volume-None] PASS    20190131 14:22:47      test_boot_vm_cpu_policy_image[1-dedicated-None-image-None] PASS    20190131 14:25:24      test_boot_vm_cpu_policy_image[1-shared-shared-volume-None] PASS    20190131 14:28:35      test_boot_vm_cpu_policy_image[2-shared-None-image-None] PASS    20190131 14:31:19      test_boot_vm_cpu_policy_image[3-dedicated-shared-volume-None] PASS    20190131 14:34:44      test_boot_vm_cpu_policy_image[1-shared-dedicated-image-CPUPolicyErr.CONFLICT_FLV_IMG] PASS    20190131 14:36:14      test_cpu_pol_vm_actions[4-None-flavor-image] PASS    20190131 14:44:44      test_cpu_pol_vm_actions[2-dedicated-flavor-volume] PASS    20190131 14:52:53      test_cpu_pol_vm_actions[3-shared-flavor-volume] PASS    20190131 15:01:09      test_cpu_pol_vm_actions[1-dedicated-flavor-image] PASS    20190131 15:09:34      test_cpu_pol_vm_actions[2-dedicated-image-volume] PASS    20190131 15:18:20      test_cpu_pol_vm_actions[3-shared-image-volume] PASS    20190131 15:26:57      test_cpu_pol_vm_actions[1-dedicated-image-image] PASS    20190131 15:36:29      test_flavor_cpu_realtime_negative[2-dedicated-yes-None-None-CpuRtErr.RT_AND_ORD_REQUIRED] PASS    20190131 15:36:51      test_flavor_cpu_realtime_negative[2-shared-yes-^0-None-CpuRtErr.DED_CPU_POL_REQUIRED] PASS    20190131 15:37:11      test_flavor_cpu_realtime_negative[3-None-yes-^1-None-CpuRtErr.DED_CPU_POL_REQUIRED] PASS    20190131 15:37:33      test_flavor_cpu_realtime_negative[4-dedicated-yes-^2-3-1-CpuRtErr.RT_MASK_SHARED_VCPU_CONFLICT] PASS    20190131 15:37:54      test_flavor_cpu_realtime_negative[1-dedicated-yes-^0-None-CpuRtErr.RT_AND_ORD_REQUIRED] PASS    20190131 15:38:16      test_flavor_cpu_realtime_negative[4-dedicated-yes-^0-3-2-CpuRtErr.RT_AND_ORD_REQUIRED] PASS    20190131 15:38:38      test_cpu_realtime_vm_actions[3-None-^0-flavor-None-None-prefer-None] SKIP    20190131 15:46:21      test_cpu_realtime_vm_actions[4-yes-^0-favor-None-None-require-None] PASS    20190131 15:46:31      test_cpu_realtime_vm_actions[6-yes-^2-3-flavor-None-None-isolate-None] PASS    20190131 15:53:03      test_cpu_realtime_vm_actions[2-yes-^1-flavor-1-None-None-None] PASS    20190131 15:59:33      test_cpu_realtime_vm_actions[3-yes-^0-1-image-None-None-None-None] PASS    20190131 16:06:38      test_cpu_realtime_vm_actions[3-yes-^1-2-image-None-None-isolate-None] PASS    20190131 16:13:28      test_cpu_realtime_vm_actions[4-no-^0-2-flavor-2-None-None-None] PASS    20190131 16:20:01      test_cpu_realtime_vm_actions[4-no-^0-2-image-None-None-None-None] PASS    20190131 16:27:03      test_cpu_thread_flavor_set_negative[None-isolate-None-None-CPUThreadErr.DEDICATED_CPU_REQUIRED_FLAVOR] PASS    20190131 16:27:25      test_cpu_thread_flavor_set_negative[None-require-None-None-CPUThreadErr.DEDICATED_CPU_REQUIRED_FLAVOR] PASS    20190131 16:27:46      test_cpu_thread_flavor_set_negative[None-prefer-None-None-CPUThreadErr.DEDICATED_CPU_REQUIRED_FLAVOR] PASS    20190131 16:28:07      test_cpu_thread_flavor_set_negative[shared-isolate-None-None-CPUThreadErr.DEDICATED_CPU_REQUIRED_FLAVOR] PASS    20190131 16:28:29      test_cpu_thread_flavor_set_negative[shared-require-None-None-CPUThreadErr.DEDICATED_CPU_REQUIRED_FLAVOR] PASS    20190131 16:28:50      test_cpu_thread_flavor_set_negative[dedicated--None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:29:12      test_cpu_thread_flavor_set_negative[dedicated-requi-None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:29:34      test_cpu_thread_flavor_set_negative[dedicated-REQUIRE-None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:29:55      test_cpu_thread_flavor_set_negative[dedicated-AOID-None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:30:16      test_cpu_thread_flavor_set_negative[dedicated-ISOLATE-None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:30:38      test_cpu_thread_flavor_set_negative[dedicated-PREFR-None-None-CPUThreadErr.INVALID_POLICY] PASS    20190131 16:30:59      test_cpu_thread_flavor_set_negative[None-None-1-None-SharedCPUErr.DEDICATED_CPU_REQUIRED] PASS    20190131 16:31:21      test_cpu_thread_flavor_set_negative[shared-None-0-None-SharedCPUErr.DEDICATED_CPU_REQUIRED] PASS    20190131 16:31:42      test_cpu_thread_flavor_set_negative[dedicated-isolate-0-None-CPUThreadErr.UNSET_SHARED_VCPU] PASS    20190131 16:32:04      test_cpu_thread_flavor_set_negative[dedicated-require-1-None-CPUThreadErr.UNSET_SHARED_VCPU] PASS    20190131 16:32:26      test_cpu_thread_flavor_add_negative[specs_preset0-specs_to_set0-CPUThreadErr.UNSET_SHARED_VCPU] PASS    20190131 16:32:51      test_cpu_thread_flavor_add_negative[specs_preset1-specs_to_set1-CPUThreadErr.UNSET_SHARED_VCPU] PASS    20190131 16:33:17      test_cpu_thread_flavor_delete_negative[isolate] PASS    20190131 16:33:42      test_cpu_thread_flavor_delete_negative[require] PASS    20190131 16:34:09      test_cpu_thread_flavor_delete_negative[prefer] PASS    20190131 16:39:06      test_boot_vm_cpu_thread_ht_disabled[2-require-None-CPUThreadErr.HT_HOST_UNAVAIL] PASS    20190131 16:40:11      test_boot_vm_cpu_thread_ht_disabled[3-require-None-CPUThreadErr.HT_HOST_UNAVAIL] PASS    20190131 16:41:16      test_boot_vm_cpu_thread_ht_disabled[3-isolate-None-None] PASS    20190131 16:42:40      test_boot_vm_cpu_thread_ht_disabled[2-prefer-None-None] PASS    20190131 16:45:23      test_evacuate_vms_with_inst_backing[local_image] PASS    20190131 16:59:27      test_reboot_only_host PASS    20190131 17:13:10      test_flavor_default_specs PASS    20190131 17:13:36      test_set_flavor_extra_specs[hw:cpu_model-values0] PASS    20190131 17:14:10      test_set_flavor_extra_specs[hw:cpu_policy-values1] PASS    20190131 17:14:31      test_set_flavor_extra_specs[sw:wrs:auto_recovery-values2] PASS    20190131 17:15:04      test_create_flavor_with_excessive_vcpu_negative PASS    20190131 17:15:23      test_force_lock_with_mig_vms PASS    20190131 17:34:23      test_force_lock_with_non_mig_vms PASS    20190131 17:48:13      test_create_image_with_metadata[sw_wrs_auto_recovery-values0-qcow2-bare] PASS    20190131 17:51:01      test_create_image_with_metadata[sw_wrs_auto_recovery-values1-raw-bare] PASS    20190131 17:53:46      test_lock_with_vms FAIL    20190131 18:09:23      test_boot_vm_mem_page_size[None-None] FAIL    20190131 18:15:49      test_boot_vm_mem_page_size[None-any] FAIL    20190131 18:15:58      test_boot_vm_mem_page_size[None-large] FAIL    20190131 18:16:08      test_boot_vm_mem_page_size[None-small] FAIL    20190131 18:16:17      test_boot_vm_mem_page_size[None-2048] FAIL    20190131 18:16:27      test_boot_vm_mem_page_size[None-1048576] FAIL    20190131 18:16:36      test_boot_vm_mem_page_size[any-None] FAIL    20190131 18:16:45      test_boot_vm_mem_page_size[any-any] FAIL    20190131 18:16:55      test_boot_vm_mem_page_size[any-large] FAIL    20190131 18:17:04      test_boot_vm_mem_page_size[any-small] FAIL    20190131 18:17:13      test_boot_vm_mem_page_size[any-2048] FAIL    20190131 18:17:23      test_boot_vm_mem_page_size[any-1048576] FAIL    20190131 18:17:32      test_boot_vm_mem_page_size[large-None] FAIL    20190131 18:17:41      test_boot_vm_mem_page_size[large-any] FAIL    20190131 18:17:51      test_boot_vm_mem_page_size[large-large] FAIL    20190131 18:18:00      test_boot_vm_mem_page_size[large-small] FAIL    20190131 18:18:10      test_boot_vm_mem_page_size[large-2048] FAIL    20190131 18:18:19      test_boot_vm_mem_page_size[large-1048576] FAIL    20190131 18:18:29      test_boot_vm_mem_page_size[small-None] FAIL    20190131 18:18:38      test_boot_vm_mem_page_size[small-any] FAIL    20190131 18:18:47      test_boot_vm_mem_page_size[small-large] FAIL    20190131 18:18:57      test_boot_vm_mem_page_size[small-small] FAIL    20190131 18:19:06      test_boot_vm_mem_page_size[small-2048] FAIL    20190131 18:19:15      test_boot_vm_mem_page_size[small-1048576] FAIL    20190131 18:19:24      test_boot_vm_mem_page_size[2048-None] FAIL    20190131 18:19:34      test_boot_vm_mem_page_size[2048-any] FAIL    20190131 18:19:43      test_boot_vm_mem_page_size[2048-large] FAIL    20190131 18:19:53      test_boot_vm_mem_page_size[2048-small] FAIL    20190131 18:20:02      test_boot_vm_mem_page_size[2048-2048] FAIL    20190131 18:20:11      test_boot_vm_mem_page_size[2048-1048576] FAIL    20190131 18:20:21      test_boot_vm_mem_page_size[1048576-None] FAIL    20190131 18:20:30      test_boot_vm_mem_page_size[1048576-any] FAIL    20190131 18:20:39      test_boot_vm_mem_page_size[1048576-large] FAIL    20190131 18:20:48      test_boot_vm_mem_page_size[1048576-small] FAIL    20190131 18:20:58      test_boot_vm_mem_page_size[1048576-2048] FAIL    20190131 18:21:07      test_boot_vm_mem_page_size[1048576-1048576] FAIL    20190131 18:21:16      test_schedule_vm_mempage_config[1048576] FAIL    20190131 18:21:26      test_schedule_vm_mempage_config[large] FAIL    20190131 18:21:35      test_schedule_vm_mempage_config[small] PASS    20190131 18:21:44      test_compute_mempage_vars PASS    20190131 18:45:40      test_set_mem_page_size_extra_specs[small] PASS    20190131 18:45:58      test_set_mem_page_size_extra_specs[large] PASS    20190131 18:46:12      test_set_mem_page_size_extra_specs[any] PASS    20190131 18:46:25      test_set_mem_page_size_extra_specs[2048] PASS    20190131 18:46:38      test_set_mem_page_size_extra_specs[1048576] PASS    20190131 18:46:52      test_vm_mem_pool[2048] PASS    20190131 18:48:23      test_vm_mem_pool[large] PASS    20190131 18:49:35      test_vm_mem_pool[small] PASS    20190131 18:50:41      test_vm_mem_pool[1048576] PASS    20190131 18:51:44      test_live_migrate_vm_positive[local_image-0-0-None-1-volume-False] PASS    20190131 18:54:35      test_live_migrate_vm_positive[local_image-0-0-dedicated-2-volume-False] PASS    20190131 18:57:12      test_live_migrate_vm_positive[local_image-1-0-dedicated-2-volume-False] PASS    20190131 19:00:07      test_live_migrate_vm_positive[local_image-0-512-shared-1-volume-False] PASS    20190131 19:02:54      test_live_migrate_vm_positive[local_image-1-512-dedicated-2-volume-True] PASS    20190131 19:05:44      test_live_migrate_vm_positive[local_image-0-0-shared-2-image-True] PASS    20190131 19:08:26      test_live_migrate_vm_positive[local_image-1-512-dedicated-1-image-False] PASS    20190131 19:12:06      test_live_migrate_vm_positive[local_image-0-0-None-2-image_with_vol-False] PASS    20190131 19:15:04      test_live_migrate_vm_positive[local_image-0-0-dedicated-1-image_with_vol-True] PASS    20190131 19:17:54      test_live_migrate_vm_positive[local_image-1-512-dedicated-2-image_with_vol-True] PASS    20190131 19:21:20      test_live_migrate_vm_positive[local_image-1-512-dedicated-1-image_with_vol-False] PASS    20190131 19:25:22      test_live_migrate_vm_negative[local_image-0-0-volume-True-LiveMigErr.BLOCK_MIG_UNSUPPORTED] PASS    20190131 19:29:51      test_cold_migrate_vm[local_image-0-0-None-1-volume-confirm] PASS    20190131 19:32:29     test_cold_migrate_vm[local_image-0-0-dedicated-2-volume-confirm] PASS    20190131 19:35:09      test_cold_migrate_vm[local_image-1-0-shared-2-image-confirm] PASS    20190131 19:38:15      test_cold_migrate_vm[local_image-0-512-dedicated-1-image-confirm] PASS    20190131 19:41:11      test_cold_migrate_vm[local_image-0-0-None-1-image_with_vol-confirm] PASS    20190131 19:44:35      test_cold_migrate_vm[local_image-0-0-None-2-volume-revert] PASS    20190131 19:47:17      test_cold_migrate_vm[local_image-0-0-dedicated-1-volume-revert] PASS    20190131 19:50:13      test_cold_migrate_vm[local_image-1-0-shared-2-image-revert] PASS    20190131 19:53:00     test_cold_migrate_vm[local_image-0-512-dedicated-1-image-revert] PASS    20190131 19:56:11      test_cold_migrate_vm[local_image-0-0-dedicated-2-image_with_vol-revert] PASS    20190131 20:01:08      test_migrate_vm[ubuntu_14-live-dedicated] PASS    20190131 20:03:35      test_migrate_vm[ubuntu_14-cold-dedicated] PASS    20190131 20:06:06      test_migrate_vm[tis-centos-guest-live-None] PASS    20190131 20:08:11      test_migrate_vm[tis-centos-guest-cold-None] FAIL    20190131 20:10:32      test_migrate_vm_various_guest[ubuntu_14-1-1024-shared-volume] PASS    20190131 20:21:40      test_migrate_vm_various_guest[ubuntu_14-2-1024-dedicated-image] PASS    20190131 20:29:27     test_migrate_vm_various_guest[ubuntu_16-3-4096-dedicated-volume] PASS    20190131 20:38:05      test_migrate_vm_various_guest[centos_6-3-4096-dedicated-volume] PASS    20190131 20:47:20      test_migrate_vm_various_guest[centos_7-1-1024-dedicated-volume] PASS    20190131 20:56:18      test_migrate_vm_various_guest[centos_7-5-4096-None-image] PASS    20190131 21:05:11      test_migrate_vm_various_guest[opensuse_11-3-1024-dedicated-volume] FAIL    20190131 21:14:43      test_migrate_vm_various_guest[opensuse_12-4-4096-dedicated-volume] PASS    20190131 21:27:13      test_migrate_vm_various_guest[rhel_6-3-1024-dedicated-image] PASS    20190131 21:37:12      test_migrate_vm_various_guest[rhel_6-4-4096-None-volume] PASS    20190131 21:46:58      test_migrate_vm_various_guest[rhel_7-1-1024-dedicated-volume] PASS    20190131 21:59:01      test_migrate_vm_various_guest[win_2012-3-1024-dedicated-image] SKIP    20190131 22:14:58      test_migrate_vm_various_guest[win_2016-4-4096-dedicated-volume] FAIL    20190131 22:15:15      test_migrate_vm_various_guest[ge_edge-1-1024-shared-image] FAIL    20190131 22:17:08      test_migrate_vm_various_guest[ge_edge-4-4096-dedicated-volume] PASS    20190131 22:19:40      test_migration_auto_converge PASS    20190131 22:25:43      test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS    20190131 22:27:54      test_nova_actions[ubuntu_14-shared-stop-start] PASS    20190131 22:30:01      test_nova_actions[ubuntu_14-dedicated-auto_recover] PASS    20190131 22:36:16      test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS    20190131 22:38:27      test_nova_actions_various_guest[cgcs-guest-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 22:51:16      test_nova_actions_various_guest[ubuntu_14-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 23:03:42      test_nova_actions_various_guest[ubuntu_16-dedicated-image-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 23:16:28      test_nova_actions_various_guest[centos_6-dedicated-image-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 23:29:17      test_nova_actions_various_guest[centos_7-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 23:42:05      test_nova_actions_various_guest[opensuse_11-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190131 23:54:55      test_nova_actions_various_guest[opensuse_12-dedicated-image-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190201 00:07:32      test_nova_actions_various_guest[rhel_7-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190201 00:20:22      test_nova_actions_various_guest[rhel_6-dedicated-image-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190201 00:33:03      test_nova_actions_various_guest[win_2012-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] PASS    20190201 00:51:13      test_nova_actions_various_guest[win_2016-dedicated-image-pause-unpause-suspend-resume-stop-start-auto_recover] FAIL    20190201 01:09:47      test_nova_actions_various_guest[ge_edge-dedicated-volume-pause-unpause-suspend-resume-stop-start-auto_recover] FAIL    20190201 01:11:57      test_orphan_audit PASS    20190201 01:12:30      test_prioritized_vm_evacuations[reboot-False-diff_priority-same_vcpus-same_mem-same_root_disk-same_swap_disk] PASS    20190201 01:24:20      test_prioritized_vm_evacuations[reboot-False-same_priority-diff_vcpus-diff_mem-same_root_disk-no_swap_disk] PASS    20190201 01:35:14      test_prioritized_vm_evacuations[reboot-True-same_priority-same_vcpus-diff_mem-diff_root_disk-same_swap_disk] PASS    20190201 01:45:53      test_prioritized_vm_evacuations[reboot-True-same_priority-same_vcpus-same_mem-diff_root_disk-diff_swap_disk] PASS    20190201 01:56:28      test_prioritized_vm_evacuations[reboot-True-same_priority-same_vcpus-same_mem-same_root_disk-diff_swap_disk] PASS    20190201 02:07:07      test_prioritized_vm_evacuations[reboot-True-diff_priority-diff_vcpus-same_mem-same_root_disk-no_swap_disk] PASS    20190201 02:17:52      test_prioritized_vm_evacuations[reboot-True-diff_priority-diff_vcpus-diff_mem-diff_root_disk-diff_swap_disk] PASS    20190201 02:28:30      test_prioritized_vm_evacuations[force_reboot-False-same_priority-same_vcpus-diff_mem-diff_root_disk-diff_swap_disk] PASS    20190201 02:39:20      test_prioritized_vm_evacuations[force_reboot-True-diff_priority-diff_vcpus-diff_mem-same_root_disk-same_swap_disk] PASS    20190201 02:49:58      test_setting_evacuate_priority[set--2-error] PASS    20190201 02:50:52      test_setting_evacuate_priority[set-10-None] PASS    20190201 02:51:08      test_setting_evacuate_priority[set-11-error] PASS    20190201 02:51:23      test_setting_evacuate_priority[set--error] PASS    20190201 02:51:36      test_setting_evacuate_priority[set-random-error] PASS    20190201 02:51:50      test_setting_evacuate_priority[delete--error] PASS    20190201 02:54:29      test_resize_vm_positive[local_image-4_0_0-5_1_512-image] PASS    20190201 02:59:03      test_resize_vm_positive[local_image-4_1_512-5_2_1024-image] PASS    20190201 03:03:56      test_resize_vm_positive[local_image-5_1_512-5_1_0-image] PASS    20190201 03:09:45      test_resize_vm_positive[local_image-4_0_0-5_1_512-volume] PASS    20190201 03:14:06      test_resize_vm_positive[local_image-4_1_512-0_2_1024-volume] PASS    20190201 03:18:49      test_resize_vm_positive[local_image-4_1_512-1_1_0-volume] PASS    20190201 03:25:13      test_resize_vm_negative[local_image-5_0_0-0_0_0-image] PASS    20190201 03:27:37      test_resize_vm_negative[local_image-5_2_512-5_1_512-image] PASS    20190201 03:30:21      test_resize_vm_negative[local_image-5_1_512-4_1_512-image] PASS    20190201 03:32:50      test_resize_vm_negative[local_image-5_1_512-4_1_0-image] PASS    20190201 03:35:34      test_resize_vm_negative[local_image-1_1_512-1_0_512-volume] PASS    20190201 03:38:23      test_resize_different_comp_node[local_image] FAIL    20190201 03:44:42      test_vm_actions_secure_boot_vm FAIL    20190201 03:47:38      test_lock_unlock_secure_boot_vm FAIL    20190201 03:50:23      test_host_reboot_secure_boot_vm PASS    20190201 03:53:02      test_server_group_boot_vms[affinity-2] PASS    20190201 04:02:19      test_server_group_boot_vms[anti_affinity-2] PASS    20190201 04:07:38      test_server_group_launch_vms_in_parallel[affinity-3-4] PASS    20190201 04:09:32      test_server_group_launch_vms_in_parallel[anti_affinity-1-3] PASS    20190201 04:11:24      test_create_snapshot_using_boot_from_image_vm PASS    20190201 04:14:26      test_create_snapshot_using_boot_from_volume_vm PASS    20190201 04:19:30      test_attempt_to_delete_volume_associated_with_snapshot PASS    20190201 04:21:57      test_attach_cinder_volume_to_instance[virtio] PASS    20190201 04:24:43      test_vif_model_from_image[virtio] PASS    20190201 04:27:27      test_autorecovery_image_metadata_in_volume[False-raw-bare] PASS    20190201 04:28:29      test_vm_autorecovery_without_heartbeat[None-None-None-raw-bare-True] PASS    20190201 04:33:12      test_vm_autorecovery_without_heartbeat[None-false-true-qcow2-bare-False] PASS    20190201 04:45:42      test_vm_autorecovery_without_heartbeat[None-true-false-raw-bare-True] PASS    20190201 04:52:14      test_vm_autorecovery_without_heartbeat[dedicated-false-None-raw-bare-False] PASS    20190201 05:04:54      test_vm_autorecovery_without_heartbeat[dedicated-None-false-qcow2-bare-False] PASS    20190201 05:17:27      test_vm_autorecovery_without_heartbeat[shared-None-true-raw-bare-True] PASS    20190201 05:23:47      test_vm_autorecovery_without_heartbeat[shared-false-None-raw-bare-False] PASS    20190201 05:36:22      test_vm_autorecovery_with_heartbeat[None-true-True] PASS    20190201 05:39:29      test_vm_autorecovery_with_heartbeat[dedicated-None-True] PASS    20190201 05:42:32      test_vm_autorecovery_with_heartbeat[None-false-False] PASS    20190201 05:46:29      test_vm_autorecovery_with_heartbeat[shared-None-True] PASS    20190201 05:49:23      test_vm_autorecovery_with_heartbeat[shared-false-False] PASS    20190201 05:53:17      test_vm_heartbeat_without_autorecovery[None-False] PASS    20190201 06:01:45      test_vm_heartbeat_without_autorecovery[true-True] PASS    20190201 06:04:12      test_vm_heartbeat_without_autorecovery[false-False] PASS    20190201 06:12:45      test_vm_heartbeat_without_autorecovery[True-True] From Jason.McKenna at windriver.com Mon Feb 4 15:28:07 2019 From: Jason.McKenna at windriver.com (McKenna, Jason) Date: Mon, 4 Feb 2019 15:28:07 +0000 Subject: [Starlingx-discuss] StarlingX mirror scheduled outage Saturday Feb 9. Message-ID: Hi StarlingX, The facility where the StarlingX official mirror and build servers are hosted will have a scheduled power outage on February 9. The outage is scheduled from 1100 to 2200 UTC (6:00am to 5:00pm EST, 5:00am to 4:00pm CST, 3:00am to 2:00pm PST). During this time, the CENGN hosted StarlingX mirror will be down, and download_mirrors.sh will fetch any artifacts directly from the sources rather than the mirror. Furthermore, automated builds will not occur during this timeframe. If you plan on creating or updating a local mirror of input artifacts, I recommend you run download_mirrors.sh on February 8. This will allow your script to fetch artifacts from either the CENGN mirror or the original source. Furthermore, if you want to grab a pre-built StarlingX ISO image for testing, please download it before the outage. http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/iso/ Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Mon Feb 4 17:09:09 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Feb 2019 17:09:09 +0000 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> Maybe we should rename this to “StarlingX in a Cage” since birds go into cages, not ships into bottles like Airship. brucej From: Javier Romero [mailto:xavinux at gmail.com] Sent: Saturday, February 2, 2019 12:51 PM To: Lara, Cesar Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Cesar, Thank you for your time to answer. Will let you know if I have some ideas. Regards, El sábado, 2 de febrero de 2019, Lara, Cesar > escribió: Yes we are exploring a few possibilities for StarlingX in a bottle, vagrant in one of them. Feel free to throw some ideas at it Regards Cesar Lara Sent from my mobile phone ________________________________ From: Javier Romero > Sent: Saturday, February 2, 2019 11:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Vagrant StarlingX VM. Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- Javier Romero -- Javier Romero -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.seiler at windriver.com Mon Feb 4 17:20:56 2019 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Mon, 4 Feb 2019 17:20:56 +0000 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> , <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> Message-ID: Hmmm. Why not stick with “in a box” which is a well understood term. Not sure the image of a bird in a cage is a positive one. 🤔 Sent from my iPhone On Feb 4, 2019, at 10:11 AM, Jones, Bruce E > wrote: Maybe we should rename this to “StarlingX in a Cage” since birds go into cages, not ships into bottles like Airship. brucej From: Javier Romero [mailto:xavinux at gmail.com] Sent: Saturday, February 2, 2019 12:51 PM To: Lara, Cesar > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Cesar, Thank you for your time to answer. Will let you know if I have some ideas. Regards, El sábado, 2 de febrero de 2019, Lara, Cesar > escribió: Yes we are exploring a few possibilities for StarlingX in a bottle, vagrant in one of them. Feel free to throw some ideas at it Regards Cesar Lara Sent from my mobile phone ________________________________ From: Javier Romero > Sent: Saturday, February 2, 2019 11:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Vagrant StarlingX VM. Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- Javier Romero -- Javier Romero _______________________________________________ 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 bruce.e.jones at intel.com Mon Feb 4 17:24:42 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Feb 2019 17:24:42 +0000 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> , <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BBFD1A6F0@fmsmsx123.amr.corp.intel.com> I like it. StarlingX in a (virtual) box ☺ brucej From: Seiler, Glenn [mailto:glenn.seiler at windriver.com] Sent: Monday, February 4, 2019 9:21 AM To: Jones, Bruce E Cc: Javier Romero ; Lara, Cesar ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Hmmm. Why not stick with “in a box” which is a well understood term. Not sure the image of a bird in a cage is a positive one. 🤔 Sent from my iPhone On Feb 4, 2019, at 10:11 AM, Jones, Bruce E > wrote: Maybe we should rename this to “StarlingX in a Cage” since birds go into cages, not ships into bottles like Airship. brucej From: Javier Romero [mailto:xavinux at gmail.com] Sent: Saturday, February 2, 2019 12:51 PM To: Lara, Cesar > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Cesar, Thank you for your time to answer. Will let you know if I have some ideas. Regards, El sábado, 2 de febrero de 2019, Lara, Cesar > escribió: Yes we are exploring a few possibilities for StarlingX in a bottle, vagrant in one of them. Feel free to throw some ideas at it Regards Cesar Lara Sent from my mobile phone ________________________________ From: Javier Romero > Sent: Saturday, February 2, 2019 11:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Vagrant StarlingX VM. Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- Javier Romero -- Javier Romero _______________________________________________ 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 jose.perez.carranza at intel.com Mon Feb 4 17:27:54 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Mon, 4 Feb 2019 17:27:54 +0000 Subject: [Starlingx-discuss] [Test] Proposal for Test Repository In-Reply-To: <19C65A6E92EA384D809B1772130CD7F8621758E9@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4825AE74@ALA-MBD.corp.ad.wrs.com> <0A5D9A624DF90343892F8F3FE7DE525A2A935DD0@fmsmsx101.amr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621758E9@ALA-MBD.corp.ad.wrs.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A93702F@fmsmsx101.amr.corp.intel.com> Hi All As discussed on weekly test meeting we decide to consolidate in only one repo all the test for StarlingX. The main Idea is to have a common place to contribute with different test cases. Here is a draft document where you can add your comments and we can discuss on 02/05 Test Meeting to have an official repo structure. https://docs.google.com/document/d/1TuBZHSv0zerLp17PqIxk8HKXh0XsQJ_VAolO5rMGiac/edit?usp=sharing Regards, José From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Monday, January 28, 2019 8:11 AM To: Perez Carranza, Jose ; Waheed, Numan ; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: RE: [Test] Proposal for Test Repository Hi Jose, I think 3 separate repos will be easier from maintenance and usage perspective. - Manual/robot/pytest have very different installation/usage/contribution requirements, it would be much easier to maintain them with standard repo structure, i.e., package requirements and README in root directory of a repo. - User won't be forced to download everything if they are only interested in contributing to one of them. - Easier to separate code reviews. BR, Yang From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: January-28-19 8:50 AM To: Waheed, Numan; starlingx-discuss at lists.starlingx.io; Cabrales, Ada Subject: Re: [Starlingx-discuss] [Test] Proposal for Test Repository Hi Newman Some comments inline Regards, José From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Friday, January 25, 2019 3:18 PM To: starlingx-discuss at lists.starlingx.io; Cabrales, Ada > Subject: [Starlingx-discuss] [Test] Proposal for Test Repository Hi Ada and Christopher, After investigating existing openstack test projects, I think we should have: * separate repo for test cases that are independent from each other. Since they require different instructions for almost everything (install, usage, rules, etc.) * one repo for one auto project. Subrepos are not recommended due to complicity involved in updating common libraries(keywords, fixtures, etc.) and their usages(test cases). I think having 3 different repositories can become hard to maintain, also could be confusing for people who is contributing to the project. Maybe we can consolidate all in one repo divided by directories , below an example: -> stx-test - manual-tests - automated-tests - robot-suite - pytets-suite Thus I suggest 3 different repositories: - repo for manual test cases - Is this section going to have actual scripts or just Test Specifications (preconditions, steps and expected result) in a plain text? - repo for robot test cases - repo for pytest test cases Inside automated test repository, I would suggest the following structure: README.rst LICENSE setup.py tox.ini # pep8, py27, etc requirements.txt # project package requirements consts/... # directory for various constants modules keywords/... # directory for helper modules testfixtures/ # directory for commonly used test fixtures modules testcases/cli/mtc/... # directory for mtc test cases that is mainly using cli testcases/cli/heat/... testcases/cli/nova/... testcases/cli/networking/... testcases/cli/security/... testcases/cli/storage/... testcases/cli/sysinv/... testcases/rest/... # directory for restAPI test cases testcases/horizon/... # directory for horizon test cases testcases/system_test/... # directory for complex system test scenarios Agree with this structure inside of the automated test suites. Thanks, Numan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Mon Feb 4 18:08:27 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Mon, 4 Feb 2019 18:08:27 +0000 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: <9A85D2917C58154C960D95352B22818BBFD1A6F0@fmsmsx123.amr.corp.intel.com> References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> , <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD1A6F0@fmsmsx123.amr.corp.intel.com> Message-ID: Would not this be a bird in a box, or in short “bird box”? Dariush From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: February-04-19 12:25 PM To: Seiler, Glenn Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. I like it. StarlingX in a (virtual) box ☺ brucej From: Seiler, Glenn [mailto:glenn.seiler at windriver.com] Sent: Monday, February 4, 2019 9:21 AM To: Jones, Bruce E > Cc: Javier Romero >; Lara, Cesar >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Hmmm. Why not stick with “in a box” which is a well understood term. Not sure the image of a bird in a cage is a positive one. 🤔 Sent from my iPhone On Feb 4, 2019, at 10:11 AM, Jones, Bruce E > wrote: Maybe we should rename this to “StarlingX in a Cage” since birds go into cages, not ships into bottles like Airship. brucej From: Javier Romero [mailto:xavinux at gmail.com] Sent: Saturday, February 2, 2019 12:51 PM To: Lara, Cesar > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. Cesar, Thank you for your time to answer. Will let you know if I have some ideas. Regards, El sábado, 2 de febrero de 2019, Lara, Cesar > escribió: Yes we are exploring a few possibilities for StarlingX in a bottle, vagrant in one of them. Feel free to throw some ideas at it Regards Cesar Lara Sent from my mobile phone ________________________________ From: Javier Romero > Sent: Saturday, February 2, 2019 11:07 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Vagrant StarlingX VM. Hi Team, Think that perhaps may be useful for new users to have a Vagrant preconfigured AIO VM to use StarlingX for the fiirst time. https://www.vagrantup.com If this can be useful I can help with that. Vagrant use VirtualBox by default to star the preconfigured VM and can also be set to be used with QEMU. Best Regards, -- Javier Romero -- Javier Romero _______________________________________________ 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 michel.thebeau at windriver.com Mon Feb 4 18:34:16 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 4 Feb 2019 13:34:16 -0500 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> , <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD1A6F0@fmsmsx123.amr.corp.intel.com> Message-ID: <1549305256.13783.7.camel@windriver.com> a box of birds? https://idioms.thefreedictionary.com/a+box+of+birds On Mon, 2019-02-04 at 18:08 +0000, Eslimi, Dariush wrote: > Would not this be a bird in a box, or in short “bird box”? >   > Dariush >   > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com]  > Sent: February-04-19 12:25 PM > To: Seiler, Glenn > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >   > I like it.  StarlingX in a (virtual) box J >   >         brucej >   > From: Seiler, Glenn [mailto:glenn.seiler at windriver.com]  > Sent: Monday, February 4, 2019 9:21 AM > To: Jones, Bruce E > Cc: Javier Romero ; Lara, Cesar com>; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >   > Hmmm. Why not stick with “in a box” which is a well understood term. > Not sure the image of a bird in a cage is a positive one. 🤔 > > Sent from my iPhone > > On Feb 4, 2019, at 10:11 AM, Jones, Bruce E > wrote: > > Maybe we should rename this to “StarlingX in a Cage” since birds go > into cages, not ships into bottles like Airship. >   >        brucej >   > From: Javier Romero [mailto:xavinux at gmail.com]  > Sent: Saturday, February 2, 2019 12:51 PM > To: Lara, Cesar > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >   > Cesar, >   > Thank you for your time to answer. Will let you know if I have some > ideas. >   > Regards, > > > El sábado, 2 de febrero de 2019, Lara, Cesar > escribió: > Yes we are exploring a few possibilities for StarlingX in a bottle, > vagrant in one of them. Feel free to throw some ideas at it >   > Regards > Cesar Lara > Sent from my mobile phone > From: Javier Romero > Sent: Saturday, February 2, 2019 11:07 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Vagrant StarlingX VM. >   > Hi Team, >   > Think that perhaps may be useful for new users to have a Vagrant > preconfigured AIO VM to use StarlingX for the fiirst time. >   > https://www.vagrantup.com >   > If this can be useful I can help with that. >   > Vagrant use VirtualBox by default to star the preconfigured VM and > can also be set to be  used with QEMU. >   > Best Regards, >   >   >   > > > -- > Javier Romero >   >   >   > > > -- > Javier Romero >   >   >   > _______________________________________________ > 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 sgw at linux.intel.com Mon Feb 4 18:40:28 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 4 Feb 2019 10:40:28 -0800 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: <1549305256.13783.7.camel@windriver.com> References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> <9A85D2917C58154C960D95352B22818BBFD1A5F4@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD1A6F0@fmsmsx123.amr.corp.intel.com> <1549305256.13783.7.camel@windriver.com> Message-ID: <2367284f-9e80-b9da-a4c1-b502b8d268ce@linux.intel.com> On 2/4/19 10:34 AM, Michel Thebeau wrote: > a box of birds? > https://idioms.thefreedictionary.com/a+box+of+birds > I like this one, as I think we might get in trouble with Netflix's "bird box" Interesting movie BTW! Sau! > > > On Mon, 2019-02-04 at 18:08 +0000, Eslimi, Dariush wrote: >> Would not this be a bird in a box, or in short “bird box”? >> >> Dariush >> >> From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] >> Sent: February-04-19 12:25 PM >> To: Seiler, Glenn >> Cc: starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >> >> I like it.  StarlingX in a (virtual) box J >> >>         brucej >> >> From: Seiler, Glenn [mailto:glenn.seiler at windriver.com] >> Sent: Monday, February 4, 2019 9:21 AM >> To: Jones, Bruce E >> Cc: Javier Romero ; Lara, Cesar > com>; starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >> >> Hmmm. Why not stick with “in a box” which is a well understood term. >> Not sure the image of a bird in a cage is a positive one. 🤔 >> >> Sent from my iPhone >> >> On Feb 4, 2019, at 10:11 AM, Jones, Bruce E >> wrote: >> >> Maybe we should rename this to “StarlingX in a Cage” since birds go >> into cages, not ships into bottles like Airship. >> >>        brucej >> >> From: Javier Romero [mailto:xavinux at gmail.com] >> Sent: Saturday, February 2, 2019 12:51 PM >> To: Lara, Cesar >> Cc: starlingx-discuss at lists.starlingx.io >> Subject: Re: [Starlingx-discuss] Vagrant StarlingX VM. >> >> Cesar, >> >> Thank you for your time to answer. Will let you know if I have some >> ideas. >> >> Regards, >> >> >> El sábado, 2 de febrero de 2019, Lara, Cesar >> escribió: >> Yes we are exploring a few possibilities for StarlingX in a bottle, >> vagrant in one of them. Feel free to throw some ideas at it >> >> Regards >> Cesar Lara >> Sent from my mobile phone >> From: Javier Romero >> Sent: Saturday, February 2, 2019 11:07 AM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] Vagrant StarlingX VM. >> >> Hi Team, >> >> Think that perhaps may be useful for new users to have a Vagrant >> preconfigured AIO VM to use StarlingX for the fiirst time. >> >> https://www.vagrantup.com >> >> If this can be useful I can help with that. >> >> Vagrant use VirtualBox by default to star the preconfigured VM and >> can also be set to be  used with QEMU. >> >> Best Regards, >> >> >> >> >> >> -- >> Javier Romero >> >> >> >> >> >> -- >> Javier Romero >> >> >> >> _______________________________________________ >> 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 Ken.Young at windriver.com Mon Feb 4 18:48:55 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Mon, 4 Feb 2019 18:48:55 +0000 Subject: [Starlingx-discuss] CVE Support and Scanning Message-ID: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Team, A “Lights On” feature for the 2019.05 release is “CVE Upgrades”. This feature will enable ongoing security updates for the master branch and selectively provide CVE corrective content to supported releases. The first step for this feature is to define a policy. With the help of the Starling X security team, a draft of this policy has been provided below: https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy Please review and provide comments. I plan to reserve a spot on the Community call for any discussion on Wednesday and start the discussion with the build team to identify tools to support this policy on Thursday. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Mon Feb 4 18:54:04 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 4 Feb 2019 10:54:04 -0800 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Message-ID: On 2/4/19 10:48 AM, Young, Ken wrote: > Team, > > A “Lights On” feature for the 2019.05 release is “CVE Upgrades”.  This > feature will enable ongoing security updates for the master branch and > selectively provide CVE corrective content to supported releases. The > first step for this feature is to define a policy.  With the help of the > Starling X security team, a draft of this policy has been provided below: > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy > > Please review and provide comments.  I plan to reserve a spot on the > Community call for any discussion on Wednesday and start the discussion > with the build team to identify tools to support this policy on Thursday. > Can we try to avoid slideware in the Wiki please, ultimately wiki should be editable. Sau! > Regards, > > Ken Y > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From vm.rod25 at gmail.com Mon Feb 4 19:26:33 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 4 Feb 2019 13:26:33 -0600 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Message-ID: On Mon, Feb 4, 2019 at 12:49 PM Young, Ken wrote: > > Team, > > > > A “Lights On” feature for the 2019.05 release is “CVE Upgrades”. This feature will enable ongoing security updates for the master branch and selectively provide CVE corrective content to supported releases. The first step for this feature is to define a policy. With the help of the Starling X security team, a draft of this policy has been provided below: > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy > > > > Please review and provide comments. I plan to reserve a spot on the Community call for any discussion on Wednesday and start the discussion with the build team to identify tools to support this policy on Thursday. Question on the last slide you propose a formula as Criticality >= 7 What standard are you plan to use? CVSS v3.0 or v2.0 For example, taking this MariaDB https://nvd.nist.gov/vuln/detail/CVE-2017-15365 Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 My recommendation will be to use the highest one despite if the score came from V2 or V3 However, I think we should specify that somewhere One more question, when you said critical issues are fixed if corrections are available upstream it means that ( taking the previous example ) if MariaDB provides a Patch, is merged in master and released in the latest release, like in the previous example : https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e But CentOS has not taken it yet, are we OK to apply this patch in STX until CentOS apply in incoming future? Regards Victor R > > > Regards, > > Ken Y > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Mon Feb 4 19:31:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 4 Feb 2019 19:31:07 +0000 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Message-ID: <9A85D2917C58154C960D95352B22818BBFD1A918@fmsmsx123.amr.corp.intel.com> Victor wrote: > One more question, when you said critical issues are fixed if corrections are available upstream it means that ( taking the previous example ) if MariaDB provides a Patch, is merged in master and released in the latest release, like in the previous example : > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e > But CentOS has not taken it yet, are we OK to apply this patch in STX until CentOS apply in incoming future? If we are picking up a component from a distro (like CentOS), I think the policy should be that we pick up the change from the distro. If we're picking up a component directly from its upstream, we pick up the fix from the upstream. So I think the answer is "it depends". brucej -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Monday, February 4, 2019 11:27 AM To: Young, Ken Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CVE Support and Scanning On Mon, Feb 4, 2019 at 12:49 PM Young, Ken wrote: > > Team, > > > > A “Lights On” feature for the 2019.05 release is “CVE Upgrades”. This feature will enable ongoing security updates for the master branch and selectively provide CVE corrective content to supported releases. The first step for this feature is to define a policy. With the help of the Starling X security team, a draft of this policy has been provided below: > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy > > > > Please review and provide comments. I plan to reserve a spot on the Community call for any discussion on Wednesday and start the discussion with the build team to identify tools to support this policy on Thursday. Question on the last slide you propose a formula as Criticality >= 7 What standard are you plan to use? CVSS v3.0 or v2.0 For example, taking this MariaDB https://nvd.nist.gov/vuln/detail/CVE-2017-15365 Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 My recommendation will be to use the highest one despite if the score came from V2 or V3 However, I think we should specify that somewhere One more question, when you said critical issues are fixed if corrections are available upstream it means that ( taking the previous example ) if MariaDB provides a Patch, is merged in master and released in the latest release, like in the previous example : https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e But CentOS has not taken it yet, are we OK to apply this patch in STX until CentOS apply in incoming future? Regards Victor R > > > Regards, > > Ken Y > > _______________________________________________ > 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 michel.thebeau at windriver.com Mon Feb 4 20:25:44 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 4 Feb 2019 15:25:44 -0500 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Message-ID: <1549311944.13783.17.camel@windriver.com> Hi Victor, > My recommendation will be to use the highest one despite if > the score came from V2 or V3 The two sets of metrics are not comparable.  StarlingX policy should refer to either CVSS v2 or v3. > One more question, when you said critical issues are fixed > if corrections are available upstream it means that... The text of one of the slides has written "StarlingX depends on the upstream OS community to fix CVEs".  Is this reference to upstream you intend?  In that text 'OS community' would refer to CentOS community rather than the example MariaDB community. M On Mon, 2019-02-04 at 13:26 -0600, Victor Rodriguez wrote: > On Mon, Feb 4, 2019 at 12:49 PM Young, Ken > wrote: > > > > > > Team, > > > > > > > > A “Lights On” feature for the 2019.05 release is “CVE > > Upgrades”.  This feature will enable ongoing security updates for > > the master branch and selectively provide CVE corrective content to > > supported releases.  The first step for this feature is to define a > > policy.  With the help of the Starling X security team, a draft of > > this policy has been provided below: > > > > > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Poli > > cy > > > > > > > > Please review and provide comments.  I plan to reserve a spot on > > the Community call for any discussion on Wednesday and start the > > discussion with the build team to identify tools to support this > > policy on Thursday. > > Question on the last slide you propose a formula as > > Criticality >= 7 > > What standard are you plan to use? CVSS v3.0 or v2.0 > > For example, taking this MariaDB > > https://nvd.nist.gov/vuln/detail/CVE-2017-15365 > > Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 > > My recommendation will be to use the highest one despite if the score > came from V2 or V3 > However, I think we should specify that somewhere > > One more question, when you said critical issues are fixed if > corrections are available upstream it means that ( taking the > previous > example ) if MariaDB provides a Patch, is merged in master and > released in the latest release,  like in the previous example : > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753 > 699787fdf46e > > But CentOS has not taken it yet, are we OK to apply this patch in STX > until CentOS apply in incoming future? > > Regards > > Victor R > > > > > > > > Regards, > > > > Ken Y > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From vm.rod25 at gmail.com Mon Feb 4 20:41:09 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 4 Feb 2019 14:41:09 -0600 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: <1549311944.13783.17.camel@windriver.com> References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> <1549311944.13783.17.camel@windriver.com> Message-ID: On Mon, Feb 4, 2019 at 2:25 PM Michel Thebeau wrote: > > Hi Victor, > > > My recommendation will be to use the highest one despite if > > the score came from V2 or V3 > > The two sets of metrics are not comparable. StarlingX policy should > refer to either CVSS v2 or v3. > But slide in the wiki say : Criticality >= 7 , if V2 = 5 adn V3 =8 shoudl that CVE be consider as Criticality >= 7 ? My observation is that we shoudl specify Criticality >= 7 ( for either V2 or V3 ) > > One more question, when you said critical issues are fixed > > if corrections are available upstream it means that... > > The text of one of the slides has written "StarlingX depends on the > upstream OS community to fix CVEs". Is this reference to upstream you > intend? In that text 'OS community' would refer to CentOS community > rather than the example MariaDB community. > Ok, thanks for the clarification. I think that there might be some special cases where we might prompt to apply a CVE patch before CentOS, but that might have to be desided in the security meeeting when they analyze the CVEs > > M > > > On Mon, 2019-02-04 at 13:26 -0600, Victor Rodriguez wrote: > > On Mon, Feb 4, 2019 at 12:49 PM Young, Ken > > wrote: > > > > > > > > > Team, > > > > > > > > > > > > A “Lights On” feature for the 2019.05 release is “CVE > > > Upgrades”. This feature will enable ongoing security updates for > > > the master branch and selectively provide CVE corrective content to > > > supported releases. The first step for this feature is to define a > > > policy. With the help of the Starling X security team, a draft of > > > this policy has been provided below: > > > > > > > > > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Poli > > > cy > > > > > > > > > > > > Please review and provide comments. I plan to reserve a spot on > > > the Community call for any discussion on Wednesday and start the > > > discussion with the build team to identify tools to support this > > > policy on Thursday. > > > > Question on the last slide you propose a formula as > > > > Criticality >= 7 > > > > What standard are you plan to use? CVSS v3.0 or v2.0 > > > > For example, taking this MariaDB > > > > https://nvd.nist.gov/vuln/detail/CVE-2017-15365 > > > > Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 > > > > My recommendation will be to use the highest one despite if the score > > came from V2 or V3 > > However, I think we should specify that somewhere > > > > One more question, when you said critical issues are fixed if > > corrections are available upstream it means that ( taking the > > previous > > example ) if MariaDB provides a Patch, is merged in master and > > released in the latest release, like in the previous example : > > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753 > > 699787fdf46e > > > > But CentOS has not taken it yet, are we OK to apply this patch in STX > > until CentOS apply in incoming future? > > > > Regards > > > > Victor R > > > > > > > > > > > > Regards, > > > > > > Ken Y > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From chris.friesen at windriver.com Mon Feb 4 20:51:03 2019 From: chris.friesen at windriver.com (Chris Friesen) Date: Mon, 4 Feb 2019 14:51:03 -0600 Subject: [Starlingx-discuss] VCPU scheduler priority In-Reply-To: References: Message-ID: <902ba073-4ab3-7f39-5bdc-3794f09d3b89@windriver.com> On 2/4/2019 6:08 AM, Himanshu Goyal wrote: > Hi, > > Please suggest how to set VCPU Scheduler policy in flavor, Not able to > found that in flavor metadata. What problem are you trying to solve? There may be alternate solutions. Chris From michel.thebeau at windriver.com Mon Feb 4 21:00:15 2019 From: michel.thebeau at windriver.com (Michel Thebeau) Date: Mon, 4 Feb 2019 16:00:15 -0500 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> <1549311944.13783.17.camel@windriver.com> Message-ID: <1549314015.13783.28.camel@windriver.com> On Mon, 2019-02-04 at 14:41 -0600, Victor Rodriguez wrote: > On Mon, Feb 4, 2019 at 2:25 PM Michel Thebeau > wrote: > > > > > > Hi Victor, > > > > > > > > My recommendation will be to use the highest one despite if > > > the score came from V2 or V3 > > The two sets of metrics are not comparable.  StarlingX policy > > should > > refer to either CVSS v2 or v3. > > > But slide in the wiki say : Criticality >= 7 , if V2 = 5 adn V3 =8 > shoudl that CVE be consider as Criticality >= 7 ? > My observation is that we shoudl specify Criticality >= 7 ( for > either > V2 or V3 ) I believe that Ken has a particular metric in mind, which was not documented.  The value of '7' is specific to the metric not documentated.  There is a hint in the document that the value '7' is for 'critical' CVEs issues.  ... refer to this document: https://nvd.nist.gov/vuln-metrics/cvss '7' is the boundary for the highest rating of CVSS v2.  Where as CVSS v3 lists critical as >9.0 > > > > > > > > > One more question, when you said critical issues are fixed > > > if corrections are available upstream it means that... > > The text of one of the slides has written "StarlingX depends on the > > upstream OS community to fix CVEs".  Is this reference to upstream > > you > > intend?  In that text 'OS community' would refer to CentOS > > community > > rather than the example MariaDB community. > > > Ok, thanks for the clarification. > I think that there might be some special cases where we might prompt > to apply a CVE patch before CentOS, but that might have to be desided > in the security meeeting when they analyze the CVEs I expect that it is unlikely a team in StarlingX will match the proficiency of the teams behind CentOS.  But I agree that the StarlingX community will discuss these things. M > > > > > > > M > > > > > > On Mon, 2019-02-04 at 13:26 -0600, Victor Rodriguez wrote: > > > > > > On Mon, Feb 4, 2019 at 12:49 PM Young, Ken > > om> > > > wrote: > > > > > > > > > > > > > > > > Team, > > > > > > > > > > > > > > > > A “Lights On” feature for the 2019.05 release is “CVE > > > > Upgrades”.  This feature will enable ongoing security updates > > > > for > > > > the master branch and selectively provide CVE corrective > > > > content to > > > > supported releases.  The first step for this feature is to > > > > define a > > > > policy.  With the help of the Starling X security team, a draft > > > > of > > > > this policy has been provided below: > > > > > > > > > > > > > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_ > > > > Poli > > > > cy > > > > > > > > > > > > > > > > Please review and provide comments.  I plan to reserve a spot > > > > on > > > > the Community call for any discussion on Wednesday and start > > > > the > > > > discussion with the build team to identify tools to support > > > > this > > > > policy on Thursday. > > > Question on the last slide you propose a formula as > > > > > > Criticality >= 7 > > > > > > What standard are you plan to use? CVSS v3.0 or v2.0 > > > > > > For example, taking this MariaDB > > > > > > https://nvd.nist.gov/vuln/detail/CVE-2017-15365 > > > > > > Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 > > > > > > My recommendation will be to use the highest one despite if the > > > score > > > came from V2 or V3 > > > However, I think we should specify that somewhere > > > > > > One more question, when you said critical issues are fixed if > > > corrections are available upstream it means that ( taking the > > > previous > > > example ) if MariaDB provides a Patch, is merged in master and > > > released in the latest release,  like in the previous example : > > > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7 > > > e753 > > > 699787fdf46e > > > > > > But CentOS has not taken it yet, are we OK to apply this patch in > > > STX > > > until CentOS apply in incoming future? > > > > > > Regards > > > > > > Victor R > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > Ken Y > > > > > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > > > scus > > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss From vm.rod25 at gmail.com Mon Feb 4 21:23:44 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Mon, 4 Feb 2019 15:23:44 -0600 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: <1549314015.13783.28.camel@windriver.com> References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> <1549311944.13783.17.camel@windriver.com> <1549314015.13783.28.camel@windriver.com> Message-ID: On Mon, Feb 4, 2019 at 3:01 PM Michel Thebeau wrote: > > On Mon, 2019-02-04 at 14:41 -0600, Victor Rodriguez wrote: > > On Mon, Feb 4, 2019 at 2:25 PM Michel Thebeau > > wrote: > > > > > > > > > Hi Victor, > > > > > > > > > > > My recommendation will be to use the highest one despite if > > > > the score came from V2 or V3 > > > The two sets of metrics are not comparable. StarlingX policy > > > should > > > refer to either CVSS v2 or v3. > > > > > But slide in the wiki say : Criticality >= 7 , if V2 = 5 adn V3 =8 > > shoudl that CVE be consider as Criticality >= 7 ? > > My observation is that we shoudl specify Criticality >= 7 ( for > > either > > V2 or V3 ) > > > I believe that Ken has a particular metric in mind, which was not > documented. The value of '7' is specific to the metric not > documentated. There is a hint in the document that the value '7' is > for 'critical' CVEs issues. > > ... refer to this document: > https://nvd.nist.gov/vuln-metrics/cvss > > '7' is the boundary for the highest rating of CVSS v2. Where as CVSS > v3 lists critical as >9.0 > Ok , then Based on NVD Vulnerability Severity Ratings 7 is ok for both V2 or V3 We cond then said in the wiki that if CVE critilarity is >= High ... > > > > > > > > > > > > > > > One more question, when you said critical issues are fixed > > > > if corrections are available upstream it means that... > > > The text of one of the slides has written "StarlingX depends on the > > > upstream OS community to fix CVEs". Is this reference to upstream > > > you > > > intend? In that text 'OS community' would refer to CentOS > > > community > > > rather than the example MariaDB community. > > > > > Ok, thanks for the clarification. > > I think that there might be some special cases where we might prompt > > to apply a CVE patch before CentOS, but that might have to be desided > > in the security meeeting when they analyze the CVEs > > > I expect that it is unlikely a team in StarlingX will match the > proficiency of the teams behind CentOS. But I agree that the StarlingX > community will discuss these things. > I have seen cases before, as CVE mantianer of an OS for some time there were times were the severity of the CVE make us really urgent to update the package and release a new version of the OS, our mindset was security first. As an open comunity I woudl like to hear more feedabck from multiple users and developers Regards Victor > M > > > > > > > > > > > > > M > > > > > > > > > On Mon, 2019-02-04 at 13:26 -0600, Victor Rodriguez wrote: > > > > > > > > On Mon, Feb 4, 2019 at 12:49 PM Young, Ken > > > om> > > > > wrote: > > > > > > > > > > > > > > > > > > > > Team, > > > > > > > > > > > > > > > > > > > > A “Lights On” feature for the 2019.05 release is “CVE > > > > > Upgrades”. This feature will enable ongoing security updates > > > > > for > > > > > the master branch and selectively provide CVE corrective > > > > > content to > > > > > supported releases. The first step for this feature is to > > > > > define a > > > > > policy. With the help of the Starling X security team, a draft > > > > > of > > > > > this policy has been provided below: > > > > > > > > > > > > > > > > > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_ > > > > > Poli > > > > > cy > > > > > > > > > > > > > > > > > > > > Please review and provide comments. I plan to reserve a spot > > > > > on > > > > > the Community call for any discussion on Wednesday and start > > > > > the > > > > > discussion with the build team to identify tools to support > > > > > this > > > > > policy on Thursday. > > > > Question on the last slide you propose a formula as > > > > > > > > Criticality >= 7 > > > > > > > > What standard are you plan to use? CVSS v3.0 or v2.0 > > > > > > > > For example, taking this MariaDB > > > > > > > > https://nvd.nist.gov/vuln/detail/CVE-2017-15365 > > > > > > > > Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 > > > > > > > > My recommendation will be to use the highest one despite if the > > > > score > > > > came from V2 or V3 > > > > However, I think we should specify that somewhere > > > > > > > > One more question, when you said critical issues are fixed if > > > > corrections are available upstream it means that ( taking the > > > > previous > > > > example ) if MariaDB provides a Patch, is merged in master and > > > > released in the latest release, like in the previous example : > > > > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7 > > > > e753 > > > > 699787fdf46e > > > > > > > > But CentOS has not taken it yet, are we OK to apply this patch in > > > > STX > > > > until CentOS apply in incoming future? > > > > > > > > Regards > > > > > > > > Victor R > > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > Ken Y > > > > > > > > > > _______________________________________________ > > > > > Starlingx-discuss mailing list > > > > > Starlingx-discuss at lists.starlingx.io > > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-di > > > > > scus > > > > > s > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > > uss From Ken.Young at windriver.com Mon Feb 4 22:23:59 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Mon, 4 Feb 2019 22:23:59 +0000 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> Message-ID: <6E7E2668-C4A0-4290-A79F-499F8E4F94C8@windriver.com> See inline. On 2019-02-04, 2:26 PM, "Victor Rodriguez" wrote: On Mon, Feb 4, 2019 at 12:49 PM Young, Ken wrote: > > Team, > > > > A “Lights On” feature for the 2019.05 release is “CVE Upgrades”. This feature will enable ongoing security updates for the master branch and selectively provide CVE corrective content to supported releases. The first step for this feature is to define a policy. With the help of the Starling X security team, a draft of this policy has been provided below: > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy > > > > Please review and provide comments. I plan to reserve a spot on the Community call for any discussion on Wednesday and start the discussion with the build team to identify tools to support this policy on Thursday. Question on the last slide you propose a formula as Criticality >= 7 What standard are you plan to use? CVSS v3.0 or v2.0 I am suggesting we start with v2. I need to look into v3 a little more. For example, taking this MariaDB https://nvd.nist.gov/vuln/detail/CVE-2017-15365 Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 My recommendation will be to use the highest one despite if the score came from V2 or V3 However, I think we should specify that somewhere Agreed. One more question, when you said critical issues are fixed if corrections are available upstream it means that ( taking the previous example ) if MariaDB provides a Patch, is merged in master and released in the latest release, like in the previous example : https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e But CentOS has not taken it yet, are we OK to apply this patch in STX until CentOS apply in incoming future? We will wait for CentOS. We are in the process of patch elimination. I do not to carry more. Regards Victor R > > > Regards, > > Ken Y > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Tue Feb 5 14:05:57 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 5 Feb 2019 15:05:57 +0100 (CET) Subject: [Starlingx-discuss] Installation problem: Configuration failed: Failed to update hiera configuration In-Reply-To: <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> References: <1484346064.187533.1549035095571@communicator.strato.com> <4430FF2D-2A7C-4C5F-85C9-D3EEBC250697@windriver.com> <1883615762.190291.1549037961751@communicator.strato.com> <87F75100-3132-4085-B3CA-E851E0725B6C@windriver.com> Message-ID: <1355835714.102284.1549375557966@communicator.strato.com> [root at localhost ~(keystone_admin)]# openstack endpoint list +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ | 0c6612f4307548ac93a7f193b8e2434d | RegionOne | barbican | key-manager | True | admin | http://127.0.0.1:9311 | | 9b37261408974b36b2ea57cfe159eada | RegionOne | barbican | key-manager | True | internal | http://127.0.0.1:9311 | | d8b3e9f76c8a478796cc384961c9d202 | RegionOne | barbican | key-manager | True | public | http://127.0.0.1:9311 | | 08126550bd5c4027a2bb0b6ea147ba71 | RegionOne | keystone | identity | True | admin | http://127.0.0.1:5000/v3 | | e3403a40c8be45a8a6b3535832d8b06e | RegionOne | keystone | identity | True | internal | http://127.0.0.1:5000/v3 | | 2b2c606607464e61b2d4c1c9298d744d | RegionOne | keystone | identity | True | public | http://127.0.0.1:5000/v3 | | fe2ffb3fd52e4f0e91e41c7688ec6e81 | RegionOne | sysinv | platform | True | admin | http://127.0.0.1:6385/v1 | | 5099dee5af8a46eb9ea018ab3c175521 | RegionOne | sysinv | platform | True | internal | http://127.0.0.1:6385/v1 | | 11b28a902ebe425999b825fe63e372b5 | RegionOne | sysinv | platform | True | public | http://127.0.0.1:6385/v1 | +----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+ > "Peters, Matt" hat am 1. Februar 2019 um 17:38 geschrieben: > > > Hello, > I'm not sure why it is giving that error response. > > Are you able to run the following? > openstack endpoint list > > > On 2019-02-01, 11:19 AM, "Marcel Schaible" wrote: > > Hi Matt, > > thanks for your response. > > controller-0:~# source /etc/nova/openrc > -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0 > internalURL endpoint for smapi service in RegionOne region not found > [root at controller-0 ~(keystone_admin)]# > > Any idea what "RegionOne" mean? > Thanks > Marcel > > > > "Peters, Matt" hat am 1. Februar 2019 um 17:07 geschrieben: > > > > > > Hell Marcel, > > If your system is still in that state, can you run the following commands? > > > > source /etc/nova/openrc > > system host-ethernet-port-list controller-0 > > system host-if-list -a controller-0 > > > > > > On 2019-02-01, 10:32 AM, "Marcel Schaible" wrote: > > > > Hi, > > > > during installation when appling the configuration I'll get an error message from hiera: > > > > Configuration failed: Failed to update hiera configuration > > > > Configuration log and apply_manifet.log is attached below. > > > > Any idea or hint? > > > > Thanks > > > > Marcel > > > > > > > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:25 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: > > Aborting configuration > > localhost:~# config_controller > > System Configuration > > ==================== > > Enter Q at any prompt to abort... > > > > System date and time: > > --------------------- > > > > The system date and time must be set now. Note that UTC time must be used and > > that the date and time must be set as accurately as possible, even if NTP/PTP is > > to be configured later. > > > > Current system date and time (UTC): 2019-02-01 15:15:40 > > > > Is the current date and time correct? [y/n]: y > > Current system date and time will be used. > > > > System timezone: > > ---------------- > > > > The system timezone must be set now. The timezone must be a valid timezone from > > /usr/share/zoneinfo (e.g. UTC, Asia/Hong_Kong, etc...) > > > > Please input the timezone[UTC]:Europe/Berlin > > > > System Configuration: > > --------------------- > > > > System mode. Available options are: > > > > 1) duplex-direct - two node redundant configuration. Management and > > infrastructure networks are directly connected to peer ports > > 2) duplex - two node redundant configuration. > > 3) simplex - single node non-redundant configuration. > > System mode [duplex-direct]: 1 > > > > PXEBoot Network: > > ---------------- > > > > The PXEBoot network is used for initial booting and installation of each node. > > IP addresses on this network are reachable only within the data center. > > > > The default configuration combines the PXEBoot network and the management > > network. If a separate PXEBoot network is used, it will share the management > > interface, which requires the management network to be placed on a VLAN. > > > > Configure a separate PXEBoot network [y/N]: N > > > > Management Network: > > ------------------- > > > > The management network is used for internal communication between platform > > components. IP addresses on this network are reachable only within the data > > center. > > > > A management bond interface provides redundant connections for the management > > network. > > It is strongly recommended to configure Management interface link > > aggregation, for All-in-one duplex-direct. > > > > Management interface link aggregation [y/N]: y > > Management interface [bond0]: > > Management interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) 802.3ad (LACP) policy > > 2) Active-backup policy > > > > Management interface bonding policy [802.3ad]: > > A maximum of 2 physical interfaces can be attached to the management interface. > > > > First management interface member [enp3s0f1]: enp8s20f4 > > Second management interface member []: enp8s20f5 > > Management subnet [192.168.204.0/24]: 172.27.1.0/24 > > Use entire management subnet [Y/n]: Y > > > > IP addresses can be assigned to hosts dynamically or a static IP address can be > > specified for each host. This choice applies to both the management network and > > infrastructure network (if configured). > > Warning: Selecting 'N', or static IP address allocation, disables automatic > > provisioning of new hosts in System Inventory, requiring the user to manually > > provision using the 'system host-add' command. > > Dynamic IP address allocation [Y/n]: Y > > Management Network Multicast subnet [239.1.1.0/28]: > > > > Infrastructure Network: > > ----------------------- > > > > The infrastructure network is used for internal communication between platform > > components to offload the management network of high bandwidth services. IP > > addresses on this network are reachable only within the data center. > > > > If a separate infrastructure interface is not configured the management network > > will be used. > > > > It is NOT recommended to configure infrastructure network for All-in- > > one duplex-direct. > > Configure an infrastructure interface [y/N]: N > > > > External OAM Network: > > --------------------- > > > > The external OAM network is used for management of the cloud. It also provides > > access to the platform APIs. IP addresses on this network are reachable outside > > the data center. > > > > An external OAM bond interface provides redundant connections for the OAM > > network. > > > > External OAM interface link aggregation [y/N]: y > > External OAM interface [bond1]: > > Configure an external OAM VLAN [y/N]: > > External OAM interface MTU [1500]: > > > > Specify one of the bonding policies. Possible values are: > > 1) Active-backup policy > > 2) Balanced XOR policy > > 3) 802.3ad (LACP) policy > > > > External OAM interface bonding policy [active-backup]: > > A maximum of 2 physical interfaces can be attached to the external OAM > > interface. > > > > First external OAM interface member [enp3s0f0]: enp7s16f1 > > Second external oam interface member []: enp7s16f7 > > External OAM subnet [10.10.10.0/24]: 10.62.150.0/24 > > External OAM gateway address [10.62.150.1]: > > External OAM floating address [10.62.150.2]: > > External OAM address for first controller node [10.62.150.3]: 10.62.150.210 > > External OAM address for second controller node [10.62.150.211]: > > > > Cloud Authentication: > > ------------------------------- > > > > Configure a password for the Cloud admin user The Password must have a minimum > > length of 7 character, and conform to password complexity rules > > Create admin user password: > > Repeat admin user password: > > > > > > > > The following configuration will be applied: > > > > System Configuration > > -------------------- > > Time Zone: Europe/Berlin > > System mode: duplex-direct > > > > PXEBoot Network Configuration > > ----------------------------- > > Separate PXEBoot network not configured > > PXEBoot Controller floating hostname: pxecontroller > > > > Management Network Configuration > > -------------------------------- > > Management interface name: bond0 > > Management interface: bond0 > > Management interface MTU: 1500 > > Management ae member 0: enp8s20f4 > > Management ae member 1: enp8s20f5 > > Management ae policy : 802.3ad > > Management subnet: 172.27.1.0/24 > > Controller floating address: 172.27.1.2 > > Controller 0 address: 172.27.1.3 > > Controller 1 address: 172.27.1.4 > > NFS Management Address 1: 172.27.1.5 > > NFS Management Address 2: 172.27.1.6 > > Controller floating hostname: controller > > Controller hostname prefix: controller- > > OAM Controller floating hostname: oamcontroller > > Dynamic IP address allocation is selected > > Management multicast subnet: 239.1.1.0/28 > > > > Infrastructure Network Configuration > > ------------------------------------ > > Infrastructure interface not configured > > > > External OAM Network Configuration > > ---------------------------------- > > External OAM interface name: bond1 > > External OAM interface: bond1 > > External OAM interface MTU: 1500 > > External OAM ae member 0: enp7s16f1 > > External OAM ae member 1: enp7s16f7 > > External OAM ae policy : active-backup > > External OAM subnet: 10.62.150.0/24 > > External OAM gateway address: 10.62.150.1 > > External OAM floating address: 10.62.150.2 > > External OAM 0 address: 10.62.150.210 > > External OAM 1 address: 10.62.150.211 > > > > Apply the above configuration? [y/n]: y > > > > Applying configuration (this will take several minutes): > > > > 01/08: Creating bootstrap configuration ... DONE > > 02/08: Applying bootstrap manifest ... DONE > > 03/08: Persisting local configuration ... DONE > > 04/08: Populating initial system inventory ... DONE > > 05/08: Creating system configuration ... sysinv 2019-02-01 15:20:44.053 25508 CRITICAL sysinv [-] 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv Traceback (most recent call last): > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/bin/sysinv-puppet", line 10, in > > 2019-02-01 15:20:44.053 25508 TRACE sysinv sys.exit(main()) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 75, in main > > 2019-02-01 15:20:44.053 25508 TRACE sysinv CONF.action.func(CONF.action.path, CONF.action.hostname) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/cmd/puppet.py", line 47, in create_host_config_action > > 2019-02-01 15:20:44.053 25508 TRACE sysinv operator.update_host_config(host) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 30, in _wrapper > > 2019-02-01 15:20:44.053 25508 TRACE sysinv func(self, *args, **kwargs) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/puppet.py", line 145, in update_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv config.update(puppet_plugin.obj.get_host_config(host)) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 99, in get_host_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_interface_configs(context, config) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 1029, in generate_interface_configs > > 2019-02-01 15:20:44.053 25508 TRACE sysinv generate_network_config(context, config, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 924, in generate_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv network_config = get_interface_network_config(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 896, in get_interface_network_config > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_os_ifname(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 507, in get_interface_os_ifname > > 2019-02-01 15:20:44.053 25508 TRACE sysinv os_ifname = get_interface_port_name(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 472, in get_interface_port_name > > 2019-02-01 15:20:44.053 25508 TRACE sysinv port = get_interface_port(context, iface) > > 2019-02-01 15:20:44.053 25508 TRACE sysinv File "/usr/lib64/python2.7/site-packages/sysinv/puppet/interface.py", line 464, in get_interface_port > > 2019-02-01 15:20:44.053 25508 TRACE sysinv return context['ports'][iface['id']] > > 2019-02-01 15:20:44.053 25508 TRACE sysinv KeyError: 24 > > 2019-02-01 15:20:44.053 25508 TRACE sysinv > > Failed to update puppet hiera host config > > > > Configuration failed: Failed to update hiera configuration > > localhost:~# > > > > /tmp/apply_manifest.log: > > ======================== > > > > cp: cannot stat ‘/tmp/hieradata/172.27.1.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 > > Applying puppet bootstrap manifest... > > [DONE] > > > > > > ls /tmp/puppet/hieradata/ > > ========================= > > global.yaml personality.yaml secure_static.yaml static.yaml > > localhost:~# > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > From ada.cabrales at intel.com Tue Feb 5 16:33:28 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 5 Feb 2019 16:33:28 +0000 Subject: [Starlingx-discuss] [ Test ] meeting - 02/05/ -> 02/06 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD67462@FMSMSX114.amr.corp.intel.com> Hello Due to some schedule conflicts, I'm changing the testing meeting for tomorrow, 02/06 at 6am PST. This is a one-time change. Sorry for the short notice. Thanks Ada From bruce.e.jones at intel.com Tue Feb 5 17:00:43 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 5 Feb 2019 17:00:43 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting today and time change for next week Message-ID: <9A85D2917C58154C960D95352B22818BBFD1BCB6@fmsmsx123.amr.corp.intel.com> At today's meeting we reviewed and updated the tracking spreadsheet which can be found here: [0]. We have 18 items of 58 that we are tracking that are at risk or unlikely to make the Stein release. Next week's meeting will start at 6:30 PST (9:30) EST to allow the Test team to have the first 30 minutes of our usual time slot. Brucej [0] https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Feb 5 18:15:26 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 5 Feb 2019 18:15:26 +0000 Subject: [Starlingx-discuss] Distro.openstack meeting today and time change for next week In-Reply-To: <9A85D2917C58154C960D95352B22818BBFD1BCB6@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BBFD1BCB6@fmsmsx123.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD67683@FMSMSX114.amr.corp.intel.com> Hello :) We have a confusion here: Testing meeting for this week will take place tomorrow, 02/06 at 6am PDT. We will use the distro.non-openstack time slot, as they cancelled their meeting occurrence due to the Chinese New Year. Thanks! Ada From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Tuesday, February 5, 2019 11:01 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Distro.openstack meeting today and time change for next week At today's meeting we reviewed and updated the tracking spreadsheet which can be found here: [0]. We have 18 items of 58 that we are tracking that are at risk or unlikely to make the Stein release. Next week's meeting will start at 6:30 PST (9:30) EST to allow the Test team to have the first 30 minutes of our usual time slot. Brucej [0] https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing -------------- next part -------------- An HTML attachment was scrubbed... URL: From cristopher.j.lemus.contreras at intel.com Tue Feb 5 18:45:56 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Tue, 5 Feb 2019 18:45:56 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status Message-ID: <27B234A6-A098-4034-9108-2BD1D25AC819@intel.com> Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: * Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) * With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. * During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): * 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" * Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Tue Feb 5 19:09:28 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 5 Feb 2019 19:09:28 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status In-Reply-To: <27B234A6-A098-4034-9108-2BD1D25AC819@intel.com> References: <27B234A6-A098-4034-9108-2BD1D25AC819@intel.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3BCF12@ALA-MBD.corp.ad.wrs.com> Hi Cristopher, I don’t believe the commit you reference is ready to merge, it is currently at -1 It also will not address the application images as you noted below. This is Mingyuan’s story, not sure if someone else was lined up to work on this during CNY. Brent From: Lemus Contreras, Cristopher J [mailto:cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, February 5, 2019 1:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Deployment status Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: - Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) - With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. - During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): o 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" - Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Feb 5 19:42:58 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 5 Feb 2019 20:42:58 +0100 Subject: [Starlingx-discuss] Community Planning call reminder Message-ID: Hi, This is a friendly reminder that we’re having the next community planning call __tomorrow (February 6) at 8am PT / 1600 UTC__. We will discuss topics such as outreach and onboarding, planning event presence and further items the participants are interested in discussing. You can find the agenda, dial-in info and notes from the previous call on this etherpad: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans Please feel free to add discussion topics to the agenda with your name/IRC nick to know who to ping during the call. Thanks and Best Regards, Ildikó From cristopher.j.lemus.contreras at intel.com Tue Feb 5 20:03:00 2019 From: cristopher.j.lemus.contreras at intel.com (Lemus Contreras, Cristopher J) Date: Tue, 5 Feb 2019 20:03:00 +0000 Subject: [Starlingx-discuss] [Containers] Deployment status In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3BCF12@ALA-MBD.corp.ad.wrs.com> References: <27B234A6-A098-4034-9108-2BD1D25AC819@intel.com> <2588653EBDFFA34B982FAF00F1B4844EBB3BCF12@ALA-MBD.corp.ad.wrs.com> Message-ID: <57658498-F20C-445A-A343-9391718D8C18@intel.com> Hi Brent, We used the commit to verify it, being that the only option that we have for our lab, is to use a local registry. It helped us to check that config_controller completed without errors. So, basically, we are waiting for the story to be completed to unblock us and fully provision our baremetal environments. Thanks & Regards, Cristopher Lemus From: "Rowsell, Brent" Date: Tuesday, February 5, 2019 at 1:10 PM To: "Lemus Contreras, Cristopher J" , "starlingx-discuss at lists.starlingx.io" Subject: RE: [Containers] Deployment status Hi Cristopher, I don’t believe the commit you reference is ready to merge, it is currently at -1 It also will not address the application images as you noted below. This is Mingyuan’s story, not sure if someone else was lined up to work on this during CNY. Brent From: Lemus Contreras, Cristopher J [mailto:cristopher.j.lemus.contreras at intel.com] Sent: Tuesday, February 5, 2019 1:46 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Deployment status Hi All, ** Baremetal Environment ** Simplex configuration on BareMetal servers without internet access. SUMMARY: * Worked with Erich and Mingyuan to apply the patch for config_controller (storyboard: https://storyboard.openstack.org/#!/story/2004711) * With these patches, we can define a mirror registry during the `config_controller --kubernetes` . Using the new option, config_controller completed without any issues, pulling the required images from our internal registry. * During system-application apply, there are errors related to images still trying to be downloaded from public registry (overriding private registries definitions): * 2019-02-01T17:51:57.394 controller-0 dockerd[2325]: info time="2019-02-01T17:51:57.394492462Z" level=info msg="Attempting next endpoint for pull after error: Get https://quay.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" * Mingyuan mentioned that another patch is in progress for application-apply. Is somebody going to work on it during CNY? Regards, Cristopher Lemus -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Tue Feb 5 20:14:41 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 5 Feb 2019 15:14:41 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! Message-ID: <893714213.371.1549397683021.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 44 Status: Failure Timestamp: 20190205T190936Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190205T164241Z OS: centos MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root BASE_VERSION: f-stein-20190205T164241Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: f-stein PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs PUBLISH_TIMESTAMP: 20190205T164241Z FLOCK_VERSION: f-stein-centos-master-20190205T164241Z PREFIX: f-stein OPENSTACK_RELEASE: master TIMESTAMP: 20190205T164241Z REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Tue Feb 5 20:14:49 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 5 Feb 2019 15:14:49 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_images - Build # 41 - Failure! Message-ID: <772143831.374.1549397690491.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 41 Status: Failure Timestamp: 20190205T190637Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/stein MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190205T164241Z OS: centos MUNGED_BRANCH: f-stein MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein PUBLISH_DISTRO_BASE: /export/mirror/starlingx/feature/stein/centos PUBLISH_TIMESTAMP: 20190205T164241Z DOCKER_BUILD_ID: jenkins-f-stein-20190205T164241Z-builder OPENSTACK_RELEASE: master TIMESTAMP: 20190205T164241Z OS_VERSION: 7.5.1804 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/outputs From build.starlingx at gmail.com Tue Feb 5 20:14:53 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 5 Feb 2019 15:14:53 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_stein_master - Build # 42 - Failure! Message-ID: <590783122.377.1549397694960.JavaMail.javamailuser@localhost> Project: STX_build_stein_master Build #: 42 Status: Failure Timestamp: 20190205T164241Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From jose.perez.carranza at intel.com Tue Feb 5 20:48:23 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 5 Feb 2019 20:48:23 +0000 Subject: [Starlingx-discuss] [Containers]Problems setting proxy via config_file Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A937350@fmsmsx101.amr.corp.intel.com> Hi I'm doing a configuring a controller using a configuration file `sudo config_controller --kubernetes --confi-file my-file.ini`. I modified my configuration file to add my proxies but this is causing errors [1], seems like when parsing the configuration file the NO_PROXY variable is set as python list format and hence not recognized by http library. 1. http://paste.openstack.org/show/744593/ Do you if there is a special way to assign multiple values to a variable on configuration file? Below is the example of my configuration file settings: ======================================================= [DOCKER_PROXY] DOCKER_HTTP_PROXY = http://:PORT DOCKER_HTTPS_PROXY = http://:PORT DOCKER_NO_PROXY = localhost,127.0.0.1,192.168.204.2,192.168.204.3,192.168.204.4,10.10.10.3 ======================================================== Regards, José From Barton.Wensley at windriver.com Tue Feb 5 21:38:28 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 5 Feb 2019 21:38:28 +0000 Subject: [Starlingx-discuss] [Containers]Problems setting proxy via config_file In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A937350@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A937350@fmsmsx101.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA61F64@ALA-MBD.corp.ad.wrs.com> José, You have uncovered a bug in the configuration file processing for the DOCKER_PROXY section. This was introduced in the original commit for the docker proxy: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=3a30da9a88920fef4d6b185708bd5013bb8dd95c Please raise a bug for this. For now, your only option is to run config_controller interactively (without the config file). Bart -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: February 5, 2019 3:48 PM To: starlingx-discuss at lists.starlingx.io Cc: Miller, Frank; Wensley, Barton Subject: [Containers]Problems setting proxy via config_file Hi I'm doing a configuring a controller using a configuration file `sudo config_controller --kubernetes --confi-file my-file.ini`. I modified my configuration file to add my proxies but this is causing errors [1], seems like when parsing the configuration file the NO_PROXY variable is set as python list format and hence not recognized by http library. 1. http://paste.openstack.org/show/744593/ Do you if there is a special way to assign multiple values to a variable on configuration file? Below is the example of my configuration file settings: ======================================================= [DOCKER_PROXY] DOCKER_HTTP_PROXY = http://:PORT DOCKER_HTTPS_PROXY = http://:PORT DOCKER_NO_PROXY = localhost,127.0.0.1,192.168.204.2,192.168.204.3,192.168.204.4,10.10.10.3 ======================================================== Regards, José From scott.little at windriver.com Tue Feb 5 21:36:43 2019 From: scott.little at windriver.com (Scott Little) Date: Tue, 5 Feb 2019 16:36:43 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! In-Reply-To: <893714213.371.1549397683021.JavaMail.javamailuser@localhost> References: <893714213.371.1549397683021.JavaMail.javamailuser@localhost> Message-ID: <22364911-94cb-9c8c-b876-f63b6768cbd3@windriver.com> Need designer input. The build failed on the flock image "stx-cinder" No matching distribution found for google-api-python-client===1.7.8 (from -c /tmp/wheels/upper-constraints.txt (line 238)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-cinder... Aborting Full log is here ... http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/latest_build/logs/jenkins-STX_build_docker_flock_images-44.log Scott On 2019-02-05 3:14 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_docker_flock_images > Build #: 44 > Status: Failure > Timestamp: 20190205T190936Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs > -------------------------------------------------------------------------------- > Parameters > > HOST_PORT: 80 > MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190205T164241Z > OS: centos > MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root > BASE_VERSION: f-stein-20190205T164241Z > PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs > REGISTRY_USERID: slittlewrs > HOST: build.starlingx.cengn.ca > LATEST_PREFIX: f-stein > PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs > PUBLISH_TIMESTAMP: 20190205T164241Z > FLOCK_VERSION: f-stein-centos-master-20190205T164241Z > PREFIX: f-stein > OPENSTACK_RELEASE: master > TIMESTAMP: 20190205T164241Z > REGISTRY_ORG: starlingx > PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/outputs > REGISTRY: docker.io > > _______________________________________________ > 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 Al.Bailey at windriver.com Tue Feb 5 21:47:46 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 5 Feb 2019 21:47:46 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! In-Reply-To: <22364911-94cb-9c8c-b876-f63b6768cbd3@windriver.com> References: <893714213.371.1549397683021.JavaMail.javamailuser@localhost> <22364911-94cb-9c8c-b876-f63b6768cbd3@windriver.com> Message-ID: The 1.7.8 wheel on pypi is python3 only, even though the project is declared python2 and python3. Previous version was built as py2-py3 I don't know what the best way to fix this is. Al From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, February 05, 2019 4:37 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! Need designer input. The build failed on the flock image "stx-cinder" No matching distribution found for google-api-python-client===1.7.8 (from -c /tmp/wheels/upper-constraints.txt (line 238)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-cinder... Aborting Full log is here ... http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/latest_build/logs/jenkins-STX_build_docker_flock_images-44.log Scott On 2019-02-05 3:14 p.m., build.starlingx at gmail.com wrote: Project: STX_build_docker_flock_images Build #: 44 Status: Failure Timestamp: 20190205T190936Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190205T164241Z OS: centos MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root BASE_VERSION: f-stein-20190205T164241Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: f-stein PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs PUBLISH_TIMESTAMP: 20190205T164241Z FLOCK_VERSION: f-stein-centos-master-20190205T164241Z PREFIX: f-stein OPENSTACK_RELEASE: master TIMESTAMP: 20190205T164241Z REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/outputs REGISTRY: docker.io _______________________________________________ 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 jose.perez.carranza at intel.com Tue Feb 5 22:24:54 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 5 Feb 2019 22:24:54 +0000 Subject: [Starlingx-discuss] [Containers]Problems setting proxy via config_file In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA61F64@ALA-MBD.corp.ad.wrs.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A937350@fmsmsx101.amr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA61F64@ALA-MBD.corp.ad.wrs.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A9373DA@fmsmsx101.amr.corp.intel.com> Done https://bugs.launchpad.net/starlingx/+bug/1814833 Regards, José > -----Original Message----- > From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] > Sent: Tuesday, February 5, 2019 3:38 PM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io > Cc: Miller, Frank > Subject: RE: [Containers]Problems setting proxy via config_file > > José, > > You have uncovered a bug in the configuration file processing for the > DOCKER_PROXY section. This was introduced in the original commit for the > docker proxy: > https://git.openstack.org/cgit/openstack/stx- > config/commit/?id=3a30da9a88920fef4d6b185708bd5013bb8dd95c > > Please raise a bug for this. For now, your only option is to run config_controller > interactively (without the config file). > > Bart > > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: February 5, 2019 3:48 PM > To: starlingx-discuss at lists.starlingx.io > Cc: Miller, Frank; Wensley, Barton > Subject: [Containers]Problems setting proxy via config_file > > Hi > > I'm doing a configuring a controller using a configuration file `sudo > config_controller --kubernetes --confi-file my-file.ini`. I modified my > configuration file to add my proxies but this is causing errors [1], seems like > when parsing the configuration file the NO_PROXY variable is set as python list > format and hence not recognized by http library. > > 1. http://paste.openstack.org/show/744593/ > > Do you if there is a special way to assign multiple values to a variable on > configuration file? > > Below is the example of my configuration file settings: > > ======================================================= > [DOCKER_PROXY] > DOCKER_HTTP_PROXY = http://:PORT > DOCKER_HTTPS_PROXY = http://:PORT > DOCKER_NO_PROXY = > localhost,127.0.0.1,192.168.204.2,192.168.204.3,192.168.204.4,10.10.10.3 > ======================================================== > > Regards, > José From Al.Bailey at windriver.com Tue Feb 5 22:39:33 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 5 Feb 2019 22:39:33 +0000 Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! In-Reply-To: References: <893714213.371.1549397683021.JavaMail.javamailuser@localhost> <22364911-94cb-9c8c-b876-f63b6768cbd3@windriver.com> Message-ID: Note: This only affects containers and only affects the stein branch. Bug report: https://bugs.launchpad.net/starlingx/+bug/1814835 Code Review: https://review.openstack.org/#/c/635065/ Al From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Tuesday, February 05, 2019 4:48 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! The 1.7.8 wheel on pypi is python3 only, even though the project is declared python2 and python3. Previous version was built as py2-py3 I don't know what the best way to fix this is. Al From: Scott Little [mailto:scott.little at windriver.com] Sent: Tuesday, February 05, 2019 4:37 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 44 - Failure! Need designer input. The build failed on the flock image "stx-cinder" No matching distribution found for google-api-python-client===1.7.8 (from -c /tmp/wheels/upper-constraints.txt (line 238)) The command '/bin/sh -c /opt/loci/scripts/install.sh' returned a non-zero code: 1 Failed to build stx-cinder... Aborting Full log is here ... http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/latest_build/logs/jenkins-STX_build_docker_flock_images-44.log Scott On 2019-02-05 3:14 p.m., build.starlingx at gmail.com wrote: Project: STX_build_docker_flock_images Build #: 44 Status: Failure Timestamp: 20190205T190936Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190205T164241Z OS: centos MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root BASE_VERSION: f-stein-20190205T164241Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: f-stein PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/logs PUBLISH_TIMESTAMP: 20190205T164241Z FLOCK_VERSION: f-stein-centos-master-20190205T164241Z PREFIX: f-stein OPENSTACK_RELEASE: master TIMESTAMP: 20190205T164241Z REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190205T164241Z/outputs REGISTRY: docker.io _______________________________________________ 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 ada.cabrales at intel.com Tue Feb 5 23:05:22 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 5 Feb 2019 23:05:22 +0000 Subject: [Starlingx-discuss] [ Test ] meeting agenda - 02/06/2019 - 6am PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD67914@FMSMSX114.amr.corp.intel.com> Agenda for 02/06 meeting - please remember the meeting will take place at 6am PDT. 1. Test plan for May release - Ghada/Ada - 15 min 2. Stories for upstream OpenStack testing - Bruce - 15 min 3. Test repo structure and reviewers - Jose/Cristopher - 15 min 4. Opens - all - 15 min Regards Ada From abraham.arce.moreno at intel.com Wed Feb 6 00:01:46 2019 From: abraham.arce.moreno at intel.com (Arce Moreno, Abraham) Date: Wed, 6 Feb 2019 00:01:46 +0000 Subject: [Starlingx-discuss] Contribution to the project. In-Reply-To: References: <9A85D2917C58154C960D95352B22818BBFD18EB2@fmsmsx123.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BBFD18F0D@fmsmsx123.amr.corp.intel.com> Message-ID: > Hi Abraham, Hi again Javier ☺ welcome to Documentation team! > Thanks for your attentiion and I can help on the documentation team if you > need help there. Here you have our Documentation Tree roadmap [0], please feel free to take a look. Based in the resources you have available and the priority of tasks, my suggestion for your short term and medium term tasks would be: 1. Go through " Developer’s Guide" to get your workstation setup [1] 2. Feedback new "Installation Guides" [Short Term] 1.1 See section "Installing and Configuring StarlingX with Containers" under [2] 3. SWIFT Configuration & Management [Medium Term] 3.1 Once you have exercised the installation and configuration, it is time to generate your first introductory guide for SWIFT, taking advantage of your experience. "Two" is being actively review now by our community and it will be translated from the Wiki format to the RST format to land under stx-docs [3] Please let this list know about improvements, findings, whatever you consider important, you will learn how to deploy StarlingX. When we have that new RST format, we will add you as reviewer (with Ubuntu Account obtained at [1]). "Three" We can have more details once you feel comfortable with tasks "one" and "two" on what the community is looking for, anyway, please take into consideration this is a great opportunity for you exercise the complete development cycle, from creating a first draft of a guide, through submitting your first patchset and finally, seeing it approved :) > Have a good day! You too! [0] https://docs.google.com/spreadsheets/d/1kvXEZl4XwNgHTYXPIcoZfKE4LBNcif4sBJdZCNSvBGw/edit?usp=sharing [1] https://docs.openstack.org/infra/manual/developers.html [2] https://wiki.openstack.org/wiki/StarlingX/Containers [3] https://git.openstack.org/cgit/openstack/stx-docs From cindy.xie at intel.com Wed Feb 6 01:11:12 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 6 Feb 2019 01:11:12 +0000 Subject: [Starlingx-discuss] [Containers]Problems setting proxy via config_file In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A9373DA@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A937350@fmsmsx101.amr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA61F64@ALA-MBD.corp.ad.wrs.com> <0A5D9A624DF90343892F8F3FE7DE525A2A9373DA@fmsmsx101.amr.corp.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E79845@SHSMSX104.ccr.corp.intel.com> Thanks - I've assigned this bug to Mingyuan in the LP. -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: Wednesday, February 6, 2019 6:25 AM To: Wensley, Barton ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers]Problems setting proxy via config_file Done https://bugs.launchpad.net/starlingx/+bug/1814833 Regards, José > -----Original Message----- > From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] > Sent: Tuesday, February 5, 2019 3:38 PM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io > Cc: Miller, Frank > Subject: RE: [Containers]Problems setting proxy via config_file > > José, > > You have uncovered a bug in the configuration file processing for the > DOCKER_PROXY section. This was introduced in the original commit for > the docker proxy: > https://git.openstack.org/cgit/openstack/stx- > config/commit/?id=3a30da9a88920fef4d6b185708bd5013bb8dd95c > > Please raise a bug for this. For now, your only option is to run > config_controller interactively (without the config file). > > Bart > > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: February 5, 2019 3:48 PM > To: starlingx-discuss at lists.starlingx.io > Cc: Miller, Frank; Wensley, Barton > Subject: [Containers]Problems setting proxy via config_file > > Hi > > I'm doing a configuring a controller using a configuration file `sudo > config_controller --kubernetes --confi-file my-file.ini`. I modified > my configuration file to add my proxies but this is causing errors > [1], seems like when parsing the configuration file the NO_PROXY > variable is set as python list format and hence not recognized by http library. > > 1. http://paste.openstack.org/show/744593/ > > Do you if there is a special way to assign multiple values to a > variable on configuration file? > > Below is the example of my configuration file settings: > > ======================================================= > [DOCKER_PROXY] > DOCKER_HTTP_PROXY = http://:PORT > DOCKER_HTTPS_PROXY = http://:PORT > DOCKER_NO_PROXY = > localhost,127.0.0.1,192.168.204.2,192.168.204.3,192.168.204.4,10.10.10 > .3 ======================================================== > > Regards, > José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From serverascode at gmail.com Wed Feb 6 12:59:20 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 6 Feb 2019 07:59:20 -0500 Subject: [Starlingx-discuss] Vagrant StarlingX VM. In-Reply-To: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> References: <970a6b61-79eb-46ec-9364-b297f18f5c84@intel.com> Message-ID: On Sat, Feb 2, 2019 at 12:44 PM Lara, Cesar wrote: > Yes we are exploring a few possibilities for StarlingX in a bottle, > vagrant in one of them. Feel free to throw some ideas at it > > I've not been doing a good job following the "in a bottle" work...in which project/meeting are these possibilities being discussed? I think the "in a bottle", ie. environments that can quickly be created for evaluation and development, are quite important, and also relate to zero touch provisioning. Thanks, Curtis > Regards > Cesar Lara > Sent from my mobile phone > ------------------------------ > *From:* Javier Romero > *Sent:* Saturday, February 2, 2019 11:07 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] Vagrant StarlingX VM. > > Hi Team, > > Think that perhaps may be useful for new users to have a Vagrant > preconfigured AIO VM to use StarlingX for the fiirst time. > > https://www.vagrantup.com > > If this can be useful I can help with that. > > Vagrant use VirtualBox by default to star the preconfigured VM and can > also be set to be used with QEMU. > > Best Regards, > > > > > > -- > *Javier Romero* > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Wed Feb 6 15:28:24 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 6 Feb 2019 09:28:24 -0600 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: <6E7E2668-C4A0-4290-A79F-499F8E4F94C8@windriver.com> References: <3BD8A4F0-7C15-407E-9671-7E3C666F03E1@windriver.com> <6E7E2668-C4A0-4290-A79F-499F8E4F94C8@windriver.com> Message-ID: On Mon, Feb 4, 2019 at 4:24 PM Young, Ken wrote: > > See inline. > > On 2019-02-04, 2:26 PM, "Victor Rodriguez" wrote: > > On Mon, Feb 4, 2019 at 12:49 PM Young, Ken wrote: > > > > Team, > > > > > > > > A “Lights On” feature for the 2019.05 release is “CVE Upgrades”. This feature will enable ongoing security updates for the master branch and selectively provide CVE corrective content to supported releases. The first step for this feature is to define a policy. With the help of the Starling X security team, a draft of this policy has been provided below: > > > > > > > > https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy > > > > > > > > Please review and provide comments. I plan to reserve a spot on the Community call for any discussion on Wednesday and start the discussion with the build team to identify tools to support this policy on Thursday. > > > Question on the last slide you propose a formula as > > Criticality >= 7 > > What standard are you plan to use? CVSS v3.0 or v2.0 > > I am suggesting we start with v2. I need to look into v3 a little more. > > For example, taking this MariaDB > > https://nvd.nist.gov/vuln/detail/CVE-2017-15365 > > Base Score: 8.8 HIGH in V3 and 6.5 MEDIUM in V2 > > My recommendation will be to use the highest one despite if the score > came from V2 or V3 > > However, I think we should specify that somewhere > > Agreed. > > One more question, when you said critical issues are fixed if > corrections are available upstream it means that ( taking the previous > example ) if MariaDB provides a Patch, is merged in master and > released in the latest release, like in the previous example : > https://github.com/MariaDB/server/commit/0b5a5258abbeaf8a0c3a18c7e753699787fdf46e > > But CentOS has not taken it yet, are we OK to apply this patch in STX > until CentOS apply in incoming future? > > We will wait for CentOS. We are in the process of patch elimination. I do not to carry more. > Hi Ken This is the link to the tool that we could use to catch the CVEs https://github.com/clearlinux/cve-check-tool Hoep it helps as an starting point Regards Victor > Regards > > Victor R > > > > > > Regards, > > > > Ken Y > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From ada.cabrales at intel.com Wed Feb 6 17:18:56 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 6 Feb 2019 17:18:56 +0000 Subject: [Starlingx-discuss] [ Test ] meeting minutes - 02/06/2019 - 6am PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD67E38@FMSMSX114.amr.corp.intel.com> Agenda for 02/06/2019 Attendees: Elio, Cristopher, Jose, Victor, JP, Numan, Bruce, Javier, Fernando, Richo, Javier, Ada 1. Test plan for May release - Ghada/Ada - 15 min + https://docs.google.com/spreadsheets/d/1FwPTFKFFoNwWAsgbdw0kH_Bwv5JiutTWu_9UU4OAQbw/edit#gid=0 + resource planning to be finished by 02/08 2. Stories for upstream OpenStack testing - Bruce - 15 min + Test plan and test cases for HPET timer feature - https://storyboard.openstack.org/#!/story/2004736 + Implement test plan and test cases for SR-IOV scheduling policy change https://storyboard.openstack.org/#!/story/2004888 + Test cases for the updated vswitch affinity feature - https://storyboard.openstack.org/#!/story/2004889 + test cases for the changed Nova DB purge feature - https://storyboard.openstack.org/#!/story/2004890 + Ada to assign the stories Verify if there are test cases that can be used. 3. Test repo structure and reviewers - Jose/Cristopher - 15 min + To align with OpenStack model, the repo should also contain a "docs" and "releasenotes" directories. + Abraham to train the team on the way of submitting things to the releasenotes and docs. To be delivered next week. + "manual suite" directory should match the automated suite tree. + For documentation: consider the scenario of running only one test cases, several, or all the suite. + Cristopher to create the structure. + Also add Abraham for documentation reviews. + Reviewers: an UbuntuOne account is required. + The group of reviewers: - Numan Waheed - Chris Winnicki - Maria Yousaf - Nimalini Rasa - Wendy Mitchell - Yang Liu - Yosief Gebremariam - Jose Perez - Elio Martinez - JC Alonso + There might be other files related to OpenStack CI. + Structure to be set today. Reviewers to check and approve. + Have everything ready for testing submissions next week. + Link to the test case template: https://wiki.openstack.org/wiki/StarlingX/TestCaseDocument 4. Opens - all - 15 min + Test dashboard - are we going to make this a priority? Ada says that is really good to have it for May release. Ada to check Cristopher's bandwidth. Cristopher to send requirements to Ken, Numan and Ada (02/06) to ask CENGN. Suggestion: download and try it locally. From juan.carlos.alonso at intel.com Wed Feb 6 17:20:07 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 6 Feb 2019 17:20:07 +0000 Subject: [Starlingx-discuss] New docker0 interface enabled? Message-ID: <8557B550001AFB46A43A0CCC314BF85153C8F533@FMSMSX108.amr.corp.intel.com> Hi, For today's ISO, in Simplex and Duplex configurations, we noticed a new interface called 'docker0', our framework takes the first interface and set a temporary ip address, but this 'docker0' interface could not be set, then STX setup fails. We applied a workaround to take the next interface to continue the STX tests. We also noticed that this 'docker0' interface is not present in Multinode configurations. localhost:~$ ls /sys/class/net docker0 enp2s1 enp2s2 eth1000 eth1001 lo Is this new interface enabled for configuration with kubernetes? Will this interface be enabled in Multinode configurations? Why docker0 interface cannot be set with an ip address? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From xavinux at gmail.com Wed Feb 6 17:44:36 2019 From: xavinux at gmail.com (Javier Romero) Date: Wed, 6 Feb 2019 14:44:36 -0300 Subject: [Starlingx-discuss] New docker0 interface enabled? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C8F533@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C8F533@FMSMSX108.amr.corp.intel.com> Message-ID: Hi Juan Carlos, After a Docker installationis finished, the Bridge interface *docker0* is created by default and it's IP range is 172.17.0.0/16. But you can create another network interfaces running *docker network create new_network_name * If you want to change the *docker0 * settings, you can use the daemon.json file in /etc/docker/ If the file is not their you can create it and specify some parameters like the following for the bridge network: { "bip": "10.10.10.5/24", "fixed-cidr": "10.10.10.5/25", "fixed-cidr-v6": "2001:db8::/64", "mtu": 1500, "default-gateway": "10.20.1.1", "default-gateway-v6": "2001:db8:abcd::89", "dns": ["10.20.1.2","10.20.1.3"] } Then restart Docker. Hope this can help you. Best Regards, *Javier Romero* El mié., 6 feb. 2019 a las 14:21, Alonso, Juan Carlos (< juan.carlos.alonso at intel.com>) escribió: > Hi, > > > > For today’s ISO, in Simplex and Duplex configurations, we noticed a new > interface called ‘docker0’, our framework takes the first interface and set > a temporary ip address, but this ‘docker0’ interface could not be set, then > STX setup fails. > > We applied a workaround to take the next interface to continue the STX > tests. > > We also noticed that this ‘docker0’ interface is not present in Multinode > configurations. > > > > localhost:~$ ls /sys/class/net > > *docker0* enp2s1 enp2s2 eth1000 eth1001 lo > > > > Is this new interface enabled for configuration with kubernetes? Will this > interface be enabled in Multinode configurations? > > Why docker0 interface cannot be set with an ip address? > > > > 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 David.Sullivan at windriver.com Wed Feb 6 18:07:45 2019 From: David.Sullivan at windriver.com (Sullivan, David) Date: Wed, 6 Feb 2019 18:07:45 +0000 Subject: [Starlingx-discuss] New docker0 interface enabled? In-Reply-To: References: <8557B550001AFB46A43A0CCC314BF85153C8F533@FMSMSX108.amr.corp.intel.com> Message-ID: There was a mistake in my submission https://review.openstack.org/#/c/633433/ The kubelet service is being started on all workers node, which creates the docker interface. This would affect all AIO installations but not standard installations. It will be addressed tonight. For now you should be able to ignore the extra interface. David From: Javier Romero [mailto:xavinux at gmail.com] Sent: Wednesday, February 6, 2019 12:45 PM To: Alonso, Juan Carlos Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] New docker0 interface enabled? Hi Juan Carlos, After a Docker installationis finished, the Bridge interface docker0 is created by default and it's IP range is 172.17.0.0/16. But you can create another network interfaces running docker network create new_network_name If you want to change the docker0 settings, you can use the daemon.json file in /etc/docker/ If the file is not their you can create it and specify some parameters like the following for the bridge network: { "bip": "10.10.10.5/24", "fixed-cidr": "10.10.10.5/25", "fixed-cidr-v6": "2001:db8::/64", "mtu": 1500, "default-gateway": "10.20.1.1", "default-gateway-v6": "2001:db8:abcd::89", "dns": ["10.20.1.2","10.20.1.3"] } Then restart Docker. Hope this can help you. Best Regards, Javier Romero El mié., 6 feb. 2019 a las 14:21, Alonso, Juan Carlos (>) escribió: Hi, For today’s ISO, in Simplex and Duplex configurations, we noticed a new interface called ‘docker0’, our framework takes the first interface and set a temporary ip address, but this ‘docker0’ interface could not be set, then STX setup fails. We applied a workaround to take the next interface to continue the STX tests. We also noticed that this ‘docker0’ interface is not present in Multinode configurations. localhost:~$ ls /sys/class/net docker0 enp2s1 enp2s2 eth1000 eth1001 lo Is this new interface enabled for configuration with kubernetes? Will this interface be enabled in Multinode configurations? Why docker0 interface cannot be set with an ip address? 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 michael.l.tullis at intel.com Wed Feb 6 21:38:07 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 6 Feb 2019 21:38:07 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2/6/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AA4365@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Feb 6 22:01:55 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 6 Feb 2019 22:01:55 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190206 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C8F5E9@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-06 (link) Sanity Test is executed in a Bare Metal Environment Status: YELLOW Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: YELLOW Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 22 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ A new interface called 'docker0' was enabled and present in Simplex and Duplex configurations. Issue will be addressed. Launchpad open: https://bugs.launchpad.net/starlingx/+bug/1814946 Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Wed Feb 6 22:20:57 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Wed, 6 Feb 2019 22:20:57 +0000 Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on Duplex installation Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A9386E5@fmsmsx101.amr.corp.intel.com> Hi, I'm installing a Duplex with containers and I'm getting below error when unlocking controller-1 ======== | task | Configuration Failed, re-enabling | | task | Rebooting | | task | Booting | ... ... ... | 200.011 | controller-1 experienced a configuration failure. | host=controller-1 | critical | 2019-02-06T13:44:19 | controller ======== then controller tries to boot again until but below failure appears and the controller satays on failure status. =================== | task | Configuration failure, threshold reached, Lock/Unlock to retry | ====================== If I made a lock/unlock cycle I get with the same issues. I was searching on the puppet.log of controller-1 and I found below errors, seems like the repository is not reachable, my question is if I used a proxy on the config_controller those proxies are also propagated to controller-1 when is automatically installed? ==================== 2019-02-06T13:52:15.219 Notice: 2019-02-06 13:52:15 +0000 /Stage[main]/Platform::Helm/Exec[initialize helm]/returns: Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes-charts.storage.googleapis.com on 8.8.4.4:53: read udp 10.10.10.4:52260->8.8.4.4:53: i/o timeout ======================= I created a Launchpad to track down this behavior https://bugs.launchpad.net/starlingx/+bug/1814968 Regards, José From xiongzhiwei at baicells.com Sat Feb 2 07:33:38 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Sat, 2 Feb 2019 15:33:38 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server References: Message-ID: <20190202153337711807156@baicells.com> Hi Yong, puppet.log attached. Thanks From: Hu, Yong Date: 2019-02-02 15:10 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Pls share us your /var/log/puppet/latest/puppet.log. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 3:07 PM To: "xiongzhiwei at baicells.com" , "Hu, Yong" , "Xie, Cindy" , starlingx-discuss Subject: Re: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Yong and Cindy, The same error appeared after removed these two sata disks. Thanks Tim From: xiongzhiwei at baicells.com Date: 2019-02-02 14:34 To: Hu, Yong; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Thanks Hu Yong and Cindy, I am trying to again after remove these two SATA HD. Will tell you once successed. Regards Tim From: Hu, Yong Date: 2019-02-02 14:27 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: puppet.rar Type: application/octet-stream Size: 142597 bytes Desc: not available URL: From ada.cabrales at intel.com Tue Feb 5 15:39:44 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 5 Feb 2019 15:39:44 +0000 Subject: [Starlingx-discuss] StarlingX Test meeting - 6:00 PDT Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD66FE4@FMSMSX114.amr.corp.intel.com> Re-scheduling for this week only - Wed 02/06 6am PDT Same zoom info -- Ada Changing the frequency to weekly. Weekly meetings on Tuesdays at 9am PDT / 1600 UTC * 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: 4778 bytes Desc: not available URL: From bruce.e.jones at intel.com Wed Feb 6 17:24:12 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 6 Feb 2019 17:24:12 +0000 Subject: [Starlingx-discuss] Community call notes Feb 6 2019 Message-ID: <9A85D2917C58154C960D95352B22818BBFD1C8CF@fmsmsx123.amr.corp.intel.com> Agenda and notes - Feb 6th call * CVE Support Policy - Ken * https://wiki.openstack.org/wiki/StarlingX/Security/CVE_Support_Policy * Upcoming container and openstack master cutover - Brent * Reminder to the community that the container/stein branch will merge to master next week - valentines day is the target * Release gating bug updates - Bruce / Ghada * stx.209.05 Release Gating Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2019.05 * Action: Project leads to review their bugs and drive resolution. ? Also to close any that are no longer valid due to the move to containers * Action: Ask BillZ can share the launchpad trend charts weekly in the community call * Process * Story Board Template * Community agreed to go with a simple template to set * Proposed Story Template: ? Brief Description: ? Justification: * Abandoning stale gerrit reviews -- need to agree on a policy ? Dean notes that there is no consistent best practice in the community. It depends on the community. Some do it per cycle due to time investment. ? Agreed to go with once per cycle -- core reviewers to abandon based on 3-6months inactivity. * Note: Abandoned reviews can be reversed and restarted again. It's not irreversible. * Release Plan Update * https://docs.google.com/spreadsheets/d/1HUwbsaSerzFRuvXVB_qvoGdI0Chx1YiiA2WYHwvIoYI/edit#gid=405844719 * Release Verification Plan: * https://docs.google.com/spreadsheets/d/1FwPTFKFFoNwWAsgbdw0kH_Bwv5JiutTWu_9UU4OAQbw/edit#gid=0 * Ada/Numan expect to have the resourcing plan in place by Feb 8 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Feb 6 18:17:53 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 6 Feb 2019 19:17:53 +0100 Subject: [Starlingx-discuss] [all] Denver Open Infrastructure Summit Community Contributor Awards! Message-ID: Hello Everyone! As we approach the Summit (still a ways away thankfully), its time to kick off the Community Contributor Award nominations[1]! For those of you that have never heard of the CCA, I'll briefly explain what they are :) We all know people in our communities that do the dirty jobs, we all know people that will bend over backwards trying to help someone new, we all know someone that is a savant in some area of the code we could never hope to understand. These people rarely get the thanks they deserve and the Community Contributor Awards are a chance to make sure they know that they are appreciated for the amazing work they do and skills they have. As always, participation is voluntary :) Nominations will close on April 14th at 7:00 UTC and recipients will be announced at the Open Infrastructure Summit in Denver[2]. Recipients will be selected by a panel of top-level OSF project representatives who wish to participate. Finally, congrats again to recipients in Berlin[3]! -Kendall Nelson (diablo_rojo) [1] https://openstackfoundation.formstack.com/forms/train_cca_nominations [2]https://www.openstack.org/summit/denver-2019/ [3] http://superuser.openstack.org/articles/openstack-community-contributor-awards-berlin-summit-edition/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From himanshugoyal500 at gmail.com Thu Feb 7 07:32:11 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Thu, 7 Feb 2019 13:02:11 +0530 Subject: [Starlingx-discuss] RT Patch on StarlingX Server Message-ID: Hi, Please let us know is there any available version of RT Patch that we can apply on starlingX compute host server. Regards Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Feb 7 07:50:16 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 7 Feb 2019 02:50:16 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 137 - Failure! Message-ID: <335340080.383.1549525818260.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 137 Status: Failure Timestamp: 20190207T062103Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190207T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190207T060000Z DOCKER_BUILD_ID: jenkins-master-20190207T060000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190207T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190207T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Thu Feb 7 07:50:21 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 7 Feb 2019 02:50:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 130 - Failure! Message-ID: <302024602.386.1549525822575.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 130 Status: Failure Timestamp: 20190207T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190207T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From serverascode at gmail.com Thu Feb 7 13:04:07 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 7 Feb 2019 08:04:07 -0500 Subject: [Starlingx-discuss] ONAP OOM similarities Message-ID: Hi All, Like many of us, I'm on a few open source lists. One of those lists is for the ONAP project. From a high level, I see some similarities with their OOM (ONAP Operations Manager) project and some of the things StarlingX does. Might be worthwhile having a look at what they are doing and thinking about there. (Not to say what they have decided on is right for everyone, or StarlingX, but considering their thought process and understanding issues they have run into could be valuable.) Perhaps some similar work to multi-os (their CIA project I believe): * Meeting notes: https://wiki.onap.org/display/DW/CIA+Meeting+Notes * Initiating email: https://lists.onap.org/g/onap-discuss/message/11800 Issues with managing container image versions and integration: * https://lists.onap.org/g/onap-discuss/message/15388 * https://lists.onap.org/g/onap-discuss/attachment/15388/0/oom_version_tests.pdf Those are just some examples; likely others as well, multi-CPU images etc. At any rate, something to think about! :) Thanks, Curtis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Thu Feb 7 13:30:20 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 7 Feb 2019 13:30:20 +0000 Subject: [Starlingx-discuss] Reverting commit due to load breakage Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62A97@ALA-MBD.corp.ad.wrs.com> The following commit appears to have broken installations and is being reverted: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=24fd045f6883dc060d6e09b5444080cae5196847 The failure happens during config_controller at step 02: Failed at Step 02 . . . Failed to execute bootstrap manifest. The following error is seen in /var/log/puppet/latest/puppet.log: 2019-02-07T00:03:07.915 Debug: 2019-02-07 00:03:06 +0000 Executing: '/usr/bin/openstack complete' 2019-02-07T00:03:08.827 Debug: 2019-02-07 00:03:08 +0000 importing '/usr/share/puppet/modules/platform/manifests/sysinv.pp' in environment production 2019-02-07T00:03:08.849 Debug: 2019-02-07 00:03:08 +0000 Automatically imported platform::sysinv::bootstrap from platform/sysinv into production 2019-02-07T00:03:08.851 Error: 2019-02-07 00:03:08 +0000 Evaluation Error: Error while evaluating a Function Call, Could not find class ::sysinv::db::postgresql for localhost at /usr/share/puppet/modules/platform/manifests/sysinv.pp:160:3 on node localhost Due to the build failure last night, this commit does not yet appear in a public build. Bart Wensley, Member of Technical Staff, Wind River direct 613.963.1385 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Feb 7 13:37:45 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 7 Feb 2019 14:37:45 +0100 Subject: [Starlingx-discuss] Community Planning Call update Message-ID: Hi, We’ve had a great call yesterday where we discussed goals for the year in the area of outreach and contributor onboarding and discussed plans onwards. We’ve touched on already ongoing activities such as documentation work, hands-on workshop for the Open Infrastructure Summit in Denver, Packet PoC, collaboration with the Edge WG on use cases and content for the StarlingX blog. You can find pointers of the above and further notes from the meeting on this etherpad: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans We are looking for contributors to the StarlingX blog. If you have stories to share, like introducing a feature or driving attention to an ongoing design and implementation work please sign up on the above etherpad or reach out to me. We agreed on a bi-weekly cadence so I created an invite that runs the call series until the Summit in Denver. Please let me know if you have any questions. Thanks, Ildikó -------------- next part -------------- A non-text attachment was scrubbed... Name: STX Community Planning Call.ics Type: text/calendar Size: 1781 bytes Desc: not available URL: -------------- next part -------------- From scott.little at windriver.com Thu Feb 7 15:20:26 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 7 Feb 2019 10:20:26 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 130 - Failure! In-Reply-To: <302024602.386.1549525822575.JavaMail.javamailuser@localhost> References: <302024602.386.1549525822575.JavaMail.javamailuser@localhost> Message-ID: <635b43d9-19c0-eb26-ae8e-d6c3f43d30db@windriver.com> Ran out of disk space. The old build cleaner is running now to clean up older loads (retention policy is 2 weeks unless a specific load has be marked as one to preserve.  The cleanup job will now run daily. I'll also audit disk usage per build. We are clearly using more than was originally estimated. Scott On 2019-02-07 2:50 a.m., build.starlingx at gmail.com wrote: > Project: STX_build_master_pike > Build #: 130 > Status: Failure > Timestamp: 20190207T060000Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190207T060000Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > > _______________________________________________ > 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 cesar.lara at intel.com Thu Feb 7 16:03:49 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 7 Feb 2019 16:03:49 +0000 Subject: [Starlingx-discuss] [build][meeting] Build team meeting Agenda for 2/7/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105D5DE2@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 2/7/2019 - Build system for containers - Improvements for current build system - MultiOS build system - discussion - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Thu Feb 7 17:10:49 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 7 Feb 2019 17:10:49 +0000 Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on Duplex installation In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A9386E5@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9386E5@fmsmsx101.amr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62CF3@ALA-MBD.corp.ad.wrs.com> José, The proxy configuration you supply during config_controller should be propagated to controller-1. If you are sure your controller-1 has connectivity to your proxy, then you will need help from Mingyuan Qi who implemented the proxy support. Bart -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: February 6, 2019 5:21 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on Duplex installation Hi, I'm installing a Duplex with containers and I'm getting below error when unlocking controller-1 ======== | task | Configuration Failed, re-enabling | | task | Rebooting | | task | Booting | ... ... ... | 200.011 | controller-1 experienced a configuration failure. | host=controller-1 | critical | 2019-02-06T13:44:19 | controller ======== then controller tries to boot again until but below failure appears and the controller satays on failure status. =================== | task | Configuration failure, threshold reached, Lock/Unlock to retry | ====================== If I made a lock/unlock cycle I get with the same issues. I was searching on the puppet.log of controller-1 and I found below errors, seems like the repository is not reachable, my question is if I used a proxy on the config_controller those proxies are also propagated to controller-1 when is automatically installed? ==================== 2019-02-06T13:52:15.219 Notice: 2019-02-06 13:52:15 +0000 /Stage[main]/Platform::Helm/Exec[initialize helm]/returns: Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes-charts.storage.googleapis.com on 8.8.4.4:53: read udp 10.10.10.4:52260->8.8.4.4:53: i/o timeout ======================= I created a Launchpad to track down this behavior https://bugs.launchpad.net/starlingx/+bug/1814968 Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Thu Feb 7 17:30:31 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Thu, 7 Feb 2019 17:30:31 +0000 Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on Duplex installation In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62CF3@ALA-MBD.corp.ad.wrs.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9386E5@fmsmsx101.amr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62CF3@ALA-MBD.corp.ad.wrs.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A9389F8@fmsmsx101.amr.corp.intel.com> Thanks Bart Yes, I have connectivity actually the proxies are set correctly on "/etc/systemd/system/docker.service.d/http-proxy.conf" but seems like are not well recognized by controller-1. If I run below commands the URL is reachable. I'll update the Launchpad with this info. $ https_proxy= curl https://kubernetes-charts.storage.googleapis.com $ https_proxy= helm init Regards, José > -----Original Message----- > From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] > Sent: Thursday, February 7, 2019 11:11 AM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] [Containers] Not able to boot controller-1 on > Duplex installation > > José, > > The proxy configuration you supply during config_controller should be > propagated to controller-1. If you are sure your controller-1 has connectivity to > your proxy, then you will need help from Mingyuan Qi who implemented the > proxy support. > > Bart > > -----Original Message----- > From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] > Sent: February 6, 2019 5:21 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on > Duplex installation > > Hi, > > I'm installing a Duplex with containers and I'm getting below error when > unlocking controller-1 ======== > > | task | Configuration Failed, re-enabling | > | task | Rebooting | > | task | Booting | > ... > ... > ... > | 200.011 | controller-1 experienced a configuration failure. | > | host=controller-1 | critical | 2019-02-06T13:44:19 | controller > ======== > > then controller tries to boot again until but below failure appears and the > controller satays on failure status. > =================== > | task | Configuration failure, threshold reached, Lock/Unlock to retry > | | > ====================== > > If I made a lock/unlock cycle I get with the same issues. I was searching on the > puppet.log of controller-1 and I found below errors, seems like the repository > is not reachable, my question is if I used a proxy on the config_controller those > proxies are also propagated to controller-1 when is automatically installed? > > ==================== > 2019-02-06T13:52:15.219 Notice: 2019-02-06 13:52:15 +0000 > /Stage[main]/Platform::Helm/Exec[initialize helm]/returns: Error: Looks like > "https://kubernetes-charts.storage.googleapis.com" is not a valid chart > repository or cannot be reached: Get https://kubernetes- > charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes- > charts.storage.googleapis.com on 8.8.4.4:53: read udp 10.10.10.4:52260- > >8.8.4.4:53: i/o timeout ======================= > > I created a Launchpad to track down this behavior > > https://bugs.launchpad.net/starlingx/+bug/1814968 > > Regards, > José > > > > _______________________________________________ > 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 Thu Feb 7 17:36:40 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 7 Feb 2019 09:36:40 -0800 Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on Duplex installation In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A9389F8@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9386E5@fmsmsx101.amr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62CF3@ALA-MBD.corp.ad.wrs.com> <0A5D9A624DF90343892F8F3FE7DE525A2A9389F8@fmsmsx101.amr.corp.intel.com> Message-ID: Jose, Can you also talk with Memo as he is looking into this while Mingyuan is on break. Sau! On 2/7/19 9:30 AM, Perez Carranza, Jose wrote: > Thanks Bart > > Yes, I have connectivity actually the proxies are set correctly on "/etc/systemd/system/docker.service.d/http-proxy.conf" but seems like are not well recognized by controller-1. > > If I run below commands the URL is reachable. I'll update the Launchpad with this info. > > $ https_proxy= curl https://kubernetes-charts.storage.googleapis.com > $ https_proxy= helm init > > > Regards, > José > > >> -----Original Message----- >> From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] >> Sent: Thursday, February 7, 2019 11:11 AM >> To: Perez Carranza, Jose ; starlingx- >> discuss at lists.starlingx.io >> Subject: RE: [Starlingx-discuss] [Containers] Not able to boot controller-1 on >> Duplex installation >> >> José, >> >> The proxy configuration you supply during config_controller should be >> propagated to controller-1. If you are sure your controller-1 has connectivity to >> your proxy, then you will need help from Mingyuan Qi who implemented the >> proxy support. >> >> Bart >> >> -----Original Message----- >> From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] >> Sent: February 6, 2019 5:21 PM >> To: starlingx-discuss at lists.starlingx.io >> Subject: [Starlingx-discuss] [Containers] Not able to boot controller-1 on >> Duplex installation >> >> Hi, >> >> I'm installing a Duplex with containers and I'm getting below error when >> unlocking controller-1 ======== >> >> | task | Configuration Failed, re-enabling | >> | task | Rebooting | >> | task | Booting | >> ... >> ... >> ... >> | 200.011 | controller-1 experienced a configuration failure. | >> | host=controller-1 | critical | 2019-02-06T13:44:19 | controller >> ======== >> >> then controller tries to boot again until but below failure appears and the >> controller satays on failure status. >> =================== >> | task | Configuration failure, threshold reached, Lock/Unlock to retry >> | | >> ====================== >> >> If I made a lock/unlock cycle I get with the same issues. I was searching on the >> puppet.log of controller-1 and I found below errors, seems like the repository >> is not reachable, my question is if I used a proxy on the config_controller those >> proxies are also propagated to controller-1 when is automatically installed? >> >> ==================== >> 2019-02-06T13:52:15.219 Notice: 2019-02-06 13:52:15 +0000 >> /Stage[main]/Platform::Helm/Exec[initialize helm]/returns: Error: Looks like >> "https://kubernetes-charts.storage.googleapis.com" is not a valid chart >> repository or cannot be reached: Get https://kubernetes- >> charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes- >> charts.storage.googleapis.com on 8.8.4.4:53: read udp 10.10.10.4:52260- >>> 8.8.4.4:53: i/o timeout ======================= >> >> I created a Launchpad to track down this behavior >> >> https://bugs.launchpad.net/starlingx/+bug/1814968 >> >> Regards, >> José >> >> >> >> _______________________________________________ >> 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 Tao.Liu at windriver.com Thu Feb 7 19:43:29 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Thu, 7 Feb 2019 19:43:29 +0000 Subject: [Starlingx-discuss] Host HTTP/HTTPS port number changed Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDB6F3F@ALA-MBD.corp.ad.wrs.com> Hi All, In order to avoid conflicts with containerized services, the default HTTP(80) and HTTPS(443) port numbers have been changed to 8080 and 8443. The platform horizon UI is now available at http://:8080 To configure a different port for http or https using system CLI: system service-parameter-list --service http +--------------------------------------+---------+---------+------------+-------+-------------+----------+ | uuid | service | section | name | value | personality | resource | +--------------------------------------+---------+---------+------------+-------+-------------+----------+ | 4fc7e8f5-4621-4a07-a207-86c40c6b05fa | http | config | http_port | 8080 | None | None | | 96180927-50f6-4f26-af78-f0cb7c1d4b37 | http | config | https_port | 8443 | None | None | +--------------------------------------+---------+---------+------------+-------+-------------+----------+ system service-parameter-modify http config http_port=8090 system service-parameter-modify http config https_port=9443 system service-parameter-apply http Containerized deployment: For custom apps that use a hard-coded location in the manifest file, the URL needs to be updated accordingly. For example: Location: http://172.17.0.1/helm_charts/hello-kitty.tgz Change to Location: http://172.17.0.1:8080/helm_charts/hello-kitty.tgz 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 mario.alfredo.c.arevalo at intel.com Thu Feb 7 20:12:46 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Thu, 7 Feb 2019 20:12:46 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com> Hi team, There is a pair of issues which needs to be solved in order to create a “fm rest api” docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the “api-paste.ini” file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable “CUSTOMIZATION” of loci with something like this: “cat > /etc/fm/api-paste.ini << EOF config lines EOF” or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to “/etc/fm”. Issue 2: ======= The “fm rest api” requires a shared object called “libfmcommon.so”, this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however­ I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Thu Feb 7 20:37:59 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 7 Feb 2019 20:37:59 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com> Message-ID: For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cesar.lara at intel.com Thu Feb 7 20:50:54 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Thu, 7 Feb 2019 20:50:54 +0000 Subject: [Starlingx-discuss] [multios][meetings] MultiOS team meeting Agenda for 2/11/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105D6499@fmsmsx104.amr.corp.intel.com> MultiOS team meeting Agenda for 2/11/2019 - Continue Discussion on uploaded specs around MultiOS Multi-OS overview specification - https://review.openstack.org/#/c/619801/ Reorganize Flock Services Source Code repositories - https://review.openstack.org/#/c/631288/ Example of repo based on this spec - https://github.com/starlingx-staging/stx-packaging - MultiOS build system - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario.alfredo.c.arevalo at intel.com Thu Feb 7 21:01:06 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Thu, 7 Feb 2019 21:01:06 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com>, Message-ID: <6594B51DBE477C48AAE23675314E6C466456A9E8@fmsmsx107.amr.corp.intel.com> Hi Al, Thanks for your answer. I have done a tests with the fm_core-1.0-cp27-cp27mu-linux_x86_64.whl package that you mention, however it does not include libfmcommon.so library. I downloaded the last wheels taball and I unzip all packages and I could not find that library. Best regards. Mario. ________________________________________ From: Bailey, Henry Albert (Al) [Al.Bailey at windriver.com] Sent: Thursday, February 07, 2019 12:37 PM To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ildiko.vancsa at gmail.com Thu Feb 7 21:12:15 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 7 Feb 2019 22:12:15 +0100 Subject: [Starlingx-discuss] OpenStack Foundation 2018 Annual Report Message-ID: <2113C627-45E5-44B0-8AC3-D42386EECB4A@gmail.com> Hi, I would like to draw your attention to the OpenStack Foundation 2018 Annual Report [1], that we have published today, which is a yearly report highlighting the incredible work and advancements being achieved by the community. You can find information about news and activities that happened under the OpenStack Foundation umbrella including a summary on StarlingX. Read the latest on: • The Foundation’s latest initiatives to support Open Infrastructure • Project updates from the OpenStack, Airship, Kata Containers, StarlingX, and Zuul communities • Highlights from OpenStack Workings Groups and SIGs • Community programs including OpenStack Upstream Institute, the Travel Support Program, Outreachy Internship Programs, and Contributor recognition • OpenStack Foundation events including PTGs, Forums, OpenStack / OpenInfra Days, and the OpenStack Summit With almost 100,000 individual members, our community accomplished a lot last year. If you would like to continue to stay updated in the latest Foundation and project news, subscribe to the bi-weekly Open Infrastructure newsletter [2]. We look forward to another successful year in 2019! Thanks, Ildikó [1] https://www.openstack.org/foundation/2018-openstack-foundation-annual-report [2] https://www.openstack.org/community/email-signup From Al.Bailey at windriver.com Thu Feb 7 21:12:55 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 7 Feb 2019 21:12:55 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6594B51DBE477C48AAE23675314E6C466456A9E8@fmsmsx107.amr.corp.intel.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466456A9E8@fmsmsx107.amr.corp.intel.com> Message-ID: Looks like the wheel is not complete. the regular RPM is the only place that installs that shared lib. fm-common-1.0-8.tis.x86_64.rpm ie: /usr/lib64/libfmcommon.so.1 /usr/lib64/libfmcommon.so.1.0 I think you need to add this line in your build file DIST_PACKAGES="fm-common" Sort of this gnocchi does for rados https://github.com/openstack/stx-upstream/blob/master/openstack/python-gnocchi/centos/stx-gnocchi.pike_docker_image#L7 Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 4:01 PM To: Bailey, Henry Albert (Al); Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Al, Thanks for your answer. I have done a tests with the fm_core-1.0-cp27-cp27mu-linux_x86_64.whl package that you mention, however it does not include libfmcommon.so library. I downloaded the last wheels taball and I unzip all packages and I could not find that library. Best regards. Mario. ________________________________________ From: Bailey, Henry Albert (Al) [Al.Bailey at windriver.com] Sent: Thursday, February 07, 2019 12:37 PM To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ 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 Feb 7 21:26:03 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 7 Feb 2019 21:26:03 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466456A9E8@fmsmsx107.amr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA435C02@ALA-MBD.corp.ad.wrs.com> The wheel includes the fm_core.so library, which is compiled from the python source in fm-common. libfmcommon.so, however, is not python code, so would not be part of a wheel. It would need to be installed via the DIST_PACKAGES entry, as Al describes. -----Original Message----- From: Bailey, Henry Albert (Al) Sent: Thursday, February 07, 2019 4:13 PM To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Looks like the wheel is not complete. the regular RPM is the only place that installs that shared lib. fm-common-1.0-8.tis.x86_64.rpm ie: /usr/lib64/libfmcommon.so.1 /usr/lib64/libfmcommon.so.1.0 I think you need to add this line in your build file DIST_PACKAGES="fm-common" Sort of this gnocchi does for rados https://github.com/openstack/stx-upstream/blob/master/openstack/python-gnocchi/centos/stx-gnocchi.pike_docker_image#L7 Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 4:01 PM To: Bailey, Henry Albert (Al); Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Al, Thanks for your answer. I have done a tests with the fm_core-1.0-cp27-cp27mu-linux_x86_64.whl package that you mention, however it does not include libfmcommon.so library. I downloaded the last wheels taball and I unzip all packages and I could not find that library. Best regards. Mario. ________________________________________ From: Bailey, Henry Albert (Al) [Al.Bailey at windriver.com] Sent: Thursday, February 07, 2019 12:37 PM To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mario.alfredo.c.arevalo at intel.com Thu Feb 7 21:46:19 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Thu, 7 Feb 2019 21:46:19 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm charts In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA435C02@ALA-MBD.corp.ad.wrs.com> References: <6594B51DBE477C48AAE23675314E6C466456672F@fmsmsx107.amr.corp.intel.com> , <6703202FD9FDFF4A8DA9ACF104AE129FBA42F3BA@ALA-MBD.corp.ad.wrs.com>, <6594B51DBE477C48AAE23675314E6C4664568846@fmsmsx107.amr.corp.intel.com> <6594B51DBE477C48AAE23675314E6C466456A983@fmsmsx107.amr.corp.intel.com>, <6594B51DBE477C48AAE23675314E6C466456A9E8@fmsmsx107.amr.corp.intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA435C02@ALA-MBD.corp.ad.wrs.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466456AA6F@fmsmsx107.amr.corp.intel.com> Sounds good, thanks team!. Best Regards. Mario. > -----Original Message----- > From: Penney, Don [mailto:Don.Penney at windriver.com] > Sent: Thursday, February 7, 2019 3:26 PM > To: Bailey, Henry Albert (Al) ; Arevalo, Mario > Alfredo C ; Wold, Saul > ; Troyer, Dean > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > The wheel includes the fm_core.so library, which is compiled from the python > source in fm-common. > > libfmcommon.so, however, is not python code, so would not be part of a wheel. > It would need to be installed via the DIST_PACKAGES entry, as Al describes. > > > -----Original Message----- > From: Bailey, Henry Albert (Al) > Sent: Thursday, February 07, 2019 4:13 PM > To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > Looks like the wheel is not complete. > > the regular RPM is the only place that installs that shared lib. > fm-common-1.0-8.tis.x86_64.rpm > > ie: > /usr/lib64/libfmcommon.so.1 > /usr/lib64/libfmcommon.so.1.0 > > > I think you need to add this line in your build file DIST_PACKAGES="fm- > common" > > Sort of this gnocchi does for rados > https://github.com/openstack/stx-upstream/blob/master/openstack/python- > gnocchi/centos/stx-gnocchi.pike_docker_image#L7 > > Al > > -----Original Message----- > From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] > Sent: Thursday, February 07, 2019 4:01 PM > To: Bailey, Henry Albert (Al); Penney, Don; Wold, Saul; Troyer, Dean > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > Hi Al, > > Thanks for your answer. > > I have done a tests with the fm_core-1.0-cp27-cp27mu-linux_x86_64.whl > package that you mention, however it does not include libfmcommon.so library. > I downloaded the last wheels taball and I unzip all packages and I could not find > that library. > > Best regards. > Mario. > ________________________________________ > From: Bailey, Henry Albert (Al) [Al.Bailey at windriver.com] > Sent: Thursday, February 07, 2019 12:37 PM > To: Arevalo, Mario Alfredo C; Penney, Don; Wold, Saul; Troyer, Dean > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > For issue 1) > Other openstack components write the paste like this Here's the template for > writing the api-paste.ini > https://github.com/openstack/openstack- > helm/blob/master/heat/templates/configmap-etc.yaml#L139 > Here's example data being written to it: > https://github.com/openstack/openstack- > helm/blob/master/heat/values.yaml#L275 > > For issue 2) > You should be able to include the wheel for fm_core, which is defined here > https://github.com/openstack/stx-fault/blob/master/fm- > common/sources/setup.py > > it's in fm-common folder, but its called fm_core and it is included in the wheels > tarball > http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_ > image_build/outputs/wheels/ > > fm_core-1.0-cp27-cp27mu-linux_x86_64.whl > > The wheel contains C code, so it is an architecture specific wheel > > Al > > > -----Original Message----- > From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] > Sent: Thursday, February 07, 2019 3:13 PM > To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > Hi team, > > There is a pair of issues which needs to be solved in order to create a "fm rest > api" docker image that can work correctly. > > Issue 1: > ======= > > The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems > that this file is created in the deployment process in this section by puppet: > https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet- > fm/src/fm/manifests/init.pp#n109 > > proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" > file was added manually inside devstack/files directory[1], then during the > devstack execution process, the plugin just makes a copy to the environment: > https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 > > I wonder if it is the best approach to do something similar using the variable > "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini > << EOF config lines EOF" or maybe cloning the stx-fault repository and copying > the available file in the devstack directory[0] to "/etc/fm". > > Issue 2: > ======= > > The "fm rest api" requires a shared object called "libfmcommon.so", this library > is created in fm-common project, however it is not available in any wheel > package. > > Proposal: I am not sure if something like this should be enough: > data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] > > Furthermore I tried to add it from the specfile: > https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm- > common.spec#n54 > however I think this is not a good option. > > What do you think is the best approach to tackle these issues? > > Any comments are welcome. > > Best regards. > Mario. > > [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini > [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files > [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py > > > > ________________________________________ > From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] > Sent: Friday, February 01, 2019 7:54 PM > To: Penney, Don; Miller, Frank > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts > > Hi Folks, > > This a short update about this task (I will be in holiday for our next > containerization meeting). > During this week I have been exploring the scripts and tools involved in the > containerization building process. This activity and the wiki page shared by Don > Penny have allowed me to get a better understating of the work-flow. I have > sent a PR[1] with the required files to create an image for fm-rest-api service. At > this moment it is WIP due to I need to do testing. Possibly it will require more > dependencies which are not available in the wheels.cfg/tarball, I will continue > working on this. > During the building tools exploration I had some issues related to network due > to I am working behind a proxy, I sent a patch[2] to set it in the docker > build/run commands and avoid manually modification efforts. > > Any comments, feel free to contact me. > > [1] https://review.openstack.org/#/c/634540/ > [2] https://review.openstack.org/#/c/634542/ > > Best regards. > Mario. > > ________________________________________ > From: Penney, Don [Don.Penney at windriver.com] > Sent: Wednesday, January 30, 2019 7:24 AM > To: Arevalo, Mario Alfredo C; Miller, Frank > Cc: Saul Wold; starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages > > > -----Original Message----- > From: Penney, Don > Sent: Tuesday, January 29, 2019 10:34 AM > To: 'Arevalo, Mario Alfredo C'; Miller, Frank > Cc: Saul Wold; starlingx-discuss at lists.starlingx.io > Subject: RE: [Containers] Background info on helm charts > > Hi Mario, > > I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on > it today, and try to get something published in the next couple of days, barring > other issues coming along. > > Cheers, > Don. > > -----Original Message----- > From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] > Sent: Monday, January 28, 2019 4:15 PM > To: Miller, Frank > Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don > Subject: RE: [Containers] Background info on helm charts > > Hi Frank, > > Thank you for the information, however my doubts are oriented more to the > work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] > for FM service in the last week, nevertheless, the starlingx work-flow includes > some parts which I have not digested completely yet. Don Penny have helped > me sending useful information related to this (Thanks for that), the interaction > between OpenStack/loci system and python/wheels. However I have some > gaps, for example, as staring point I have to create the docker image which will > be consumed by the chart. There are some build scripts and notes that talks > about this, but precisely, there are a pair of lines in the build-tools/README > which makes reference to a exposed service that is not specified [2,3]. > For that reason I asked for a little more detailed information about the work- > flow during our meeting today. > > Thanks for your attention. > > Best regards. > Mario. > > [1] https://github.com/MarioCarrilloA/chart-playground > [2] https://github.com/openstack/stx-root/blob/master/build-tools/build- > docker-images/README#L4 > [3] https://github.com/openstack/stx-root/blob/master/build-tools/build- > docker-images/README#L9 > > > > > > > > From: Miller, Frank [Frank.Miller at windriver.com] > > Sent: Monday, January 28, 2019 11:19 AM > > To: Arevalo, Mario Alfredo C > > Cc: Saul Wold; starlingx-discuss at lists.starlingx.io > > Subject: [Containers] Background info on helm charts > > > > > > > > Mario: > > On the containers community call this morning we took an action to identify > information about helm charts. Irina Mihai identified four references that she > used when working on the cinder helm chart overrides. See [1] to [4] below. > > Also as you work on creating a helm chart for the FM service, you should look at > examples of existing helm charts for a reference. 2 good examples are: > * > Cinder helm chart which is available in the upstream openstack-helm project [5] > and uses certain defaults. We have added StarlingX specific overrides which are > generated from code we added [6]. > * > Nova-api-proxy which is a StarlingX specific service and hence was created from > scratch [7,8] > > Frank > > [1] > > https://docs.helm.sh/developing_charts/ > [2] https://medium.com/containerum/how-to-make-and-share-your-own- > helm-package-50ae40f6c221 > [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ > [4] Helm chart install order https://github.com/helm/helm/blob/release- > 2.10/pkg/tiller/kind_sorter.go#L29 > [5] Cinder helm chart in upstream openstack-helm: > > https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder > [6] StarlingX cinder overrides: See cinder.py in > > https://github.com/openstack/stx- > config/tree/master/sysinv/sysinv/sysinv/sysinv/helm > > [7] Helm chart for nova_api_proxy: > > https://git.openstack.org/cgit/openstack/stx- > config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx- > openstack-helm/nova-api-proxy > > [8] nova_api_proxy override code: See nova_api_proxy.py in > https://github.com/openstack/stx- > config/tree/master/sysinv/sysinv/sysinv/sysinv/helm > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Feb 7 21:52:01 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 7 Feb 2019 21:52:01 +0000 Subject: [Starlingx-discuss] Docs mega spec up for review Message-ID: <9A85D2917C58154C960D95352B22818BBFD1D64E@fmsmsx123.amr.corp.intel.com> The Docs team has been working on a spec for an overhaul of our formal project documentation, and the spec has been posted for review. You can find it at https://review.openstack.org/#/c/635641. Feedback and comments graciously accepted! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Thu Feb 7 22:20:03 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Thu, 7 Feb 2019 22:20:03 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDB70F7@ALA-MBD.corp.ad.wrs.com> Hi Mario, With regards to issues # 2, FM rest api (located under stx/stx-fault/fm-rest-api) does not use a shared object called “libfmcommon.so”. Unless you are referring to FM application API (located under /stx/stx-fault/fm-api), correct me if I am wrong. The application API is provided as a python package and it is used by the platform applications to raise/clear alarms, or generate logs. The rest API provides client interfaces, and a API server for communicating with other applications(both internal and external) that request to review alarms/logs, or suppress alarms (from viewing). In the pre-k8s world, VIM uses the application API to raise/clear alarms, and generates logs; this api is imported as a python package. For orchestration, VIM uses the rest api to monitor system alarms/logs. With regards to the issue #1, you are referring to FM rest api paste config file. I assume that you are containerizing FM rest api, since the application API is not a message-based interface . Regards, Tao ----------------------------------------------------------------------------------------------------------------------------------------------------- Message: 3 Date: Thu, 7 Feb 2019 20:12:46 +0000 From: "Arevalo, Mario Alfredo C" To: "Penney, Don" , "Wold, Saul" , "al.bailey at windriver.com" , "Troyer, Dean" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Message-ID: <6594B51DBE477C48AAE23675314E6C466456A983 at fmsmsx107.amr.corp.intel.com> Content-Type: text/plain; charset="Windows-1252" Hi team, There is a pair of issues which needs to be solved in order to create a “fm rest api” docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the “api-paste.ini” file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable “CUSTOMIZATION” of loci with something like this: “cat > /etc/fm/api-paste.ini << EOF config lines EOF” or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to “/etc/fm”. Issue 2: ======= The “fm rest api” requires a shared object called “libfmcommon.so”, this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however­ I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 4 Date: Thu, 7 Feb 2019 20:37:59 +0000 From: "Bailey, Henry Albert (Al)" To: "Arevalo, Mario Alfredo C" , "Penney, Don" , "Wold, Saul" , "Troyer, Dean" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Message-ID: Content-Type: text/plain; charset="us-ascii" For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ 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 9, Issue 34 ************************************************ From mario.alfredo.c.arevalo at intel.com Thu Feb 7 22:54:54 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Thu, 7 Feb 2019 22:54:54 +0000 Subject: [Starlingx-discuss] [Containers] Background info on helm In-Reply-To: <7242A3DC72E453498E3D783BBB134C3E9DDB70F7@ALA-MBD.corp.ad.wrs.com> References: <7242A3DC72E453498E3D783BBB134C3E9DDB70F7@ALA-MBD.corp.ad.wrs.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466456AAE3@fmsmsx107.amr.corp.intel.com> Hi Tao, That is correct, I was making reference to "/stx/stx-fault/fm-api", and yeah I am containerizing FM rest api, thanks for your answer. Best regards. Mario. ________________________________________ From: Liu, Tao [Tao.Liu at windriver.com] Sent: Thursday, February 07, 2019 2:20 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm Hi Mario, With regards to issues # 2, FM rest api (located under stx/stx-fault/fm-rest-api) does not use a shared object called “libfmcommon.so”. Unless you are referring to FM application API (located under /stx/stx-fault/fm-api), correct me if I am wrong. The application API is provided as a python package and it is used by the platform applications to raise/clear alarms, or generate logs. The rest API provides client interfaces, and a API server for communicating with other applications(both internal and external) that request to review alarms/logs, or suppress alarms (from viewing). In the pre-k8s world, VIM uses the application API to raise/clear alarms, and generates logs; this api is imported as a python package. For orchestration, VIM uses the rest api to monitor system alarms/logs. With regards to the issue #1, you are referring to FM rest api paste config file. I assume that you are containerizing FM rest api, since the application API is not a message-based interface . Regards, Tao ----------------------------------------------------------------------------------------------------------------------------------------------------- Message: 3 Date: Thu, 7 Feb 2019 20:12:46 +0000 From: "Arevalo, Mario Alfredo C" To: "Penney, Don" , "Wold, Saul" , "al.bailey at windriver.com" , "Troyer, Dean" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Message-ID: <6594B51DBE477C48AAE23675314E6C466456A983 at fmsmsx107.amr.corp.intel.com> Content-Type: text/plain; charset="Windows-1252" Hi team, There is a pair of issues which needs to be solved in order to create a “fm rest api” docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the “api-paste.ini” file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable “CUSTOMIZATION” of loci with something like this: “cat > /etc/fm/api-paste.ini << EOF config lines EOF” or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to “/etc/fm”. Issue 2: ======= The “fm rest api” requires a shared object called “libfmcommon.so”, this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however­ I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ Message: 4 Date: Thu, 7 Feb 2019 20:37:59 +0000 From: "Bailey, Henry Albert (Al)" To: "Arevalo, Mario Alfredo C" , "Penney, Don" , "Wold, Saul" , "Troyer, Dean" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Message-ID: Content-Type: text/plain; charset="us-ascii" For issue 1) Other openstack components write the paste like this Here's the template for writing the api-paste.ini https://github.com/openstack/openstack-helm/blob/master/heat/templates/configmap-etc.yaml#L139 Here's example data being written to it: https://github.com/openstack/openstack-helm/blob/master/heat/values.yaml#L275 For issue 2) You should be able to include the wheel for fm_core, which is defined here https://github.com/openstack/stx-fault/blob/master/fm-common/sources/setup.py it's in fm-common folder, but its called fm_core and it is included in the wheels tarball http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/wheels/ fm_core-1.0-cp27-cp27mu-linux_x86_64.whl The wheel contains C code, so it is an architecture specific wheel Al -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Thursday, February 07, 2019 3:13 PM To: Penney, Don; Wold, Saul; Bailey, Henry Albert (Al); Troyer, Dean Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi team, There is a pair of issues which needs to be solved in order to create a "fm rest api" docker image that can work correctly. Issue 1: ======= The fm-rest-api requires a configuration file called "api-paste.ini"[0]. It seems that this file is created in the deployment process in this section by puppet: https://git.starlingx.io/cgit/stx-config/tree/puppet-modules-wrs/puppet-fm/src/fm/manifests/init.pp#n109 proposal: I noticed how devstack process deal with this, firstly the "api-paste.ini" file was added manually inside devstack/files directory[1], then during the devstack execution process, the plugin just makes a copy to the environment: https://git.starlingx.io/cgit/stx-fault/tree/devstack/lib/stx-fault#n173 I wonder if it is the best approach to do something similar using the variable "CUSTOMIZATION" of loci with something like this: "cat > /etc/fm/api-paste.ini << EOF config lines EOF" or maybe cloning the stx-fault repository and copying the available file in the devstack directory[0] to "/etc/fm". Issue 2: ======= The "fm rest api" requires a shared object called "libfmcommon.so", this library is created in fm-common project, however it is not available in any wheel package. Proposal: I am not sure if something like this should be enough: data_files=[('/usr/lib64', ['libfmcommon.so'])], inside the setup.py[2] Furthermore I tried to add it from the specfile: https://git.starlingx.io/cgit/stx-fault/tree/fm-common/centos/fm-common.spec#n54 however I think this is not a good option. What do you think is the best approach to tackle these issues? Any comments are welcome. Best regards. Mario. [0] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files/api-paste.ini [1] https://git.starlingx.io/cgit/stx-fault/tree/devstack/files [2] https://git.starlingx.io/cgit/stx-fault/tree/fm-common/sources/setup.py ________________________________________ From: Arevalo, Mario Alfredo C [mario.alfredo.c.arevalo at intel.com] Sent: Friday, February 01, 2019 7:54 PM To: Penney, Don; Miller, Frank Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Background info on helm charts Hi Folks, This a short update about this task (I will be in holiday for our next containerization meeting). During this week I have been exploring the scripts and tools involved in the containerization building process. This activity and the wiki page shared by Don Penny have allowed me to get a better understating of the work-flow. I have sent a PR[1] with the required files to create an image for fm-rest-api service. At this moment it is WIP due to I need to do testing. Possibly it will require more dependencies which are not available in the wheels.cfg/tarball, I will continue working on this. During the building tools exploration I had some issues related to network due to I am working behind a proxy, I sent a patch[2] to set it in the docker build/run commands and avoid manually modification efforts. Any comments, feel free to contact me. [1] https://review.openstack.org/#/c/634540/ [2] https://review.openstack.org/#/c/634542/ Best regards. Mario. ________________________________________ From: Penney, Don [Don.Penney at windriver.com] Sent: Wednesday, January 30, 2019 7:24 AM To: Arevalo, Mario Alfredo C; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts https://wiki.openstack.org/wiki/StarlingX/Containers/BuildingImages -----Original Message----- From: Penney, Don Sent: Tuesday, January 29, 2019 10:34 AM To: 'Arevalo, Mario Alfredo C'; Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Background info on helm charts Hi Mario, I'm making "writing a wiki" one of my top priorities. I'm hoping to get started on it today, and try to get something published in the next couple of days, barring other issues coming along. Cheers, Don. -----Original Message----- From: Arevalo, Mario Alfredo C [mailto:mario.alfredo.c.arevalo at intel.com] Sent: Monday, January 28, 2019 4:15 PM To: Miller, Frank Cc: Saul Wold; starlingx-discuss at lists.starlingx.io; Penney, Don Subject: RE: [Containers] Background info on helm charts Hi Frank, Thank you for the information, however my doubts are oriented more to the work-flow than the Dockerfile/helm/chart/ tools. Even I created a dockerfile[1] for FM service in the last week, nevertheless, the starlingx work-flow includes some parts which I have not digested completely yet. Don Penny have helped me sending useful information related to this (Thanks for that), the interaction between OpenStack/loci system and python/wheels. However I have some gaps, for example, as staring point I have to create the docker image which will be consumed by the chart. There are some build scripts and notes that talks about this, but precisely, there are a pair of lines in the build-tools/README which makes reference to a exposed service that is not specified [2,3]. For that reason I asked for a little more detailed information about the work-flow during our meeting today. Thanks for your attention. Best regards. Mario. [1] https://github.com/MarioCarrilloA/chart-playground [2] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L4 [3] https://github.com/openstack/stx-root/blob/master/build-tools/build-docker-images/README#L9 From: Miller, Frank [Frank.Miller at windriver.com] Sent: Monday, January 28, 2019 11:19 AM To: Arevalo, Mario Alfredo C Cc: Saul Wold; starlingx-discuss at lists.starlingx.io Subject: [Containers] Background info on helm charts Mario: On the containers community call this morning we took an action to identify information about helm charts. Irina Mihai identified four references that she used when working on the cinder helm chart overrides. See [1] to [4] below. Also as you work on creating a helm chart for the FM service, you should look at examples of existing helm charts for a reference. 2 good examples are: * Cinder helm chart which is available in the upstream openstack-helm project [5] and uses certain defaults. We have added StarlingX specific overrides which are generated from code we added [6]. * Nova-api-proxy which is a StarlingX specific service and hence was created from scratch [7,8] Frank [1] https://docs.helm.sh/developing_charts/ [2] https://medium.com/containerum/how-to-make-and-share-your-own-helm-package-50ae40f6c221 [3] https://docs.bitnami.com/kubernetes/how-to/create-your-first-helm-chart/ [4] Helm chart install order https://github.com/helm/helm/blob/release-2.10/pkg/tiller/kind_sorter.go#L29 [5] Cinder helm chart in upstream openstack-helm: https://git.openstack.org/cgit/openstack/openstack-helm/tree/cinder [6] StarlingX cinder overrides: See cinder.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm [7] Helm chart for nova_api_proxy: https://git.openstack.org/cgit/openstack/stx-config/tree/kubernetes/applications/stx-openstack/stx-openstack-helm/stx-openstack-helm/nova-api-proxy [8] nova_api_proxy override code: See nova_api_proxy.py in https://github.com/openstack/stx-config/tree/master/sysinv/sysinv/sysinv/sysinv/helm _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss ------------------------------ 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 9, Issue 34 ************************************************ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From yang.liu at windriver.com Fri Feb 8 18:08:32 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Fri, 8 Feb 2019 18:08:32 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Message-ID: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Fri Feb 8 22:31:54 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 8 Feb 2019 22:31:54 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190208 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C8FA1D@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-08 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 22 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Sat Feb 9 00:38:09 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Sat, 9 Feb 2019 00:38:09 +0000 Subject: [Starlingx-discuss] Reverting commit due to load breakage In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62A97@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA62A97@ALA-MBD.corp.ad.wrs.com> Message-ID: Sorry about this, there was a bug in the installation path in the modified specfiles. I sent the new review with this change and config_controller run without issues: https://review.openstack.org/#/c/635990/1 -Erich On Thu, 2019-02-07 at 13:30 +0000, Wensley, Barton wrote: > The following commit appears to have broken installations and is > being reverted: > https://git.openstack.org/cgit/openstack/stx-config/commit/?id=24fd04 > 5f6883dc060d6e09b5444080cae5196847 > > The failure happens during config_controller at step 02: > Failed at Step 02 . . . Failed to execute bootstrap manifest. > > The following error is seen in /var/log/puppet/latest/puppet.log: > 2019-02-07T00:03:07.915 Debug: 2019-02-07 00:03:06 +0000 Executing: > '/usr/bin/openstack complete' > 2019-02-07T00:03:08.827 Debug: 2019-02-07 00:03:08 +0000 importing > '/usr/share/puppet/modules/platform/manifests/sysinv.pp' in > environment production > 2019-02-07T00:03:08.849 Debug: 2019-02-07 00:03:08 +0000 > Automatically imported platform::sysinv::bootstrap from > platform/sysinv into production > 2019-02-07T00:03:08.851 Error: 2019-02-07 00:03:08 +0000 Evaluation > Error: Error while evaluating a Function Call, Could not find class > ::sysinv::db::postgresql for localhost at > /usr/share/puppet/modules/platform/manifests/sysinv.pp:160:3 on node > localhost > > Due to the build failure last night, this commit does not yet appear > in a public build. > > Bart Wensley, Member of Technical Staff, Wind River > direct 613.963.1385 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From cindy.xie at intel.com Sat Feb 9 01:27:32 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sat, 9 Feb 2019 01:27:32 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Sat Feb 9 02:18:00 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Sat, 9 Feb 2019 02:18:00 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Sat Feb 9 16:13:34 2019 From: sgw at linux.intel.com (Saul Wold) Date: Sat, 9 Feb 2019 08:13:34 -0800 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> Message-ID: <1f26a897-8f51-da70-2af1-8bbefdad3c6c@linux.intel.com> Cindy, I asked Ada to rebuild and re-test based on the patch that Martin provided before CNY, the 20190202 ISO failed the Duplex testing, but when manually patched succeeded. I wondered if the 20190202 ISO was not rebuilt correctly. This is why I have not merged Martin's patch yet, I did not find out about this failure mode until Thursday. They started that build on Friday and should be able to test it on Monday. If your team is back already and can also rebuild with the patch included and confirm it's correct, then we can work to unblock testing of CentOS-76 work. Sau! On 2/8/19 6:18 PM, Liu, Yang wrote: > Correct. > > BR, > > Yang > > *From:*Xie, Cindy [mailto:cindy.xie at intel.com] > *Sent:* February-08-19 8:28 PM > *To:* Liu, Yang; starlingx-discuss at lists.starlingx.io > *Subject:* RE: CentOS7.6 testing status - blocked > > Hi, Yang, > > Thanks for the report. > > Are the “two node system” below referring to Duplex? Just want to > confirm because #1814360 we have a patch pending and we do want to > ensure it works on Duplex as well. > > Th.x - cindy > > *From:* Liu, Yang [mailto:yang.liu at windriver.com] > *Sent:* Saturday, February 9, 2019 2:09 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] CentOS7.6 testing status - blocked > > Hi folks, > > Here’s an update for CentOS7.6 testing. > > We are currently blocked due to pxeboot from controller-0 does not work > for EFI. (#1814360) > > We will continue after that issue is resolved. > > System > > > > NICs > > Mgmt;infra;data > > > > Special Configs > > > > Test coverage after Install and Config > > > > Status/Issues > > Dedicated storage > > > > X540-AT2; X540-AT2; fortville > > > > IPv6 > > > > Sanity, nova > > > > Completed. New issues logged. > > #1814336 CentOS7.6: Unable to launch vm directly from virsh > > > #1814335 CentOS7.6: Unable to launch vm with UEFI boot > > > One node system > > > > none; none; X522/X577-AT > > > > > > Sanity, basic regression > > > > Completed. Passed. > > Two node system > > > > fortville; fortville; fortville > > > > tboot, tpm, https, > > extended security profile > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > BCM5720; Niantic; Niantic > > > > Sriov(niantic),pcipt(niantic) > > > > Sanity, networking > > > > Completed. Passed. > > Two node system > > > > Fortville; none; Fortville > > > > Low latency, UEFI > > > > Sanity, basic regression, cyclictest > > > > Blocked by #1814360 > > Two node system > > > > Fortville; none; Fortville > > > > Secure boot > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > I350; Niantic/cx3; cx3 > > > > Pxeboot script > > > > Sanity > > > > Completed. Passed. > > Only compute-0 was used, since compute-1 has CX3 data nic. > > ?? > > > > CX4 on infra or mgmt, but NOT data > > > > Won’t test. We don’t have a system have required nics. > > BR, > > yang > > > _______________________________________________ > 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 Sun Feb 10 06:00:35 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 10 Feb 2019 01:00:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 165 - Failure! Message-ID: <962573924.2.1549778437065.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 165 Status: Failure Timestamp: 20190210T060031Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190210T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190210T060000Z DOCKER_DL_ID: jenkins-master-20190210T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190210T060000Z/logs DOCKER_DL_TAG: master-20190210T060000Z-downloader-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190210T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Feb 10 06:00:39 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 10 Feb 2019 01:00:39 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 133 - Failure! Message-ID: <897966598.5.1549778440552.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 133 Status: Failure Timestamp: 20190210T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190210T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From cindy.xie at intel.com Sun Feb 10 13:29:12 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Sun, 10 Feb 2019 13:29:12 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <1f26a897-8f51-da70-2af1-8bbefdad3c6c@linux.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <1f26a897-8f51-da70-2af1-8bbefdad3c6c@linux.intel.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E824FE@SHSMSX104.ccr.corp.intel.com> Thank you, Saul - it's might be possible that the ISO is not consistent with the patch that supposed to be built in. It will be very valuable that Ada continue the testing of the re-built image with the patch cherry-pick in. Thx. - cindy -----Original Message----- From: Saul Wold [mailto:sgw at linux.intel.com] Sent: Sunday, February 10, 2019 12:14 AM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Cindy, I asked Ada to rebuild and re-test based on the patch that Martin provided before CNY, the 20190202 ISO failed the Duplex testing, but when manually patched succeeded. I wondered if the 20190202 ISO was not rebuilt correctly. This is why I have not merged Martin's patch yet, I did not find out about this failure mode until Thursday. They started that build on Friday and should be able to test it on Monday. If your team is back already and can also rebuild with the patch included and confirm it's correct, then we can work to unblock testing of CentOS-76 work. Sau! On 2/8/19 6:18 PM, Liu, Yang wrote: > Correct. > > BR, > > Yang > > *From:*Xie, Cindy [mailto:cindy.xie at intel.com] > *Sent:* February-08-19 8:28 PM > *To:* Liu, Yang; starlingx-discuss at lists.starlingx.io > *Subject:* RE: CentOS7.6 testing status - blocked > > Hi, Yang, > > Thanks for the report. > > Are the “two node system” below referring to Duplex? Just want to > confirm because #1814360 we have a patch pending and we do want to > ensure it works on Duplex as well. > > Th.x - cindy > > *From:* Liu, Yang [mailto:yang.liu at windriver.com] > *Sent:* Saturday, February 9, 2019 2:09 AM > *To:* starlingx-discuss at lists.starlingx.io > *Subject:* [Starlingx-discuss] CentOS7.6 testing status - blocked > > Hi folks, > > Here’s an update for CentOS7.6 testing. > > We are currently blocked due to pxeboot from controller-0 does not > work for EFI. (#1814360) > > We will continue after that issue is resolved. > > System > > > > NICs > > Mgmt;infra;data > > > > Special Configs > > > > Test coverage after Install and Config > > > > Status/Issues > > Dedicated storage > > > > X540-AT2; X540-AT2; fortville > > > > IPv6 > > > > Sanity, nova > > > > Completed. New issues logged. > > #1814336 CentOS7.6: Unable to launch vm directly from virsh > > > #1814335 CentOS7.6: Unable to launch vm with UEFI boot > > > One node system > > > > none; none; X522/X577-AT > > > > > > Sanity, basic regression > > > > Completed. Passed. > > Two node system > > > > fortville; fortville; fortville > > > > tboot, tpm, https, > > extended security profile > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > BCM5720; Niantic; Niantic > > > > Sriov(niantic),pcipt(niantic) > > > > Sanity, networking > > > > Completed. Passed. > > Two node system > > > > Fortville; none; Fortville > > > > Low latency, UEFI > > > > Sanity, basic regression, cyclictest > > > > Blocked by #1814360 > > Two node system > > > > Fortville; none; Fortville > > > > Secure boot > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > I350; Niantic/cx3; cx3 > > > > Pxeboot script > > > > Sanity > > > > Completed. Passed. > > Only compute-0 was used, since compute-1 has CX3 data nic. > > ?? > > > > CX4 on infra or mgmt, but NOT data > > > > Won’t test. We don’t have a system have required nics. > > BR, > > yang > > > _______________________________________________ > 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 build.starlingx at gmail.com Mon Feb 11 06:00:34 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 11 Feb 2019 01:00:34 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 166 - Still Failing! In-Reply-To: <639788786.0.1549778432919.JavaMail.javamailuser@localhost> References: <639788786.0.1549778432919.JavaMail.javamailuser@localhost> Message-ID: <482644970.8.1549864835541.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 166 Status: Still Failing Timestamp: 20190211T060029Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190211T060000Z DOCKER_DL_ID: jenkins-master-20190211T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T060000Z/logs DOCKER_DL_TAG: master-20190211T060000Z-downloader-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190211T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Feb 11 06:00:37 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 11 Feb 2019 01:00:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 134 - Still Failing! In-Reply-To: <1878626154.3.1549778437936.JavaMail.javamailuser@localhost> References: <1878626154.3.1549778437936.JavaMail.javamailuser@localhost> Message-ID: <1883447254.11.1549864838898.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 134 Status: Still Failing Timestamp: 20190211T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From Ian.Jolliffe at windriver.com Mon Feb 11 14:52:40 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Mon, 11 Feb 2019 14:52:40 +0000 Subject: [Starlingx-discuss] [TSC]MInutes - February 7, 2019 Message-ID: <351CFA9E-A2D3-4CBC-8AE1-965B517CD250@windriver.com> Hi all; TSC attendees: Brent, Curtis, Dean, Ian, Miguel, Saul First Contact SIG/Group (ildikov) * Came up on the community planning call to explore the idea of creating a group to help new comers to participate in the community * Group in OpenStack: https://wiki.openstack.org/wiki/First_Contact_SIG * Focus is helping new contributors * Coordinate office hours, other ways to help new users, developers encourage community norms on boarding new developers and potentially new orgs help dev's in different time zones * and people who don't work full time on stx and can't attend meetings as they are usually during NA working hours. * The SIG developed doc's to help getting started in the community * Do we want a similar group within STX community? It could be a way to move forward ideas from F2F. Curtis - need for a structured group, don't need to adopt carte blanche, how helpful is office hours? Liason list might help Table for today - what items are important to the project - get feedback from ML - Bruce put on community call agenda for next week. Community planning call to happen every other week. * May want to change the name of the call, bit confusing to have a "community" call and a "community planning" call, which is really open source biz dev-type stuff Pharos labs - testing opportunity (Ian) * tie in with OPNFV test suites – Functest, storperf, Dovetail, Yardstick (which also pull in Rally from OpenStack) * One Pharos lab is running StarlingX release 1 – very cool * can we leverage these resources * Tie in with Ci/CD pipelines * Miguel - talked to OPNFV QA project leader - will work to connect dots STX policies (Curtis) * Some discussion of security policy in community meeting around making policy immutable by storing text in images...should come to some kind of governance conclusion on how to store policies, and whether or not immutability is even an issue. Of course enforcing polices is another gray area... :) * once one is written - where does it live and how does it evolve. Immutablity - that change happens but it is reviewed and can be reverted as required stx/gov and stx/specs are places for those reviews, some could go into docs if required * gerrit review process works for policy management/updates * TSC should approve policy - and changes - what is the threshold for change approval we want * we need think what the threshold should be based on some examples ( simple majority vs super majority ) * Do we need a policy repo? * Close on path forward at Feb 14th meeting. Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Mon Feb 11 15:30:25 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 11 Feb 2019 15:30:25 +0000 Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Message-ID: <8557B550001AFB46A43A0CCC314BF85153C95ECF@FMSMSX108.amr.corp.intel.com> Hi, In order to launch instances from a volume snapshot, I use nova boot command. After deploy an STX containerized system this command is returning below error: [wrsroot at controller-0 ~(keystone_admin)]$ nova boot -flavor --snapshot --nic ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) I tried with 'source /etc/nova/openrc' and 'source /etc/platform/openrc' authentication, both got the same issue. Is this nova boot command still supported with containers? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Mon Feb 11 15:41:07 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Mon, 11 Feb 2019 15:41:07 +0000 Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C95ECF@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C95ECF@FMSMSX108.amr.corp.intel.com> Message-ID: I believe you are authenticating with the keystone that is on the controller, rather than the one that is running in the container. Refer to this section of the wiki https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints Once you are pointing at the nova that is running in the container, those nova commands should work as expected. Al From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, February 11, 2019 10:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Hi, In order to launch instances from a volume snapshot, I use nova boot command. After deploy an STX containerized system this command is returning below error: [wrsroot at controller-0 ~(keystone_admin)]$ nova boot -flavor --snapshot --nic ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) I tried with 'source /etc/nova/openrc' and 'source /etc/platform/openrc' authentication, both got the same issue. Is this nova boot command still supported with containers? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Mon Feb 11 15:49:09 2019 From: scott.little at windriver.com (Scott Little) Date: Mon, 11 Feb 2019 10:49:09 -0500 Subject: [Starlingx-discuss] Access to mirror.starlingx.cengn.ca Message-ID: Access to mirror.starlingx.cengn.ca will be subject to a few interruptions throughout the day. I am working with the folks at CENGN to restore normal operations after the maintenance outage of the past weekend. Apologies for the inconvenience. Scott From juan.carlos.alonso at intel.com Mon Feb 11 16:45:35 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 11 Feb 2019 16:45:35 +0000 Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Message-ID: <8557B550001AFB46A43A0CCC314BF85153C96F0C@FMSMSX108.amr.corp.intel.com> Hi, Yes, export OS_CLOUD=openstack_helm already applied. Openstack commands work correctly but nova, glance, cinder are asking for user name, user id, project name, tenant id, etc.. I think some this parameters are defined on /etc/openstack/clouds.yaml, right? Does clouds.yaml need extra parameters? That's why also I am asking if nova, glance, cinder, etc commands won't be supported? In order to update to openstack command. Regards. Juan Carlos Alonso From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, February 11, 2019 9:41 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? I believe you are authenticating with the keystone that is on the controller, rather than the one that is running in the container. Refer to this section of the wiki https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints Once you are pointing at the nova that is running in the container, those nova commands should work as expected. Al From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, February 11, 2019 10:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Hi, In order to launch instances from a volume snapshot, I use nova boot command. After deploy an STX containerized system this command is returning below error: [wrsroot at controller-0 ~(keystone_admin)]$ nova boot -flavor --snapshot --nic ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) I tried with 'source /etc/nova/openrc' and 'source /etc/platform/openrc' authentication, both got the same issue. Is this nova boot command still supported with containers? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Mon Feb 11 17:00:52 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Mon, 11 Feb 2019 17:00:52 +0000 Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C96F0C@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C96F0C@FMSMSX108.amr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F86218307E@ALA-MBD.corp.ad.wrs.com> If you ever sourced to openrc file in the same shell, then the auth url in the openrc file will be used. After sourcing to /etc/nova/openrc, if you want to switch back to containerized openstack cli's, you can export the os_auth_url to make sure the correct keystone is used. export OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3 BR, Yang From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: February-11-19 11:46 AM To: Bailey, Henry Albert (Al); 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Hi, Yes, export OS_CLOUD=openstack_helm already applied. Openstack commands work correctly but nova, glance, cinder are asking for user name, user id, project name, tenant id, etc.. I think some this parameters are defined on /etc/openstack/clouds.yaml, right? Does clouds.yaml need extra parameters? That's why also I am asking if nova, glance, cinder, etc commands won't be supported? In order to update to openstack command. Regards. Juan Carlos Alonso From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Monday, February 11, 2019 9:41 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: Re: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? I believe you are authenticating with the keystone that is on the controller, rather than the one that is running in the container. Refer to this section of the wiki https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints Once you are pointing at the nova that is running in the container, those nova commands should work as expected. Al From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, February 11, 2019 10:30 AM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? Hi, In order to launch instances from a volume snapshot, I use nova boot command. After deploy an STX containerized system this command is returning below error: [wrsroot at controller-0 ~(keystone_admin)]$ nova boot -flavor --snapshot --nic ERROR (ConnectFailure): Unable to establish connection to http://192.168.204.2:8774/v2.1/a4952fba408146b9b6cbe2e028da2708: HTTPConnectionPool(host='192.168.204.2', port=8774): Max retries exceeded with url: /v2.1/a4952fba408146b9b6cbe2e028da2708 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',)) I tried with 'source /etc/nova/openrc' and 'source /etc/platform/openrc' authentication, both got the same issue. Is this nova boot command still supported with containers? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Mon Feb 11 18:54:09 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 11 Feb 2019 13:54:09 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 141 - Failure! Message-ID: <2099069497.15.1549911250970.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 141 Status: Failure Timestamp: 20190211T165925Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T161653Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190211T161653Z DOCKER_BUILD_ID: jenkins-master-20190211T161653Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T161653Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190211T161653Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Feb 11 18:54:13 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 11 Feb 2019 13:54:13 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 135 - Still Failing! In-Reply-To: <457906627.9.1549864836334.JavaMail.javamailuser@localhost> References: <457906627.9.1549864836334.JavaMail.javamailuser@localhost> Message-ID: <202765377.18.1549911254637.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 135 Status: Still Failing Timestamp: 20190211T161653Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190211T161653Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From bruce.e.jones at intel.com Tue Feb 12 01:09:54 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 12 Feb 2019 01:09:54 +0000 Subject: [Starlingx-discuss] distro.openstack call this week Message-ID: <9A85D2917C58154C960D95352B22818BBFD2611B@fmsmsx123.amr.corp.intel.com> Agenda Review tracking sheet for the latest updates Checkpoint progress and discuss options -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Feb 12 01:10:01 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 12 Feb 2019 01:10:01 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Feb 12 01:22:10 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 12 Feb 2019 01:22:10 +0000 Subject: [Starlingx-discuss] [ Test ] meeting agenda - 02/12/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD72264@FMSMSX114.amr.corp.intel.com> Agenda for 02/12/2019 1. Release verification plan check - Ada - 15 min 2. Repo submissions - Numan - 15 min 3. Release notes generation (for testing repo) - Abraham/Cristopher - 15 min 4. Opens - all Regards Ada From kyle.oh95 at gmail.com Tue Feb 12 05:54:46 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Tue, 12 Feb 2019 14:54:46 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Message-ID: Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. *However I cannot access to the dashboard.* I used "2019-*Feb-08* 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, *I cannot find #1 service (oam-ip)*, and I think this is one of the main reasons. *And also I had a problem when I followed the installation instruction.* [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "*DataNetwork providernet-a could not be found*." So I googled and I figured out I should command $ *system datanetwork-add providernet-a vlan* first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Tue Feb 12 06:19:34 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 12 Feb 2019 06:19:34 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 2/13 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E842BE@SHSMSX104.ccr.corp.intel.com> Agenda for 2/13 meeting: 1. CentOS 7.6 upgrade, test status (Shuicheng, Ada/Numan) 2. Ceph upgrade status (Frank/Ovidiu, Changcheng) 3. Bug triage (Cindy) 4. Opens (All) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; 'Khalil, Ghada'; Sun, Austin; Somerville, Jim; 'Rowsell, Brent'; Liu, ZhipengS; Wold, Saul; starlingx-discuss at lists.starlingx.io; Shang, Dehao; Waheed, Numan; Troyer, Dean; Jones, Bruce E; Lin, Shuicheng; Zhu, Vivian; Hu, Yong Cc: Hu, Wei W; 'Seiler, Glenn'; Gomez, Juan P; 'Chen, Jacky'; Perez Rodriguez, Humberto I; 'Young, Ken'; Cobbley, David A; 'Waines, Greg'; Arce Moreno, Abraham; 'Eslimi, Dariush'; Lara, Cesar; Perez Carranza, Jose; 'Hellmann, Gil'; Armstrong, Robert H; Martinez Landa, Hayde; Martinez Monroy, Elio; Fang, Liang A Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 13, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From austin.sun at intel.com Tue Feb 12 08:02:41 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 12 Feb 2019 08:02:41 +0000 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: References: Message-ID: Hi Jaewook: 1) are you deploy on Virtual env or bare-metal ? 2) can you ping oam-ip ? and do you have any proxy setting in your web browser ? 3) for system datanetwork-add, please refer http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002788.html for more detail. Thanks. BR Austin Sun. From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, February 12, 2019 1:55 PM To: starlingx-discuss at lists.starlingx.io Cc: 오재욱 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. However I cannot access to the dashboard. I used "2019-Feb-08 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons. And also I had a problem when I followed the installation instruction. [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found." So I googled and I figured out I should command $ system datanetwork-add providernet-a vlan first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Tue Feb 12 14:00:12 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Tue, 12 Feb 2019 14:00:12 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F8621832F3@ALA-MBD.corp.ad.wrs.com> Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tao.Liu at windriver.com Tue Feb 12 15:49:14 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Tue, 12 Feb 2019 15:49:14 +0000 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDBD1EC@ALA-MBD.corp.ad.wrs.com> Hi Jaewook, In regard to *However I cannot access to the dashboard.* Per Feb 7 discussion (link below), the platform horizon UI is now available at http://:8080. http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003017.html If you use VirtualBox Nat Networking, you will need to update the port forwarding for dashboard per wiki. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards, Tao ------------------------------------------------------------------------------------------------------------------------------------ Message: 2 Date: Tue, 12 Feb 2019 14:54:46 +0900 From: Jaewook Oh To: starlingx-discuss at lists.starlingx.io Cc: 오재욱 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Message-ID: Content-Type: text/plain; charset="utf-8" Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. *However I cannot access to the dashboard.* I used "2019-*Feb-08* 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, *I cannot find #1 service (oam-ip)*, and I think this is one of the main reasons. *And also I had a problem when I followed the installation instruction.* [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "*DataNetwork providernet-a could not be found*." So I googled and I figured out I should command $ *system datanetwork-add providernet-a vlan* first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- 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 9, Issue 44 ************************************************ From Bin.Qian at windriver.com Tue Feb 12 16:09:19 2019 From: Bin.Qian at windriver.com (Qian, Bin) Date: Tue, 12 Feb 2019 16:09:19 +0000 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: References: , Message-ID: Hi, Jaewook, oam-ip service is not provisioned for an All-in-one simplex system. Looks like all services are running fine. You probably want to focus on the connectivity of the oam interface. Regards, Bin ________________________________ From: Sun, Austin [austin.sun at intel.com] Sent: Tuesday, February 12, 2019 12:02 AM To: Jaewook Oh; starlingx-discuss at lists.starlingx.io Cc: 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hi Jaewook: 1) are you deploy on Virtual env or bare-metal ? 2) can you ping oam-ip ? and do you have any proxy setting in your web browser ? 3) for system datanetwork-add, please refer http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002788.html for more detail. Thanks. BR Austin Sun. From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Tuesday, February 12, 2019 1:55 PM To: starlingx-discuss at lists.starlingx.io Cc: 오재욱 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. However I cannot access to the dashboard. I used "2019-Feb-08 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons. And also I had a problem when I followed the installation instruction. [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found." So I googled and I figured out I should command $ system datanetwork-add providernet-a vlan first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Tue Feb 12 17:06:20 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 12 Feb 2019 09:06:20 -0800 Subject: [Starlingx-discuss] Denver PTG Attending Teams Message-ID: Hello! The results are in! Here are the list of teams that are planning to attend the upcoming PTG in Denver, following the summit. Hopefully we are getting it to you soon enough to plan travel. If you haven't already registered yet, you can do that here[1]. If you haven't booked your hotel yet, please please please use our hotel block here[2]. ----------------------------------------- Pilot Projects: - Airship - Kata Containers - StarlingX OpenStack Components: - - Barbican - Charms - Cinder - Cyborg - Docs/I18n - Glance - Heat - Horizon - Infrastructure - Ironic - Keystone - LOCI - Manila - Monasca - Neutron - Nova - Octavia - OpenStack Ansible - OpenStack QA - OpenStackClient - Oslo - Placement - Release Management - Requirements - Swift - Tacker - TripleO - Vitrage - OpenStack-Helm SIGs: - API-SIG - AutoScaling SIG - Edge Computing Group - Extended Maintenance SIG - First Contact SIG - Interop WG/RefStack - K8s SIG - Scientific SIG - Security SIG - Self-healing SIG ------------------------------------------ If your team is missing from this list, its because I didn't get a 'yes' response from your PTL/Chair/Contact Person. Have them contact me and we can try to work something out. Now that we have this list, we will start putting together a draft schedule. See you all in Denver! -Kendall (diablo_rojo) [1] https://www.eventbrite.com/e/open-infrastructure-summit-project-teams-gathering-tickets-52606153421 [2] https://www.hyatt.com/en-US/group-booking/DENCC/G-FNTE -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Tue Feb 12 18:26:24 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 12 Feb 2019 18:26:24 +0000 Subject: [Starlingx-discuss] Docs mega spec up for review In-Reply-To: <9A85D2917C58154C960D95352B22818BBFD1D64E@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BBFD1D64E@fmsmsx123.amr.corp.intel.com> Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC09FE60D@ALA-MBD.corp.ad.wrs.com> Hi Bruce, To help with the documentation effort, we've dug back and found some onboarding documents that can be used to as seed documents (topics like Networking, Security, Storage, etc). We've noted in each what needs to be changed to bring it up to date for StarlingX. I've put them up in the shared StarlingX folder: https://drive.google.com/open?id=1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY Another great source of input for these documents would be the SDL documents that were created previously. Bill... From: Jones, Bruce E Sent: Thursday, February 7, 2019 4:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docs mega spec up for review The Docs team has been working on a spec for an overhaul of our formal project documentation, and the spec has been posted for review. You can find it at https://review.openstack.org/#/c/635641. Feedback and comments graciously accepted! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Tue Feb 12 20:36:13 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Tue, 12 Feb 2019 20:36:13 +0000 Subject: [Starlingx-discuss] [multiOS][meetings] MulitOS team meeting minutes 2/11/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105EA368@fmsmsx104.amr.corp.intel.com> MulitOS team meeting Agenda for 2/11/2019 - Presentation about separation of monolithic build - Continue Discussion on uploaded specs around MultiOS Multi-OS overview specification - https://review.openstack.org/#/c/619801/ Reorganize Flock Services Source Code repositories - https://review.openstack.org/#/c/631288/ Example of repo based on this spec - https://github.com/starlingx-staging/stx-packaging - MultiOS build system - Opens Notes: Presentation about separation of monolithic build - Ken to share these slides, high level presentation about the multiOS challenge and some implementation details. Topics covered: Separate the OS build from the rest of StarlingX specific services and artifacts, build only specific elements and the non-OS piece. Continue discussion on uploaded specs around MultiOS - -Still no spec around the generation of deb. files and the generation of Ubuntu version of StarlingX There has been some integration and testing on this but need to integrate this as part of a new spec We might want to do the same for newer versions of CentOS This team has to evaluate the option to build each component of the flock services and their 3rd party components and ship those independently -Still no clear scope for multiOS activities for May release - we need to clearly state what are we trying to achieve for next release on the multiOS space. There are some activities that are happening around the cleanup of mocks and dependencies of spec files We are targeting those to be included as part of laying the ground work for multiOS The team is on hold with a few tasks regarding directory structure, adding repos and build system while the meta spec is approved to continue with some of these "ground work tasks" - For may release the multiOS efforts should be focused around these main topics Source code reorganization Directory Layout Dependency cleanup We are waiting for these topics to be described in formal specs so we can start assessing the implementation details and discussing the wins around these for the project AR - start writing the specs only focused on may release topics AR - Come back with an updated proposal AR - Need to start working on the next level of multiOS and details around the implementation so we can discuss them MultiOS build system - this topic was discussed along with the specs discussion, although, I wanted to restate that there are no changes planned to current build system, to support other OS we will bring up tooling and infrastructure native to new supported OS, that and the ground work will set us up for supporting this multiOS effort. Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Feb 12 20:55:07 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 12 Feb 2019 20:55:07 +0000 Subject: [Starlingx-discuss] Docs mega spec up for review In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC09FE60D@ALA-MBD.corp.ad.wrs.com> References: <9A85D2917C58154C960D95352B22818BBFD1D64E@fmsmsx123.amr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC09FE60D@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BBFD26959@fmsmsx123.amr.corp.intel.com> Wow, thank you ! This is very cool. Michael, can we please put this topic on the Docs team agenda for this week? brucej From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, February 12, 2019 10:26 AM To: Jones, Bruce E ; starlingx-discuss at lists.starlingx.io Subject: RE: Docs mega spec up for review Hi Bruce, To help with the documentation effort, we've dug back and found some onboarding documents that can be used to as seed documents (topics like Networking, Security, Storage, etc). We've noted in each what needs to be changed to bring it up to date for StarlingX. I've put them up in the shared StarlingX folder: https://drive.google.com/open?id=1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY Another great source of input for these documents would be the SDL documents that were created previously. Bill... From: Jones, Bruce E > Sent: Thursday, February 7, 2019 4:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docs mega spec up for review The Docs team has been working on a spec for an overhaul of our formal project documentation, and the spec has been posted for review. You can find it at https://review.openstack.org/#/c/635641. Feedback and comments graciously accepted! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Tue Feb 12 21:08:21 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Tue, 12 Feb 2019 21:08:21 +0000 Subject: [Starlingx-discuss] Docs mega spec up for review In-Reply-To: <9A85D2917C58154C960D95352B22818BBFD26959@fmsmsx123.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BBFD1D64E@fmsmsx123.amr.corp.intel.com> <586E8B730EA0DA4A9D6A80A10E486BC09FE60D@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BBFD26959@fmsmsx123.amr.corp.intel.com> Message-ID: <3808363B39586544A6839C76CF81445EA1AB4C41@ORSMSX104.amr.corp.intel.com> Fantastic! Yes, this is on the agenda. From: Jones, Bruce E Sent: Tuesday, February 12, 2019 1:55 PM To: Zvonar, Bill ; Tullis, Michael L Cc: starlingx-discuss at lists.starlingx.io Subject: RE: Docs mega spec up for review Wow, thank you ! This is very cool. Michael, can we please put this topic on the Docs team agenda for this week? brucej From: Zvonar, Bill [mailto:Bill.Zvonar at windriver.com] Sent: Tuesday, February 12, 2019 10:26 AM To: Jones, Bruce E >; starlingx-discuss at lists.starlingx.io Subject: RE: Docs mega spec up for review Hi Bruce, To help with the documentation effort, we've dug back and found some onboarding documents that can be used to as seed documents (topics like Networking, Security, Storage, etc). We've noted in each what needs to be changed to bring it up to date for StarlingX. I've put them up in the shared StarlingX folder: https://drive.google.com/open?id=1YlAlWT7FtSFNyYDdJ2hbFFW4aNGQXCHY Another great source of input for these documents would be the SDL documents that were created previously. Bill... From: Jones, Bruce E > Sent: Thursday, February 7, 2019 4:52 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Docs mega spec up for review The Docs team has been working on a spec for an overhaul of our formal project documentation, and the spec has been posted for review. You can find it at https://review.openstack.org/#/c/635641. Feedback and comments graciously accepted! brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Feb 12 23:07:15 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 12 Feb 2019 23:07:15 +0000 Subject: [Starlingx-discuss] [ Test ] meeting minutes - 02/12/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD72C2C@FMSMSX114.amr.corp.intel.com> Notes from 02/12/2019 Attendees: Abraham, Fernando, Maria, Cristopher, Elio, JC, JP, Numan, Victor, Ada, Ghada , Bruce, Richo 1. Release verification plan check - Ada - 15 min - Performance testing - define our set of initial metrics and take our baseline, that would be our May release. - Victor checking OPNFV suites. - Have OPNFV as the first set of metrics for the May release and continue growing the performance framework. Communicate this into the community meeting tomorrow. + Spec ready: 03/08 + Metrics for May release defined by: 02/28 + First set of metrics taken: 03/15 - For automation - define which test cases should be automated first. Ada and Numan to work on it. 2. Repo submissions - Numan - 15 min - Opt 1 - each test case as a single file - Opt 2 - all the test cases for a domain, in a single file - Opt 3 - a single file for each sub-domain (areas). For example: nova_livemigration in one file. - Numan to send the proposal for this one. Looks more manageable. Send your comments by EOW. + https://drive.google.com/file/d/1EJnQrz-JSafVW9ZNYBbGdo0TgwcrfI9w/view?usp=sharing 3. Release notes generation (for testing repo) - Abraham/Cristopher - 15 min - Presentation: https://drive.google.com/file/d/14DNcnISH1hUfb36kUruQhzutJnGRKY7f/view?usp=sharing - doc and releasenotes are populated automatically with every commit. - Do we need release notes for the test cases? Abraham to help us checking what other teams related to OpenStack are doing regarding release notes for tests. 4. Opens - all N/A > -----Original Message----- > From: Cabrales, Ada [mailto:ada.cabrales at intel.com] > Sent: Monday, February 11, 2019 7:22 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] [ Test ] meeting agenda - 02/12/2019 > > Agenda for 02/12/2019 > > 1. Release verification plan check - Ada - 15 min > > 2. Repo submissions - Numan - 15 min > > 3. Release notes generation (for testing repo) - Abraham/Cristopher - 15 min > > 4. Opens - all > > > Regards > Ada > > _______________________________________________ > 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 Wed Feb 13 00:03:21 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 13 Feb 2019 00:03:21 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190212 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9A431@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-12 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 22 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtroyer at gmail.com Wed Feb 13 00:31:05 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Tue, 12 Feb 2019 18:31:05 -0600 Subject: [Starlingx-discuss] [Container] Is 'nova boot' command still supported? In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C96F0C@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C96F0C@FMSMSX108.amr.corp.intel.com> Message-ID: On Mon, Feb 11, 2019 at 10:46 AM Alonso, Juan Carlos wrote: > Openstack commands work correctly but nova, glance, cinder are asking for user name, user id, project name, tenant id, etc.. I think some this parameters are defined on /etc/openstack/clouds.yaml, right? > Does clouds.yaml need extra parameters? A modern python-novaclient (and friends) has support for clouds.yaml, the pike versions currently in the build do not. Aside from Python dependency issues you can use modern CLIs against old API servers. (Also excepting any WRS changes to the clients, there are a few.) > That’s why also I am asking if nova, glance, cinder, etc commands won’t be supported? In order to update to openstack command. Are there things you need to use the old clients for that OSC does not support? dt -- Dean Troyer dtroyer at gmail.com From sgw at linux.intel.com Wed Feb 13 05:25:23 2019 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 12 Feb 2019 21:25:23 -0800 Subject: [Starlingx-discuss] [TSC] Request TSC Members please review and comment on MultiOS Specs Message-ID: <77c29f01-10e8-3690-663c-dad3042f4861@linux.intel.com> TSC Members, There have been some additional changes and updates to the MultiOS related specifications [0], I would request that TSC members review these specifications ahead of Thursday's TSC Meeting so we can have some discussion on these in order to move them forward. Thanks for your contributions Sau! [0] https://review.openstack.org/#/q/topic:multi-os From marcel at schaible-consulting.de Wed Feb 13 11:56:44 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 12:56:44 +0100 (CET) Subject: [Starlingx-discuss] Build for Duplex Configuration In-Reply-To: References: Message-ID: <601521071.413736.1550059004249@communicator.strato.com> Hi, since I am still striggling with the installation of a duplex configuration: Which build do you currently recommend for testing? Thanks Marcel From cindy.xie at intel.com Wed Feb 13 14:31:54 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 13 Feb 2019 14:31:54 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 2/13 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E862A8@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 2/13 meeting: 1. CentOS 7.6 upgrade, test status (Shuicheng, Ada/Numan) 2 bugs reported, and 2 fixes merged into f/centOS7.6; Branch rebase from master to feature branch. New test images built from f/CentOS7.6 has been provided. One more test failure reported from GDC: >>> 1 Test Case Failed Reject changing interface MTU size to values smaller than MTU of provider network / The system accepts MTU values smaller than MTU of provider network. Details to be clarified w/ test reproduce steps; and we need to check if the same issue can be seen in the latest master. Numan is taking day off today. They already have one image today and should be able to re-start the testing, #1814360 has been resolved which were block the WR testing. stx-upstream has several conficts btw f/Stein and f/CentOS76: 6 packages in stx-upstream being upgraded. 4 of them were not changed in Stein branch; 2 of them were changed from Pike to Stein. Python-heatclient and Python-openStack-Client. The proposed solution is to take the components from f/Stein (and it will land into Master earlier than Cent7.6). Still plan to have feature branch merged into Master on Feb 22nd, with risk on test results. 2. Ceph upgrade status (Frank, Changcheng) Ovidiu successed built the ISO and installed the storage nodes not yet provision the OSD yet. Daniel is debugging the OSD issue by reviewing the patches. Ovidiu went through all commit and have high level view for what needs to be chagned. Will summarize that for Changcheng and will meet w/ Changcheng, Vivian and Yong for the recommendations for the next steps. Suggestion to split the work btw the two teams. Yong: may have some hints regarding the issues of create OSD. Will work w/ Ovidiu offline to share the workaround. Rough plan: good idea for the remaining tasks, will provide ETA after the meeting. 3. Bug triage (Cindy) #1814595: to be assigned #1814360 patch merged to f/CentOS76 #1814345 assigned to Haitao #1814335 patch merged to f/CentOS76 4. Opens (All) None -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: 'Khalil, Ghada'; Sun, Austin; Somerville, Jim; 'Rowsell, Brent'; Liu, ZhipengS; Wold, Saul; starlingx-discuss at lists.starlingx.io; Shang, Dehao; Waheed, Numan; Troyer, Dean; Jones, Bruce E; Lin, Shuicheng; Zhu, Vivian; Hu, Yong; Xie, Cindy; 'Khalil, Ghada'; Somerville, Jim; 'Rowsell, Brent'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Hu, Wei W; 'Seiler, Glenn'; Gomez, Juan P; 'Chen, Jacky'; Perez Rodriguez, Humberto I; 'Young, Ken'; Cobbley, David A; 'Waines, Greg'; Arce Moreno, Abraham; 'Eslimi, Dariush'; Lara, Cesar; Perez Carranza, Jose; 'Hellmann, Gil'; Armstrong, Robert H; Martinez Landa, Hayde; Martinez Monroy, Elio; Fang, Liang A; 'Seiler, Glenn'; 'Chen, Jacky'; Perez Rodriguez, Humberto I; 'Young, Ken'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Hellmann, Gil'; Poncea, Ovidiu Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 13, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From marcel at schaible-consulting.de Wed Feb 13 15:28:24 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 16:28:24 +0100 (CET) Subject: [Starlingx-discuss] neutron: cannot create a providernet Message-ID: <1317027184.431577.1550071704349@communicator.strato.com> Hi, I am getting the following error when initially creating a providernet: DataNetwork providernet-a could not be found. I am following the installation guide from here: https://docs.starlingx.io/installation_guide/duplex.html#duplex Any idea is welcome! Thanks Marcel ---------------------------------------- The following configuration will be applied: System Configuration -------------------- Time Zone: Europe/Berlin System mode: duplex PXEBoot Network Configuration ----------------------------- Separate PXEBoot network not configured PXEBoot Controller floating hostname: pxecontroller Management Network Configuration -------------------------------- Management interface name: enp9s20f7 Management interface: enp9s20f7 Management interface MTU: 1500 Management subnet: 172.27.1.0/24 Controller floating address: 172.27.1.2 Controller 0 address: 172.27.1.3 Controller 1 address: 172.27.1.4 NFS Management Address 1: 172.27.1.5 NFS Management Address 2: 172.27.1.6 Controller floating hostname: controller Controller hostname prefix: controller- OAM Controller floating hostname: oamcontroller Dynamic IP address allocation is selected Management multicast subnet: 239.1.1.0/28 Infrastructure Network Configuration ------------------------------------ Infrastructure interface not configured External OAM Network Configuration ---------------------------------- External OAM interface name: bond0 External OAM interface: bond0 External OAM interface MTU: 1500 External OAM ae member 0: ens1f1 External OAM ae member 1: ens1f3 External OAM ae policy : active-backup External OAM subnet: 10.62.150.0/24 External OAM gateway address: 10.62.150.1 External OAM floating address: 10.62.150.211 External OAM 0 address: 10.62.150.212 External OAM 1 address: 10.62.150.213 Apply the above configuration? [y/n]: y Applying configuration (this will take several minutes): 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... DONE 03/08: Persisting local configuration ... DONE 04/08: Populating initial system inventory ... DONE 05/08: Creating system configuration ... DONE 06/08: Applying controller manifest ... DONE 07/08: Finalize controller configuration ... DONE 08/08: Waiting for service activation ... DONE Configuration was applied Please complete any out of service commissioning steps with system commands and unlock controller to proceed. localhost:~# source /etc/nova/openrc [root at localhost ~(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Created a new providernet: +------------------+--------------------------------------+ | Field | Value | +------------------+--------------------------------------+ | description | | | id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | | mtu | 1500 | | name | providernet-a | | ranges | | | status | DOWN | | type | vlan | | vlan_transparent | False | +------------------+--------------------------------------+ [root at localhost ~(keystone_admin)]# neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Created a new providernet_range: +------------------+--------------------------------------+ | Field | Value | +------------------+--------------------------------------+ | description | | | id | ce8bba6a-5bb0-4ddb-b430-bd216912a5c6 | | maximum | 400 | | minimum | 100 | | name | providernet-a-range1 | | project_id | 4f59503b008e49be9f43e393bf89a19e | | providernet_id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | | providernet_name | providernet-a | | providernet_type | vlan | | shared | False | | tenant_id | 4f59503b008e49be9f43e393bf89a19e | +------------------+--------------------------------------+ [root at localhost ~(keystone_admin)]# system host-if-list -a controller-0 +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | data networks | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ | 04665f98-8318-4855-a591-1307231a40b3 | bond0 | platform | ae | None | [] | [u'ens1f1', u'ens1f3'] | [] | MTU=1500,AE_MODE=active_standby | [] | | 2a6b70cb-53ad-43c3-adc7-b92c4c44470d | enp9s20f6 | None | ethernet | None | [u'enp9s20f6'] | [] | [] | MTU=1500 | [] | | 2dcbe277-530e-400c-b156-43545b4507c8 | ens1f1 | None | ethernet | None | [u'ens1f1'] | [] | [u'bond0'] | MTU=1500 | [] | | 3acd41aa-aeb0-400c-86ba-79f0fdb24829 | ens1f3 | None | ethernet | None | [u'ens1f3'] | [] | [u'bond0'] | MTU=1500 | [] | | 86b8867a-2aee-4cb9-a04a-7587ff8d833d | enp3s0f0 | None | ethernet | None | [u'enp3s0f0'] | [] | [] | MTU=1500 | [] | | ce78e71f-4300-4a6b-ae0a-43e3139a5515 | enp3s0f1 | None | ethernet | None | [u'enp3s0f1'] | [] | [] | MTU=1500 | [] | | d3e101a0-a873-4c76-b7b5-83368626acd4 | enp9s21f0 | None | ethernet | None | [u'enp9s21f0'] | [] | [] | MTU=1500 | [] | | e93f1d26-e6ee-4c7f-84ef-8b68e312ef16 | enp9s21f1 | None | ethernet | None | [u'enp9s21f1'] | [] | [] | MTU=1500 | [] | | ed1b47c8-0311-4e39-8840-9931c69c147e | ens1f0 | None | ethernet | None | [u'ens1f0'] | [] | [] | MTU=1500 | [] | | ee4ce037-1408-4695-b05d-e5491f30e274 | enp9s20f7 | platform | ethernet | None | [u'enp9s20f7'] | [] | [] | MTU=1500 | [] | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ [root at localhost ~(keystone_admin)]# neutron providernet-list neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ | id | name | type | mtu | ranges | +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | providernet-a | vlan | 1500 | {"minimum": 100, "maximum": 400, "name": "providernet-a-range1"} | +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ enp9s21f1 -p providernet-a_admin)]# system host-if-modify -c data controller-0 DataNetwork providernet-a could not be found. [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ec:9e:cd:1f:7e:b0 brd ff:ff:ff:ff:ff:ff 3: ens1f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:60 brd ff:ff:ff:ff:ff:ff 4: ens1f1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 5: enp3s0f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ec:9e:cd:1f:7e:b1 brd ff:ff:ff:ff:ff:ff 6: ens1f3: mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 7: enp9s20f6: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:15 brd ff:ff:ff:ff:ff:ff 8: enp9s20f7: mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 02:01:00:10:02:15 brd ff:ff:ff:ff:ff:ff inet 172.27.1.3/24 brd 172.27.1.255 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 169.254.202.2/24 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.2/24 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.5/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.6/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet6 fe80::1:ff:fe10:215/64 scope link valid_lft forever preferred_lft forever 9: enp9s21f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:16 brd ff:ff:ff:ff:ff:ff 10: enp9s21f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:02:16 brd ff:ff:ff:ff:ff:ff 11: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff inet 10.62.150.211/24 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::b696:91ff:fe1a:161/64 scope link valid_lft forever preferred_lft forever [root at localhost ~(keystone_admin)]# From Brent.Rowsell at windriver.com Wed Feb 13 15:35:39 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 13 Feb 2019 15:35:39 +0000 Subject: [Starlingx-discuss] neutron: cannot create a providernet In-Reply-To: <1317027184.431577.1550071704349@communicator.strato.com> References: <1317027184.431577.1550071704349@communicator.strato.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3D1B7C@ALA-MBD.corp.ad.wrs.com> Hi, This has been changed. See the following mail post http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002788.html Brent -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 10:28 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] neutron: cannot create a providernet Hi, I am getting the following error when initially creating a providernet: DataNetwork providernet-a could not be found. I am following the installation guide from here: https://docs.starlingx.io/installation_guide/duplex.html#duplex Any idea is welcome! Thanks Marcel ---------------------------------------- The following configuration will be applied: System Configuration -------------------- Time Zone: Europe/Berlin System mode: duplex PXEBoot Network Configuration ----------------------------- Separate PXEBoot network not configured PXEBoot Controller floating hostname: pxecontroller Management Network Configuration -------------------------------- Management interface name: enp9s20f7 Management interface: enp9s20f7 Management interface MTU: 1500 Management subnet: 172.27.1.0/24 Controller floating address: 172.27.1.2 Controller 0 address: 172.27.1.3 Controller 1 address: 172.27.1.4 NFS Management Address 1: 172.27.1.5 NFS Management Address 2: 172.27.1.6 Controller floating hostname: controller Controller hostname prefix: controller- OAM Controller floating hostname: oamcontroller Dynamic IP address allocation is selected Management multicast subnet: 239.1.1.0/28 Infrastructure Network Configuration ------------------------------------ Infrastructure interface not configured External OAM Network Configuration ---------------------------------- External OAM interface name: bond0 External OAM interface: bond0 External OAM interface MTU: 1500 External OAM ae member 0: ens1f1 External OAM ae member 1: ens1f3 External OAM ae policy : active-backup External OAM subnet: 10.62.150.0/24 External OAM gateway address: 10.62.150.1 External OAM floating address: 10.62.150.211 External OAM 0 address: 10.62.150.212 External OAM 1 address: 10.62.150.213 Apply the above configuration? [y/n]: y Applying configuration (this will take several minutes): 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... DONE 03/08: Persisting local configuration ... DONE 04/08: Populating initial system inventory ... DONE 05/08: Creating system configuration ... DONE 06/08: Applying controller manifest ... DONE 07/08: Finalize controller configuration ... DONE 08/08: Waiting for service activation ... DONE Configuration was applied Please complete any out of service commissioning steps with system commands and unlock controller to proceed. localhost:~# source /etc/nova/openrc [root at localhost ~(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Created a new providernet: +------------------+--------------------------------------+ | Field | Value | +------------------+--------------------------------------+ | description | | | id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | | mtu | 1500 | | name | providernet-a | | ranges | | | status | DOWN | | type | vlan | | vlan_transparent | False | +------------------+--------------------------------------+ [root at localhost ~(keystone_admin)]# neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Created a new providernet_range: +------------------+--------------------------------------+ | Field | Value | +------------------+--------------------------------------+ | description | | | id | ce8bba6a-5bb0-4ddb-b430-bd216912a5c6 | | maximum | 400 | | minimum | 100 | | name | providernet-a-range1 | | project_id | 4f59503b008e49be9f43e393bf89a19e | | providernet_id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | | providernet_name | providernet-a | | providernet_type | vlan | | shared | False | | tenant_id | 4f59503b008e49be9f43e393bf89a19e | +------------------+--------------------------------------+ [root at localhost ~(keystone_admin)]# system host-if-list -a controller-0 +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | data networks | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ | 04665f98-8318-4855-a591-1307231a40b3 | bond0 | platform | ae | None | [] | [u'ens1f1', u'ens1f3'] | [] | MTU=1500,AE_MODE=active_standby | [] | | 2a6b70cb-53ad-43c3-adc7-b92c4c44470d | enp9s20f6 | None | ethernet | None | [u'enp9s20f6'] | [] | [] | MTU=1500 | [] | | 2dcbe277-530e-400c-b156-43545b4507c8 | ens1f1 | None | ethernet | None | [u'ens1f1'] | [] | [u'bond0'] | MTU=1500 | [] | | 3acd41aa-aeb0-400c-86ba-79f0fdb24829 | ens1f3 | None | ethernet | None | [u'ens1f3'] | [] | [u'bond0'] | MTU=1500 | [] | | 86b8867a-2aee-4cb9-a04a-7587ff8d833d | enp3s0f0 | None | ethernet | None | [u'enp3s0f0'] | [] | [] | MTU=1500 | [] | | ce78e71f-4300-4a6b-ae0a-43e3139a5515 | enp3s0f1 | None | ethernet | None | [u'enp3s0f1'] | [] | [] | MTU=1500 | [] | | d3e101a0-a873-4c76-b7b5-83368626acd4 | enp9s21f0 | None | ethernet | None | [u'enp9s21f0'] | [] | [] | MTU=1500 | [] | | e93f1d26-e6ee-4c7f-84ef-8b68e312ef16 | enp9s21f1 | None | ethernet | None | [u'enp9s21f1'] | [] | [] | MTU=1500 | [] | | ed1b47c8-0311-4e39-8840-9931c69c147e | ens1f0 | None | ethernet | None | [u'ens1f0'] | [] | [] | MTU=1500 | [] | | ee4ce037-1408-4695-b05d-e5491f30e274 | enp9s20f7 | platform | ethernet | None | [u'enp9s20f7'] | [] | [] | MTU=1500 | [] | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ [root at localhost ~(keystone_admin)]# neutron providernet-list neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ | id | name | type | mtu | ranges | +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | providernet-a | vlan | 1500 | | {"minimum": 100, "maximum": 400, "name": "providernet-a-range1"} | +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ enp9s21f1 -p providernet-a_admin)]# system host-if-modify -c data controller-0 DataNetwork providernet-a could not be found. [root at localhost ~(keystone_admin)]# [root at localhost ~(keystone_admin)]# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ec:9e:cd:1f:7e:b0 brd ff:ff:ff:ff:ff:ff 3: ens1f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:60 brd ff:ff:ff:ff:ff:ff 4: ens1f1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 5: enp3s0f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ec:9e:cd:1f:7e:b1 brd ff:ff:ff:ff:ff:ff 6: ens1f3: mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 7: enp9s20f6: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:15 brd ff:ff:ff:ff:ff:ff 8: enp9s20f7: mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 02:01:00:10:02:15 brd ff:ff:ff:ff:ff:ff inet 172.27.1.3/24 brd 172.27.1.255 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 169.254.202.2/24 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.2/24 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.5/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.6/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet6 fe80::1:ff:fe10:215/64 scope link valid_lft forever preferred_lft forever 9: enp9s21f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:16 brd ff:ff:ff:ff:ff:ff 10: enp9s21f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:02:16 brd ff:ff:ff:ff:ff:ff 11: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff inet 10.62.150.211/24 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::b696:91ff:fe1a:161/64 scope link valid_lft forever preferred_lft forever [root at localhost ~(keystone_admin)]# _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Wed Feb 13 16:10:01 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 17:10:01 +0100 (CET) Subject: [Starlingx-discuss] neutron: cannot create a providernet In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3D1B7C@ALA-MBD.corp.ad.wrs.com> References: <1317027184.431577.1550071704349@communicator.strato.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D1B7C@ALA-MBD.corp.ad.wrs.com> Message-ID: <365038342.434792.1550074201286@communicator.strato.com> Thanks Brent for your quick response. Before going again thru the disk configuration part, is this looking correct: [root at controller-0 ~(keystone_admin)]# system datanetwork-list +--------------------------------------+---------------+----------+------+ | uuid | name | network_ | mtu | | | | type | | +--------------------------------------+---------------+----------+------+ | 4cb64a85-801e-4a30-aa10-0a073357b81e | providernet-a | vlan | 1500 | +--------------------------------------+---------------+----------+------+ [root at controller-0 ~(keystone_admin)]# system datanetwork-show 4cb64a85-801e-4a3... +--------------+--------------------------------------+ | Property | Value | +--------------+--------------------------------------+ | id | 2 | | uuid | 4cb64a85-801e-4a30-aa10-0a073357b81e | | name | providernet-a | | network_type | vlan | | mtu | 1500 | | description | None | +--------------+--------------------------------------+ Thanks Marcel > "Rowsell, Brent" hat am 13. Februar 2019 um 16:35 geschrieben: > > > Hi, > > This has been changed. See the following mail post > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-January/002788.html > > Brent > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 10:28 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] neutron: cannot create a providernet > > Hi, > > I am getting the following error when initially creating a providernet: > > DataNetwork providernet-a could not be found. > > I am following the installation guide from here: > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > Any idea is welcome! > > Thanks > > Marcel > > ---------------------------------------- > The following configuration will be applied: > > System Configuration > -------------------- > Time Zone: Europe/Berlin > System mode: duplex > > PXEBoot Network Configuration > ----------------------------- > Separate PXEBoot network not configured > PXEBoot Controller floating hostname: pxecontroller > > Management Network Configuration > -------------------------------- > Management interface name: enp9s20f7 > Management interface: enp9s20f7 > Management interface MTU: 1500 > Management subnet: 172.27.1.0/24 > Controller floating address: 172.27.1.2 > Controller 0 address: 172.27.1.3 > Controller 1 address: 172.27.1.4 > NFS Management Address 1: 172.27.1.5 > NFS Management Address 2: 172.27.1.6 > Controller floating hostname: controller Controller hostname prefix: controller- OAM Controller floating hostname: oamcontroller Dynamic IP address allocation is selected Management multicast subnet: 239.1.1.0/28 > > Infrastructure Network Configuration > ------------------------------------ > Infrastructure interface not configured > > External OAM Network Configuration > ---------------------------------- > External OAM interface name: bond0 > External OAM interface: bond0 > External OAM interface MTU: 1500 > External OAM ae member 0: ens1f1 > External OAM ae member 1: ens1f3 > External OAM ae policy : active-backup > External OAM subnet: 10.62.150.0/24 > External OAM gateway address: 10.62.150.1 External OAM floating address: 10.62.150.211 External OAM 0 address: 10.62.150.212 External OAM 1 address: 10.62.150.213 > > Apply the above configuration? [y/n]: y > > Applying configuration (this will take several minutes): > > 01/08: Creating bootstrap configuration ... DONE > 02/08: Applying bootstrap manifest ... DONE > 03/08: Persisting local configuration ... DONE > 04/08: Populating initial system inventory ... DONE > 05/08: Creating system configuration ... DONE > 06/08: Applying controller manifest ... DONE > 07/08: Finalize controller configuration ... DONE > 08/08: Waiting for service activation ... DONE > > Configuration was applied > > Please complete any out of service commissioning steps with system commands and unlock controller to proceed. > localhost:~# source /etc/nova/openrc > [root at localhost ~(keystone_admin)]# neutron providernet-create providernet-a --type=vlan neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. > Created a new providernet: > +------------------+--------------------------------------+ > | Field | Value | > +------------------+--------------------------------------+ > | description | | > | id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | > | mtu | 1500 | > | name | providernet-a | > | ranges | | > | status | DOWN | > | type | vlan | > | vlan_transparent | False | > +------------------+--------------------------------------+ > [root at localhost ~(keystone_admin)]# neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. > Created a new providernet_range: > +------------------+--------------------------------------+ > | Field | Value | > +------------------+--------------------------------------+ > | description | | > | id | ce8bba6a-5bb0-4ddb-b430-bd216912a5c6 | > | maximum | 400 | > | minimum | 100 | > | name | providernet-a-range1 | > | project_id | 4f59503b008e49be9f43e393bf89a19e | > | providernet_id | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | > | providernet_name | providernet-a | > | providernet_type | vlan | > | shared | False | > | tenant_id | 4f59503b008e49be9f43e393bf89a19e | > +------------------+--------------------------------------+ > [root at localhost ~(keystone_admin)]# system host-if-list -a controller-0 > +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ > | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | data networks | > +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ > | 04665f98-8318-4855-a591-1307231a40b3 | bond0 | platform | ae | None | [] | [u'ens1f1', u'ens1f3'] | [] | MTU=1500,AE_MODE=active_standby | [] | > | 2a6b70cb-53ad-43c3-adc7-b92c4c44470d | enp9s20f6 | None | ethernet | None | [u'enp9s20f6'] | [] | [] | MTU=1500 | [] | > | 2dcbe277-530e-400c-b156-43545b4507c8 | ens1f1 | None | ethernet | None | [u'ens1f1'] | [] | [u'bond0'] | MTU=1500 | [] | > | 3acd41aa-aeb0-400c-86ba-79f0fdb24829 | ens1f3 | None | ethernet | None | [u'ens1f3'] | [] | [u'bond0'] | MTU=1500 | [] | > | 86b8867a-2aee-4cb9-a04a-7587ff8d833d | enp3s0f0 | None | ethernet | None | [u'enp3s0f0'] | [] | [] | MTU=1500 | [] | > | ce78e71f-4300-4a6b-ae0a-43e3139a5515 | enp3s0f1 | None | ethernet | None | [u'enp3s0f1'] | [] | [] | MTU=1500 | [] | > | d3e101a0-a873-4c76-b7b5-83368626acd4 | enp9s21f0 | None | ethernet | None | [u'enp9s21f0'] | [] | [] | MTU=1500 | [] | > | e93f1d26-e6ee-4c7f-84ef-8b68e312ef16 | enp9s21f1 | None | ethernet | None | [u'enp9s21f1'] | [] | [] | MTU=1500 | [] | > | ed1b47c8-0311-4e39-8840-9931c69c147e | ens1f0 | None | ethernet | None | [u'ens1f0'] | [] | [] | MTU=1500 | [] | > | ee4ce037-1408-4695-b05d-e5491f30e274 | enp9s20f7 | platform | ethernet | None | [u'enp9s20f7'] | [] | [] | MTU=1500 | [] | > +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+---------------+ > [root at localhost ~(keystone_admin)]# neutron providernet-list neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. > +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ > | id | name | type | mtu | ranges | > +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ > | e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | providernet-a | vlan | 1500 | > | {"minimum": 100, "maximum": 400, "name": "providernet-a-range1"} | > +--------------------------------------+---------------+------+------+------------------------------------------------------------------+ > enp9s21f1 -p providernet-a_admin)]# system host-if-modify -c data controller-0 DataNetwork providernet-a could not be found. > [root at localhost ~(keystone_admin)]# > [root at localhost ~(keystone_admin)]# ip addr > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp3s0f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether ec:9e:cd:1f:7e:b0 brd ff:ff:ff:ff:ff:ff > 3: ens1f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether b4:96:91:1a:01:60 brd ff:ff:ff:ff:ff:ff > 4: ens1f1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 > link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff > 5: enp3s0f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether ec:9e:cd:1f:7e:b1 brd ff:ff:ff:ff:ff:ff > 6: ens1f3: mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000 > link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff > 7: enp9s20f6: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether 02:01:00:10:01:15 brd ff:ff:ff:ff:ff:ff > 8: enp9s20f7: mtu 1500 qdisc htb state UP group default qlen 1000 > link/ether 02:01:00:10:02:15 brd ff:ff:ff:ff:ff:ff > inet 172.27.1.3/24 brd 172.27.1.255 scope global enp9s20f7 > valid_lft forever preferred_lft forever > inet 169.254.202.2/24 scope global enp9s20f7 > valid_lft forever preferred_lft forever > inet 172.27.1.2/24 scope global secondary enp9s20f7 > valid_lft forever preferred_lft forever > inet 172.27.1.5/24 brd 172.27.1.255 scope global secondary enp9s20f7 > valid_lft forever preferred_lft forever > inet 172.27.1.6/24 brd 172.27.1.255 scope global secondary enp9s20f7 > valid_lft forever preferred_lft forever > inet6 fe80::1:ff:fe10:215/64 scope link > valid_lft forever preferred_lft forever > 9: enp9s21f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether 02:01:00:10:01:16 brd ff:ff:ff:ff:ff:ff > 10: enp9s21f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 > link/ether 02:01:00:10:02:16 brd ff:ff:ff:ff:ff:ff > 11: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 > link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff > inet 10.62.150.211/24 scope global bond0 > valid_lft forever preferred_lft forever > inet6 fe80::b696:91ff:fe1a:161/64 scope link > valid_lft forever preferred_lft forever [root at localhost ~(keystone_admin)]# > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Wed Feb 13 16:28:00 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 17:28:00 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Message-ID: <1722106541.435943.1550075280383@communicator.strato.com> Hi, when I unlock the controller-0 after installation following this tutorial https://docs.starlingx.io/installation_guide/duplex.html#duplex the system is rebooting automatically with a lot of errors from drdb. Controller-1 is not configured at this point in time. Must I configure the secondary controller before unlocking controller-0? Thanks Marcel From Don.Penney at windriver.com Wed Feb 13 16:41:44 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 16:41:44 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <1722106541.435943.1550075280383@communicator.strato.com> References: <1722106541.435943.1550075280383@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> Yes, this is the correct behavior. As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 11:28 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Hi, when I unlock the controller-0 after installation following this tutorial https://docs.starlingx.io/installation_guide/duplex.html#duplex the system is rebooting automatically with a lot of errors from drdb. Controller-1 is not configured at this point in time. Must I configure the secondary controller before unlocking controller-0? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Wed Feb 13 16:47:40 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 17:47:40 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> Message-ID: <1898058568.437106.1550076460788@communicator.strato.com> I am using the build centos-20190206T060000Z. The main problem, beside of the noise is, that the system comes up and reboots immediately again. > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > Yes, this is the correct behavior. > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:28 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > Hi, > > when I unlock the controller-0 after installation following this tutorial > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > the system is rebooting automatically with a lot of errors from drdb. > > Controller-1 is not configured at this point in time. > > Must I configure the secondary controller before unlocking controller-0? > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From mario.alfredo.c.arevalo at intel.com Wed Feb 13 16:55:35 2019 From: mario.alfredo.c.arevalo at intel.com (Arevalo, Mario Alfredo C) Date: Wed, 13 Feb 2019 16:55:35 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <1722106541.435943.1550075280383@communicator.strato.com> References: <1722106541.435943.1550075280383@communicator.strato.com> Message-ID: <6594B51DBE477C48AAE23675314E6C466457ACDE@fmsmsx107.amr.corp.intel.com> Hi Marcel Can you please share us the output of the drbd error? Thanks. Best regards. Mario. ________________________________________ From: Marcel Schaible [marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 8:28 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Hi, when I unlock the controller-0 after installation following this tutorial https://docs.starlingx.io/installation_guide/duplex.html#duplex the system is rebooting automatically with a lot of errors from drdb. Controller-1 is not configured at this point in time. Must I configure the secondary controller before unlocking controller-0? Thanks Marcel _______________________________________________ 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 Feb 13 17:02:18 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 17:02:18 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <1898058568.437106.1550076460788@communicator.strato.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> <1898058568.437106.1550076460788@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> Ok, my updates related to the DRBD state change failures merged Feb 8th. I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: * install node, run config_controller, do config steps * system host-unlock controller-0 * system reboots * system reboots a second time? At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 11:48 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot I am using the build centos-20190206T060000Z. The main problem, beside of the noise is, that the system comes up and reboots immediately again. > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > Yes, this is the correct behavior. > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:28 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > Hi, > > when I unlock the controller-0 after installation following this tutorial > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > the system is rebooting automatically with a lot of errors from drdb. > > Controller-1 is not configured at this point in time. > > Must I configure the secondary controller before unlocking controller-0? > > Thanks > > Marcel > > _______________________________________________ > 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 marcel at schaible-consulting.de Wed Feb 13 17:17:39 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 18:17:39 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> <1898058568.437106.1550076460788@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> Message-ID: <23037907.438773.1550078259297@communicator.strato.com> At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? If yes, I would start to configure the controller-1. root at controller-0 ~(keystone_admin)]# fm alarm-list +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ [root at controller-0 ~(keystone_admin)]# > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > * install node, run config_controller, do config steps > * system host-unlock controller-0 > * system reboots > * system reboots a second time? Yes, exactly. > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. The second reboot starts in about 1 minute after the login prompt is shown. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:48 AM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > I am using the build centos-20190206T060000Z. > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > Yes, this is the correct behavior. > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:28 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > Hi, > > > > when I unlock the controller-0 after installation following this tutorial > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > Controller-1 is not configured at this point in time. > > > > Must I configure the secondary controller before unlocking controller-0? > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > 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 felipe.de.jesus.ruiz.garcia at intel.com Wed Feb 13 17:19:13 2019 From: felipe.de.jesus.ruiz.garcia at intel.com (Ruiz Garcia, Felipe De Jesus) Date: Wed, 13 Feb 2019 17:19:13 +0000 Subject: [Starlingx-discuss] build-pkgs behavior: packages always compile Message-ID: <6454B6BCFEF18140B07C3AF1FA04DC89496B37FD@FMSMSX108.amr.corp.intel.com> Hi Scott I am working on the bug 1804687, and I have realized that some packages are rebuilt when "build-pkgs" is executed even if the package does not have new changes. The packages mentioned are: sm-common-debuginfo-1.0.0-20.tis.x86_64.rpm sm-common-dev-1.0.0-20.tis.x86_64.rpm sm-common-libs-1.0.0-20.tis.x86_64.rpm sm-eru-1.0.0-20.tis.x86_64.rpm sm-common-1.0.0-20.tis.src.rpm sm-common-1.0.0-20.tis.x86_64.rpm build-info-1.0-4.tis.src.rpm build-info-1.0-4.tis.x86_64.rpm build-info-dev-1.0-4.tis.x86_64.rpm Is this behavior a bug? otherwise why are those packages built every time if they have the same version? Note: The fix for the bug is ready for review https://review.openstack.org/#/c/634513/ Regards Felipe Ruiz / Pipo / Tranzemc Before anything else, preparation is the key to success. ( Alexander Graham Bell ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Wed Feb 13 17:20:33 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 18:20:33 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <6594B51DBE477C48AAE23675314E6C466457ACDE@fmsmsx107.amr.corp.intel.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6594B51DBE477C48AAE23675314E6C466457ACDE@fmsmsx107.amr.corp.intel.com> Message-ID: <92325439.438880.1550078433683@communicator.strato.com> controller-0 login: wrsroot Password: [ 447.539473] block drbd5: State change failed: Device is held open by someone [ 447.547353] block drbd5: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.557656] block drbd5: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.616216] block drbd1: State change failed: Device is held open by someone [ 447.624093] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.625520] block drbd2: State change failed: Device is held open by someone [ 447.625523] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.625524] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.663063] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.695930] block drbd0: State change failed: Device is held open by someone [ 447.703809] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.714117] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.717735] block drbd5: State change failed: Device is held open by someone [ 447.717737] block drbd5: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.717739] block drbd5: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.744998] block drbd2: State change failed: Device is held open by someone [ 447.745001] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.745002] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.790092] block drbd1: State change failed: Device is held open by someone [ 447.792927] block drbd0: State change failed: Device is held open by someone [ 447.792930] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.792931] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 447.826631] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 447.826633] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 448.813520] block drbd2: State change failed: Device is held open by someone [ 448.816397] block drbd0: State change failed: Device is held open by someone [ 448.816399] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 448.816400] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 448.850061] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 448.850062] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 448.851141] block drbd1: State change failed: Device is held open by someone [ 448.851143] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 448.851144] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 449.902198] block drbd0: State change failed: Device is held open by someone [ 449.910077] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 449.920380] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 449.933114] block drbd1: State change failed: Device is held open by someone [ 449.935475] block drbd2: State change failed: Device is held open by someone [ 449.935478] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 449.935479] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 449.969656] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 449.969658] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 450.975871] block drbd2: State change failed: Device is held open by someone [ 450.983748] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 450.994052] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 451.015768] block drbd0: State change failed: Device is held open by someone [ 451.023643] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 451.033947] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 451.038700] block drbd1: State change failed: Device is held open by someone [ 451.038702] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 451.038703] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 451.954434] block drbd3: State change failed: Device is held open by someone [ 451.962309] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 451.972608] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 452.007079] block drbd3: State change failed: Device is held open by someone [ 452.012542] block drbd2: State change failed: Device is held open by someone [ 452.012544] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 452.012545] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 452.043617] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 452.043619] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 452.074582] block drbd1: State change failed: Device is held open by someone [ 452.080401] block drbd0: State change failed: Device is held open by someone [ 452.080403] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 452.080404] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 452.111118] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 452.111120] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 453.045601] block drbd2: State change failed: Device is held open by someone [ 453.053478] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 453.063780] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 453.096723] block drbd3: State change failed: Device is held open by someone [ 453.104599] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 453.114898] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 453.137325] block drbd0: State change failed: Device is held open by someone [ 453.142791] block drbd1: State change failed: Device is held open by someone [ 453.142793] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 453.142794] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 453.173863] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 453.173864] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 454.091972] block drbd2: State change failed: Device is held open by someone [ 454.099849] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 454.110150] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 454.145690] block drbd3: State change failed: Device is held open by someone [ 454.153561] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 454.163867] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 454.176301] block drbd1: State change failed: Device is held open by someone [ 454.184182] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 454.184184] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 454.207939] block drbd0: State change failed: Device is held open by someone [ 454.215814] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 454.226114] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 455.139180] block drbd2: State change failed: Device is held open by someone [ 455.147055] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 455.157356] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 455.187247] block drbd3: State change failed: Device is held open by someone [ 455.195124] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 455.205430] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 455.206796] block drbd1: State change failed: Device is held open by someone [ 455.206798] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 455.206800] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 455.254455] block drbd0: State change failed: Device is held open by someone [ 455.262332] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 455.272633] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 456.186309] block drbd2: State change failed: Device is held open by someone [ 456.194185] block drbd2: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 456.204488] block drbd2: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 456.223846] block drbd1: State change failed: Device is held open by someone [ 456.224096] block drbd3: State change failed: Device is held open by someone [ 456.224098] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 456.224099] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 456.260386] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 456.260388] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 456.300789] block drbd0: State change failed: Device is held open by someone [ 456.308664] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 456.318965] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 457.242948] block drbd3: State change failed: Device is held open by someone [ 457.250834] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 457.250835] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 457.279143] block drbd1: State change failed: Device is held open by someone [ 457.287019] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 457.297319] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 457.346954] block drbd0: State change failed: Device is held open by someone [ 457.354829] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 457.365129] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 458.310997] block drbd3: State change failed: Device is held open by someone [ 458.318872] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 458.326017] block drbd1: State change failed: Device is held open by someone [ 458.326019] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 458.326020] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 458.357835] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 458.393913] block drbd0: State change failed: Device is held open by someone [ 458.401786] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 458.412085] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 459.346078] block drbd1: State change failed: Device is held open by someone [ 459.353953] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 459.364252] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 459.375826] block drbd3: State change failed: Device is held open by someone [ 459.383716] block drbd3: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 459.383717] block drbd3: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 459.440444] block drbd0: State change failed: Device is held open by someone [ 459.448319] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 459.458619] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 460.394649] block drbd1: State change failed: Device is held open by someone [ 460.402529] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 460.402530] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 460.498012] block drbd0: State change failed: Device is held open by someone [ 460.505890] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 460.505891] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 461.458950] block drbd1: State change failed: Device is held open by someone [ 461.466830] block drbd1: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 461.466831] block drbd1: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } [ 461.529731] block drbd0: State change failed: Device is held open by someone [ 461.537611] block drbd0: state = { cs:WFConnection ro:Primary/Unknown ds:UpToDate/DUnknown r----- } [ 461.537612] block drbd0: wanted = { cs:WFConnection ro:Secondary/Unknown ds:UpToDate/DUnknown r----- } > "Arevalo, Mario Alfredo C" hat am 13. Februar 2019 um 17:55 geschrieben: > > > Hi Marcel > > Can you please share us the output of the drbd error? > > Thanks. > > Best regards. > Mario. > ________________________________________ > From: Marcel Schaible [marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 8:28 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > Hi, > > when I unlock the controller-0 after installation following this tutorial > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > the system is rebooting automatically with a lot of errors from drdb. > > Controller-1 is not configured at this point in time. > > Must I configure the secondary controller before unlocking controller-0? > > Thanks > > Marcel > > _______________________________________________ > 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 Feb 13 17:20:11 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 17:20:11 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <23037907.438773.1550078259297@communicator.strato.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> <1898058568.437106.1550076460788@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> <23037907.438773.1550078259297@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D27F@ALA-MBD.corp.ad.wrs.com> I would suggest checking the puppet logs for a failure.... grep for Error. The redundancy alarms are because you don't have controller-1 yet, and can be ignored. The port failure alarm is concerning, I think... maybe that's related to the configuration error. -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 12:18 PM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? If yes, I would start to configure the controller-1. root at controller-0 ~(keystone_admin)]# fm alarm-list +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ [root at controller-0 ~(keystone_admin)]# > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > * install node, run config_controller, do config steps > * system host-unlock controller-0 > * system reboots > * system reboots a second time? Yes, exactly. > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. The second reboot starts in about 1 minute after the login prompt is shown. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:48 AM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > I am using the build centos-20190206T060000Z. > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > Yes, this is the correct behavior. > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:28 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > Hi, > > > > when I unlock the controller-0 after installation following this tutorial > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > Controller-1 is not configured at this point in time. > > > > Must I configure the secondary controller before unlocking controller-0? > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > 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 Don.Penney at windriver.com Wed Feb 13 17:23:26 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 17:23:26 +0000 Subject: [Starlingx-discuss] build-pkgs behavior: packages always compile In-Reply-To: <6454B6BCFEF18140B07C3AF1FA04DC89496B37FD@FMSMSX108.amr.corp.intel.com> References: <6454B6BCFEF18140B07C3AF1FA04DC89496B37FD@FMSMSX108.amr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D2A8@ALA-MBD.corp.ad.wrs.com> The build-info package rebuilds every time, as it generates the /etc/build-info file with info about the build. You can skip this by using "build-pkgs --no-build-info". SM rebuilds because it has a dependency on build-info. From: Ruiz Garcia, Felipe De Jesus [mailto:felipe.de.jesus.ruiz.garcia at intel.com] Sent: Wednesday, February 13, 2019 12:19 PM To: Little, Scott Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] build-pkgs behavior: packages always compile Hi Scott I am working on the bug 1804687, and I have realized that some packages are rebuilt when "build-pkgs" is executed even if the package does not have new changes. The packages mentioned are: sm-common-debuginfo-1.0.0-20.tis.x86_64.rpm sm-common-dev-1.0.0-20.tis.x86_64.rpm sm-common-libs-1.0.0-20.tis.x86_64.rpm sm-eru-1.0.0-20.tis.x86_64.rpm sm-common-1.0.0-20.tis.src.rpm sm-common-1.0.0-20.tis.x86_64.rpm build-info-1.0-4.tis.src.rpm build-info-1.0-4.tis.x86_64.rpm build-info-dev-1.0-4.tis.x86_64.rpm Is this behavior a bug? otherwise why are those packages built every time if they have the same version? Note: The fix for the bug is ready for review https://review.openstack.org/#/c/634513/ Regards Felipe Ruiz / Pipo / Tranzemc Before anything else, preparation is the key to success. ( Alexander Graham Bell ) -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Wed Feb 13 17:27:01 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 13 Feb 2019 18:27:01 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D27F@ALA-MBD.corp.ad.wrs.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> <1898058568.437106.1550076460788@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> <23037907.438773.1550078259297@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D27F@ALA-MBD.corp.ad.wrs.com> Message-ID: <1103410681.439174.1550078821148@communicator.strato.com> Ok. The latest puppet logs from controller-0 do not contain any errors. Should I try to install a newer image? > "Penney, Don" hat am 13. Februar 2019 um 18:20 geschrieben: > > > I would suggest checking the puppet logs for a failure.... grep for Error. The redundancy alarms are because you don't have controller-1 yet, and can be ignored. The port failure alarm is concerning, I think... maybe that's related to the configuration error. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 12:18 PM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. > > Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? > If yes, I would start to configure the controller-1. > > > root at controller-0 ~(keystone_admin)]# fm alarm-list > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | > | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | > | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | > | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | > | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | > | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | > | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | > | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | > | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | > | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | > | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | > | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > [root at controller-0 ~(keystone_admin)]# > > > > > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > > * install node, run config_controller, do config steps > > * system host-unlock controller-0 > > * system reboots > > * system reboots a second time? > > Yes, exactly. > > > > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. > > The second reboot starts in about 1 minute after the login prompt is shown. > > > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:48 AM > > To: Penney, Don; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > I am using the build centos-20190206T060000Z. > > > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > > > > Yes, this is the correct behavior. > > > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > > > -----Original Message----- > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > Sent: Wednesday, February 13, 2019 11:28 AM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > > > Hi, > > > > > > when I unlock the controller-0 after installation following this tutorial > > > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > > > Controller-1 is not configured at this point in time. > > > > > > Must I configure the secondary controller before unlocking controller-0? > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > 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 Don.Penney at windriver.com Wed Feb 13 17:31:21 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 17:31:21 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot In-Reply-To: <1103410681.439174.1550078821148@communicator.strato.com> References: <1722106541.435943.1550075280383@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D211@ALA-MBD.corp.ad.wrs.com> <1898058568.437106.1550076460788@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F@ALA-MBD.corp.ad.wrs.com> <23037907.438773.1550078259297@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D27F@ALA-MBD.corp.ad.wrs.com> <1103410681.439174.1550078821148@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D2C9@ALA-MBD.corp.ad.wrs.com> You'd need to look at the puppet log from the first reboot to see if some failure occurred there, or whether the reboot was triggered by a config change. I don't know if the configuration failure alarm is related to puppet or not. Given the OAM port alarm, you should double-check your OAM interface and configuration. Maybe John Kung has better advice on what to check... John? -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 12:27 PM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Ok. The latest puppet logs from controller-0 do not contain any errors. Should I try to install a newer image? > "Penney, Don" hat am 13. Februar 2019 um 18:20 geschrieben: > > > I would suggest checking the puppet logs for a failure.... grep for Error. The redundancy alarms are because you don't have controller-1 yet, and can be ignored. The port failure alarm is concerning, I think... maybe that's related to the configuration error. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 12:18 PM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. > > Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? > If yes, I would start to configure the controller-1. > > > root at controller-0 ~(keystone_admin)]# fm alarm-list > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | > | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | > | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | > | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | > | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | > | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | > | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | > | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | > | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | > | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | > | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | > | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > [root at controller-0 ~(keystone_admin)]# > > > > > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > > * install node, run config_controller, do config steps > > * system host-unlock controller-0 > > * system reboots > > * system reboots a second time? > > Yes, exactly. > > > > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. > > The second reboot starts in about 1 minute after the login prompt is shown. > > > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:48 AM > > To: Penney, Don; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > I am using the build centos-20190206T060000Z. > > > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > > > > Yes, this is the correct behavior. > > > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > > > -----Original Message----- > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > Sent: Wednesday, February 13, 2019 11:28 AM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > > > Hi, > > > > > > when I unlock the controller-0 after installation following this tutorial > > > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > > > Controller-1 is not configured at this point in time. > > > > > > Must I configure the secondary controller before unlocking controller-0? > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > 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 ildiko.vancsa at gmail.com Wed Feb 13 18:05:51 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 13 Feb 2019 19:05:51 +0100 Subject: [Starlingx-discuss] Open Infrastructure Summit and PTG planning Message-ID: <1F2C4A3F-7E11-4C9E-8993-14BD20BB25D1@gmail.com> Hi StarlingX Community, As we are getting closer to the Open Infrastructure Summit it is time to start to think about planning for the working sessions such as the Forum and PTG. The first priority at this point is the Forum as the session proposal phase opens on February 22. You can find the full timeline here: https://wiki.openstack.org/wiki/Forum I created an etherpad to brainstorm about topics to cover so we don’t have duplications when we submit session ideas: https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 Our team is currently working on scheduling for the PTG which will happen right after the Summit. You can see in a previous email the teams who applied for space which information we can use when we plan cross-project sessions: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003057.html I created another etherpad to plan PTG topics as we get closer to the event: https://etherpad.openstack.org/p/stx-ptg-preparation-denver-2019 Please let me know if you have any questions. Thanks and Best Regards, Ildikó From John.Kung at windriver.com Wed Feb 13 18:27:48 2019 From: John.Kung at windriver.com (Kung, John) Date: Wed, 13 Feb 2019 18:27:48 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes Message-ID: Marcel, controller-0 should be unlocked successfully for the first time before attempting to provision/configure controller-1 As noted, the presence of 'Error' logs on controller-0 (under directory /var/log/puppet ) would indicate the reason for the configuration failure (200.011). In regards to the OAM interface configured, please check 'system host-if-list -a controller-0' and 'system host-ethernet-port-list controller-0' to determine the current interface configuration. Furthermore, after the 'host-unlock controller-0', the configured OAM interface IP should be reachable from your OAM network 'system host-addr-list controller-0' to see the addresses allocated for that host. John ---------------------------------------------------------------------- Message: 1 Date: Wed, 13 Feb 2019 17:02:18 +0000 From: "Penney, Don" To: Marcel Schaible , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D23F at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="utf-8" Ok, my updates related to the DRBD state change failures merged Feb 8th. I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: * install node, run config_controller, do config steps * system host-unlock controller-0 * system reboots * system reboots a second time? At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 11:48 AM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot I am using the build centos-20190206T060000Z. The main problem, beside of the noise is, that the system comes up and reboots immediately again. > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > Yes, this is the correct behavior. > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:28 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > Hi, > > when I unlock the controller-0 after installation following this tutorial > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > the system is rebooting automatically with a lot of errors from drdb. > > Controller-1 is not configured at this point in time. > > Must I configure the secondary controller before unlocking controller-0? > > Thanks > > Marcel > > _______________________________________________ > 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 ------------------------------ Message: 2 Date: Wed, 13 Feb 2019 18:17:39 +0100 (CET) From: Marcel Schaible To: "Penney, Don" , starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Message-ID: <23037907.438773.1550078259297 at communicator.strato.com> Content-Type: text/plain; charset=UTF-8 At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? If yes, I would start to configure the controller-1. root at controller-0 ~(keystone_admin)]# fm alarm-list +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ [root at controller-0 ~(keystone_admin)]# > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > * install node, run config_controller, do config steps > * system host-unlock controller-0 > * system reboots > * system reboots a second time? Yes, exactly. > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. The second reboot starts in about 1 minute after the login prompt is shown. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 11:48 AM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > I am using the build centos-20190206T060000Z. > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > Yes, this is the correct behavior. > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:28 AM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > Hi, > > > > when I unlock the controller-0 after installation following this tutorial > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > Controller-1 is not configured at this point in time. > > > > Must I configure the secondary controller before unlocking controller-0? > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > 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 John.Kung at windriver.com Wed Feb 13 18:36:07 2019 From: John.Kung at windriver.com (Kung, John) Date: Wed, 13 Feb 2019 18:36:07 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 9, Issue 54 In-Reply-To: References: Message-ID: Marcel, controller-0 should be unlocked successfully for the first time before attempting to provision/configure controller-1 As noted, the presence of 'Error' logs on controller-0 (under directory /var/log/puppet ) would indicate the reason for the configuration failure (200.011). In regards to the OAM interface configured, please check 'system host-if-list -a controller-0' and 'system host-ethernet-port-list controller-0' to determine the current interface configuration. Furthermore, after the 'host-unlock controller-0', the configured OAM interface IP should be reachable from your OAM network 'system host-addr-list controller-0' to see the addresses allocated for that host. John ---------------------------------------------------------------------- Message: 1 Date: Wed, 13 Feb 2019 17:31:21 +0000 From: "Penney, Don" To: Marcel Schaible , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D2C9 at ALA-MBD.corp.ad.wrs.com> Content-Type: text/plain; charset="utf-8" You'd need to look at the puppet log from the first reboot to see if some failure occurred there, or whether the reboot was triggered by a config change. I don't know if the configuration failure alarm is related to puppet or not. Given the OAM port alarm, you should double-check your OAM interface and configuration. Maybe John Kung has better advice on what to check... John? -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Wednesday, February 13, 2019 12:27 PM To: Penney, Don; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot Ok. The latest puppet logs from controller-0 do not contain any errors. Should I try to install a newer image? > "Penney, Don" hat am 13. Februar 2019 um 18:20 geschrieben: > > > I would suggest checking the puppet logs for a failure.... grep for Error. The redundancy alarms are because you don't have controller-1 yet, and can be ignored. The port failure alarm is concerning, I think... maybe that's related to the configuration error. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 12:18 PM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. > > Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? > If yes, I would start to configure the controller-1. > > > root at controller-0 ~(keystone_admin)]# fm alarm-list > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | > | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | > | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | > | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | > | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | > | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | > | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | > | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | > | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | > | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | > | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | > | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > [root at controller-0 ~(keystone_admin)]# > > > > > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > > * install node, run config_controller, do config steps > > * system host-unlock controller-0 > > * system reboots > > * system reboots a second time? > > Yes, exactly. > > > > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. > > The second reboot starts in about 1 minute after the login prompt is shown. > > > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 11:48 AM > > To: Penney, Don; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > I am using the build centos-20190206T060000Z. > > > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > > > > Yes, this is the correct behavior. > > > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > > > -----Original Message----- > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > Sent: Wednesday, February 13, 2019 11:28 AM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > > > Hi, > > > > > > when I unlock the controller-0 after installation following this tutorial > > > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > > > Controller-1 is not configured at this point in time. > > > > > > Must I configure the secondary controller before unlocking controller-0? > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > 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 yang.liu at windriver.com Wed Feb 13 19:01:35 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Wed, 13 Feb 2019 19:01:35 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it's wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Feb 13 19:21:48 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 13 Feb 2019 19:21:48 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190213 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9B6A2@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-13 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 22 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Feb 13 20:21:05 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 13 Feb 2019 20:21:05 +0000 Subject: [Starlingx-discuss] ceilometer event-list Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9B703@FMSMSX108.amr.corp.intel.com> Hi, I am trying to get the output of ceilometer event-list command, from an STX container system, but I am getting the below error: [wrsroot at controller-0 ~(keystone_admin)]$ ceilometer event-list internalURL endpoint for metering service in RegionOne region not found I used source /etc/platform/openrc authentication. I also use the keystone in the container https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints, but get the same error. Do you know how to resolve this issue? The command have been updated? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Wed Feb 13 20:43:09 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Wed, 13 Feb 2019 20:43:09 +0000 Subject: [Starlingx-discuss] ceilometer event-list In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C9B703@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C9B703@FMSMSX108.amr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F862183920@ALA-MBD.corp.ad.wrs.com> If you sourced to /etc/platform/openrc, then even if you do export OS_CLOUD=openstack_helm later on, the OS_AUTH_URL in the openrc will still be used. You have two options: 1. source /etc/platform/openrc; export OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3; ceilometer event-list 2. open a new shell (DO NOT source to platform openrc) > export OS_CLOUD=openstack_helm; ceilometer event-list (or openstack event list) BR, Yang From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: February-13-19 3:21 PM To: 'starlingx-discuss at lists.starlingx.io' Subject: [Starlingx-discuss] ceilometer event-list Hi, I am trying to get the output of ceilometer event-list command, from an STX container system, but I am getting the below error: [wrsroot at controller-0 ~(keystone_admin)]$ ceilometer event-list internalURL endpoint for metering service in RegionOne region not found I used source /etc/platform/openrc authentication. I also use the keystone in the container https://wiki.openstack.org/wiki/StarlingX/Containers/Installation#Verify_the_cluster_endpoints, but get the same error. Do you know how to resolve this issue? The command have been updated? Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Wed Feb 13 20:58:25 2019 From: scott.little at windriver.com (Scott Little) Date: Wed, 13 Feb 2019 15:58:25 -0500 Subject: [Starlingx-discuss] build-pkgs behavior: packages always compile In-Reply-To: <6454B6BCFEF18140B07C3AF1FA04DC89496B37FD@FMSMSX108.amr.corp.intel.com> References: <6454B6BCFEF18140B07C3AF1FA04DC89496B37FD@FMSMSX108.amr.corp.intel.com> Message-ID: <151a4f37-f239-5ed1-e5e2-d2cc317b3e62@windriver.com> build-info is always rebuilt, unless the --no-build-info flag is used. the others likely have a BuildRequires on build-info.  We do that in case there is a .h change that might alter the compilation of 'descendent' packages.  You can suppress that behaviour with  --no-descendants. Scott On 2019-02-13 12:19 p.m., Ruiz Garcia, Felipe De Jesus wrote: > > Hi Scott > > I am working on the bug 1804687 > , and I have > realized that some packages are rebuilt when "build-pkgs" is executed > even if the package does not have new changes. > > The packages mentioned are: > > sm-common-debuginfo-1.0.0-20.tis.x86_64.rpm > > sm-common-dev-1.0.0-20.tis.x86_64.rpm > > sm-common-libs-1.0.0-20.tis.x86_64.rpm > > sm-eru-1.0.0-20.tis.x86_64.rpm > > sm-common-1.0.0-20.tis.src.rpm > > sm-common-1.0.0-20.tis.x86_64.rpm > > build-info-1.0-4.tis.src.rpm > > build-info-1.0-4.tis.x86_64.rpm > > build-info-dev-1.0-4.tis.x86_64.rpm > > Is this behavior a bug? otherwise why are those packages built every > time if they have the same version? > > Note: > > The fix for the bug is ready for review > https://review.openstack.org/#/c/634513/ > > > Regards > *Felipe Ruiz / Pipo / Tranzemc* > /Before anything else, preparation is the key to success. (  Alexander > Graham Bell  )/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Feb 13 21:45:44 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 13 Feb 2019 21:45:44 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> ,<19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> Message-ID: <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Wed Feb 13 22:00:53 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Wed, 13 Feb 2019 22:00:53 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> ,<19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like "tail -f /var/log/daemon.log | grep -i tftp" while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don't see this file transferred, I'd recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It's interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it's wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Wed Feb 13 23:22:20 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 13 Feb 2019 18:22:20 -0500 Subject: [Starlingx-discuss] Open Infrastructure Summit and PTG planning In-Reply-To: <1F2C4A3F-7E11-4C9E-8993-14BD20BB25D1@gmail.com> References: <1F2C4A3F-7E11-4C9E-8993-14BD20BB25D1@gmail.com> Message-ID: On Wed, Feb 13, 2019 at 1:07 PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > As we are getting closer to the Open Infrastructure Summit it is time to > start to think about planning for the working sessions such as the Forum > and PTG. > > The first priority at this point is the Forum as the session proposal > phase opens on February 22. You can find the full timeline here: > https://wiki.openstack.org/wiki/Forum > > I created an etherpad to brainstorm about topics to cover so we don’t have > duplications when we submit session ideas: > https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 I added a potential session regarding OpenStack Operators, and if there is anyone else in the community who would like to help moderate this potential session, I'm happy to have help. When I say "operator" I don't mean that in the telecommunication sense, but rather "OpenStack Operators"--people charged with day to day management of an OpenStack cloud. Thanks, Curtis PS. There is an upcoming OpenStack Operators meetup in Berlin: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002436.html should there be anyone on this list capable of attending. I wish I could. I love Berlin. :) > > > > Our team is currently working on scheduling for the PTG which will happen > right after the Summit. You can see in a previous email the teams who > applied for space which information we can use when we plan cross-project > sessions: > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003057.html > > I created another etherpad to plan PTG topics as we get closer to the > event: https://etherpad.openstack.org/p/stx-ptg-preparation-denver-2019 > > > Please let me know if you have any questions. > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Wed Feb 13 23:57:52 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 13 Feb 2019 23:57:52 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting agenda 2/14/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105EC160@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 2/14/2019 - Cengn update - CVE scan integration - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Feb 14 00:22:25 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Feb 2019 19:22:25 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_wheels - Build # 46 - Failure! Message-ID: <336072122.23.1550103749380.JavaMail.javamailuser@localhost> Project: STX_build_wheels Build #: 46 Status: Failure Timestamp: 20190214T000905Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190213T213623Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190213T213623Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190213T213623Z/logs OPENSTACK_RELEASE: pike OS_VERSION: 7.5.1804 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190213T213623Z/logs From build.starlingx at gmail.com Thu Feb 14 00:22:31 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Feb 2019 19:22:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_images - Build # 46 - Failure! Message-ID: <1430595795.26.1550103752545.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 46 Status: Failure Timestamp: 20190214T000721Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190213T213623Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190213T213623Z 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/20190213T213623Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190213T213623Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20190213T213623Z DOCKER_BUILD_ID: jenkins-master-20190213T213623Z-builder OPENSTACK_RELEASE: pike TIMESTAMP: 20190213T213623Z OS_VERSION: 7.5.1804 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190213T213623Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190213T213623Z/outputs From build.starlingx at gmail.com Thu Feb 14 00:22:35 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 13 Feb 2019 19:22:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 138 - Failure! Message-ID: <442856396.29.1550103755915.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 138 Status: Failure Timestamp: 20190213T213623Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190213T213623Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: true From michael.l.tullis at intel.com Thu Feb 14 00:29:01 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Thu, 14 Feb 2019 00:29:01 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2/13/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AB6766@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Thu Feb 14 00:53:54 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Thu, 14 Feb 2019 00:53:54 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> ,<19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E86C0A@SHSMSX104.ccr.corp.intel.com> Thanks, Don for the details. We will do as instructed and ensure the test is done correctly. Thx. - cindy From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like "tail -f /var/log/daemon.log | grep -i tftp" while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don't see this file transferred, I'd recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It's interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it's wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Thu Feb 14 07:31:33 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Thu, 14 Feb 2019 07:31:33 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> ,<19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the "grubx64.efi" in "export/dist/isolinux/pxeboot/EFI/" is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the "grubx64.efi" is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: " 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi " 3. Austin confirmed "install -D -m 755" will set the grubx64.efi with 755 permission mode. " -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x " 4. I try to go through the build log. Here is the log from grub2's build.log " + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi " And in build-iso script, the file will be extracted and copied to the EFI folder: " extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot ... \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ " Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is "install -D -m 755 grubx64.efi" in the "loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log" or not. 2. Please help extract "grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm" in "loadbuild/std/rpmbuild/RPMS", and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the "grubx64.efi" in "export/dist/isolinux/pxeboot/EFI/" folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like "tail -f /var/log/daemon.log | grep -i tftp" while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don't see this file transferred, I'd recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It's interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it's wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From cheng1.li at intel.com Thu Feb 14 08:06:10 2019 From: cheng1.li at intel.com (Li, Cheng1) Date: Thu, 14 Feb 2019 08:06:10 +0000 Subject: [Starlingx-discuss] STX ovs containerization Message-ID: Hi Matt, Joseph, I have updated the patch per your comments. https://review.openstack.org/633924 Regarding per-host overrides of network information( network -> auto_bridge_add), seems openstack-helm doesn't support it. I prefer to leave auto_bridge_add scope as it is until openstack-helm support per-host overrides of network info. If that, we need add nic to bridge by hand, instead of initContainer. I believe Joseph is trying to find an approach for auto_bridge_add, let's waiting for the result. Thanks, Cheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Feb 14 12:39:14 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Feb 2019 13:39:14 +0100 (CET) Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 9, Issue 54 In-Reply-To: References: Message-ID: <1274355318.481180.1550147954209@communicator.strato.com> Hi John, thanks for your help! At the moment the controller-0 is stable and spontaneous rebooting. The box is not reachable thru our lab net with the ip 10.62.150.211. The box responds on ICMP at this address but the web server is not reachable. The network config looks like this: Any ideas what is wrong with that? -0oot at controller-0 ~(keystone_admin)]# system host-if-list -a controller-0- +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+--------------------+ | uuid | name | class | type | vlan id | ports | uses i/f | used by i/f | attributes | data networks | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+--------------------+ | 04665f98-8318-4855-a591-1307231a40b3 | bond0 | platform | ae | None | [] | [u'ens1f3', u'ens1f1'] | [] | MTU=1500,AE_MODE=active_standby | [] | | 2a6b70cb-53ad-43c3-adc7-b92c4c44470d | enp9s20f6 | None | ethernet | None | [u'enp9s20f6'] | [] | [] | MTU=1500 | [] | | 2dcbe277-530e-400c-b156-43545b4507c8 | ens1f1 | None | ethernet | None | [u'ens1f1'] | [] | [u'bond0'] | MTU=1500 | [] | | 3acd41aa-aeb0-400c-86ba-79f0fdb24829 | ens1f3 | None | ethernet | None | [u'ens1f3'] | [] | [u'bond0'] | MTU=1500 | [] | | 86b8867a-2aee-4cb9-a04a-7587ff8d833d | enp3s0f0 | None | ethernet | None | [u'enp3s0f0'] | [] | [] | MTU=1500 | [] | | ce78e71f-4300-4a6b-ae0a-43e3139a5515 | enp3s0f1 | None | ethernet | None | [u'enp3s0f1'] | [] | [] | MTU=1500 | [] | | d3e101a0-a873-4c76-b7b5-83368626acd4 | enp9s21f0 | None | ethernet | None | [u'enp9s21f0'] | [] | [] | MTU=1500 | [] | | e93f1d26-e6ee-4c7f-84ef-8b68e312ef16 | enp9s21f1 | data | ethernet | None | [u'enp9s21f1'] | [] | [] | MTU=1500,accelerated=True | [u'providernet-a'] | | ed1b47c8-0311-4e39-8840-9931c69c147e | ens1f0 | None | ethernet | None | [u'ens1f0'] | [] | [] | MTU=1500 | [] | | ee4ce037-1408-4695-b05d-e5491f30e274 | enp9s20f7 | platform | ethernet | None | [u'enp9s20f7'] | [] | [] | MTU=1500 | [] | +--------------------------------------+-----------+----------+----------+---------+----------------+------------------------+-------------+---------------------------------+--------------------+ -0oot at controller-0 ~(keystone_admin)]# system host-ethernet-port-list controller- +--------------------------------------+-----------+-------------------+--------------+-----------+----------+--------------------------------------------+----------+ | uuid | name | mac address | pci address | processor | auto neg | device type | boot i/f | +--------------------------------------+-----------+-------------------+--------------+-----------+----------+--------------------------------------------+----------+ | b93a396b-0fcb-4f51-b121-9e85ded4b49d | enp3s0f0 | ec:9e:cd:1f:7e:b0 | 0000:03:00.0 | 0 | Yes | Ethernet Connection X552 10 GbE Backplane | False | | e24e7cca-9e78-48a5-8d84-dd563fea2626 | enp3s0f1 | ec:9e:cd:1f:7e:b1 | 0000:03:00.1 | 0 | Yes | Ethernet Connection X552 10 GbE Backplane | False | | 41a17a4d-f5eb-4dea-9bcb-0decb10137a4 | enp9s20f6 | 02:01:00:10:01:15 | 0000:09:14.6 | 0 | Yes | 82599 Ethernet Controller Virtual Function | False | | 9d159107-2199-40bb-9e6b-189d6285ca4d | enp9s20f7 | 02:01:00:10:02:15 | 0000:09:14.7 | 0 | Yes | 82599 Ethernet Controller Virtual Function | True | | c0bab514-5c77-48a7-97e5-8a9790df1584 | enp9s21f0 | 02:01:00:10:01:16 | 0000:09:15.0 | 0 | Yes | 82599 Ethernet Controller Virtual Function | False | | 55d31ed0-3370-4b5b-822f-d2766d0b769b | enp9s21f1 | 02:01:00:10:02:16 | 0000:09:15.1 | 0 | Yes | 82599 Ethernet Controller Virtual Function | False | | f4105b07-041e-4a75-90c5-f9f097c33616 | ens1f0 | b4:96:91:1a:01:60 | 0000:07:00.0 | 0 | Yes | I350 Gigabit Network Connection | False | | 000f730d-626e-4087-9a3b-33ac673d688c | ens1f1 | b4:96:91:1a:01:61 | 0000:07:00.1 | 0 | Yes | I350 Gigabit Network Connection | False | | cd202069-f5a0-43bb-a445-d3b9b58ce631 | ens1f3 | b4:96:91:1a:01:63 | 0000:07:00.3 | 0 | Yes | I350 Gigabit Network Connection | False | +--------------------------------------+-----------+-------------------+--------------+-----------+----------+--------------------------------------------+----------+ [root at controller-0 ~(keystone_admin)]# [root at controller-0 ~(keystone_admin)]# ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0f0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ec:9e:cd:1f:7e:b0 brd ff:ff:ff:ff:ff:ff inet6 fe80::ee9e:cdff:fe1f:7eb0/64 scope link valid_lft forever preferred_lft forever 3: ens1f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:60 brd ff:ff:ff:ff:ff:ff 4: ens1f1: mtu 1500 qdisc mq master bond0 state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 5: enp3s0f1: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ec:9e:cd:1f:7e:b1 brd ff:ff:ff:ff:ff:ff 6: ens1f3: mtu 1500 qdisc mq master bond0 state DOWN group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff 7: enp9s20f6: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:15 brd ff:ff:ff:ff:ff:ff 8: enp9s20f7: mtu 1500 qdisc htb state UP group default qlen 1000 link/ether 02:01:00:10:02:15 brd ff:ff:ff:ff:ff:ff inet 172.27.1.3/24 brd 172.27.1.255 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 169.254.202.2/24 scope global enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.2/24 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.5/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet 172.27.1.6/24 brd 172.27.1.255 scope global secondary enp9s20f7 valid_lft forever preferred_lft forever inet6 fe80::1:ff:fe10:215/64 scope link valid_lft forever preferred_lft forever 9: enp9s21f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 02:01:00:10:01:16 brd ff:ff:ff:ff:ff:ff 11: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether b4:96:91:1a:01:61 brd ff:ff:ff:ff:ff:ff inet 10.62.150.211/24 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::b696:91ff:fe1a:161/64 scope link valid_lft forever preferred_lft forever 12: ovs-netdev: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether a2:a0:71:9e:02:81 brd ff:ff:ff:ff:ff:ff 13: br-int: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 06:dc:56:31:96:42 brd ff:ff:ff:ff:ff:ff 16: br-phy0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 56:e3:6b:8a:ff:45 brd ff:ff:ff:ff:ff:ff inet6 fe80::54e3:6bff:fe8a:ff45/64 scope link valid_lft forever preferred_lft forever 17: lldp55d31ed0-33: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether e6:e6:7b:46:1a:b2 brd ff:ff:ff:ff:ff:ff inet6 fe80::e4e6:7bff:fe46:1ab2/64 scope link valid_lft forever preferred_lft forever [root at controller-0 ~(keystone_admin)]# Thanks Marcel > "Kung, John" hat am 13. Februar 2019 um 19:36 geschrieben: > > > Marcel, > > controller-0 should be unlocked successfully for the first time before attempting to provision/configure controller-1 > > As noted, the presence of 'Error' logs on controller-0 (under directory /var/log/puppet ) would indicate the reason for the configuration failure (200.011). > > In regards to the OAM interface configured, please check 'system host-if-list -a controller-0' and 'system host-ethernet-port-list controller-0' to determine the current interface configuration. Furthermore, after the 'host-unlock controller-0', the configured OAM interface IP should be reachable from your OAM network 'system host-addr-list controller-0' to see the addresses allocated for that host. > > > John > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 13 Feb 2019 17:31:21 +0000 > From: "Penney, Don" > To: Marcel Schaible , > "starlingx-discuss at lists.starlingx.io" > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of > controller-0 causes reboot > Message-ID: > <6703202FD9FDFF4A8DA9ACF104AE129FBA43D2C9 at ALA-MBD.corp.ad.wrs.com> > Content-Type: text/plain; charset="utf-8" > > You'd need to look at the puppet log from the first reboot to see if some failure occurred there, or whether the reboot was triggered by a config change. > > I don't know if the configuration failure alarm is related to puppet or not. Given the OAM port alarm, you should double-check your OAM interface and configuration. > > Maybe John Kung has better advice on what to check... John? > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Wednesday, February 13, 2019 12:27 PM > To: Penney, Don; starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > Ok. The latest puppet logs from controller-0 do not contain any errors. > > Should I try to install a newer image? > > > > "Penney, Don" hat am 13. Februar 2019 um 18:20 geschrieben: > > > > > > I would suggest checking the puppet logs for a failure.... grep for Error. The redundancy alarms are because you don't have controller-1 yet, and can be ignored. The port failure alarm is concerning, I think... maybe that's related to the configuration error. > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Wednesday, February 13, 2019 12:18 PM > > To: Penney, Don; starlingx-discuss at lists.starlingx.io > > Subject: RE: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > At the moment the system seems to stablize after 2 reboots. I'll keep an eye on that. > > > > Is the alarm list looking reasonable after the controller-0 is unlocked and rebooted? > > If yes, I would start to configure the controller-1. > > > > > > root at controller-0 ~(keystone_admin)]# fm alarm-list > > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > > | Alarm ID | Reason Text | Entity ID | Severity | Time Stamp | > > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > > | 200.011 | controller-0 experienced a configuration failure. | host=controller-0 | critical | 2019-02-13T18:57:13.772108 | > > | 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=controller-services | major | 2019-02-13T18:56:15.215083 | > > | 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=vim-services | major | 2019-02-13T18:56:15.174083 | > > | 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=cloud-services | major | 2019-02-13T18:56:12.213065 | > > | 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=oam-services | major | 2019-02-13T18:56:05.330099 | > > | 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_domain=controller.service_group=patching-services | major | 2019-02-13T18:56:04.276424 | > > | 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=directory-services | major | 2019-02-13T18:56:04.195081 | > > | 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_domain=controller.service_group=web-services | major | 2019-02-13T18:56:04.114064 | > > | 400.005 | Communication failure detected with peer over port enp9s20f7 on host controller-0 | host=controller-0.network=mgmt | major | 2019-02-13T18:56:03.790070 | > > | 100.106 | 'OAM' Port failed. | host=controller-0.port=cd202069-f5a0-43bb-a445-d3b9b58ce631 | major | 2019-02-13T18:56:00.563067 | > > | 100.107 | 'OAM' Interface degraded. | host=controller-0.interface=oam | major | 2019-02-13T18:56:00.515836 | > > | 300.004 | No enabled compute host with connectivity to provider network. | service=networking.providernet=e9eef26b-d266-4b3f-b1b7-6d9c2cd3a86b | major | 2019-02-13T17:20:21.110405 | > > +----------+-------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+----------+----------------------------+ > > [root at controller-0 ~(keystone_admin)]# > > > > > > > > > "Penney, Don" hat am 13. Februar 2019 um 18:02 geschrieben: > > > > > > > > > Ok, my updates related to the DRBD state change failures merged Feb 8th. > > > > > > I wouldn't expect to see an additional reboot. So what you're seeing, just to confirm, is: > > > * install node, run config_controller, do config steps > > > * system host-unlock controller-0 > > > * system reboots > > > * system reboots a second time? > > > > Yes, exactly. > > > > > > > > At what point is it rebooting a second time? Maybe a reboot is being triggered due to config changes made when the puppet manifests apply, which I think we could confirm from the puppet logs. > > > > The second reboot starts in about 1 minute after the login prompt is shown. > > > > > > > > > > -----Original Message----- > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > Sent: Wednesday, February 13, 2019 11:48 AM > > > To: Penney, Don; starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > > > I am using the build centos-20190206T060000Z. > > > > > > The main problem, beside of the noise is, that the system comes up and reboots immediately again. > > > > > > > > > > > > > "Penney, Don" hat am 13. Februar 2019 um 17:41 geschrieben: > > > > > > > > > > > > Yes, this is the correct behavior. > > > > > > > > As for the drbd warnings, there are some state change failures that occur as the system shuts down, but aren't a problem (aside from the noise). I've managed to clean up most of these in a recent update. What build are you using? > > > > > > > > -----Original Message----- > > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > > Sent: Wednesday, February 13, 2019 11:28 AM > > > > To: starlingx-discuss at lists.starlingx.io > > > > Subject: [Starlingx-discuss] Duplex Configuration: Unlock of controller-0 causes reboot > > > > > > > > Hi, > > > > > > > > when I unlock the controller-0 after installation following this tutorial > > > > > > > > https://docs.starlingx.io/installation_guide/duplex.html#duplex > > > > > > > > the system is rebooting automatically with a lot of errors from drdb. > > > > > > > > Controller-1 is not configured at this point in time. > > > > > > > > Must I configure the secondary controller before unlocking controller-0? > > > > > > > > Thanks > > > > > > > > Marcel > > > > > > > > _______________________________________________ > > > > 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 yang.liu at windriver.com Thu Feb 14 13:36:46 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Thu, 14 Feb 2019 13:36:46 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> ,<19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the "grubx64.efi" in "export/dist/isolinux/pxeboot/EFI/" is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the "grubx64.efi" is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: " 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi " 3. Austin confirmed "install -D -m 755" will set the grubx64.efi with 755 permission mode. " -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x " 4. I try to go through the build log. Here is the log from grub2's build.log " + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi " And in build-iso script, the file will be extracted and copied to the EFI folder: " extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot ... \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ " Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is "install -D -m 755 grubx64.efi" in the "loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log" or not. 2. Please help extract "grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm" in "loadbuild/std/rpmbuild/RPMS", and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the "grubx64.efi" in "export/dist/isolinux/pxeboot/EFI/" folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like "tail -f /var/log/daemon.log | grep -i tftp" while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don't see this file transferred, I'd recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It's interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it's wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the "two node system" below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here's an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won't test. We don't have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Thu Feb 14 14:33:26 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Thu, 14 Feb 2019 14:33:26 +0000 Subject: [Starlingx-discuss] Gnocchi Test Cases In-Reply-To: <0483622846A57742B81A944248DD69042FC015C7@fmsmsx101.amr.corp.intel.com> References: <0483622846A57742B81A944248DD69042FC0053E@fmsmsx101.amr.corp.intel.com> <0483622846A57742B81A944248DD69042FC015C7@fmsmsx101.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE48273C77@ALA-MBD.corp.ad.wrs.com> Hi Juan, I have posted Gnocchi test plan at the following shared drive. I hope you will find it helpful. https://drive.google.com/drive/folders/1nab5AW18HIxpbkjAR6-dwk-kt1rv_8HQ Thanks, Numan. From: Gomez, Juan P Sent: February-13-19 12:33 PM To: Waheed, Numan Cc: Cabrales, Ada Subject: RE: Gnocchi Test Cases Hi Numan, Any update on this? Thanks, JP From: Gomez, Juan P Sent: Monday, February 11, 2019 5:08 PM To: Waheed, Numan > Cc: Cabrales, Ada > Subject: Gnocchi Test Cases Hi Numan, Could you give me a light for Gnocchi Test Cases? Is there any existing test cases that We can port to cover Gnocchi? Which components integrate Gnocchi? Is there any relation between Ceilometer and Gnocchi? Thanks and Best Regards, JP Juan Pablo Gomez Software Quality Assurance Engineer OTC Edge Computing -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Feb 14 15:38:11 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Feb 2019 16:38:11 +0100 (CET) Subject: [Starlingx-discuss] Change of OAM Floating IP on active controller Message-ID: <1325149833.495158.1550158691943@communicator.strato.com> Hi, I must change the OAM floating IP on our active controller-0 (duplex configuration and controller-1 is not configured). I have changed the IP over WebUI and must now lock->unlock the controller-0. This is not possible for the active controller. When I reboot the box the old OAM IP ist getting applied again. What is teh recommended procedure for doing this? Thanks Marcel From juan.carlos.alonso at intel.com Thu Feb 14 15:47:29 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 14 Feb 2019 15:47:29 +0000 Subject: [Starlingx-discuss] Change of OAM Floating IP on active controller In-Reply-To: <1325149833.495158.1550158691943@communicator.strato.com> References: <1325149833.495158.1550158691943@communicator.strato.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9B8C5@FMSMSX108.amr.corp.intel.com> Hi, I think you need to configure the controller-1, then perform a controller swact to make the controller-0 standby and controller-1 the active one. You can lock/unlock the controller-0 now. Regards. Juan Carlos Alonso -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Thursday, February 14, 2019 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Change of OAM Floating IP on active controller Hi, I must change the OAM floating IP on our active controller-0 (duplex configuration and controller-1 is not configured). I have changed the IP over WebUI and must now lock->unlock the controller-0. This is not possible for the active controller. When I reboot the box the old OAM IP ist getting applied again. What is teh recommended procedure for doing this? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From serverascode at gmail.com Thu Feb 14 15:53:58 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 14 Feb 2019 10:53:58 -0500 Subject: [Starlingx-discuss] Packet.com baremetal cloud opportunity In-Reply-To: References: Message-ID: Hi All, If you are interested in this potential project we are working on having a meeting in the near future for next steps, so please add your email to the bottom of the etherpad [1] if you'd like to be included. We are still moving forward with initial investigations, and would like to come up with some concrete next steps. :) Thanks, Curtis [1]: https://etherpad.openstack.org/p/starlingx-packet-edge-pilot On Thu, Jan 31, 2019 at 10:59 AM Curtis wrote: > Hi All, > > There is an opportunity to work with the Packet.com cloud in terms of them > providing cloud resources to the STX community in a couple of different > ways, but you can read about all that in the etherpad [1] and add any > comments/questions/ideas, etc. :) > > Obviously there is some due diligence and information gathering to be > completed, but overall, from my own perspective, having been on a few > related calls, it seems like the STX TSC and other community members that > have had input are thus far positive towards this opportunity. > > Do let us know what you think! > > Thanks kindly, > Curtis > > [1]: https://etherpad.openstack.org/p/starlingx-packet-edge-pilot > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Volker.Hoesslin at swsn.de Thu Feb 14 16:23:09 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 14 Feb 2019 16:23:09 +0000 Subject: [Starlingx-discuss] Nova instance - Change system product name Message-ID: hi, is there any given glance image metadata to change the instance product name? i want to change the xml entry for file libvirt.xml from instance: # by default it looks like this: OpenStack Nova thx, volker... -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Thu Feb 14 16:26:53 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Thu, 14 Feb 2019 16:26:53 +0000 Subject: [Starlingx-discuss] contact for OPNFV In-Reply-To: <0F0AD23D-45CF-4F11-A22D-2FC63DCDF549@intel.com> References: <0EECF16D-278B-46E9-848E-E138060D906C@intel.com> <0F0AD23D-45CF-4F11-A22D-2FC63DCDF549@intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE48273E9B@ALA-MBD.corp.ad.wrs.com> Hi Victor, Peng from my team can help you with any question regarding OPNFV and Refstack test suite. Thanks, Numan. -----Original Message----- From: Rodriguez Bahena, Victor Sent: February-14-19 10:57 AM To: Waheed, Numan Subject: Re: contact for OPNFV Hi Friendly reminder -----Original Message----- From: "Rodriguez Bahena, Victor" Date: Tuesday, February 12, 2019 at 2:33 PM To: "Numan.Waheed at windriver.com" Subject: contact for OPNFV Hi Numan I was wondering if you have the information about the steps to run the performance tests from OPNFV ? Regards Victor Rodriguez From sgw at linux.intel.com Thu Feb 14 17:50:33 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 14 Feb 2019 09:50:33 -0800 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 Message-ID: Folks, I was doing some experimentation with an un-patched CentOS and running config_controller. One of the main issues I found is that doing the initial installation and execution discovered many un-resolved runtime requirements. I will start sending some pull requests to fault, metal, and config with more detailed "Requires:" statements. Another item is that since that we are rebuilding openstack-keystone among other openstack related packages with additional configuration and scripts, which are needed for controller-0. In the stx-integ (base OS) case, we re-factored many of the packages to remove configuration and additional scripts to a separate package, I would like to see something similar here for packages are are needed for controller-0 (ie the things we are not installing from PyPi directly). What I saw is that we include the CentOS-Openstack RPM repo along with, of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack packages directly along with some StarlingX specific additions in a seperate package, rather than creating a new package with both upstream and StarlingX content. Thoughts, Sau! From vm.rod25 at gmail.com Thu Feb 14 18:04:56 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 14 Feb 2019 12:04:56 -0600 Subject: [Starlingx-discuss] contact for OPNFV In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE48273E9B@ALA-MBD.corp.ad.wrs.com> References: <0EECF16D-278B-46E9-848E-E138060D906C@intel.com> <0F0AD23D-45CF-4F11-A22D-2FC63DCDF549@intel.com> <3CAA827B7A79BA46B15B280EC82088FE48273E9B@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks a lot, Numan Peng , Numan mention last testing meeting about a wiki with the steps to run the OPNFV performance framework on top of STX, could you please share those steps? Regards On Thu, Feb 14, 2019 at 10:27 AM Waheed, Numan wrote: > > Hi Victor, > > Peng from my team can help you with any question regarding OPNFV and Refstack test suite. > > Thanks, > > Numan. > > -----Original Message----- > From: Rodriguez Bahena, Victor > Sent: February-14-19 10:57 AM > To: Waheed, Numan > Subject: Re: contact for OPNFV > > Hi > > Friendly reminder > > > -----Original Message----- > From: "Rodriguez Bahena, Victor" > Date: Tuesday, February 12, 2019 at 2:33 PM > To: "Numan.Waheed at windriver.com" > Subject: contact for OPNFV > > Hi Numan > > I was wondering if you have the information about the steps to run the performance tests from OPNFV ? > > Regards > > Victor Rodriguez > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Thu Feb 14 18:39:35 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Feb 2019 19:39:35 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Message-ID: <701275276.504630.1550169575394@communicator.strato.com> Hi, I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: Console log: ============= [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Kernel parameter: ================== dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 ======= The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? Any idea is welcome! Thanks Marcel From Don.Penney at windriver.com Thu Feb 14 18:50:15 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Feb 2019 18:50:15 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <701275276.504630.1550169575394@communicator.strato.com> References: <701275276.504630.1550169575394@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: * problems with the lighttpd server on the active controller * NICs that are unsupported by the initrd kernel modules * some other comms issue What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Thursday, February 14, 2019 1:40 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi, I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: Console log: ============= [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. [ OK ] Started Show Plymouth Boot Screen. [ OK ] Started Device-Mapper Multipath Device Controller. Starting Open-iSCSI... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. [ OK ] Started Open-iSCSI. Starting dracut initqueue hook... [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts ... [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts [Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. dracut:/# Kernel parameter: ================== dracut:/# journalctl | grep -i boot Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 ======= The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? Any idea is welcome! Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Thu Feb 14 18:57:18 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Feb 2019 19:57:18 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> Message-ID: <1434107517.505254.1550170638899@communicator.strato.com> I am using the release ISO centos-20190206T060000Z. > "Penney, Don" hat am 14. Februar 2019 um 19:50 geschrieben: > > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > * problems with the lighttpd server on the active controller > * NICs that are unsupported by the initrd kernel modules > * some other comms issue > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Thursday, February 14, 2019 1:40 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi, > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > Console log: > ============= > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > [ OK ] Started Show Plymouth Boot Screen. > [ OK ] Started Device-Mapper Multipath Device Controller. > Starting Open-iSCSI... > [ OK ] Reached target Paths. > [ OK ] Reached target Basic System. > [ OK ] Started Open-iSCSI. > Starting dracut initqueue hook... > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > ... > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [Warning: /dev/root does not exist > > Generating "/run/initramfs/rdsosreport.txt" > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > after mounting them and attach it to a bug report. > > dracut:/# > > Kernel parameter: > ================== > > dracut:/# journalctl | grep -i boot > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > ======= > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > Any idea is welcome! > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Feb 14 18:57:29 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 14 Feb 2019 18:57:29 +0000 Subject: [Starlingx-discuss] upstream Nova NUMA live migration work Message-ID: <9A85D2917C58154C960D95352B22818BC3AD0D3C@fmsmsx121.amr.corp.intel.com> It looks like there is work moving forward in the Nova community on this topic. There are active and recent code submissions in review here: [0]. Brent, Chris - I have some questions for you. Are you aware of these reviews? Are you planning to review the code? More importantly, does this code meet StarlingX's needs - is it heading in the right direction for us? If not, how and where might we want to influence where the work is going? I have one other ask, for the Test team. Are there existing test cases that we can run to test live migration, to make sure that it 1) works in stx.2019.10 and fails in the current builds? Thanks! Brucej [0] https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Thu Feb 14 19:24:53 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Thu, 14 Feb 2019 19:24:53 +0000 Subject: [Starlingx-discuss] upstream Nova NUMA live migration work In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD0D3C@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD0D3C@fmsmsx121.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD73BA9@FMSMSX114.amr.corp.intel.com> Yes, we have tests that can verify live migration + NUMA. I didn't understand the last part of your question: you want to run those test cases (on a containers config) and verify those don't work, then try those into the stx.2019.10 (October this year)? A. From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, February 14, 2019 12:57 PM To: Rowsell, Brent ; Friesen, Chris Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] upstream Nova NUMA live migration work It looks like there is work moving forward in the Nova community on this topic. There are active and recent code submissions in review here: [0]. Brent, Chris - I have some questions for you. Are you aware of these reviews? Are you planning to review the code? More importantly, does this code meet StarlingX's needs - is it heading in the right direction for us? If not, how and where might we want to influence where the work is going? I have one other ask, for the Test team. Are there existing test cases that we can run to test live migration, to make sure that it 1) works in stx.2019.10 and fails in the current builds? Thanks! Brucej [0] https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Feb 14 19:38:00 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 14 Feb 2019 19:38:00 +0000 Subject: [Starlingx-discuss] upstream Nova NUMA live migration work In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7CD73BA9@FMSMSX114.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD0D3C@fmsmsx121.amr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CD73BA9@FMSMSX114.amr.corp.intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3AD0F04@fmsmsx121.amr.corp.intel.com> I fat fingered the release number in my note below :(. I'd like to know if those tests pass on the 2018.10 release - the one that has the StarlingX NUMA live migration patches. And I'd like to know what tests fail and how when we run the same tests today against the Stein feature branch that does not have those patches. I'd like to also know that if/when the current upstream Nova work completes, do we pass the tests when we run a version of StarlingX that includes those changes. brucej From: Cabrales, Ada Sent: Thursday, February 14, 2019 11:25 AM To: Jones, Bruce E ; Rowsell, Brent ; Friesen, Chris Cc: starlingx-discuss at lists.starlingx.io Subject: RE: upstream Nova NUMA live migration work Yes, we have tests that can verify live migration + NUMA. I didn't understand the last part of your question: you want to run those test cases (on a containers config) and verify those don't work, then try those into the stx.2019.10 (October this year)? A. From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, February 14, 2019 12:57 PM To: Rowsell, Brent >; Friesen, Chris > Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] upstream Nova NUMA live migration work It looks like there is work moving forward in the Nova community on this topic. There are active and recent code submissions in review here: [0]. Brent, Chris - I have some questions for you. Are you aware of these reviews? Are you planning to review the code? More importantly, does this code meet StarlingX's needs - is it heading in the right direction for us? If not, how and where might we want to influence where the work is going? I have one other ask, for the Test team. Are there existing test cases that we can run to test live migration, to make sure that it 1) works in stx.2019.10 and fails in the current builds? Thanks! Brucej [0] https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged) -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Feb 14 19:40:32 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 14 Feb 2019 20:40:32 +0100 Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> Message-ID: <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> Hi Don, which build do you recommend? Is there a workaround so I can keep my installation for now? Thanks Marcel Von meinem iPhone gesendet > Am 14.02.2019 um 19:50 schrieb Penney, Don : > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > * problems with the lighttpd server on the active controller > * NICs that are unsupported by the initrd kernel modules > * some other comms issue > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Thursday, February 14, 2019 1:40 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi, > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > Console log: > ============= > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > [ OK ] Started Show Plymouth Boot Screen. > [ OK ] Started Device-Mapper Multipath Device Controller. > Starting Open-iSCSI... > [ OK ] Reached target Paths. > [ OK ] Reached target Basic System. > [ OK ] Started Open-iSCSI. > Starting dracut initqueue hook... > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > ... > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [Warning: /dev/root does not exist > > Generating "/run/initramfs/rdsosreport.txt" > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > after mounting them and attach it to a bug report. > > dracut:/# > > Kernel parameter: > ================== > > dracut:/# journalctl | grep -i boot > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > ======= > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > Any idea is welcome! > > Thanks > > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From ada.cabrales at intel.com Thu Feb 14 19:43:40 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Thu, 14 Feb 2019 19:43:40 +0000 Subject: [Starlingx-discuss] upstream Nova NUMA live migration work In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD0F04@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD0D3C@fmsmsx121.amr.corp.intel.com> <4F6AACE4B0F173488D033B02A8BB5B7E7CD73BA9@FMSMSX114.amr.corp.intel.com> <9A85D2917C58154C960D95352B22818BC3AD0F04@fmsmsx121.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD73BF1@FMSMSX114.amr.corp.intel.com> That's better :) Yes, we can run on a stx.2018.10 image the tests. We haven't try a setup with stein: we've been working with master. However, this is next in the list. Would it be OK to begin with that next week? A. From: Jones, Bruce E Sent: Thursday, February 14, 2019 1:38 PM To: Cabrales, Ada ; Rowsell, Brent ; Friesen, Chris Cc: starlingx-discuss at lists.starlingx.io Subject: RE: upstream Nova NUMA live migration work I fat fingered the release number in my note below :(. I'd like to know if those tests pass on the 2018.10 release - the one that has the StarlingX NUMA live migration patches. And I'd like to know what tests fail and how when we run the same tests today against the Stein feature branch that does not have those patches. I'd like to also know that if/when the current upstream Nova work completes, do we pass the tests when we run a version of StarlingX that includes those changes. brucej From: Cabrales, Ada Sent: Thursday, February 14, 2019 11:25 AM To: Jones, Bruce E >; Rowsell, Brent >; Friesen, Chris > Cc: starlingx-discuss at lists.starlingx.io Subject: RE: upstream Nova NUMA live migration work Yes, we have tests that can verify live migration + NUMA. I didn't understand the last part of your question: you want to run those test cases (on a containers config) and verify those don't work, then try those into the stx.2019.10 (October this year)? A. From: Jones, Bruce E [mailto:bruce.e.jones at intel.com] Sent: Thursday, February 14, 2019 12:57 PM To: Rowsell, Brent >; Friesen, Chris > Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] upstream Nova NUMA live migration work It looks like there is work moving forward in the Nova community on this topic. There are active and recent code submissions in review here: [0]. Brent, Chris - I have some questions for you. Are you aware of these reviews? Are you planning to review the code? More importantly, does this code meet StarlingX's needs - is it heading in the right direction for us? If not, how and where might we want to influence where the work is going? I have one other ask, for the Test team. Are there existing test cases that we can run to test live migration, to make sure that it 1) works in stx.2019.10 and fails in the current builds? Thanks! Brucej [0] https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Thu Feb 14 19:45:00 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 14 Feb 2019 19:45:00 +0000 Subject: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA65301@ALA-MBD.corp.ad.wrs.com> I'd like to add Kevin Smith as a core reviewer for stx-nfv. Kevin has been contributing to the stx-nfv project since it was created and has been both a valuable reviewer and code author. I'd like confirmation (or objections) from the existing cores please... Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Thu Feb 14 19:45:53 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Thu, 14 Feb 2019 19:45:53 +0000 Subject: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA65301@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA65301@ALA-MBD.corp.ad.wrs.com> Message-ID: +1 From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Thursday, February 14, 2019 2:45 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core I'd like to add Kevin Smith as a core reviewer for stx-nfv. Kevin has been contributing to the stx-nfv project since it was created and has been both a valuable reviewer and code author. I'd like confirmation (or objections) from the existing cores please... Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Feb 14 19:48:48 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Feb 2019 19:48:48 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DAC9@ALA-MBD.corp.ad.wrs.com> Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues. -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Thursday, February 14, 2019 2:41 PM To: Penney, Don Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi Don, which build do you recommend? Is there a workaround so I can keep my installation for now? Thanks Marcel Von meinem iPhone gesendet > Am 14.02.2019 um 19:50 schrieb Penney, Don : > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > * problems with the lighttpd server on the active controller > * NICs that are unsupported by the initrd kernel modules > * some other comms issue > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Thursday, February 14, 2019 1:40 PM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi, > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > Console log: > ============= > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > [ OK ] Started Show Plymouth Boot Screen. > [ OK ] Started Device-Mapper Multipath Device Controller. > Starting Open-iSCSI... > [ OK ] Reached target Paths. > [ OK ] Reached target Basic System. > [ OK ] Started Open-iSCSI. > Starting dracut initqueue hook... > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > ... > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > [Warning: /dev/root does not exist > > Generating "/run/initramfs/rdsosreport.txt" > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > after mounting them and attach it to a bug report. > > dracut:/# > > Kernel parameter: > ================== > > dracut:/# journalctl | grep -i boot > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > ======= > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > Any idea is welcome! > > Thanks > > Marcel > > _______________________________________________ > 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 Thu Feb 14 19:59:51 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 14 Feb 2019 14:59:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 149 - Failure! Message-ID: <1581176458.33.1550174393521.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 149 Status: Failure Timestamp: 20190214T182011Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190214T150726Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-centos76/20190214T150726Z DOCKER_BUILD_ID: jenkins-f-centos76-20190214T150726Z-builder MY_REPO: /localdisk/designer/jenkins/f-centos76/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190214T150726Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos76/centos/20190214T150726Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos76 From build.starlingx at gmail.com Thu Feb 14 19:59:56 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 14 Feb 2019 14:59:56 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_centos76_pike - Build # 1 - Failure! Message-ID: <785911781.36.1550174397483.JavaMail.javamailuser@localhost> Project: STX_build_centos76_pike Build #: 1 Status: Failure Timestamp: 20190214T150726Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190214T150726Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From Don.Penney at windriver.com Thu Feb 14 20:55:43 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Feb 2019 20:55:43 +0000 Subject: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core In-Reply-To: References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA65301@ALA-MBD.corp.ad.wrs.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DB89@ALA-MBD.corp.ad.wrs.com> +1 from me, as well. Kevin has done a lot of work in the stx-nfv repo. From: Bailey, Henry Albert (Al) [mailto:Al.Bailey at windriver.com] Sent: Thursday, February 14, 2019 2:46 PM To: Wensley, Barton; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core +1 From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Thursday, February 14, 2019 2:45 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Nominate Kevin Smith as stx-nfv core I'd like to add Kevin Smith as a core reviewer for stx-nfv. Kevin has been contributing to the stx-nfv project since it was created and has been both a valuable reviewer and code author. I'd like confirmation (or objections) from the existing cores please... Bart -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Feb 14 21:14:02 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 14 Feb 2019 21:14:02 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190214 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9B9E0@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-14 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 22 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Thu Feb 14 21:25:04 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Thu, 14 Feb 2019 21:25:04 +0000 Subject: [Starlingx-discuss] Unable to Modify StarlingX Wiki Page Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4827423B@ALA-MBD.corp.ad.wrs.com> Hi Bruce and Abraham, There are few pages on StarlingX wiki that are locked and cannot be modified. We were looking for adding some instructions on Wiki and the page where we want to make the changes are locked. In specific, I would like to add some instructions under Documentation page and the pages under it are locked. Can you please give me (Numan Waheed, email: numan.waheed at windriver.com) and Yang Liu (email: yang.liu at windriver.com) privileges to update these pages. If you are not the right person to provide this privilege, please let me know who can do it. Thanks, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Feb 14 21:39:39 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 14 Feb 2019 21:39:39 +0000 Subject: [Starlingx-discuss] Unable to Modify StarlingX Wiki Page In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4827423B@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE4827423B@ALA-MBD.corp.ad.wrs.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3AD100C@fmsmsx121.amr.corp.intel.com> Ildiko, can you help please? From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] Sent: Thursday, February 14, 2019 1:25 PM To: starlingx-discuss at lists.starlingx.io; Jones, Bruce E ; Arce Moreno, Abraham Cc: Liu, Yang Subject: Unable to Modify StarlingX Wiki Page Hi Bruce and Abraham, There are few pages on StarlingX wiki that are locked and cannot be modified. We were looking for adding some instructions on Wiki and the page where we want to make the changes are locked. In specific, I would like to add some instructions under Documentation page and the pages under it are locked. Can you please give me (Numan Waheed, email: numan.waheed at windriver.com) and Yang Liu (email: yang.liu at windriver.com) privileges to update these pages. If you are not the right person to provide this privilege, please let me know who can do it. Thanks, Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Feb 14 23:22:25 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 14 Feb 2019 23:22:25 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190214 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9BA3C@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-14 (link) Sanity Test is executed in a Containers - Virtual Environment Status: YELLOW Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 36 TCs [PASS] | 1 TC [FAIL] Sanity Platform In Development TOTAL: [ 36 TCs PASS | 1 TC FAIL ] ------------------------------------------------------------------ Ceilometer command does not retrieve output. Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1815976 ------------------------------------------------------------------ List of test cases executed: Test Scenario Test Case Status Instances-From-Image Create Flavors for Instances PASS Create Images for Instances PASS Create Networks for Instances PASS Launch Instances PASS Suspend Resume Instances PASS Set Error Active Flags Instances PASS Pause Unpause Instances PASS Stop Start Instances PASS Lock Unlock Instances PASS Reboot Instance PASS Rebuild Instances PASS Resize Instances PASS Set Unset Properties Instances PASS Instances-From-Volume Create Flavors for Instances PASS Create Images for Instances PASS Create Networks for Instances PASS Create Volume for Instances PASS Launch Instances PASS Suspend Resume Instances PASS Set Error Active Flags Instances PASS Pause Unpause Instances PASS Stop Start Instances PASS Lock Unlock Instances PASS Reboot Instance PASS Rebuild Instances PASS Resize Instances PASS Set Unset Properties Instances PASS test_openstack_services_healthy PASS test_reapply_stx_openstack PASS test_stx_openstack_helm_override_update_and_reset PASS test_horizon_create_delete_instance PASS test_heat_template PASS test_add_host_simplex_negative PASS test_measurements_for_metric PASS test_ceilometer_meters_exist FAIL test_vm_meta_data_retrieval PASS test_nova_actions PASS Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Feb 13 15:56:39 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 13 Feb 2019 15:56:39 +0000 Subject: [Starlingx-discuss] Community meeting Feb 13th notes Message-ID: <9A85D2917C58154C960D95352B22818BBFD271D9@fmsmsx123.amr.corp.intel.com> Agenda and notes for the Feb 13th call * Bruce will be OOO next week. Can someone else chair this meeting? [Bill Z volunteers] * The outreach working group has the following suggestions for things we'd like to see to help community outreach * A "getting started" SIG / sub-project to help new contributors get up to speed * Office hours on IRC * Marking LP/SB entries that are simple/easy to also help new contributors ? Mark stories with "stx.easy" or similar? Use stx.help.wanted - Bill to look for bugs to label * This is something many projects do, especially in github where labelling is quite easy, eg. Kata Containers, "help wanted" - https://github.com/kata-containers/runtime/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22 * Would need people who know what issues/bugs/features in all the projects are good for new contributors to label them, and then have somewhere that those labels are linked from (perhaps off the main website?). ? Define new stories for easy but not yet staffed efforts e.g. Unit Testing? ? Posting a todo list? ? Ask each sub-project to identify easy work items in their domains? * A series of blog posts in the OSF blog about the new features in the May release (to be posted post May) ? e.g containers, distributed cloud, CentOS 7.6, Ceph 13, etc... ? Brent to write a container blog. * Meanwhile please do everything you can to spread the word about StarlingX within your company and communities, to welcome new community members to the project and help make them successful. * Abraham will help. Curtis too. * Our wiki needs updating. Any objections to me (Bruce) doing some major refactoring? None heard :) * Open Infrastructure Summit and PTG planning (ildikov) * Forum session proposal planning: ? https://wiki.openstack.org/wiki/Forum ? https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 * PTG planning: ? http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003057.html ? https://etherpad.openstack.org/p/stx-ptg-preparation-denver-2019 * Open ARs from Mini-PTG https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-RnUQoyc4/edit?usp=sharing * Sub-project updates: * Release (Ghada) ? stx.209.05 Release Gating Bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.2019.05 ? The bug trend is upward :( ? see updated trend line at https://docs.google.com/spreadsheets/d/1DZZgqrCIL6wxv51_yFBk6Lfmtf1AqPD6z7e5hEs3prU/edit?usp=sharing * Containers (Frank) - are we getting a Valentine's Day present? :) ? Team working very hard on 3 gating issues - will not make tomorrow. Day by day. * 4 high priority LPs to be addressed (one may close) * docker mirror story board needs to merge - pending on Mingyuan's review * Sanity results from Ada's team - looking for them to come out tommorrow. * please use stx.containers for any new issues so the team can find them! * Security (Ken) ? work in progress on CVE scans (as per ARs above) ? Github is doing security scans of our repos there. Ken getting them indirectly. Dean to help see if we can add recipients * Ceph upgrade (Vivian) ? Team discussing how to divide and conquer the remaining work. Key team members still on CNY. * CentOS upgrade (Cindy) ? First run of tests done by Ada and Numan's team. UEFI issue found which blocked some testing. Fixed, second run of testing can proceed. ? Plan is to merge Feb 22nd but might be delayed due to test cycle. * Networking (Ghada) ? Continue to push on neutron upstreaming. Working on OVS in a container. * Docs (Michael / Bruce) ? Mega-spec working through the approval process. WR has contributed some additional seed documents, thank you! * Build (Cesar) ? Build is fairly stable, no issues expected for container cut-over * Dist-Cloud (Dariush) ? Looking for issues that need resolution that might be caused by the container changes. * Test (Ada) ? See above :) Work continues to review the regression suite and decide which tests can be kept and which need to change. * Multi-OS (Cesar) ? We had an _interesting_ meeting on Monday and reset expectations for what we want to do for May. Multi-OS spec has been updated and the team is looking for review and feedback! -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Feb 14 14:56:14 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 14 Feb 2019 09:56:14 -0500 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> Message-ID: <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: > > Hi Shuicheng, > > I checked the 3 items as per your instructions, build log does contain > the expected step, however the results are different. > > @ Scott/Don, any thoughts on this? > > 1.+ install -D -m 755 grubx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi > > 2.-rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi > > 3.-rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi > > BR, > > Yang > > *From:*Lin, Shuicheng [mailto:shuicheng.lin at intel.com] > *Sent:* February-14-19 2:32 AM > *To:* Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin > *Cc:* starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, > Numan; Little, Scott > *Subject:* RE: CentOS7.6 testing status - blocked > > Hi Yang/Don, > > We double checked the issue today. Here is our finding: > > 1.I try to revert the fix [0], then do build-pkgs and build-iso, the > “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 > permission mode. > > Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” > is changed to 755 permission mode. > > I also checked the grubx64.efi file in both ISO image, it has the same > mode as upper file. > > 2.Martin confirmed there is tftp log in the deployment: > > “ > > 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent > /pxeboot/EFI/grubx64.efi to 169.254.202.76 > > controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi  -l > > -rwxr-xr-x. 1 root root 1234192 Feb  3 06:52 /pxeboot/EFI/grubx64.efi > > “ > > 3.Austin confirmed “install -D -m 755” will set the grubx64.efi with > 755 permission mode. > > “ > > -m, --mode=MODE > > set permission mode (as in chmod), instead of rwxr-xr-x > > “ > > 4.I try to go through the build log. Here is the log from grub2’s > build.log > > “ > > + install -m 700 grubx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned > > + install -m 700 gcdx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned > > + install -D -m 755 grubx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi > > + install -m 700 grubx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi > > + install -m 700 gcdx64.efi > /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi > > “ > > And in build-iso script, the file will be extracted and copied to the > EFI folder: > > “ > > extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} > grub2-efi-x64-pxeboot > > … > > \cp --preserve=all pxeboot/EFI/grubx64.efi > $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ > > “ > > Due to we cannot reproduce the issue, we are not sure which step cause > the issue yet. > > So could you help me have a check with below step to narrow down the > issue? Thanks. > > 1.Please help check whether there is “install -D -m 755 grubx64.efi” > in the > “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” > or not. > > 2.Please help extract > “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in > “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file > is with 755 mode or not. > > Extract cmd: rpm2cpio > grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv > > 3.Please help check the “grubx64.efi” in > “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. > > [0]: https://review.openstack.org/634559 > > > Best Regards > > Shuicheng > > *From:* Penney, Don [mailto:Don.Penney at windriver.com] > *Sent:* Thursday, February 14, 2019 6:01 AM > *To:* Xie, Cindy ; Liu, Yang > *Cc:* starlingx-discuss at lists.starlingx.io; Cabrales, Ada > ; Waheed, Numan ; > Little, Scott > *Subject:* Re: [Starlingx-discuss] CentOS7.6 testing status - blocked > > Hi Cindy, > > In a successful case, you should see a TFTP log in daemon.log on the > active controller indicating the file was transferred, such as: > > 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent > /pxeboot/EFI/grubx64.efi to 192.168.204.4 > > I would suggest doing something like “tail -f /var/log/daemon.log | > grep -i tftp” while doing the installation of nodes from the active > controller, to verify the expected file is getting transferred. If the > host installs and you don’t see this file transferred, I’d recommend > reconfirming that the node is installing via UEFI. > > *From:*Xie, Cindy [mailto:cindy.xie at intel.com] > *Sent:* Wednesday, February 13, 2019 4:46 PM > *To:* Liu, Yang > *Cc:* starlingx-discuss at lists.starlingx.io > ; Cabrales, Ada; Waheed, > Numan; Little, Scott > *Subject:* Re: [Starlingx-discuss] CentOS7.6 testing status - blocked > > Hi, Yang > > Sorry about the issue! It’s interesting as I did have my engineer > tested the scenarios. There must be something missing from my side. > > We will redo the patch and test. In the same time, can you manually > change the file permissions as temporarily workaround and unblock the > test cycle? > > Thanks! Cindy > > Sent from my iPhone > > > On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: > > Hi Cindy, > > We are still seeing the same file permission issue for grubx64.efi > under pxeboot/EFI, causing UEFI pxeboot to fail. > > We need the grubx64.efi to be readable by others as well. > > ../pxeboot/EFI/ > > total 1220 > > drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 . > > drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 .. > > drwxrwsr-x 3 jenkins mock    4096 Feb 12 16:48 centos > > -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi > > The patch seems to have changed the dir permission for centos from > 700 to 755, but not grubx64.efi. > > For the dir permission for centos, I believe the original 700 > should be sufficient (@Scott, please correct me if it’s wrong). > > BR, > > Yang > > *From:*Liu, Yang > *Sent:* February-12-19 9:00 AM > *To:* 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io > ; Cabrales, Ada; > Waheed, Numan > *Subject:* RE: CentOS7.6 testing status - blocked > > Thanks Cindy. Will do. > > BR, > > Yang > > *From:*Xie, Cindy [mailto:cindy.xie at intel.com] > *Sent:* February-11-19 8:10 PM > *To:* Liu, Yang; starlingx-discuss at lists.starlingx.io > ; Cabrales, Ada; > Waheed, Numan > *Subject:* RE: CentOS7.6 testing status - blocked > > Hi, Numan/Yang, > > The last pending patch (https://review.openstack.org/#/c/634559/) > which was blocking your testing (#1814360) was just merged. Please > get new build ISO from Jason so you can continue the testing. > > Thx. - cindy > > *From:* Liu, Yang [mailto:yang.liu at windriver.com] > *Sent:* Saturday, February 9, 2019 10:18 AM > *To:* Xie, Cindy >; > starlingx-discuss at lists.starlingx.io > > *Subject:* RE: CentOS7.6 testing status - blocked > > Correct. > > BR, > > Yang > > *From:*Xie, Cindy [mailto:cindy.xie at intel.com] > *Sent:* February-08-19 8:28 PM > *To:* Liu, Yang; starlingx-discuss at lists.starlingx.io > > *Subject:* RE: CentOS7.6 testing status - blocked > > Hi, Yang, > > Thanks for the report. > > Are the “two node system” below referring to Duplex? Just want to > confirm because #1814360 we have a patch pending and we do want to > ensure it works on Duplex as well. > > Th.x - cindy > > *From:* Liu, Yang [mailto:yang.liu at windriver.com] > *Sent:* Saturday, February 9, 2019 2:09 AM > *To:* starlingx-discuss at lists.starlingx.io > > *Subject:* [Starlingx-discuss] CentOS7.6 testing status - blocked > > Hi folks, > > Here’s an update for CentOS7.6 testing. > > We are currently blocked due to pxeboot from controller-0 does not > work for EFI. (#1814360) > > We will continue after that issue is resolved. > > System > > > > NICs > > Mgmt;infra;data > > > > Special Configs > > > > Test coverage after Install and Config > > > > Status/Issues > > Dedicated storage > > > > X540-AT2; X540-AT2; fortville > > > > IPv6 > > > > Sanity, nova > > > > Completed. New issues logged. > > #1814336 CentOS7.6: Unable to launch vm directly from virsh > > > #1814335 CentOS7.6: Unable to launch vm with UEFI boot > > > One node system > > > > none; none; X522/X577-AT > > > > > > Sanity, basic regression > > > > Completed. Passed. > > Two node system > > > > fortville; fortville; fortville > > > > tboot, tpm, https, > > extended security profile > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > BCM5720; Niantic; Niantic > > > > Sriov(niantic),pcipt(niantic) > > > > Sanity, networking > > > > Completed. Passed. > > Two node system > > > > Fortville; none; Fortville > > > > Low latency, UEFI > > > > Sanity, basic regression, cyclictest > > > > Blocked by #1814360 > > Two node system > > > > Fortville; none; Fortville > > > > Secure boot > > > > Sanity, security > > > > Blocked by #1814360 > > Multi-node system > > > > I350; Niantic/cx3; cx3 > > > > Pxeboot script > > > > Sanity > > > > Completed. Passed. > > Only compute-0 was used, since compute-1 has CX3 data nic. > > ?? > > > > CX4 on infra or mgmt, but NOT data > > > > > > Won’t test. We don’t have a system have required nics. > > BR, > > yang > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Thu Feb 14 15:39:53 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 14 Feb 2019 15:39:53 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> Looking at our in-house jenkins build output, I see: $ rpm -qp --dump std/results/jenkins-STX_Feature_centos76_Build-2019-02-12_14-43-05-tis-r6-pike-std/grub2-2.02-0.76.el7.centos.tis.12/grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm /pxeboot/EFI/grubx64.efi 1233016 1550007456 3d0f3ae9293f23e1ebe6f56e1eb04fc6 0100700 root root 0 0 0 X Looking at the grub.macro file, which is providing the %install and %files directives, it certainly seems like this should be 755. The %defattr being set ignores the permissions. And I don’t see anything in the build.log that would indicate another chmod is happening after. From: Little, Scott Sent: Thursday, February 14, 2019 9:56 AM To: Liu, Yang; Lin, Shuicheng; Penney, Don; Xie, Cindy; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Fri Feb 15 00:05:55 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Fri, 15 Feb 2019 00:05:55 +0000 Subject: [Starlingx-discuss] Proposal: Build and Multi-OS strategy Message-ID: <9A85D2917C58154C960D95352B22818BC3AD11C1@fmsmsx121.amr.corp.intel.com> I would like to start a thread that I hope will result in more focus and direction for the Build and Multi-OS teams. It's right before I disappear for vacation, so I'll ask Saul and Cesar to address any follow-ups. What I would like to propose is that we as a community take on the task of delivering support for Ubuntu as a StarlingX host OS for the November 2019 release. This would allow us to support the ~35% of the cloud ecosystem that doesn't run on RHEL or CentOS. It will require a lot of work and therefore we should start as soon as possible. What I would propose we do is: 1) The Build team to create a new and separate build system for an Ubuntu LTS hosted ISO [0] 2) The MultiOS team to review the outstanding carried patches and apply those needed to the Ubuntu packages 3) The MultiOS team to update the system as needed to use an Ubuntu installer to get controller-0 fully installed 4) Which would then lead to work in the MultiOS team to bring up the Ubuntu hosted StarlingX in Simplex mode [1]. We would then have a (kind of) working StarlingX image that will enable the broader community to contribute to all of the other work needed to deliver a fully supported Ubuntu host for the November release. That work would include bringing up the other configurations beyond Simplex, changes to the StarlingX software management and update services, the additional testing needed, and other tasks which can be parallelized. Meanwhile, on the Intel side we have received new guidance from our new management on the requirement for Clear Linux support. We will continue but slow down that work for now and focus on Ubuntu. So for November, the goal is to support 2 Host OS's, not 3. We will need support and contributions from the community to achieve this goal in time for November. The MultiOS team in particular will need help and additional contribtutors. Brucej [0] Making the build system common between Ubuntu and CentOS is hard and probably should not be attempted. We should leverage what we can, of course, from our own code and the broader ecosystem. [1] Or in which ever configuration is easier.... -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Feb 15 01:07:36 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 14 Feb 2019 20:07:36 -0500 Subject: [Starlingx-discuss] Proposal: Build and Multi-OS strategy In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD11C1@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD11C1@fmsmsx121.amr.corp.intel.com> Message-ID: On Thu, Feb 14, 2019 at 7:07 PM Jones, Bruce E wrote: > I would like to start a thread that I hope will result in more focus and > direction for the Build and Multi-OS teams. It’s right before I disappear > for vacation, so I’ll ask Saul and Cesar to address any follow-ups. > > > > What I would like to propose is that we as a community take on the task of > delivering support for Ubuntu as a StarlingX host OS for the November 2019 > release. This would allow us to support the ~35% of the cloud ecosystem > that doesn’t run on RHEL or CentOS. > > > > It will require a lot of work and therefore we should start as soon as > possible. What I would propose we do is: > > 1) The Build team to create a new and separate build system for an > Ubuntu LTS hosted ISO [0] > > 2) The MultiOS team to review the outstanding carried patches and > apply those needed to the Ubuntu packages > > 3) The MultiOS team to update the system as needed to use an Ubuntu > installer to get controller-0 fully installed > > 4) Which would then lead to work in the MultiOS team to bring up the > Ubuntu hosted StarlingX in Simplex mode [1]. > > > > We would then have a (kind of) working StarlingX image that will enable > the broader community to contribute to all of the other work needed to > deliver a fully supported Ubuntu host for the November release. That > work would include bringing up the other configurations beyond Simplex, > changes to the StarlingX software management and update services, the > additional testing needed, and other tasks which can be parallelized. > > > > Meanwhile, on the Intel side we have received new guidance from our new > management on the requirement for Clear Linux support. We will continue > but slow down that work for now and focus on Ubuntu. So for November, > the goal is to support 2 Host OS’s, not 3. > > > > We will need support and contributions from the community to achieve this > goal in time for November. The MultiOS team in particular will need help > and additional contribtutors. > I think something has to change, as I personally view the multios direction as a bit risky for the project overall. I don't mean that it shouldn't be done, but that it carries some measure of risk and that risk has to be taken into consideration. (Of course, I'm not privy to any previous discussions on the topic as I'm new to the project.) That said I can't quantify the risk in any meaningful way, other than to say it's a gut reaction from somewhat of an outsider. :) I certainly like the idea of simplifying in some way. As well I think it's important to admit when things might be getting too complex--I believe there are some hidden dependencies out there. I look forward to hearing other peoples thoughts and ideas in this thread! Thanks, Curtis > > > Brucej > > > > [0] Making the build system common between Ubuntu and CentOS is hard and > probably should not be attempted. We should leverage what we can, of > course, from our own code and the broader ecosystem. > > [1] Or in which ever configuration is easier…. > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Feb 15 00:59:01 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 15 Feb 2019 00:59:01 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8561F1532@CDSMSX102.ccr.corp.intel.com> I check this command in my build machine [hellen at 5b2f0e3259aa starlingx]$ [hellen at 5b2f0e3259aa starlingx]$ rpm -qp --dump std/results/hellen-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm /pxeboot/EFI/grubx64.efi 1234192 1549176759 783bd7e57e64d8a74f1c44849e51f76a2fd3062f7b81071053edf3f3771c2d43 0100755 root root 0 0 0 X [hellen at 5b2f0e3259aa starlingx]$ When I build iso, I follow these steps, Shuicheng used to share to me. 1, build-pkgs ; build-iso ; build-srpms --installer ; build-rpms --installer ; build-iso ; update-pxe-network-installer 2, copy generated vmlinuz, squashfs.img, initrd.img to /import/mirror/CentOS/stx-installer/ (depends on pxe-network-installer.spec) 3, build-pkgs ; build-iso Maybe we could root cause, what’s the difference. BR! Martin, Chen SSP, Software Engineer 021-61164330 From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 11:40 PM To: Little, Scott ; Liu, Yang ; Lin, Shuicheng ; Xie, Cindy ; Chen, Haochuan Z ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Looking at our in-house jenkins build output, I see: $ rpm -qp --dump std/results/jenkins-STX_Feature_centos76_Build-2019-02-12_14-43-05-tis-r6-pike-std/grub2-2.02-0.76.el7.centos.tis.12/grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm /pxeboot/EFI/grubx64.efi 1233016 1550007456 3d0f3ae9293f23e1ebe6f56e1eb04fc6 0100700 root root 0 0 0 X Looking at the grub.macro file, which is providing the %install and %files directives, it certainly seems like this should be 755. The %defattr being set ignores the permissions. And I don’t see anything in the build.log that would indicate another chmod is happening after. From: Little, Scott Sent: Thursday, February 14, 2019 9:56 AM To: Liu, Yang; Lin, Shuicheng; Penney, Don; Xie, Cindy; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Feb 15 02:08:41 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 15 Feb 2019 02:08:41 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE8486C@SHSMSX101.ccr.corp.intel.com> Hi Scott, What do you mean “installer rebuild”? Grub2 package is not included in “update-pxe-network-installer”. Could you share me more details? Thanks. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, February 14, 2019 10:56 PM To: Liu, Yang ; Lin, Shuicheng ; Penney, Don ; Xie, Cindy ; Chen, Haochuan Z ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From haochuan.z.chen at intel.com Fri Feb 15 02:14:15 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Fri, 15 Feb 2019 02:14:15 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE8486C@SHSMSX101.ccr.corp.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> <9700A18779F35F49AF027300A49E7C765FE8486C@SHSMSX101.ccr.corp.intel.com> Message-ID: <56829C2A36C2E542B0CCB9854828E4D8561F158A@CDSMSX102.ccr.corp.intel.com> I think Penny means we should explicityly add file attribute in such way? %{expand:%%files %{1}-pxeboot} \ %defattr(-,root,root,-) \ %attr(0755,root,root)/pxeboot/EFI/%{grubefiname} \ Wait for your comment. Thanks Martin, Chen SSP, Software Engineer 021-61164330 From: Lin, Shuicheng Sent: Friday, February 15, 2019 10:09 AM To: Scott Little ; Liu, Yang ; Penney, Don ; Xie, Cindy ; Chen, Haochuan Z ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi Scott, What do you mean “installer rebuild”? Grub2 package is not included in “update-pxe-network-installer”. Could you share me more details? Thanks. Best Regards Shuicheng From: Scott Little [mailto:scott.little at windriver.com] Sent: Thursday, February 14, 2019 10:56 PM To: Liu, Yang >; Lin, Shuicheng >; Penney, Don >; Xie, Cindy >; Chen, Haochuan Z >; Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada >; Waheed, Numan > Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Fri Feb 15 02:21:48 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 15 Feb 2019 02:21:48 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE84894@SHSMSX101.ccr.corp.intel.com> Hi Don, So it seems “%defattr” has different effect in your and our build system. Is my understanding correct? In grub.macros, “%defattr” just define the default user/group, the default permission is not set. It seems like an issue of the spec, what’s your suggestion to fix it? Thanks. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 11:40 PM To: Little, Scott ; Liu, Yang ; Lin, Shuicheng ; Xie, Cindy ; Chen, Haochuan Z ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Looking at our in-house jenkins build output, I see: $ rpm -qp --dump std/results/jenkins-STX_Feature_centos76_Build-2019-02-12_14-43-05-tis-r6-pike-std/grub2-2.02-0.76.el7.centos.tis.12/grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm /pxeboot/EFI/grubx64.efi 1233016 1550007456 3d0f3ae9293f23e1ebe6f56e1eb04fc6 0100700 root root 0 0 0 X Looking at the grub.macro file, which is providing the %install and %files directives, it certainly seems like this should be 755. The %defattr being set ignores the permissions. And I don’t see anything in the build.log that would indicate another chmod is happening after. From: Little, Scott Sent: Thursday, February 14, 2019 9:56 AM To: Liu, Yang; Lin, Shuicheng; Penney, Don; Xie, Cindy; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Fri Feb 15 09:23:24 2019 From: ildiko at openstack.org (Ildiko Vancsa) Date: Fri, 15 Feb 2019 10:23:24 +0100 Subject: [Starlingx-discuss] Unable to Modify StarlingX Wiki Page In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD100C@fmsmsx121.amr.corp.intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE4827423B@ALA-MBD.corp.ad.wrs.com> <9A85D2917C58154C960D95352B22818BC3AD100C@fmsmsx121.amr.corp.intel.com> Message-ID: <50986D35-FDCE-4471-92BB-C5365329DDF4@openstack.org> Hi Numan, As far as I know the StarlingX team has moved all their documentation into git and they render it from there to the Documentation web page: * http://git.starlingx.io/cgit/stx-docs/ * https://docs.starlingx.io If you would like to add modifications to the documentation you need to propose a patch to the documentation repository. If this is not what you tried to do, could you please link the exact wiki page and describe the operation you tried to make so I can look into what the issue might be? Thanks and Best Regards, Ildikó > On 2019. Feb 14., at 22:39, Jones, Bruce E wrote: > > Ildiko, can you help please? > > From: Waheed, Numan [mailto:Numan.Waheed at windriver.com] > Sent: Thursday, February 14, 2019 1:25 PM > To: starlingx-discuss at lists.starlingx.io; Jones, Bruce E ; Arce Moreno, Abraham > Cc: Liu, Yang > Subject: Unable to Modify StarlingX Wiki Page > > Hi Bruce and Abraham, > > There are few pages on StarlingX wiki that are locked and cannot be modified. We were looking for adding some instructions on Wiki and the page where we want to make the changes are locked. In specific, I would like to add some instructions under Documentation page and the pages under it are locked. > > Can you please give me (Numan Waheed, email: numan.waheed at windriver.com) and Yang Liu (email: yang.liu at windriver.com) privileges to update these pages. > > If you are not the right person to provide this privilege, please let me know who can do it. > > Thanks, > > Numan. From xiongzhiwei at baicells.com Fri Feb 15 10:32:07 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Fri, 15 Feb 2019 18:32:07 +0800 Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server References: , <20190202153337711807156@baicells.com> Message-ID: <20190215183206776070302@baicells.com> Hi Yong and Cindy, I had deployed successfully Simplex All-in-one on bear metal , the root cause is error RAID configuration and caused incompatible hard disks. Thanks BR Tim Xiong From: xiongzhiwei at baicells.com Date: 2019-02-02 15:33 To: Hu, Yong; Xie, Cindy; starlingx-discuss Subject: Re: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Yong, puppet.log attached. Thanks From: Hu, Yong Date: 2019-02-02 15:10 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Pls share us your /var/log/puppet/latest/puppet.log. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 3:07 PM To: "xiongzhiwei at baicells.com" , "Hu, Yong" , "Xie, Cindy" , starlingx-discuss Subject: Re: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Yong and Cindy, The same error appeared after removed these two sata disks. Thanks Tim From: xiongzhiwei at baicells.com Date: 2019-02-02 14:34 To: Hu, Yong; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Thanks Hu Yong and Cindy, I am trying to again after remove these two SATA HD. Will tell you once successed. Regards Tim From: Hu, Yong Date: 2019-02-02 14:27 To: xiongzhiwei at baicells.com; Xie, Cindy; starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server If using 240G SATA HD as the boot disk, the storage might not be enough. At least, in our virtual environment, the boot disk has to be larger than 250 GB. From: "xiongzhiwei at baicells.com" Date: Saturday, 2 February 2019 at 2:17 PM To: "Xie, Cindy" , starlingx-discuss Subject: Re: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi Cindy, This image was build by myself, fetched on 24th Jan. It is working normally in my VM enviroment but failed on the bear metal server. My server is Huawei RH2288v3: E5-2630 v3 at 2.4GHz, 2*8cores, 16*8G DDR4 RAM, 2*900G SAS+2*240G SATA HD. Thanks Tim Xiong From: Xie, Cindy Date: 2019-02-02 13:00 To: xiongzhiwei at baicells.com; starlingx-discuss Subject: RE: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server HI, Tim, Can you please provide the following info: - Exact version of the StarlingX: if you downloaded it from Cengen, please provide the link; if you built it by yourself, please provide the date on master. - Your HW config for your bare metal server. Our recommended HW config can be found here: https://docs.starlingx.io/installation_guide/index.html Thanks. - cindy From: xiongzhiwei at baicells.com [mailto:xiongzhiwei at baicells.com] Sent: Saturday, February 2, 2019 12:38 PM To: starlingx-discuss Subject: [Starlingx-discuss] EXT-fs error when deploying staringx on bearmetal server Hi, I am trying to deploy starlingx on a bearmetal server, but failed, After execute "sudo config_controller" and some default configuration confirmed(all-in-one, simplex), exception printed as below: 01/08: Creating bootstrap configuration ... DONE 02/08: Applying bootstrap manifest ... [ 452.567312] EXT4-fs error (device drbd1): ext4_journal_check_start:56: Detected aborted journal [ 452.576753] EXT4-fs (drbd1): Remounting filesystem read-only [ 466.880792] EXT4-fs error (device drbd3): ext4_journal_check_start:56: Detected aborted journal [ 466.886032] EXT4-fs (drbd3): Remounting filesystem read-only [ 479.755269] EXT4-fs error (device drbd0): ext4_journal_check_start:56: Detected aborted journal [ 479.760818] EXT4-fs (drbd0): Remounting filesystem read-only [ 479.766425] EXT4-fs (drbd0): ext4_writepages: jbd2_start: 13312 pages, ino 28; err -30 Failed to execute bootstrap manifest Configuration failed: failed to apply bootstrap manifest. See /var/log/puppet/latest/puppet.log for details. I had deployed successfully on a qemu VM with same image, also all-in-one and simplex. Is there any configurations missed for the bear metal server? I had recovered all BIOS configurations to default for it. Could anyone help me to fix it? Thanks BR Tim Xiong -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Feb 15 13:23:47 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 15 Feb 2019 08:23:47 -0500 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: References: Message-ID: On Thu, Feb 14, 2019 at 12:51 PM Saul Wold wrote: > > Folks, > > I was doing some experimentation with an un-patched CentOS and running > config_controller. One of the main issues I found is that doing the > initial installation and execution discovered many un-resolved runtime > requirements. > Thanks for looking into this Saul, I think this is a good thing to do to work towards getting a understanding of dependencies. > > I will start sending some pull requests to fault, metal, and config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding openstack-keystone > among other openstack related packages with additional configuration and > scripts, which are needed for controller-0. In the stx-integ (base OS) > case, we re-factored many of the packages to remove configuration and > additional scripts to a separate package, I would like to see something > similar here for packages are are needed for controller-0 (ie the things > we are not installing from PyPi directly). > Do we install things directly from PyPi? When does that happen? > What I saw is that we include the CentOS-Openstack RPM repo along with, > of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack > packages directly along with some StarlingX specific additions in a > seperate package, rather than creating a new package with both upstream > and StarlingX content. > > I don't know what the extra things are that we are packaging, but if they are only helper scripts and the like and don't affect the actual keystone code then I'd hope we would use the upstream RPMs. My two cents. :) Thanks, Curtis > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Feb 15 15:12:02 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 15 Feb 2019 15:12:02 +0000 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: References: Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> Comments inline. From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 8:24 AM To: Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Thu, Feb 14, 2019 at 12:51 PM Saul Wold > wrote: Folks, I was doing some experimentation with an un-patched CentOS and running config_controller. One of the main issues I found is that doing the initial installation and execution discovered many un-resolved runtime requirements. Thanks for looking into this Saul, I think this is a good thing to do to work towards getting a understanding of dependencies. I will start sending some pull requests to fault, metal, and config with more detailed "Requires:" statements. Another item is that since that we are rebuilding openstack-keystone among other openstack related packages with additional configuration and scripts, which are needed for controller-0. In the stx-integ (base OS) case, we re-factored many of the packages to remove configuration and additional scripts to a separate package, I would like to see something similar here for packages are are needed for controller-0 (ie the things we are not installing from PyPi directly). Do we install things directly from PyPi? When does that happen? [Don] No, we don’t install anything from PyPi. What I saw is that we include the CentOS-Openstack RPM repo along with, of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack packages directly along with some StarlingX specific additions in a seperate package, rather than creating a new package with both upstream and StarlingX content. I don't know what the extra things are that we are packaging, but if they are only helper scripts and the like and don't affect the actual keystone code then I'd hope we would use the upstream RPMs. [Don] As much as possible, we look to use unmodified upstream RPMs. My two cents. :) Thanks, Curtis Thoughts, Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Feb 15 15:18:46 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 15 Feb 2019 10:18:46 -0500 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, Feb 15, 2019 at 10:12 AM Penney, Don wrote: > Comments inline. > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 8:24 AM > *To:* Saul Wold > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > On Thu, Feb 14, 2019 at 12:51 PM Saul Wold wrote: > > > Folks, > > I was doing some experimentation with an un-patched CentOS and running > config_controller. One of the main issues I found is that doing the > initial installation and execution discovered many un-resolved runtime > requirements. > > > > Thanks for looking into this Saul, I think this is a good thing to do to > work towards getting a understanding of dependencies. > > > > > I will start sending some pull requests to fault, metal, and config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding openstack-keystone > among other openstack related packages with additional configuration and > scripts, which are needed for controller-0. In the stx-integ (base OS) > case, we re-factored many of the packages to remove configuration and > additional scripts to a separate package, I would like to see something > similar here for packages are are needed for controller-0 (ie the things > we are not installing from PyPi directly). > > > > Do we install things directly from PyPi? When does that happen? > > *[Don] No, we don’t install anything from PyPi.* > Thanks. Good to know. :) > > > > What I saw is that we include the CentOS-Openstack RPM repo along with, > of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack > packages directly along with some StarlingX specific additions in a > seperate package, rather than creating a new package with both upstream > and StarlingX content. > > > > I don't know what the extra things are that we are packaging, but if they > are only helper scripts and the like and don't affect the actual keystone > code then I'd hope we would use the upstream RPMs. > > *[Don] As much as possible, we look to use unmodified upstream RPMs.* > Can you expand on that statement in the context of this particular RPM? (Sorry I'm not familiar with what we are doing with Keystone.) Thanks, Curtis > > > My two cents. :) > > > > Thanks, > > Curtis > > > > > > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Fri Feb 15 15:42:06 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 15 Feb 2019 15:42:06 +0000 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> A few points to keep in mind here: 1) Config_controller is being removed and replaced with ansible. 2) Openstack deployment will not be part of the initial controller bootstrapping. Openstack will be deployed in containers. 3) We are in the process of moving to vanilla openstack. Brent From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 10:19 AM To: Penney, Don Cc: Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > wrote: Comments inline. From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 8:24 AM To: Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Thu, Feb 14, 2019 at 12:51 PM Saul Wold > wrote: Folks, I was doing some experimentation with an un-patched CentOS and running config_controller. One of the main issues I found is that doing the initial installation and execution discovered many un-resolved runtime requirements. Thanks for looking into this Saul, I think this is a good thing to do to work towards getting a understanding of dependencies. [BR] Keep in mind config_controller is being removed and being replaced with ansible. The bootsta I will start sending some pull requests to fault, metal, and config with more detailed "Requires:" statements. Another item is that since that we are rebuilding openstack-keystone among other openstack related packages with additional configuration and scripts, which are needed for controller-0. In the stx-integ (base OS) case, we re-factored many of the packages to remove configuration and additional scripts to a separate package, I would like to see something similar here for packages are are needed for controller-0 (ie the things we are not installing from PyPi directly). Do we install things directly from PyPi? When does that happen? [Don] No, we don’t install anything from PyPi. Thanks. Good to know. :) What I saw is that we include the CentOS-Openstack RPM repo along with, of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack packages directly along with some StarlingX specific additions in a seperate package, rather than creating a new package with both upstream and StarlingX content. I don't know what the extra things are that we are packaging, but if they are only helper scripts and the like and don't affect the actual keystone code then I'd hope we would use the upstream RPMs. [Don] As much as possible, we look to use unmodified upstream RPMs. Can you expand on that statement in the context of this particular RPM? (Sorry I'm not familiar with what we are doing with Keystone.) Thanks, Curtis My two cents. :) Thanks, Curtis Thoughts, Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Feb 15 16:30:11 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 15 Feb 2019 11:30:11 -0500 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, Feb 15, 2019 at 10:42 AM Rowsell, Brent wrote: > A few points to keep in mind here: > > 1) Config_controller is being removed and replaced with ansible. > > 2) Openstack deployment will not be part of the initial controller > bootstrapping. Openstack will be deployed in containers. > > 3) We are in the process of moving to vanilla openstack. > With those points in mind, does that mean after moving to vanilla openstack the keystone code will come from an upstream RPM? Thanks, Curtis > > > Brent > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 10:19 AM > *To:* Penney, Don > *Cc:* Saul Wold ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > > > > > On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > wrote: > > Comments inline. > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 8:24 AM > *To:* Saul Wold > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > On Thu, Feb 14, 2019 at 12:51 PM Saul Wold wrote: > > > Folks, > > I was doing some experimentation with an un-patched CentOS and running > config_controller. One of the main issues I found is that doing the > initial installation and execution discovered many un-resolved runtime > requirements. > > > > Thanks for looking into this Saul, I think this is a good thing to do to > work towards getting a understanding of dependencies. > > [BR] Keep in mind config_controller is being removed and being replaced > with ansible. The bootsta > > > I will start sending some pull requests to fault, metal, and config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding openstack-keystone > among other openstack related packages with additional configuration and > scripts, which are needed for controller-0. In the stx-integ (base OS) > case, we re-factored many of the packages to remove configuration and > additional scripts to a separate package, I would like to see something > similar here for packages are are needed for controller-0 (ie the things > we are not installing from PyPi directly). > > > > Do we install things directly from PyPi? When does that happen? > > *[Don] No, we don’t install anything from PyPi.* > > > > Thanks. Good to know. :) > > > > > > > > > What I saw is that we include the CentOS-Openstack RPM repo along with, > of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack > packages directly along with some StarlingX specific additions in a > seperate package, rather than creating a new package with both upstream > and StarlingX content. > > > > I don't know what the extra things are that we are packaging, but if they > are only helper scripts and the like and don't affect the actual keystone > code then I'd hope we would use the upstream RPMs. > > *[Don] As much as possible, we look to use unmodified upstream RPMs.* > > > > Can you expand on that statement in the context of this particular RPM? > (Sorry I'm not familiar with what we are doing with Keystone.) > > > > Thanks, > > Curtis > > > > > > > > My two cents. :) > > > > Thanks, > > Curtis > > > > > > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Fri Feb 15 16:46:10 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Fri, 15 Feb 2019 16:46:10 +0000 Subject: [Starlingx-discuss] Proposal: Build and Multi-OS strategy In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD11C1@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD11C1@fmsmsx121.amr.corp.intel.com> Message-ID: Hi all. I've been gathering thoughs on how to achieve multi OS since the beginning of the project and this is a good oppportunity to drop all of them here :) ~~~~~~~~~ I think multi OS is a challenge with many faces that can be summarized in two high level areas: building and running. Building ======== Currently, developers plays a mixed role, they are developing and packaging software. They have defined a workflow where in addition of creating new features, fixing bugs and other tasks, they need to be aware of the build system that consumes their work. This model is similar to Yocto's (which I think was used in the past) where developers needs to create/modify recipes to get their changes checked in. This model ain't bad but I think it could be incomplatible with a multi OS approach. It could enforce that developers needs to be aware of additional build layers and add an extra effort everytime they want to make changes. If you take any distribution out there, all of them have the same entry point: a software released by upstream. Let's say there is a `abc` project and they release the `abc-1.2.3` version packaged in a `abc- 1.2.3.tar.gz` file. Any distribution that wants to include `abc` takes that packaged file and create a distribution package. The `abc` team doesn't care on how distros package their software, they just care on creating a good piece of software that is flexible enough to run well on any distribution. Anytime `abc` releases a new version, they increment the version number accordingly and the distribution packagers includes the new version. In my opinion, having a separation between build system and our software components will help the project in many ways. From one side, building for multiple OS is easier because the multi OS team can only care about threating our software as upstream, building, packaging and eventually creating bugs for upstream (as all distros does). In the other side, the software component maintainers can only care about robustness of their project, that can be tested, builded and installed. The downside in this separation is that we need things we currently don't have, like proper versioning and release tools (autotools and friends). But also the mindset to start threating our software components as any software project out there. I believe some of this intentions has been captured in the ongoing multi OS specs, but I want to highlight the importance of the role of software maintainers in this model. Some workflows might need to change (if we take this path), but we can find equivalence in a new scenario. Once we have this separation, the multi OS building effort relies more on packaging and creating bugs for upstream. The next of the challenges are in the running part. Running ======= In my opinion running in multiple OS is a challenge even higher than creating the RPM o DEB packages. At this point we don't have enough information on how the system will behave in Ubuntu, I've seen hard coded paths in the source code, some for executables and some other for configuration files. Extending the example, in distros like Clear Linux, the configuration files needs to be in a different path, this is also true for distros under the Atomic Project[0] (This is just an example I know they are out of the scope right now). The point here is that there's a high level of uncertainty on how the entire system will behave. I think there are a lot of questions, for example, the configuration will work in Ubuntu? (there's a plan to use Ansible that could help), the installation process can work the same? does anaconda works the same way in Ubuntu? What refactors are needed in stx-update to support DEBs? and other questions. The multi OS doesn't have (and I think it shouldn't) enough vision in these topics. The software component maintainers are the best people to offer insights into how their projects will work in a multi OS environment. I we take the build system and source code separation again, then the software projects should only care that the software are flexible and can run well in different operating systems (as upstream source projects does). I believe we might need more involvement of the community to solve this kind of questions or, at least, raise red flags that could help to plan and act accordingly. [0] https://www.projectatomic.io/ On Fri, 2019-02-15 at 00:05 +0000, Jones, Bruce E wrote: > I would like to start a thread that I hope will result in more focus > and direction for the Build and Multi-OS teams. It’s right before I > disappear for vacation, so I’ll ask Saul and Cesar to address any > follow-ups. > > What I would like to propose is that we as a community take on the > task of delivering support for Ubuntu as a StarlingX host OS for the > November 2019 release. This would allow us to support the ~35% of > the cloud ecosystem that doesn’t run on RHEL or CentOS. > > It will require a lot of work and therefore we should start as soon > as possible. What I would propose we do is: > 1) The Build team to create a new and separate build system for > an Ubuntu LTS hosted ISO [0] > 2) The MultiOS team to review the outstanding carried patches > and apply those needed to the Ubuntu packages > 3) The MultiOS team to update the system as needed to use an > Ubuntu installer to get controller-0 fully installed > 4) Which would then lead to work in the MultiOS team to bring up > the Ubuntu hosted StarlingX in Simplex mode [1]. > > We would then have a (kind of) working StarlingX image that will > enable the broader community to contribute to all of the other work > needed to deliver a fully supported Ubuntu host for the November > release. That work would include bringing up the other > configurations beyond Simplex, changes to the StarlingX software > management and update services, the additional testing needed, and > other tasks which can be parallelized. > > Meanwhile, on the Intel side we have received new guidance from our > new management on the requirement for Clear Linux support. We will > continue but slow down that work for now and focus on Ubuntu. So for > November, the goal is to support 2 Host OS’s, not 3. > > We will need support and contributions from the community to achieve > this goal in time for November. The MultiOS team in particular will > need help and additional contribtutors. > > Brucej > > [0] Making the build system common between Ubuntu and CentOS is hard > and probably should not be attempted. We should leverage what we > can, of course, from our own code and the broader ecosystem. > [1] Or in which ever configuration is easier…. > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Fri Feb 15 17:16:37 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 15 Feb 2019 18:16:37 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DAC9@ALA-MBD.corp.ad.wrs.com> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> <6703202FD9FDFF4A8DA9ACF104AE129FBA43DAC9@ALA-MBD.corp.ad.wrs.com> Message-ID: <194188777.555385.1550250997219@communicator.strato.com> Hi Don, your analysis was correct. Our interface ist not supported by the initrd. Do you know by chance how to unpack and pack the initrd correctly? Thanks Marcel > "Penney, Don" hat am 14. Februar 2019 um 20:48 geschrieben: > > > Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Thursday, February 14, 2019 2:41 PM > To: Penney, Don > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi Don, > > which build do you recommend? > > Is there a workaround so I can keep my installation for now? > > Thanks > > Marcel > > Von meinem iPhone gesendet > > > Am 14.02.2019 um 19:50 schrieb Penney, Don : > > > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > > * problems with the lighttpd server on the active controller > > * NICs that are unsupported by the initrd kernel modules > > * some other comms issue > > > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Thursday, February 14, 2019 1:40 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > > > Hi, > > > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > > > Console log: > > ============= > > > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > > [ OK ] Started Show Plymouth Boot Screen. > > [ OK ] Started Device-Mapper Multipath Device Controller. > > Starting Open-iSCSI... > > [ OK ] Reached target Paths. > > [ OK ] Reached target Basic System. > > [ OK ] Started Open-iSCSI. > > Starting dracut initqueue hook... > > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > ... > > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [Warning: /dev/root does not exist > > > > Generating "/run/initramfs/rdsosreport.txt" > > > > Entering emergency mode. Exit the shell to continue. > > Type "journalctl" to view system logs. > > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > > after mounting them and attach it to a bug report. > > > > dracut:/# > > > > Kernel parameter: > > ================== > > > > dracut:/# journalctl | grep -i boot > > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > > ======= > > > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > > > Any idea is welcome! > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > 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 Feb 15 17:47:16 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 15 Feb 2019 09:47:16 -0800 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> Message-ID: <6ff71695-020f-020b-a655-3eeccab02eba@linux.intel.com> On 2/15/19 7:42 AM, Rowsell, Brent wrote: > A few points to keep in mind here: > > 1)Config_controller is being removed and replaced with ansible. > I know there is a specification for this work, is there some preliminary work that I can look at or work with to test? > 2)Openstack deployment will not be part of the initial controller > bootstrapping. Openstack will be deployed in containers. > I understood there were still some openstack requirements on controller-0 such as keystone and horizon. I am looking at the stx_container_update PDF from the Chandler meeting. > 3)We are in the process of moving to vanilla openstack. > Yes, I know this. Sau! > Brent > > *From:*Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 10:19 AM > *To:* Penney, Don > *Cc:* Saul Wold ; starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > wrote: > > Comments inline. > > *From:*Curtis [mailto:serverascode at gmail.com > ] > *Sent:* Friday, February 15, 2019 8:24 AM > *To:* Saul Wold > *Cc:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements > on the bare-metal controller-0 > > On Thu, Feb 14, 2019 at 12:51 PM Saul Wold > wrote: > > > Folks, > > I was doing some experimentation with an un-patched CentOS and > running > config_controller. One of the main issues I found is that doing the > initial installation and execution discovered many un-resolved > runtime > requirements. > > Thanks for looking into this Saul, I think this is a good thing to > do to work towards getting a understanding of dependencies. > > [BR] Keep in mind config_controller is being removed and being > replaced with ansible. The bootsta > > > I will start sending some pull requests to fault, metal, and > config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding > openstack-keystone > among other openstack related packages with additional > configuration and > scripts, which are needed for controller-0. In the stx-integ > (base OS) > case, we re-factored many of the packages to remove > configuration and > additional scripts to a separate package, I would like to see > something > similar here for packages are are needed for controller-0 (ie > the things > we are not installing from PyPi directly). > > Do we install things directly from PyPi? When does that happen? > > */[Don] No, we don’t install anything from PyPi./* > > Thanks. Good to know. :) > > > What I saw is that we include the CentOS-Openstack RPM repo > along with, > of course, our StarlingX RPM repo. Why can't we use the > CentOS-Openstack > packages directly along with some StarlingX specific additions in a > seperate package, rather than creating a new package with both > upstream > and StarlingX content. > > I don't know what the extra things are that we are packaging, but if > they are only helper scripts and the like and don't affect the > actual keystone code then I'd hope we would use the upstream RPMs. > > */[Don] As much as possible, we look to use unmodified upstream RPMs./* > > Can you expand on that statement in the context of this particular RPM? > (Sorry I'm not familiar with what we are doing with Keystone.) > > Thanks, > > Curtis > > My two cents. :) > > Thanks, > > Curtis > > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From Brent.Rowsell at windriver.com Fri Feb 15 17:59:52 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Fri, 15 Feb 2019 17:59:52 +0000 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> Message-ID: <2588653EBDFFA34B982FAF00F1B4844EBB3D706E@ALA-MBD.corp.ad.wrs.com> See inline From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 11:30 AM To: Rowsell, Brent Cc: Penney, Don ; Saul Wold ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Fri, Feb 15, 2019 at 10:42 AM Rowsell, Brent > wrote: A few points to keep in mind here: 1) Config_controller is being removed and replaced with ansible. 2) Openstack deployment will not be part of the initial controller bootstrapping. Openstack will be deployed in containers. 3) We are in the process of moving to vanilla openstack. With those points in mind, does that mean after moving to vanilla openstack the keystone code will come from an upstream RPM? [BR] Since we will be doing CI with openstack master, we will be building our own rpm’s. The upstream centos distro would only have release rpm’s (i.e. rocky). Thanks, Curtis Brent From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 10:19 AM To: Penney, Don > Cc: Saul Wold >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > wrote: Comments inline. From: Curtis [mailto:serverascode at gmail.com] Sent: Friday, February 15, 2019 8:24 AM To: Saul Wold Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 On Thu, Feb 14, 2019 at 12:51 PM Saul Wold > wrote: Folks, I was doing some experimentation with an un-patched CentOS and running config_controller. One of the main issues I found is that doing the initial installation and execution discovered many un-resolved runtime requirements. Thanks for looking into this Saul, I think this is a good thing to do to work towards getting a understanding of dependencies. [BR] Keep in mind config_controller is being removed and being replaced with ansible. The bootsta I will start sending some pull requests to fault, metal, and config with more detailed "Requires:" statements. Another item is that since that we are rebuilding openstack-keystone among other openstack related packages with additional configuration and scripts, which are needed for controller-0. In the stx-integ (base OS) case, we re-factored many of the packages to remove configuration and additional scripts to a separate package, I would like to see something similar here for packages are are needed for controller-0 (ie the things we are not installing from PyPi directly). Do we install things directly from PyPi? When does that happen? [Don] No, we don’t install anything from PyPi. Thanks. Good to know. :) What I saw is that we include the CentOS-Openstack RPM repo along with, of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack packages directly along with some StarlingX specific additions in a seperate package, rather than creating a new package with both upstream and StarlingX content. I don't know what the extra things are that we are packaging, but if they are only helper scripts and the like and don't affect the actual keystone code then I'd hope we would use the upstream RPMs. [Don] As much as possible, we look to use unmodified upstream RPMs. Can you expand on that statement in the context of this particular RPM? (Sorry I'm not familiar with what we are doing with Keystone.) Thanks, Curtis My two cents. :) Thanks, Curtis Thoughts, Sau! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- Blog: serverascode.com -- Blog: serverascode.com -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Fri Feb 15 18:13:56 2019 From: serverascode at gmail.com (Curtis) Date: Fri, 15 Feb 2019 13:13:56 -0500 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3D706E@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D706E@ALA-MBD.corp.ad.wrs.com> Message-ID: On Fri, Feb 15, 2019 at 1:00 PM Rowsell, Brent wrote: > See inline > > > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 11:30 AM > *To:* Rowsell, Brent > *Cc:* Penney, Don ; Saul Wold < > sgw at linux.intel.com>; starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > > > > > On Fri, Feb 15, 2019 at 10:42 AM Rowsell, Brent < > Brent.Rowsell at windriver.com> wrote: > > A few points to keep in mind here: > > 1) Config_controller is being removed and replaced with ansible. > > 2) Openstack deployment will not be part of the initial controller > bootstrapping. Openstack will be deployed in containers. > > 3) We are in the process of moving to vanilla openstack. > > > > With those points in mind, does that mean after moving to vanilla > openstack the keystone code will come from an upstream RPM? > > [BR] Since we will be doing CI with openstack master, we will be building > our own rpm’s. The upstream centos distro would only have release rpm’s > (i.e. rocky). > > > OK thanks for the answer. Interesting. Thanks, Curtis > Thanks, > > Curtis > > > > > > > > Brent > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 10:19 AM > *To:* Penney, Don > *Cc:* Saul Wold ; > starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > > > > > On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > wrote: > > Comments inline. > > > > *From:* Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 8:24 AM > *To:* Saul Wold > *Cc:* starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > > > On Thu, Feb 14, 2019 at 12:51 PM Saul Wold wrote: > > > Folks, > > I was doing some experimentation with an un-patched CentOS and running > config_controller. One of the main issues I found is that doing the > initial installation and execution discovered many un-resolved runtime > requirements. > > > > Thanks for looking into this Saul, I think this is a good thing to do to > work towards getting a understanding of dependencies. > > [BR] Keep in mind config_controller is being removed and being replaced > with ansible. The bootsta > > > I will start sending some pull requests to fault, metal, and config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding openstack-keystone > among other openstack related packages with additional configuration and > scripts, which are needed for controller-0. In the stx-integ (base OS) > case, we re-factored many of the packages to remove configuration and > additional scripts to a separate package, I would like to see something > similar here for packages are are needed for controller-0 (ie the things > we are not installing from PyPi directly). > > > > Do we install things directly from PyPi? When does that happen? > > *[Don] No, we don’t install anything from PyPi.* > > > > Thanks. Good to know. :) > > > > > > > > > What I saw is that we include the CentOS-Openstack RPM repo along with, > of course, our StarlingX RPM repo. Why can't we use the CentOS-Openstack > packages directly along with some StarlingX specific additions in a > seperate package, rather than creating a new package with both upstream > and StarlingX content. > > > > I don't know what the extra things are that we are packaging, but if they > are only helper scripts and the like and don't affect the actual keystone > code then I'd hope we would use the upstream RPMs. > > *[Don] As much as possible, we look to use unmodified upstream RPMs.* > > > > Can you expand on that statement in the context of this particular RPM? > (Sorry I'm not familiar with what we are doing with Keystone.) > > > > Thanks, > > Curtis > > > > > > > > My two cents. :) > > > > Thanks, > > Curtis > > > > > > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Fri Feb 15 18:21:18 2019 From: sgw at linux.intel.com (Saul Wold) Date: Fri, 15 Feb 2019 10:21:18 -0800 Subject: [Starlingx-discuss] [Containers] Package Requirements on the bare-metal controller-0 In-Reply-To: <2588653EBDFFA34B982FAF00F1B4844EBB3D706E@ALA-MBD.corp.ad.wrs.com> References: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE6D@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D6792@ALA-MBD.corp.ad.wrs.com> <2588653EBDFFA34B982FAF00F1B4844EBB3D706E@ALA-MBD.corp.ad.wrs.com> Message-ID: <05f9a850-1723-e27b-1717-04828866dbc7@linux.intel.com> On 2/15/19 9:59 AM, Rowsell, Brent wrote: > See inline > > *From:*Curtis [mailto:serverascode at gmail.com] > *Sent:* Friday, February 15, 2019 11:30 AM > *To:* Rowsell, Brent > *Cc:* Penney, Don ; Saul Wold > ; starlingx-discuss at lists.starlingx.io > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements on > the bare-metal controller-0 > > On Fri, Feb 15, 2019 at 10:42 AM Rowsell, Brent > > wrote: > > A few points to keep in mind here: > > 1)Config_controller is being removed and replaced with ansible. > > 2)Openstack deployment will not be part of the initial controller > bootstrapping. Openstack will be deployed in containers. > > 3)We are in the process of moving to vanilla openstack. > > With those points in mind, does that mean after moving to vanilla > openstack the keystone code will come from an upstream RPM? > > [BR] Since we will be doing CI with openstack master, we will be > building our own rpm’s.  The upstream centos distro would only have > release rpm’s (i.e. rocky). > This is great news, thanks for this update. Sau! > Thanks, > > Curtis > > Brent > > *From:*Curtis [mailto:serverascode at gmail.com > ] > *Sent:* Friday, February 15, 2019 10:19 AM > *To:* Penney, Don > > *Cc:* Saul Wold >; > starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] [Containers] Package Requirements > on the bare-metal controller-0 > > On Fri, Feb 15, 2019 at 10:12 AM Penney, Don > > wrote: > > Comments inline. > > *From:*Curtis [mailto:serverascode at gmail.com > ] > *Sent:* Friday, February 15, 2019 8:24 AM > *To:* Saul Wold > *Cc:* starlingx-discuss at lists.starlingx.io > > *Subject:* Re: [Starlingx-discuss] [Containers] Package > Requirements on the bare-metal controller-0 > > On Thu, Feb 14, 2019 at 12:51 PM Saul Wold > wrote: > > > Folks, > > I was doing some experimentation with an un-patched CentOS > and running > config_controller. One of the main issues I found is that > doing the > initial installation and execution discovered many > un-resolved runtime > requirements. > > Thanks for looking into this Saul, I think this is a good thing > to do to work towards getting a understanding of dependencies. > > [BR] Keep in mind config_controller is being removed and being > replaced with ansible. The bootsta > > > I will start sending some pull requests to fault, metal, and > config with > more detailed "Requires:" statements. > > Another item is that since that we are rebuilding > openstack-keystone > among other openstack related packages with additional > configuration and > scripts, which are needed for controller-0. In the stx-integ > (base OS) > case, we re-factored many of the packages to remove > configuration and > additional scripts to a separate package, I would like to > see something > similar here for packages are are needed for controller-0 > (ie the things > we are not installing from PyPi directly). > > Do we install things directly from PyPi? When does that happen? > > */[Don] No, we don’t install anything from PyPi./* > > Thanks. Good to know. :) > > > What I saw is that we include the CentOS-Openstack RPM repo > along with, > of course, our StarlingX RPM repo. Why can't we use the > CentOS-Openstack > packages directly along with some StarlingX specific > additions in a > seperate package, rather than creating a new package with > both upstream > and StarlingX content. > > I don't know what the extra things are that we are packaging, > but if they are only helper scripts and the like and don't > affect the actual keystone code then I'd hope we would use the > upstream RPMs. > > */[Don] As much as possible, we look to use unmodified upstream > RPMs./* > > Can you expand on that statement in the context of this particular > RPM? (Sorry I'm not familiar with what we are doing with Keystone.) > > Thanks, > > Curtis > > My two cents. :) > > Thanks, > > Curtis > > Thoughts, > > Sau! > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > > -- > > Blog: serverascode.com > > > _______________________________________________ > 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 Fri Feb 15 18:58:08 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 15 Feb 2019 18:58:08 +0000 Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <194188777.555385.1550250997219@communicator.strato.com> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> <6703202FD9FDFF4A8DA9ACF104AE129FBA43DAC9@ALA-MBD.corp.ad.wrs.com> <194188777.555385.1550250997219@communicator.strato.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43E077@ALA-MBD.corp.ad.wrs.com> If it's not supported by the initrd, it's not supported by the runtime load. The installer images are updated with the runtime kernel and drivers, to align with runtime. What type of NIC are you using? -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Friday, February 15, 2019 12:17 PM To: Penney, Don Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout Hi Don, your analysis was correct. Our interface ist not supported by the initrd. Do you know by chance how to unpack and pack the initrd correctly? Thanks Marcel > "Penney, Don" hat am 14. Februar 2019 um 20:48 geschrieben: > > > Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues. > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Thursday, February 14, 2019 2:41 PM > To: Penney, Don > Cc: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi Don, > > which build do you recommend? > > Is there a workaround so I can keep my installation for now? > > Thanks > > Marcel > > Von meinem iPhone gesendet > > > Am 14.02.2019 um 19:50 schrieb Penney, Don : > > > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > > * problems with the lighttpd server on the active controller > > * NICs that are unsupported by the initrd kernel modules > > * some other comms issue > > > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Thursday, February 14, 2019 1:40 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > > > Hi, > > > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > > > Console log: > > ============= > > > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > > [ OK ] Started Show Plymouth Boot Screen. > > [ OK ] Started Device-Mapper Multipath Device Controller. > > Starting Open-iSCSI... > > [ OK ] Reached target Paths. > > [ OK ] Reached target Basic System. > > [ OK ] Started Open-iSCSI. > > Starting dracut initqueue hook... > > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > ... > > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > [Warning: /dev/root does not exist > > > > Generating "/run/initramfs/rdsosreport.txt" > > > > Entering emergency mode. Exit the shell to continue. > > Type "journalctl" to view system logs. > > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > > after mounting them and attach it to a bug report. > > > > dracut:/# > > > > Kernel parameter: > > ================== > > > > dracut:/# journalctl | grep -i boot > > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > > ======= > > > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > > > Any idea is welcome! > > > > Thanks > > > > Marcel > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From marcel at schaible-consulting.de Fri Feb 15 19:12:47 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Fri, 15 Feb 2019 20:12:47 +0100 (CET) Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA43E077@ALA-MBD.corp.ad.wrs.com> References: <701275276.504630.1550169575394@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D9CA@ALA-MBD.corp.ad.wrs.com> <543FEB76-F032-4865-A12F-B45C56A3B0B7@schaible-consulting.de> <6703202FD9FDFF4A8DA9ACF104AE129FBA43DAC9@ALA-MBD.corp.ad.wrs.com> <194188777.555385.1550250997219@communicator.strato.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43E077@ALA-MBD.corp.ad.wrs.com> Message-ID: <33387997.558340.1550257967471@communicator.strato.com> It is the ixgbevf driver. I have packed into the pxeboot image and it works now. Thanks again for your support! Marcel > "Penney, Don" hat am 15. Februar 2019 um 19:58 geschrieben: > > > If it's not supported by the initrd, it's not supported by the runtime load. The installer images are updated with the runtime kernel and drivers, to align with runtime. > > What type of NIC are you using? > > > -----Original Message----- > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > Sent: Friday, February 15, 2019 12:17 PM > To: Penney, Don > Cc: starlingx-discuss at lists.starlingx.io > Subject: RE: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > Hi Don, > > your analysis was correct. Our interface ist not supported by the initrd. > > Do you know by chance how to unpack and pack the initrd correctly? > > Thanks > > Marcel > > > "Penney, Don" hat am 14. Februar 2019 um 20:48 geschrieben: > > > > > > Your load shouldn't have the http port change, which was merged the next day. So I would suggest checking that the lighttpd server is running fine on the active controller as the first step. If it is, then if you have some shell access from the failed installation, maybe you can confirm that the boot interface is supported by the initrd and rule out comms issues. > > > > -----Original Message----- > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > Sent: Thursday, February 14, 2019 2:41 PM > > To: Penney, Don > > Cc: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > > > Hi Don, > > > > which build do you recommend? > > > > Is there a workaround so I can keep my installation for now? > > > > Thanks > > > > Marcel > > > > Von meinem iPhone gesendet > > > > > Am 14.02.2019 um 19:50 schrieb Penney, Don : > > > > > > This means the initrd was unable to download the squashfs.img from the active controller. This could be a couple of things: > > > * problems with the lighttpd server on the active controller > > > * NICs that are unsupported by the initrd kernel modules > > > * some other comms issue > > > > > > What load are you using? There was a recent update around http port config that moved lighttpd to listen to port 8080 instead of 80, but your boot cmdline is referencing http://pxecontroller/ > > > > > > > > > -----Original Message----- > > > From: Marcel Schaible [mailto:marcel at schaible-consulting.de] > > > Sent: Thursday, February 14, 2019 1:40 PM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: [Starlingx-discuss] Duplex Configuration: Installation of controller-1 fails with dracut timeout > > > > > > Hi, > > > > > > I am trying to install controller-1 in a duplex configuration (bare metal) and getting the following error: > > > > > > Console log: > > > ============= > > > > > > [ 201.379136] dracut-initqueue[730]: Warning: Could not boot. > > > [ OK ] Started Show Plymouth Boot Screen. > > > [ OK ] Started Device-Mapper Multipath Device Controller. > > > Starting Open-iSCSI... > > > [ OK ] Reached target Paths. > > > [ OK ] Reached target Basic System. > > > [ OK ] Started Open-iSCSI. > > > Starting dracut initqueue hook... > > > [ 140.683067] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > > [ 141.198294] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > > ... > > > [ 195.770491] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > > [ 196.280235] dracut-initqueue[730]: Warning: dracut-initqueue timeout - starting timeout scripts > > > [Warning: /dev/root does not exist > > > > > > Generating "/run/initramfs/rdsosreport.txt" > > > > > > Entering emergency mode. Exit the shell to continue. > > > Type "journalctl" to view system logs. > > > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot > > > after mounting them and attach it to a bug report. > > > > > > dracut:/# > > > > > > Kernel parameter: > > > ================== > > > > > > dracut:/# journalctl | grep -i boot > > > Jan 09 00:16:06 localhost kernel: Command line: BOOT_IMAGE=rel-19.01/installer-bzImage bootifonly=1 devfs=nomount inst.repo=http://pxecontroller/feed/rel-19.01/ inst.ks=http://pxecontroller/feed/rel-19.01/net_smallsystem_ks.cfg usbcore.autosuspend=-1 biosdevname=0 rd.net.timeout.dhcp=120 ksdevice=02:01:00:10:02:06 BOOTIF=02:01:00:10:02:06 boot_device=nvme0n1 rootfs_device=nvme0n1 inst.text console=ttyS0,115200 tisnotify=http://pxecontroller:6385/v1/ihosts/00273dcb-25fa-4204-98de-64fed0bfabfe/install_progress inst.gpt user_namespace.enable=1 security_profile=standard nopti nospectre_v2 > > > ======= > > > > > > The message "[Warning: /dev/root does not exist" make me nervous. What does that mean? > > > > > > Any idea is welcome! > > > > > > Thanks > > > > > > Marcel > > > > > > _______________________________________________ > > > 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 Fri Feb 15 21:00:25 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Fri, 15 Feb 2019 21:00:25 +0000 Subject: [Starlingx-discuss] StarlingX Infrastructure Containerization Message-ID: Due to a holiday for many on the containers subproject on Monday, moving this meeting to Tuesday Feb 19th for this week only. -----------------------------------> For those contributing to or interested in the Containerization subproject a weekly meeting has been set up: Timeslot: 11am EST / 8am PDT / 1600 UTC Call details * Zoom link: https://zoom.us/j/342730236 * Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ Agenda and meeting minutes Project notes are at https://etherpad.openstack.org/p/stx-containerization Containerization subproject wiki: https://wiki.openstack.org/wiki/StarlingX/Containers -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2467 bytes Desc: not available URL: From cesar.lara at intel.com Fri Feb 15 21:45:10 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Fri, 15 Feb 2019 21:45:10 +0000 Subject: [Starlingx-discuss] [multios][meetings] MultiOS team meeting agenda for 2/18/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105EF3D6@fmsmsx104.amr.corp.intel.com> MultiOS team meeting Agenda for 2/18/2019 - Discuss multiOS team activities for May release - Opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Fri Feb 15 22:42:00 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 15 Feb 2019 22:42:00 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190215 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9BCB0@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-15 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS]s TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Fri Feb 15 23:07:08 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Fri, 15 Feb 2019 17:07:08 -0600 Subject: [Starlingx-discuss] contact for OPNFV In-Reply-To: <38CB89DDEF80A04D89F30124F87D7A559D22186F@ALA-MBD.corp.ad.wrs.com> References: <0EECF16D-278B-46E9-848E-E138060D906C@intel.com> <0F0AD23D-45CF-4F11-A22D-2FC63DCDF549@intel.com> <3CAA827B7A79BA46B15B280EC82088FE48273E9B@ALA-MBD.corp.ad.wrs.com> <38CB89DDEF80A04D89F30124F87D7A559D22186F@ALA-MBD.corp.ad.wrs.com> Message-ID: Thanks a lot Peng I will follow the steps and get back with questions Regards Victor On Fri, Feb 15, 2019 at 12:59 PM Peng, Peng wrote: > > Hi Victor, > > I summarized the Refstack setup steps. Please check attachment for detail. > > Thanks, > Peng > > -----Original Message----- > From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] > Sent: Thursday, February 14, 2019 1:05 PM > To: Waheed, Numan > Cc: Rodriguez Bahena, Victor; Peng, Peng; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] contact for OPNFV > > Thanks a lot, Numan > > Peng , Numan mention last testing meeting about a wiki with the steps > to run the OPNFV performance framework on top of STX, could you please > share those steps? > > > Regards > > On Thu, Feb 14, 2019 at 10:27 AM Waheed, Numan > wrote: > > > > Hi Victor, > > > > Peng from my team can help you with any question regarding OPNFV and Refstack test suite. > > > > Thanks, > > > > Numan. > > > > -----Original Message----- > > From: Rodriguez Bahena, Victor > > Sent: February-14-19 10:57 AM > > To: Waheed, Numan > > Subject: Re: contact for OPNFV > > > > Hi > > > > Friendly reminder > > > > > > -----Original Message----- > > From: "Rodriguez Bahena, Victor" > > Date: Tuesday, February 12, 2019 at 2:33 PM > > To: "Numan.Waheed at windriver.com" > > Subject: contact for OPNFV > > > > Hi Numan > > > > I was wondering if you have the information about the steps to run the performance tests from OPNFV ? > > > > Regards > > > > Victor Rodriguez > > > > > > > > > > _______________________________________________ > > 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 Fri Feb 15 23:23:59 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 15 Feb 2019 23:23:59 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190215 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9BCE4@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-15 (link) Sanity Test is executed in a Containers - Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 35 TCs [PASS] Sanity Platform In Development TOTAL: [ 35 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Status: RED Simplex Setup Manual [FAIL] Provisioning Manual [FAIL] Sanity OpenStack 35 TCs [FAIL] Sanity Platform In Development TOTAL: [ 35 TCs FAIL ] ------------------------------------------------------------------ 'Config_controller -kubernetes' failed during step '06/08 Applying controller manifest' Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1816199 Test to check ceilometer services was removed. Containerized telemetry services have not been enabled on master branch. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From volker.von.hoesslin at gmx.de Sat Feb 16 19:21:01 2019 From: volker.von.hoesslin at gmx.de (Volker von Hoesslin) Date: Sat, 16 Feb 2019 20:21:01 +0100 Subject: [Starlingx-discuss] Nova instance - Change system product name In-Reply-To: References: Message-ID: <45461628-2af1-7e17-47a8-97e12010aa5b@gmx.de> just checkout /etc/nova/release Am 14.02.2019 um 17:23 schrieb von Hoesslin, Volker: > hi, > is there any given glance image metadata to change the instance > product name? > > i want to change the xml entry for file libvirt.xml from instance: > > # by default it looks like this: > > |OpenStack Nova| > thx, >   volker... > > > _______________________________________________ > 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 build.starlingx at gmail.com Sun Feb 17 06:24:31 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 17 Feb 2019 01:24:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_download_mirror - Build # 169 - Failure! Message-ID: <715991703.40.1550384673227.JavaMail.javamailuser@localhost> Project: STX_download_mirror Build #: 169 Status: Failure Timestamp: 20190217T061731Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190217T060000Z/logs -------------------------------------------------------------------------------- Parameters DOCKER_DL_ID: jenkins-master-20190217T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190217T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190217T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Feb 17 06:24:35 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 17 Feb 2019 01:24:35 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 142 - Failure! Message-ID: <197547165.43.1550384676965.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 142 Status: Failure Timestamp: 20190217T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190217T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From haochuan.z.chen at intel.com Mon Feb 18 02:07:04 2019 From: haochuan.z.chen at intel.com (Chen, Haochuan Z) Date: Mon, 18 Feb 2019 02:07:04 +0000 Subject: [Starlingx-discuss] plan to remove IMA redundant kernel patch Message-ID: <56829C2A36C2E542B0CCB9854828E4D8561F1A34@CDSMSX102.ccr.corp.intel.com> Hi I study this patch cgcs-root/stx/stx-integ/kernel/kernel-std/centos/patches/US101216-IMA-support-in-Titanium-kernel.patch My assumption is that for integrity function code in kernel 3.10 is tool old, it introduces kernel module cgcs-root/stx/stx-integ/kernel/kernel-modules/integrity So for CentOS 8 upgrade, as integrity in later kernel is already upgrade, what about remove this package cgcs-root/stx/stx-integ/kernel/kernel-modules/integrity And enable integrity config in cgcs-root/stx/stx-integ/kernel/kernel-std/centos/patches/kernel-3.10.0-x86_64.config.tis_extra For ima.conf, we could move to cgcs-root/stx/stx-integ/config-files. By this way, we could remove several redundant patches for IMA and easy for maintenance. Wait for your opinion Thanks! Martin, Chen SSP, Software Engineer 021-61164330 -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Mon Feb 18 13:11:02 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 18 Feb 2019 08:11:02 -0500 Subject: [Starlingx-discuss] Packet.com baremetal cloud opportunity In-Reply-To: References: Message-ID: FYI - Based on the results of the doodle poll I've updated the etherpad with the information for the next meeting, which is Tues Feb 19, 2-3PM EST (tomorrow). https://etherpad.openstack.org/p/starlingx-packet-edge-pilot John from packet should be in attendance, as well as a gentleman from another open source project who is utilizing packet infrastructure in much the same way we potentially would, and thus can give us some idea of what it's like. :) Thanks All! Curtis On Thu, Jan 31, 2019 at 10:59 AM Curtis wrote: > Hi All, > > There is an opportunity to work with the Packet.com cloud in terms of them > providing cloud resources to the STX community in a couple of different > ways, but you can read about all that in the etherpad [1] and add any > comments/questions/ideas, etc. :) > > Obviously there is some due diligence and information gathering to be > completed, but overall, from my own perspective, having been on a few > related calls, it seems like the STX TSC and other community members that > have had input are thus far positive towards this opportunity. > > Do let us know what you think! > > Thanks kindly, > Curtis > > [1]: https://etherpad.openstack.org/p/starlingx-packet-edge-pilot > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Mon Feb 18 13:38:21 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Mon, 18 Feb 2019 13:38:21 +0000 Subject: [Starlingx-discuss] Agenda for Distro OpenStack Call (Feb 19, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A06752@ALA-MBD.corp.ad.wrs.com> Agenda... - updates on work items in OpenStack tracking sheet [0] - please plan to attend, or provide your update(s) beforehand on [0] - Nova: Frank, Yong, Yongli - Neutron: Ghada, Kailun, Chenjie, Chen, Huifeng, Matt Welch, Enyinna - Horizon: Yan Chen - Glance/Cinder: Liang Fang [0] tracking sheet: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/ [1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#6am_PDT_.2F_1400_UTC_-_Distro_OpenStack_Team_Call From fungi at yuggoth.org Mon Feb 18 16:09:03 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 18 Feb 2019 16:09:03 +0000 Subject: [Starlingx-discuss] CVE Support and Scanning In-Reply-To: Message-ID: <20190218160903.iix6egvwmie36avd@yuggoth.org> On 2019-02-06 15:28:24 +0000 (+0000), Victor Rodriguez wrote: [...] > This is the link to the tool that we could use to catch the CVEs > > https://github.com/clearlinux/cve-check-tool > > Hoep it helps as an starting point That seems to be unmaintained for the past couple of years (last commit was from April 2017 and it has accumulated a number of untriaged issues and pull requests since then). If you're interested in using it, you may want to consider helping the previous maintainers resurrect it. Maybe also consider (actively-maintained) https://github.com/intel/cve-bin-tool which uses a different approach: looking for signs of vulnerable libraries linked into compiled files. It could help you identify when packages you're maintaining need to be rebuilt due to vulnerabilities in their dependencies. -- 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 cesar.lara at intel.com Mon Feb 18 18:28:51 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Mon, 18 Feb 2019 18:28:51 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting minutes 02/14/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105F1123@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 02/14/2019 - Cengn update - CVE scan integration - Opens Notes Cengn Update Build environment stable, there has been some minor issues due to upstream changes, we don't have a huge impact and they have been solved in a timely manner. We need to establish an strategy to lock down bits and minimize risks on file versions on upstream changes, for this we discuss the possibility to have the latest versions for Master branch and lock down versions for release branch. We will write down a script to enforce this strategy AR - Cesar to identify a resource to help Scott on enabling AR - Cesar will identify a resource to help Scott to review scripts on Cengn that updates to packages on mirror CVE scan integration CVE scanning tool proposals presented a sub team will evaluate tool and a proposal based on the following requirements - is fully automated - is up to date with vulnerabilities - can handle multiple OS - need scanning of containers (maybe take a look on Clair tool) - needs a report for further analysis - link to patches or merged patch - patch update - fix in OS first AR Ken to send a communication to mailing list about the process we were following on this and updates Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From cesar.lara at intel.com Mon Feb 18 18:46:45 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Mon, 18 Feb 2019 18:46:45 +0000 Subject: [Starlingx-discuss] [multios][meetings] MultiOS team meeting minutes 2/18/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105F11CD@fmsmsx104.amr.corp.intel.com> MultiOS team meeting Agenda for 2/18/2019 - Discuss multiOS team activities for May release - Opens Notes Discuss multiOS team activities for May release The intention of these activities is to minimize the risk of current StarlingX build CentOS based as we are not intended to change anything regarding of the current environment, with that in mind we separated the effort required to spin up and Ubuntu based PoC and requested the following activities to be reviewed by the community and the TSC -Create a new directory to host Ubuntu files https://review.openstack.org/#/c/634074/ -Create a new repo to store rules for dev file creation for flock services https://review.openstack.org/#/c/631288/ -Work on the Ubuntu PoC and their tools https://review.openstack.org/#/c/621033/ AR- Victor to update spec files accordingly to reflect the scope of these changes These activities are targeted for code freeze on April 1st, but are not to be categorized as blockers for May release Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From Don.Penney at windriver.com Fri Feb 15 15:10:05 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Fri, 15 Feb 2019 15:10:05 +0000 Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE84894@SHSMSX101.ccr.corp.intel.com> References: <19C65A6E92EA384D809B1772130CD7F862182B19@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E8182D@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862182D18@ALA-MBD.corp.ad.wrs.com> <2FD5DDB5A04D264C80D42CA35194914F35E83FB0@SHSMSX104.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F8621838AE@ALA-MBD.corp.ad.wrs.com> <40048C47-DECC-4096-844D-7B8C3047F51B@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D454@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84643@SHSMSX101.ccr.corp.intel.com> <19C65A6E92EA384D809B1772130CD7F862183A40@ALA-MBD.corp.ad.wrs.com> <7c5185d8-daaa-41de-597c-ae566b76918a@windriver.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA43D7D9@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE84894@SHSMSX101.ccr.corp.intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA43DE4D@ALA-MBD.corp.ad.wrs.com> No, I believe the defattr here has ‘-‘ for the permissions, so it should be using the 755 that’s set by the install. I think there needs to be investigation on our side to determine what’s going on here. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Thursday, February 14, 2019 9:22 PM To: Penney, Don; Little, Scott; Liu, Yang; Xie, Cindy; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi Don, So it seems “%defattr” has different effect in your and our build system. Is my understanding correct? In grub.macros, “%defattr” just define the default user/group, the default permission is not set. It seems like an issue of the spec, what’s your suggestion to fix it? Thanks. Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 11:40 PM To: Little, Scott ; Liu, Yang ; Lin, Shuicheng ; Xie, Cindy ; Chen, Haochuan Z ; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Looking at our in-house jenkins build output, I see: $ rpm -qp --dump std/results/jenkins-STX_Feature_centos76_Build-2019-02-12_14-43-05-tis-r6-pike-std/grub2-2.02-0.76.el7.centos.tis.12/grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm /pxeboot/EFI/grubx64.efi 1233016 1550007456 3d0f3ae9293f23e1ebe6f56e1eb04fc6 0100700 root root 0 0 0 X Looking at the grub.macro file, which is providing the %install and %files directives, it certainly seems like this should be 755. The %defattr being set ignores the permissions. And I don’t see anything in the build.log that would indicate another chmod is happening after. From: Little, Scott Sent: Thursday, February 14, 2019 9:56 AM To: Liu, Yang; Lin, Shuicheng; Penney, Don; Xie, Cindy; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: Re: CentOS7.6 testing status - blocked I think it's on our side. The in house jenkins script I cloned for the 76 build does not include an installer rebuild. Scott On 2019-02-14 8:36 a.m., Liu, Yang wrote: Hi Shuicheng, I checked the 3 items as per your instructions, build log does contain the expected step, however the results are different. @ Scott/Don, any thoughts on this? 1. + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi 2. -rwx------ 1 yliu12 users 1233016 Feb 12 16:37 ./pxeboot/EFI/grubx64.efi 3. -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi BR, Yang From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February-14-19 2:32 AM To: Penney, Don; Xie, Cindy; Liu, Yang; Chen, Haochuan Z; Sun, Austin Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: RE: CentOS7.6 testing status - blocked Hi Yang/Don, We double checked the issue today. Here is our finding: 1. I try to revert the fix [0], then do build-pkgs and build-iso, the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” is with 700 permission mode. Add the fix [0] back, then build-pkgs and build-iso, the “grubx64.efi” is changed to 755 permission mode. I also checked the grubx64.efi file in both ISO image, it has the same mode as upper file. 2. Martin confirmed there is tftp log in the deployment: “ 2019-02-11T00:36:52.000 controller-0 dnsmasq-tftp[8262]: info sent /pxeboot/EFI/grubx64.efi to 169.254.202.76 controller-0:/var/log$ ls /pxeboot/EFI/grubx64.efi -l -rwxr-xr-x. 1 root root 1234192 Feb 3 06:52 /pxeboot/EFI/grubx64.efi “ 3. Austin confirmed “install -D -m 755” will set the grubx64.efi with 755 permission mode. “ -m, --mode=MODE set permission mode (as in chmod), instead of rwxr-xr-x “ 4. I try to go through the build log. Here is the log from grub2’s build.log “ + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi.unsigned + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi.unsigned + install -D -m 755 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/pxeboot/EFI/grubx64.efi + install -m 700 grubx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/grubx64.efi + install -m 700 gcdx64.efi /builddir/build/BUILDROOT/grub2-2.02-0.76.el7.centos.tis.12.x86_64/boot/efi/EFI/centos/gcdx64.efi “ And in build-iso script, the file will be extracted and copied to the EFI folder: “ extract_pkg_from_local_repo ${MY_YUM_CONF} ${STD_REPO_ID} grub2-efi-x64-pxeboot … \cp --preserve=all pxeboot/EFI/grubx64.efi $OUTPUT_DIST_DIR/isolinux/pxeboot/EFI/ “ Due to we cannot reproduce the issue, we are not sure which step cause the issue yet. So could you help me have a check with below step to narrow down the issue? Thanks. 1. Please help check whether there is “install -D -m 755 grubx64.efi” in the “loadbuild/std/results/slin14-starlingx-tis-r5-pike-std/grub2-2.02-0.76.el7.centos.tis.12/build.log” or not. 2. Please help extract “grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm” in “loadbuild/std/rpmbuild/RPMS”, and check whether the grubx64.efi file is with 755 mode or not. Extract cmd: rpm2cpio grub2-efi-x64-pxeboot-2.02-0.76.el7.centos.tis.12.x86_64.rpm | cpio -idmv 3. Please help check the “grubx64.efi” in “export/dist/isolinux/pxeboot/EFI/” folder is with 755 mode or not. [0]: https://review.openstack.org/634559 Best Regards Shuicheng From: Penney, Don [mailto:Don.Penney at windriver.com] Sent: Thursday, February 14, 2019 6:01 AM To: Xie, Cindy ; Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada ; Waheed, Numan ; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi Cindy, In a successful case, you should see a TFTP log in daemon.log on the active controller indicating the file was transferred, such as: 2019-02-12T13:20:45.000 controller-0 dnsmasq-tftp[200877]: info sent /pxeboot/EFI/grubx64.efi to 192.168.204.4 I would suggest doing something like “tail -f /var/log/daemon.log | grep -i tftp” while doing the installation of nodes from the active controller, to verify the expected file is getting transferred. If the host installs and you don’t see this file transferred, I’d recommend reconfirming that the node is installing via UEFI. From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: Wednesday, February 13, 2019 4:46 PM To: Liu, Yang Cc: starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan; Little, Scott Subject: Re: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi, Yang Sorry about the issue! It’s interesting as I did have my engineer tested the scenarios. There must be something missing from my side. We will redo the patch and test. In the same time, can you manually change the file permissions as temporarily workaround and unblock the test cycle? Thanks! Cindy Sent from my iPhone On Feb 14, 2019, at 3:02 AM, Liu, Yang > wrote: Hi Cindy, We are still seeing the same file permission issue for grubx64.efi under pxeboot/EFI, causing UEFI pxeboot to fail. We need the grubx64.efi to be readable by others as well. ../pxeboot/EFI/ total 1220 drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 . drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 .. drwxrwsr-x 3 jenkins mock 4096 Feb 12 16:48 centos -rwx------ 1 jenkins mock 1233016 Feb 12 16:37 grubx64.efi The patch seems to have changed the dir permission for centos from 700 to 755, but not grubx64.efi. For the dir permission for centos, I believe the original 700 should be sufficient (@Scott, please correct me if it’s wrong). BR, Yang From: Liu, Yang Sent: February-12-19 9:00 AM To: 'Xie, Cindy'; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Thanks Cindy. Will do. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-11-19 8:10 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io; Cabrales, Ada; Waheed, Numan Subject: RE: CentOS7.6 testing status - blocked Hi, Numan/Yang, The last pending patch (https://review.openstack.org/#/c/634559/) which was blocking your testing (#1814360) was just merged. Please get new build ISO from Jason so you can continue the testing. Thx. - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 10:18 AM To: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Correct. BR, Yang From: Xie, Cindy [mailto:cindy.xie at intel.com] Sent: February-08-19 8:28 PM To: Liu, Yang; starlingx-discuss at lists.starlingx.io Subject: RE: CentOS7.6 testing status - blocked Hi, Yang, Thanks for the report. Are the “two node system” below referring to Duplex? Just want to confirm because #1814360 we have a patch pending and we do want to ensure it works on Duplex as well. Th.x - cindy From: Liu, Yang [mailto:yang.liu at windriver.com] Sent: Saturday, February 9, 2019 2:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] CentOS7.6 testing status - blocked Hi folks, Here’s an update for CentOS7.6 testing. We are currently blocked due to pxeboot from controller-0 does not work for EFI. (#1814360) We will continue after that issue is resolved. System NICs Mgmt;infra;data Special Configs Test coverage after Install and Config Status/Issues Dedicated storage X540-AT2; X540-AT2; fortville IPv6 Sanity, nova Completed. New issues logged. #1814336 CentOS7.6: Unable to launch vm directly from virsh #1814335 CentOS7.6: Unable to launch vm with UEFI boot One node system none; none; X522/X577-AT Sanity, basic regression Completed. Passed. Two node system fortville; fortville; fortville tboot, tpm, https, extended security profile Sanity, security Blocked by #1814360 Multi-node system BCM5720; Niantic; Niantic Sriov(niantic),pcipt(niantic) Sanity, networking Completed. Passed. Two node system Fortville; none; Fortville Low latency, UEFI Sanity, basic regression, cyclictest Blocked by #1814360 Two node system Fortville; none; Fortville Secure boot Sanity, security Blocked by #1814360 Multi-node system I350; Niantic/cx3; cx3 Pxeboot script Sanity Completed. Passed. Only compute-0 was used, since compute-1 has CX3 data nic. ?? CX4 on infra or mgmt, but NOT data Won’t test. We don’t have a system have required nics. BR, yang -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Fri Feb 15 18:59:34 2019 From: Peng.Peng at windriver.com (Peng, Peng) Date: Fri, 15 Feb 2019 18:59:34 +0000 Subject: [Starlingx-discuss] contact for OPNFV In-Reply-To: References: <0EECF16D-278B-46E9-848E-E138060D906C@intel.com> <0F0AD23D-45CF-4F11-A22D-2FC63DCDF549@intel.com> <3CAA827B7A79BA46B15B280EC82088FE48273E9B@ALA-MBD.corp.ad.wrs.com> Message-ID: <38CB89DDEF80A04D89F30124F87D7A559D22186F@ALA-MBD.corp.ad.wrs.com> Hi Victor, I summarized the Refstack setup steps. Please check attachment for detail. Thanks, Peng -----Original Message----- From: Victor Rodriguez [mailto:vm.rod25 at gmail.com] Sent: Thursday, February 14, 2019 1:05 PM To: Waheed, Numan Cc: Rodriguez Bahena, Victor; Peng, Peng; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] contact for OPNFV Thanks a lot, Numan Peng , Numan mention last testing meeting about a wiki with the steps to run the OPNFV performance framework on top of STX, could you please share those steps? Regards On Thu, Feb 14, 2019 at 10:27 AM Waheed, Numan wrote: > > Hi Victor, > > Peng from my team can help you with any question regarding OPNFV and Refstack test suite. > > Thanks, > > Numan. > > -----Original Message----- > From: Rodriguez Bahena, Victor > Sent: February-14-19 10:57 AM > To: Waheed, Numan > Subject: Re: contact for OPNFV > > Hi > > Friendly reminder > > > -----Original Message----- > From: "Rodriguez Bahena, Victor" > Date: Tuesday, February 12, 2019 at 2:33 PM > To: "Numan.Waheed at windriver.com" > Subject: contact for OPNFV > > Hi Numan > > I was wondering if you have the information about the steps to run the performance tests from OPNFV ? > > Regards > > Victor Rodriguez > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Refstack_setup.txt URL: From liang.a.fang at intel.com Mon Feb 18 08:20:14 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Mon, 18 Feb 2019 08:20:14 +0000 Subject: [Starlingx-discuss] Which code line created the users in keystone table local_user Message-ID: Hi Bart and Don In keystone table 'local_user', there's lots of users created (see below), could you please point out which code line created these users? [cid:image002.jpg at 01D4C7A5.D2DF2E40] The background: In code review https://review.openstack.org/#/c/633400/, we need to create an internal project and user for raw cache. Currently I use puppet to call cmd "openstack" to create/get the project/user id. I found the user(cinder) has already been created by some existing code, see above picture please. So I'm expecting to create internal project the same way as internal user. Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 51722 bytes Desc: image002.jpg URL: From juan.carlos.alonso at intel.com Mon Feb 18 21:00:38 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 18 Feb 2019 21:00:38 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190218 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C0AA@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-18 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS]s TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Mon Feb 18 22:59:33 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Mon, 18 Feb 2019 22:59:33 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190218 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C112@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-18 (link) Sanity Test is executed in a Containers - Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 35 TCs [PASS] Sanity Platform In Development TOTAL: [ 35 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Status: RED Simplex Setup Manual [FAIL] Provisioning Manual [FAIL] Sanity OpenStack 35 TCs [FAIL] Sanity Platform In Development TOTAL: [ 35 TCs FAIL ] ------------------------------------------------------------------ 'Config_controller -kubernetes' failed during step '06/08 Applying controller manifest' Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1816199 Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Mon Feb 18 23:43:54 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Mon, 18 Feb 2019 23:43:54 +0000 Subject: [Starlingx-discuss] [ Test ] meeting agenda - 02/19/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD751F0@FMSMSX114.amr.corp.intel.com> 1. Repo status - submissions tried? - Ada - 15 min Closure on how to submit the tests - gather by sub-domain 2. Progress on regression tests selection - Elio, JP, Fer, Numan - 10 min 3. OPNFV test suite for performance metrics - status - Victor - 10 min 4. Opens - All - 15 min Regards Ada From changcheng.liu at intel.com Tue Feb 19 02:53:34 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 19 Feb 2019 02:53:34 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F70679@SHSMSX104.ccr.corp.intel.com> Hi Kam & Emile & Rosales, Have you hit below build error? 3/3 times failed to build below SRC RPMs in StarlingX: 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build_log.tar.bz2 Type: application/octet-stream Size: 21525 bytes Desc: build_log.tar.bz2 URL: From changcheng.liu at intel.com Tue Feb 19 03:03:41 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 19 Feb 2019 11:03:41 +0800 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Message-ID: <20190219030341.GA8093@nstcloud.sh.intel.com> Hi Kam & Emile & Rosales, Have you hit below build error? 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng -------------- next part -------------- A non-text attachment was scrubbed... Name: build_log.tar.bz2 Type: application/octet-stream Size: 21525 bytes Desc: not available URL: From kyle.oh95 at gmail.com Tue Feb 19 04:48:46 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Tue, 19 Feb 2019 13:48:46 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: References: Message-ID: Hello StarlingX Teams, I found that *the horizon dashboard project were not installed automatically* when I deployed StarlingX all-in-one simplex on Baremetal. Are there any reason for this problem..? I used "2019-*Feb-08* 03:40:29 bootimage.iso". [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | | ecf3478c84334c2ba647740bde190739 | neutron | network | | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | | 57a5cb58128445b5819747271c095a89 | heat | orchestration | | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | +----------------------------------+------------+-----------------+ I thought horizon should also be installed with StarlingX's deployment. If not, please let me know how can I install horizon in this StarlingX. Thanks for help in advance :) Best Regards, Jaewook. 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: > Hello starlingx team, > > I deployed Starlingx All-in-one simplex setting on my server, > it seems deployment was done well. > *However I cannot access to the dashboard.* > > I used "2019-*Feb-08* 03:40:29 bootimage.iso". > > > Following log is the service that are now enabled, > [wrsroot at controller-0 ~(keystone_admin)]$ system service-list > +-----+-------------------------------+--------------+----------------+ > | id | service_name | hostname | state | > +-----+-------------------------------+--------------+----------------+ > | 68 | aodh-api | controller-0 | enabled-active | > | 69 | aodh-evaluator | controller-0 | enabled-active | > | 70 | aodh-listener | controller-0 | enabled-active | > | 71 | aodh-notifier | controller-0 | enabled-active | > | 102 | barbican-api | controller-0 | enabled-active | > | 103 | barbican-keystone-listener | controller-0 | enabled-active | > | 104 | barbican-worker | controller-0 | enabled-active | > | 43 | ceilometer-agent-notification | controller-0 | enabled-active | > | 14 | cgcs-export-fs | controller-0 | enabled-active | > | 10 | cgcs-fs | controller-0 | enabled-active | > | 16 | cgcs-nfs-ip | controller-0 | enabled-active | > | 35 | cinder-api | controller-0 | enabled-active | > | 38 | cinder-backup | controller-0 | enabled-active | > | 58 | cinder-ip | controller-0 | enabled-active | > | 56 | cinder-lvm | controller-0 | enabled-active | > | 36 | cinder-scheduler | controller-0 | enabled-active | > | 37 | cinder-volume | controller-0 | enabled-active | > | 23 | dnsmasq | controller-0 | enabled-active | > | 5 | drbd-cgcs | controller-0 | enabled-active | > | 55 | drbd-cinder | controller-0 | enabled-active | > | 75 | drbd-extension | controller-0 | enabled-active | > | 3 | drbd-pg | controller-0 | enabled-active | > | 6 | drbd-platform | controller-0 | enabled-active | > | 4 | drbd-rabbit | controller-0 | enabled-active | > | 77 | extension-export-fs | controller-0 | enabled-active | > | 76 | extension-fs | controller-0 | enabled-active | > | 24 | fm-mgr | controller-0 | enabled-active | > | 27 | glance-api | controller-0 | enabled-active | > | 26 | glance-registry | controller-0 | enabled-active | > | 108 | gnocchi-api | controller-0 | enabled-active | > | 109 | gnocchi-metricd | controller-0 | enabled-active | > | 62 | guest-agent | controller-0 | enabled-active | > | 64 | haproxy | controller-0 | enabled-active | > | 45 | heat-api | controller-0 | enabled-active | > | 46 | heat-api-cfn | controller-0 | enabled-active | > | 47 | heat-api-cloudwatch | controller-0 | enabled-active | > | 44 | heat-engine | controller-0 | enabled-active | > | 51 | horizon | controller-0 | enabled-active | > | 22 | hw-mon | controller-0 | enabled-active | > | 57 | iscsi | controller-0 | enabled-active | > | 25 | keystone | controller-0 | enabled-active | > | 50 | lighttpd | controller-0 | enabled-active | > | 2 | management-ip | controller-0 | enabled-active | > | 20 | mtc-agent | controller-0 | enabled-active | > | 28 | neutron-server | controller-0 | enabled-active | > | 9 | nfs-mgmt | controller-0 | enabled-active | > | 29 | nova-api | controller-0 | enabled-active | > | 63 | nova-api-proxy | controller-0 | enabled-active | > | 31 | nova-conductor | controller-0 | enabled-active | > | 33 | nova-console-auth | controller-0 | enabled-active | > | 34 | nova-novnc | controller-0 | enabled-active | > | 83 | nova-placement-api | controller-0 | enabled-active | > | 30 | nova-scheduler | controller-0 | enabled-active | > | 48 | open-ldap | controller-0 | enabled-active | > | 82 | panko-api | controller-0 | enabled-active | > | 52 | patch-alarm-manager | controller-0 | enabled-active | > | 7 | pg-fs | controller-0 | enabled-active | > | 15 | platform-export-fs | controller-0 | enabled-active | > | 11 | platform-fs | controller-0 | enabled-active | > | 17 | platform-nfs-ip | controller-0 | enabled-active | > | 12 | postgres | controller-0 | enabled-active | > | 65 | pxeboot-ip | controller-0 | enabled-active | > | 13 | rabbit | controller-0 | enabled-active | > | 8 | rabbit-fs | controller-0 | enabled-active | > | 49 | snmp | controller-0 | enabled-active | > | 19 | sysinv-conductor | controller-0 | enabled-active | > | 18 | sysinv-inv | controller-0 | enabled-active | > | 59 | vim | controller-0 | enabled-active | > | 60 | vim-api | controller-0 | enabled-active | > | 61 | vim-webserver | controller-0 | enabled-active | > +-----+-------------------------------+--------------+----------------+ > > As you can see, *I cannot find #1 service (oam-ip)*, and I think this is > one of the main reasons. > > *And also I had a problem when I followed the installation instruction.* > > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan > [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a > > [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a > > > Above instruction was not naturally worked, I mean the third command, > 'host-if-modify' failed with the message "*DataNetwork providernet-a > could not be found*." > > So I googled and I figured out I should command > $ *system datanetwork-add providernet-a vlan* > first. > > But I remember when my first deployment succeed, I didn't need to use that > command at all. (The deployment was implemented on Jan.) > > Any help is appreciated, thank you for your help in advance. > > Best Regards, > Jaewook. > > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Tue Feb 19 05:54:19 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 19 Feb 2019 05:54:19 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 In-Reply-To: <20190219030341.GA8093@nstcloud.sh.intel.com> References: <20190219030341.GA8093@nstcloud.sh.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE85152@SHSMSX101.ccr.corp.intel.com> Hi Changcheng, Per your build failure log in tss2, it should be due to your local tss2 package is not downloaded correctly. I also find there is a new patch under review for tss2. https://review.openstack.org/637574 Please cherry-pick it to fix your issue. Thanks. Best Regards Shuicheng -----Original Message----- From: Liu, Changcheng [mailto:changcheng.liu at intel.com] Sent: Tuesday, February 19, 2019 11:04 AM To: kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi Kam & Emile & Rosales, Have you hit below build error? 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng From changcheng.liu at intel.com Tue Feb 19 06:25:02 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 19 Feb 2019 06:25:02 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE85152@SHSMSX101.ccr.corp.intel.com> References: <20190219030341.GA8093@nstcloud.sh.intel.com> <9700A18779F35F49AF027300A49E7C765FE85152@SHSMSX101.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F707A6@SHSMSX104.ccr.corp.intel.com> Thanks Shuicheng. I've replaced the tss2-930.tar.gz with a new one. md5 org: 53e11a8738b2721adf62a78d7168a180 md5 new: d7b95f3be87012160780276c5a0f38f5 Feedback the build result later. -----Original Message----- From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 1:54 PM To: Liu, Changcheng ; kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi Changcheng, Per your build failure log in tss2, it should be due to your local tss2 package is not downloaded correctly. I also find there is a new patch under review for tss2. https://review.openstack.org/637574 Please cherry-pick it to fix your issue. Thanks. Best Regards Shuicheng -----Original Message----- From: Liu, Changcheng [mailto:changcheng.liu at intel.com] Sent: Tuesday, February 19, 2019 11:04 AM To: kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi Kam & Emile & Rosales, Have you hit below build error? 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng From shuicheng.lin at intel.com Tue Feb 19 06:33:14 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 19 Feb 2019 06:33:14 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data Message-ID: <9700A18779F35F49AF027300A49E7C765FE8527A@SHSMSX101.ccr.corp.intel.com> +Al since Tao is OOO. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From xiongzhiwei at baicells.com Tue Feb 19 06:56:13 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Tue, 19 Feb 2019 14:56:13 +0800 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration References: , Message-ID: <201902191456126968489@baicells.com> Hi Jaewook, I just finished stx all-in-one simplex on Bearmetal last week. The horizon service had been installed defaultly and you should be able to access the dashboard now. Your service list is same as mine. [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | | df07161f527b483292ac5aa5ed722687 | keystone | identity | | 744183df128d414f97390fb70fcac72f | sysinv | platform | | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | | 5d7855696b1f440b8401670e1df6cb28 | glance | image | | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | | 68362243cc214c4181a15e583894e495 | placement | placement | | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | | cbf811729020470a81b3c7be0d453fc9 | neutron | network | | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | | bc5297541def4f8b8881254af9896824 | smapi | smapi | | a388667479484a04824f07a672a331eb | panko | event | | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | | 253390980b274178b7a16844e2c7a826 | cinder | volume | +----------------------------------+------------+-----------------+ BR Tim Xiong From: Jaewook Oh Date: 2019-02-19 12:48 To: starlingx-discuss; 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello StarlingX Teams, I found that the horizon dashboard project were not installed automatically when I deployed StarlingX all-in-one simplex on Baremetal. Are there any reason for this problem..? I used "2019-Feb-08 03:40:29 bootimage.iso". [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | | ecf3478c84334c2ba647740bde190739 | neutron | network | | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | | 57a5cb58128445b5819747271c095a89 | heat | orchestration | | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | +----------------------------------+------------+-----------------+ I thought horizon should also be installed with StarlingX's deployment. If not, please let me know how can I install horizon in this StarlingX. Thanks for help in advance :) Best Regards, Jaewook. 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. However I cannot access to the dashboard. I used "2019-Feb-08 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons. And also I had a problem when I followed the installation instruction. [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found." So I googled and I figured out I should command $ system datanetwork-add providernet-a vlan first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Tue Feb 19 07:00:38 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Tue, 19 Feb 2019 16:00:38 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: <201902191456126968489@baicells.com> References: <201902191456126968489@baicells.com> Message-ID: Hello Tim, thanks for your answer :) However, still I cannot access to the dashboard. I deployed StarlingX 3 times again, but the situation never changes.. If you don't mind, can I see your ip setting with (ip a command)? Best Regards, Jaewook. 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com 님이 작성: > Hi Jaewook, > > I just finished stx all-in-one simplex on Bearmetal last week. The horizon > service had been installed defaultly and you should be able to access the > dashboard now. > Your service list is same as mine. > > [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list > +----------------------------------+------------+-----------------+ > | ID | Name | Type | > +----------------------------------+------------+-----------------+ > | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | > | df07161f527b483292ac5aa5ed722687 | keystone | identity | > | 744183df128d414f97390fb70fcac72f | sysinv | platform | > | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | > | 5d7855696b1f440b8401670e1df6cb28 | glance | image | > | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | > | 68362243cc214c4181a15e583894e495 | placement | placement | > | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | > | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | > | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | > | cbf811729020470a81b3c7be0d453fc9 | neutron | network | > | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | > | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | > | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | > | bc5297541def4f8b8881254af9896824 | smapi | smapi | > | a388667479484a04824f07a672a331eb | panko | event | > | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | > | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | > | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | > | 253390980b274178b7a16844e2c7a826 | cinder | volume | > +----------------------------------+------------+-----------------+ > > BR > Tim Xiong > > *From:* Jaewook Oh > *Date:* 2019-02-19 12:48 > *To:* starlingx-discuss ; 오재욱 > > *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy > All-in-one simplex configuration > Hello StarlingX Teams, > > I found that *the horizon dashboard project were not installed > automatically* when I deployed StarlingX all-in-one simplex on Baremetal. > Are there any reason for this problem..? > I used "2019-*Feb-08* 03:40:29 bootimage.iso". > > [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list > +----------------------------------+------------+-----------------+ > | ID | Name | Type | > +----------------------------------+------------+-----------------+ > | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | > | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | > | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | > | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | > | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | > | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | > | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | > | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | > | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | > | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | > | ecf3478c84334c2ba647740bde190739 | neutron | network | > | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | > | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | > | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | > | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | > | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | > | 57a5cb58128445b5819747271c095a89 | heat | orchestration | > | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | > | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | > | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | > +----------------------------------+------------+-----------------+ > > I thought horizon should also be installed with StarlingX's deployment. > If not, please let me know how can I install horizon in this StarlingX. > > Thanks for help in advance :) > > Best Regards, > Jaewook. > > > 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: > >> Hello starlingx team, >> >> I deployed Starlingx All-in-one simplex setting on my server, >> it seems deployment was done well. >> *However I cannot access to the dashboard.* >> >> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >> >> >> Following log is the service that are now enabled, >> [wrsroot at controller-0 ~(keystone_admin)]$ system service-list >> +-----+-------------------------------+--------------+----------------+ >> | id | service_name | hostname | state | >> +-----+-------------------------------+--------------+----------------+ >> | 68 | aodh-api | controller-0 | enabled-active | >> | 69 | aodh-evaluator | controller-0 | enabled-active | >> | 70 | aodh-listener | controller-0 | enabled-active | >> | 71 | aodh-notifier | controller-0 | enabled-active | >> | 102 | barbican-api | controller-0 | enabled-active | >> | 103 | barbican-keystone-listener | controller-0 | enabled-active | >> | 104 | barbican-worker | controller-0 | enabled-active | >> | 43 | ceilometer-agent-notification | controller-0 | enabled-active | >> | 14 | cgcs-export-fs | controller-0 | enabled-active | >> | 10 | cgcs-fs | controller-0 | enabled-active | >> | 16 | cgcs-nfs-ip | controller-0 | enabled-active | >> | 35 | cinder-api | controller-0 | enabled-active | >> | 38 | cinder-backup | controller-0 | enabled-active | >> | 58 | cinder-ip | controller-0 | enabled-active | >> | 56 | cinder-lvm | controller-0 | enabled-active | >> | 36 | cinder-scheduler | controller-0 | enabled-active | >> | 37 | cinder-volume | controller-0 | enabled-active | >> | 23 | dnsmasq | controller-0 | enabled-active | >> | 5 | drbd-cgcs | controller-0 | enabled-active | >> | 55 | drbd-cinder | controller-0 | enabled-active | >> | 75 | drbd-extension | controller-0 | enabled-active | >> | 3 | drbd-pg | controller-0 | enabled-active | >> | 6 | drbd-platform | controller-0 | enabled-active | >> | 4 | drbd-rabbit | controller-0 | enabled-active | >> | 77 | extension-export-fs | controller-0 | enabled-active | >> | 76 | extension-fs | controller-0 | enabled-active | >> | 24 | fm-mgr | controller-0 | enabled-active | >> | 27 | glance-api | controller-0 | enabled-active | >> | 26 | glance-registry | controller-0 | enabled-active | >> | 108 | gnocchi-api | controller-0 | enabled-active | >> | 109 | gnocchi-metricd | controller-0 | enabled-active | >> | 62 | guest-agent | controller-0 | enabled-active | >> | 64 | haproxy | controller-0 | enabled-active | >> | 45 | heat-api | controller-0 | enabled-active | >> | 46 | heat-api-cfn | controller-0 | enabled-active | >> | 47 | heat-api-cloudwatch | controller-0 | enabled-active | >> | 44 | heat-engine | controller-0 | enabled-active | >> | 51 | horizon | controller-0 | enabled-active | >> | 22 | hw-mon | controller-0 | enabled-active | >> | 57 | iscsi | controller-0 | enabled-active | >> | 25 | keystone | controller-0 | enabled-active | >> | 50 | lighttpd | controller-0 | enabled-active | >> | 2 | management-ip | controller-0 | enabled-active | >> | 20 | mtc-agent | controller-0 | enabled-active | >> | 28 | neutron-server | controller-0 | enabled-active | >> | 9 | nfs-mgmt | controller-0 | enabled-active | >> | 29 | nova-api | controller-0 | enabled-active | >> | 63 | nova-api-proxy | controller-0 | enabled-active | >> | 31 | nova-conductor | controller-0 | enabled-active | >> | 33 | nova-console-auth | controller-0 | enabled-active | >> | 34 | nova-novnc | controller-0 | enabled-active | >> | 83 | nova-placement-api | controller-0 | enabled-active | >> | 30 | nova-scheduler | controller-0 | enabled-active | >> | 48 | open-ldap | controller-0 | enabled-active | >> | 82 | panko-api | controller-0 | enabled-active | >> | 52 | patch-alarm-manager | controller-0 | enabled-active | >> | 7 | pg-fs | controller-0 | enabled-active | >> | 15 | platform-export-fs | controller-0 | enabled-active | >> | 11 | platform-fs | controller-0 | enabled-active | >> | 17 | platform-nfs-ip | controller-0 | enabled-active | >> | 12 | postgres | controller-0 | enabled-active | >> | 65 | pxeboot-ip | controller-0 | enabled-active | >> | 13 | rabbit | controller-0 | enabled-active | >> | 8 | rabbit-fs | controller-0 | enabled-active | >> | 49 | snmp | controller-0 | enabled-active | >> | 19 | sysinv-conductor | controller-0 | enabled-active | >> | 18 | sysinv-inv | controller-0 | enabled-active | >> | 59 | vim | controller-0 | enabled-active | >> | 60 | vim-api | controller-0 | enabled-active | >> | 61 | vim-webserver | controller-0 | enabled-active | >> +-----+-------------------------------+--------------+----------------+ >> >> As you can see, *I cannot find #1 service (oam-ip)*, and I think this is >> one of the main reasons. >> >> *And also I had a problem when I followed the installation instruction.* >> >> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan >> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a >> >> [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a >> >> >> Above instruction was not naturally worked, I mean the third command, >> 'host-if-modify' failed with the message "*DataNetwork providernet-a >> could not be found*." >> >> So I googled and I figured out I should command >> $ *system datanetwork-add providernet-a vlan* >> first. >> >> But I remember when my first deployment succeed, I didn't need to use >> that command at all. (The deployment was implemented on Jan.) >> >> Any help is appreciated, thank you for your help in advance. >> >> Best Regards, >> Jaewook. >> >> ================================================ >> *Jaewook Oh* (오재욱) >> IISTRC - Internet Infra System Technology Research Center >> 369 Sangdo-ro, Dongjak-gu, >> 06978, Seoul, Republic of Korea >> > > > -- > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Tue Feb 19 07:12:22 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 19 Feb 2019 07:12:22 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50F707A6@SHSMSX104.ccr.corp.intel.com> References: <20190219030341.GA8093@nstcloud.sh.intel.com> <9700A18779F35F49AF027300A49E7C765FE85152@SHSMSX101.ccr.corp.intel.com> <0D7994A90DD70040A9F5E77C4D23C57D50F707A6@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F7082A@SHSMSX104.ccr.corp.intel.com> Thanks Shuicheng. Make successful build of all packages. -----Original Message----- From: Liu, Changcheng [mailto:changcheng.liu at intel.com] Sent: Tuesday, February 19, 2019 2:25 PM To: Lin, Shuicheng ; kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Thanks Shuicheng. I've replaced the tss2-930.tar.gz with a new one. md5 org: 53e11a8738b2721adf62a78d7168a180 md5 new: d7b95f3be87012160780276c5a0f38f5 Feedback the build result later. -----Original Message----- From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 1:54 PM To: Liu, Changcheng ; kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi Changcheng, Per your build failure log in tss2, it should be due to your local tss2 package is not downloaded correctly. I also find there is a new patch under review for tss2. https://review.openstack.org/637574 Please cherry-pick it to fix your issue. Thanks. Best Regards Shuicheng -----Original Message----- From: Liu, Changcheng [mailto:changcheng.liu at intel.com] Sent: Tuesday, February 19, 2019 11:04 AM To: kam.nasim at windriver.com; Paul-Emile.Element at windriver.com; Rosales Jimenez, Marcela A Cc: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi Kam & Emile & Rosales, Have you hit below build error? 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng _______________________________________________ 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 Tue Feb 19 09:07:08 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 19 Feb 2019 04:07:08 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_wheels - Build # 47 - Still Failing! In-Reply-To: <667015406.21.1550103743019.JavaMail.javamailuser@localhost> References: <667015406.21.1550103743019.JavaMail.javamailuser@localhost> Message-ID: <1291294034.48.1550567232372.JavaMail.javamailuser@localhost> Project: STX_build_wheels Build #: 47 Status: Still Failing Timestamp: 20190219T090614Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190219T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190219T060000Z OS: centos MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190219T060000Z/logs OPENSTACK_RELEASE: pike OS_VERSION: 7.5.1804 PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190219T060000Z/logs From build.starlingx at gmail.com Tue Feb 19 09:07:15 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 19 Feb 2019 04:07:15 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_images - Build # 47 - Still Failing! In-Reply-To: <25409885.24.1550103750216.JavaMail.javamailuser@localhost> References: <25409885.24.1550103750216.JavaMail.javamailuser@localhost> Message-ID: <224998103.51.1550567237550.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 47 Status: Still Failing Timestamp: 20190219T090404Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190219T060000Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: master MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190219T060000Z 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/20190219T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190219T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master PUBLISH_DISTRO_BASE: /export/mirror/starlingx/master/centos PUBLISH_TIMESTAMP: 20190219T060000Z DOCKER_BUILD_ID: jenkins-master-20190219T060000Z-builder OPENSTACK_RELEASE: pike TIMESTAMP: 20190219T060000Z OS_VERSION: 7.5.1804 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/master/centos/20190219T060000Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/master/centos/20190219T060000Z/outputs From build.starlingx at gmail.com Tue Feb 19 09:07:21 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Tue, 19 Feb 2019 04:07:21 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 144 - Failure! Message-ID: <135013074.54.1550567243399.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 144 Status: Failure Timestamp: 20190219T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190219T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From cindy.xie at intel.com Tue Feb 19 12:28:18 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 19 Feb 2019 12:28:18 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 2/20 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E8FC10@SHSMSX104.ccr.corp.intel.com> Agenda for 2/20 meeting: 1. CentOS 7.6 upgrade test status (Ada/Numan) 2. Ceph upgrade status (Frank, Changcheng) 3. DevStack status update (Yi/Dean) 4. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Sun, Austin; Liu, ZhipengS; Wold, Saul; Shang, Dehao; Troyer, Dean; Jones, Bruce E; Lin, Shuicheng; Zhu, Vivian; Hu, Yong; 'Khalil, Ghada'; Somerville, Jim; 'Rowsell, Brent'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Hu, Wei W; Gomez, Juan P; Cobbley, David A; Arce Moreno, Abraham; Lara, Cesar; Perez Carranza, Jose; Armstrong, Robert H; Martinez Landa, Hayde; Martinez Monroy, Elio; Fang, Liang A; 'Seiler, Glenn'; 'Chen, Jacky'; Perez Rodriguez, Humberto I; 'Young, Ken'; 'Waines, Greg'; 'Eslimi, Dariush'; 'Hellmann, Gil'; Poncea, Ovidiu Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 20, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From Barton.Wensley at windriver.com Tue Feb 19 13:13:24 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 19 Feb 2019 13:13:24 +0000 Subject: [Starlingx-discuss] Which code line created the users in keystone table local_user In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA66122@ALA-MBD.corp.ad.wrs.com> Liang, Today, the cinder user is created by puppet when it applies the ::cinder::keystone::auth class. You can see this class being included in stx-config/puppet-manifests/src/modules/openstack/manifests/cinder.pp. However, this puppet code will no longer be used, once we cut over to containers (in the next week or so I think). After that, the cinder user would be created by the application of helm charts. You can see the overrides for the cinder helm chart being populated at stx-config/sysinv/sysinv/sysinv/helm/cinder.py. I would recommend you start working with the helm charts in the containers environment, since the puppet code will be gone soon. Bart From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: February 18, 2019 3:20 AM To: Wensley, Barton; Penney, Don Cc: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: Which code line created the users in keystone table local_user Hi Bart and Don In keystone table 'local_user', there's lots of users created (see below), could you please point out which code line created these users? [Bart] Table deleted due to mailing list size restrictions that were apparently defined when we were all using 300 baud modems... The background: In code review https://review.openstack.org/#/c/633400/, we need to create an internal project and user for raw cache. Currently I use puppet to call cmd "openstack" to create/get the project/user id. I found the user(cinder) has already been created by some existing code, see above picture please. So I'm expecting to create internal project the same way as internal user. Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Tue Feb 19 14:38:10 2019 From: austin.sun at intel.com (Sun, Austin) Date: Tue, 19 Feb 2019 14:38:10 +0000 Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Message-ID: Hi All: I'm deploying duplex container mode with latest code . meet some error for neutron-ovs-agent Both controller have same configuration and deploy in virtual machine (qemu kvm env) . Does anyone have similar experience and suggest how to solve it ? *) The status of neutron-ovs-agent: neutron-ovs-agent-controller-0-a762cb46-h9xqw 0/1 Init:CrashLoopBackOff 11 42m neutron-ovs-agent-controller-1-f2c6aeed-427h8 1/1 Running 0 42m *) The log of neutron-ovs-agent-controller-0-a762cb46-h9xqw is : + timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so pleas e use SIGUSR2 to generate reports. 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] Logging enabled! 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 11.0.0 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch/impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfa ces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib [-] Timed out retrieving ofport on port 192.0.2.1.: RetryError: RetryError[] 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib Traceback (most recent call last): 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", lin e 321, in get_port_ofport 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib ofport = self._get_port_val(port_name, "ofport") 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 89, in wrapped 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return new_fn(*args, **kwargs) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 171, in wrapped_f 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return self.call(f, *args, **kw) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 248, in call 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib start_time=start_time) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 216, in iter 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise RetryError(fut).reraise() 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 298, in reraise 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise self 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib RetryError: RetryError[ From Al.Bailey at windriver.com Tue Feb 19 15:58:35 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 19 Feb 2019 15:58:35 +0000 Subject: [Starlingx-discuss] Nominate Don Penney as stx-upstream core Message-ID: I'd like to add Don Penney as a core reviewer for stx-upstream. Don has been contributing to the stx-upstream project since it was created and has been both a valuable and responsive reviewer and code author. I'd like confirmation (or objections) from the existing cores please... Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Richard at windriver.com Tue Feb 19 17:09:51 2019 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Tue, 19 Feb 2019 17:09:51 +0000 Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent In-Reply-To: References: Message-ID: <7B6A2AE64F40F245AE81F245059F0C366BE43190@ALA-MBD.corp.ad.wrs.com> Which build is this? Can you provide the contents of these files on your lab? /opt/platform/helm/19.01/openstack-neutron.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml Also, please provide the output of this command run on controller-0: ovs-vsctl show From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, February 19, 2019 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi All: I'm deploying duplex container mode with latest code . meet some error for neutron-ovs-agent Both controller have same configuration and deploy in virtual machine (qemu kvm env) . Does anyone have similar experience and suggest how to solve it ? *) The status of neutron-ovs-agent: neutron-ovs-agent-controller-0-a762cb46-h9xqw 0/1 Init:CrashLoopBackOff 11 42m neutron-ovs-agent-controller-1-f2c6aeed-427h8 1/1 Running 0 42m *) The log of neutron-ovs-agent-controller-0-a762cb46-h9xqw is : + timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so pleas e use SIGUSR2 to generate reports. 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] Logging enabled! 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 11.0.0 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch/impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfa ces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib [-] Timed out retrieving ofport on port 192.0.2.1.: RetryError: RetryError[] 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib Traceback (most recent call last): 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", lin e 321, in get_port_ofport 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib ofport = self._get_port_val(port_name, "ofport") 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 89, in wrapped 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return new_fn(*args, **kwargs) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 171, in wrapped_f 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return self.call(f, *args, **kw) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 248, in call 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib start_time=start_time) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 216, in iter 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise RetryError(fut).reraise() 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 298, in reraise 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise self 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib RetryError: RetryError[ From erich.cordoba.malibran at intel.com Tue Feb 19 17:49:26 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 19 Feb 2019 17:49:26 +0000 Subject: [Starlingx-discuss] [Build] Removing Makefile for docker base image creation. Message-ID: <6d375bb9568383814bdfebf5eb67eb245f730d44.camel@intel.com> Hi all, Trying to fix this bug[0], I realize that the Makefile used to create the docker build base image can be removed in favor of the tb.sh script. I'm proposing this change[1] that will help to enable building in non- ubuntu systems. Also, I'm updating the documentation[2]. This change could break some workflows, please let me know if you have any objection. Best regards. -Erich [0] https://storyboard.openstack.org/#!/story/2002560 [1] https://review.openstack.org/#/c/637944/2 [2] https://review.openstack.org/#/c/637946/ From Bill.Zvonar at windriver.com Tue Feb 19 18:43:44 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Tue, 19 Feb 2019 18:43:44 +0000 Subject: [Starlingx-discuss] Call for Agenda Items for Community Call (Feb 20, 2019) Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A06D70@ALA-MBD.corp.ad.wrs.com> Hi folks - for tomorrow's Community call, please add any items you'd like to see on the agenda to the etherpad [1]. Thanks, Bill... [0] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_PDT_.2F_1500_UTC_-_Community_Call [1] etherpad: https://etherpad.openstack.org/p/stx-status -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Feb 19 20:50:08 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 19 Feb 2019 21:50:08 +0100 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit Message-ID: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> Hi, I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ Is there a need to request an extended slot for the project update? Please let me know if you have any questions. Thanks, Ildikó From Brent.Rowsell at windriver.com Tue Feb 19 21:34:34 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Tue, 19 Feb 2019 21:34:34 +0000 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit In-Reply-To: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> References: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> Message-ID: <2739FAC9-F55E-4742-9D1A-8D2896D4A727@windriver.com> Hi, I volunteer for the project update session Brent Sent from my iPhone > On Feb 19, 2019, at 2:50 PM, Ildiko Vancsa wrote: > > Hi, > > I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. > > This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. > > The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. > > The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. > > I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ > > Is there a need to request an extended slot for the project update? > > Please let me know if you have any questions. > > Thanks, > Ildikó > > > > _______________________________________________ > 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 Tue Feb 19 22:45:30 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 19 Feb 2019 22:45:30 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190219 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C446@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-19 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Tue Feb 19 22:49:03 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 19 Feb 2019 22:49:03 +0000 Subject: [Starlingx-discuss] Volumes take a long time to create and to delete Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C469@FMSMSX108.amr.corp.intel.com> Hi, Did someone figured out that volumes take a long time to create and to delete in a STX virtual environment (No Containers)? About 20 minutes to be created and about 5 minutes to be deleted. Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Feb 19 23:06:37 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 19 Feb 2019 23:06:37 +0000 Subject: [Starlingx-discuss] [ Test ] meeting minutes - 02/19/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD75BB4@FMSMSX114.amr.corp.intel.com> Agenda for 02/19/2019 Attendees: Abraham, Chris, Cristopher, Elio, JC, JP, Gerry, Victor, Numan, Ada, Jose, Fer 1. Repo status - submissions tried? - Ada - 15 min - Jose will try the submission to the repo today/tomorrow early. Sync with Cristopher for any requirements. - Maria Y. will try submission for the Ceph tests. Ask Cristopher for help if needed. Try to do it by EOW. Closure on how to submit the tests - gather by sub-domain. Numan sent the template. - https://drive.google.com/open?id=1EJnQrz-JSafVW9ZNYBbGdo0TgwcrfI9w 2. Progress on regression tests selection - Elio, JP, Fer, Numan, Ada - 10 min - Elio - 150 test selected, working on the update. Working with Forrest and other person for OVS-DPDK. ~70 don't have steps. Submission will begin this week. Include Numan into the loop for the updates of the networking tests. - JP - Gnocchi and simplex are almost finished. Working on completing the steps. - Fer - Security selection is done. Working on update for new architecture. Horizon selection done, considering the two horizon for containers. Working also in Heat selection. - Ada - system inventory and system test. Selection to be done this week. - Numan - progress going well. Test cases being selected and updated as required. Then, those will be exported into text format and adapted to the format proposed. Next step will be to upload them. Expectation is to have all the domains ready by end of next week. 3. OPNFV test suite for performance metrics - status - Victor - 10 min - Instructions received from Numan's team. Will work this week for the first installation. Will try on a virtual env. Then, try with simplex on bare metal. - Define if this is going to be on containers or standard setup. - Begin simple: try to not do complex configuration. Numan's team setup is on regular arch, not containers. - Help required - extra hands are welcome :) 4. Opens - All - 15 min - Elio - are we including tempest into our testing? Yes - let's assign someone to work on set it up and how to run it using our containerized STX. - Abraham - on the release notes topic. There are a couple of testing projects that use the release notes: tempest and sahara. (Include the links) Tempest - https://docs.openstack.org/releasenotes/tempest/v19.0.0.html Sahara - https://docs.openstack.org/releasenotes/sahara-tests/unreleased.html#relnotes-0-7-0-14 Jose - for big changes it will be good to have release notes. Elio - good to have release notes for new test plans and bug fixing. Numan - for big changes is fine. Decision - use release notes for big changes and critical bug fixing. - Link to demo recording - https://zoom.us/recording/share/PFaZXVJt6hlZpZdBM5tyYmoveZc4skAjUzZ7hq8e_a2wIumekTziMw starting at 00:56 - Ada to ask Ildiko on how to watch the recording of the meetings. links are not available, but she shared the one for the demo (included). From changcheng.liu at intel.com Tue Feb 19 02:42:31 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Tue, 19 Feb 2019 02:42:31 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F7063E@SHSMSX104.ccr.corp.intel.com> Hi all, 3/3 times failed to build below SRC RPMs in StarlingX: 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpmDoes anyone know how to solve problem? Does anyone know how to solve it? I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: tpm2_build.log Type: application/octet-stream Size: 5691 bytes Desc: tpm2_build.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: tss2_build.log Type: application/octet-stream Size: 14511 bytes Desc: tss2_build.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build_log Type: application/octet-stream Size: 271284 bytes Desc: build_log URL: From xiongzhiwei at baicells.com Tue Feb 19 07:16:39 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Tue, 19 Feb 2019 15:16:39 +0800 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration References: , , <201902191456126968489@baicells.com>, Message-ID: <2019021915163953671221@baicells.com> Hi Jaewook, My ip setting is as below: Actually, I had used three physical interface, enp2s0f0 is OAM inf with default ip 10.10.10.2/24, because it is not inconvenient in my operation room, so I had configured enp2s0f1 for my romote access. I can access the dashboard both with ip 10.10.10.2 in lab and 192.168.107.232/22 in my operation room. The third inf enp2s0f2 is used to data interface, I had created three VMs and network worked normally. controller-0:~$ ip a 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 192.168.204.3/28 brd 192.168.204.15 scope host lo valid_lft forever preferred_lft forever inet 169.254.202.2/24 scope host lo valid_lft forever preferred_lft forever inet 192.168.204.2/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.5/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.10/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.6/28 scope host secondary lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff 3: enp2s0f0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 valid_lft forever preferred_lft forever inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link valid_lft forever preferred_lft forever 4: enp2s0f1: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 valid_lft forever preferred_lft forever inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link valid_lft forever preferred_lft forever 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff 8: br-int: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff 12: br-phy0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link valid_lft forever preferred_lft forever 13: lldp0d64ae5d-22: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff inet6 fe80::94e0:3ff:fe51:176d/64 scope link valid_lft forever preferred_lft forever BR Tim Xiong From: Jaewook Oh Date: 2019-02-19 15:00 To: xiongzhiwei at baicells.com CC: starlingx-discuss; 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello Tim, thanks for your answer :) However, still I cannot access to the dashboard. I deployed StarlingX 3 times again, but the situation never changes.. If you don't mind, can I see your ip setting with (ip a command)? Best Regards, Jaewook. 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com 님이 작성: Hi Jaewook, I just finished stx all-in-one simplex on Bearmetal last week. The horizon service had been installed defaultly and you should be able to access the dashboard now. Your service list is same as mine. [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | | df07161f527b483292ac5aa5ed722687 | keystone | identity | | 744183df128d414f97390fb70fcac72f | sysinv | platform | | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | | 5d7855696b1f440b8401670e1df6cb28 | glance | image | | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | | 68362243cc214c4181a15e583894e495 | placement | placement | | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | | cbf811729020470a81b3c7be0d453fc9 | neutron | network | | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | | bc5297541def4f8b8881254af9896824 | smapi | smapi | | a388667479484a04824f07a672a331eb | panko | event | | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | | 253390980b274178b7a16844e2c7a826 | cinder | volume | +----------------------------------+------------+-----------------+ BR Tim Xiong From: Jaewook Oh Date: 2019-02-19 12:48 To: starlingx-discuss; 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello StarlingX Teams, I found that the horizon dashboard project were not installed automatically when I deployed StarlingX all-in-one simplex on Baremetal. Are there any reason for this problem..? I used "2019-Feb-08 03:40:29 bootimage.iso". [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | | ecf3478c84334c2ba647740bde190739 | neutron | network | | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | | 57a5cb58128445b5819747271c095a89 | heat | orchestration | | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | +----------------------------------+------------+-----------------+ I thought horizon should also be installed with StarlingX's deployment. If not, please let me know how can I install horizon in this StarlingX. Thanks for help in advance :) Best Regards, Jaewook. 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. However I cannot access to the dashboard. I used "2019-Feb-08 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons. And also I had a problem when I followed the installation instruction. [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found." So I googled and I figured out I should command $ system datanetwork-add providernet-a vlan first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Tue Feb 19 07:34:04 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Tue, 19 Feb 2019 16:34:04 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: <2019021915163953671221@baicells.com> References: <201902191456126968489@baicells.com> <2019021915163953671221@baicells.com> Message-ID: Thank you very much Tim, I really appreciate you :) I'm now trying to reinstall StarlingX. Whether the deployment succeeds or not, I'll report it. BR Jaewook. 2019년 2월 19일 (화) 오후 4:16, xiongzhiwei at baicells.com 님이 작성: > Hi Jaewook, > > My ip setting is as below: > Actually, I had used three physical interface, enp2s0f0 is OAM inf with > default ip 10.10.10.2/24, because it is not inconvenient in my operation > room, so I had configured enp2s0f1 for my romote access. > I can access the dashboard both with ip 10.10.10.2 in lab and > 192.168.107.232/22 in my operation room. > The third inf enp2s0f2 is used to data interface, I had created three VMs > and network worked normally. > > > controller-0:~$ ip a > 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group > default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 192.168.204.3/28 brd 192.168.204.15 scope host lo > valid_lft forever preferred_lft forever > inet 169.254.202.2/24 scope host lo > valid_lft forever preferred_lft forever > inet 192.168.204.2/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.5/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.10/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.6/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group > default qlen 1000 > link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff > 3: enp2s0f0: mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff > inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 > valid_lft forever preferred_lft forever > inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link > valid_lft forever preferred_lft forever > 4: enp2s0f1: mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff > inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 > valid_lft forever preferred_lft forever > inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link > valid_lft forever preferred_lft forever > 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group > default qlen 1000 > link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff > 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff > 8: br-int: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff > 12: br-phy0: mtu 1500 qdisc pfifo_fast > state UNKNOWN group default qlen 1000 > link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link > valid_lft forever preferred_lft forever > 13: lldp0d64ae5d-22: mtu 1500 qdisc > pfifo_fast state UNKNOWN group default qlen 1000 > link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff > inet6 fe80::94e0:3ff:fe51:176d/64 scope link > valid_lft forever preferred_lft forever > > > BR > Tim Xiong > > > *From:* Jaewook Oh > *Date:* 2019-02-19 15:00 > *To:* xiongzhiwei at baicells.com > *CC:* starlingx-discuss ; 오재욱 > > *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy > All-in-one simplex configuration > Hello Tim, > > thanks for your answer :) > > However, still I cannot access to the dashboard. > > I deployed StarlingX 3 times again, but the situation never changes.. > > If you don't mind, can I see your ip setting with (ip a command)? > > Best Regards, > Jaewook. > > 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com < > xiongzhiwei at baicells.com>님이 작성: > >> Hi Jaewook, >> >> I just finished stx all-in-one simplex on Bearmetal last week. The >> horizon service had been installed defaultly and you should be able to >> access the dashboard now. >> Your service list is same as mine. >> >> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >> +----------------------------------+------------+-----------------+ >> | ID | Name | Type | >> +----------------------------------+------------+-----------------+ >> | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | >> | df07161f527b483292ac5aa5ed722687 | keystone | identity | >> | 744183df128d414f97390fb70fcac72f | sysinv | platform | >> | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | >> | 5d7855696b1f440b8401670e1df6cb28 | glance | image | >> | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | >> | 68362243cc214c4181a15e583894e495 | placement | placement | >> | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | >> | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | >> | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | >> | cbf811729020470a81b3c7be0d453fc9 | neutron | network | >> | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | >> | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | >> | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | >> | bc5297541def4f8b8881254af9896824 | smapi | smapi | >> | a388667479484a04824f07a672a331eb | panko | event | >> | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | >> | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | >> | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | >> | 253390980b274178b7a16844e2c7a826 | cinder | volume | >> +----------------------------------+------------+-----------------+ >> >> BR >> Tim Xiong >> >> *From:* Jaewook Oh >> *Date:* 2019-02-19 12:48 >> *To:* starlingx-discuss ; 오재욱 >> >> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >> All-in-one simplex configuration >> Hello StarlingX Teams, >> >> I found that *the horizon dashboard project were not installed >> automatically* when I deployed StarlingX all-in-one simplex on Baremetal. >> Are there any reason for this problem..? >> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >> >> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >> +----------------------------------+------------+-----------------+ >> | ID | Name | Type | >> +----------------------------------+------------+-----------------+ >> | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | >> | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | >> | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | >> | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | >> | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | >> | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | >> | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | >> | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | >> | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | >> | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | >> | ecf3478c84334c2ba647740bde190739 | neutron | network | >> | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | >> | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | >> | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | >> | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | >> | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | >> | 57a5cb58128445b5819747271c095a89 | heat | orchestration | >> | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | >> | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | >> | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | >> +----------------------------------+------------+-----------------+ >> >> I thought horizon should also be installed with StarlingX's deployment. >> If not, please let me know how can I install horizon in this StarlingX. >> >> Thanks for help in advance :) >> >> Best Regards, >> Jaewook. >> >> >> 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: >> >>> Hello starlingx team, >>> >>> I deployed Starlingx All-in-one simplex setting on my server, >>> it seems deployment was done well. >>> *However I cannot access to the dashboard.* >>> >>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>> >>> >>> Following log is the service that are now enabled, >>> [wrsroot at controller-0 ~(keystone_admin)]$ system service-list >>> +-----+-------------------------------+--------------+----------------+ >>> | id | service_name | hostname | state | >>> +-----+-------------------------------+--------------+----------------+ >>> | 68 | aodh-api | controller-0 | enabled-active | >>> | 69 | aodh-evaluator | controller-0 | enabled-active | >>> | 70 | aodh-listener | controller-0 | enabled-active | >>> | 71 | aodh-notifier | controller-0 | enabled-active | >>> | 102 | barbican-api | controller-0 | enabled-active | >>> | 103 | barbican-keystone-listener | controller-0 | enabled-active | >>> | 104 | barbican-worker | controller-0 | enabled-active | >>> | 43 | ceilometer-agent-notification | controller-0 | enabled-active | >>> | 14 | cgcs-export-fs | controller-0 | enabled-active | >>> | 10 | cgcs-fs | controller-0 | enabled-active | >>> | 16 | cgcs-nfs-ip | controller-0 | enabled-active | >>> | 35 | cinder-api | controller-0 | enabled-active | >>> | 38 | cinder-backup | controller-0 | enabled-active | >>> | 58 | cinder-ip | controller-0 | enabled-active | >>> | 56 | cinder-lvm | controller-0 | enabled-active | >>> | 36 | cinder-scheduler | controller-0 | enabled-active | >>> | 37 | cinder-volume | controller-0 | enabled-active | >>> | 23 | dnsmasq | controller-0 | enabled-active | >>> | 5 | drbd-cgcs | controller-0 | enabled-active | >>> | 55 | drbd-cinder | controller-0 | enabled-active | >>> | 75 | drbd-extension | controller-0 | enabled-active | >>> | 3 | drbd-pg | controller-0 | enabled-active | >>> | 6 | drbd-platform | controller-0 | enabled-active | >>> | 4 | drbd-rabbit | controller-0 | enabled-active | >>> | 77 | extension-export-fs | controller-0 | enabled-active | >>> | 76 | extension-fs | controller-0 | enabled-active | >>> | 24 | fm-mgr | controller-0 | enabled-active | >>> | 27 | glance-api | controller-0 | enabled-active | >>> | 26 | glance-registry | controller-0 | enabled-active | >>> | 108 | gnocchi-api | controller-0 | enabled-active | >>> | 109 | gnocchi-metricd | controller-0 | enabled-active | >>> | 62 | guest-agent | controller-0 | enabled-active | >>> | 64 | haproxy | controller-0 | enabled-active | >>> | 45 | heat-api | controller-0 | enabled-active | >>> | 46 | heat-api-cfn | controller-0 | enabled-active | >>> | 47 | heat-api-cloudwatch | controller-0 | enabled-active | >>> | 44 | heat-engine | controller-0 | enabled-active | >>> | 51 | horizon | controller-0 | enabled-active | >>> | 22 | hw-mon | controller-0 | enabled-active | >>> | 57 | iscsi | controller-0 | enabled-active | >>> | 25 | keystone | controller-0 | enabled-active | >>> | 50 | lighttpd | controller-0 | enabled-active | >>> | 2 | management-ip | controller-0 | enabled-active | >>> | 20 | mtc-agent | controller-0 | enabled-active | >>> | 28 | neutron-server | controller-0 | enabled-active | >>> | 9 | nfs-mgmt | controller-0 | enabled-active | >>> | 29 | nova-api | controller-0 | enabled-active | >>> | 63 | nova-api-proxy | controller-0 | enabled-active | >>> | 31 | nova-conductor | controller-0 | enabled-active | >>> | 33 | nova-console-auth | controller-0 | enabled-active | >>> | 34 | nova-novnc | controller-0 | enabled-active | >>> | 83 | nova-placement-api | controller-0 | enabled-active | >>> | 30 | nova-scheduler | controller-0 | enabled-active | >>> | 48 | open-ldap | controller-0 | enabled-active | >>> | 82 | panko-api | controller-0 | enabled-active | >>> | 52 | patch-alarm-manager | controller-0 | enabled-active | >>> | 7 | pg-fs | controller-0 | enabled-active | >>> | 15 | platform-export-fs | controller-0 | enabled-active | >>> | 11 | platform-fs | controller-0 | enabled-active | >>> | 17 | platform-nfs-ip | controller-0 | enabled-active | >>> | 12 | postgres | controller-0 | enabled-active | >>> | 65 | pxeboot-ip | controller-0 | enabled-active | >>> | 13 | rabbit | controller-0 | enabled-active | >>> | 8 | rabbit-fs | controller-0 | enabled-active | >>> | 49 | snmp | controller-0 | enabled-active | >>> | 19 | sysinv-conductor | controller-0 | enabled-active | >>> | 18 | sysinv-inv | controller-0 | enabled-active | >>> | 59 | vim | controller-0 | enabled-active | >>> | 60 | vim-api | controller-0 | enabled-active | >>> | 61 | vim-webserver | controller-0 | enabled-active | >>> +-----+-------------------------------+--------------+----------------+ >>> >>> As you can see, *I cannot find #1 service (oam-ip)*, and I think this >>> is one of the main reasons. >>> >>> *And also I had a problem when I followed the installation instruction.* >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan >>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a >>> >>> >>> Above instruction was not naturally worked, I mean the third command, >>> 'host-if-modify' failed with the message "*DataNetwork providernet-a >>> could not be found*." >>> >>> So I googled and I figured out I should command >>> $ *system datanetwork-add providernet-a vlan* >>> first. >>> >>> But I remember when my first deployment succeed, I didn't need to use >>> that command at all. (The deployment was implemented on Jan.) >>> >>> Any help is appreciated, thank you for your help in advance. >>> >>> Best Regards, >>> Jaewook. >>> >>> ================================================ >>> *Jaewook Oh* (오재욱) >>> IISTRC - Internet Infra System Technology Research Center >>> 369 Sangdo-ro, Dongjak-gu, >>> 06978, Seoul, Republic of Korea >>> >> >> >> -- >> ================================================ >> *Jaewook Oh* (오재욱) >> IISTRC - Internet Infra System Technology Research Center >> 369 Sangdo-ro, Dongjak-gu, >> 06978, Seoul, Republic of Korea >> >> > > -- > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Tue Feb 19 11:52:44 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Tue, 19 Feb 2019 20:52:44 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: <2019021915163953671221@baicells.com> References: <201902191456126968489@baicells.com> <2019021915163953671221@baicells.com> Message-ID: Unfortunately, still I cannot access dashboard. I'll try another latest boot image. Thank you for all helps :) BR. Jaewook. 2019년 2월 19일 (화) 오후 4:16, xiongzhiwei at baicells.com 님이 작성: > Hi Jaewook, > > My ip setting is as below: > Actually, I had used three physical interface, enp2s0f0 is OAM inf with > default ip 10.10.10.2/24, because it is not inconvenient in my operation > room, so I had configured enp2s0f1 for my romote access. > I can access the dashboard both with ip 10.10.10.2 in lab and > 192.168.107.232/22 in my operation room. > The third inf enp2s0f2 is used to data interface, I had created three VMs > and network worked normally. > > > controller-0:~$ ip a > 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group > default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 192.168.204.3/28 brd 192.168.204.15 scope host lo > valid_lft forever preferred_lft forever > inet 169.254.202.2/24 scope host lo > valid_lft forever preferred_lft forever > inet 192.168.204.2/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.5/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.10/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet 192.168.204.6/28 scope host secondary lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group > default qlen 1000 > link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff > 3: enp2s0f0: mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff > inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 > valid_lft forever preferred_lft forever > inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link > valid_lft forever preferred_lft forever > 4: enp2s0f1: mtu 1500 qdisc mq state UP > group default qlen 1000 > link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff > inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 > valid_lft forever preferred_lft forever > inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link > valid_lft forever preferred_lft forever > 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group > default qlen 1000 > link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff > 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff > 8: br-int: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff > 12: br-phy0: mtu 1500 qdisc pfifo_fast > state UNKNOWN group default qlen 1000 > link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff > inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link > valid_lft forever preferred_lft forever > 13: lldp0d64ae5d-22: mtu 1500 qdisc > pfifo_fast state UNKNOWN group default qlen 1000 > link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff > inet6 fe80::94e0:3ff:fe51:176d/64 scope link > valid_lft forever preferred_lft forever > > > BR > Tim Xiong > > > *From:* Jaewook Oh > *Date:* 2019-02-19 15:00 > *To:* xiongzhiwei at baicells.com > *CC:* starlingx-discuss ; 오재욱 > > *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy > All-in-one simplex configuration > Hello Tim, > > thanks for your answer :) > > However, still I cannot access to the dashboard. > > I deployed StarlingX 3 times again, but the situation never changes.. > > If you don't mind, can I see your ip setting with (ip a command)? > > Best Regards, > Jaewook. > > 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com < > xiongzhiwei at baicells.com>님이 작성: > >> Hi Jaewook, >> >> I just finished stx all-in-one simplex on Bearmetal last week. The >> horizon service had been installed defaultly and you should be able to >> access the dashboard now. >> Your service list is same as mine. >> >> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >> +----------------------------------+------------+-----------------+ >> | ID | Name | Type | >> +----------------------------------+------------+-----------------+ >> | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | >> | df07161f527b483292ac5aa5ed722687 | keystone | identity | >> | 744183df128d414f97390fb70fcac72f | sysinv | platform | >> | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | >> | 5d7855696b1f440b8401670e1df6cb28 | glance | image | >> | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | >> | 68362243cc214c4181a15e583894e495 | placement | placement | >> | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | >> | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | >> | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | >> | cbf811729020470a81b3c7be0d453fc9 | neutron | network | >> | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | >> | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | >> | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | >> | bc5297541def4f8b8881254af9896824 | smapi | smapi | >> | a388667479484a04824f07a672a331eb | panko | event | >> | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | >> | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | >> | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | >> | 253390980b274178b7a16844e2c7a826 | cinder | volume | >> +----------------------------------+------------+-----------------+ >> >> BR >> Tim Xiong >> >> *From:* Jaewook Oh >> *Date:* 2019-02-19 12:48 >> *To:* starlingx-discuss ; 오재욱 >> >> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >> All-in-one simplex configuration >> Hello StarlingX Teams, >> >> I found that *the horizon dashboard project were not installed >> automatically* when I deployed StarlingX all-in-one simplex on Baremetal. >> Are there any reason for this problem..? >> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >> >> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >> +----------------------------------+------------+-----------------+ >> | ID | Name | Type | >> +----------------------------------+------------+-----------------+ >> | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | >> | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | >> | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | >> | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | >> | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | >> | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | >> | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | >> | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | >> | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | >> | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | >> | ecf3478c84334c2ba647740bde190739 | neutron | network | >> | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | >> | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | >> | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | >> | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | >> | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | >> | 57a5cb58128445b5819747271c095a89 | heat | orchestration | >> | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | >> | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | >> | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | >> +----------------------------------+------------+-----------------+ >> >> I thought horizon should also be installed with StarlingX's deployment. >> If not, please let me know how can I install horizon in this StarlingX. >> >> Thanks for help in advance :) >> >> Best Regards, >> Jaewook. >> >> >> 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: >> >>> Hello starlingx team, >>> >>> I deployed Starlingx All-in-one simplex setting on my server, >>> it seems deployment was done well. >>> *However I cannot access to the dashboard.* >>> >>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>> >>> >>> Following log is the service that are now enabled, >>> [wrsroot at controller-0 ~(keystone_admin)]$ system service-list >>> +-----+-------------------------------+--------------+----------------+ >>> | id | service_name | hostname | state | >>> +-----+-------------------------------+--------------+----------------+ >>> | 68 | aodh-api | controller-0 | enabled-active | >>> | 69 | aodh-evaluator | controller-0 | enabled-active | >>> | 70 | aodh-listener | controller-0 | enabled-active | >>> | 71 | aodh-notifier | controller-0 | enabled-active | >>> | 102 | barbican-api | controller-0 | enabled-active | >>> | 103 | barbican-keystone-listener | controller-0 | enabled-active | >>> | 104 | barbican-worker | controller-0 | enabled-active | >>> | 43 | ceilometer-agent-notification | controller-0 | enabled-active | >>> | 14 | cgcs-export-fs | controller-0 | enabled-active | >>> | 10 | cgcs-fs | controller-0 | enabled-active | >>> | 16 | cgcs-nfs-ip | controller-0 | enabled-active | >>> | 35 | cinder-api | controller-0 | enabled-active | >>> | 38 | cinder-backup | controller-0 | enabled-active | >>> | 58 | cinder-ip | controller-0 | enabled-active | >>> | 56 | cinder-lvm | controller-0 | enabled-active | >>> | 36 | cinder-scheduler | controller-0 | enabled-active | >>> | 37 | cinder-volume | controller-0 | enabled-active | >>> | 23 | dnsmasq | controller-0 | enabled-active | >>> | 5 | drbd-cgcs | controller-0 | enabled-active | >>> | 55 | drbd-cinder | controller-0 | enabled-active | >>> | 75 | drbd-extension | controller-0 | enabled-active | >>> | 3 | drbd-pg | controller-0 | enabled-active | >>> | 6 | drbd-platform | controller-0 | enabled-active | >>> | 4 | drbd-rabbit | controller-0 | enabled-active | >>> | 77 | extension-export-fs | controller-0 | enabled-active | >>> | 76 | extension-fs | controller-0 | enabled-active | >>> | 24 | fm-mgr | controller-0 | enabled-active | >>> | 27 | glance-api | controller-0 | enabled-active | >>> | 26 | glance-registry | controller-0 | enabled-active | >>> | 108 | gnocchi-api | controller-0 | enabled-active | >>> | 109 | gnocchi-metricd | controller-0 | enabled-active | >>> | 62 | guest-agent | controller-0 | enabled-active | >>> | 64 | haproxy | controller-0 | enabled-active | >>> | 45 | heat-api | controller-0 | enabled-active | >>> | 46 | heat-api-cfn | controller-0 | enabled-active | >>> | 47 | heat-api-cloudwatch | controller-0 | enabled-active | >>> | 44 | heat-engine | controller-0 | enabled-active | >>> | 51 | horizon | controller-0 | enabled-active | >>> | 22 | hw-mon | controller-0 | enabled-active | >>> | 57 | iscsi | controller-0 | enabled-active | >>> | 25 | keystone | controller-0 | enabled-active | >>> | 50 | lighttpd | controller-0 | enabled-active | >>> | 2 | management-ip | controller-0 | enabled-active | >>> | 20 | mtc-agent | controller-0 | enabled-active | >>> | 28 | neutron-server | controller-0 | enabled-active | >>> | 9 | nfs-mgmt | controller-0 | enabled-active | >>> | 29 | nova-api | controller-0 | enabled-active | >>> | 63 | nova-api-proxy | controller-0 | enabled-active | >>> | 31 | nova-conductor | controller-0 | enabled-active | >>> | 33 | nova-console-auth | controller-0 | enabled-active | >>> | 34 | nova-novnc | controller-0 | enabled-active | >>> | 83 | nova-placement-api | controller-0 | enabled-active | >>> | 30 | nova-scheduler | controller-0 | enabled-active | >>> | 48 | open-ldap | controller-0 | enabled-active | >>> | 82 | panko-api | controller-0 | enabled-active | >>> | 52 | patch-alarm-manager | controller-0 | enabled-active | >>> | 7 | pg-fs | controller-0 | enabled-active | >>> | 15 | platform-export-fs | controller-0 | enabled-active | >>> | 11 | platform-fs | controller-0 | enabled-active | >>> | 17 | platform-nfs-ip | controller-0 | enabled-active | >>> | 12 | postgres | controller-0 | enabled-active | >>> | 65 | pxeboot-ip | controller-0 | enabled-active | >>> | 13 | rabbit | controller-0 | enabled-active | >>> | 8 | rabbit-fs | controller-0 | enabled-active | >>> | 49 | snmp | controller-0 | enabled-active | >>> | 19 | sysinv-conductor | controller-0 | enabled-active | >>> | 18 | sysinv-inv | controller-0 | enabled-active | >>> | 59 | vim | controller-0 | enabled-active | >>> | 60 | vim-api | controller-0 | enabled-active | >>> | 61 | vim-webserver | controller-0 | enabled-active | >>> +-----+-------------------------------+--------------+----------------+ >>> >>> As you can see, *I cannot find #1 service (oam-ip)*, and I think this >>> is one of the main reasons. >>> >>> *And also I had a problem when I followed the installation instruction.* >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan >>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a >>> >>> >>> Above instruction was not naturally worked, I mean the third command, >>> 'host-if-modify' failed with the message "*DataNetwork providernet-a >>> could not be found*." >>> >>> So I googled and I figured out I should command >>> $ *system datanetwork-add providernet-a vlan* >>> first. >>> >>> But I remember when my first deployment succeed, I didn't need to use >>> that command at all. (The deployment was implemented on Jan.) >>> >>> Any help is appreciated, thank you for your help in advance. >>> >>> Best Regards, >>> Jaewook. >>> >>> ================================================ >>> *Jaewook Oh* (오재욱) >>> IISTRC - Internet Infra System Technology Research Center >>> 369 Sangdo-ro, Dongjak-gu, >>> 06978, Seoul, Republic of Korea >>> >> >> >> -- >> ================================================ >> *Jaewook Oh* (오재욱) >> IISTRC - Internet Infra System Technology Research Center >> 369 Sangdo-ro, Dongjak-gu, >> 06978, Seoul, Republic of Korea >> >> > > -- > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From changcheng.liu at intel.com Wed Feb 20 01:21:01 2019 From: changcheng.liu at intel.com (Liu, Changcheng) Date: Wed, 20 Feb 2019 01:21:01 +0000 Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 In-Reply-To: <0D7994A90DD70040A9F5E77C4D23C57D50F7063E@SHSMSX104.ccr.corp.intel.com> References: <0D7994A90DD70040A9F5E77C4D23C57D50F7063E@SHSMSX104.ccr.corp.intel.com> Message-ID: <0D7994A90DD70040A9F5E77C4D23C57D50F70F5A@SHSMSX104.ccr.corp.intel.com> Please ignore this email. Something wrong with my email client. From: Liu, Changcheng [mailto:changcheng.liu at intel.com] Sent: Tuesday, February 19, 2019 10:43 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] fail to build src rpm: tpm2-openssl and tss2-930-1 Hi all, 3/3 times failed to build below SRC RPMs in StarlingX: 2897 10:24:22 *** Build Failed *** 2898 10:24:22 Tried 3 times - following pkgs could not be successfully built: 2899 10:24:22 *** Build Failed *** 2900 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tss2-930-1.tis.1.src.rpm 2901 10:24:22 /localdisk/loadbuild/nstcc1/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpmDoes anyone know how to solve problem? Does anyone know how to solve it? I see some patches are merged into master branch: https://review.openstack.org/#/q/branch:master+project:openstack/stx-tools+status:merged Is there any patch used to fix the build problem? Build commands: [nstcc1 at nstcloudcc1 starlingx]$ build-pkgs 2>&1 | tee build_log B.R. Changcheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From shuicheng.lin at intel.com Wed Feb 20 02:40:33 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 20 Feb 2019 02:40:33 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng ; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Feb 20 02:41:02 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 19 Feb 2019 18:41:02 -0800 Subject: [Starlingx-discuss] [all] Denver Forum Brainstorming Message-ID: Hello Everyone! Welcome to the topic selection process for our Forum in Denver! This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. For OpenStack Denver marks the beginning of Train’s release cycle, where ideas and requirements will be gathered. We should come armed with feedback from the upcoming Stein release if at all possible. We aim to ensure the broadest coverage of topics that will allow for multiple parts of the community getting together to discuss key areas within our community/projects. For OSF Projects (StarlingX, Zuul, Airship, Kata Containers) As a refresher, the idea is to gather ideas and requirements for your project’s upcoming release. Look to https://wiki.openstack.org/wiki/Forum for an idea of how to structure fishbowls and discussions for your project. The idea is to ensure the broadest coverage of topics, while allowing for the project community to discuss critical areas of concern. To make sure we are presenting the best topics for discussion, we have asked representatives of each of your projects to help us out in the Forum selection process. There are two stages to the brainstorming: 1.If you haven’t already, its encouraged that you set up an etherpad with your team and start discussing ideas you'd like to talk about at the Forum and work out which ones to submit. 2. On the 22nd of February, we will open up a more formal web-based tool for you to submit abstracts for the most popular sessions that came out of your brainstorming. Make an etherpad and add it to the list at: https://wiki.openstack.org/wiki/Forum/Denver2018 This is your opportunity to think outside the box and talk with other projects, groups, and individuals that you might not see during Summit sessions. Look for interested parties to collaborate with and share your ideas. Examples of typical sessions that make for a great Forum: - Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies - eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal - Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community - eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. - Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release - eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. Think about what kind of session ideas might end up as: Project-specific, cross-project or strategic/whole-of-community discussions. There'll be more slots for the latter two, so do try and think outside the box! This part of the process is where we gather broad community consensus - in theory the second part is just about fitting in as many of the good ideas into the schedule as we can. Further details about the forum can be found at: https://wiki.openstack.org/wiki/Forum Thanks all! Kendall Nelson, on behalf of the OpenStack Foundation, User Committee & Technical Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Wed Feb 20 07:36:26 2019 From: austin.sun at intel.com (Sun, Austin) Date: Wed, 20 Feb 2019 07:36:26 +0000 Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent In-Reply-To: <7B6A2AE64F40F245AE81F245059F0C366BE43190@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE43190@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Joseph: Thanks. The result of ovs-vsctl show is below: I have pasted the yaml files with below link. /opt/platform/helm/19.01/openstack-neutron.yaml http://paste.openstack.org/show/745435/ /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml http://paste.openstack.org/show/745436/ /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml http://paste.openstack.org/show/745437/ 168464a5-d278-47b8-a3b0-01f86cfec2bb Manager "ptcp:6640:127.0.0.1" Bridge "br-phy1" Port "lldp160b8b4f-a3" Interface "lldp160b8b4f-a3" type: internal Port "eth1" Interface "eth1" type: dpdk options: {dpdk-devargs="0000:02:04.0", n_rxq="2"} Port "br-phy1" Interface "br-phy1" type: internal Bridge "br-phy0" Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:03.0", n_rxq="2"} Port "br-phy0" Interface "br-phy0" type: internal Port "lldp706c54b4-b5" Interface "lldp706c54b4-b5" type: internal ovs_version: "2.9.0" Thanks. BR Austin Sun. From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Wednesday, February 20, 2019 1:10 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Which build is this? Can you provide the contents of these files on your lab? /opt/platform/helm/19.01/openstack-neutron.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml Also, please provide the output of this command run on controller-0: ovs-vsctl show From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, February 19, 2019 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi All: I'm deploying duplex container mode with latest code . meet some error for neutron-ovs-agent Both controller have same configuration and deploy in virtual machine (qemu kvm env) . Does anyone have similar experience and suggest how to solve it ? *) The status of neutron-ovs-agent: neutron-ovs-agent-controller-0-a762cb46-h9xqw 0/1 Init:CrashLoopBackOff 11 42m neutron-ovs-agent-controller-1-f2c6aeed-427h8 1/1 Running 0 42m *) The log of neutron-ovs-agent-controller-0-a762cb46-h9xqw is : + timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so pleas e use SIGUSR2 to generate reports. 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] Logging enabled! 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 11.0.0 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch/impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfa ces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib [-] Timed out retrieving ofport on port 192.0.2.1.: RetryError: RetryError[] 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib Traceback (most recent call last): 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", lin e 321, in get_port_ofport 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib ofport = self._get_port_val(port_name, "ofport") 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 89, in wrapped 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return new_fn(*args, **kwargs) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 171, in wrapped_f 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return self.call(f, *args, **kw) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 248, in call 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib start_time=start_time) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 216, in iter 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise RetryError(fut).reraise() 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 298, in reraise 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise self 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib RetryError: RetryError[ From zhang.kunpeng at 99cloud.net Wed Feb 20 13:57:22 2019 From: zhang.kunpeng at 99cloud.net (=?utf-8?B?5byg6bKy6bmP?=) Date: Wed, 20 Feb 2019 21:57:22 +0800 Subject: [Starlingx-discuss] =?utf-8?q?Please_help_for_stx-nova_patch_?= =?utf-8?q?=E2=80=9D01111_-_Exclude_current_instance_when_checking__server?= =?utf-8?q?_group_live_migrations=E2=80=9C?= Message-ID: <0615962F-A0BA-4EDB-8FC7-FDE35EF90DFF@99cloud.net> Hi All: I am working for merging starlingx patch to nova project. There is a fix patch[1] which I cannot understand what scene it fixes. In the patch description, it is a bug fix for patch[2], “0024 - primary: server-groups best effort and group size “, and the best-effort functionality is similar to server-group soft-affinty & soft-anti-affinty. Could anyone tell me their difference? As the 0111 patch says “However if a host is specified, there are some scenarios where the dest compute will be preset causing that host to be included in the list of server group hosts thereby preventing the current live migration from scheduling”, I review the code in stx-nova/nova/conductor/tasks/live-migration.py[3], but I still don’t understand what the "some scenarios” are. [1] https://github.com/starlingx-staging/stx-nova/blob/master/stx-patches/0111-Exclude-current-instance-when-checking-ser.patch [2] https://github.com/starlingx-staging/stx-nova/blob/master/stx-patches/0024-primary-server-groups-best-effort-and-group-size.patch [3] https://github.com/starlingx-staging/stx-nova/blob/master/nova/conductor/tasks/live_migrate.py Best Regards Kunpeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Feb 20 14:31:33 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 20 Feb 2019 14:31:33 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 2/20 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E91395@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 2/20 meeting: 1. CentOS 7.6 upgrade test status (Ada/Numan) 2 bugs found during 1st round validation: https://bugs.launchpad.net/starlingx/+bug/1814360 https://bugs.launchpad.net/starlingx/+bug/1814335 both have patch merged to f/CentOS7.6 2nd round validation report from GDC received, no new issue reported from Ricardo. found several issues, few test cases pending to run. Most related to security (https, low latency, secure boot) remaining. Still waiting for the builds to pick up the patch (https://review.openstack.org/#/c/634559/) . AR for Numan to contact Ken to get correct builds. So will be 2-3 days validation effort remaining. We will not have f/CentOS7.6 merged to master before container. 2. Ceph upgrade status (Frank, Changcheng) Changcheng finished moving Ceph spec wrs file into stx-integ repo. Will squash small patches into bigger ones. Ovidiu: Daniel working on ceph-pythonclient lib, will integrate into sys-inv code. Prototyping done. Workspace to define the collabration btw WR and Intel will be send out by Ovidiu so that both teams can build the same code using same manifest. Proposal of the test plan for joint plan w/ a list of milestones. 3. DevStack status update (Yi/Dean) Dean: switch to Openstack & Devstack master in 2 wks. taking time for the changes in all repos. get the plug-ins infra working again, then get the services run again. Problems for the dependencies for the services are in circular. and we have to enable certain services in order. Get the dependencies sorted out. List the order of the things - please send the list to Yi/Martin. focus on get the platform working with the master Openstack/Devstack right now. AR: Yi to provide a start-point of service dependencies and work with Dean to define the right order to enable the flock plug-in. Yi: 10+ services to be enabled in 5 repos. 11 tasks created in 5 storyboards.1 patch submitted to bring up 2 services in stx-nfv project. Need to switch to Stein now. consumer could be in testing side, for example REST_API testing can be moved from post build; also for developers to test the services as well. 4. Opens (all) NA -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; 'Rowsell, Brent'; starlingx-discuss at lists.starlingx.io; Waheed, Numan; Wold, Saul; 'Khalil, Ghada'; Hu, Yong; Liu, ZhipengS; Zhu, Vivian; Sun, Austin; Lin, Shuicheng; Troyer, Dean; Somerville, Jim; Shang, Dehao; Jones, Bruce E Cc: Gomez, Juan P; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; 'Young, Ken'; 'Eslimi, Dariush'; Martinez Monroy, Elio; Arce Moreno, Abraham; 'Seiler, Glenn'; Hu, Wei W; Martinez Landa, Hayde; Perez Rodriguez, Humberto I; Perez Carranza, Jose; Cobbley, David A; 'Hellmann, Gil'; 'Poncea, Ovidiu'; Fang, Liang A Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 20, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From ildiko.vancsa at gmail.com Wed Feb 20 14:33:51 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 20 Feb 2019 15:33:51 +0100 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit In-Reply-To: <2739FAC9-F55E-4742-9D1A-8D2896D4A727@windriver.com> References: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> <2739FAC9-F55E-4742-9D1A-8D2896D4A727@windriver.com> Message-ID: Sounds good, thanks Brent! I think we can have up to two speakers for this slot if there would be others interested as well. Best Regards, Ildikó > On 2019. Feb 19., at 22:34, Rowsell, Brent wrote: > > Hi, > > I volunteer for the project update session > > Brent > > Sent from my iPhone > >> On Feb 19, 2019, at 2:50 PM, Ildiko Vancsa wrote: >> >> Hi, >> >> I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. >> >> This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. >> >> The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. >> >> The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. >> >> I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ >> >> Is there a need to request an extended slot for the project update? >> >> Please let me know if you have any questions. >> >> Thanks, >> Ildikó >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From david.a.cobbley at intel.com Wed Feb 20 14:52:38 2019 From: david.a.cobbley at intel.com (Cobbley, David A) Date: Wed, 20 Feb 2019 14:52:38 +0000 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit In-Reply-To: References: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> <2739FAC9-F55E-4742-9D1A-8D2896D4A727@windriver.com> Message-ID: <996EA3E5-A376-4D68-88D8-0F7DCE557159@intel.com> I think that Bruce may be interested in doing this as well, though he is currently out on vacation. -- David C From: Ildiko Vancsa Date: Wednesday, February 20, 2019 at 6:34 AM To: "Rowsell, Brent" Cc: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit Sounds good, thanks Brent! I think we can have up to two speakers for this slot if there would be others interested as well. Best Regards, Ildikó On 2019. Feb 19., at 22:34, Rowsell, Brent > wrote: Hi, I volunteer for the project update session Brent Sent from my iPhone On Feb 19, 2019, at 2:50 PM, Ildiko Vancsa > wrote: Hi, I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ Is there a need to request an extended slot for the project update? Please let me know if you have any questions. Thanks, Ildikó _______________________________________________ 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 ildiko.vancsa at gmail.com Wed Feb 20 14:55:45 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 20 Feb 2019 15:55:45 +0100 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit In-Reply-To: <996EA3E5-A376-4D68-88D8-0F7DCE557159@intel.com> References: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> <2739FAC9-F55E-4742-9D1A-8D2896D4A727@windriver.com> <996EA3E5-A376-4D68-88D8-0F7DCE557159@intel.com> Message-ID: <3312025A-B645-47BA-AEE1-08086FFAE107@gmail.com> Sounds good, thanks David. I will check with him and get him added once he confirmed. Would anyone be interested in running the Project Onboarding session? Thanks, Ildikó > On 2019. Feb 20., at 15:52, Cobbley, David A wrote: > > I think that Bruce may be interested in doing this as well, though he is currently out on vacation. > > -- David C > > > From: Ildiko Vancsa > Date: Wednesday, February 20, 2019 at 6:34 AM > To: "Rowsell, Brent" > Cc: "starlingx-discuss at lists.starlingx.io" > Subject: Re: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit > > Sounds good, thanks Brent! > > I think we can have up to two speakers for this slot if there would be others interested as well. > > Best Regards, > Ildikó > > >> On 2019. Feb 19., at 22:34, Rowsell, Brent wrote: >> Hi, >> I volunteer for the project update session >> Brent >> Sent from my iPhone >>> On Feb 19, 2019, at 2:50 PM, Ildiko Vancsa wrote: >>> Hi, >>> I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. >>> This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. >>> The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. >>> The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. >>> I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ >>> Is there a need to request an extended slot for the project update? >>> Please let me know if you have any questions. >>> Thanks, >>> Ildikó >>> _______________________________________________ >>> 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 ildiko.vancsa at gmail.com Wed Feb 20 16:03:14 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 20 Feb 2019 17:03:14 +0100 Subject: [Starlingx-discuss] Community Marketing planning call is on Message-ID: <7C784C89-33C7-4BDC-BA31-E7D866148849@gmail.com> Hi, Our bi-weekly community marketing meeting is on. Further details on the wiki: https://wiki.openstack.org/wiki/Starlingx/Meetings#8am_PDT_.2F_1600_UTC_-_Community_Marketing_Planning_Call Thanks, Ildikó From ildiko.vancsa at gmail.com Wed Feb 20 17:03:21 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 20 Feb 2019 18:03:21 +0100 Subject: [Starlingx-discuss] Open Infrastructure Summit Denver Schedule is now live! Message-ID: <37A4911A-B611-443B-A7BC-BDD1EC241619@gmail.com> Hi StarlingX community, I’m excited to share with you that the agenda is now live for the Open Infrastructure Summit with a dedicated track to edge computing and quite a few StarlingX talks - congratulations to all of the speakers! You can see the full agenda here: https://www.openstack.org/summit/denver-2019/summit-schedule#day=2019-04-29 StarlingX sessions include: • Precision Time Protocol (PTP) on StarlingX (Matt Peters, Alexander Kozyrev) • Getting a new Open Source Project off the ground – the StarlingX story (Ian Jolliffe, Bruce Jones) • Edge Computing Group’s MVP Architecture - StarlingX making it real! (Greg Waines, James Penick) • 5G-based intelligent manufacturing edge solution (Hong Kan, Jianqing Jiang) • StarlingX: Hardened Managed Kubernetes Platform for the Edge (Brent Rowsell, Bart Wensley, Greg Waines) I would also like to remind you that the prices to register for the Summit increase on February 27. If you haven’t done it yet, you can register here: https://openinfrasummitandptgdenver.eventbrite.com Please also keep in mind the preparation for the Forum and PTG. You can add your ideas to the following etherpads: • https://etherpad.openstack.org/p/stx-forum-preparation-denver-2019 • https://etherpad.openstack.org/p/stx-ptg-preparation-denver-2019 The Forum session proposal period starts on February 22. Thanks, Ildikó From Bill.Zvonar at windriver.com Wed Feb 20 17:50:06 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Feb 2019 17:50:06 +0000 Subject: [Starlingx-discuss] Contributor Survey Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A0749D@ALA-MBD.corp.ad.wrs.com> Hi Ildiko, As discussed in the Community Marketing Planning call today, I've placed a draft of a Contributor Survey up on [0]. It's not quite the same as the survey you started, it's more directed at individuals who have already expressed an interest in contributing - a survey like this will help them understand how & where they can do so. It's a draft - comments welcome from the community. Bill... [0] https://etherpad.openstack.org/p/stx-user-survey -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Feb 20 18:19:12 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 20 Feb 2019 18:19:12 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190220 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C6AE@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-20 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcelx.schaible at intel.com Wed Feb 20 19:01:07 2019 From: marcelx.schaible at intel.com (Schaible, MarcelX) Date: Wed, 20 Feb 2019 19:01:07 +0000 Subject: [Starlingx-discuss] Duplex Config: Controller-0 stays in degraded state Message-ID: Hi *, we are using the 20190109T162801Z iso image on bare metal. The controller-0 stays in degraded state and we are running out of ideas what the root cause of this problem could be. [root at controller-0 etc(keystone_admin)]# system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | degraded | +----+--------------+-------------+----------------+-------------+--------------+ The output of python /usr/share/openvswitch/scripts/dpdk-devbind.py -status: Network devices using DPDK-compatible driver ============================================ 0000:09:15.1 '82599 Ethernet Controller Virtual Function 10ed' drv=vfio-pci unused= Network devices using kernel driver =================================== 0000:03:00.0 'Ethernet Connection X552 10 GbE Backplane 15ab' if=enp3s0f0 drv=ixgbe unused=vfio-pci 0000:03:00.1 'Ethernet Connection X552 10 GbE Backplane 15ab' if=enp3s0f1 drv=ixgbe unused=vfio-pci 0000:07:00.0 'I350 Gigabit Network Connection 1521' if=ens1f0 drv=igb unused=vfio-pci 0000:07:00.1 'I350 Gigabit Network Connection 1521' if=ens1f1 drv=igb unused=vfio-pci 0000:07:00.3 'I350 Gigabit Network Connection 1521' if=ens1f3 drv=igb unused=vfio-pci 0000:09:14.6 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s20f6 drv=ixgbevf unused=vfio-pci 0000:09:14.7 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s20f7 drv=ixgbevf unused=vfio-pci *Active* 0000:09:15.0 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s21f0 drv=ixgbevf unused=vfio-pci Other Network devices ===================== 0000:07:00.2 'I350 Gigabit Network Connection 1521' unused=vfio-pci 0000:26:00.0 'Device 9797' unused=vfio-pci Crypto devices using DPDK-compatible driver =========================================== Crypto devices using kernel driver ================================== Other Crypto devices ==================== Eventdev devices using DPDK-compatible driver ============================================= Eventdev devices using kernel driver ==================================== Other Eventdev devices ====================== Mempool devices using DPDK-compatible driver ============================================ Mempool devices using kernel driver =================================== Other Mempool devices ===================== And ovs-vsctl show gives: 5047dd61-faa2-448c-be2c-f4ef2f5c9501 Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} Port br-int Interface br-int type: internal Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:09:15.1", n_rxq="2"} error: "Error attaching device '0000:09:15.1' to DPDK" Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "br-phy0" Interface "br-phy0" type: internal Port "lldp55d31ed0-33" Interface "lldp55d31ed0-33" type: internal ovs_version: "2.9.0" Can anyone recommend an iso image for duplex on bare metal? Thanks Marcel Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Feb 20 19:25:57 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 20 Feb 2019 20:25:57 +0100 Subject: [Starlingx-discuss] Contributor Survey In-Reply-To: <586E8B730EA0DA4A9D6A80A10E486BC0A0749D@ALA-MBD.corp.ad.wrs.com> References: <586E8B730EA0DA4A9D6A80A10E486BC0A0749D@ALA-MBD.corp.ad.wrs.com> Message-ID: <834BB696-A390-4E15-9874-52141B49335F@gmail.com> Hi Bill, Thank you for adding the contributor focused questions. On the today’s call we’ve discussed the base idea being to have a high level user survey type of questionnaire that focuses on understanding the use case and motivation for companies who are planning to deploy or use an edge platform and ask their plans and current stage with StarlingX. Our motivation is to start building and growing the ecosystem around StarlingX and understand the market a little better as well. When it comes to contributions we listed two options. We can either add a question or two to the above initial survey to see if a certain responder is also interested in contributing or we can run it as a separate survey. If we can make it happen on the tooling side we could also consider showing deeper dive questions if someone says they are interested in contributing and not displaying those questions if that’s not a primary interest for them at this point. In my view if we run a contribution focused survey we need to set the scope and decide what challenges we would like to get an answer to when we put together the questions. Like whether we would like to find roadblocks or bottlenecks that make it harder for people to join or learn which area they are interested in and if the latter what the next step is once we have the results and whether the survey is the best way to reach out to new contributors who are just getting started to help them. What do others think or would be interested in learning about? If you would like to participate in drafting the survey(s) please check out the etherpad and add comments and ideas! Thanks, Ildikó > On 2019. Feb 20., at 18:50, Zvonar, Bill wrote: > > Hi Ildiko, > > As discussed in the Community Marketing Planning call today, I’ve placed a draft of a Contributor Survey up on [0]. > > It’s not quite the same as the survey you started, it’s more directed at individuals who have already expressed an interest in contributing – a survey like this will help them understand how & where they can do so. > > It’s a draft – comments welcome from the community. > > Bill… > > [0] https://etherpad.openstack.org/p/stx-user-survey > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Joseph.Richard at windriver.com Wed Feb 20 19:28:17 2019 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Wed, 20 Feb 2019 19:28:17 +0000 Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent In-Reply-To: References: <7B6A2AE64F40F245AE81F245059F0C366BE43190@ALA-MBD.corp.ad.wrs.com> Message-ID: <7B6A2AE64F40F245AE81F245059F0C366BE4351D@ALA-MBD.corp.ad.wrs.com> Which build is this? Has you reproduced this failure? Do you see any errors in your puppet logs on controller-0 from when you unlocked it? From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, February 20, 2019 2:36 AM To: Richard, Joseph; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi Joseph: Thanks. The result of ovs-vsctl show is below: I have pasted the yaml files with below link. /opt/platform/helm/19.01/openstack-neutron.yaml http://paste.openstack.org/show/745435/ /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml http://paste.openstack.org/show/745436/ /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml http://paste.openstack.org/show/745437/ 168464a5-d278-47b8-a3b0-01f86cfec2bb Manager "ptcp:6640:127.0.0.1" Bridge "br-phy1" Port "lldp160b8b4f-a3" Interface "lldp160b8b4f-a3" type: internal Port "eth1" Interface "eth1" type: dpdk options: {dpdk-devargs="0000:02:04.0", n_rxq="2"} Port "br-phy1" Interface "br-phy1" type: internal Bridge "br-phy0" Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:03.0", n_rxq="2"} Port "br-phy0" Interface "br-phy0" type: internal Port "lldp706c54b4-b5" Interface "lldp706c54b4-b5" type: internal ovs_version: "2.9.0" Thanks. BR Austin Sun. From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Wednesday, February 20, 2019 1:10 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Which build is this? Can you provide the contents of these files on your lab? /opt/platform/helm/19.01/openstack-neutron.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml Also, please provide the output of this command run on controller-0: ovs-vsctl show From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, February 19, 2019 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi All: I'm deploying duplex container mode with latest code . meet some error for neutron-ovs-agent Both controller have same configuration and deploy in virtual machine (qemu kvm env) . Does anyone have similar experience and suggest how to solve it ? *) The status of neutron-ovs-agent: neutron-ovs-agent-controller-0-a762cb46-h9xqw 0/1 Init:CrashLoopBackOff 11 42m neutron-ovs-agent-controller-1-f2c6aeed-427h8 1/1 Running 0 42m *) The log of neutron-ovs-agent-controller-0-a762cb46-h9xqw is : + timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so pleas e use SIGUSR2 to generate reports. 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] Logging enabled! 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 11.0.0 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch/impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfa ces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib [-] Timed out retrieving ofport on port 192.0.2.1.: RetryError: RetryError[] 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib Traceback (most recent call last): 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", lin e 321, in get_port_ofport 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib ofport = self._get_port_val(port_name, "ofport") 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 89, in wrapped 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return new_fn(*args, **kwargs) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 171, in wrapped_f 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return self.call(f, *args, **kw) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 248, in call 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib start_time=start_time) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 216, in iter 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise RetryError(fut).reraise() 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 298, in reraise 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise self 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib RetryError: RetryError[ From Numan.Waheed at windriver.com Wed Feb 20 21:21:32 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 20 Feb 2019 21:21:32 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer Message-ID: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> A Python-based installer for StarlingX has been submitted to stx-tools repo. This automated installer has been used by Wind River engineers on a continual basis for installing StarlingX on VBox environment. This installer is not a new development. This has been used for several years for quick install on VBox. It is being delivered to help community for ease of installation of starlingx. Feel free to use this installer and even add new features to serve the community better. The installer is going in via following submission: https://review.openstack.org/#/c/637958/ Numan. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Wed Feb 20 21:28:51 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 20 Feb 2019 15:28:51 -0600 Subject: [Starlingx-discuss] [TSC] Request TSC Members please review and comment on MultiOS Specs In-Reply-To: <77c29f01-10e8-3690-663c-dad3042f4861@linux.intel.com> References: <77c29f01-10e8-3690-663c-dad3042f4861@linux.intel.com> Message-ID: Hello Team As we highlight on today meeting the MultiOS specifications have been adjusted to do not modify master of current directories or request any changes in source reorg Since no changes in the master branch of current repositories are required, I would like to discuss this on tomorrow TSC meeting for approval Regards Victor R On Tue, Feb 12, 2019 at 11:26 PM Saul Wold wrote: > > > TSC Members, > > There have been some additional changes and updates to the MultiOS > related specifications [0], I would request that TSC members review > these specifications ahead of Thursday's TSC Meeting so we can have some > discussion on these in order to move them forward. > > Thanks for your contributions > > Sau! > > > > [0] https://review.openstack.org/#/q/topic:multi-os > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From michael.l.tullis at intel.com Wed Feb 20 21:36:56 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 20 Feb 2019 21:36:56 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2/20/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1AB8ECC@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Wed Feb 20 22:08:27 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 20 Feb 2019 22:08:27 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190220 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9C784@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-20 (link) Sanity Test is executed in a Containers - Bare Metal Environment Status: No execution on Bare Metal today due to infrastructure relocation. Simplex Setup Manual [] Provisioning Manual [] Sanity OpenStack 35 TCs [] Sanity Platform In Development TOTAL: [ ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 35 TCs [PASS] Sanity Platform In Development TOTAL: [ 35 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Wed Feb 20 22:11:05 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Wed, 20 Feb 2019 22:11:05 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX OpenStack Distro Meeting, 2/19/19 Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A077EE@ALA-MBD.corp.ad.wrs.com> Notes from Distro OpenStack meeting 2/19/2019... We went through all of the items in the list and downgraded many to "At Risk" for the coming release. These are primarily in Nova, and will not make it into this release unless some new action is taken on behalf of the StarlingX community to influence them in upstream. I will raise this overall risk to the TSC agenda tomorrow. Details below and in colour at [0]. Bill... [0] Distro OpenStack Tracker: https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Summary - At Risk: 11 items - No Plan: 13 items - Likely: 12 items - Certain: 4 items Nova Features (9 at risk, 1 no plan) Live Migration Patch w/ Pinning (numa_topology): At Risk - Nova (Artem?) - need to check where we're at with this - at least we're seeing some progress on this - monitor to see if it's going to land soon Shared/Dedicated vcpus on the same host or standardize CPU resource tracking: At Risk - Nova (Jay Pipes) - this hasn't been active for ~9 weeks - so it's At Risk for sure Shared VCPU Extension: At Risk - Nova (TBD) - same as previous one vCPU model: No Plan - Intel, unassigned - no chance of this being done for this release now Clean Up Orphan Instances: At Risk - Yongli - he says this is lower priority - has time (but isn't working on it right now) - lowering status to At Risk - likely to suffer same lack of attention in community Server Group Show Enhancement: At Risk - Yongli - code has been posted, is actively working on it - not this week, but maybe next week (no Core reviewer yet) - Frank asked Yongli how he thinks we can get Core attention on this - can we get Alex Xu to +2 this? - Yongli will talk to him Numa Topology API: At Risk - Yongli - this is in the same boat as the previous one - Yongli will talk to Alex Xu about this too Add support for emulated virtual TPM: At Risk - Chris Friesen, Certain - this will be taken over by Chris F, will try to get it in - downgraded this to At Risk Disk Performance Fixes: At Risk - Jack Ding - suffering from lack of reviews by Cores - Frank will meet with Chris to see if he can help - get him to +1 it & say who would be the right Core to chase Extra Spec Validation: At Risk - Jack Ding - same comment as previous feature Nova Refactor (1 Likely) PCI Interrupt Affinity: Likely - Yong Hu - planning to have code posted for review by end of next week (March 1st) Nova Config (1 Likely) RPC Timeout Handling: Likely - Frank - planning to assign this after the container cutover (target is March 31st) Nova Features - Test Only (need plan from test team) Replace SR-IOV/PT best effort scheduling policy with Queens feature Replace vswitch affinity with Rocky feature DB purge - need Ada to provide plan for completing these test activities Nova Bug Fixes (10 No Plan, unstaffed) rbd disks: convert from source format to raw Intel to fix upstram Migrate code to use request_spec for server groups Specify migration type in db filter for anti-affinity migration Do not bypass scheduler when using forced hosts Exclude current instance when checking server group live migrations Live block migration fails following auth token expiration Drop support for forced hosts for live migrate Unsquash: primary: server-groups best-effort and group size Unsquash: primary: live migration driver fixes Unsquash: Fix stale RequestSpec instance numa topology for live-migration - currently these 10 bug fixes are unstaffed, will not make it into the release Neutron Features (5 Likely - but need updates) Network Segment Range Management (top Neutron priority) - Kailun, likely - need update Populate binding levels when concurrent ops fail (da31d0e) - Kailun, likely - need update DHCP agent rescheduling / rebalancing - Kevin Smith, likely - need update L3 agent rescheduling / rebalancing - Kevin Smith, likely - need udpate Modeling the provider networks in sysinv - John Kung, likely - need udpate Neutron Bug Fixes (2 At Risk, 2 Likely, 1 Certain) - need updates Prevent DHCP from processing stale RPC messages (fd6cfc) - Kailun, Certain - need update 0039-dhcp-handle-concurrent-port-creation-error.patch (a38f89) - Kailun, At Risk - need update 0047-wsgi-prevent-accepting-socket-without-a-gr.patch (8e72491) - Le Huifeng, At Risk - need update 0062-dvr-force-admin-state-update-before-distri.patch (edf9731) - Matt Welch, Likely - need update 0065-dvr-do-not-create-agent-gateway-ports-unle.patch (2857911) - Enyinna, Likely - need update Horizon Features (2 Likely, 2 No Plan) CSRF AngularJS Fixes: Likely - Yan Chen - Yong to check, he thinks it may have been merged already Custom Confirmation Messages: Not Required - Yan Chen - under discussion now, may decide we don't need this - post-meeting, got update that this has been confirmed Configurable Auto Page Refresh: No Plan - Intel - currently no plan, unstaffed Auth Plugin Extensions: No Plan - WR - currently no plan, unstaffed - Bill to check with Dariush on this Move Items to stx-gui: Likely - Kristine Bujold - in progress, some work to be done after Stein cutover (re: port forwarding) - it'll be done by mid-March, it's not upstreaming, so no risk Glance/Cinder Refactor (1 Likely) Refactor StarlingX to make use of Cinder caching to replace glance-cache raw implementation. - Liang Fang, Likely - need to get an update from Liang on forecast - may have to reforecast based on not using Puppet; Liang may need help with that -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Wed Feb 20 06:13:35 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Wed, 20 Feb 2019 15:13:35 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: References: <201902191456126968489@baicells.com> <2019021915163953671221@baicells.com> Message-ID: Hello StarlingX Team and Tim, I'm still struggling to deploy StarlingX normally, but it seems it will never succeed. I used the latest boot image, Feb 18th. However the symptom is same. And I found that there were no horizon directory in /etc/. [image: image.png] Do I need to install horizon manually? BR, Jaewook. 2019년 2월 19일 (화) 오후 8:52, Jaewook Oh 님이 작성: > Unfortunately, still I cannot access dashboard. > > I'll try another latest boot image. > > Thank you for all helps :) > > BR. > Jaewook. > > 2019년 2월 19일 (화) 오후 4:16, xiongzhiwei at baicells.com < > xiongzhiwei at baicells.com>님이 작성: > >> Hi Jaewook, >> >> My ip setting is as below: >> Actually, I had used three physical interface, enp2s0f0 is OAM inf with >> default ip 10.10.10.2/24, because it is not inconvenient in my >> operation room, so I had configured enp2s0f1 for my romote access. >> I can access the dashboard both with ip 10.10.10.2 in lab and >> 192.168.107.232/22 in my operation room. >> The third inf enp2s0f2 is used to data interface, I had created three VMs >> and network worked normally. >> >> >> controller-0:~$ ip a >> 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group >> default qlen 1000 >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> inet 127.0.0.1/8 scope host lo >> valid_lft forever preferred_lft forever >> inet 192.168.204.3/28 brd 192.168.204.15 scope host lo >> valid_lft forever preferred_lft forever >> inet 169.254.202.2/24 scope host lo >> valid_lft forever preferred_lft forever >> inet 192.168.204.2/28 scope host secondary lo >> valid_lft forever preferred_lft forever >> inet 192.168.204.5/28 scope host secondary lo >> valid_lft forever preferred_lft forever >> inet 192.168.204.10/28 scope host secondary lo >> valid_lft forever preferred_lft forever >> inet 192.168.204.6/28 scope host secondary lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group >> default qlen 1000 >> link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff >> 3: enp2s0f0: mtu 1500 qdisc mq state >> UP group default qlen 1000 >> link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff >> inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 >> valid_lft forever preferred_lft forever >> inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link >> valid_lft forever preferred_lft forever >> 4: enp2s0f1: mtu 1500 qdisc mq state >> UP group default qlen 1000 >> link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff >> inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 >> valid_lft forever preferred_lft forever >> inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link >> valid_lft forever preferred_lft forever >> 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group >> default qlen 1000 >> link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff >> 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group >> default qlen 1000 >> link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff >> 8: br-int: mtu 1500 qdisc noop state DOWN group >> default qlen 1000 >> link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff >> 12: br-phy0: mtu 1500 qdisc pfifo_fast >> state UNKNOWN group default qlen 1000 >> link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff >> inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link >> valid_lft forever preferred_lft forever >> 13: lldp0d64ae5d-22: mtu 1500 qdisc >> pfifo_fast state UNKNOWN group default qlen 1000 >> link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff >> inet6 fe80::94e0:3ff:fe51:176d/64 scope link >> valid_lft forever preferred_lft forever >> >> >> BR >> Tim Xiong >> >> >> *From:* Jaewook Oh >> *Date:* 2019-02-19 15:00 >> *To:* xiongzhiwei at baicells.com >> *CC:* starlingx-discuss ; 오재욱 >> >> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >> All-in-one simplex configuration >> Hello Tim, >> >> thanks for your answer :) >> >> However, still I cannot access to the dashboard. >> >> I deployed StarlingX 3 times again, but the situation never changes.. >> >> If you don't mind, can I see your ip setting with (ip a command)? >> >> Best Regards, >> Jaewook. >> >> 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com < >> xiongzhiwei at baicells.com>님이 작성: >> >>> Hi Jaewook, >>> >>> I just finished stx all-in-one simplex on Bearmetal last week. The >>> horizon service had been installed defaultly and you should be able to >>> access the dashboard now. >>> Your service list is same as mine. >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >>> +----------------------------------+------------+-----------------+ >>> | ID | Name | Type | >>> +----------------------------------+------------+-----------------+ >>> | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | >>> | df07161f527b483292ac5aa5ed722687 | keystone | identity | >>> | 744183df128d414f97390fb70fcac72f | sysinv | platform | >>> | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | >>> | 5d7855696b1f440b8401670e1df6cb28 | glance | image | >>> | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | >>> | 68362243cc214c4181a15e583894e495 | placement | placement | >>> | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | >>> | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | >>> | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | >>> | cbf811729020470a81b3c7be0d453fc9 | neutron | network | >>> | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | >>> | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | >>> | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | >>> | bc5297541def4f8b8881254af9896824 | smapi | smapi | >>> | a388667479484a04824f07a672a331eb | panko | event | >>> | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | >>> | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | >>> | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | >>> | 253390980b274178b7a16844e2c7a826 | cinder | volume | >>> +----------------------------------+------------+-----------------+ >>> >>> BR >>> Tim Xiong >>> >>> *From:* Jaewook Oh >>> *Date:* 2019-02-19 12:48 >>> *To:* starlingx-discuss ; 오재욱 >>> >>> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >>> All-in-one simplex configuration >>> Hello StarlingX Teams, >>> >>> I found that *the horizon dashboard project were not installed >>> automatically* when I deployed StarlingX all-in-one simplex on >>> Baremetal. >>> Are there any reason for this problem..? >>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>> >>> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >>> +----------------------------------+------------+-----------------+ >>> | ID | Name | Type | >>> +----------------------------------+------------+-----------------+ >>> | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | >>> | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | >>> | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | >>> | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | >>> | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | >>> | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | >>> | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | >>> | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | >>> | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | >>> | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | >>> | ecf3478c84334c2ba647740bde190739 | neutron | network | >>> | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | >>> | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | >>> | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | >>> | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | >>> | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | >>> | 57a5cb58128445b5819747271c095a89 | heat | orchestration | >>> | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | >>> | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | >>> | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | >>> +----------------------------------+------------+-----------------+ >>> >>> I thought horizon should also be installed with StarlingX's deployment. >>> If not, please let me know how can I install horizon in this StarlingX. >>> >>> Thanks for help in advance :) >>> >>> Best Regards, >>> Jaewook. >>> >>> >>> 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: >>> >>>> Hello starlingx team, >>>> >>>> I deployed Starlingx All-in-one simplex setting on my server, >>>> it seems deployment was done well. >>>> *However I cannot access to the dashboard.* >>>> >>>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>>> >>>> >>>> Following log is the service that are now enabled, >>>> [wrsroot at controller-0 ~(keystone_admin)]$ system service-list >>>> +-----+-------------------------------+--------------+----------------+ >>>> | id | service_name | hostname | state | >>>> +-----+-------------------------------+--------------+----------------+ >>>> | 68 | aodh-api | controller-0 | enabled-active | >>>> | 69 | aodh-evaluator | controller-0 | enabled-active | >>>> | 70 | aodh-listener | controller-0 | enabled-active | >>>> | 71 | aodh-notifier | controller-0 | enabled-active | >>>> | 102 | barbican-api | controller-0 | enabled-active | >>>> | 103 | barbican-keystone-listener | controller-0 | enabled-active | >>>> | 104 | barbican-worker | controller-0 | enabled-active | >>>> | 43 | ceilometer-agent-notification | controller-0 | enabled-active | >>>> | 14 | cgcs-export-fs | controller-0 | enabled-active | >>>> | 10 | cgcs-fs | controller-0 | enabled-active | >>>> | 16 | cgcs-nfs-ip | controller-0 | enabled-active | >>>> | 35 | cinder-api | controller-0 | enabled-active | >>>> | 38 | cinder-backup | controller-0 | enabled-active | >>>> | 58 | cinder-ip | controller-0 | enabled-active | >>>> | 56 | cinder-lvm | controller-0 | enabled-active | >>>> | 36 | cinder-scheduler | controller-0 | enabled-active | >>>> | 37 | cinder-volume | controller-0 | enabled-active | >>>> | 23 | dnsmasq | controller-0 | enabled-active | >>>> | 5 | drbd-cgcs | controller-0 | enabled-active | >>>> | 55 | drbd-cinder | controller-0 | enabled-active | >>>> | 75 | drbd-extension | controller-0 | enabled-active | >>>> | 3 | drbd-pg | controller-0 | enabled-active | >>>> | 6 | drbd-platform | controller-0 | enabled-active | >>>> | 4 | drbd-rabbit | controller-0 | enabled-active | >>>> | 77 | extension-export-fs | controller-0 | enabled-active | >>>> | 76 | extension-fs | controller-0 | enabled-active | >>>> | 24 | fm-mgr | controller-0 | enabled-active | >>>> | 27 | glance-api | controller-0 | enabled-active | >>>> | 26 | glance-registry | controller-0 | enabled-active | >>>> | 108 | gnocchi-api | controller-0 | enabled-active | >>>> | 109 | gnocchi-metricd | controller-0 | enabled-active | >>>> | 62 | guest-agent | controller-0 | enabled-active | >>>> | 64 | haproxy | controller-0 | enabled-active | >>>> | 45 | heat-api | controller-0 | enabled-active | >>>> | 46 | heat-api-cfn | controller-0 | enabled-active | >>>> | 47 | heat-api-cloudwatch | controller-0 | enabled-active | >>>> | 44 | heat-engine | controller-0 | enabled-active | >>>> | 51 | horizon | controller-0 | enabled-active | >>>> | 22 | hw-mon | controller-0 | enabled-active | >>>> | 57 | iscsi | controller-0 | enabled-active | >>>> | 25 | keystone | controller-0 | enabled-active | >>>> | 50 | lighttpd | controller-0 | enabled-active | >>>> | 2 | management-ip | controller-0 | enabled-active | >>>> | 20 | mtc-agent | controller-0 | enabled-active | >>>> | 28 | neutron-server | controller-0 | enabled-active | >>>> | 9 | nfs-mgmt | controller-0 | enabled-active | >>>> | 29 | nova-api | controller-0 | enabled-active | >>>> | 63 | nova-api-proxy | controller-0 | enabled-active | >>>> | 31 | nova-conductor | controller-0 | enabled-active | >>>> | 33 | nova-console-auth | controller-0 | enabled-active | >>>> | 34 | nova-novnc | controller-0 | enabled-active | >>>> | 83 | nova-placement-api | controller-0 | enabled-active | >>>> | 30 | nova-scheduler | controller-0 | enabled-active | >>>> | 48 | open-ldap | controller-0 | enabled-active | >>>> | 82 | panko-api | controller-0 | enabled-active | >>>> | 52 | patch-alarm-manager | controller-0 | enabled-active | >>>> | 7 | pg-fs | controller-0 | enabled-active | >>>> | 15 | platform-export-fs | controller-0 | enabled-active | >>>> | 11 | platform-fs | controller-0 | enabled-active | >>>> | 17 | platform-nfs-ip | controller-0 | enabled-active | >>>> | 12 | postgres | controller-0 | enabled-active | >>>> | 65 | pxeboot-ip | controller-0 | enabled-active | >>>> | 13 | rabbit | controller-0 | enabled-active | >>>> | 8 | rabbit-fs | controller-0 | enabled-active | >>>> | 49 | snmp | controller-0 | enabled-active | >>>> | 19 | sysinv-conductor | controller-0 | enabled-active | >>>> | 18 | sysinv-inv | controller-0 | enabled-active | >>>> | 59 | vim | controller-0 | enabled-active | >>>> | 60 | vim-api | controller-0 | enabled-active | >>>> | 61 | vim-webserver | controller-0 | enabled-active | >>>> +-----+-------------------------------+--------------+----------------+ >>>> >>>> As you can see, *I cannot find #1 service (oam-ip)*, and I think this >>>> is one of the main reasons. >>>> >>>> *And also I had a problem when I followed the installation instruction.* >>>> >>>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan >>>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a >>>> >>>> [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a >>>> >>>> >>>> Above instruction was not naturally worked, I mean the third command, >>>> 'host-if-modify' failed with the message "*DataNetwork providernet-a >>>> could not be found*." >>>> >>>> So I googled and I figured out I should command >>>> $ *system datanetwork-add providernet-a vlan* >>>> first. >>>> >>>> But I remember when my first deployment succeed, I didn't need to use >>>> that command at all. (The deployment was implemented on Jan.) >>>> >>>> Any help is appreciated, thank you for your help in advance. >>>> >>>> Best Regards, >>>> Jaewook. >>>> >>>> ================================================ >>>> *Jaewook Oh* (오재욱) >>>> IISTRC - Internet Infra System Technology Research Center >>>> 369 Sangdo-ro, Dongjak-gu, >>>> 06978, Seoul, Republic of Korea >>>> >>> >>> >>> -- >>> ================================================ >>> *Jaewook Oh* (오재욱) >>> IISTRC - Internet Infra System Technology Research Center >>> 369 Sangdo-ro, Dongjak-gu, >>> 06978, Seoul, Republic of Korea >>> >>> >> >> -- >> ================================================ >> *Jaewook Oh* (오재욱) >> IISTRC - Internet Infra System Technology Research Center >> 369 Sangdo-ro, Dongjak-gu, >> 06978, Seoul, Republic of Korea >> >> > > -- > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 21938 bytes Desc: not available URL: From xiongzhiwei at baicells.com Wed Feb 20 06:23:31 2019 From: xiongzhiwei at baicells.com (xiongzhiwei at baicells.com) Date: Wed, 20 Feb 2019 14:23:31 +0800 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration References: , , <201902191456126968489@baicells.com>, , <2019021915163953671221@baicells.com>, , Message-ID: <2019022014233126084427@baicells.com> Hi Jaewook, There is no horizon directory in /etc, openstack-dashboard was installed in /usr/share/. Can you ignore to access the installation directory and try to test with 'wget' command? Just like below: controller-0:~$ wget http://10.10.10.2/dashboard --2019-02-20 06:15:23-- http://10.10.10.2/dashboard Connecting to 10.10.10.2:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-02-20 06:15:23 ERROR 404: Not Found. controller-0:~$ wget http://10.10.10.2/ --2019-02-20 06:15:38-- http://10.10.10.2/ Connecting to 10.10.10.2:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://10.10.10.2/auth/login/?next=/ [following] --2019-02-20 06:15:38-- http://10.10.10.2/auth/login/?next=/ Connecting to 10.10.10.2:80... connected. HTTP request sent, awaiting response... 200 OK Length: 9309 (9.1K) [text/html] Saving to: ‘index.html’ 100%[==================================================================================================================================================================================================>] 9,309 --.-K/s in 0s 2019-02-20 06:15:38 (55.8 MB/s) - ‘index.html’ saved [9309/9309] controller-0:~$ wget http://192.168.107.232 --2019-02-20 06:16:31-- http://192.168.107.232/ Connecting to 192.168.107.232:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://192.168.107.232/auth/login/?next=/ [following] --2019-02-20 06:16:31-- http://192.168.107.232/auth/login/?next=/ Connecting to 192.168.107.232:80... connected. HTTP request sent, awaiting response... 200 OK Length: 9309 (9.1K) [text/html] Saving to: ‘index.html.1’ 100%[==================================================================================================================================================================================================>] 9,309 --.-K/s in 0s 2019-02-20 06:16:31 (137 MB/s) - ‘index.html.1’ saved [9309/9309] BR Tim Xiong From: Jaewook Oh Date: 2019-02-20 14:13 To: xiongzhiwei at baicells.com CC: starlingx-discuss; 오재욱 Subject: Re: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello StarlingX Team and Tim, I'm still struggling to deploy StarlingX normally, but it seems it will never succeed. I used the latest boot image, Feb 18th. However the symptom is same. And I found that there were no horizon directory in /etc/. Do I need to install horizon manually? BR, Jaewook. 2019년 2월 19일 (화) 오후 8:52, Jaewook Oh 님이 작성: Unfortunately, still I cannot access dashboard. I'll try another latest boot image. Thank you for all helps :) BR. Jaewook. 2019년 2월 19일 (화) 오후 4:16, xiongzhiwei at baicells.com 님이 작성: Hi Jaewook, My ip setting is as below: Actually, I had used three physical interface, enp2s0f0 is OAM inf with default ip 10.10.10.2/24, because it is not inconvenient in my operation room, so I had configured enp2s0f1 for my romote access. I can access the dashboard both with ip 10.10.10.2 in lab and 192.168.107.232/22 in my operation room. The third inf enp2s0f2 is used to data interface, I had created three VMs and network worked normally. controller-0:~$ ip a 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 192.168.204.3/28 brd 192.168.204.15 scope host lo valid_lft forever preferred_lft forever inet 169.254.202.2/24 scope host lo valid_lft forever preferred_lft forever inet 192.168.204.2/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.5/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.10/28 scope host secondary lo valid_lft forever preferred_lft forever inet 192.168.204.6/28 scope host secondary lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff 3: enp2s0f0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 valid_lft forever preferred_lft forever inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link valid_lft forever preferred_lft forever 4: enp2s0f1: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 valid_lft forever preferred_lft forever inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link valid_lft forever preferred_lft forever 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff 8: br-int: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff 12: br-phy0: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link valid_lft forever preferred_lft forever 13: lldp0d64ae5d-22: mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff inet6 fe80::94e0:3ff:fe51:176d/64 scope link valid_lft forever preferred_lft forever BR Tim Xiong From: Jaewook Oh Date: 2019-02-19 15:00 To: xiongzhiwei at baicells.com CC: starlingx-discuss; 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello Tim, thanks for your answer :) However, still I cannot access to the dashboard. I deployed StarlingX 3 times again, but the situation never changes.. If you don't mind, can I see your ip setting with (ip a command)? Best Regards, Jaewook. 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com 님이 작성: Hi Jaewook, I just finished stx all-in-one simplex on Bearmetal last week. The horizon service had been installed defaultly and you should be able to access the dashboard now. Your service list is same as mine. [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | | df07161f527b483292ac5aa5ed722687 | keystone | identity | | 744183df128d414f97390fb70fcac72f | sysinv | platform | | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | | 5d7855696b1f440b8401670e1df6cb28 | glance | image | | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | | 68362243cc214c4181a15e583894e495 | placement | placement | | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | | cbf811729020470a81b3c7be0d453fc9 | neutron | network | | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | | bc5297541def4f8b8881254af9896824 | smapi | smapi | | a388667479484a04824f07a672a331eb | panko | event | | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | | 253390980b274178b7a16844e2c7a826 | cinder | volume | +----------------------------------+------------+-----------------+ BR Tim Xiong From: Jaewook Oh Date: 2019-02-19 12:48 To: starlingx-discuss; 오재욱 Subject: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration Hello StarlingX Teams, I found that the horizon dashboard project were not installed automatically when I deployed StarlingX all-in-one simplex on Baremetal. Are there any reason for this problem..? I used "2019-Feb-08 03:40:29 bootimage.iso". [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list +----------------------------------+------------+-----------------+ | ID | Name | Type | +----------------------------------+------------+-----------------+ | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | | ecf3478c84334c2ba647740bde190739 | neutron | network | | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | | 57a5cb58128445b5819747271c095a89 | heat | orchestration | | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | +----------------------------------+------------+-----------------+ I thought horizon should also be installed with StarlingX's deployment. If not, please let me know how can I install horizon in this StarlingX. Thanks for help in advance :) Best Regards, Jaewook. 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: Hello starlingx team, I deployed Starlingx All-in-one simplex setting on my server, it seems deployment was done well. However I cannot access to the dashboard. I used "2019-Feb-08 03:40:29 bootimage.iso". Following log is the service that are now enabled, [wrsroot at controller-0 ~(keystone_admin)]$ system service-list +-----+-------------------------------+--------------+----------------+ | id | service_name | hostname | state | +-----+-------------------------------+--------------+----------------+ | 68 | aodh-api | controller-0 | enabled-active | | 69 | aodh-evaluator | controller-0 | enabled-active | | 70 | aodh-listener | controller-0 | enabled-active | | 71 | aodh-notifier | controller-0 | enabled-active | | 102 | barbican-api | controller-0 | enabled-active | | 103 | barbican-keystone-listener | controller-0 | enabled-active | | 104 | barbican-worker | controller-0 | enabled-active | | 43 | ceilometer-agent-notification | controller-0 | enabled-active | | 14 | cgcs-export-fs | controller-0 | enabled-active | | 10 | cgcs-fs | controller-0 | enabled-active | | 16 | cgcs-nfs-ip | controller-0 | enabled-active | | 35 | cinder-api | controller-0 | enabled-active | | 38 | cinder-backup | controller-0 | enabled-active | | 58 | cinder-ip | controller-0 | enabled-active | | 56 | cinder-lvm | controller-0 | enabled-active | | 36 | cinder-scheduler | controller-0 | enabled-active | | 37 | cinder-volume | controller-0 | enabled-active | | 23 | dnsmasq | controller-0 | enabled-active | | 5 | drbd-cgcs | controller-0 | enabled-active | | 55 | drbd-cinder | controller-0 | enabled-active | | 75 | drbd-extension | controller-0 | enabled-active | | 3 | drbd-pg | controller-0 | enabled-active | | 6 | drbd-platform | controller-0 | enabled-active | | 4 | drbd-rabbit | controller-0 | enabled-active | | 77 | extension-export-fs | controller-0 | enabled-active | | 76 | extension-fs | controller-0 | enabled-active | | 24 | fm-mgr | controller-0 | enabled-active | | 27 | glance-api | controller-0 | enabled-active | | 26 | glance-registry | controller-0 | enabled-active | | 108 | gnocchi-api | controller-0 | enabled-active | | 109 | gnocchi-metricd | controller-0 | enabled-active | | 62 | guest-agent | controller-0 | enabled-active | | 64 | haproxy | controller-0 | enabled-active | | 45 | heat-api | controller-0 | enabled-active | | 46 | heat-api-cfn | controller-0 | enabled-active | | 47 | heat-api-cloudwatch | controller-0 | enabled-active | | 44 | heat-engine | controller-0 | enabled-active | | 51 | horizon | controller-0 | enabled-active | | 22 | hw-mon | controller-0 | enabled-active | | 57 | iscsi | controller-0 | enabled-active | | 25 | keystone | controller-0 | enabled-active | | 50 | lighttpd | controller-0 | enabled-active | | 2 | management-ip | controller-0 | enabled-active | | 20 | mtc-agent | controller-0 | enabled-active | | 28 | neutron-server | controller-0 | enabled-active | | 9 | nfs-mgmt | controller-0 | enabled-active | | 29 | nova-api | controller-0 | enabled-active | | 63 | nova-api-proxy | controller-0 | enabled-active | | 31 | nova-conductor | controller-0 | enabled-active | | 33 | nova-console-auth | controller-0 | enabled-active | | 34 | nova-novnc | controller-0 | enabled-active | | 83 | nova-placement-api | controller-0 | enabled-active | | 30 | nova-scheduler | controller-0 | enabled-active | | 48 | open-ldap | controller-0 | enabled-active | | 82 | panko-api | controller-0 | enabled-active | | 52 | patch-alarm-manager | controller-0 | enabled-active | | 7 | pg-fs | controller-0 | enabled-active | | 15 | platform-export-fs | controller-0 | enabled-active | | 11 | platform-fs | controller-0 | enabled-active | | 17 | platform-nfs-ip | controller-0 | enabled-active | | 12 | postgres | controller-0 | enabled-active | | 65 | pxeboot-ip | controller-0 | enabled-active | | 13 | rabbit | controller-0 | enabled-active | | 8 | rabbit-fs | controller-0 | enabled-active | | 49 | snmp | controller-0 | enabled-active | | 19 | sysinv-conductor | controller-0 | enabled-active | | 18 | sysinv-inv | controller-0 | enabled-active | | 59 | vim | controller-0 | enabled-active | | 60 | vim-api | controller-0 | enabled-active | | 61 | vim-webserver | controller-0 | enabled-active | +-----+-------------------------------+--------------+----------------+ As you can see, I cannot find #1 service (oam-ip), and I think this is one of the main reasons. And also I had a problem when I followed the installation instruction. [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a Above instruction was not naturally worked, I mean the third command, 'host-if-modify' failed with the message "DataNetwork providernet-a could not be found." So I googled and I figured out I should command $ system datanetwork-add providernet-a vlan first. But I remember when my first deployment succeed, I didn't need to use that command at all. (The deployment was implemented on Jan.) Any help is appreciated, thank you for your help in advance. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image(02-20-14-18-25).png Type: image/png Size: 21938 bytes Desc: not available URL: From kyle.oh95 at gmail.com Wed Feb 20 06:33:51 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Wed, 20 Feb 2019 15:33:51 +0900 Subject: [Starlingx-discuss] [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: <2019022014233126084427@baicells.com> References: <201902191456126968489@baicells.com> <2019021915163953671221@baicells.com> <2019022014233126084427@baicells.com> Message-ID: Thank you Tim, I didn't know the dashboard is in the /usr/share TT... By the way, I tried as you showed, but it showed Connection Refused. So I had thought maybe firewall something like that can impact to this, I disabled iptables, ip6tables, and firewalld. However, the result was same... [image: image.png] And I'm not sure what below figure means, but attach anyway. Please it could be the key of the problem... [image: image.png] Best Regards, Jaewook. 2019년 2월 20일 (수) 오후 3:23, xiongzhiwei at baicells.com 님이 작성: > Hi Jaewook, > There is no horizon directory in /etc, openstack-dashboard was installed > in /usr/share/. > Can you ignore to access the installation directory and try to test with > 'wget' command? > Just like below: > > controller-0:~$ wget http://10.10.10.2/dashboard > --2019-02-20 06:15:23-- http://10.10.10.2/dashboard > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2019-02-20 06:15:23 ERROR 404: Not Found. > > controller-0:~$ wget http://10.10.10.2/ > --2019-02-20 06:15:38-- http://10.10.10.2/ > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://10.10.10.2/auth/login/?next=/ [following] > --2019-02-20 06:15:38-- http://10.10.10.2/auth/login/?next=/ > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 9309 (9.1K) [text/html] > Saving to: ‘index.html’ > > 100%[==================================================================================================================================================================================================>] > 9,309 --.-K/s in 0s > > 2019-02-20 06:15:38 (55.8 MB/s) - ‘index.html’ saved [9309/9309] > > controller-0:~$ wget http://192.168.107.232 > --2019-02-20 06:16:31-- http://192.168.107.232/ > Connecting to 192.168.107.232:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://192.168.107.232/auth/login/?next=/ [following] > --2019-02-20 06:16:31-- http://192.168.107.232/auth/login/?next=/ > Connecting to 192.168.107.232:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 9309 (9.1K) [text/html] > Saving to: ‘index.html.1’ > > 100%[==================================================================================================================================================================================================>] > 9,309 --.-K/s in 0s > > 2019-02-20 06:16:31 (137 MB/s) - ‘index.html.1’ saved [9309/9309] > > BR > Tim Xiong > > > *From:* Jaewook Oh > *Date:* 2019-02-20 14:13 > *To:* xiongzhiwei at baicells.com > *CC:* starlingx-discuss ; 오재욱 > > *Subject:* Re: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy > All-in-one simplex configuration > Hello StarlingX Team and Tim, > > I'm still struggling to deploy StarlingX normally, but it seems it will > never succeed. > I used the latest boot image, Feb 18th. > > However the symptom is same. > And I found that there were no horizon directory in /etc/. > [image: image.png] > > Do I need to install horizon manually? > > BR, > Jaewook. > > 2019년 2월 19일 (화) 오후 8:52, Jaewook Oh 님이 작성: > >> Unfortunately, still I cannot access dashboard. >> >> I'll try another latest boot image. >> >> Thank you for all helps :) >> >> BR. >> Jaewook. >> >> 2019년 2월 19일 (화) 오후 4:16, xiongzhiwei at baicells.com < >> xiongzhiwei at baicells.com>님이 작성: >> >>> Hi Jaewook, >>> >>> My ip setting is as below: >>> Actually, I had used three physical interface, enp2s0f0 is OAM inf with >>> default ip 10.10.10.2/24, because it is not inconvenient in my >>> operation room, so I had configured enp2s0f1 for my romote access. >>> I can access the dashboard both with ip 10.10.10.2 in lab and >>> 192.168.107.232/22 in my operation room. >>> The third inf enp2s0f2 is used to data interface, I had created three >>> VMs and network worked normally. >>> >>> >>> controller-0:~$ ip a >>> 1: lo: mtu 1500 qdisc noqueue state UNKNOWN group >>> default qlen 1000 >>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>> inet 127.0.0.1/8 scope host lo >>> valid_lft forever preferred_lft forever >>> inet 192.168.204.3/28 brd 192.168.204.15 scope host lo >>> valid_lft forever preferred_lft forever >>> inet 169.254.202.2/24 scope host lo >>> valid_lft forever preferred_lft forever >>> inet 192.168.204.2/28 scope host secondary lo >>> valid_lft forever preferred_lft forever >>> inet 192.168.204.5/28 scope host secondary lo >>> valid_lft forever preferred_lft forever >>> inet 192.168.204.10/28 scope host secondary lo >>> valid_lft forever preferred_lft forever >>> inet 192.168.204.6/28 scope host secondary lo >>> valid_lft forever preferred_lft forever >>> inet6 ::1/128 scope host >>> valid_lft forever preferred_lft forever >>> 2: enp4s0f0: mtu 1500 qdisc mq state DOWN group >>> default qlen 1000 >>> link/ether 00:1b:21:bc:ff:a8 brd ff:ff:ff:ff:ff:ff >>> 3: enp2s0f0: mtu 1500 qdisc mq state >>> UP group default qlen 1000 >>> link/ether f8:75:88:6e:8f:e2 brd ff:ff:ff:ff:ff:ff >>> inet 10.10.10.2/24 brd 10.10.10.255 scope global enp2s0f0 >>> valid_lft forever preferred_lft forever >>> inet6 fe80::fa75:88ff:fe6e:8fe2/64 scope link >>> valid_lft forever preferred_lft forever >>> 4: enp2s0f1: mtu 1500 qdisc mq state >>> UP group default qlen 1000 >>> link/ether f8:75:88:6e:8f:e3 brd ff:ff:ff:ff:ff:ff >>> inet 192.168.107.232/22 brd 192.168.107.255 scope global enp2s0f1 >>> valid_lft forever preferred_lft forever >>> inet6 fe80::fa75:88ff:fe6e:8fe3/64 scope link >>> valid_lft forever preferred_lft forever >>> 6: enp2s0f3: mtu 1500 qdisc mq state DOWN group >>> default qlen 1000 >>> link/ether f8:75:88:6e:8f:e5 brd ff:ff:ff:ff:ff:ff >>> 7: ovs-netdev: mtu 1500 qdisc noop state DOWN group >>> default qlen 1000 >>> link/ether 8e:da:6c:1b:fd:15 brd ff:ff:ff:ff:ff:ff >>> 8: br-int: mtu 1500 qdisc noop state DOWN group >>> default qlen 1000 >>> link/ether f6:df:04:bf:a1:43 brd ff:ff:ff:ff:ff:ff >>> 12: br-phy0: mtu 1500 qdisc pfifo_fast >>> state UNKNOWN group default qlen 1000 >>> link/ether f8:75:88:6e:8f:e4 brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::fa75:88ff:fe6e:8fe4/64 scope link >>> valid_lft forever preferred_lft forever >>> 13: lldp0d64ae5d-22: mtu 1500 qdisc >>> pfifo_fast state UNKNOWN group default qlen 1000 >>> link/ether 96:e0:03:51:17:6d brd ff:ff:ff:ff:ff:ff >>> inet6 fe80::94e0:3ff:fe51:176d/64 scope link >>> valid_lft forever preferred_lft forever >>> >>> >>> BR >>> Tim Xiong >>> >>> >>> *From:* Jaewook Oh >>> *Date:* 2019-02-19 15:00 >>> *To:* xiongzhiwei at baicells.com >>> *CC:* starlingx-discuss ; 오재욱 >>> >>> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >>> All-in-one simplex configuration >>> Hello Tim, >>> >>> thanks for your answer :) >>> >>> However, still I cannot access to the dashboard. >>> >>> I deployed StarlingX 3 times again, but the situation never changes.. >>> >>> If you don't mind, can I see your ip setting with (ip a command)? >>> >>> Best Regards, >>> Jaewook. >>> >>> 2019년 2월 19일 (화) 오후 3:56, xiongzhiwei at baicells.com < >>> xiongzhiwei at baicells.com>님이 작성: >>> >>>> Hi Jaewook, >>>> >>>> I just finished stx all-in-one simplex on Bearmetal last week. The >>>> horizon service had been installed defaultly and you should be able to >>>> access the dashboard now. >>>> Your service list is same as mine. >>>> >>>> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >>>> +----------------------------------+------------+-----------------+ >>>> | ID | Name | Type | >>>> +----------------------------------+------------+-----------------+ >>>> | c51dfde10adf4445a78113ad6e648b9a | barbican | key-manager | >>>> | df07161f527b483292ac5aa5ed722687 | keystone | identity | >>>> | 744183df128d414f97390fb70fcac72f | sysinv | platform | >>>> | b9730f2e673443e4a6d003a7dad1d220 | fm | faultmanagement | >>>> | 5d7855696b1f440b8401670e1df6cb28 | glance | image | >>>> | 814a777c22884c97ab44baf0a4c2c669 | aodh | alarming | >>>> | 68362243cc214c4181a15e583894e495 | placement | placement | >>>> | 375cfb87c5f6449e81512ead128a513e | gnocchi | metric | >>>> | 2643dadbe71b4fc68ad4daa7d9d3859f | nova | compute | >>>> | f312a1c459c245c5a045c69688f695db | heat-cfn | cloudformation | >>>> | cbf811729020470a81b3c7be0d453fc9 | neutron | network | >>>> | 0fb46b24873648f9bac3a3e4d9f1f4e2 | patching | patching | >>>> | 52db1ccfca9d4033be5f1180c50d8234 | ceilometer | metering | >>>> | 094935b6dee245278bffc3f7ee21e9e9 | vim | nfv | >>>> | bc5297541def4f8b8881254af9896824 | smapi | smapi | >>>> | a388667479484a04824f07a672a331eb | panko | event | >>>> | 8c982073cd6c4d04b6ecb49e76650d2c | heat | orchestration | >>>> | 38c0b001ef514af5b1ba6947bed1bc6c | cinderv3 | volumev3 | >>>> | 98699ea84e4543b6b0808e24395542bb | cinderv2 | volumev2 | >>>> | 253390980b274178b7a16844e2c7a826 | cinder | volume | >>>> +----------------------------------+------------+-----------------+ >>>> >>>> BR >>>> Tim Xiong >>>> >>>> *From:* Jaewook Oh >>>> *Date:* 2019-02-19 12:48 >>>> *To:* starlingx-discuss ; 오재욱 >>>> >>>> *Subject:* Re: [Starlingx-discuss] [deploy-fail] Failed to deploy >>>> All-in-one simplex configuration >>>> Hello StarlingX Teams, >>>> >>>> I found that *the horizon dashboard project were not installed >>>> automatically* when I deployed StarlingX all-in-one simplex on >>>> Baremetal. >>>> Are there any reason for this problem..? >>>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>>> >>>> [wrsroot at controller-0 ~(keystone_admin)]$ openstack service list >>>> +----------------------------------+------------+-----------------+ >>>> | ID | Name | Type | >>>> +----------------------------------+------------+-----------------+ >>>> | f8b821fdd8e44d8484a3521ade041340 | barbican | key-manager | >>>> | 6f34b6874b624604a7f8798b95743dc4 | keystone | identity | >>>> | d31b2325f40e4ce88ca6974ee852eff6 | sysinv | platform | >>>> | cb68c2d74dc34caf91dfc92c9b099d22 | fm | faultmanagement | >>>> | a7f2ae41f2ff45bd904012a0a53b63ec | glance | image | >>>> | 3daea4e7507a4568a132579b4f30e4d6 | aodh | alarming | >>>> | af6e9c3f185f498a8f8b7d1afaeaa06d | placement | placement | >>>> | b1c2243ab7e24fe08bf408677a7f8e1d | gnocchi | metric | >>>> | 0e21d579ddee4f2dbfe98ff4069ce321 | nova | compute | >>>> | 15067bfe219b4645973f7399099c47da | heat-cfn | cloudformation | >>>> | ecf3478c84334c2ba647740bde190739 | neutron | network | >>>> | 28973cbc638c41c6b99b5e77264a2aec | patching | patching | >>>> | a120d0d2ed0b45b39114e4e9cab5fd78 | ceilometer | metering | >>>> | 12b32e4a181a4684ab05be02b3726d0c | vim | nfv | >>>> | a9c28c1889a347359a9b77edf53e5833 | smapi | smapi | >>>> | 2697e71aa8dc4f8b8d96c72b32c89440 | panko | event | >>>> | 57a5cb58128445b5819747271c095a89 | heat | orchestration | >>>> | 10c93aecb5a84278b940da2f8c3a1721 | cinderv3 | volumev3 | >>>> | b569ff8b77364311bbf3a5dee38dd614 | cinderv2 | volumev2 | >>>> | 449ceb89f8fe40779dd65c5a9c867161 | cinder | volume | >>>> +----------------------------------+------------+-----------------+ >>>> >>>> I thought horizon should also be installed with StarlingX's deployment. >>>> If not, please let me know how can I install horizon in this StarlingX. >>>> >>>> Thanks for help in advance :) >>>> >>>> Best Regards, >>>> Jaewook. >>>> >>>> >>>> 2019년 2월 12일 (화) 오후 2:54, Jaewook Oh 님이 작성: >>>> >>>>> Hello starlingx team, >>>>> >>>>> I deployed Starlingx All-in-one simplex setting on my server, >>>>> it seems deployment was done well. >>>>> *However I cannot access to the dashboard.* >>>>> >>>>> I used "2019-*Feb-08* 03:40:29 bootimage.iso". >>>>> >>>>> >>>>> Following log is the service that are now enabled, >>>>> [wrsroot at controller-0 ~(keystone_admin)]$ system service-list >>>>> +-----+-------------------------------+--------------+----------------+ >>>>> | id | service_name | hostname | state | >>>>> +-----+-------------------------------+--------------+----------------+ >>>>> | 68 | aodh-api | controller-0 | enabled-active | >>>>> | 69 | aodh-evaluator | controller-0 | enabled-active | >>>>> | 70 | aodh-listener | controller-0 | enabled-active | >>>>> | 71 | aodh-notifier | controller-0 | enabled-active | >>>>> | 102 | barbican-api | controller-0 | enabled-active | >>>>> | 103 | barbican-keystone-listener | controller-0 | enabled-active | >>>>> | 104 | barbican-worker | controller-0 | enabled-active | >>>>> | 43 | ceilometer-agent-notification | controller-0 | enabled-active | >>>>> | 14 | cgcs-export-fs | controller-0 | enabled-active | >>>>> | 10 | cgcs-fs | controller-0 | enabled-active | >>>>> | 16 | cgcs-nfs-ip | controller-0 | enabled-active | >>>>> | 35 | cinder-api | controller-0 | enabled-active | >>>>> | 38 | cinder-backup | controller-0 | enabled-active | >>>>> | 58 | cinder-ip | controller-0 | enabled-active | >>>>> | 56 | cinder-lvm | controller-0 | enabled-active | >>>>> | 36 | cinder-scheduler | controller-0 | enabled-active | >>>>> | 37 | cinder-volume | controller-0 | enabled-active | >>>>> | 23 | dnsmasq | controller-0 | enabled-active | >>>>> | 5 | drbd-cgcs | controller-0 | enabled-active | >>>>> | 55 | drbd-cinder | controller-0 | enabled-active | >>>>> | 75 | drbd-extension | controller-0 | enabled-active | >>>>> | 3 | drbd-pg | controller-0 | enabled-active | >>>>> | 6 | drbd-platform | controller-0 | enabled-active | >>>>> | 4 | drbd-rabbit | controller-0 | enabled-active | >>>>> | 77 | extension-export-fs | controller-0 | enabled-active | >>>>> | 76 | extension-fs | controller-0 | enabled-active | >>>>> | 24 | fm-mgr | controller-0 | enabled-active | >>>>> | 27 | glance-api | controller-0 | enabled-active | >>>>> | 26 | glance-registry | controller-0 | enabled-active | >>>>> | 108 | gnocchi-api | controller-0 | enabled-active | >>>>> | 109 | gnocchi-metricd | controller-0 | enabled-active | >>>>> | 62 | guest-agent | controller-0 | enabled-active | >>>>> | 64 | haproxy | controller-0 | enabled-active | >>>>> | 45 | heat-api | controller-0 | enabled-active | >>>>> | 46 | heat-api-cfn | controller-0 | enabled-active | >>>>> | 47 | heat-api-cloudwatch | controller-0 | enabled-active | >>>>> | 44 | heat-engine | controller-0 | enabled-active | >>>>> | 51 | horizon | controller-0 | enabled-active | >>>>> | 22 | hw-mon | controller-0 | enabled-active | >>>>> | 57 | iscsi | controller-0 | enabled-active | >>>>> | 25 | keystone | controller-0 | enabled-active | >>>>> | 50 | lighttpd | controller-0 | enabled-active | >>>>> | 2 | management-ip | controller-0 | enabled-active | >>>>> | 20 | mtc-agent | controller-0 | enabled-active | >>>>> | 28 | neutron-server | controller-0 | enabled-active | >>>>> | 9 | nfs-mgmt | controller-0 | enabled-active | >>>>> | 29 | nova-api | controller-0 | enabled-active | >>>>> | 63 | nova-api-proxy | controller-0 | enabled-active | >>>>> | 31 | nova-conductor | controller-0 | enabled-active | >>>>> | 33 | nova-console-auth | controller-0 | enabled-active | >>>>> | 34 | nova-novnc | controller-0 | enabled-active | >>>>> | 83 | nova-placement-api | controller-0 | enabled-active | >>>>> | 30 | nova-scheduler | controller-0 | enabled-active | >>>>> | 48 | open-ldap | controller-0 | enabled-active | >>>>> | 82 | panko-api | controller-0 | enabled-active | >>>>> | 52 | patch-alarm-manager | controller-0 | enabled-active | >>>>> | 7 | pg-fs | controller-0 | enabled-active | >>>>> | 15 | platform-export-fs | controller-0 | enabled-active | >>>>> | 11 | platform-fs | controller-0 | enabled-active | >>>>> | 17 | platform-nfs-ip | controller-0 | enabled-active | >>>>> | 12 | postgres | controller-0 | enabled-active | >>>>> | 65 | pxeboot-ip | controller-0 | enabled-active | >>>>> | 13 | rabbit | controller-0 | enabled-active | >>>>> | 8 | rabbit-fs | controller-0 | enabled-active | >>>>> | 49 | snmp | controller-0 | enabled-active | >>>>> | 19 | sysinv-conductor | controller-0 | enabled-active | >>>>> | 18 | sysinv-inv | controller-0 | enabled-active | >>>>> | 59 | vim | controller-0 | enabled-active | >>>>> | 60 | vim-api | controller-0 | enabled-active | >>>>> | 61 | vim-webserver | controller-0 | enabled-active | >>>>> +-----+-------------------------------+--------------+----------------+ >>>>> >>>>> As you can see, *I cannot find #1 service (oam-ip)*, and I think this >>>>> is one of the main reasons. >>>>> >>>>> *And also I had a problem when I followed the installation >>>>> instruction.* >>>>> >>>>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-create providernet-a --type=vlan >>>>> [wrsroot at controller-0 ~(keystone_admin)]$ neutron providernet-range-create --name providernet-a-range1 --range 100-400 providernet-a >>>>> >>>>> [wrsroot at controller-0 ~(keystone_admin)]$ system host-if-modify -c data controller-0 eth1000 -p providernet-a >>>>> >>>>> >>>>> Above instruction was not naturally worked, I mean the third command, >>>>> 'host-if-modify' failed with the message "*DataNetwork providernet-a >>>>> could not be found*." >>>>> >>>>> So I googled and I figured out I should command >>>>> $ *system datanetwork-add providernet-a vlan* >>>>> first. >>>>> >>>>> But I remember when my first deployment succeed, I didn't need to use >>>>> that command at all. (The deployment was implemented on Jan.) >>>>> >>>>> Any help is appreciated, thank you for your help in advance. >>>>> >>>>> Best Regards, >>>>> Jaewook. >>>>> >>>>> ================================================ >>>>> *Jaewook Oh* (오재욱) >>>>> IISTRC - Internet Infra System Technology Research Center >>>>> 369 Sangdo-ro, Dongjak-gu, >>>>> 06978, Seoul, Republic of Korea >>>>> >>>> >>>> >>>> -- >>>> ================================================ >>>> *Jaewook Oh* (오재욱) >>>> IISTRC - Internet Infra System Technology Research Center >>>> 369 Sangdo-ro, Dongjak-gu, >>>> 06978, Seoul, Republic of Korea >>>> >>>> >>> >>> -- >>> ================================================ >>> *Jaewook Oh* (오재욱) >>> IISTRC - Internet Infra System Technology Research Center >>> 369 Sangdo-ro, Dongjak-gu, >>> 06978, Seoul, Republic of Korea >>> >>> >> >> -- >> ================================================ >> *Jaewook Oh* (오재욱) >> IISTRC - Internet Infra System Technology Research Center >> 369 Sangdo-ro, Dongjak-gu, >> 06978, Seoul, Republic of Korea >> > > > -- > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image(02-20-14-18-25).png Type: image/png Size: 21938 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 27999 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 66122 bytes Desc: not available URL: From kyle.oh95 at gmail.com Wed Feb 20 06:41:55 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Wed, 20 Feb 2019 15:41:55 +0900 Subject: [Starlingx-discuss] Fwd: Re: [deploy-fail] Failed to deploy All-in-one simplex configuration In-Reply-To: References: <201902191456126968489@baicells.com> <2019021915163953671221@baicells.com> <2019022014233126084427@baicells.com> Message-ID: Thank you Tim, I didn't know the dashboard is in the /usr/share TT... By the way, I tried as you showed, but it showed Connection Refused. So I had thought maybe firewall something like that can impact to this, I disabled iptables, ip6tables, and firewalld. However, the result was same... [image: image.png] And I'm not sure what below figure means, but attach anyway. Please it could be the key of the problem... [image: image.png] Best Regards, Jaewook. 2019년 2월 20일 (수) 오후 3:23, xiongzhiwei at baicells.com 님이 작성: > Hi Jaewook, > There is no horizon directory in /etc, openstack-dashboard was installed > in /usr/share/. > Can you ignore to access the installation directory and try to test with > 'wget' command? > Just like below: > > controller-0:~$ wget http://10.10.10.2/dashboard > --2019-02-20 06:15:23-- http://10.10.10.2/dashboard > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2019-02-20 06:15:23 ERROR 404: Not Found. > > controller-0:~$ wget http://10.10.10.2/ > --2019-02-20 06:15:38-- http://10.10.10.2/ > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://10.10.10.2/auth/login/?next=/ [following] > --2019-02-20 06:15:38-- http://10.10.10.2/auth/login/?next=/ > Connecting to 10.10.10.2:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 9309 (9.1K) [text/html] > Saving to: ‘index.html’ > > 100%[==================================================================================================================================================================================================>] > 9,309 --.-K/s in 0s > > 2019-02-20 06:15:38 (55.8 MB/s) - ‘index.html’ saved [9309/9309] > > controller-0:~$ wget http://192.168.107.232 > --2019-02-20 06:16:31-- http://192.168.107.232/ > Connecting to 192.168.107.232:80... connected. > HTTP request sent, awaiting response... 302 Found > Location: http://192.168.107.232/auth/login/?next=/ [following] > --2019-02-20 06:16:31-- http://192.168.107.232/auth/login/?next=/ > Connecting to 192.168.107.232:80... connected. > HTTP request sent, awaiting response... 200 OK > Length: 9309 (9.1K) [text/html] > Saving to: ‘index.html.1’ > > 100%[==================================================================================================================================================================================================>] > 9,309 --.-K/s in 0s > > 2019-02-20 06:16:31 (137 MB/s) - ‘index.html.1’ saved [9309/9309] > > BR > Tim Xiong > > > *From:* Jaewook Oh > *Date:* 2019-02-20 14:13 > *To:* xiongzhiwei at baicells.com > *CC:* starlingx-discuss ; 오재욱 > > *Subject:* Re: Re: [Starlingx-discuss] [deploy-fail] Failed to deploy > All-in-one simplex configuration > Hello StarlingX Team and Tim, > > I'm still struggling to deploy StarlingX normally, but it seems it will > never succeed. > I used the latest boot image, Feb 18th. > > However the symptom is same. > And I found that there were no horizon directory in /etc/. > [image: image.png] > > Do I need to install horizon manually? > > BR, > Jaewook. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image(02-20-14-18-25).png Type: image/png Size: 21938 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 27999 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 66122 bytes Desc: not available URL: From openstack at medberry.net Wed Feb 20 13:58:15 2019 From: openstack at medberry.net (David Medberry) Date: Wed, 20 Feb 2019 06:58:15 -0700 Subject: [Starlingx-discuss] [all] Denver Forum Brainstorming In-Reply-To: References: Message-ID: Probably that should have been a link to: https://wiki.openstack.org/wiki/Forum/Denver2019 On Tue, Feb 19, 2019 at 7:41 PM Kendall Nelson wrote: > > Hello Everyone! > > > Welcome to the topic selection process for our Forum in Denver! This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. > > > For OpenStack > > Denver marks the beginning of Train’s release cycle, where ideas and requirements will be gathered. We should come armed with feedback from the upcoming Stein release if at all possible. We aim to ensure the broadest coverage of topics that will allow for multiple parts of the community getting together to discuss key areas within our community/projects. > > > For OSF Projects (StarlingX, Zuul, Airship, Kata Containers) > > As a refresher, the idea is to gather ideas and requirements for your project’s upcoming release. Look to https://wiki.openstack.org/wiki/Forum for an idea of how to structure fishbowls and discussions for your project. The idea is to ensure the broadest coverage of topics, while allowing for the project community to discuss critical areas of concern. To make sure we are presenting the best topics for discussion, we have asked representatives of each of your projects to help us out in the Forum selection process. > > > There are two stages to the brainstorming: > > > 1.If you haven’t already, its encouraged that you set up an etherpad with your team and start discussing ideas you'd like to talk about at the Forum and work out which ones to submit. > > > 2. On the 22nd of February, we will open up a more formal web-based tool for you to submit abstracts for the most popular sessions that came out of your brainstorming. > > > Make an etherpad and add it to the list at: https://wiki.openstack.org/wiki/Forum/Denver2018 > > > This is your opportunity to think outside the box and talk with other projects, groups, and individuals that you might not see during Summit sessions. Look for interested parties to collaborate with and share your ideas. > > > Examples of typical sessions that make for a great Forum: > > Strategic, whole-of-community discussions, to think about the big picture, including beyond just one release cycle and new technologies > > eg Making OpenStack One Platform for containers/VMs/Bare Metal (Strategic session) the entire community congregates to share opinions on how to make OpenStack achieve its integration engine goal > > Cross-project sessions, in a similar vein to what has happened at past forums, but with increased emphasis on issues that are of relevant to all areas of the community > > eg Rolling Upgrades at Scale (Cross-Project session) – the Large Deployments Team collaborates with Nova, Cinder and Keystone to tackle issues that come up with rolling upgrades when there’s a large number of machines. > > Project-specific sessions, where community members most interested in a specific project can discuss their experience with the project over the last release and provide feedback, collaborate on priorities, and present or generate 'blue sky' ideas for the next release > > eg Neutron Pain Points (Project-Specific session) – Co-organized by neutron developers and users. Neutron developers bring some specific questions about implementation and usage. Neutron users bring feedback from the latest release. All community members interested in Neutron discuss ideas about the future. > > > Think about what kind of session ideas might end up as: Project-specific, cross-project or strategic/whole-of-community discussions. There'll be more slots for the latter two, so do try and think outside the box! > > > This part of the process is where we gather broad community consensus - in theory the second part is just about fitting in as many of the good ideas into the schedule as we can. > > > Further details about the forum can be found at: https://wiki.openstack.org/wiki/Forum > > > Thanks all! > > Kendall Nelson, on behalf of the OpenStack Foundation, User Committee & Technical Committee > > > > From build.starlingx at gmail.com Wed Feb 20 23:00:04 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Feb 2019 18:00:04 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_flock_images - Build # 49 - Failure! Message-ID: <2074885088.59.1550703605114.JavaMail.javamailuser@localhost> Project: STX_build_docker_flock_images Build #: 49 Status: Failure Timestamp: 20190220T211338Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs -------------------------------------------------------------------------------- Parameters HOST_PORT: 80 MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190220T181924Z OS: centos MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root BASE_VERSION: f-stein-20190220T181924Z PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs REGISTRY_USERID: slittlewrs HOST: build.starlingx.cengn.ca LATEST_PREFIX: f-stein PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs PUBLISH_TIMESTAMP: 20190220T181924Z FLOCK_VERSION: f-stein-centos-master-20190220T181924Z PREFIX: f-stein OPENSTACK_RELEASE: master TIMESTAMP: 20190220T181924Z REGISTRY_ORG: starlingx PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190220T181924Z/outputs REGISTRY: docker.io From build.starlingx at gmail.com Wed Feb 20 23:00:07 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Feb 2019 18:00:07 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_docker_images - Build # 48 - Still Failing! In-Reply-To: <1658330854.49.1550567233607.JavaMail.javamailuser@localhost> References: <1658330854.49.1550567233607.JavaMail.javamailuser@localhost> Message-ID: <36263661.62.1550703609074.JavaMail.javamailuser@localhost> Project: STX_build_docker_images Build #: 48 Status: Still Failing Timestamp: 20190220T210610Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs -------------------------------------------------------------------------------- Parameters BRANCH: f/stein MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190220T181924Z OS: centos MUNGED_BRANCH: f-stein MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein PUBLISH_DISTRO_BASE: /export/mirror/starlingx/feature/stein/centos PUBLISH_TIMESTAMP: 20190220T181924Z DOCKER_BUILD_ID: jenkins-f-stein-20190220T181924Z-builder OPENSTACK_RELEASE: master TIMESTAMP: 20190220T181924Z OS_VERSION: 7.5.1804 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190220T181924Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/feature/stein/centos/20190220T181924Z/outputs From build.starlingx at gmail.com Wed Feb 20 23:00:11 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Wed, 20 Feb 2019 18:00:11 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_stein_master - Build # 50 - Failure! Message-ID: <868626973.65.1550703612875.JavaMail.javamailuser@localhost> Project: STX_build_stein_master Build #: 50 Status: Failure Timestamp: 20190220T181924Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190220T181924Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: true From erich.cordoba.malibran at intel.com Wed Feb 20 23:20:56 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 20 Feb 2019 23:20:56 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> Message-ID: <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> Hi, I just reviewed the tool and I think it's a great tool and it will be really useful for the community. I just have one general question that I would like to extend to the community. Should this tool be supported by a spec? -Erich On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: > A Python-based installer for StarlingX has been submitted to stx- > tools repo. This automated installer has been used by Wind River > engineers on a continual basis for installing StarlingX on VBox > environment. This installer is not a new development. This has been > used for several years for quick install on VBox. It is being > delivered to help community for ease of installation of starlingx. > Feel free to use this installer and even add new features to serve > the community better. > > The installer is going in via following submission: > https://review.openstack.org/#/c/637958/ > > Numan. > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From glenn.seiler at windriver.com Wed Feb 20 23:21:39 2019 From: glenn.seiler at windriver.com (Seiler, Glenn) Date: Wed, 20 Feb 2019 23:21:39 +0000 Subject: [Starlingx-discuss] Contributor Survey In-Reply-To: <834BB696-A390-4E15-9874-52141B49335F@gmail.com> References: <586E8B730EA0DA4A9D6A80A10E486BC0A0749D@ALA-MBD.corp.ad.wrs.com> <834BB696-A390-4E15-9874-52141B49335F@gmail.com> Message-ID: Ildiko, team I think there are logical steps in the progression of someone using a project like StarlingX. First is just to download it, (or build it) and try to run some sample VMs or containers. Second would be to start a PoC or evaluation and maybe contribute to the project. Only after the first two steps would anyone start to consider deployment. So I think asking about deployment will not get us where we want to be. I think we focus on the first step, almost exclusively. - do they even know about StarlingX!! -have they downloaded it? Do they plan to? -have they had any problems... -what can we do to make it easier for them... I think that is step 1. We can agree to skip that step and go straight to what they want to deploy on the edge, but those are really two very different surveys. If we want to focus on what they deploy at the edge, we have to acknowledge they very well may not even be deploying StarlingX....after all it is still very young and companies can take many months or years before they deploy. -glenn -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Wednesday, February 20, 2019 11:26 AM To: Zvonar, Bill Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Contributor Survey Hi Bill, Thank you for adding the contributor focused questions. On the today’s call we’ve discussed the base idea being to have a high level user survey type of questionnaire that focuses on understanding the use case and motivation for companies who are planning to deploy or use an edge platform and ask their plans and current stage with StarlingX. Our motivation is to start building and growing the ecosystem around StarlingX and understand the market a little better as well. When it comes to contributions we listed two options. We can either add a question or two to the above initial survey to see if a certain responder is also interested in contributing or we can run it as a separate survey. If we can make it happen on the tooling side we could also consider showing deeper dive questions if someone says they are interested in contributing and not displaying those questions if that’s not a primary interest for them at this point. In my view if we run a contribution focused survey we need to set the scope and decide what challenges we would like to get an answer to when we put together the questions. Like whether we would like to find roadblocks or bottlenecks that make it harder for people to join or learn which area they are interested in and if the latter what the next step is once we have the results and whether the survey is the best way to reach out to new contributors who are just getting started to help them. What do others think or would be interested in learning about? If you would like to participate in drafting the survey(s) please check out the etherpad and add comments and ideas! Thanks, Ildikó > On 2019. Feb 20., at 18:50, Zvonar, Bill wrote: > > Hi Ildiko, > > As discussed in the Community Marketing Planning call today, I’ve placed a draft of a Contributor Survey up on [0]. > > It’s not quite the same as the survey you started, it’s more directed at individuals who have already expressed an interest in contributing – a survey like this will help them understand how & where they can do so. > > It’s a draft – comments welcome from the community. > > Bill… > > [0] https://etherpad.openstack.org/p/stx-user-survey > > > _______________________________________________ > 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 Thu Feb 21 01:11:48 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 21 Feb 2019 01:11:48 +0000 Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent In-Reply-To: <7B6A2AE64F40F245AE81F245059F0C366BE4351D@ALA-MBD.corp.ad.wrs.com> References: <7B6A2AE64F40F245AE81F245059F0C366BE43190@ALA-MBD.corp.ad.wrs.com> <7B6A2AE64F40F245AE81F245059F0C366BE4351D@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Joseph: This is based on latest master. I have tried several times . The good news is that after increasing VM memory (from 18G to 24G) , This issue is gone. (same iso, same pc) Thanks your support. Thanks. BR Austin Sun. From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Thursday, February 21, 2019 3:28 AM To: Sun, Austin ; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Which build is this? Has you reproduced this failure? Do you see any errors in your puppet logs on controller-0 from when you unlocked it? From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Wednesday, February 20, 2019 2:36 AM To: Richard, Joseph; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi Joseph: Thanks. The result of ovs-vsctl show is below: I have pasted the yaml files with below link. /opt/platform/helm/19.01/openstack-neutron.yaml http://paste.openstack.org/show/745435/ /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml http://paste.openstack.org/show/745436/ /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml http://paste.openstack.org/show/745437/ 168464a5-d278-47b8-a3b0-01f86cfec2bb Manager "ptcp:6640:127.0.0.1" Bridge "br-phy1" Port "lldp160b8b4f-a3" Interface "lldp160b8b4f-a3" type: internal Port "eth1" Interface "eth1" type: dpdk options: {dpdk-devargs="0000:02:04.0", n_rxq="2"} Port "br-phy1" Interface "br-phy1" type: internal Bridge "br-phy0" Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:02:03.0", n_rxq="2"} Port "br-phy0" Interface "br-phy0" type: internal Port "lldp706c54b4-b5" Interface "lldp706c54b4-b5" type: internal ovs_version: "2.9.0" Thanks. BR Austin Sun. From: Richard, Joseph [mailto:Joseph.Richard at windriver.com] Sent: Wednesday, February 20, 2019 1:10 AM To: Sun, Austin >; starlingx-discuss at lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Which build is this? Can you provide the contents of these files on your lab? /opt/platform/helm/19.01/openstack-neutron.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.3.yaml /opt/platform/puppet/19.01/hieradata/192.168.204.4.yaml Also, please provide the output of this command run on controller-0: ovs-vsctl show From: Sun, Austin [mailto:austin.sun at intel.com] Sent: Tuesday, February 19, 2019 9:38 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] duplex deploy failed neutron-ovs-agent Hi All: I'm deploying duplex container mode with latest code . meet some error for neutron-ovs-agent Both controller have same configuration and deploy in virtual machine (qemu kvm env) . Does anyone have similar experience and suggest how to solve it ? *) The status of neutron-ovs-agent: neutron-ovs-agent-controller-0-a762cb46-h9xqw 0/1 Init:CrashLoopBackOff 11 42m neutron-ovs-agent-controller-1-f2c6aeed-427h8 1/1 Running 0 42m *) The log of neutron-ovs-agent-controller-0-a762cb46-h9xqw is : + timeout 3m neutron-sanity-check --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/openvswitch_agent.ini --ovsdb_native --nokeepalived_ipv6_support Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so pleas e use SIGUSR2 to generate reports. 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] Logging enabled! 2019-02-19 13:12:44.720 254 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-sanity-check version 11.0.0 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch/impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: vxlantest-fe9ff 2019-02-19 13:12:45.083 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl [-] Post-commit checks failed: VswitchdInterfaceAddException: Failed to add interfa ces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl Traceback (most recent call last): 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 38, in post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl self.do_post_commit(txn) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl File "/var/lib/openstack/lib/python2.7/site-packages/ovsdbapp/schema/open_vswitch /impl_idl.py", line 50, in do_post_commit 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl ifaces=", ".join(failed)) 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl VswitchdInterfaceAddException: Failed to add interfaces: 192.0.2.1 2019-02-19 13:12:45.102 254 ERROR ovsdbapp.schema.open_vswitch.impl_idl 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib [-] Timed out retrieving ofport on port 192.0.2.1.: RetryError: RetryError[] 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib Traceback (most recent call last): 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", lin e 321, in get_port_ofport 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib ofport = self._get_port_val(port_name, "ofport") 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/neutron/agent/common/ovs_lib.py", line 89, in wrapped 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return new_fn(*args, **kwargs) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 171, in wrapped_f 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib return self.call(f, *args, **kw) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 248, in call 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib start_time=start_time) 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 216, in iter 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise RetryError(fut).reraise() 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib File "/var/lib/openstack/lib/python2.7/site-packages/tenacity/__init__.py", line 298, in reraise 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib raise self 2019-02-19 13:12:55.412 254 ERROR neutron.agent.common.ovs_lib RetryError: RetryError[ From liang.a.fang at intel.com Thu Feb 21 09:05:55 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Thu, 21 Feb 2019 09:05:55 +0000 Subject: [Starlingx-discuss] Which code line created the users in keystone table local_user In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA66122@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA66122@ALA-MBD.corp.ad.wrs.com> Message-ID: Hi Bart I take a look of cinder.pp and now know the cinder user is created by openstack cmd(openstack client) finally in keystone.rb. Thanks. You said: "After that, the cinder user would be created by the application of helm charts", currently this code has not been checked-in in stx-config, right? I tried to find related code but with no luck. I believe the code is ready in somewhere because it is about to cut over. Could you please point out the code? Thanks. Currently my environment is deployed by an ISO which generated on Jan 1st 2019. Before the cut over finished, it is not possible to deploy an containerized starlingx environment through an official ISO, right? Appreciate if you can share something about how you are debugging with containerized starlingx. Regards Liang From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Tuesday, February 19, 2019 9:13 PM To: Fang, Liang A ; Penney, Don Cc: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: Which code line created the users in keystone table local_user Liang, Today, the cinder user is created by puppet when it applies the ::cinder::keystone::auth class. You can see this class being included in stx-config/puppet-manifests/src/modules/openstack/manifests/cinder.pp. However, this puppet code will no longer be used, once we cut over to containers (in the next week or so I think). After that, the cinder user would be created by the application of helm charts. You can see the overrides for the cinder helm chart being populated at stx-config/sysinv/sysinv/sysinv/helm/cinder.py. I would recommend you start working with the helm charts in the containers environment, since the puppet code will be gone soon. Bart From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: February 18, 2019 3:20 AM To: Wensley, Barton; Penney, Don Cc: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: Which code line created the users in keystone table local_user Hi Bart and Don In keystone table 'local_user', there's lots of users created (see below), could you please point out which code line created these users? [Bart] Table deleted due to mailing list size restrictions that were apparently defined when we were all using 300 baud modems... The background: In code review https://review.openstack.org/#/c/633400/, we need to create an internal project and user for raw cache. Currently I use puppet to call cmd "openstack" to create/get the project/user id. I found the user(cinder) has already been created by some existing code, see above picture please. So I'm expecting to create internal project the same way as internal user. Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From huang.shuquan at 99cloud.net Thu Feb 21 11:22:23 2019 From: huang.shuquan at 99cloud.net (Shuquan Huang) Date: Thu, 21 Feb 2019 19:22:23 +0800 Subject: [Starlingx-discuss] Project Update and Onboarding sessions at the Open Infra Summit In-Reply-To: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> References: <4A9BD7B6-3723-4168-9F44-284DBB3ACF66@gmail.com> Message-ID: Hi Ildiko, I'd like to help with both sessions. On 2019/2/20, 4:50 AM, "Ildiko Vancsa" wrote: Hi, I’m reaching out to you as we’ve reached the point of Summit planning to decide about the project update and onboarding sessions. This is the time period to request the above mentioned sessions and decide about speakers if the project decides to have them. We had both of these in Berlin and as we would like to make sure that we use every opportunity to spread the word about StarlingX and help onboarding new contributors I think it is a great opportunity to request both of these slots for Denver as well. The project onboarding session is a 40-minute long session with the purpose of helping newcomers to find the entry points to the project and make sure they have all the basic information to get started. The project update session is a 20-minute long session to highlight enhancements, new features and interesting items from the roadmap. There is an opportunity to request a full 40-minute long slot for this session that the project will get based on availability. I need volunteers for both sessions as presenters from the community. __Please reply to this thread in case you are interested in participating in either or both of the above sessions.__ Is there a need to request an extended slot for the project update? Please let me know if you have any questions. Thanks, Ildikó _______________________________________________ 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 Thu Feb 21 11:50:14 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 21 Feb 2019 11:50:14 +0000 Subject: [Starlingx-discuss] Pipe external multiple VLANs Message-ID: Hi, i have several external VLANs and i would like to bring them as tagged VLANs into a tenant network. I'm not sure how to implement this in StarlingX? Most of the changes to config files will be overwritten by puppet, do you have a hint for me how to do that? thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bill.Zvonar at windriver.com Thu Feb 21 12:36:51 2019 From: Bill.Zvonar at windriver.com (Zvonar, Bill) Date: Thu, 21 Feb 2019 12:36:51 +0000 Subject: [Starlingx-discuss] Community Meeting Notes - Feb 20, 2019 Message-ID: <586E8B730EA0DA4A9D6A80A10E486BC0A07AA6@ALA-MBD.corp.ad.wrs.com> Notes from Feb 20th call below, and at [0]. Bill... [0] https://etherpad.openstack.org/p/stx-status Open Infrastructure Summit sessions speakers needed (ildikov) - Project Update 20min (Can request a 40min slot) - Project Onboarding 40min - schedule will go live today - still need volunteers for the Onboarding session - reach out to Ildiko if you're interested VirtualBox install instructions (Numan) - https://wiki.openstack.org/wiki/StarlingX/StarlingX_VirtualBox_Configuration_Guide - working on an automated one-click install https://review.openstack.org/#/c/637958/ - very close to being ready for everyone to use - please try it out & let Numan know via the community mailing list if you run into any issues Sub-project updates - Release (Ghada) - line by line through the Release Plan, for everything that's not complete - Build: Build System Support for multi-OS Prep - Victor: changing to focus on Ubuntu, but won't touch the existing build system - nothing's going into Master, so we agreed to remove it from the current release plan - Lights On: CVE Upgrades - Ken: working to select preliminary tools, close by March 1; have first report by April 5 - Lights On: User Documentation - Abraham: working to split this & update docs.starlingx.io, next week - Lights On: CentOS 7.6 - Cindy: test (Numan) stuck currently due to build issue; still planning to do the cutover after the cutover to Stein - ~week of March 4 to week of March 11 - Lights On: OVS/Mellanox - Ghada: will need to re-plan - Lights On: Ceph Upgrade - Cindy/Frank: working through training/planning - will propose a new plan by next week's meeting (won't make 2/28) - Lights On: Python 3 Readiness (Prep) - Cindy/Victor: one minor-ish story to complete - Lights On: C/C++ w/ Defenses Enabled - Victor: this is currently on hold while performance measurement framework is being sorted out - New: Containerized OpenStack - Frank: day by day right now, working through cutover-gating items & getting sanity clean across all configs - best case next Monday (Feb 25) - New: Distributed Cloud UI / Distributed Keystone / Distributed Glance - no update this week - Other: Integrate Containerized OVS - Ghada: working with Forrest on this, will have provide update after next networking meeting - Other: Ansible Bootstrap Deployment - Dariush: code should be out for review in the first week of March - Saul requested a work in progress code review as soon as possible (W-1) - Technical Debt: Distro OpenStack Patch Elimination - Bill: getting redder as we get closer to Stein cut-off - Bill to send minutes from yesterday's DOS meeting - Technical Debt: Distro Non-OpenStack Patch Backlog - Cindy: not much progress recently - still believe they can finish the ~20 patches after finishing up CentOS upgrade - Technical: OpenStack Rebase - Ghada: we are on Stein, cutting over soon - Test: DevStack Enablement - Cindy: may be bigger than thought initially, due to Stein - some Pike stuff won't work on Stein out of the box - working the plan to get through this, will provide an update next week - sub-projects were covered as we went through the release plan items, except where noted... - Containers (Frank) - Security (Ken) - Ceph Upgrade (Vivian) - CentOS Upgrade (Cindy) - Networking (Ghada) - Docs (Michael / Bruce) - no update - will ask about it offline - Build (Caesar) - Test (Ada/Numan) - mostly working on manual regression testcases - plan is to have in repo by end of next week - other focus areas are Containers & OVS-DPDK - next up is the feature testcases into the repo - Multi-OS (Cesar) - OpenStack (Bill) - flat trend upstream continues, particularly in Nova - need to take new action in order to get stuff in for this release, will send details in distro meeting notes - Defect Trend (Bill) - https://docs.google.com/spreadsheets/d/1DZZgqrCIL6wxv51_yFBk6Lfmtf1AqPD6z7e5hEs3prU/edit?usp=sharing - similar trend continuing, Bill still has the action about the "help wanted" tags - Open ARs - https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-RnUQoyc4/edit?usp=sharing - AR owners are asked to update their ARs on this sheet From Dariush.Eslimi at windriver.com Thu Feb 21 13:44:02 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Thu, 21 Feb 2019 13:44:02 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> Message-ID: Hi, I see Spec as a high level design for a code that going to be developed, and to make sure it aligns with how community is going to use it and to make everybody aware of what is going to do, so others can chime in and say things that can address multiple needs and influence its design. Let's call this apple. Now I see the case of a code that has been developed before even the community existed, and now been presented to the community to fill a gap and improve productivity, no time to change the design and would be up to community to accept or reject it as is. A case of donation really, I call this one Orange. For Orange I think Spec is not the right word, we need a wiki/readme to see what it does, and how to use it. It is too late to produce a spec to influence the design. My .02$, Dariush -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: February-20-19 6:21 PM To: Waheed, Numan ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Python Based VBox Installer Hi, I just reviewed the tool and I think it's a great tool and it will be really useful for the community. I just have one general question that I would like to extend to the community. Should this tool be supported by a spec? -Erich On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: > A Python-based installer for StarlingX has been submitted to stx- > tools repo. This automated installer has been used by Wind River > engineers on a continual basis for installing StarlingX on VBox > environment. This installer is not a new development. This has been > used for several years for quick install on VBox. It is being > delivered to help community for ease of installation of starlingx. > Feel free to use this installer and even add new features to serve the > community better. > > The installer is going in via following submission: > https://review.openstack.org/#/c/637958/ > > Numan. > _______________________________________________ > 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 Barton.Wensley at windriver.com Thu Feb 21 14:04:08 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Thu, 21 Feb 2019 14:04:08 +0000 Subject: [Starlingx-discuss] Which code line created the users in keystone table local_user In-Reply-To: References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA66122@ALA-MBD.corp.ad.wrs.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA66FB9@ALA-MBD.corp.ad.wrs.com> Liang, Brent Rowsell added a comment to your inspection on February 16th that points you to the code you would need to modify. You can install a containerized environment with a recent ISO - instructions are found at https://wiki.openstack.org/wiki/StarlingX/Containers. Bart From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: February 21, 2019 4:06 AM To: Wensley, Barton; Penney, Don Cc: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: RE: Which code line created the users in keystone table local_user Hi Bart I take a look of cinder.pp and now know the cinder user is created by openstack cmd(openstack client) finally in keystone.rb. Thanks. You said: "After that, the cinder user would be created by the application of helm charts", currently this code has not been checked-in in stx-config, right? I tried to find related code but with no luck. I believe the code is ready in somewhere because it is about to cut over. Could you please point out the code? Thanks. Currently my environment is deployed by an ISO which generated on Jan 1st 2019. Before the cut over finished, it is not possible to deploy an containerized starlingx environment through an official ISO, right? Appreciate if you can share something about how you are debugging with containerized starlingx. Regards Liang From: Wensley, Barton [mailto:Barton.Wensley at windriver.com] Sent: Tuesday, February 19, 2019 9:13 PM To: Fang, Liang A ; Penney, Don Cc: Rowsell, Brent ; starlingx-discuss at lists.starlingx.io Subject: RE: Which code line created the users in keystone table local_user Liang, Today, the cinder user is created by puppet when it applies the ::cinder::keystone::auth class. You can see this class being included in stx-config/puppet-manifests/src/modules/openstack/manifests/cinder.pp. However, this puppet code will no longer be used, once we cut over to containers (in the next week or so I think). After that, the cinder user would be created by the application of helm charts. You can see the overrides for the cinder helm chart being populated at stx-config/sysinv/sysinv/sysinv/helm/cinder.py. I would recommend you start working with the helm charts in the containers environment, since the puppet code will be gone soon. Bart From: Fang, Liang A [mailto:liang.a.fang at intel.com] Sent: February 18, 2019 3:20 AM To: Wensley, Barton; Penney, Don Cc: Rowsell, Brent; starlingx-discuss at lists.starlingx.io Subject: Which code line created the users in keystone table local_user Hi Bart and Don In keystone table 'local_user', there's lots of users created (see below), could you please point out which code line created these users? [Bart] Table deleted due to mailing list size restrictions that were apparently defined when we were all using 300 baud modems... The background: In code review https://review.openstack.org/#/c/633400/, we need to create an internal project and user for raw cache. Currently I use puppet to call cmd "openstack" to create/get the project/user id. I found the user(cinder) has already been created by some existing code, see above picture please. So I'm expecting to create internal project the same way as internal user. Thanks. Regards Liang -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Thu Feb 21 14:15:18 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Feb 2019 09:15:18 -0500 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> Message-ID: On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush < Dariush.Eslimi at windriver.com> wrote: > Hi, > > I see Spec as a high level design for a code that going to be developed, > and to make sure it aligns with how community is going to use it and to > make everybody aware of what is going to do, so others can chime in and say > things that can address multiple needs and influence its design. Let's call > this apple. > > Now I see the case of a code that has been developed before even the > community existed, and now been presented to the community to fill a gap > and improve productivity, no time to change the design and would be up to > community to accept or reject it as is. A case of donation really, I call > this one Orange. > > For Orange I think Spec is not the right word, we need a wiki/readme to > see what it does, and how to use it. It is too late to produce a spec to > influence the design. > > OpenStack Operators have a tools landing repository [1] that didn't/doesn't have the same level of requirements the rest of the OpenStack code typically does, so organizations could open source internal. potentially untested, scripts but not have to necessarily adhere to all of the usual requirements. Over time the code in that repository could be improved and moved out once it made sense. I think it's worthwhile to have useful internal code open sourced, and in some cases make it a bit easier to do so, and if the code/tool gets used then start improving it following general standards. This would require a new repository. Just a thought. :) Thanks, Curtis [1]: https://git.openstack.org/cgit/openstack/osops-tools-contrib/tree/README.rst My .02$, > Dariush > > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > Sent: February-20-19 6:21 PM > To: Waheed, Numan ; > starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > Hi, > > I just reviewed the tool and I think it's a great tool and it will be > really useful for the community. I just have one general question that I > would like to extend to the community. Should this tool be supported by a > spec? > > -Erich > > On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: > > A Python-based installer for StarlingX has been submitted to stx- > > tools repo. This automated installer has been used by Wind River > > engineers on a continual basis for installing StarlingX on VBox > > environment. This installer is not a new development. This has been > > used for several years for quick install on VBox. It is being > > delivered to help community for ease of installation of starlingx. > > Feel free to use this installer and even add new features to serve the > > community better. > > > > The installer is going in via following submission: > > https://review.openstack.org/#/c/637958/ > > > > Numan. > > _______________________________________________ > > 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 > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jolliffe at windriver.com Thu Feb 21 14:25:46 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 21 Feb 2019 14:25:46 +0000 Subject: [Starlingx-discuss] Minutes - Feb 14th TSC meeting Message-ID: Hi all; TSC attendees: Ana, Brent, Curtis, Dean, Ian, Miguel, Saul Notes and actions: Deep Dive into Multi-OS related Specs - Homework for TSC members, please read Specifications before TSC meeting. * The MultiOS specs were discussed and TSC members were asked to review and provide comments. Next steps for Packet.com PoC * We discussed the potential of the Packet.com opportunity. There are many ways we could approach this and we decided we needed a call with the Packet team to understand more. * https://etherpad.openstack.org/p/starlingx-packet-edge-pilot * Action: Curtis to set up a call with the interested parties on the Etherpad Documentation Mega Spec: https://review.openstack.org/#/c/635641/ * Curtis - The proposed docs are quite extensive (which frankly, is great) and would, and if completed, considerably expand (AFAIK) on what architecture and operations documentation exist in upstream OpenStack. Also, some of the proposed documentation, network providers for example, may be better off either pointing upstream or having the work be done upstream. I guess my point is that if there are resources to complete this documentation, then maybe we should think a bit about upstream as well. Could we collaborate with the upstream docs team? If some of STX's documentation could help outside of STX, then that might help to clear up confusion around exactly what STX is. Maybe cross-project is a better term than upstream. :) * Action: comments in spec Gerrit – TSC members please review FYI - OpenStack Operator meetup in Berlin – Curtis * It is sponsored by a telecom. * Links: * http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002436.html * https://etherpad.openstack.org/p/BER-ops-meetup * Action: If anyone lives close or has people in the area that could attend. Regards; Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Thu Feb 21 15:02:39 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Thu, 21 Feb 2019 16:02:39 +0100 (CET) Subject: [Starlingx-discuss] Duplex, Bare Metal: controller-0 hangs in "Created/Removed slice User Slice of root" Message-ID: <313117267.138021.1550761359312@communicator.strato.com> Hi, after installation of controller-0 (bare metal, duplex) it hangs after 2 reboots in [ OK ] Started Open vSwitch Forwarding Unit. Starting Open vSwitch... [ OK ] Started Open vSwitch. Starting Cleanup of Temporary Directories... [ OK ] Started Cleanup of Temporary Directories. [ OK ] Created slice User Slice of root. [ OK ] Removed slice User Slice of root. [ OK ] Created slice User Slice of root. [ OK ] Removed slice User Slice of root. [ OK ] Created slice User Slice of root. [ OK ] Removed slice User Slice of root. [ OK ] Created slice User Slice of root. [ OK ] Removed slice User Slice of root. Any idea what this is? We are using the image centos-20190219T060000Z. Thanks Marcel From Volker.Hoesslin at swsn.de Thu Feb 21 15:26:18 2019 From: Volker.Hoesslin at swsn.de (von Hoesslin, Volker) Date: Thu, 21 Feb 2019 15:26:18 +0000 Subject: [Starlingx-discuss] Pipe external multiple VLANs In-Reply-To: <3k03ta01c8bua41d@shdsegapp2> References: <3k03ta01c8bua41d@shdsegapp2> Message-ID: i know, this is all openstack basic knowledg but sometimes i need some additional time to see all this stuff. to answer my own questen, see: https://wiki.openstack.org/wiki/Neutron/TrunkPort#CLI_usage_examples by the way, so i'm missing the horizon gui to handle trunks. is this also comming in new release "stein" ? btw2: what about the facts to update the official stable relase to the new one? can this be without a complet new install?! volker... ________________________________ Von: von Hoesslin, Volker [Volker.Hoesslin at swsn.de] Gesendet: Donnerstag, 21. Februar 2019 12:50 An: starlingx-discuss at lists.starlingx.io Betreff: [Starlingx-discuss] Pipe external multiple VLANs Hi, i have several external VLANs and i would like to bring them as tagged VLANs into a tenant network. I'm not sure how to implement this in StarlingX? Most of the changes to config files will be overwritten by puppet, do you have a hint for me how to do that? thx, volker -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Thu Feb 21 17:05:12 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Thu, 21 Feb 2019 17:05:12 +0000 Subject: [Starlingx-discuss] Nominate Don Penney as stx-upstream core Message-ID: +1 Bob From: "Bailey, Henry Albert (Al)" Date: Tuesday, February 19, 2019 at 10:00 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Nominate Don Penney as stx-upstream core I’d like to add Don Penney as a core reviewer for stx-upstream. Don has been contributing to the stx-upstream project since it was created and has been both a valuable and responsive reviewer and code author. I’d like confirmation (or objections) from the existing cores please… Al -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Thu Feb 21 18:19:04 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 21 Feb 2019 18:19:04 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> Message-ID: <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > > On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush iver.com> wrote: > > Hi, > > > > I see Spec as a high level design for a code that going to be > > developed, and to make sure it aligns with how community is going > > to use it and to make everybody aware of what is going to do, so > > others can chime in and say things that can address multiple needs > > and influence its design. Let's call this apple. > > > > Now I see the case of a code that has been developed before even > > the community existed, and now been presented to the community to > > fill a gap and improve productivity, no time to change the design > > and would be up to community to accept or reject it as is. A case > > of donation really, I call this one Orange. > > > > For Orange I think Spec is not the right word, we need a > > wiki/readme to see what it does, and how to use it. It is too late > > to produce a spec to influence the design. > > > > OpenStack Operators have a tools landing repository [1] that > didn't/doesn't have the same level of requirements the rest of the > OpenStack code typically does, so organizations could open source > internal. potentially untested, scripts but not have to necessarily > adhere to all of the usual requirements. Over time the code in that > repository could be improved and moved out once it made sense. > > I think it's worthwhile to have useful internal code open sourced, > and in some cases make it a bit easier to do so, and if the code/tool > gets used then start improving it following general standards. This > would require a new repository. > > Just a thought. :) > I really like the idea of having a new repository as a landing zone where things can be stabilize over time. When I started reviewing this tool I noticed that my comments were more focused on design (features that we might not need, restructure of cli arguments and so on) and I understand that fixing this is outside of the scope of sharing an internal tool. So, should be go in the path of creating a new repository? or can we use an "experimental" folder within stx-tools? What do you think about this? > Thanks, > Curtis > > [1]: https://git.openstack.org/cgit/openstack/osops-tools-contrib/tre > e/README.rst > > > My .02$, > > Dariush > > > > > > -----Original Message----- > > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel. > > com] > > Sent: February-20-19 6:21 PM > > To: Waheed, Numan ; starlingx-discuss at l > > ists.starlingx.io > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > Hi, > > > > I just reviewed the tool and I think it's a great tool and it will > > be really useful for the community. I just have one general > > question that I would like to extend to the community. Should this > > tool be supported by a spec? > > > > -Erich > > > > On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: > > > A Python-based installer for StarlingX has been submitted to > > stx- > > > tools repo. This automated installer has been used by Wind River > > > engineers on a continual basis for installing StarlingX on VBox > > > environment. This installer is not a new development. This has > > been > > > used for several years for quick install on VBox. It is being > > > delivered to help community for ease of installation of > > starlingx. > > > Feel free to use this installer and even add new features to > > serve the > > > community better. > > > > > > The installer is going in via following submission: > > > https://review.openstack.org/#/c/637958/ > > > > > > Numan. > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > uss > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > From serverascode at gmail.com Thu Feb 21 19:28:46 2019 From: serverascode at gmail.com (Curtis) Date: Thu, 21 Feb 2019 14:28:46 -0500 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> Message-ID: On Thu, Feb 21, 2019 at 1:19 PM Cordoba Malibran, Erich < erich.cordoba.malibran at intel.com> wrote: > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > > > > > On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > iver.com> wrote: > > > Hi, > > > > > > I see Spec as a high level design for a code that going to be > > > developed, and to make sure it aligns with how community is going > > > to use it and to make everybody aware of what is going to do, so > > > others can chime in and say things that can address multiple needs > > > and influence its design. Let's call this apple. > > > > > > Now I see the case of a code that has been developed before even > > > the community existed, and now been presented to the community to > > > fill a gap and improve productivity, no time to change the design > > > and would be up to community to accept or reject it as is. A case > > > of donation really, I call this one Orange. > > > > > > For Orange I think Spec is not the right word, we need a > > > wiki/readme to see what it does, and how to use it. It is too late > > > to produce a spec to influence the design. > > > > > > > OpenStack Operators have a tools landing repository [1] that > > didn't/doesn't have the same level of requirements the rest of the > > OpenStack code typically does, so organizations could open source > > internal. potentially untested, scripts but not have to necessarily > > adhere to all of the usual requirements. Over time the code in that > > repository could be improved and moved out once it made sense. > > > > I think it's worthwhile to have useful internal code open sourced, > > and in some cases make it a bit easier to do so, and if the code/tool > > gets used then start improving it following general standards. This > > would require a new repository. > > > > Just a thought. :) > > > > I really like the idea of having a new repository as a landing zone > where things can be stabilize over time. When I started reviewing this > tool I noticed that my comments were more focused on design (features > that we might not need, restructure of cli arguments and so on) and I > understand that fixing this is outside of the scope of sharing an > internal tool. > > So, should be go in the path of creating a new repository? or can we > use an "experimental" folder within stx-tools? > > What do you think about this? > I did put it on the agenda for the TSC meeting that happened earlier today and it was discussed. There were some reasons to have a separate repo, and some not to. It felt like, to me anyways, there were more reasons not to brought up in the meeting, but I'll let others discuss their own reasoning should they want to. :) As an OpenStack Operator who mostly deployed OpenStack and used custom tools to help manage it on Day 2, my perspective may be different than most in terms of sharing tooling that may not have all the Ts crossed and I's dotted in relation to what is now standard open source code quality expectations. Operators are a different sort. :) Thanks, Curtis > > > Thanks, > > Curtis > > > > [1]: https://git.openstack.org/cgit/openstack/osops-tools-contrib/tre > > e/README.rst > > > > > My .02$, > > > Dariush > > > > > > > > > -----Original Message----- > > > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel. > > > com] > > > Sent: February-20-19 6:21 PM > > > To: Waheed, Numan ; starlingx-discuss at l > > > ists.starlingx.io > > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > Hi, > > > > > > I just reviewed the tool and I think it's a great tool and it will > > > be really useful for the community. I just have one general > > > question that I would like to extend to the community. Should this > > > tool be supported by a spec? > > > > > > -Erich > > > > > > On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: > > > > A Python-based installer for StarlingX has been submitted to > > > stx- > > > > tools repo. This automated installer has been used by Wind River > > > > engineers on a continual basis for installing StarlingX on VBox > > > > environment. This installer is not a new development. This has > > > been > > > > used for several years for quick install on VBox. It is being > > > > delivered to help community for ease of installation of > > > starlingx. > > > > Feel free to use this installer and even add new features to > > > serve the > > > > community better. > > > > > > > > The installer is going in via following submission: > > > > https://review.openstack.org/#/c/637958/ > > > > > > > > Numan. > > > > _______________________________________________ > > > > Starlingx-discuss mailing list > > > > Starlingx-discuss at lists.starlingx.io > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc > > > uss > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > > s > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > > s > > > > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Feb 21 21:29:39 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 21 Feb 2019 21:29:39 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 20190221 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9CA9E@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-21 (link) Sanity Test is executed in a Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Thu Feb 21 22:34:30 2019 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Thu, 21 Feb 2019 22:34:30 +0000 Subject: [Starlingx-discuss] Minutes: StarlingX Networking Meeting - 02/21 Message-ID: <151EE31B9FCCA54397A757BC674650F0BA4BDA22@ALA-MBD.corp.ad.wrs.com> Meeting minutes/agenda are captured at: https://etherpad.openstack.org/p/stx-networking Team Meeting Agenda/Notes - Feb 20/2019 - Welcome back from the holidays Neutron Patch Upstreaming: - Network Segment Range - Gerrit Reviews: https://review.openstack.org/#/q/topic:bp/network-segment-range-management+(status:open+OR+status:merged) - Need to drive to get the code merged. Stein MS-3 fast approaching (Mar 8). How do we escalate the merge? - Ghada to send email to Miguel - From Matt: Discuss the original segment range validation as follow-up gerrit reviews - Not all the validation code was proposed to neutron - Segment Range overlap validation has been added. - Min/Max leverage functions in neutron-lib - Matt will have a look to see what else is missing. - The use of the plugin utils covers off the range validation from the original patch. - The attribute validation is not required since these parameters are no longer specified on a segment range basis. - No additional changes required. - Other Patches - Last update: 6-7 patches still on-going - Status updates made to the upstreaming spreadsheet Containerized OVS Integration - Code Merge Plan: Mar 15 - Created a story for the required openstack-helm per-host override enhancement : https://storyboard.openstack.org/#!/story/2005059 - Chengli has made the required code changes in a private git. Testing was successful. - Tried AIO-simplex with OVS container and OVS-DPDK on the host - Posted STX code review for the required stx-config changes: https://review.openstack.org/#/c/633924/ - Next step is to test the other configurations -- AIO-duplex and multi-node - Need to test inter-node traffic between VMs to ensure the physical interface is setup properly - Ghada to ask Bob Church on process to push changes to the openstack-helm project OVS process monitoring and alarming - Code Merge Plan: Mar 22 - Not started yet as Chenjie is developing TCs for the openvswitch patckage upversion OVS-DPDK Firewall - Code Merge Plan: Mar 22 - 80% of functional testing complete; no issues found. Kailun needs to check on the performance testing status. openvswitch package Upversion - Code Merge Plan: Mar 22 - v2.11.0 is not posted on github yet; monitoring: https://github.com/openvswitch/ovs/releases - Will update the plan accordingly once the release is available - Chenjie is defining the TCs for basic functional testing and also working w/ Elio (test team) on defining the TCs for feature functional testing. - Ghada requested that the selected TCs be shared with the networking team TSN support in STX - A TSN related submission is at https://www.openstack.org/summit/denver-2019/summit-schedule/events/23389/precision-time-protocol-ptp-on-starlingx - PTP is already supported in StarlingX. The code is already merged: https://review.openstack.org/#/q/status:merged+project:openstack/stx-config+branch:master+topic:ptp - What's the plan to support TSN in STX? - TSN is treated separately from PTP in STX - For TSN, the plan is to just confirm that passthru of the I210 NICs to the guest is working in Stein - The nova support was done by the community under a re-factoring/cleanup PCI activity. Not sure about the exact commit/review. - This will need to be verified after cut-over to Stein Regards, Ghada From sgw at linux.intel.com Thu Feb 21 23:18:46 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 21 Feb 2019 15:18:46 -0800 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> Message-ID: On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: >> >> >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > iver.com> wrote: >>> Hi, >>> >>> I see Spec as a high level design for a code that going to be >>> developed, and to make sure it aligns with how community is going >>> to use it and to make everybody aware of what is going to do, so >>> others can chime in and say things that can address multiple needs >>> and influence its design. Let's call this apple. >>> >>> Now I see the case of a code that has been developed before even >>> the community existed, and now been presented to the community to >>> fill a gap and improve productivity, no time to change the design >>> and would be up to community to accept or reject it as is. A case >>> of donation really, I call this one Orange. >>> >>> For Orange I think Spec is not the right word, we need a >>> wiki/readme to see what it does, and how to use it. It is too late >>> to produce a spec to influence the design. >>> >> >> OpenStack Operators have a tools landing repository [1] that >> didn't/doesn't have the same level of requirements the rest of the >> OpenStack code typically does, so organizations could open source >> internal. potentially untested, scripts but not have to necessarily >> adhere to all of the usual requirements. Over time the code in that >> repository could be improved and moved out once it made sense. >> >> I think it's worthwhile to have useful internal code open sourced, >> and in some cases make it a bit easier to do so, and if the code/tool >> gets used then start improving it following general standards. This >> would require a new repository. >> >> Just a thought. :) >> > > I really like the idea of having a new repository as a landing zone > where things can be stabilize over time. When I started reviewing this > tool I noticed that my comments were more focused on design (features > that we might not need, restructure of cli arguments and so on) and I > understand that fixing this is outside of the scope of sharing an > internal tool. > > So, should be go in the path of creating a new repository? or can we > use an "experimental" folder within stx-tools? > > What do you think about this? > I think that this can land in the stx-tools directory along with the other deployment scripts. As was pointed out in the meeting this morning, this code has been in use within WindRiver for a while now and they are making it available to the community. I think that the initial PR needed to have a better commit message explaining this and a little more thought put into the request before it got reviewed, such as removing the .pyc files, licensing, documentation, the first two where show stopper for me, but easily fixed, documentation could be added later. Sau! >> Thanks, >> Curtis >> >> [1]: https://git.openstack.org/cgit/openstack/osops-tools-contrib/tre >> e/README.rst >> >>> My .02$, >>> Dariush >>> >>> >>> -----Original Message----- >>> From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel. >>> com] >>> Sent: February-20-19 6:21 PM >>> To: Waheed, Numan ; starlingx-discuss at l >>> ists.starlingx.io >>> Subject: Re: [Starlingx-discuss] Python Based VBox Installer >>> >>> Hi, >>> >>> I just reviewed the tool and I think it's a great tool and it will >>> be really useful for the community. I just have one general >>> question that I would like to extend to the community. Should this >>> tool be supported by a spec? >>> >>> -Erich >>> >>> On Wed, 2019-02-20 at 21:21 +0000, Waheed, Numan wrote: >>>> A Python-based installer for StarlingX has been submitted to >>> stx- >>>> tools repo. This automated installer has been used by Wind River >>>> engineers on a continual basis for installing StarlingX on VBox >>>> environment. This installer is not a new development. This has >>> been >>>> used for several years for quick install on VBox. It is being >>>> delivered to help community for ease of installation of >>> starlingx. >>>> Feel free to use this installer and even add new features to >>> serve the >>>> community better. >>>> >>>> The installer is going in via following submission: >>>> https://review.openstack.org/#/c/637958/ >>>> >>>> Numan. >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc >>> uss >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus >>> s >> >> > _______________________________________________ > 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 Fri Feb 22 00:08:56 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 22 Feb 2019 00:08:56 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190221 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9CB23@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-21 (link) Sanity Test is executed in a Containers - Bare Metal Environment Status: GREEN Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Status: GREEN Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 43 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From yong.hu at intel.com Fri Feb 22 01:43:09 2019 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 22 Feb 2019 01:43:09 +0000 Subject: [Starlingx-discuss] Contributor Survey In-Reply-To: References: <586E8B730EA0DA4A9D6A80A10E486BC0A0749D@ALA-MBD.corp.ad.wrs.com> <834BB696-A390-4E15-9874-52141B49335F@gmail.com> Message-ID: <316CBC07-771E-4975-AC02-8B2BCA29B87D@intel.com> Hi Glenn and Ildiko, I like this question the most: "- do they even know about StarlingX?!!", because this is the very beginning of everything. ☺ While, before jumping to the hands-on (downloading and trying out further with it), I might hold on for a second and think over why I am interested in it, like: - how can StarlingX benefit my business or serve technical purpose? Regards, -Yong, On 21/02/2019, 7:22 AM, "Seiler, Glenn" wrote: Ildiko, team I think there are logical steps in the progression of someone using a project like StarlingX. First is just to download it, (or build it) and try to run some sample VMs or containers. Second would be to start a PoC or evaluation and maybe contribute to the project. Only after the first two steps would anyone start to consider deployment. So I think asking about deployment will not get us where we want to be. I think we focus on the first step, almost exclusively. - do they even know about StarlingX!! -have they downloaded it? Do they plan to? -have they had any problems... -what can we do to make it easier for them... I think that is step 1. We can agree to skip that step and go straight to what they want to deploy on the edge, but those are really two very different surveys. If we want to focus on what they deploy at the edge, we have to acknowledge they very well may not even be deploying StarlingX....after all it is still very young and companies can take many months or years before they deploy. -glenn -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Wednesday, February 20, 2019 11:26 AM To: Zvonar, Bill Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Contributor Survey Hi Bill, Thank you for adding the contributor focused questions. On the today’s call we’ve discussed the base idea being to have a high level user survey type of questionnaire that focuses on understanding the use case and motivation for companies who are planning to deploy or use an edge platform and ask their plans and current stage with StarlingX. Our motivation is to start building and growing the ecosystem around StarlingX and understand the market a little better as well. When it comes to contributions we listed two options. We can either add a question or two to the above initial survey to see if a certain responder is also interested in contributing or we can run it as a separate survey. If we can make it happen on the tooling side we could also consider showing deeper dive questions if someone says they are interested in contributing and not displaying those questions if that’s not a primary interest for them at this point. In my view if we run a contribution focused survey we need to set the scope and decide what challenges we would like to get an answer to when we put together the questions. Like whether we would like to find roadblocks or bottlenecks that make it harder for people to join or learn which area they are interested in and if the latter what the next step is once we have the results and whether the survey is the best way to reach out to new contributors who are just getting started to help them. What do others think or would be interested in learning about? If you would like to participate in drafting the survey(s) please check out the etherpad and add comments and ideas! Thanks, Ildikó > On 2019. Feb 20., at 18:50, Zvonar, Bill wrote: > > Hi Ildiko, > > As discussed in the Community Marketing Planning call today, I’ve placed a draft of a Contributor Survey up on [0]. > > It’s not quite the same as the survey you started, it’s more directed at individuals who have already expressed an interest in contributing – a survey like this will help them understand how & where they can do so. > > It’s a draft – comments welcome from the community. > > Bill… > > [0] https://etherpad.openstack.org/p/stx-user-survey > > > _______________________________________________ > 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 yong.hu at intel.com Fri Feb 22 01:51:52 2019 From: yong.hu at intel.com (Hu, Yong) Date: Fri, 22 Feb 2019 01:51:52 +0000 Subject: [Starlingx-discuss] Duplex Config: Controller-0 stays in degraded state In-Reply-To: References: Message-ID: <02DDD545-AB85-4934-8751-AA278A2D434A@intel.com> Marcel, This is expected since your system is duplex while you are only having one controller (controller-0) right now. Let’s see if controller-0 will come to availability state, *after* you’ve done with the second controller. Regards, Yong From: "Schaible, MarcelX" Date: Thursday, 21 February 2019 at 3:02 AM To: "starlingx-discuss at lists.starlingx.io" Subject: [Starlingx-discuss] Duplex Config: Controller-0 stays in degraded state Hi *, we are using the 20190109T162801Z iso image on bare metal. The controller-0 stays in degraded state and we are running out of ideas what the root cause of this problem could be. [root at controller-0 etc(keystone_admin)]# system host-list +----+--------------+-------------+----------------+-------------+--------------+ | id | hostname | personality | administrative | operational | availability | +----+--------------+-------------+----------------+-------------+--------------+ | 1 | controller-0 | controller | unlocked | enabled | degraded | +----+--------------+-------------+----------------+-------------+--------------+ The output of python /usr/share/openvswitch/scripts/dpdk-devbind.py –status: Network devices using DPDK-compatible driver ============================================ 0000:09:15.1 '82599 Ethernet Controller Virtual Function 10ed' drv=vfio-pci unused= Network devices using kernel driver =================================== 0000:03:00.0 'Ethernet Connection X552 10 GbE Backplane 15ab' if=enp3s0f0 drv=ixgbe unused=vfio-pci 0000:03:00.1 'Ethernet Connection X552 10 GbE Backplane 15ab' if=enp3s0f1 drv=ixgbe unused=vfio-pci 0000:07:00.0 'I350 Gigabit Network Connection 1521' if=ens1f0 drv=igb unused=vfio-pci 0000:07:00.1 'I350 Gigabit Network Connection 1521' if=ens1f1 drv=igb unused=vfio-pci 0000:07:00.3 'I350 Gigabit Network Connection 1521' if=ens1f3 drv=igb unused=vfio-pci 0000:09:14.6 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s20f6 drv=ixgbevf unused=vfio-pci 0000:09:14.7 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s20f7 drv=ixgbevf unused=vfio-pci *Active* 0000:09:15.0 '82599 Ethernet Controller Virtual Function 10ed' if=enp9s21f0 drv=ixgbevf unused=vfio-pci Other Network devices ===================== 0000:07:00.2 'I350 Gigabit Network Connection 1521' unused=vfio-pci 0000:26:00.0 'Device 9797' unused=vfio-pci Crypto devices using DPDK-compatible driver =========================================== Crypto devices using kernel driver ================================== Other Crypto devices ==================== Eventdev devices using DPDK-compatible driver ============================================= Eventdev devices using kernel driver ==================================== Other Eventdev devices ====================== Mempool devices using DPDK-compatible driver ============================================ Mempool devices using kernel driver =================================== Other Mempool devices ===================== And ovs-vsctl show gives: 5047dd61-faa2-448c-be2c-f4ef2f5c9501 Manager "ptcp:6639:127.0.0.1" is_connected: true Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "int-br-phy0" Interface "int-br-phy0" type: patch options: {peer="phy-br-phy0"} Port br-int Interface br-int type: internal Bridge "br-phy0" Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port "eth0" Interface "eth0" type: dpdk options: {dpdk-devargs="0000:09:15.1", n_rxq="2"} error: "Error attaching device '0000:09:15.1' to DPDK" Port "phy-br-phy0" Interface "phy-br-phy0" type: patch options: {peer="int-br-phy0"} Port "br-phy0" Interface "br-phy0" type: internal Port "lldp55d31ed0-33" Interface "lldp55d31ed0-33" type: internal ovs_version: "2.9.0" Can anyone recommend an iso image for duplex on bare metal? Thanks Marcel Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid Chairperson of the Supervisory Board: Nicole Lau Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From zhipengs.liu at intel.com Fri Feb 22 03:24:11 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Fri, 22 Feb 2019 03:24:11 +0000 Subject: [Starlingx-discuss] PCI Interrupt affinity task Message-ID: <93814834B4855241994F290E959305C753042E86@SHSMSX104.ccr.corp.intel.com> Hi all Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600) So far I have finished coding, basic deployment test and function test. Now, I'm preparing for uploading my patch for code review. However, I need to decide where to put code folder. >From my point, there are two options below. 1) stx-integ/utilities/nova-utils/pci-affinity-agent 2) stx-config/sysinv/pci-affinity-agent (I put code here currently) I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova. We can reuse nova-utils package with additional RPM for pci-affinity-agent Any comment from you? Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From kyle.oh95 at gmail.com Fri Feb 22 06:54:27 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Fri, 22 Feb 2019 15:54:27 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Message-ID: Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, [image: image.png] And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 27357 bytes Desc: not available URL: From austin.sun at intel.com Fri Feb 22 08:02:04 2019 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 22 Feb 2019 08:02:04 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Jaewook: 1. Could you share the hw info for controller-1 ? and check bios setting ? is it using UEFI ? VTx/Iommu enable or not ? 2. Could you try access controller-1 and press Alt+F10 to see any log if the system is bare metal ? Thanks. BR Austin Sun. From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Friday, February 22, 2019 2:54 PM To: starlingx-discuss Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From chenjie.xu at intel.com Fri Feb 22 09:00:13 2019 From: chenjie.xu at intel.com (Xu, Chenjie) Date: Fri, 22 Feb 2019 09:00:13 +0000 Subject: [Starlingx-discuss] OVS-DPDK Upgrade Testing Message-ID: Hi all, Elio, Huifeng and Chenjie has discussed OVS-DPDK Upgrade Testing on a meeting. Main contents of the meeting are as following: 1. We agreed to pick up the test cases based on selection criteria. 2. Still need Elio to review the selection criteria: Test OVS-DPDK related aspects: Structure: Single node & multiple node Network type: vlan/vxlan Protocol: IPv4/IPv6/TCP/UDP/ICMP Feature: Security group/QOS/MTU 3. Chenjie has picked up some test cases for Basic Functional Testing based on selection criteria, and the test cases has been attached. Need Elio to review and provide the comments, steps, and scripts. 4. Chenjie will help to address the opens from Elio's Feature Test Design. Best Regards, Xu, Chenjie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Basic_Functional_Testing.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12836 bytes Desc: Basic_Functional_Testing.xlsx URL: From ildiko.vancsa at gmail.com Fri Feb 22 09:09:03 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 22 Feb 2019 10:09:03 +0100 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram Message-ID: Hi StarlingX Community, We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? Thanks and Best Regards, Ildikó From kyle.oh95 at gmail.com Fri Feb 22 10:09:45 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Fri, 22 Feb 2019 19:09:45 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Austin, 1. - Here is the spec Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz RAM : 32GB (Is this the problem? I already saw for the controller 64GB RAM is needed, but I'm not sure, cause the installation was just stuck literally, SSD : 500GB SuperMicro - Bios Setting: I enabled and disabled as the instruction said. And at first try, I didn't used UEFI, after failure, I changed it into UEFI, but the result was same. I enabled VTx/Iommu enable or not ? 2. I used bare metal one.. however when I pressed the buttons, nothing happened. And the controller-1 is just stopped as I said before. Thank you for helping me :) Best Regards, Jaewook. 2019년 2월 22일 (금) 오후 5:02, Sun, Austin 님이 작성: > Hi Jaewook: > > > > 1. Could you share the hw info for controller-1 ? and check bios > setting ? is it using UEFI ? VTx/Iommu enable or not ? > > 2. Could you try access controller-1 and press Alt+F10 to see any log > if the system is bare metal ? > > > > > > Thanks. > > BR > Austin Sun. > > > > > > *From:* Jaewook Oh [mailto:kyle.oh95 at gmail.com] > *Sent:* Friday, February 22, 2019 2:54 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] Duplex PXE Booting seems failed > > > > Hello StarlingX Team, > > > > I finally solved the horizon error, the port number was different. > > I don't know why the port was changed, but anyway the port number was > 8080, not 80. > > > > But I'm now facing new obstacles, Duplex PXE Booting. > > > > I succeed to connect PXE mode, but no more process.. > > > > In Controller-0, I can find below result, > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Fri Feb 22 13:12:57 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Fri, 22 Feb 2019 13:12:57 +0000 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: References: Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> Ildikó, I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. Bart -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: February 22, 2019 4:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Feedback needed on updated overview diagram Hi StarlingX Community, We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? Thanks and Best Regards, Ildikó _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From kennelson11 at gmail.com Fri Feb 22 17:24:27 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 22 Feb 2019 09:24:27 -0800 Subject: [Starlingx-discuss] [all] Forum Submissions are Open! Message-ID: Hello Everyone! We are now accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas through the Summit CFP tool [3] through March 8th. Don't forget to put your brainstorming etherpad up on the Denver Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Feb 22nd | Formal topic submission tool opens: https://www.openstack.org/summit/denver-2019/call-for-presentations. March 8th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. March 22nd | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. March 29th | Scheduling committee final meeting April 5th | Forum schedule final April 29th-May 1st | Forum Time! If you have questions or concerns, please reach out to speakersupport at openstack.org. Cheers, Kendall Nelson (diablo_rojo) [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/denver-2019/ [3] https://www.openstack.org/summit/denver-2019/call-for-presentations [4] https://wiki.openstack.org/wiki/Forum/Denver2019 -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Fri Feb 22 18:58:36 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Fri, 22 Feb 2019 18:58:36 +0000 Subject: [Starlingx-discuss] Regression test cases for networking testing Message-ID: <1466AF2176E6F040BD63860D0A241BBD46C8C793@FMSMSX109.amr.corp.intel.com> Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Regression tests Networking .xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 22600 bytes Desc: Regression tests Networking .xlsx URL: From Numan.Waheed at windriver.com Fri Feb 22 19:17:41 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Fri, 22 Feb 2019 19:17:41 +0000 Subject: [Starlingx-discuss] Regression test cases for networking testing In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46C8C793@FMSMSX109.amr.corp.intel.com> References: <1466AF2176E6F040BD63860D0A241BBD46C8C793@FMSMSX109.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE48277D61@ALA-MBD.corp.ad.wrs.com> Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio Sent: February-22-19 1:59 PM To: Xu, Chenjie ; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada ; Khalil, Ghada ; Waheed, Numan ; Zhao, Forrest Subject: Regression test cases for networking testing Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [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: -------------- next part -------------- A non-text attachment was scrubbed... Name: Regression tests Networking .xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 22600 bytes Desc: Regression tests Networking .xlsx URL: From Jeff.Gowan at windriver.com Fri Feb 22 20:42:03 2019 From: Jeff.Gowan at windriver.com (Gowan, Jeff) Date: Fri, 22 Feb 2019 20:42:03 +0000 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> Message-ID: <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> I agree with Bart. -Jeff On 2/22/19, 5:14 AM, "Wensley, Barton" wrote: Ildikó, I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. Bart -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: February 22, 2019 4:09 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Feedback needed on updated overview diagram Hi StarlingX Community, We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? Thanks and Best Regards, Ildikó _______________________________________________ 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 scott.little at windriver.com Fri Feb 22 21:50:29 2019 From: scott.little at windriver.com (Scott Little) Date: Fri, 22 Feb 2019 16:50:29 -0500 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git Message-ID: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> The idea was floated several weeks ago that we should place the jenkins scripts used by starlingx.cengn.ca builds under git revision control, and publish them somewhere. If we are all agreed this would be a good thing, I would like to move forward with that proposal. Where should we publish it,  github or openstack? If openstack, I'll need some pointers on how to set up the new git. Thanks Scott From juan.carlos.alonso at intel.com Fri Feb 22 23:26:54 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 22 Feb 2019 23:26:54 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190222 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9CD6C@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-22 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Multinode Local Storage Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc In order to debug and discard, proceed to update, override and redeploy the application. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 43 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Fri Feb 22 23:26:59 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Fri, 22 Feb 2019 23:26:59 +0000 Subject: [Starlingx-discuss] Sanity Test - ISO 2019022 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9CD78@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-22 (link) Status: GREEN =========================================== Sanity Test is executed in a Bare Metal Environment Simplex Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 43 TCs PASS ] =========================================== Sanity Test is executed in a Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 42 TCs [PASS] TOTAL: [ 47 TCs PASS ] Duplex Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Controller Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] Multinode Dedicated Storage Setup 04 TCs [PASS] Provisioning 01 TCs [PASS] Sanity 45 TCs [PASS] TOTAL: [ 50 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Sun Feb 24 08:31:37 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Feb 2019 03:31:37 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 163 - Failure! Message-ID: <1228309591.2.1550997115670.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 163 Status: Failure Timestamp: 20190224T062338Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190224T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190224T060000Z DOCKER_BUILD_ID: jenkins-master-20190224T060000Z-builder MY_REPO: /localdisk/designer/jenkins/master/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190224T060000Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190224T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Sun Feb 24 08:32:01 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Sun, 24 Feb 2019 03:32:01 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 149 - Failure! Message-ID: <2146368385.5.1550997122435.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 149 Status: Failure Timestamp: 20190224T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190224T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From build.starlingx at gmail.com Mon Feb 25 06:15:31 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Feb 2019 01:15:31 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_DL_container_setup - Build # 191 - Failure! Message-ID: <525968478.8.1551075333028.JavaMail.javamailuser@localhost> Project: STX_DL_container_setup Build #: 191 Status: Failure Timestamp: 20190225T060032Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190225T060000Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master/20190225T060000Z DOCKER_DL_ID: jenkins-master-20190225T060000Z-downloader PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190225T060000Z/logs DOCKER_DL_TAG: master-20190225T060000Z-downloader-image PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/20190225T060000Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/master From build.starlingx at gmail.com Mon Feb 25 06:15:36 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Feb 2019 01:15:36 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_master_pike - Build # 150 - Still Failing! In-Reply-To: <626617056.3.1550997118636.JavaMail.javamailuser@localhost> References: <626617056.3.1550997118636.JavaMail.javamailuser@localhost> Message-ID: <1561967748.11.1551075336960.JavaMail.javamailuser@localhost> Project: STX_build_master_pike Build #: 150 Status: Still Failing Timestamp: 20190225T060000Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190225T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From shuicheng.lin at intel.com Mon Feb 25 07:58:02 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Mon, 25 Feb 2019 07:58:02 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric ; Liu, Tao ; Al.Bailey at windriver.com Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Mon Feb 25 13:10:01 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Mon, 25 Feb 2019 13:10:01 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric ; Liu, Tao ; Al.Bailey at windriver.com Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Mon Feb 25 14:23:05 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Mon, 25 Feb 2019 14:23:05 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric ; Liu, Tao ; Al.Bailey at windriver.com Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Mon Feb 25 15:41:03 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Mon, 25 Feb 2019 16:41:03 +0100 (CET) Subject: [Starlingx-discuss] cinder-volumes and nova-local on same disk throws an error? Message-ID: <1278310074.296468.1551109263518@communicator.strato.com> Hi, when I try to setup our duplex config with the cinder-volumes and nova-local on the same nvm drive I'll get the following error: [root at controller-0 ~(keystone_admin)]# system host-pv-add controller-0 nova-local d79a7560-d92a-4544-9788-1caab390cc66 Cannot use this partition. A partition (/dev/disk/by-path/pci-0000:0b:00.0-nvme-1-part1) on this disk is already in use by cinder-volumes. [root at controller-0 ~(keystone_admin)]# system host-pv-list controller-0 +--------------------------------------+----------------+--------------------------------------+--------------------------+-------------------------------------------------+--------------------+-----------+----------------+--------------------------------------+ | uuid | lvm_pv_name | disk_or_part_uuid | disk_or_part_device_node | disk_or_part_device_path | pv_state | pv_type | lvm_vg_name | ihost_uuid | +--------------------------------------+----------------+--------------------------------------+--------------------------+-------------------------------------------------+--------------------+-----------+----------------+--------------------------------------+ | ccbf1fe5-1d30-44f4-be82-897a7524c63d | /dev/nvme1n1p1 | 815a4ba4-7f76-4f98-b795-a61ccf64bc94 | /dev/nvme1n1p1 | /dev/disk/by-path/pci-0000:0b:00.0-nvme-1-part1 | adding (on unlock) | partition | cinder-volumes | 3e24324b-1c90-419a-b4bc-1c2de0b45048 | | feb603ce-f95f-44fc-bbef-1170a56f45e2 | /dev/nvme0n1p4 | 70cbe49b-eefb-40fb-a799-232463fe5ddf | /dev/nvme0n1p4 | /dev/disk/by-path/pci-0000:0a:00.0-nvme-1-part4 | provisioned | partition | cgts-vg | 3e24324b-1c90-419a-b4bc-1c2de0b45048 | +--------------------------------------+----------------+--------------------------------------+--------------------------+-------------------------------------------------+--------------------+-----------+----------------+--------------------------------------+ Is this intendend or is there something other wrong with my config? Thanx Marcel From Don.Penney at windriver.com Mon Feb 25 15:49:21 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 25 Feb 2019 15:49:21 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> > -----Original Message----- > From: Saul Wold [mailto:sgw at linux.intel.com] > Sent: Thursday, February 21, 2019 6:19 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > >> > >> > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush >> iver.com> wrote: > >>> Hi, > >>> > >>> I see Spec as a high level design for a code that going to be > >>> developed, and to make sure it aligns with how community is going > >>> to use it and to make everybody aware of what is going to do, so > >>> others can chime in and say things that can address multiple needs > >>> and influence its design. Let's call this apple. > >>> > >>> Now I see the case of a code that has been developed before even > >>> the community existed, and now been presented to the community to > >>> fill a gap and improve productivity, no time to change the design > >>> and would be up to community to accept or reject it as is. A case > >>> of donation really, I call this one Orange. > >>> > >>> For Orange I think Spec is not the right word, we need a > >>> wiki/readme to see what it does, and how to use it. It is too late > >>> to produce a spec to influence the design. > >>> > >> > >> OpenStack Operators have a tools landing repository [1] that > >> didn't/doesn't have the same level of requirements the rest of the > >> OpenStack code typically does, so organizations could open source > >> internal. potentially untested, scripts but not have to necessarily > >> adhere to all of the usual requirements. Over time the code in that > >> repository could be improved and moved out once it made sense. > >> > >> I think it's worthwhile to have useful internal code open sourced, > >> and in some cases make it a bit easier to do so, and if the code/tool > >> gets used then start improving it following general standards. This > >> would require a new repository. > >> > >> Just a thought. :) > >> > > > > I really like the idea of having a new repository as a landing zone > > where things can be stabilize over time. When I started reviewing this > > tool I noticed that my comments were more focused on design (features > > that we might not need, restructure of cli arguments and so on) and I > > understand that fixing this is outside of the scope of sharing an > > internal tool. > > > > So, should be go in the path of creating a new repository? or can we > > use an "experimental" folder within stx-tools? > > > > What do you think about this? > > > I think that this can land in the stx-tools directory along with the > other deployment scripts. As was pointed out in the meeting this > morning, this code has been in use within WindRiver for a while now and > they are making it available to the community. > > I think that the initial PR needed to have a better commit message > explaining this and a little more thought put into the request before it > got reviewed, such as removing the .pyc files, licensing, documentation, > the first two where show stopper for me, but easily fixed, documentation > could be added later. > > Sau! > Things like the inadvertent inclusion of pyc files (which were already noted in multiple comments in the review) and missing license identifiers seem to be minor and easily correctable mistakes, and maybe not completely unexpected for a “new contributor”. As well, I had also noted in a review comment that this was a long-existing tool that was being published, referencing the email from Numan and asking for the commit message to be updated to explain this. As well, note that this was an optional productivity aid. It does not impact the build, it does not impact any software. It is a tool to help people launch StarlingX in a VirtualBox environment, to aid them in installing and configuring the system. Nobody is required to use it. With that said, the review had been given two -2 votes from cores. As I understand it, this is not a minor thing. From the openstack guidelines, a -2 “is to indicate to the submitter that any further time they spend on the change will almost certainly be wasted.” Having two -2 votes on the update is very significant, thus the decision to abandon the review. The openstack guidelines describing -1 and -2 votes seems pretty clear here: https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#code-review-minus-2 Cheers, Don. From serverascode at gmail.com Mon Feb 25 16:11:32 2019 From: serverascode at gmail.com (Curtis) Date: Mon, 25 Feb 2019 11:11:32 -0500 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> Message-ID: On Mon, Feb 25, 2019 at 10:51 AM Penney, Don wrote: > > > > -----Original Message----- > > From: Saul Wold [mailto:sgw at linux.intel.com] > > Sent: Thursday, February 21, 2019 6:19 PM > > To: starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > >> > > >> > > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > >> iver.com> wrote: > > >>> Hi, > > >>> > > >>> I see Spec as a high level design for a code that going to be > > >>> developed, and to make sure it aligns with how community is going > > >>> to use it and to make everybody aware of what is going to do, so > > >>> others can chime in and say things that can address multiple needs > > >>> and influence its design. Let's call this apple. > > >>> > > >>> Now I see the case of a code that has been developed before even > > >>> the community existed, and now been presented to the community to > > >>> fill a gap and improve productivity, no time to change the design > > >>> and would be up to community to accept or reject it as is. A case > > >>> of donation really, I call this one Orange. > > >>> > > >>> For Orange I think Spec is not the right word, we need a > > >>> wiki/readme to see what it does, and how to use it. It is too late > > >>> to produce a spec to influence the design. > > >>> > > >> > > >> OpenStack Operators have a tools landing repository [1] that > > >> didn't/doesn't have the same level of requirements the rest of the > > >> OpenStack code typically does, so organizations could open source > > >> internal. potentially untested, scripts but not have to necessarily > > >> adhere to all of the usual requirements. Over time the code in that > > >> repository could be improved and moved out once it made sense. > > >> > > >> I think it's worthwhile to have useful internal code open sourced, > > >> and in some cases make it a bit easier to do so, and if the code/tool > > >> gets used then start improving it following general standards. This > > >> would require a new repository. > > >> > > >> Just a thought. :) > > >> > > > > > > I really like the idea of having a new repository as a landing zone > > > where things can be stabilize over time. When I started reviewing this > > > tool I noticed that my comments were more focused on design (features > > > that we might not need, restructure of cli arguments and so on) and I > > > understand that fixing this is outside of the scope of sharing an > > > internal tool. > > > > > > So, should be go in the path of creating a new repository? or can we > > > use an "experimental" folder within stx-tools? > > > > > > What do you think about this? > > > > > I think that this can land in the stx-tools directory along with the > > other deployment scripts. As was pointed out in the meeting this > > morning, this code has been in use within WindRiver for a while now and > > they are making it available to the community. > > > > I think that the initial PR needed to have a better commit message > > explaining this and a little more thought put into the request before it > > got reviewed, such as removing the .pyc files, licensing, documentation, > > the first two where show stopper for me, but easily fixed, documentation > > could be added later. > > > > Sau! > > > > Things like the inadvertent inclusion of pyc files (which were already > noted in multiple comments in the review) and missing license identifiers > seem to be minor and easily correctable mistakes, and maybe not completely > unexpected for a “new contributor”. As well, I had also noted in a review > comment that this was a long-existing tool that was being published, > referencing the email from Numan and asking for the commit message to be > updated to explain this. > > As well, note that this was an optional productivity aid. It does not > impact the build, it does not impact any software. It is a tool to help > people launch StarlingX in a VirtualBox environment, to aid them in > installing and configuring the system. Nobody is required to use it. > > With that said, the review had been given two -2 votes from cores. As I > understand it, this is not a minor thing. From the openstack guidelines, a > -2 “is to indicate to the submitter that any further time they spend on the > change will almost certainly be wasted.” Having two -2 votes on the update > is very significant, thus the decision to abandon the review. The openstack > guidelines describing -1 and -2 votes seems pretty clear here: > > https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#code-review-minus-2 > > Sounds like we need to come to a consensus as to when a -2 is appropriate. I personally don't think a -2 is appropriate for a first contribution, regardless of circumstances. Obviously we can't commit .pyc files and need licensing, but I definitely would prefer not to see -2s in this situation. I think this code is important and we need to get this back on track. This is a good "teachable moment" maybe for all sides? :) Thanks, Curtis > Cheers, > Don. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Mon Feb 25 16:51:21 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 25 Feb 2019 16:51:21 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> Message-ID: <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> On Mon, 2019-02-25 at 11:11 -0500, Curtis wrote: > On Mon, Feb 25, 2019 at 10:51 AM Penney, Don m> wrote: > > > > > -----Original Message----- > > > From: Saul Wold [mailto:sgw at linux.intel.com] > > > Sent: Thursday, February 21, 2019 6:19 PM > > > To: starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > > > > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > > >> > > > >> > > > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > i at windr > > > >> iver.com> wrote: > > > >>> Hi, > > > >>> > > > >>> I see Spec as a high level design for a code that going to be > > > >>> developed, and to make sure it aligns with how community is > > going > > > >>> to use it and to make everybody aware of what is going to do, > > so > > > >>> others can chime in and say things that can address multiple > > needs > > > >>> and influence its design. Let's call this apple. > > > >>> > > > >>> Now I see the case of a code that has been developed before > > even > > > >>> the community existed, and now been presented to the > > community to > > > >>> fill a gap and improve productivity, no time to change the > > design > > > >>> and would be up to community to accept or reject it as is. A > > case > > > >>> of donation really, I call this one Orange. > > > >>> > > > >>> For Orange I think Spec is not the right word, we need a > > > >>> wiki/readme to see what it does, and how to use it. It is too > > late > > > >>> to produce a spec to influence the design. > > > >>> > > > >> > > > >> OpenStack Operators have a tools landing repository [1] that > > > >> didn't/doesn't have the same level of requirements the rest of > > the > > > >> OpenStack code typically does, so organizations could open > > source > > > >> internal. potentially untested, scripts but not have to > > necessarily > > > >> adhere to all of the usual requirements. Over time the code in > > that > > > >> repository could be improved and moved out once it made sense. > > > >> > > > >> I think it's worthwhile to have useful internal code open > > sourced, > > > >> and in some cases make it a bit easier to do so, and if the > > code/tool > > > >> gets used then start improving it following general standards. > > This > > > >> would require a new repository. > > > >> > > > >> Just a thought. :) > > > >> > > > > > > > > I really like the idea of having a new repository as a landing > > zone > > > > where things can be stabilize over time. When I started > > reviewing this > > > > tool I noticed that my comments were more focused on design > > (features > > > > that we might not need, restructure of cli arguments and so on) > > and I > > > > understand that fixing this is outside of the scope of sharing > > an > > > > internal tool. > > > > > > > > So, should be go in the path of creating a new repository? or > > can we > > > > use an "experimental" folder within stx-tools? > > > > > > > > What do you think about this? > > > > > > > I think that this can land in the stx-tools directory along with > > the > > > other deployment scripts. As was pointed out in the meeting this > > > morning, this code has been in use within WindRiver for a while > > now and > > > they are making it available to the community. > > > > > > I think that the initial PR needed to have a better commit > > message > > > explaining this and a little more thought put into the request > > before it > > > got reviewed, such as removing the .pyc files, licensing, > > documentation, > > > the first two where show stopper for me, but easily fixed, > > documentation > > > could be added later. > > > > > > Sau! > > > > > > > Things like the inadvertent inclusion of pyc files (which were > > already noted in multiple comments in the review) and missing > > license identifiers seem to be minor and easily correctable > > mistakes, and maybe not completely unexpected for a “new > > contributor”. As well, I had also noted in a review comment that > > this was a long-existing tool that was being published, referencing > > the email from Numan and asking for the commit message to be > > updated to explain this. > > > > As well, note that this was an optional productivity aid. It does > > not impact the build, it does not impact any software. It is a tool > > to help people launch StarlingX in a VirtualBox environment, to aid > > them in installing and configuring the system. Nobody is required > > to use it. > > > > With that said, the review had been given two -2 votes from cores. > > As I understand it, this is not a minor thing. From the openstack > > guidelines, a -2 “is to indicate to the submitter that any further > > time they spend on the change will almost certainly be wasted.” > > Having two -2 votes on the update is very significant, thus the > > decision to abandon the review. The openstack guidelines describing > > -1 and -2 votes seems pretty clear here: > > https://docs.openstack.org/project-team-guide/review-the-openstack- > > way.html#code-review-minus-2 > > > > Sounds like we need to come to a consensus as to when a -2 is > appropriate. I personally don't think a -2 is appropriate for a first > contribution, regardless of circumstances. Obviously we can't commit > .pyc files and need licensing, but I definitely would prefer not to > see -2s in this situation. > > I think this code is important and we need to get this back on track. > This is a good "teachable moment" maybe for all sides? :) > I agree, we need to get it back. I gave my -2 in the understanding that every new functionality to the project needs a spec and an approval process first. Now that this has been discussed and it's clear we can have this kind of contributions, then I can remove the -2 (the review needs to be restored first) and continue with the review. -Erich > Thanks, > Curtis > > > > Cheers, > > Don. > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From fungi at yuggoth.org Mon Feb 25 16:59:44 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 25 Feb 2019 16:59:44 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> Message-ID: <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> On 2019-02-25 16:51:21 +0000 (+0000), Cordoba Malibran, Erich wrote: [...] > > > With that said, the review had been given two -2 votes from cores. > > > As I understand it, this is not a minor thing. From the openstack > > > guidelines, a -2 “is to indicate to the submitter that any further > > > time they spend on the change will almost certainly be wasted.” > > > Having two -2 votes on the update is very significant, thus the > > > decision to abandon the review. The openstack guidelines describing > > > -1 and -2 votes seems pretty clear here: > > > https://docs.openstack.org/project-team-guide/review-the-openstack- > > > way.html#code-review-minus-2 > > > > > > > Sounds like we need to come to a consensus as to when a -2 is > > appropriate. I personally don't think a -2 is appropriate for a first > > contribution, regardless of circumstances. Obviously we can't commit > > .pyc files and need licensing, but I definitely would prefer not to > > see -2s in this situation. > > > > I think this code is important and we need to get this back on track. > > This is a good "teachable moment" maybe for all sides? :) > > > > I agree, we need to get it back. I gave my -2 in the understanding that > every new functionality to the project needs a spec and an approval > process first. Now that this has been discussed and it's clear we can > have this kind of contributions, then I can remove the -2 (the review > needs to be restored first) and continue with the review. Sounds like the use of -2 in that case was more akin to: https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#procedural-code-review-2 Basically, "put this contribution on hold, it can't merge until we have some other discussions." The distinction is easy to miss though, which is why explaining exactly why you voted -2 on a change is critical, as well as stating what you think the next steps are. -- 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 build.starlingx at gmail.com Mon Feb 25 17:46:47 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Feb 2019 12:46:47 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 164 - Still Failing! In-Reply-To: <299666674.0.1550997083667.JavaMail.javamailuser@localhost> References: <299666674.0.1550997083667.JavaMail.javamailuser@localhost> Message-ID: <1004505376.15.1551116808691.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 164 Status: Still Failing Timestamp: 20190225T165549Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190225T164431Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190225T164431Z DOCKER_BUILD_ID: jenkins-f-stein-20190225T164431Z-builder MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190225T164431Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/stein/centos/20190225T164431Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein From build.starlingx at gmail.com Mon Feb 25 17:46:51 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Mon, 25 Feb 2019 12:46:51 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_stein_master - Build # 53 - Failure! Message-ID: <882001757.18.1551116812930.JavaMail.javamailuser@localhost> Project: STX_build_stein_master Build #: 53 Status: Failure Timestamp: 20190225T164431Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/stein/centos/20190225T164431Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From erich.cordoba.malibran at intel.com Mon Feb 25 17:49:44 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Mon, 25 Feb 2019 17:49:44 +0000 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> Message-ID: <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> Hi Scott, I think that is a great idea! I would suggest a new stx-automation or stx-ci repository, also not sure where is the best place, I would suggest github, but for sure Dean will have better insights on this :) -Erich On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: > The idea was floated several weeks ago that we should place the > jenkins > scripts used by starlingx.cengn.ca builds under git revision > control, > and publish them somewhere. > > If we are all agreed this would be a good thing, I would like to > move > forward with that proposal. > > Where should we publish it, github or openstack? > > If openstack, I'll need some pointers on how to set up the new git. > > > Thanks > > Scott > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Mon Feb 25 17:52:40 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Mon, 25 Feb 2019 17:52:40 +0000 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> Great idea! Maybe stx-tools? brucej -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] Sent: Monday, February 25, 2019 9:50 AM To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git Hi Scott, I think that is a great idea! I would suggest a new stx-automation or stx-ci repository, also not sure where is the best place, I would suggest github, but for sure Dean will have better insights on this :) -Erich On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: > The idea was floated several weeks ago that we should place the > jenkins scripts used by starlingx.cengn.ca builds under git revision > control, and publish them somewhere. > > If we are all agreed this would be a good thing, I would like to move > forward with that proposal. > > Where should we publish it, github or openstack? > > If openstack, I'll need some pointers on how to set up the new git. > > > Thanks > > Scott > > > > _______________________________________________ > 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 Don.Penney at windriver.com Mon Feb 25 18:10:38 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 25 Feb 2019 18:10:38 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA44900F@ALA-MBD.corp.ad.wrs.com> > -----Original Message----- > From: Jeremy Stanley [mailto:fungi at yuggoth.org] > Sent: Monday, February 25, 2019 12:00 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > On 2019-02-25 16:51:21 +0000 (+0000), Cordoba Malibran, Erich wrote: > [...] > > > > With that said, the review had been given two -2 votes from cores. > > > > As I understand it, this is not a minor thing. From the openstack > > > > guidelines, a -2 “is to indicate to the submitter that any further > > > > time they spend on the change will almost certainly be wasted.” > > > > Having two -2 votes on the update is very significant, thus the > > > > decision to abandon the review. The openstack guidelines > > > > describing > > > > -1 and -2 votes seems pretty clear here: > > > > https://docs.openstack.org/project-team-guide/review-the-openstack > > > > - > > > > way.html#code-review-minus-2 > > > > > > > > > > Sounds like we need to come to a consensus as to when a -2 is > > > appropriate. I personally don't think a -2 is appropriate for a > > > first contribution, regardless of circumstances. Obviously we can't > > > commit .pyc files and need licensing, but I definitely would prefer > > > not to see -2s in this situation. > > > > > > I think this code is important and we need to get this back on track. > > > This is a good "teachable moment" maybe for all sides? :) > > > > > > > I agree, we need to get it back. I gave my -2 in the understanding > > that every new functionality to the project needs a spec and an > > approval process first. Now that this has been discussed and it's > > clear we can have this kind of contributions, then I can remove the -2 > > (the review needs to be restored first) and continue with the review. > > Sounds like the use of -2 in that case was more akin to: > > https://docs.openstack.org/project-team-guide/review-the-openstack- > way.html#procedural-code-review-2 > > Basically, "put this contribution on hold, it can't merge until we have some > other discussions." The distinction is easy to miss though, which is why > explaining exactly why you voted -2 on a change is critical, as well as stating > what you think the next steps are. > -- > Jeremy Stanley I read the "procedural -2", as well, but it didn't seem applicable here. This section seems to describe a "code freeze", which is not the case here. The description of a "workflow -1" seems to align more with what it sounds like the intent of the -2s were. https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#workflow-1 Cheers, Don. From fungi at yuggoth.org Mon Feb 25 18:25:31 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 25 Feb 2019 18:25:31 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA44900F@ALA-MBD.corp.ad.wrs.com> References: <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> <6703202FD9FDFF4A8DA9ACF104AE129FBA44900F@ALA-MBD.corp.ad.wrs.com> Message-ID: <20190225182530.fxldkkqvu5jd2e65@yuggoth.org> On 2019-02-25 18:10:38 +0000 (+0000), Penney, Don wrote: [...] > I read the "procedural -2", as well, but it didn't seem applicable > here. This section seems to describe a "code freeze", which is not > the case here. > > The description of a "workflow -1" seems to align more with what > it sounds like the intent of the -2s were. > https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#workflow-1 The description of a procedural -2 there fails to convey that they're used for a lot more in OpenStack besides just deferring changes until after a code freeze. They tend to get used for any sort of "not now" deferrals which the core reviewers want to remain "sticky" in the face of new patch uploads on the same change. For example, they're commonly applied to block approval of changes are associated with a spec which has been postponed to a subsequent development cycle. Workflow -1 does certainly have some similar connotations, but is more ephemeral and also (primarily) used to simply indicate that a change is a work in progress and so the current patch in it is not yet ready to be reviewed. It gets cleared when a new patch is pushed for the change, since the most common case is that the author expects the next patch to be ready for review. Workflow -1 is also capable of being applied by the change author, whereas a Code-Review -2 can only be applied by a core reviewer on the project. -- 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 Don.Penney at windriver.com Mon Feb 25 18:32:43 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Mon, 25 Feb 2019 18:32:43 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <20190225182530.fxldkkqvu5jd2e65@yuggoth.org> References: <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> <6703202FD9FDFF4A8DA9ACF104AE129FBA44900F@ALA-MBD.corp.ad.wrs.com> <20190225182530.fxldkkqvu5jd2e65@yuggoth.org> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA449060@ALA-MBD.corp.ad.wrs.com> > -----Original Message----- > From: Jeremy Stanley [mailto:fungi at yuggoth.org] > Sent: Monday, February 25, 2019 1:26 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > On 2019-02-25 18:10:38 +0000 (+0000), Penney, Don wrote: > [...] > > I read the "procedural -2", as well, but it didn't seem applicable > > here. This section seems to describe a "code freeze", which is not the > > case here. > > > > The description of a "workflow -1" seems to align more with what it > > sounds like the intent of the -2s were. > > https://docs.openstack.org/project-team-guide/review-the-openstack- > way > > .html#workflow-1 > > The description of a procedural -2 there fails to convey that they're used for a > lot more in OpenStack besides just deferring changes until after a code > freeze. They tend to get used for any sort of "not now" deferrals which the > core reviewers want to remain "sticky" in the face of new patch uploads on > the same change. For example, they're commonly applied to block approval > of changes are associated with a spec which has been postponed to a > subsequent development cycle. > > Workflow -1 does certainly have some similar connotations, but is more > ephemeral and also (primarily) used to simply indicate that a change is a work > in progress and so the current patch in it is not yet ready to be reviewed. It > gets cleared when a new patch is pushed for the change, since the most > common case is that the author expects the next patch to be ready for > review. Workflow -1 is also capable of being applied by the change author, > whereas a Code-Review > -2 can only be applied by a core reviewer on the project. > -- > Jeremy Stanley Ok, thanks for the clarification. Is there some other documentation of voting guidelines/implications that describe this, or is this an unwritten convention? From sgw at linux.intel.com Mon Feb 25 19:51:29 2019 From: sgw at linux.intel.com (Saul Wold) Date: Mon, 25 Feb 2019 11:51:29 -0800 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> Message-ID: On 2/25/19 8:11 AM, Curtis wrote: > On Mon, Feb 25, 2019 at 10:51 AM Penney, Don > wrote: > > > > > -----Original Message----- > > From: Saul Wold [mailto:sgw at linux.intel.com > ] > > Sent: Thursday, February 21, 2019 6:19 PM > > To: starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > >> > > >> > > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > > >> iver.com > wrote: > > >>> Hi, > > >>> > > >>> I see Spec as a high level design for a code that going to be > > >>> developed, and to make sure it aligns with how community is going > > >>> to use it and to make everybody aware of what is going to do, so > > >>> others can chime in and say things that can address multiple > needs > > >>> and influence its design. Let's call this apple. > > >>> > > >>> Now I see the case of a code that has been developed before even > > >>> the community existed, and now been presented to the community to > > >>> fill a gap and improve productivity, no time to change the design > > >>> and would be up to community to accept or reject it as is. A case > > >>> of donation really, I call this one Orange. > > >>> > > >>> For Orange I think Spec is not the right word, we need a > > >>> wiki/readme to see what it does, and how to use it. It is too > late > > >>> to produce a spec to influence the design. > > >>> > > >> > > >> OpenStack Operators have a tools landing repository [1] that > > >> didn't/doesn't have the same level of requirements the rest of the > > >> OpenStack code typically does, so organizations could open source > > >> internal. potentially untested, scripts but not have to > necessarily > > >> adhere to all of the usual requirements. Over time the code in > that > > >> repository could be improved and moved out once it made sense. > > >> > > >> I think it's worthwhile to have useful internal code open sourced, > > >> and in some cases make it a bit easier to do so, and if the > code/tool > > >> gets used then start improving it following general standards. > This > > >> would require a new repository. > > >> > > >> Just a thought. :) > > >> > > > > > > I really like the idea of having a new repository as a landing zone > > > where things can be stabilize over time. When I started > reviewing this > > > tool I noticed that my comments were more focused on design > (features > > > that we might not need, restructure of cli arguments and so on) > and I > > > understand that fixing this is outside of the scope of sharing an > > > internal tool. > > > > > > So, should be go in the path of creating a new repository? or > can we > > > use an "experimental" folder within stx-tools? > > > > > > What do you think about this? > > > > > I think that this can land in the stx-tools directory along with the > > other deployment scripts. As was pointed out in the meeting this > > morning, this code has been in use within WindRiver for a while > now and > > they are making it available to the community. > > > > I think that the initial PR needed to have a better commit message > > explaining this and a little more thought put into the request > before it > > got reviewed, such as removing the .pyc files, licensing, > documentation, > > the first two where show stopper for me, but easily fixed, > documentation > > could be added later. > > > > Sau! > > > > Things like the inadvertent inclusion of pyc files (which were > already noted in multiple comments in the review) and missing > license identifiers seem to be minor and easily correctable > mistakes, and maybe not completely unexpected for a “new > contributor”. As well, I had also noted in a review comment that > this was a long-existing tool that was being published, referencing > the email from Numan and asking for the commit message to be updated > to explain this. > > As well, note that this was an optional productivity aid. It does > not impact the build, it does not impact any software. It is a tool > to help people launch StarlingX in a VirtualBox environment, to aid > them in installing and configuring the system. Nobody is required to > use it. > > With that said, the review had been given two -2 votes from cores. > As I understand it, this is not a minor thing. From the openstack > guidelines, a -2 “is to indicate to the submitter that any further > time they spend on the change will almost certainly be wasted.” > Having two -2 votes on the update is very significant, thus the > decision to abandon the review. The openstack guidelines describing > -1 and -2 votes seems pretty clear here: > https://docs.openstack.org/project-team-guide/review-the-openstack-way.html#code-review-minus-2 > > > Sounds like we need to come to a consensus as to when a -2 is > appropriate. I personally don't think a -2 is appropriate for a first > contribution, regardless of circumstances. Obviously we can't commit > .pyc files and need licensing, but I definitely would prefer not to see > -2s in this situation. > As I mentioned above, I was probably over zealous on marking it -2, consider it withdrawn. > I think this code is important and we need to get this back on track. > This is a good "teachable moment" maybe for all sides? :) > Lesson learned! Sau! > Thanks, > Curtis > > Cheers, > Don. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > Blog: serverascode.com > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From fungi at yuggoth.org Mon Feb 25 21:16:19 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 25 Feb 2019 21:16:19 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <6703202FD9FDFF4A8DA9ACF104AE129FBA449060@ALA-MBD.corp.ad.wrs.com> References: <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <488a08c912b83dc9d41ee17af17a474c283d7d86.camel@intel.com> <20190225165944.auv6ojh2wj2npkkj@yuggoth.org> <6703202FD9FDFF4A8DA9ACF104AE129FBA44900F@ALA-MBD.corp.ad.wrs.com> <20190225182530.fxldkkqvu5jd2e65@yuggoth.org> <6703202FD9FDFF4A8DA9ACF104AE129FBA449060@ALA-MBD.corp.ad.wrs.com> Message-ID: <20190225211619.6nhe3asqdgh6k4bv@yuggoth.org> On 2019-02-25 18:32:43 +0000 (+0000), Penney, Don wrote: [...] > Ok, thanks for the clarification. Is there some other > documentation of voting guidelines/implications that describe > this, or is this an unwritten convention? I think it's more just that the authors of the OpenStack Project Teams Guide weren't especially verbose on that point, coupled with conventions continuing to grow over time while that document may have lagged behind them. I've just now proposed https://review.openstack.org/639191 to cover these additional details. -- 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 jose.perez.carranza at intel.com Mon Feb 25 23:01:48 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Mon, 25 Feb 2019 23:01:48 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190222 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C9CD6C@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C9CD6C@FMSMSX108.amr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A946304@fmsmsx101.amr.corp.intel.com> Hi We are seeing below issue also on a virtual environment (Standard 2+2), we will are checking with today ISO and if is reproducible we will open the corresponding LP, will keep you informed kube-system calico-node-4bppq 0/2 ContainerCreating 0 6h39m 192.168.204.173 compute-1 kube-system calico-node-4gtcs 0/2 ContainerCreating 0 6h44m 192.168.204.245 compute-0 kube-system kube-proxy-jfjv7 0/1 ContainerCreating 0 6h39m 192.168.204.173 compute-1 kube-system kube-proxy-tw264 0/1 ContainerCreating 0 6h44m 192.168.204.245 compute-0 openstack nova-cell-setup-z2fgz 0/1 Init:0/2 0 142m 172.16.0.43 controller-0 openstack osh-openstack-garbd-garbd-5d495764d9-6xlrd 0/1 Pending 0 153m Regards, José From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Friday, February 22, 2019 5:27 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190222 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-22 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Multinode Local Storage Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc In order to debug and discard, proceed to update, override and redeploy the application. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 43 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Tue Feb 26 00:23:40 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 26 Feb 2019 00:23:40 +0000 Subject: [Starlingx-discuss] Agenda for Distro.openstack call this week Message-ID: <9A85D2917C58154C960D95352B22818BC3AD58E5@fmsmsx121.amr.corp.intel.com> The agenda for this week's call can be found on the Etherpad: https://etherpad.openstack.org/p/stx-distro-openstack-meetings. Please feel free to add items or questions to it. brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Tue Feb 26 00:31:06 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Tue, 26 Feb 2019 00:31:06 +0000 Subject: [Starlingx-discuss] Regression test cases for networking testing In-Reply-To: <7E4792BA14B1DE4BAB354DF77FE0233ABC89A895@ALA-MBD.corp.ad.wrs.com> References: <1466AF2176E6F040BD63860D0A241BBD46C8C793@FMSMSX109.amr.corp.intel.com>, <3CAA827B7A79BA46B15B280EC82088FE48277D61@ALA-MBD.corp.ad.wrs.com> <7E4792BA14B1DE4BAB354DF77FE0233ABC89A895@ALA-MBD.corp.ad.wrs.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46C8D18B@FMSMSX109.amr.corp.intel.com> Thanks for your feedback Chris, In total we are going to keep 117 test cases with different priority, will take a look into the other ones and will work in the others 33. BR Elio From: Winnicki, Chris [mailto:Chris.Winnicki at windriver.com] Sent: Monday, February 25, 2019 4:03 PM To: Waheed, Numan ; Martinez Monroy, Elio ; Xu, Chenjie ; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada ; Khalil, Ghada ; Zhao, Forrest Subject: RE: Regression test cases for networking testing Hi All Here is my feedback - respective to the row numbers in the "Regression tests Networking .xlsx" spreadsheet: Row 5-6: Remove TC: no vif model in stx Row 20-27: Remove the testcase: feature is depricated Row 41-42: Remove the testcase: n/a in STX Row 64: Correct the TC name: "i raised" to "is raised" Row: 68: Remove TC: not applicable Row 71: Remove TC: not applicable Row 72: Remove TC: not applicable Row 75: Remove TC: not applicable Row 81: Remove TC: not applicable Row 81: Remove TC: not applicable due to https://storyboard.openstack.org/#!/story/2004455 Row 82: Change priority to: 4 Row 86, 101, 102-106: Remove TC: No infra network in STX Row 109-111: Low value Row: 112-116: Change priority to: 3 Row 117, 119: N/A in STX Row: 133: VM misspeled with "vem" Row 137-138: Change priority to: 3 Row 139: Remove TC: No infra network in STX Row 140-143: Change priority to: 4 Row 146: Remove TC: No infra network in STX Row 148: Remove TC: No infra network in STX Row 149-151: Remove TC: No infra network in STX Chris Winnicki - MTS - SYS - PV chris.winnicki at windriver.com 613-963-1329 ________________________________ From: Waheed, Numan Sent: Friday, February 22, 2019 2:17 PM To: Martinez Monroy, Elio; Xu, Chenjie; starlingx-discuss at lists.starlingx.io; Winnicki, Chris Cc: Cabrales, Ada; Khalil, Ghada; Zhao, Forrest Subject: RE: Regression test cases for networking testing Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio > Sent: February-22-19 1:59 PM To: Xu, Chenjie >; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada >; Khalil, Ghada >; Waheed, Numan >; Zhao, Forrest > Subject: Regression test cases for networking testing Hello guys, I'm sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [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 ada.cabrales at intel.com Tue Feb 26 01:24:26 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 26 Feb 2019 01:24:26 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 02/25/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD77DD5@FMSMSX114.amr.corp.intel.com> Agenda for 2/26/2019 1. Regression selection progress - 15 min 2. Tests for Containerized OpenStack services - 15 min 3. Distro OpenStack patch elimination - additional tests - 15 min 4. Opens Regards Ada From shuicheng.lin at intel.com Tue Feb 26 01:58:41 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Tue, 26 Feb 2019 01:58:41 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton ; Lin, Shuicheng ; Liu, Tao ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FaultAPI.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 9660 bytes Desc: FaultAPI.xlsx URL: From juan.carlos.alonso at intel.com Tue Feb 26 03:14:38 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 26 Feb 2019 03:14:38 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-23 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 39 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 38 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 44 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Tue Feb 26 12:54:18 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Feb 2019 13:54:18 +0100 Subject: [Starlingx-discuss] Blog post ideas Message-ID: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> Hi, As a follow-up from last week’s community marketing planning call I would like to draw your attention to the StarlingX blog[1]. We would like to make sure that we have new content frequently to highlight news, roadmap items, new features and any further topics the community finds valuable to share. On the last call we came up with the following ideas: * Hands-on workshop[2] “advertisement” for the Denver Summit * Packet PoC/testing activity - blog post series? * StarlingX in OPNFV Pharos labs (Ildikó to drive) * Highlighting Kubernetes part of StarlingX and the roadmap for containerization as well as container support * Getting started with StarlingX - (Jeff to coordinate) * Community participation * How to deploy and use StarlingX * Simplex and duplex model details * Use cases? - (Jeff to coordinate) * Highlight StarlingX in context around use cases (industrial, telco, etc.) * How to use the platform * What benefits it gives As you can see we have drivers for a few ideas, but also need volunteers to cover the rest of topics as well as adding new ones to the list. If you would like to write up an article but you need help with polishing the text please feel free to reach out to me, I’m happy to help. This should not hold you back! We can use the bi-weekly calls[3] to review ideas and brainstorm if that helps with coming up with more content. If you would like to volunteer for any of the topics above or have a new idea you can add it to the meeting etherpad[4], respond to this thread or reach out to me. Please let me know if you have any questions. Thanks, Ildikó [1] https://www.starlingx.io/blog/ [2] https://etherpad.openstack.org/p/stx-denver-2019-workshop [3] https://wiki.openstack.org/wiki/Starlingx/Meetings#8am_PDT_.2F_1600_UTC_-_Community_Marketing_Planning_Call [4] https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans From erich.cordoba.malibran at intel.com Tue Feb 26 13:03:56 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 26 Feb 2019 13:03:56 +0000 Subject: [Starlingx-discuss] Blog post ideas In-Reply-To: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> References: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> Message-ID: <1CC096B2-9953-4560-810C-F282BADD0565@intel.com> On 2/26/19, 6:55 AM, "Ildiko Vancsa" wrote: Hi, As a follow-up from last week’s community marketing planning call I would like to draw your attention to the StarlingX blog[1]. We would like to make sure that we have new content frequently to highlight news, roadmap items, new features and any further topics the community finds valuable to share. On the last call we came up with the following ideas: * Hands-on workshop[2] “advertisement” for the Denver Summit * Packet PoC/testing activity - blog post series? * StarlingX in OPNFV Pharos labs (Ildikó to drive) * Highlighting Kubernetes part of StarlingX and the roadmap for containerization as well as container support * Getting started with StarlingX - (Jeff to coordinate) * Community participation * How to deploy and use StarlingX * Simplex and duplex model details * Use cases? - (Jeff to coordinate) * Highlight StarlingX in context around use cases (industrial, telco, etc.) * How to use the platform * What benefits it gives Hi Ildiko, I would suggest a "How to build your own StarlingX" topic, not sure if part of the Getting started or as a more advanced topic. -Erich From cindy.xie at intel.com Tue Feb 26 13:19:21 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Tue, 26 Feb 2019 13:19:21 +0000 Subject: [Starlingx-discuss] Agenda: Weekly StarlingX non-OpenStack Distro meeting, 2/27 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35E98FF1@SHSMSX104.ccr.corp.intel.com> Agenda for 2/27 meeting: 1. Ceph upgrade plan/status (Ovidiu, Daniel & Changcheng) 2. CentOS 7.6 upgrade test status (Numan) 3. OVS upgrade planning (Shuicheng) 4. Opens (all) -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 27, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From ildiko.vancsa at gmail.com Tue Feb 26 13:23:28 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Tue, 26 Feb 2019 14:23:28 +0100 Subject: [Starlingx-discuss] Blog post ideas In-Reply-To: <1CC096B2-9953-4560-810C-F282BADD0565@intel.com> References: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> <1CC096B2-9953-4560-810C-F282BADD0565@intel.com> Message-ID: <348326D5-8031-4586-B0FC-355F497332C9@gmail.com> Hi Erich, I like the idea. We can make “Getting Started” as a series and build could be one post considering it to be a step-by-step guide, can add screenshots, etc. What do you think? Would you be interested in writing it up as well? Thanks, Ildikó > On 2019. Feb 26., at 14:03, Cordoba Malibran, Erich wrote: > > > > On 2/26/19, 6:55 AM, "Ildiko Vancsa" wrote: > > Hi, > > As a follow-up from last week’s community marketing planning call I would like to draw your attention to the StarlingX blog[1]. > > We would like to make sure that we have new content frequently to highlight news, roadmap items, new features and any further topics the community finds valuable to share. > > On the last call we came up with the following ideas: > > * Hands-on workshop[2] “advertisement” for the Denver Summit > * Packet PoC/testing activity - blog post series? > * StarlingX in OPNFV Pharos labs (Ildikó to drive) > * Highlighting Kubernetes part of StarlingX and the roadmap for containerization as well as container support > * Getting started with StarlingX - (Jeff to coordinate) > * Community participation > * How to deploy and use StarlingX > * Simplex and duplex model details > * Use cases? - (Jeff to coordinate) > * Highlight StarlingX in context around use cases (industrial, telco, etc.) > * How to use the platform > * What benefits it gives > > > Hi Ildiko, > > I would suggest a "How to build your own StarlingX" topic, not sure if part of the Getting started or as a more advanced topic. > > -Erich > > From liang.a.fang at intel.com Tue Feb 26 13:39:27 2019 From: liang.a.fang at intel.com (Fang, Liang A) Date: Tue, 26 Feb 2019 13:39:27 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> Message-ID: Hi Alonso Do you have any wiki/doc to guide the deployment of containerized Starlingx? Below guider is out of date, e.g. controller-0 doesn't have a sub-function "worker". thanks. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards Liang From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, February 26, 2019 11:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-23 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 39 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 38 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 44 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From Dariush.Eslimi at windriver.com Tue Feb 26 13:58:03 2019 From: Dariush.Eslimi at windriver.com (Eslimi, Dariush) Date: Tue, 26 Feb 2019 13:58:03 +0000 Subject: [Starlingx-discuss] Deployment Improvements Proposal In-Reply-To: <80ED4CE81E3D8F4099306648E95DAFE44C9E44CA@ALA-MBD.corp.ad.wrs.com> References: <80ED4CE81E3D8F4099306648E95DAFE44C9E44CA@ALA-MBD.corp.ad.wrs.com> Message-ID: Here is initial WIP review as part of this spec: https://review.openstack.org/#/c/639246/ Thanks, Dariush From: Ngo, Tee [mailto:Tee.Ngo at windriver.com] Sent: January-09-19 1:53 PM To: Peters, Matt ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Deployment Improvements Proposal Hello, The Ansible bootstrap deployment specification is now available for review. https://review.openstack.org/#/c/629581/ Your feedback is welcome and appreciated. Regards, Tee From: Peters, Matt [mailto:Matt.Peters at windriver.com] Sent: December-13-18 2:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Deployment Improvements Proposal Hello, Attached are the slides I presented during the TSC call on Dec 13, 2018 for the proposed improvements to the StarlingX initial bootstrap and system inventory. As indicated on the call, a detailed stx-spec will follow, but wanted to share the high-level changes being proposed before the arrival of the spec to get some early feedback. Regards, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From Numan.Waheed at windriver.com Tue Feb 26 14:04:09 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Tue, 26 Feb 2019 14:04:09 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 02/25/2019 In-Reply-To: <4F6AACE4B0F173488D033B02A8BB5B7E7CD77DD5@FMSMSX114.amr.corp.intel.com> References: <4F6AACE4B0F173488D033B02A8BB5B7E7CD77DD5@FMSMSX114.amr.corp.intel.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE48279B7E@ALA-MBD.corp.ad.wrs.com> Hi Ada, Can you please add an agenda item to go over stx.2019.05 testing plan and see the progress. Thanks, Numan. -----Original Message----- From: Cabrales, Ada Sent: February-25-19 8:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [ Testing ] Meeting agenda - 02/25/2019 Agenda for 2/26/2019 1. Regression selection progress - 15 min 2. Tests for Containerized OpenStack services - 15 min 3. Distro OpenStack patch elimination - additional tests - 15 min 4. Opens Regards Ada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From James.Gauld at windriver.com Tue Feb 26 14:07:20 2019 From: James.Gauld at windriver.com (Gauld, James) Date: Tue, 26 Feb 2019 14:07:20 +0000 Subject: [Starlingx-discuss] PCI Interrupt affinity task In-Reply-To: <93814834B4855241994F290E959305C753042E86@SHSMSX104.ccr.corp.intel.com> References: <93814834B4855241994F290E959305C753042E86@SHSMSX104.ccr.corp.intel.com> Message-ID: <8E5740EC88EF3E4BA3196F2545DC8625BA1D5543@ALA-MBD.corp.ad.wrs.com> Zhipeng, Option 1) is a reasonable choice. I agree with your reasoning. FYI, I don't think we depend on nova-sriov script anymore, but we haven't actually tested with that removed. Please add me to your code inspection. -Jim From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: February-21-19 10:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] PCI Interrupt affinity task Hi all Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600) So far I have finished coding, basic deployment test and function test. Now, I'm preparing for uploading my patch for code review. However, I need to decide where to put code folder. >From my point, there are two options below. 1) stx-integ/utilities/nova-utils/pci-affinity-agent 2) stx-config/sysinv/pci-affinity-agent (I put code here currently) I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova. We can reuse nova-utils package with additional RPM for pci-affinity-agent Any comment from you? Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Barton.Wensley at windriver.com Tue Feb 26 14:11:09 2019 From: Barton.Wensley at windriver.com (Wensley, Barton) Date: Tue, 26 Feb 2019 14:11:09 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> Message-ID: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton ; Lin, Shuicheng ; Liu, Tao ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Al.Bailey at windriver.com Tue Feb 26 14:17:41 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 26 Feb 2019 14:17:41 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> Message-ID: I agree with Bart about this. V1 returns what it does now to minimize impact on existing API consumers, V2 returns your new structure so those consumers can migrate to that new result format if they choose. Al From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton ; Lin, Shuicheng ; Liu, Tao ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eric.MacDonald at windriver.com Tue Feb 26 14:18:50 2019 From: Eric.MacDonald at windriver.com (MacDonald, Eric) Date: Tue, 26 Feb 2019 14:18:50 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> Message-ID: <210898B96CA058408C55992CCAD98676B9FA767F@ALA-MBD.corp.ad.wrs.com> Agreed. From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton ; Lin, Shuicheng ; Liu, Tao ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Tue Feb 26 14:28:40 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Feb 2019 15:28:40 +0100 (CET) Subject: [Starlingx-discuss] Add OAM manually? Message-ID: <546908062.375303.1551191320112@communicator.strato.com> Hi, how can I add manually the OAM interface before unlocking controller-0? Thanks Marcel From Tao.Liu at windriver.com Tue Feb 26 14:30:58 2019 From: Tao.Liu at windriver.com (Liu, Tao) Date: Tue, 26 Feb 2019 14:30:58 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> Message-ID: <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> Hi Shuicheng, I agree with Bart's recommendation. The failure condition occurs when the FM manager has not been started by SM during the booting or swact, and raise an exception for this condition is a right approach. Having a new class for the new behavior is a good way to migrate the API changes. Regards, Tao From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton ; Lin, Shuicheng ; Liu, Tao ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Tue Feb 26 15:00:51 2019 From: serverascode at gmail.com (Curtis) Date: Tue, 26 Feb 2019 10:00:51 -0500 Subject: [Starlingx-discuss] Blog post ideas In-Reply-To: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> References: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> Message-ID: On Tue, Feb 26, 2019 at 7:55 AM Ildiko Vancsa wrote: > Hi, > > As a follow-up from last week’s community marketing planning call I would > like to draw your attention to the StarlingX blog[1]. > > We would like to make sure that we have new content frequently to > highlight news, roadmap items, new features and any further topics the > community finds valuable to share. > > On the last call we came up with the following ideas: > > * Hands-on workshop[2] “advertisement” for the Denver Summit > I can take this or work with people to write this. > * Packet PoC/testing activity - blog post series? > Same with this one. > * StarlingX in OPNFV Pharos labs (Ildikó to drive) > * Highlighting Kubernetes part of StarlingX and the roadmap for > containerization as well as container support > I think this was mentioned on a community call and that someone would be working on this, not sure who it was, but I believe this is a really important topic to "get out there." * Getting started with StarlingX - (Jeff to coordinate) > * Community participation > * How to deploy and use StarlingX > * Simplex and duplex model details > I also believe the simplex and duplex modes are extremely important to let people know about. While people on the project are familiar with these modes, from my experience I feel that most outside of the project don't know about these smaller deployment models, which are quite unique to StarlingX and are thus a considerable differentiator. Thanks, Curtis > * Use cases? - (Jeff to coordinate) > * Highlight StarlingX in context around use cases (industrial, telco, > etc.) > * How to use the platform > * What benefits it gives > > As you can see we have drivers for a few ideas, but also need volunteers > to cover the rest of topics as well as adding new ones to the list. > > If you would like to write up an article but you need help with polishing > the text please feel free to reach out to me, I’m happy to help. This > should not hold you back! > > We can use the bi-weekly calls[3] to review ideas and brainstorm if that > helps with coming up with more content. > > If you would like to volunteer for any of the topics above or have a new > idea you can add it to the meeting etherpad[4], respond to this thread or > reach out to me. > > Please let me know if you have any questions. > > Thanks, > Ildikó > > [1] https://www.starlingx.io/blog/ > [2] https://etherpad.openstack.org/p/stx-denver-2019-workshop > [3] > https://wiki.openstack.org/wiki/Starlingx/Meetings#8am_PDT_.2F_1600_UTC_-_Community_Marketing_Planning_Call > [4] https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Tue Feb 26 15:31:48 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Tue, 26 Feb 2019 15:31:48 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD78104@FMSMSX114.amr.corp.intel.com> Hello, A Launchpad has been created for the problem with the pods mentioned below: https://bugs.launchpad.net/starlingx/+bug/1817723 Regards A. From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Monday, February 25, 2019 9:15 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-23 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 39 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 38 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 44 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Tue Feb 26 15:32:55 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Tue, 26 Feb 2019 15:32:55 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 In-Reply-To: References: <8557B550001AFB46A43A0CCC314BF85153C9D252@FMSMSX108.amr.corp.intel.com> Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9D341@FMSMSX108.amr.corp.intel.com> Hi Liang, It's the wiki to deploy a Simplex configuration, and as far as I know it is updated. The personality "worker" is assigned to computes, in an standard configuration (storage and non-storage). Check this wiki: https://wiki.openstack.org/wiki/StarlingX/Containers, Below you can find the corresponding documentation to deploy each configuration. Regards. Juan Carlos Alonso From: Fang, Liang A Sent: Tuesday, February 26, 2019 7:39 AM To: Alonso, Juan Carlos ; starlingx-discuss at lists.starlingx.io Subject: RE: [Containers] Sanity Test - ISO 20190223 Hi Alonso Do you have any wiki/doc to guide the deployment of containerized Starlingx? Below guider is out of date, e.g. controller-0 doesn't have a sub-function "worker". thanks. https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards Liang From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, February 26, 2019 11:15 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190223 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-23 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 39 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 38 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 44 TCs PASS ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 39 TCs [PASS] Sanity Platform In Development TOTAL: [ 39 TCs PASS ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Cannot launch instances due to: No valid host was found. Placement service found no hosts. No filter information. Seems that some pods services are not Running nor Completed: - calico-node-fnstv - calico-node-wrmwj - kube-proxy-mvddg - kube-proxy-stnq9 - nova-cell-setup-xb8xp - osh-openstack-garbd-garbd-7779844649-6zttc Will check with today ISO and if it is reproducible a Launchpad will be open. ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Tue Feb 26 17:10:56 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Tue, 26 Feb 2019 18:10:56 +0100 (CET) Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface Message-ID: <916898801.387370.1551201057012@communicator.strato.com> Hi, I need help understanding this issue: After configuring according to the installation guide lines I cannot unlock controller-0, because of a missing oam interface: root at localhost ~(keystone_admin)]# system host-unlock controller-0 Can not unlock a controller host without an oam interface. Add an oam interface before re-attempting this command. The command [root at localhost ~(keystone_admin)]# system network-list +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | id | uuid | name | type | dynamic | pool_uuid | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | 2 | 4d532cb8-01f6-463d-8727-2884a65e5068 | pxeboot | pxeboot | True | 70f7017b-83b4-47ba-b414-b5098ad1cfd0 | | 3 | 86224548-3c59-45ff-a244-349850e92168 | oam | oam | False | 81febeed-1c71-4fa0-92d4-e92a98e61c51 | | 1 | cf644862-61ed-4760-ae95-1d4305add490 | mgmt | mgmt | True | ae271028-9814-4757-981b-396862cf2deb | | 4 | e696bc41-b460-43c7-ba15-bc90a1b2e78e | multicast | multicast | False | 442b1b92-41fa-4b46-9560-88f930928578 | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ shows the oam interface. Is there in issue with static ip? Any idea is welcome! Thanks Marcel From vm.rod25 at gmail.com Tue Feb 26 17:59:00 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Tue, 26 Feb 2019 11:59:00 -0600 Subject: [Starlingx-discuss] Is there any plan of containerize the flock services ? Message-ID: Hi Frank and STX community Based on the presentation discuss during phoenix meeting last January I had the impression that flock services were meant to be on the host OS where the containers are running, is this still valid for the long term? I am asking this because on today multi-OS meeting we present the following architecture/plan: https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7OYUBNdJyY-5ZvDc/edit?usp=sharing Where we are considering the task of build all the flock services on Ubuntu, However, based on this task: https://storyboard.openstack.org/#!/story/2004008 Gives me the impression that there is a plan for reducing the number of flock services running on the host OS, If that is the case, Could you please share the list of what flock services that you have in mind to put in a container? this will help us to reduce the list of packages we need to build. On the same topic, for the none open stack packages like systemd, bash or python, do you have the list of packages that need to run outside the containers on the host OS? Having this exact list of packages will help us to focus on the exact packages to build on Ubuntu. Regards Victor Rodriguez From Joseph.Richard at windriver.com Tue Feb 26 18:18:08 2019 From: Joseph.Richard at windriver.com (Richard, Joseph) Date: Tue, 26 Feb 2019 18:18:08 +0000 Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface In-Reply-To: <916898801.387370.1551201057012@communicator.strato.com> References: <916898801.387370.1551201057012@communicator.strato.com> Message-ID: <7B6A2AE64F40F245AE81F245059F0C366BE43D48@ALA-MBD.corp.ad.wrs.com> That shows the networks on your system, not the interfaces on controller-0. Run `system host-if-list controller-0 -a` to see the interfaces on controller-0. -----Original Message----- From: Marcel Schaible [mailto:marcel at schaible-consulting.de] Sent: Tuesday, February 26, 2019 12:11 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface Hi, I need help understanding this issue: After configuring according to the installation guide lines I cannot unlock controller-0, because of a missing oam interface: root at localhost ~(keystone_admin)]# system host-unlock controller-0 Can not unlock a controller host without an oam interface. Add an oam interface before re-attempting this command. The command [root at localhost ~(keystone_admin)]# system network-list +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | id | uuid | name | type | dynamic | pool_uuid | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | 2 | 4d532cb8-01f6-463d-8727-2884a65e5068 | pxeboot | pxeboot | True | 70f7017b-83b4-47ba-b414-b5098ad1cfd0 | | 3 | 86224548-3c59-45ff-a244-349850e92168 | oam | oam | False | 81febeed-1c71-4fa0-92d4-e92a98e61c51 | | 1 | cf644862-61ed-4760-ae95-1d4305add490 | mgmt | mgmt | True | ae271028-9814-4757-981b-396862cf2deb | | 4 | e696bc41-b460-43c7-ba15-bc90a1b2e78e | multicast | multicast | False | 442b1b92-41fa-4b46-9560-88f930928578 | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ shows the oam interface. Is there in issue with static ip? Any idea is welcome! Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Tue Feb 26 18:28:24 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Tue, 26 Feb 2019 18:28:24 +0000 Subject: [Starlingx-discuss] Nova NUMA live migration Message-ID: <9A85D2917C58154C960D95352B22818BC3AD64B2@fmsmsx121.amr.corp.intel.com> This is one of the key features needed for StarlingX. It is being actively worked on in the Nova community, and the work is coming down to the wire for Stein. You can find the active reviews here: [0]. If you can test these code changes, comment on the code reviews or otherwise help Artom complete this work for Stein, it would be greatly appreciated. Thank you! Brucej [0] https://review.openstack.org/#/q/topic:bp/numa-aware-live-migration+(status:open+OR+status:merged) -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Tue Feb 26 20:07:24 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 26 Feb 2019 20:07:24 +0000 Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> Hi Today while I was setting up a Simplex configuration with support for containers [1] I realized that when running section " Set Ceph pool replication (AIO-SX only)" only one pool is listed, but after doing the unlock of the controller another 4 pools are listed, and hence `ceph -s` is showing warning, this is solved executing again the command for osd pool set. My question here is that if this behavior is expected? Hence I can update the wiki accordingly. =================================== - Before Unlock controller-0:~$ ceph osd pool ls rbd - After Unlock wrsroot at controller-0 ~(keystone_admin)]$ ceph osd pool ls rbd .rgw.root default.rgw.control default.rgw.data.root default.rgw.gc default.rgw.log [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s cluster 783007cd-8d65-4e79-8905-b22262326a7c health HEALTH_WARN 320 pgs degraded 64 pgs stuck unclean 320 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller-0=192.168.204.3:6789/0} election epoch 4, quorum 0 controller-0 osdmap e16: 1 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v19: 384 pgs, 6 pools, 1588 bytes data, 1116 objects 43308 kB used, 101283 MB / 101325 MB avail 1116/2232 objects degraded (50.000%) 320 active+undersized+degraded 64 active+clean =================================== 1- https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards, José From Robert.Church at windriver.com Tue Feb 26 20:38:38 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 26 Feb 2019 20:38:38 +0000 Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> Message-ID: Hi José, I believe that this is the current behavior on the master branch. Those pools are created by the rados-gw. In f/stein, there is a CronJob installed in the cluster to audit and fix this condition. See https://git.starlingx.io/cgit/stx-config/commit/?h=f/stein&id=754f49a3575b78517327c3a0a7556cc25de6a18b Feel free to make the wiki change but please add a note that this is for the master branch only. After cut-over (when we merge f/stein into master), we'll need to update it again. Bob On 2/26/19, 2:08 PM, "Perez Carranza, Jose" wrote: Hi Today while I was setting up a Simplex configuration with support for containers [1] I realized that when running section " Set Ceph pool replication (AIO-SX only)" only one pool is listed, but after doing the unlock of the controller another 4 pools are listed, and hence `ceph -s` is showing warning, this is solved executing again the command for osd pool set. My question here is that if this behavior is expected? Hence I can update the wiki accordingly. =================================== - Before Unlock controller-0:~$ ceph osd pool ls rbd - After Unlock wrsroot at controller-0 ~(keystone_admin)]$ ceph osd pool ls rbd .rgw.root default.rgw.control default.rgw.data.root default.rgw.gc default.rgw.log [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s cluster 783007cd-8d65-4e79-8905-b22262326a7c health HEALTH_WARN 320 pgs degraded 64 pgs stuck unclean 320 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller-0=192.168.204.3:6789/0} election epoch 4, quorum 0 controller-0 osdmap e16: 1 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v19: 384 pgs, 6 pools, 1588 bytes data, 1116 objects 43308 kB used, 101283 MB / 101325 MB avail 1116/2232 objects degraded (50.000%) 320 active+undersized+degraded 64 active+clean =================================== 1- https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From Al.Bailey at windriver.com Tue Feb 26 20:44:41 2019 From: Al.Bailey at windriver.com (Bailey, Henry Albert (Al)) Date: Tue, 26 Feb 2019 20:44:41 +0000 Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> Message-ID: The wiki has a couple places in AIO-SX where that command is mentioned. Its listed after ceph is being configured, and listed after the services have been brought up. So, I would say that it is expected, but maybe it needs to be called out more explicitly. I think it might need to be done if you reboot or power-cycle the AIO-SX, but I am not certain of that. Ovidiu would probably be the expert on that. Al -----Original Message----- From: Perez Carranza, Jose [mailto:jose.perez.carranza at intel.com] Sent: Tuesday, February 26, 2019 3:07 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex Hi Today while I was setting up a Simplex configuration with support for containers [1] I realized that when running section " Set Ceph pool replication (AIO-SX only)" only one pool is listed, but after doing the unlock of the controller another 4 pools are listed, and hence `ceph -s` is showing warning, this is solved executing again the command for osd pool set. My question here is that if this behavior is expected? Hence I can update the wiki accordingly. =================================== - Before Unlock controller-0:~$ ceph osd pool ls rbd - After Unlock wrsroot at controller-0 ~(keystone_admin)]$ ceph osd pool ls rbd .rgw.root default.rgw.control default.rgw.data.root default.rgw.gc default.rgw.log [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s cluster 783007cd-8d65-4e79-8905-b22262326a7c health HEALTH_WARN 320 pgs degraded 64 pgs stuck unclean 320 pgs undersized recovery 1116/2232 objects degraded (50.000%) monmap e1: 1 mons at {controller-0=192.168.204.3:6789/0} election epoch 4, quorum 0 controller-0 osdmap e16: 1 osds: 1 up, 1 in flags sortbitwise,require_jewel_osds pgmap v19: 384 pgs, 6 pools, 1588 bytes data, 1116 objects 43308 kB used, 101283 MB / 101325 MB avail 1116/2232 objects degraded (50.000%) 320 active+undersized+degraded 64 active+clean =================================== 1- https://wiki.openstack.org/wiki/StarlingX/Containers/Installation Regards, José _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From jose.perez.carranza at intel.com Tue Feb 26 21:27:59 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Tue, 26 Feb 2019 21:27:59 +0000 Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex In-Reply-To: References: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A946628@fmsmsx101.amr.corp.intel.com> Hi Bob I'm using an ISO based on stein. http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190225T191350Z/ Regards, José > -----Original Message----- > From: Church, Robert [mailto:Robert.Church at windriver.com] > Sent: Tuesday, February 26, 2019 2:39 PM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Containers] Set Ceph pool replication on > Simplex > > Hi José, > > I believe that this is the current behavior on the master branch. Those pools > are created by the rados-gw. > > In f/stein, there is a CronJob installed in the cluster to audit and fix this > condition. > > See https://git.starlingx.io/cgit/stx- > config/commit/?h=f/stein&id=754f49a3575b78517327c3a0a7556cc25de6a18b > > Feel free to make the wiki change but please add a note that this is for the > master branch only. After cut-over (when we merge f/stein into master), we'll > need to update it again. > > Bob > > On 2/26/19, 2:08 PM, "Perez Carranza, Jose" > wrote: > > Hi > > Today while I was setting up a Simplex configuration with support for > containers [1] I realized that when running section " Set Ceph pool replication > (AIO-SX only)" only one pool is listed, but after doing the unlock of the > controller another 4 pools are listed, and hence `ceph -s` is showing warning, > this is solved executing again the command for osd pool set. My question here > is that if this behavior is expected? Hence I can update the wiki accordingly. > > > =================================== > - Before Unlock > > controller-0:~$ ceph osd pool ls > rbd > > > - After Unlock > > wrsroot at controller-0 ~(keystone_admin)]$ ceph osd pool ls > rbd > .rgw.root > default.rgw.control > default.rgw.data.root > default.rgw.gc > default.rgw.log > > [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s > cluster 783007cd-8d65-4e79-8905-b22262326a7c > health HEALTH_WARN > 320 pgs degraded > 64 pgs stuck unclean > 320 pgs undersized > recovery 1116/2232 objects degraded (50.000%) > monmap e1: 1 mons at {controller-0=192.168.204.3:6789/0} > election epoch 4, quorum 0 controller-0 > osdmap e16: 1 osds: 1 up, 1 in > flags sortbitwise,require_jewel_osds > pgmap v19: 384 pgs, 6 pools, 1588 bytes data, 1116 objects > 43308 kB used, 101283 MB / 101325 MB avail > 1116/2232 objects degraded (50.000%) > 320 active+undersized+degraded > 64 active+clean > > =================================== > > > > 1- https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > > Regards, > José > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From erich.cordoba.malibran at intel.com Tue Feb 26 22:08:09 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 26 Feb 2019 22:08:09 +0000 Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface In-Reply-To: <916898801.387370.1551201057012@communicator.strato.com> References: <916898801.387370.1551201057012@communicator.strato.com> Message-ID: <7449AA0F-8E2F-4A93-8563-FFDB14731C38@intel.com> Hi Marcel, I had faced the same issue following these steps[0], I'm not sure if this is the same case. Check the section "Configure Data Interfaces for Controller-1". In my case my network device was "ens3" not "enp0s3", setting this variable fixed the issue for me. OAM_IF=ens3 I hope this can help -Erich On 2/26/19, 11:11 AM, "Marcel Schaible" wrote: Hi, I need help understanding this issue: After configuring according to the installation guide lines I cannot unlock controller-0, because of a missing oam interface: root at localhost ~(keystone_admin)]# system host-unlock controller-0 Can not unlock a controller host without an oam interface. Add an oam interface before re-attempting this command. The command [root at localhost ~(keystone_admin)]# system network-list +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | id | uuid | name | type | dynamic | pool_uuid | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ | 2 | 4d532cb8-01f6-463d-8727-2884a65e5068 | pxeboot | pxeboot | True | 70f7017b-83b4-47ba-b414-b5098ad1cfd0 | | 3 | 86224548-3c59-45ff-a244-349850e92168 | oam | oam | False | 81febeed-1c71-4fa0-92d4-e92a98e61c51 | | 1 | cf644862-61ed-4760-ae95-1d4305add490 | mgmt | mgmt | True | ae271028-9814-4757-981b-396862cf2deb | | 4 | e696bc41-b460-43c7-ba15-bc90a1b2e78e | multicast | multicast | False | 442b1b92-41fa-4b46-9560-88f930928578 | +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ shows the oam interface. Is there in issue with static ip? Any idea is welcome! Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From erich.cordoba.malibran at intel.com Tue Feb 26 22:11:36 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Tue, 26 Feb 2019 22:11:36 +0000 Subject: [Starlingx-discuss] Blog post ideas In-Reply-To: <348326D5-8031-4586-B0FC-355F497332C9@gmail.com> References: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> <1CC096B2-9953-4560-810C-F282BADD0565@intel.com> <348326D5-8031-4586-B0FC-355F497332C9@gmail.com> Message-ID: <9B0641DD-F520-4DAD-BAB5-49077DA3362E@intel.com> Sure Ildiko, I'd like to help with the blog post. What is the process for writing up? Do I need to send a review in some repository or is a different process? Thanks in advance! -Erich On 2/26/19, 7:23 AM, "Ildiko Vancsa" wrote: Hi Erich, I like the idea. We can make “Getting Started” as a series and build could be one post considering it to be a step-by-step guide, can add screenshots, etc. What do you think? Would you be interested in writing it up as well? Thanks, Ildikó > On 2019. Feb 26., at 14:03, Cordoba Malibran, Erich wrote: > > > > On 2/26/19, 6:55 AM, "Ildiko Vancsa" wrote: > > Hi, > > As a follow-up from last week’s community marketing planning call I would like to draw your attention to the StarlingX blog[1]. > > We would like to make sure that we have new content frequently to highlight news, roadmap items, new features and any further topics the community finds valuable to share. > > On the last call we came up with the following ideas: > > * Hands-on workshop[2] “advertisement” for the Denver Summit > * Packet PoC/testing activity - blog post series? > * StarlingX in OPNFV Pharos labs (Ildikó to drive) > * Highlighting Kubernetes part of StarlingX and the roadmap for containerization as well as container support > * Getting started with StarlingX - (Jeff to coordinate) > * Community participation > * How to deploy and use StarlingX > * Simplex and duplex model details > * Use cases? - (Jeff to coordinate) > * Highlight StarlingX in context around use cases (industrial, telco, etc.) > * How to use the platform > * What benefits it gives > > > Hi Ildiko, > > I would suggest a "How to build your own StarlingX" topic, not sure if part of the Getting started or as a more advanced topic. > > -Erich > > From Robert.Church at windriver.com Tue Feb 26 22:46:08 2019 From: Robert.Church at windriver.com (Church, Robert) Date: Tue, 26 Feb 2019 22:46:08 +0000 Subject: [Starlingx-discuss] [Containers] Set Ceph pool replication on Simplex In-Reply-To: <0A5D9A624DF90343892F8F3FE7DE525A2A946628@fmsmsx101.amr.corp.intel.com> References: <0A5D9A624DF90343892F8F3FE7DE525A2A9465D3@fmsmsx101.amr.corp.intel.com> <0A5D9A624DF90343892F8F3FE7DE525A2A946628@fmsmsx101.amr.corp.intel.com> Message-ID: Hi José, If you are running a f/stein build, then you should see the following running every 5 minutes: controller-0:~$ kubectl get pods --all-namespaces -o wide | grep ceph openstack ceph-pools-audit-1551219000-t97lr 0/1 Completed 0 12m 172.16.0.67 controller-0 openstack ceph-pools-audit-1551219300-9nkgh 0/1 Completed 0 7m49s 172.16.0.75 controller-0 openstack ceph-pools-audit-1551219600-x5c2c 0/1 Completed 0 2m47s 172.16.0.77 controller-0 This will update the existing pools to clear any warnings. With the AIO-SX, ceph warnings will currently be seen after initial install. After the application install, once the job is running, any pools will be adjusted based on the replication settings in the ceph storage backend. Regards, Bob On 2/26/19, 3:28 PM, "Perez Carranza, Jose" wrote: Hi Bob I'm using an ISO based on stein. http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190225T191350Z/ Regards, José > -----Original Message----- > From: Church, Robert [mailto:Robert.Church at windriver.com] > Sent: Tuesday, February 26, 2019 2:39 PM > To: Perez Carranza, Jose ; starlingx- > discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [Containers] Set Ceph pool replication on > Simplex > > Hi José, > > I believe that this is the current behavior on the master branch. Those pools > are created by the rados-gw. > > In f/stein, there is a CronJob installed in the cluster to audit and fix this > condition. > > See https://git.starlingx.io/cgit/stx- > config/commit/?h=f/stein&id=754f49a3575b78517327c3a0a7556cc25de6a18b > > Feel free to make the wiki change but please add a note that this is for the > master branch only. After cut-over (when we merge f/stein into master), we'll > need to update it again. > > Bob > > On 2/26/19, 2:08 PM, "Perez Carranza, Jose" > wrote: > > Hi > > Today while I was setting up a Simplex configuration with support for > containers [1] I realized that when running section " Set Ceph pool replication > (AIO-SX only)" only one pool is listed, but after doing the unlock of the > controller another 4 pools are listed, and hence `ceph -s` is showing warning, > this is solved executing again the command for osd pool set. My question here > is that if this behavior is expected? Hence I can update the wiki accordingly. > > > =================================== > - Before Unlock > > controller-0:~$ ceph osd pool ls > rbd > > > - After Unlock > > wrsroot at controller-0 ~(keystone_admin)]$ ceph osd pool ls > rbd > .rgw.root > default.rgw.control > default.rgw.data.root > default.rgw.gc > default.rgw.log > > [wrsroot at controller-0 ~(keystone_admin)]$ ceph -s > cluster 783007cd-8d65-4e79-8905-b22262326a7c > health HEALTH_WARN > 320 pgs degraded > 64 pgs stuck unclean > 320 pgs undersized > recovery 1116/2232 objects degraded (50.000%) > monmap e1: 1 mons at {controller-0=192.168.204.3:6789/0} > election epoch 4, quorum 0 controller-0 > osdmap e16: 1 osds: 1 up, 1 in > flags sortbitwise,require_jewel_osds > pgmap v19: 384 pgs, 6 pools, 1588 bytes data, 1116 objects > 43308 kB used, 101283 MB / 101325 MB avail > 1116/2232 objects degraded (50.000%) > 320 active+undersized+degraded > 64 active+clean > > =================================== > > > > 1- https://wiki.openstack.org/wiki/StarlingX/Containers/Installation > > Regards, > José > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From yong.hu at intel.com Wed Feb 27 00:39:32 2019 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 27 Feb 2019 00:39:32 +0000 Subject: [Starlingx-discuss] Add OAM manually? In-Reply-To: <546908062.375303.1551191320112@communicator.strato.com> References: <546908062.375303.1551191320112@communicator.strato.com> Message-ID: <026DE3C9-040D-4B77-AEA3-68CDAD96BB07@intel.com> Given you have at least 2 NIC interfaces for Controller-0, and One is for OAM and another for Mgt, OAM interface will be set by "config_controller", during which you can modify the IP address. After that, I am not aware changing OAM network is allowed. Could you tell what you meant about *add manually the OAM interface*? -Yong On 26/02/2019, 10:30 PM, "Marcel Schaible" wrote: Hi, how can I add manually the OAM interface before unlocking controller-0? Thanks Marcel _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Wed Feb 27 00:47:11 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Wed, 27 Feb 2019 00:47:11 +0000 Subject: [Starlingx-discuss] Improve FM's Python API return data In-Reply-To: <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> References: <9700A18779F35F49AF027300A49E7C765FE850FA@SHSMSX101.ccr.corp.intel.com> <210898B96CA058408C55992CCAD98676B9FA630E@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE854D3@SHSMSX101.ccr.corp.intel.com> <9700A18779F35F49AF027300A49E7C765FE87381@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA67C8C@ALA-MBD.corp.ad.wrs.com> <210898B96CA058408C55992CCAD98676B9FA7348@ALA-MBD.corp.ad.wrs.com> <9700A18779F35F49AF027300A49E7C765FE876D1@SHSMSX101.ccr.corp.intel.com> <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA682EB@ALA-MBD.corp.ad.wrs.com> <7242A3DC72E453498E3D783BBB134C3E9DDC0111@ALA-MBD.corp.ad.wrs.com> Message-ID: <9700A18779F35F49AF027300A49E7C765FE87D29@SHSMSX101.ccr.corp.intel.com> Hi all, Thanks for the quick confirmation. I will implement the code as Bart's suggestion. Best Regards Shuicheng From: Liu, Tao [mailto:Tao.Liu at windriver.com] Sent: Tuesday, February 26, 2019 10:31 PM To: Wensley, Barton ; Lin, Shuicheng ; MacDonald, Eric ; Bailey, Henry Albert (Al) Cc: Xie, Cindy ; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Shuicheng, I agree with Bart's recommendation. The failure condition occurs when the FM manager has not been started by SM during the booting or swact, and raise an exception for this condition is a right approach. Having a new class for the new behavior is a good way to migrate the API changes. Regards, Tao From: Wensley, Barton Sent: Tuesday, February 26, 2019 9:11 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Shuicheng, As per your spreadsheet, there are actually three APIs that currently return ambiguous results (get_fault, get_faults and get_faults_by_id). My view is that you should be updating all six APIs to be consistent and raise an exception if the operation fails (e.g. because the API can't connect to fmmanager). You can avoid impacting the existing APIs by having both a FaultAPIs class and a FaultAPIsV2 class. To avoid code duplication, you would create a FaultAPIsBase class to hold all the common code and subclass from it. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 8:59 PM To: MacDonald, Eric; Wensley, Barton; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi Eric/Tao/Al, Please confirm you agree a new set fault API (FaultAPIs_V2) or not. The attached excel is a simple comparison between original class FaultAPIs and FaultAPIs_V2. For myself, I still prefer to add 2 new API in original class, so other API call could be kept without change. We could have more discuss about the FaultAPIs_V2 design if you all agree to choose it. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Monday, February 25, 2019 10:23 PM To: Wensley, Barton >; Lin, Shuicheng >; Liu, Tao >; Bailey, Henry Albert (Al) > Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data I see your point Bart. This Jira is an Enhancement Request and fulfilling that should not be done so half way. All the APIs in V2 should be changed to defer exception handling to the caller as apparently that is the pythonic way. From: Wensley, Barton Sent: Monday, February 25, 2019 8:10 AM To: Lin, Shuicheng; MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al) Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Importance: High I disagree with this approach. Instead of just updating two of the methods, you should be updating all the methods in the FaultAPIs class that could fail in the same way and have them raise an exception. You should create a new FaultAPIs_v2 class for the updated methods to avoid impacting existing users. When a user of this API wants to use the new exceptions, they will start using the new class. Bart From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: February 25, 2019 2:58 AM To: MacDonald, Eric; Liu, Tao; Bailey, Henry Albert (Al); Wensley, Barton Cc: Xie, Cindy; starlingx-discuss at lists.starlingx.io Subject: RE: Improve FM's Python API return data Hi all, Based on the comments in patch [0], I will add two new API, get_fault_ex and get_faults_by_id_ex. I will not add a new class, since all other APIs are kept without change. For get_fault_ex and get_faults_by_id_ex: the return value will be alarm list (maybe None). Exception will be thrown if there is error during API execution. [0]: https://review.openstack.org/637655 Best Regards Shuicheng From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Wednesday, February 20, 2019 10:41 AM To: MacDonald, Eric >; Liu, Tao >; Al.Bailey at windriver.com Cc: Xie, Cindy >; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Improve FM's Python API return data Hi Eric, Thanks for the detail comments. In my plan, the return value for get_fault API will be like below: (False, None): there is error in the API execution. (True, None): API execution correctly, and there is no alarm message. (True, Alarm): API execution correctly, and there is alarm message. I think it should fix the issue you have. Is it right? If you agree on this new API return value change, I will implement it. Thanks. Best Regards Shuicheng From: MacDonald, Eric [mailto:Eric.MacDonald at windriver.com] Sent: Tuesday, February 19, 2019 10:35 PM To: Lin, Shuicheng >; Liu, Tao > Cc: Xie, Cindy > Subject: RE: Improve FM's Python API return data I took a look and added comments. I don't think this update fixes the issue I have. From: Lin, Shuicheng [mailto:shuicheng.lin at intel.com] Sent: Monday, February 18, 2019 10:09 PM To: MacDonald, Eric; Liu, Tao Cc: Xie, Cindy Subject: RE: Improve FM's Python API return data Importance: High Resend the mail. Best Regards Shuicheng From: Lin, Shuicheng Sent: Tuesday, February 19, 2019 9:56 AM To: Liu, Tao (Wind River) >; 'eric.macdonald at windriver.com' > Cc: Xie, Cindy > Subject: Improve FM's Python API return data Hi Tao/Eric, For story 2004859, I plan to modify the get_fault api return value as a tuple. (True/False, Alarm) Alarm is valid only when the 1st item is True. Sample code is uploaded for you early review: Stx-fault: https://review.openstack.org/637655 Stx-integ: https://review.openstack.org/637656 Could you help review it and share your thought? If you agree on it, I will implement the code and test it. For test, I will try to kill fmManager/modify its listening port to simulate the failure case. For the api call outside of stx-fault, I may try to call it manually to verify. Please share me if there is better verify method. Thanks. Best Regards Shuicheng -------------- next part -------------- An HTML attachment was scrubbed... URL: From elio.martinez.monroy at intel.com Wed Feb 27 00:54:18 2019 From: elio.martinez.monroy at intel.com (Martinez Monroy, Elio) Date: Wed, 27 Feb 2019 00:54:18 +0000 Subject: [Starlingx-discuss] Add OAM manually? In-Reply-To: <026DE3C9-040D-4B77-AEA3-68CDAD96BB07@intel.com> References: <546908062.375303.1551191320112@communicator.strato.com> <026DE3C9-040D-4B77-AEA3-68CDAD96BB07@intel.com> Message-ID: <1466AF2176E6F040BD63860D0A241BBD46C8D698@FMSMSX109.amr.corp.intel.com> Hello Yong and Marcel Yes, OAM interfaces is set during config_controller. And yes, you can modify OAM interface, please check following steps: 1. In controller-0 (active), check default OAM config system oam-show 2.Modify cEXT_OAM section with compatible configuration (OAM IP for controller-1) system oam-modify oam_c1_ip=10.10.10.11 3. Verify that new configuration is accepted system oam-show 4. Verify that config_applied ID is equal for all hosts $ system host-show 5. Verify that config_target ID is equal for all hosts system host-show 6. Lock and unlock the controller-1, so config can be updated system host-lock controller-1 system host-show system host-unlock controller-1 system host-show 7. Swact controllers. Wait until new master (controller-1) controller appeared 8. verify that ip address for OAM interface is changed to new value and verify that oam controller IP address is changed to new address. ssh to host ifconfig (only for controllers) cat /etc/hosts 9. Verify that config_applied and config_target are equal to uuid of new applied config for new master host system host-show 10. lock and unlock the compute nodes one at a time, ensuring that sufficient resources are available to migrate any running instances Please let me know if you have more questions -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, February 26, 2019 6:40 PM To: Marcel Schaible ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Add OAM manually? Given you have at least 2 NIC interfaces for Controller-0, and One is for OAM and another for Mgt, OAM interface will be set by "config_controller", during which you can modify the IP address. After that, I am not aware changing OAM network is allowed. Could you tell what you meant about *add manually the OAM interface*? -Yong On 26/02/2019, 10:30 PM, "Marcel Schaible" wrote: Hi, how can I add manually the OAM interface before unlocking controller-0? Thanks Marcel _______________________________________________ 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 yong.hu at intel.com Wed Feb 27 01:30:56 2019 From: yong.hu at intel.com (Hu, Yong) Date: Wed, 27 Feb 2019 01:30:56 +0000 Subject: [Starlingx-discuss] Add OAM manually? In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46C8D698@FMSMSX109.amr.corp.intel.com> References: <546908062.375303.1551191320112@communicator.strato.com> <026DE3C9-040D-4B77-AEA3-68CDAD96BB07@intel.com> <1466AF2176E6F040BD63860D0A241BBD46C8D698@FMSMSX109.amr.corp.intel.com> Message-ID: Thanks, Elio. So, it looks we need to have 2 controllers, so that when one is locked for editing and another is playing the active role. On 27/02/2019, 8:54 AM, "Martinez Monroy, Elio" wrote: Hello Yong and Marcel Yes, OAM interfaces is set during config_controller. And yes, you can modify OAM interface, please check following steps: 1. In controller-0 (active), check default OAM config system oam-show 2.Modify cEXT_OAM section with compatible configuration (OAM IP for controller-1) system oam-modify oam_c1_ip=10.10.10.11 3. Verify that new configuration is accepted system oam-show 4. Verify that config_applied ID is equal for all hosts $ system host-show 5. Verify that config_target ID is equal for all hosts system host-show 6. Lock and unlock the controller-1, so config can be updated system host-lock controller-1 system host-show system host-unlock controller-1 system host-show 7. Swact controllers. Wait until new master (controller-1) controller appeared 8. verify that ip address for OAM interface is changed to new value and verify that oam controller IP address is changed to new address. ssh to host ifconfig (only for controllers) cat /etc/hosts 9. Verify that config_applied and config_target are equal to uuid of new applied config for new master host system host-show 10. lock and unlock the compute nodes one at a time, ensuring that sufficient resources are available to migrate any running instances Please let me know if you have more questions -----Original Message----- From: Hu, Yong [mailto:yong.hu at intel.com] Sent: Tuesday, February 26, 2019 6:40 PM To: Marcel Schaible ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Add OAM manually? Given you have at least 2 NIC interfaces for Controller-0, and One is for OAM and another for Mgt, OAM interface will be set by "config_controller", during which you can modify the IP address. After that, I am not aware changing OAM network is allowed. Could you tell what you meant about *add manually the OAM interface*? -Yong On 26/02/2019, 10:30 PM, "Marcel Schaible" wrote: Hi, how can I add manually the OAM interface before unlocking controller-0? Thanks Marcel _______________________________________________ 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 zhipengs.liu at intel.com Wed Feb 27 01:40:23 2019 From: zhipengs.liu at intel.com (Liu, ZhipengS) Date: Wed, 27 Feb 2019 01:40:23 +0000 Subject: [Starlingx-discuss] PCI Interrupt affinity task In-Reply-To: <8E5740EC88EF3E4BA3196F2545DC8625BA1D5543@ALA-MBD.corp.ad.wrs.com> References: <93814834B4855241994F290E959305C753042E86@SHSMSX104.ccr.corp.intel.com> <8E5740EC88EF3E4BA3196F2545DC8625BA1D5543@ALA-MBD.corp.ad.wrs.com> Message-ID: <93814834B4855241994F290E959305C75304499E@SHSMSX104.ccr.corp.intel.com> Jim, Thanks for your comment! I will add you to review my patch after my patch submitted. Zhipeng From: Gauld, James [mailto:James.Gauld at windriver.com] Sent: 2019年2月26日 22:07 To: Liu, ZhipengS ; starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] PCI Interrupt affinity task Zhipeng, Option 1) is a reasonable choice. I agree with your reasoning. FYI, I don’t think we depend on nova-sriov script anymore, but we haven't actually tested with that removed. Please add me to your code inspection. -Jim From: Liu, ZhipengS [mailto:zhipengs.liu at intel.com] Sent: February-21-19 10:24 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] PCI Interrupt affinity task Hi all Recently, I have being working on pci interrupt affinity task (https://storyboard.openstack.org/#!/story/2004600) So far I have finished coding, basic deployment test and function test. Now, I’m preparing for uploading my patch for code review. However, I need to decide where to put code folder. >From my point, there are two options below. 1) stx-integ/utilities/nova-utils/pci-affinity-agent 2) stx-config/sysinv/pci-affinity-agent (I put code here currently) I prefer option 1 as nova-utils is just used to install nova-sriov script only and pci affinity is also an extended feature for nova. We can reuse nova-utils package with additional RPM for pci-affinity-agent Any comment from you? Thanks! zhipeng -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ken.Young at windriver.com Wed Feb 27 01:59:55 2019 From: Ken.Young at windriver.com (Young, Ken) Date: Wed, 27 Feb 2019 01:59:55 +0000 Subject: [Starlingx-discuss] Readout of CVE Scanning Tool Selection Message-ID: <328A7CA7-5B3D-459D-8786-C6B0C3B37919@windriver.com> All, The security team has been collaborating with the build team to evaluate tools for CVE Scanning in Starling X. This collaboration has clarified the requirements for a tool which has been documented here: https://storyboard.openstack.org/#!/story/2005088 To fulfil these requirements, we started with evaluating tools for the host OS. These included: 1. cveman * this tool is hardcoded to work for CLR Linux. This does not meet the requirement to understand CVEs for CentOS and Ubuntu. 2. cve-check-tool / cve-bin-tool * OS agnostic. * Both of these tools are up-to-date with NVD * Identified 10% of known CVEs * Required a significant amount of manual work to extract a useful report. 1. vuls * Understands specific OSs including CentOS and Ubuntu * All data required to make decisions is provided in the report; easy to extract * Identified 90% of known CVEs Based on this, we are planning to proceed with vuls for the initial host OS reports. We have explored a couple of open source scanners on the container scan side: 1. Anchore Engine * Understands specific OSs including CentOS and Ubuntu * A stand-alone tool * CLI only with open source; GUI with commercial version 2. CoreOS Clair * Understands specific OSs including CentOS and Ubuntu * Stand-alone or integrated with a repository like Harbor * May have issues integrating into a dashboard Both scanners yielded similar results identifying an CVE which needs to be corrected. Both scanners have some limitations with CentOS which we are exploring further. It seems they only identify CVEs which have already been fixed in CentOS. This is due to the nature of the CentOS community CVE database. Currently we are learning towards Clair since It does have integration with repositories and correlates quite well to the results we are seeing from vuls. A big thanks to Victor Rodriguez Bahena and Irene Chen for helping with this effort. Regards, Ken Y -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brent.Rowsell at windriver.com Wed Feb 27 02:13:14 2019 From: Brent.Rowsell at windriver.com (Rowsell, Brent) Date: Wed, 27 Feb 2019 02:13:14 +0000 Subject: [Starlingx-discuss] Is there any plan of containerize the flock services ? In-Reply-To: References: Message-ID: <3E6E6B86-E9C2-4159-B3B4-9105C79700D5@windriver.com> Hi Victor, For R2 only the openstack and some of it’s supporting services will be containerized. A longer term objective is to containerize as much of the flock services as possible. This is a candidate for the next release and will be discussed as part of the R3 planning later this year. Brent Sent from my iPhone > On Feb 26, 2019, at 11:59 AM, Victor Rodriguez wrote: > > Hi Frank and STX community > > Based on the presentation discuss during phoenix meeting last January > I had the impression that flock services were meant to be on the host > OS where the containers are running, is this still valid for the long > term? > > I am asking this because on today multi-OS meeting we present the > following architecture/plan: > > https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7OYUBNdJyY-5ZvDc/edit?usp=sharing > > Where we are considering the task of build all the flock services on > Ubuntu, However, based on this task: > > https://storyboard.openstack.org/#!/story/2004008 > > Gives me the impression that there is a plan for reducing the number > of flock services running on the host OS, If that is the case, Could > you please share the list of what flock services that you have in mind > to put in a container? this will help us to reduce the list of > packages we need to build. > > On the same topic, for the none open stack packages like systemd, bash > or python, do you have the list of packages that need to run outside > the containers on the host OS? Having this exact list of packages will > help us to focus on the exact packages to build on Ubuntu. > > Regards > > Victor Rodriguez > > _______________________________________________ > 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 Wed Feb 27 03:28:22 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Wed, 27 Feb 2019 03:28:22 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190225 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9D58D@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-25 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 36 TCs [PASS] Sanity Platform In Development Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 26 TCs [PASS] | 08 TCs [FAIL] Sanity Platform 02 TCs [PASS] TOTAL: [ 32 TCs PASS | 08 TCs FAIL ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 24 TCs [PASS] | 12 TCs [FAIL] Sanity Platform In Development TOTAL: [ 24 TCs PASS | 12 TCs [FAIL] ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Standard Local Storage (2+2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development ------------------------------------------------------------------ Instances are creating with SUSPENDED status and cannot be set as ACTIVE. When power status of instances were changed, it cannot be returned as ACTIVE. Will check with today ISO, if issue is still present a LP will be created. Sanity failed since cannot create instances due to pods are not running on computes. Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1817723 Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From dangtrinhnt at gmail.com Wed Feb 27 06:14:40 2019 From: dangtrinhnt at gmail.com (Trinh Nguyen) Date: Wed, 27 Feb 2019 15:14:40 +0900 Subject: [Starlingx-discuss] OpenInfra Day Vietnam 2019 - pre-CFP Message-ID: Hello, This is the pre-calling for presentations at the OpenInfra Day in Vietnam this year. If you love to visit Hanoi , the capital of Vietnam, and share your passion for the Open Infrastructure of any topic (container, CI, deployment, edge computing, etc.), please let me know by replying to this email. Below is the tentative information of the event: - Date: 31 August 2019 - Location: Hanoi, Vietnam We are working with the OpenStack Foundation to organize the Upstream Institute at the day so this will be a great opportunity for potential contributors to come and learn. There is also a couple of PTLs and projects core members have shown their interest in visiting Hanoi for this event. We will send out the official call-for-presentations after we've done with the logistic vendors and It would be around the beginning of May or sooner. If you have any questions, please do not hesitate to contact me. See you in Hanoi :) Bests, On behalf of VietOpenInfra Group. P/S: Have a look at our last OpenInfra Day: https://2018.vietopenstack.org/ -- *Trinh Nguyen* *www.edlab.xyz * -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbuil at suse.com Wed Feb 27 08:46:40 2019 From: mbuil at suse.com (Manuel Buil) Date: Wed, 27 Feb 2019 09:46:40 +0100 Subject: [Starlingx-discuss] Where to find documentation for stx- projects Message-ID: <1551257200.2404.15.camel@suse.com> Hi, I would like to understand more about stx-distcloud and stx-nfv but unfortunately, I can't find a lot of documentation. The wiki pages don't have much content: https://wiki.openstack.org/wiki/StarlingX/NFV https://wiki.openstack.org/wiki/StarlingX/DistCloud either the docs.io : https://docs.starlingx.io/stx-nfv/index.html https://docs.starlingx.io/stx-distcloud/index.html And the README does not have anything: https://github.com/openstack/stx-nfv https://github.com/openstack/stx-distcloud I wonder if there is another place where the docs are stored or if maybe documentation will be created in the next months. I wanted to get an idea of the general architecture of them and perhaps have a basic guide, so that I could try out those projects. Thanks, Manuel From ildiko.vancsa at gmail.com Wed Feb 27 09:09:36 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 27 Feb 2019 10:09:36 +0100 Subject: [Starlingx-discuss] Blog post ideas In-Reply-To: <9B0641DD-F520-4DAD-BAB5-49077DA3362E@intel.com> References: <97460AEB-8B0C-4BF9-A3B7-C9895BFE3A28@gmail.com> <1CC096B2-9953-4560-810C-F282BADD0565@intel.com> <348326D5-8031-4586-B0FC-355F497332C9@gmail.com> <9B0641DD-F520-4DAD-BAB5-49077DA3362E@intel.com> Message-ID: Hi Erich, The StarlingX website including the blog lives on GitHub. You can create a pull request to add a new blog post as a new file under the blog folder here: https://github.com/StarlingXWeb/starlingx-website/tree/master/site/blog You can find the other blog posts there to see how the markup language looks like. It should be easy to format, but if you have any questions I’m happy to help. If you would like more people to review you can send the link to the PR to the mailing list for instance. We can also utilize the community marketing planning calls for review if that would be a preference. Does this help? Thanks, Ildikó > On 2019. Feb 26., at 23:11, Cordoba Malibran, Erich wrote: > > Sure Ildiko, I'd like to help with the blog post. > > What is the process for writing up? Do I need to send a review in some repository or is a different process? > > Thanks in advance! > > -Erich > > On 2/26/19, 7:23 AM, "Ildiko Vancsa" wrote: > > Hi Erich, > > I like the idea. > > We can make “Getting Started” as a series and build could be one post considering it to be a step-by-step guide, can add screenshots, etc. What do you think? > > Would you be interested in writing it up as well? > > Thanks, > Ildikó > > >> On 2019. Feb 26., at 14:03, Cordoba Malibran, Erich wrote: >> >> >> >> On 2/26/19, 6:55 AM, "Ildiko Vancsa" wrote: >> >> Hi, >> >> As a follow-up from last week’s community marketing planning call I would like to draw your attention to the StarlingX blog[1]. >> >> We would like to make sure that we have new content frequently to highlight news, roadmap items, new features and any further topics the community finds valuable to share. >> >> On the last call we came up with the following ideas: >> >> * Hands-on workshop[2] “advertisement” for the Denver Summit >> * Packet PoC/testing activity - blog post series? >> * StarlingX in OPNFV Pharos labs (Ildikó to drive) >> * Highlighting Kubernetes part of StarlingX and the roadmap for containerization as well as container support >> * Getting started with StarlingX - (Jeff to coordinate) >> * Community participation >> * How to deploy and use StarlingX >> * Simplex and duplex model details >> * Use cases? - (Jeff to coordinate) >> * Highlight StarlingX in context around use cases (industrial, telco, etc.) >> * How to use the platform >> * What benefits it gives >> >> >> Hi Ildiko, >> >> I would suggest a "How to build your own StarlingX" topic, not sure if part of the Getting started or as a more advanced topic. >> >> -Erich >> >> > > > From marcel at schaible-consulting.de Wed Feb 27 11:16:40 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 27 Feb 2019 12:16:40 +0100 (CET) Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface In-Reply-To: <7449AA0F-8E2F-4A93-8563-FFDB14731C38@intel.com> References: <916898801.387370.1551201057012@communicator.strato.com> <7449AA0F-8E2F-4A93-8563-FFDB14731C38@intel.com> Message-ID: <1087842854.428537.1551266200685@communicator.strato.com> Hi Erich, thanks for your reply. Where did you set the variable? Marcel > "Cordoba Malibran, Erich" hat am 26. Februar 2019 um 23:08 geschrieben: > > > Hi Marcel, > > I had faced the same issue following these steps[0], I'm not sure if this is the same case. > Check the section "Configure Data Interfaces for Controller-1". > > In my case my network device was "ens3" not "enp0s3", setting this variable fixed the issue for me. > > OAM_IF=ens3 > > I hope this can help > > -Erich > > On 2/26/19, 11:11 AM, "Marcel Schaible" wrote: > > Hi, > > I need help understanding this issue: > > After configuring according to the installation guide lines I cannot unlock controller-0, because > of a missing oam interface: > > root at localhost ~(keystone_admin)]# system host-unlock controller-0 > Can not unlock a controller host without an oam interface. Add an oam interface before re-attempting this command. > > > The command > > [root at localhost ~(keystone_admin)]# system network-list > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > | id | uuid | name | type | dynamic | pool_uuid | > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > | 2 | 4d532cb8-01f6-463d-8727-2884a65e5068 | pxeboot | pxeboot | True | 70f7017b-83b4-47ba-b414-b5098ad1cfd0 | > | 3 | 86224548-3c59-45ff-a244-349850e92168 | oam | oam | False | 81febeed-1c71-4fa0-92d4-e92a98e61c51 | > | 1 | cf644862-61ed-4760-ae95-1d4305add490 | mgmt | mgmt | True | ae271028-9814-4757-981b-396862cf2deb | > | 4 | e696bc41-b460-43c7-ba15-bc90a1b2e78e | multicast | multicast | False | 442b1b92-41fa-4b46-9560-88f930928578 | > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > > > shows the oam interface. > > Is there in issue with static ip? > > Any idea is welcome! > > Thanks > Marcel > > _______________________________________________ > 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 Wed Feb 27 14:16:38 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Wed, 27 Feb 2019 14:16:38 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190225 In-Reply-To: <8557B550001AFB46A43A0CCC314BF85153C9D58D@FMSMSX108.amr.corp.intel.com> References: <8557B550001AFB46A43A0CCC314BF85153C9D58D@FMSMSX108.amr.corp.intel.com> Message-ID: Juan Carlos: Thanks for sending these out daily so we can see the status of container sanity when using a proxy/docker mirror configuration. Numan/Yang: Can you also send out a summary of container sanity for configs that do not use a proxy nor a docker mirror? Frank From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com] Sent: Tuesday, February 26, 2019 10:28 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190225 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Feb-25 (link) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 36 TCs [PASS] Sanity Platform In Development Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 26 TCs [PASS] | 08 TCs [FAIL] Sanity Platform 02 TCs [PASS] TOTAL: [ 32 TCs PASS | 08 TCs FAIL ] Duplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 24 TCs [PASS] | 12 TCs [FAIL] Sanity Platform In Development TOTAL: [ 24 TCs PASS | 12 TCs [FAIL] ] Standard Non Storage (2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development Standard Local Storage (2+2+2) Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack [FAIL] Sanity Platform In Development ------------------------------------------------------------------ Instances are creating with SUSPENDED status and cannot be set as ACTIVE. When power status of instances were changed, it cannot be returned as ACTIVE. Will check with today ISO, if issue is still present a LP will be created. Sanity failed since cannot create instances due to pods are not running on computes. Launchpad opened: https://bugs.launchpad.net/starlingx/+bug/1817723 Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From cindy.xie at intel.com Wed Feb 27 14:35:38 2019 From: cindy.xie at intel.com (Xie, Cindy) Date: Wed, 27 Feb 2019 14:35:38 +0000 Subject: [Starlingx-discuss] Notes: Weekly StarlingX non-OpenStack Distro meeting, 2/27 Message-ID: <2FD5DDB5A04D264C80D42CA35194914F35EA4900@SHSMSX104.ccr.corp.intel.com> Agenda & Notes for 2/27 meeeting: 1. Ceph upgrade plan/status (Ovidiu, Daniel & Changcheng) Tingjie: build issues: - size is 1GB bigger than previous one (2.82G vs 1.87G). the new Ceph image include the debug info. Tingjie has a patch to strip the debug section and the new size is 1.88GB. patch is uploaded in the shared feature branch, expecting Ovidiu to review; - incremental compiling of Ceph: reduce the build time if not build Ceph every-time. Patch uploaded and verified locally. https://review.openstack.org/#/c/638698/ - src options: download tar ball or download the git src repo with manifest. External release w/ src somewhere with SHA commit ID. we can do the build with this tar.gz. This is for stable archieve purpose. Will use tar ball download for Ceph and AR for Tingjie to update the current way of setting up the repo. Ovidiu: Daniel is able to bring up 2+2+2 with WA regarding Ceph RESTful API is brought up. Plan is to get the existing code working get rid of the WA. Will do more testing with K8s up. Changcheng: beside get rid of restful AP WA. radosgw service issue remains, Ovidiu may need to enable it. Yong was trying to enable but failed and blocking control0 unlock. Ceph meeting tomorrow for detail technical discussion. purpose on week by week plan till the feature branch merged to master. 2. CentOS 7.6 upgrade test status (Numan) test report from Numan shows no blocking issue for 7.6 branch; WR internal IT issue blocks the signing image testing. Numan is using the unsigned image to conduct the remaining testing. Will send out the report after that. Expecting to have test finish by end of this week. agreement that signing image testing is not block 7.6 branch cut-over. kernel version: 3.10.0.957 3. OVS upgrade planning (Shuicheng) OVS 2.11 released just couple of days ago. Will upgrade OVS to latest version. Will do it in the feature branch first. previously we use src RPM, the new OVS 2.11 we do not have SRC RPM, so we will use tar ball from OVS upstream directly (OVS 2.11, DPDK 18.11). Plan to finish the rebase work in 2 weeks. and then handle to network sub-project team for functional testing and Ada will do network related system testing. Elio is working w/ network team for defining the testing cases to testing OVS/DPDK and with good progress. 4. Opens (all) N/A -----Original Appointment----- From: Xie, Cindy Sent: Monday, November 5, 2018 2:27 PM To: Xie, Cindy; Troyer, Dean; Zhu, Vivian; Hu, Yong; Lin, Shuicheng; Shang, Dehao; Somerville, Jim; Wold, Saul; Sun, Austin; Jones, Bruce E; Liu, ZhipengS; 'Rowsell, Brent'; 'Khalil, Ghada'; starlingx-discuss at lists.starlingx.io; Waheed, Numan Cc: Perez Carranza, Jose; 'Hellmann, Gil'; 'Seiler, Glenn'; 'Young, Ken'; Arce Moreno, Abraham; Cobbley, David A; Fang, Liang A; 'Eslimi, Dariush'; Hu, Wei W; Martinez Monroy, Elio; 'Waines, Greg'; Lara, Cesar; Armstrong, Robert H; 'Chen, Jacky'; Martinez Landa, Hayde; 'Poncea, Ovidiu'; Perez Rodriguez, Humberto I; Gomez, Juan P; Shuquan Huang Subject: Weekly StarlingX non-OpenStack Distro meeting When: Wednesday, February 27, 2019 6:00 AM-7:00 AM (UTC-08:00) Pacific Time (US & Canada). 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 From Numan.Waheed at windriver.com Wed Feb 27 14:56:07 2019 From: Numan.Waheed at windriver.com (Waheed, Numan) Date: Wed, 27 Feb 2019 14:56:07 +0000 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> Message-ID: <3CAA827B7A79BA46B15B280EC82088FE4827A6CD@ALA-MBD.corp.ad.wrs.com> Review request for Python Bases VBox Installer has been restored. Kindly remove your -2 votes and add the comments that you would like to get fixed with -1. Some of the earlier comments have been already addressed. If there are new comments, we will address them accordingly. Thanks, Numan -----Original Message----- From: Saul Wold Sent: February-25-19 2:51 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Python Based VBox Installer On 2/25/19 8:11 AM, Curtis wrote: > On Mon, Feb 25, 2019 at 10:51 AM Penney, Don > wrote: > > > > > -----Original Message----- > > From: Saul Wold [mailto:sgw at linux.intel.com > ] > > Sent: Thursday, February 21, 2019 6:19 PM > > To: starlingx-discuss at lists.starlingx.io > > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > >> > > >> > > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > > >> iver.com > wrote: > > >>> Hi, > > >>> > > >>> I see Spec as a high level design for a code that going to be > > >>> developed, and to make sure it aligns with how community is going > > >>> to use it and to make everybody aware of what is going to do, so > > >>> others can chime in and say things that can address multiple > needs > > >>> and influence its design. Let's call this apple. > > >>> > > >>> Now I see the case of a code that has been developed before even > > >>> the community existed, and now been presented to the community to > > >>> fill a gap and improve productivity, no time to change the design > > >>> and would be up to community to accept or reject it as is. A case > > >>> of donation really, I call this one Orange. > > >>> > > >>> For Orange I think Spec is not the right word, we need a > > >>> wiki/readme to see what it does, and how to use it. It is too > late > > >>> to produce a spec to influence the design. > > >>> > > >> > > >> OpenStack Operators have a tools landing repository [1] that > > >> didn't/doesn't have the same level of requirements the rest of the > > >> OpenStack code typically does, so organizations could open source > > >> internal. potentially untested, scripts but not have to > necessarily > > >> adhere to all of the usual requirements. Over time the code in > that > > >> repository could be improved and moved out once it made sense. > > >> > > >> I think it's worthwhile to have useful internal code open sourced, > > >> and in some cases make it a bit easier to do so, and if the > code/tool > > >> gets used then start improving it following general standards. > This > > >> would require a new repository. > > >> > > >> Just a thought. :) > > >> > > > > > > I really like the idea of having a new repository as a landing zone > > > where things can be stabilize over time. When I started > reviewing this > > > tool I noticed that my comments were more focused on design > (features > > > that we might not need, restructure of cli arguments and so on) > and I > > > understand that fixing this is outside of the scope of sharing an > > > internal tool. > > > > > > So, should be go in the path of creating a new repository? or > can we > > > use an "experimental" folder within stx-tools? > > > > > > What do you think about this? > > > > > I think that this can land in the stx-tools directory along with the > > other deployment scripts. As was pointed out in the meeting this > > morning, this code has been in use within WindRiver for a while > now and > > they are making it available to the community. > > > > I think that the initial PR needed to have a better commit message > > explaining this and a little more thought put into the request > before it > > got reviewed, such as removing the .pyc files, licensing, > documentation, > > the first two where show stopper for me, but easily fixed, > documentation > > could be added later. > > > > Sau! > > > > Things like the inadvertent inclusion of pyc files (which were > already noted in multiple comments in the review) and missing > license identifiers seem to be minor and easily correctable > mistakes, and maybe not completely unexpected for a “new > contributor”. As well, I had also noted in a review comment that > this was a long-existing tool that was being published, referencing > the email from Numan and asking for the commit message to be updated > to explain this. > > As well, note that this was an optional productivity aid. It does > not impact the build, it does not impact any software. It is a tool > to help people launch StarlingX in a VirtualBox environment, to aid > them in installing and configuring the system. Nobody is required to > use it. > > With that said, the review had been given two -2 votes from cores. > As I understand it, this is not a minor thing. From the openstack > guidelines, a -2 “is to indicate to the submitter that any further > time they spend on the change will almost certainly be wasted.” > Having two -2 votes on the update is very significant, thus the > decision to abandon the review. The openstack guidelines describing > -1 and -2 votes seems pretty clear here: > > https://docs.openstack.org/project-team-guide/review-the-openstack-way > .html#code-review-minus-2 > > > Sounds like we need to come to a consensus as to when a -2 is > appropriate. I personally don't think a -2 is appropriate for a first > contribution, regardless of circumstances. Obviously we can't commit > .pyc files and need licensing, but I definitely would prefer not to > see -2s in this situation. > As I mentioned above, I was probably over zealous on marking it -2, consider it withdrawn. > I think this code is important and we need to get this back on track. > This is a good "teachable moment" maybe for all sides? :) > Lesson learned! Sau! > Thanks, > Curtis > > Cheers, > Don. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > -- > Blog: serverascode.com > > _______________________________________________ > 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 himanshugoyal500 at gmail.com Wed Feb 27 15:10:26 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Wed, 27 Feb 2019 20:40:26 +0530 Subject: [Starlingx-discuss] Onap with starlingX Message-ID: Hi Team, Can we use ONAP on top of StarlingX directly. or I need to change any configuration with starlingX ? Currently we deployed starlingX with 2 servers( 1 controller + 1 compute) machine. Regards, Himanshu Goyal -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Wed Feb 27 15:24:02 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 27 Feb 2019 10:24:02 -0500 Subject: [Starlingx-discuss] Python Based VBox Installer In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE4827A6CD@ALA-MBD.corp.ad.wrs.com> References: <3CAA827B7A79BA46B15B280EC82088FE48276E7B@ALA-MBD.corp.ad.wrs.com> <22aae8d5b37711dae49e5c12c93cace0257c9a89.camel@intel.com> <35d1fd0feb3c566019a91e7ea9aa1364d02946b9.camel@intel.com> <6703202FD9FDFF4A8DA9ACF104AE129FBA448ED7@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE4827A6CD@ALA-MBD.corp.ad.wrs.com> Message-ID: On Wed, Feb 27, 2019 at 9:57 AM Waheed, Numan wrote: > Review request for Python Bases VBox Installer has been restored. Kindly > remove your -2 votes and add the comments that you would like to get fixed > with -1. > > Some of the earlier comments have been already addressed. If there are new > comments, we will address them accordingly. > Thanks! It'll be great to see this code get merged. :) Thanks, Curtis > > Thanks, > > Numan > > -----Original Message----- > From: Saul Wold > Sent: February-25-19 2:51 PM > To: starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > On 2/25/19 8:11 AM, Curtis wrote: > > On Mon, Feb 25, 2019 at 10:51 AM Penney, Don > > wrote: > > > > > > > > > -----Original Message----- > > > From: Saul Wold [mailto:sgw at linux.intel.com > > ] > > > Sent: Thursday, February 21, 2019 6:19 PM > > > To: starlingx-discuss at lists.starlingx.io > > > > > Subject: Re: [Starlingx-discuss] Python Based VBox Installer > > > > > > > > > > > > On 2/21/19 10:19 AM, Cordoba Malibran, Erich wrote: > > > > On Thu, 2019-02-21 at 09:15 -0500, Curtis wrote: > > > >> > > > >> > > > >> On Thu, Feb 21, 2019 at 8:46 AM Eslimi, Dariush > > > > >> iver.com > wrote: > > > >>> Hi, > > > >>> > > > >>> I see Spec as a high level design for a code that going to be > > > >>> developed, and to make sure it aligns with how community is > going > > > >>> to use it and to make everybody aware of what is going to do, > so > > > >>> others can chime in and say things that can address multiple > > needs > > > >>> and influence its design. Let's call this apple. > > > >>> > > > >>> Now I see the case of a code that has been developed before > even > > > >>> the community existed, and now been presented to the > community to > > > >>> fill a gap and improve productivity, no time to change the > design > > > >>> and would be up to community to accept or reject it as is. A > case > > > >>> of donation really, I call this one Orange. > > > >>> > > > >>> For Orange I think Spec is not the right word, we need a > > > >>> wiki/readme to see what it does, and how to use it. It is too > > late > > > >>> to produce a spec to influence the design. > > > >>> > > > >> > > > >> OpenStack Operators have a tools landing repository [1] that > > > >> didn't/doesn't have the same level of requirements the rest of > the > > > >> OpenStack code typically does, so organizations could open > source > > > >> internal. potentially untested, scripts but not have to > > necessarily > > > >> adhere to all of the usual requirements. Over time the code in > > that > > > >> repository could be improved and moved out once it made sense. > > > >> > > > >> I think it's worthwhile to have useful internal code open > sourced, > > > >> and in some cases make it a bit easier to do so, and if the > > code/tool > > > >> gets used then start improving it following general standards. > > This > > > >> would require a new repository. > > > >> > > > >> Just a thought. :) > > > >> > > > > > > > > I really like the idea of having a new repository as a landing > zone > > > > where things can be stabilize over time. When I started > > reviewing this > > > > tool I noticed that my comments were more focused on design > > (features > > > > that we might not need, restructure of cli arguments and so on) > > and I > > > > understand that fixing this is outside of the scope of sharing > an > > > > internal tool. > > > > > > > > So, should be go in the path of creating a new repository? or > > can we > > > > use an "experimental" folder within stx-tools? > > > > > > > > What do you think about this? > > > > > > > I think that this can land in the stx-tools directory along with > the > > > other deployment scripts. As was pointed out in the meeting this > > > morning, this code has been in use within WindRiver for a while > > now and > > > they are making it available to the community. > > > > > > I think that the initial PR needed to have a better commit message > > > explaining this and a little more thought put into the request > > before it > > > got reviewed, such as removing the .pyc files, licensing, > > documentation, > > > the first two where show stopper for me, but easily fixed, > > documentation > > > could be added later. > > > > > > Sau! > > > > > > > Things like the inadvertent inclusion of pyc files (which were > > already noted in multiple comments in the review) and missing > > license identifiers seem to be minor and easily correctable > > mistakes, and maybe not completely unexpected for a “new > > contributor”. As well, I had also noted in a review comment that > > this was a long-existing tool that was being published, referencing > > the email from Numan and asking for the commit message to be updated > > to explain this. > > > > As well, note that this was an optional productivity aid. It does > > not impact the build, it does not impact any software. It is a tool > > to help people launch StarlingX in a VirtualBox environment, to aid > > them in installing and configuring the system. Nobody is required to > > use it. > > > > With that said, the review had been given two -2 votes from cores. > > As I understand it, this is not a minor thing. From the openstack > > guidelines, a -2 “is to indicate to the submitter that any further > > time they spend on the change will almost certainly be wasted.” > > Having two -2 votes on the update is very significant, thus the > > decision to abandon the review. The openstack guidelines describing > > -1 and -2 votes seems pretty clear here: > > > > https://docs.openstack.org/project-team-guide/review-the-openstack-way > > .html#code-review-minus-2 > > > > > > Sounds like we need to come to a consensus as to when a -2 is > > appropriate. I personally don't think a -2 is appropriate for a first > > contribution, regardless of circumstances. Obviously we can't commit > > .pyc files and need licensing, but I definitely would prefer not to > > see -2s in this situation. > > > As I mentioned above, I was probably over zealous on marking it -2, > consider it withdrawn. > > > I think this code is important and we need to get this back on track. > > This is a good "teachable moment" maybe for all sides? :) > > > Lesson learned! > > Sau! > > > > Thanks, > > Curtis > > > > Cheers, > > Don. > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > > > > > > > -- > > Blog: serverascode.com > > > > _______________________________________________ > > 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 > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Wed Feb 27 15:35:43 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Wed, 27 Feb 2019 15:35:43 +0000 Subject: [Starlingx-discuss] Duplex: Cannot unlock controller-0, because of missing OAM interface In-Reply-To: <1087842854.428537.1551266200685@communicator.strato.com> References: <916898801.387370.1551201057012@communicator.strato.com> <7449AA0F-8E2F-4A93-8563-FFDB14731C38@intel.com> <1087842854.428537.1551266200685@communicator.strato.com> Message-ID: Hi Marcel, If you look into the "Provisioning the second AIO controller" section, there is a script to setup the network. This looks like this: source /etc/platform/openrc export COMPUTE='controller-1' PHYSNET0='physnet0' PHYSNET1='physnet1' OAM_IF=enp0s3 DATA0IF=eth1000 DATA1IF=eth1001 NOWRAP="--nowrap" echo ">>> Configuring OAM Network" system host-if-modify -n oam0 -c platform --networks oam ${COMPUTE} $(system host-if-list -a $COMPUTE $NOWRAP | awk -v OAM_IF=$OAM_IF '{if ($4 == OAM_IF) { print $2;}}') So you can just run the "system host-if-modify" command with the settings for your system. In my case I needed to change the value of OAM_IF. -Erich On 2/27/19, 5:17 AM, "Marcel Schaible" wrote: Hi Erich, thanks for your reply. Where did you set the variable? Marcel > "Cordoba Malibran, Erich" hat am 26. Februar 2019 um 23:08 geschrieben: > > > Hi Marcel, > > I had faced the same issue following these steps[0], I'm not sure if this is the same case. > Check the section "Configure Data Interfaces for Controller-1". > > In my case my network device was "ens3" not "enp0s3", setting this variable fixed the issue for me. > > OAM_IF=ens3 > > I hope this can help > > -Erich > > On 2/26/19, 11:11 AM, "Marcel Schaible" wrote: > > Hi, > > I need help understanding this issue: > > After configuring according to the installation guide lines I cannot unlock controller-0, because > of a missing oam interface: > > root at localhost ~(keystone_admin)]# system host-unlock controller-0 > Can not unlock a controller host without an oam interface. Add an oam interface before re-attempting this command. > > > The command > > [root at localhost ~(keystone_admin)]# system network-list > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > | id | uuid | name | type | dynamic | pool_uuid | > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > | 2 | 4d532cb8-01f6-463d-8727-2884a65e5068 | pxeboot | pxeboot | True | 70f7017b-83b4-47ba-b414-b5098ad1cfd0 | > | 3 | 86224548-3c59-45ff-a244-349850e92168 | oam | oam | False | 81febeed-1c71-4fa0-92d4-e92a98e61c51 | > | 1 | cf644862-61ed-4760-ae95-1d4305add490 | mgmt | mgmt | True | ae271028-9814-4757-981b-396862cf2deb | > | 4 | e696bc41-b460-43c7-ba15-bc90a1b2e78e | multicast | multicast | False | 442b1b92-41fa-4b46-9560-88f930928578 | > +----+--------------------------------------+-----------+-----------+---------+--------------------------------------+ > > > shows the oam interface. > > Is there in issue with static ip? > > Any idea is welcome! > > Thanks > Marcel > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > > From serverascode at gmail.com Wed Feb 27 15:37:23 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 27 Feb 2019 10:37:23 -0500 Subject: [Starlingx-discuss] Onap with starlingX In-Reply-To: References: Message-ID: On Wed, Feb 27, 2019 at 10:11 AM Himanshu Goyal wrote: > Hi Team, > > Can we use ONAP on top of StarlingX directly. or I need to change any > configuration with starlingX ? > > Currently we deployed starlingX with 2 servers( 1 controller + 1 compute) > machine. > I guess it depends on how you want to deploy and manage ONAP. Would you be using ONAP Operations Manager (OOM)? It deploys into Kubernetes (k8s) and has a fair number of requirements. Also it depends on what components of ONAP you want to deploy. ONAP has many pieces and projects. I've deployed ONAP via OOM a few times in lab situations. From my perspective there would be two ways to use OOM with StarlingX (STX), either 1) use the Kubernetes that comes with STX or 2) deploy a Kubernetes cluster onto virtual machines created in the OpenStack deployment of STX. My feeling is that option #1 makes the most sense (to me anyways) but I'm not sure where we are in terms of that use case yet in the project as we have just recently moved to providing k8s. The other thing to be aware of is that the entire ONAP suite is quite large...hundreds of containers, I think last time I deployed it was ~190. Depending on the resources available in the 2 node deployment there may be not be enough to run all of ONAP. But if you don't need all of it it can be smaller. I think ONAP on STX is an important use case so if you have more requirements you could describe, please do so that we can work towards ensuring STX is a great place to run systems like ONAP. :) Thanks, Curtis > > Regards, > Himanshu Goyal > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Wed Feb 27 15:40:34 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Wed, 27 Feb 2019 15:40:34 +0000 Subject: [Starlingx-discuss] Community call notes Feb 27 2019 Message-ID: <9A85D2917C58154C960D95352B22818BC3AD6CA4@fmsmsx121.amr.corp.intel.com> Agenda and notes for the Feb 27th call * Denver Summit * PTG attendance discount expires today! * Project Update and Onboarding sessions - covered? Yes. * Conference schedule out - congrats to the folks who have papers accepted on StarlingX * Release * Line by line through the release plan? Cover every other week * Container update ? Looking brighter - content is in, getting to stability on all 4 configs is the current work. The no-proxy/no-mirror config AIO is clean, the standard and storage configs now have good Sanity results, looking to see that repeat today. On the proxy side there are still issues around DNS, Mingyuan has a fix in flight. Please review https://review.openstack.org/#/c/639619/ asap. ? If the no-proxy configs remain clean we will cut-over this Friday. ? Outstanding bugs: https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.containers, Of the 3 High bugs - Mingyuan's fix addresses one, we believe that the CentOS 7.6 kernel update will address the other two. WR has two systems running CentOS 7.6 with containers enabled to see if the problems reproduce. No known way to repro the two issues (595 and 541) today. * CentOS 7.6 ? Seems to be stable. Current plan is to merge +1 week after the f/stein branch merges. Target 3/11. * Bug trend https://docs.google.com/spreadsheets/d/1DZZgqrCIL6wxv51_yFBk6Lfmtf1AqPD6z7e5hEs3prU/ * Other topics * Planning for the next release? Defer to next week. * Open ARs ? https://docs.google.com/spreadsheets/d/1F-JKh8_gLlUzbrUJRbsf4u65yBGVBl8HGe-RnUQoyc4/edit?usp=sharing ? AR owners are asked to update their ARs on this sheet -------------- next part -------------- An HTML attachment was scrubbed... URL: From yang.liu at windriver.com Wed Feb 27 16:35:47 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Wed, 27 Feb 2019 16:35:47 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test (no-proxy) - ISO 20190225 Message-ID: <19C65A6E92EA384D809B1772130CD7F862186F23@ALA-MBD.corp.ad.wrs.com> Load: f/stein 2019-02-25 ( http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190225T191350Z/outputs/iso/ ) Environment: Bare metal, no proxy, no mirror Simplex ----------- Overall Status: Yellow Pass Rate: 20/22 (90.9%) Issues: 1. 1817212: nova cmd fails intermittently with connection error 2. 1816177: AIO-SX: stx-openstack application failed after lock/unlock controller (Pods were all healthy even though app failed. Workaround: reapply the app) Duplex ---------- Not Run Standard (2+3) -------------------- Overall Status: Yellow Pass Rate: 34/35 (97.1%) Issues: 1. 1817770: stx-openstack reapply from controller-1 stuck at applying armada-manifest (Intermittent - repeated this test 10 times, only seen in very first reapply from controller-1) Notes: - Force reboot controller test case skipped due to current known limitation with containers Dedicated Storage (2+2+2) ------------------------------------ Overall Status: Yellow Pass Rate: 32/35 (91.4%) Issues: 1. 1817770: stx-openstack reapply from controller-1 stuck at applying armada-manifest 2. One of the coredns pods failed at Pod Predicate MatchNodeSelector since install and config. It doesn't seem to have negative impact on rest of the sanity test cases. Notes: - Force reboot controller test case skipped due to current known limitation with containers ===================== Latest Recommended Load ===================== http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190225T191350Z/outputs/iso/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Feb 27 16:40:46 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 27 Feb 2019 10:40:46 -0600 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! Message-ID: <5C76BD8E.4070504@openstack.org> Hi Everyone - A quick reminder that we are accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas through the Summit CFP tool [3] through March 8th. Don't forget to put your brainstorming etherpad up on the Denver Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. If you have questions or concerns, please reach out to speakersupport at openstack.org . Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/denver-2019/ [3] https://www.openstack.org/summit/denver-2019/call-for-presentations [4] https://wiki.openstack.org/wiki/Forum/Denver2019 ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Wed Feb 27 17:00:20 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 27 Feb 2019 11:00:20 -0600 Subject: [Starlingx-discuss] Is there any plan of containerize the flock services ? In-Reply-To: <3E6E6B86-E9C2-4159-B3B4-9105C79700D5@windriver.com> References: <3E6E6B86-E9C2-4159-B3B4-9105C79700D5@windriver.com> Message-ID: On Tue, Feb 26, 2019 at 8:14 PM Rowsell, Brent wrote: > > Hi Victor, > > For R2 only the openstack and some of it’s supporting services will be containerized. > > A longer term objective is to containerize as much of the flock services as possible. This is a candidate for the next release and will be discussed as part of the R3 planning later this year. > > Brent > Thanks a lot for your repply Brent I definitely support the approach of containers, now, one question, if the goal is to containerize as much of the flock services as possible, can we have the list of what services are not going to be on containers? based on that we can minimize the efforts of packaging for Ubuntu and maybe help more on the containerization of the flock services. The more we have in containers the easier is for us to migrate to other OS ( the packages that might need be ported to other OS might be: kernel, horizon, and keystone right ? ) So far we have a POC of fm-manager and fm-common [1], what I don't want is to spend time building debs that will not be useful in the future. Regards Victor Rodriguez [1] https://github.com/marcelarosalesj/stx-packaging/commit/4bf237bf5f97e68b96a5be14a3e260467190e767 > Sent from my iPhone > > > On Feb 26, 2019, at 11:59 AM, Victor Rodriguez wrote: > > > > Hi Frank and STX community > > > > Based on the presentation discuss during phoenix meeting last January > > I had the impression that flock services were meant to be on the host > > OS where the containers are running, is this still valid for the long > > term? > > > > I am asking this because on today multi-OS meeting we present the > > following architecture/plan: > > > > https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7OYUBNdJyY-5ZvDc/edit?usp=sharing > > > > Where we are considering the task of build all the flock services on > > Ubuntu, However, based on this task: > > > > https://storyboard.openstack.org/#!/story/2004008 > > > > Gives me the impression that there is a plan for reducing the number > > of flock services running on the host OS, If that is the case, Could > > you please share the list of what flock services that you have in mind > > to put in a container? this will help us to reduce the list of > > packages we need to build. > > > > On the same topic, for the none open stack packages like systemd, bash > > or python, do you have the list of packages that need to run outside > > the containers on the host OS? Having this exact list of packages will > > help us to focus on the exact packages to build on Ubuntu. > > > > Regards > > > > Victor Rodriguez > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From himanshugoyal500 at gmail.com Wed Feb 27 17:06:30 2019 From: himanshugoyal500 at gmail.com (Himanshu Goyal) Date: Wed, 27 Feb 2019 22:36:30 +0530 Subject: [Starlingx-discuss] Onap with starlingX In-Reply-To: References: Message-ID: Thanks Curtis, Currently i will install my ONAP on some other servers, but can i use starlingX as a VIM(virtual Infrastructure Manager) for that & use ONAP to manage my starlingX controller & VNFs. Regards, Himanshu Goyal On Wed, Feb 27, 2019 at 9:07 PM Curtis wrote: > On Wed, Feb 27, 2019 at 10:11 AM Himanshu Goyal < > himanshugoyal500 at gmail.com> wrote: > >> Hi Team, >> >> Can we use ONAP on top of StarlingX directly. or I need to change any >> configuration with starlingX ? >> >> Currently we deployed starlingX with 2 servers( 1 controller + 1 compute) >> machine. >> > > I guess it depends on how you want to deploy and manage ONAP. Would you be > using ONAP Operations Manager (OOM)? It deploys into Kubernetes (k8s) and > has a fair number of requirements. Also it depends on what components of > ONAP you want to deploy. ONAP has many pieces and projects. > > I've deployed ONAP via OOM a few times in lab situations. From my > perspective there would be two ways to use OOM with StarlingX (STX), either > 1) use the Kubernetes that comes with STX or 2) deploy a Kubernetes cluster > onto virtual machines created in the OpenStack deployment of STX. My > feeling is that option #1 makes the most sense (to me anyways) but I'm not > sure where we are in terms of that use case yet in the project as we have > just recently moved to providing k8s. > > The other thing to be aware of is that the entire ONAP suite is quite > large...hundreds of containers, I think last time I deployed it was ~190. > Depending on the resources available in the 2 node deployment there may be > not be enough to run all of ONAP. But if you don't need all of it it can be > smaller. > > I think ONAP on STX is an important use case so if you have more > requirements you could describe, please do so that we can work towards > ensuring STX is a great place to run systems like ONAP. :) > > Thanks, > Curtis > > > >> >> Regards, >> Himanshu Goyal >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io >> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >> > > > -- > Blog: serverascode.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: From serverascode at gmail.com Wed Feb 27 17:46:34 2019 From: serverascode at gmail.com (Curtis) Date: Wed, 27 Feb 2019 12:46:34 -0500 Subject: [Starlingx-discuss] Onap with starlingX In-Reply-To: References: Message-ID: On Wed, Feb 27, 2019 at 12:06 PM Himanshu Goyal wrote: > Thanks Curtis, > > Currently i will install my ONAP on some other servers, but can i use > starlingX as a VIM(virtual Infrastructure Manager) for that & use ONAP to > manage my starlingX controller & VNFs. > Oh, yes for sure. STX deploys OpenStack so you get all the defacto standard APIs, so you get the VIM and NFVi components. Thanks, Curtis > > Regards, > Himanshu Goyal > > On Wed, Feb 27, 2019 at 9:07 PM Curtis wrote: > >> On Wed, Feb 27, 2019 at 10:11 AM Himanshu Goyal < >> himanshugoyal500 at gmail.com> wrote: >> >>> Hi Team, >>> >>> Can we use ONAP on top of StarlingX directly. or I need to change any >>> configuration with starlingX ? >>> >>> Currently we deployed starlingX with 2 servers( 1 controller + 1 >>> compute) machine. >>> >> >> I guess it depends on how you want to deploy and manage ONAP. Would you >> be using ONAP Operations Manager (OOM)? It deploys into Kubernetes (k8s) >> and has a fair number of requirements. Also it depends on what components >> of ONAP you want to deploy. ONAP has many pieces and projects. >> >> I've deployed ONAP via OOM a few times in lab situations. From my >> perspective there would be two ways to use OOM with StarlingX (STX), either >> 1) use the Kubernetes that comes with STX or 2) deploy a Kubernetes cluster >> onto virtual machines created in the OpenStack deployment of STX. My >> feeling is that option #1 makes the most sense (to me anyways) but I'm not >> sure where we are in terms of that use case yet in the project as we have >> just recently moved to providing k8s. >> >> The other thing to be aware of is that the entire ONAP suite is quite >> large...hundreds of containers, I think last time I deployed it was ~190. >> Depending on the resources available in the 2 node deployment there may be >> not be enough to run all of ONAP. But if you don't need all of it it can be >> smaller. >> >> I think ONAP on STX is an important use case so if you have more >> requirements you could describe, please do so that we can work towards >> ensuring STX is a great place to run systems like ONAP. :) >> >> Thanks, >> Curtis >> >> >> >>> >>> Regards, >>> Himanshu Goyal >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >>> >> >> >> -- >> Blog: serverascode.com >> > -- Blog: serverascode.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Feb 27 18:04:21 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 27 Feb 2019 12:04:21 -0600 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> Message-ID: <5C76D125.2040404@openstack.org> Hi Erik, We are able to extend the deadline to 11:59PM Pacific, March 10th. That should give the weekend to get any additional stragglers in and still allow the Forum Programming Committee enough time to manage the rest of the approval and publishing process in time for people's travel needs, etc... For the Ops Meetup specifically, I'd suggest going a bit broader with the proposals and offering to fill in the blanks later. For example, if something comes up and everyone agrees it should go to the Forum, just submit before the end of the Ops session. Kendall or myself would be happy to help you add details a bit later in the process, should clarification be necessary. We typically have enough spots for the majority of proposed Forum sessions. That's not a guarantee, but food for thought. Cheers, Jimmy > Erik McCormick > February 27, 2019 at 11:31 AM > Would it be possible to push the deadline back a couple weeks? I > expect there to be a few session proposals that will come out of the > Ops Meetup which ends the day before the deadline. It would be helpful > to have a little time to organize and submit things afterwards. > > Thanks, > Erik > > Jimmy McArthur > February 27, 2019 at 10:40 AM > Hi Everyone - > > A quick reminder that we are accepting Forum [1] submissions for the > 2019 Open Infrastructure Summit in Denver [2]. Please submit your > ideas through the Summit CFP tool [3] through March 8th. Don't forget > to put your brainstorming etherpad up on the Denver Forum page [4]. > > This is not a classic conference track with speakers and > presentations. OSF community members (participants in development > teams, operators, working groups, SIGs, and other interested > individuals) discuss the topics they want to cover and get alignment > on and we welcome your participation. The Forum is your opportunity > to help shape the development of future project releases. More > information about the Forum [1]. > > If you have questions or concerns, please reach out to > speakersupport at openstack.org . > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/denver-2019/ > [3] https://www.openstack.org/summit/denver-2019/call-for-presentations > [4] https://wiki.openstack.org/wiki/Forum/Denver2019 > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From marcel at schaible-consulting.de Wed Feb 27 18:16:55 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 27 Feb 2019 19:16:55 +0100 (CET) Subject: [Starlingx-discuss] OAM interface gets disabled during ovs-vsctl set Open_vSwitch . other_config:dpdk-init=true Message-ID: <758391016.459294.1551291415550@communicator.strato.com> Hi, another mysterious problem on our Artesyn Maxcore box: It looks like when during the initial come up of the controller-0 the execution of the command (as seen on the console output) ovs-vsctl set Open_vSwitch . other_config:dpdk-init=true seems to do some nasty things with the interface. The command just hangs forever and after a reboot, probably because of the watchdog the interface is dead: [ 14.880565] igb 0000:07:00.3: The NVM Checksum Is Not Valid [ 14.933308] igb: probe of 0000:07:00.3 failed with error -5 Maye be someone can shed some light what is going on in this step. Thanks Marcel From marcel at schaible-consulting.de Wed Feb 27 18:19:18 2019 From: marcel at schaible-consulting.de (Marcel Schaible) Date: Wed, 27 Feb 2019 19:19:18 +0100 (CET) Subject: [Starlingx-discuss] Add OAM manually? In-Reply-To: <1466AF2176E6F040BD63860D0A241BBD46C8D698@FMSMSX109.amr.corp.intel.com> References: <546908062.375303.1551191320112@communicator.strato.com> <026DE3C9-040D-4B77-AEA3-68CDAD96BB07@intel.com> <1466AF2176E6F040BD63860D0A241BBD46C8D698@FMSMSX109.amr.corp.intel.com> Message-ID: <148509961.459407.1551291558891@communicator.strato.com> Elio, thanks for sharing this valuable information. Marcel > "Martinez Monroy, Elio" hat am 27. Februar 2019 um 01:54 geschrieben: > > > Hello Yong and Marcel > > Yes, OAM interfaces is set during config_controller. > > And yes, you can modify OAM interface, please check following steps: > > 1. In controller-0 (active), check default OAM config > system oam-show > 2.Modify cEXT_OAM section with compatible configuration (OAM IP for controller-1) > system oam-modify oam_c1_ip=10.10.10.11 > 3. Verify that new configuration is accepted > system oam-show > 4. Verify that config_applied ID is equal for all hosts > $ system host-show > 5. Verify that config_target ID is equal for all hosts > system host-show > 6. Lock and unlock the controller-1, so config can be updated > system host-lock controller-1 > system host-show > system host-unlock controller-1 > system host-show > 7. Swact controllers. Wait until new master (controller-1) controller appeared > 8. verify that ip address for OAM interface is changed to new value and verify that oam controller IP address is changed to new address. > ssh to host > ifconfig (only for controllers) > cat /etc/hosts > 9. Verify that config_applied and config_target are equal to uuid of new applied config for new master host > system host-show > 10. lock and unlock the compute nodes one at a time, ensuring that sufficient resources are available to migrate any running instances > > Please let me know if you have more questions > > -----Original Message----- > From: Hu, Yong [mailto:yong.hu at intel.com] > Sent: Tuesday, February 26, 2019 6:40 PM > To: Marcel Schaible ; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] Add OAM manually? > > Given you have at least 2 NIC interfaces for Controller-0, and One is for OAM and another for Mgt, OAM interface will be set by "config_controller", during which you can modify the IP address. > After that, I am not aware changing OAM network is allowed. > > Could you tell what you meant about *add manually the OAM interface*? > > -Yong > > On 26/02/2019, 10:30 PM, "Marcel Schaible" wrote: > > Hi, > > how can I add manually the OAM interface before unlocking controller-0? > > Thanks > > Marcel > > _______________________________________________ > 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 jimmy at openstack.org Wed Feb 27 19:08:31 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 27 Feb 2019 13:08:31 -0600 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> Message-ID: <5C76E02F.4010906@openstack.org> Erik, I definitely understand the timeline is tight. One of the reasons that we publish the schedule so early is to enable community members to plan their schedule early, especially as there is more overlap with the main Summit Schedule in Denver. Additionally, travel approval is often predicated upon someone showing they're leading/moderating a session. Before publishing the schedule, we print a draft Forum schedule for community feedback and start promotion of the schedule, which we have to put up on the OpenStack website and apps at 5 weeks out. Extending the date beyond the 10th won't give the Forum Selection Committee enough time to complete those tasks. I think if the Ops team can come up with some high level discussion topics, we'll be happy to put some holds in the Forum schedule for Ops-specific content. diablo_rojo has also offered to attend some of the Ops sessions remotely as well, if that would help you all shape some things into actual sessions. I wish I could offer a further extension, but extending it another week would push too far into the process. Cheers, Jimmy > Erik McCormick > February 27, 2019 at 12:43 PM > Jimmy, > > I won't even get home until the 10th much less have time to follow up > with anyone. The formation of those sessions often come from > discussions spawned at the meetup and expanded upon later with folks > who could not attend. Could we at least get until 3/17? I understand > your desire to finalize the schedule, but 6 weeks out should be more > than enough time, no? > > Thanks, > Erik > Jimmy McArthur > February 27, 2019 at 12:04 PM > Hi Erik, > > We are able to extend the deadline to 11:59PM Pacific, March 10th. > That should give the weekend to get any additional stragglers in and > still allow the Forum Programming Committee enough time to manage the > rest of the approval and publishing process in time for people's > travel needs, etc... > > For the Ops Meetup specifically, I'd suggest going a bit broader with > the proposals and offering to fill in the blanks later. For example, > if something comes up and everyone agrees it should go to the Forum, > just submit before the end of the Ops session. Kendall or myself > would be happy to help you add details a bit later in the process, > should clarification be necessary. We typically have enough spots for > the majority of proposed Forum sessions. That's not a guarantee, but > food for thought. > > Cheers, > Jimmy > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Erik McCormick > February 27, 2019 at 11:31 AM > Would it be possible to push the deadline back a couple weeks? I > expect there to be a few session proposals that will come out of the > Ops Meetup which ends the day before the deadline. It would be helpful > to have a little time to organize and submit things afterwards. > > Thanks, > Erik > > Jimmy McArthur > February 27, 2019 at 10:40 AM > Hi Everyone - > > A quick reminder that we are accepting Forum [1] submissions for the > 2019 Open Infrastructure Summit in Denver [2]. Please submit your > ideas through the Summit CFP tool [3] through March 8th. Don't forget > to put your brainstorming etherpad up on the Denver Forum page [4]. > > This is not a classic conference track with speakers and > presentations. OSF community members (participants in development > teams, operators, working groups, SIGs, and other interested > individuals) discuss the topics they want to cover and get alignment > on and we welcome your participation. The Forum is your opportunity > to help shape the development of future project releases. More > information about the Forum [1]. > > If you have questions or concerns, please reach out to > speakersupport at openstack.org . > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/denver-2019/ > [3] https://www.openstack.org/summit/denver-2019/call-for-presentations > [4] https://wiki.openstack.org/wiki/Forum/Denver2019 > ___________________________________________ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Feb 27 19:14:54 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 27 Feb 2019 11:14:54 -0800 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <5C76E02F.4010906@openstack.org> References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> Message-ID: Hello :) On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur wrote: > Erik, > > I definitely understand the timeline is tight. One of the reasons that we > publish the schedule so early is to enable community members to plan their > schedule early, especially as there is more overlap with the main Summit > Schedule in Denver. Additionally, travel approval is often predicated upon > someone showing they're leading/moderating a session. > > Before publishing the schedule, we print a draft Forum schedule for > community feedback and start promotion of the schedule, which we have to > put up on the OpenStack website and apps at 5 weeks out. Extending the date > beyond the 10th won't give the Forum Selection Committee enough time to > complete those tasks. > > I think if the Ops team can come up with some high level discussion > topics, we'll be happy to put some holds in the Forum schedule for > Ops-specific content. diablo_rojo has also offered to attend some of the > Ops sessions remotely as well, if that would help you all shape some things > into actual sessions. > I'm definitely happy to help as much as I can. If you'll have something set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I definitely will. I could also read through etherpads you take notes in and help summarize things into forum proposals. Another thing to note is that whatever you/we submit, it doesn't have to be award winning :) Its totally possible to change session descriptions and edit who the speaker is later. Other random thought, I know Sean McGinnis has attended a lot of the Operators stuff in the past so maybe he could help narrow things down too? Not to sign him up for more work, but I know he's written a forum propsal or two in the past ;) > > I wish I could offer a further extension, but extending it another week > would push too far into the process. > > Cheers, > Jimmy > > Erik McCormick > February 27, 2019 at 12:43 PM > > Jimmy, > > I won't even get home until the 10th much less have time to follow up > with anyone. The formation of those sessions often come from > discussions spawned at the meetup and expanded upon later with folks > who could not attend. Could we at least get until 3/17? I understand > your desire to finalize the schedule, but 6 weeks out should be more > than enough time, no? > > Thanks, > Erik > > Jimmy McArthur > February 27, 2019 at 12:04 PM > > Hi Erik, > > We are able to extend the deadline to 11:59PM Pacific, March 10th. That > should give the weekend to get any additional stragglers in and still allow > the Forum Programming Committee enough time to manage the rest of the > approval and publishing process in time for people's travel needs, etc... > > For the Ops Meetup specifically, I'd suggest going a bit broader with the > proposals and offering to fill in the blanks later. For example, if > something comes up and everyone agrees it should go to the Forum, just > submit before the end of the Ops session. Kendall or myself would be happy > to help you add details a bit later in the process, should clarification be > necessary. We typically have enough spots for the majority of proposed > Forum sessions. That's not a guarantee, but food for thought. > > Cheers, > Jimmy > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > Erik McCormick > February 27, 2019 at 11:31 AM > Would it be possible to push the deadline back a couple weeks? I expect > there to be a few session proposals that will come out of the Ops Meetup > which ends the day before the deadline. It would be helpful to have a > little time to organize and submit things afterwards. > > Thanks, > Erik > > Jimmy McArthur > February 27, 2019 at 10:40 AM > Hi Everyone - > > A quick reminder that we are accepting Forum [1] submissions for the 2019 > Open Infrastructure Summit in Denver [2]. Please submit your ideas through > the Summit CFP tool [3] through March 8th. Don't forget to put your > brainstorming etherpad up on the Denver Forum page [4]. > > This is not a classic conference track with speakers and presentations. > OSF community members (participants in development teams, operators, > working groups, SIGs, and other interested individuals) discuss the topics > they want to cover and get alignment on and we welcome your participation. > The Forum is your opportunity to help shape the development of future > project releases. More information about the Forum [1]. > > If you have questions or concerns, please reach out to > speakersupport at openstack.org. > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/denver-2019/ > [3] https://www.openstack.org/summit/denver-2019/call-for-presentations > [4] https://wiki.openstack.org/wiki/Forum/Denver2019 > ___________________________________________ > > Hopefully that helps! -Kendall (diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Feb 27 19:19:54 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 27 Feb 2019 11:19:54 -0800 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> Message-ID: Another- nother thought: You could take a look at what is submitted by project teams closer to the deadline and see if your ideas might fit well with theirs since they are looking for feedback from operators anyway. In the past I have always hoped for more engagement in the forum sessions I've submitted but only ever had one or two operators able to join us. -Kendall (diablo_rojo) On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson wrote: > Hello :) > > On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur > wrote: > >> Erik, >> >> I definitely understand the timeline is tight. One of the reasons that >> we publish the schedule so early is to enable community members to plan >> their schedule early, especially as there is more overlap with the main >> Summit Schedule in Denver. Additionally, travel approval is often >> predicated upon someone showing they're leading/moderating a session. >> >> Before publishing the schedule, we print a draft Forum schedule for >> community feedback and start promotion of the schedule, which we have to >> put up on the OpenStack website and apps at 5 weeks out. Extending the date >> beyond the 10th won't give the Forum Selection Committee enough time to >> complete those tasks. >> >> I think if the Ops team can come up with some high level discussion >> topics, we'll be happy to put some holds in the Forum schedule for >> Ops-specific content. diablo_rojo has also offered to attend some of the >> Ops sessions remotely as well, if that would help you all shape some things >> into actual sessions. >> > > I'm definitely happy to help as much as I can. If you'll have something > set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I > definitely will. I could also read through etherpads you take notes in and > help summarize things into forum proposals. > > Another thing to note is that whatever you/we submit, it doesn't have to > be award winning :) Its totally possible to change session descriptions and > edit who the speaker is later. > > Other random thought, I know Sean McGinnis has attended a lot of the > Operators stuff in the past so maybe he could help narrow things down too? > Not to sign him up for more work, but I know he's written a forum propsal > or two in the past ;) > > >> >> I wish I could offer a further extension, but extending it another week >> would push too far into the process. >> >> Cheers, >> Jimmy >> >> Erik McCormick >> February 27, 2019 at 12:43 PM >> >> Jimmy, >> >> I won't even get home until the 10th much less have time to follow up >> with anyone. The formation of those sessions often come from >> discussions spawned at the meetup and expanded upon later with folks >> who could not attend. Could we at least get until 3/17? I understand >> your desire to finalize the schedule, but 6 weeks out should be more >> than enough time, no? >> >> Thanks, >> Erik >> >> Jimmy McArthur >> February 27, 2019 at 12:04 PM >> >> Hi Erik, >> >> We are able to extend the deadline to 11:59PM Pacific, March 10th. That >> should give the weekend to get any additional stragglers in and still allow >> the Forum Programming Committee enough time to manage the rest of the >> approval and publishing process in time for people's travel needs, etc... >> >> For the Ops Meetup specifically, I'd suggest going a bit broader with the >> proposals and offering to fill in the blanks later. For example, if >> something comes up and everyone agrees it should go to the Forum, just >> submit before the end of the Ops session. Kendall or myself would be happy >> to help you add details a bit later in the process, should clarification be >> necessary. We typically have enough spots for the majority of proposed >> Forum sessions. That's not a guarantee, but food for thought. >> >> Cheers, >> Jimmy >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> >> Erik McCormick >> February 27, 2019 at 11:31 AM >> Would it be possible to push the deadline back a couple weeks? I expect >> there to be a few session proposals that will come out of the Ops Meetup >> which ends the day before the deadline. It would be helpful to have a >> little time to organize and submit things afterwards. >> >> Thanks, >> Erik >> >> Jimmy McArthur >> February 27, 2019 at 10:40 AM >> Hi Everyone - >> >> A quick reminder that we are accepting Forum [1] submissions for the 2019 >> Open Infrastructure Summit in Denver [2]. Please submit your ideas through >> the Summit CFP tool [3] through March 8th. Don't forget to put your >> brainstorming etherpad up on the Denver Forum page [4]. >> >> This is not a classic conference track with speakers and presentations. >> OSF community members (participants in development teams, operators, >> working groups, SIGs, and other interested individuals) discuss the topics >> they want to cover and get alignment on and we welcome your participation. >> The Forum is your opportunity to help shape the development of future >> project releases. More information about the Forum [1]. >> >> If you have questions or concerns, please reach out to >> speakersupport at openstack.org. >> >> Cheers, >> Jimmy >> >> [1] https://wiki.openstack.org/wiki/Forum >> [2] https://www.openstack.org/summit/denver-2019/ >> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations >> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >> ___________________________________________ >> >> > Hopefully that helps! > > -Kendall (diablo_rojo) > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Feb 27 21:57:42 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 27 Feb 2019 13:57:42 -0800 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> Message-ID: Hello :) On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan wrote: > I think the issue is that forum submissions building on what gets > discussed in Berlin can't be expected to be finalised whilst attendees to > the berlin meetup are still traveling. It's not that Erik can't pull these > things together, in fact he's an old hand at this, it's more that this > process isn't reasonable if there's so little time to collate what we learn > in Berlin and feed it forward to Denver. Frankly it sounds like because the > planning committee needs 5 weeks, Erik can have two days. Seem unfair. > Honestly, the decision process doesn't take much time, aside from organizing a time that all 10 people can meet across x timezones (a thing unto itself). Its the community feedback period, giving people enough time to secure travel approval from their management, loading the sessions into the actual schedule app, and other print deadlines that force us to have everything set this far out. I will definitely help the ops community in whatever way I can! Do you have remote attendance set up for the meetup? > Chris > > On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson > wrote: > >> Another- nother thought: You could take a look at what is submitted by >> project teams closer to the deadline and see if your ideas might fit well >> with theirs since they are looking for feedback from operators anyway. In >> the past I have always hoped for more engagement in the forum sessions I've >> submitted but only ever had one or two operators able to join us. >> >> -Kendall (diablo_rojo) >> >> On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson >> wrote: >> >>> Hello :) >>> >>> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur >>> wrote: >>> >>>> Erik, >>>> >>>> I definitely understand the timeline is tight. One of the reasons that >>>> we publish the schedule so early is to enable community members to plan >>>> their schedule early, especially as there is more overlap with the main >>>> Summit Schedule in Denver. Additionally, travel approval is often >>>> predicated upon someone showing they're leading/moderating a session. >>>> >>>> Before publishing the schedule, we print a draft Forum schedule for >>>> community feedback and start promotion of the schedule, which we have to >>>> put up on the OpenStack website and apps at 5 weeks out. Extending the date >>>> beyond the 10th won't give the Forum Selection Committee enough time to >>>> complete those tasks. >>>> >>>> I think if the Ops team can come up with some high level discussion >>>> topics, we'll be happy to put some holds in the Forum schedule for >>>> Ops-specific content. diablo_rojo has also offered to attend some of the >>>> Ops sessions remotely as well, if that would help you all shape some things >>>> into actual sessions. >>>> >>> >>> I'm definitely happy to help as much as I can. If you'll have something >>> set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I >>> definitely will. I could also read through etherpads you take notes in and >>> help summarize things into forum proposals. >>> >>> Another thing to note is that whatever you/we submit, it doesn't have to >>> be award winning :) Its totally possible to change session descriptions and >>> edit who the speaker is later. >>> >>> Other random thought, I know Sean McGinnis has attended a lot of the >>> Operators stuff in the past so maybe he could help narrow things down too? >>> Not to sign him up for more work, but I know he's written a forum propsal >>> or two in the past ;) >>> >>> >>>> >>>> I wish I could offer a further extension, but extending it another week >>>> would push too far into the process. >>>> >>>> Cheers, >>>> Jimmy >>>> >>>> Erik McCormick >>>> February 27, 2019 at 12:43 PM >>>> >>>> Jimmy, >>>> >>>> I won't even get home until the 10th much less have time to follow up >>>> with anyone. The formation of those sessions often come from >>>> discussions spawned at the meetup and expanded upon later with folks >>>> who could not attend. Could we at least get until 3/17? I understand >>>> your desire to finalize the schedule, but 6 weeks out should be more >>>> than enough time, no? >>>> >>>> Thanks, >>>> Erik >>>> >>>> Jimmy McArthur >>>> February 27, 2019 at 12:04 PM >>>> >>>> Hi Erik, >>>> >>>> We are able to extend the deadline to 11:59PM Pacific, March 10th. >>>> That should give the weekend to get any additional stragglers in and still >>>> allow the Forum Programming Committee enough time to manage the rest of the >>>> approval and publishing process in time for people's travel needs, etc... >>>> >>>> For the Ops Meetup specifically, I'd suggest going a bit broader with >>>> the proposals and offering to fill in the blanks later. For example, if >>>> something comes up and everyone agrees it should go to the Forum, just >>>> submit before the end of the Ops session. Kendall or myself would be happy >>>> to help you add details a bit later in the process, should clarification be >>>> necessary. We typically have enough spots for the majority of proposed >>>> Forum sessions. That's not a guarantee, but food for thought. >>>> >>>> Cheers, >>>> Jimmy >>>> >>>> >>>> _______________________________________________ >>>> Airship-discuss mailing list >>>> Airship-discuss at lists.airshipit.org >>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>>> >>>> Erik McCormick >>>> February 27, 2019 at 11:31 AM >>>> Would it be possible to push the deadline back a couple weeks? I expect >>>> there to be a few session proposals that will come out of the Ops Meetup >>>> which ends the day before the deadline. It would be helpful to have a >>>> little time to organize and submit things afterwards. >>>> >>>> Thanks, >>>> Erik >>>> >>>> Jimmy McArthur >>>> February 27, 2019 at 10:40 AM >>>> Hi Everyone - >>>> >>>> A quick reminder that we are accepting Forum [1] submissions for the >>>> 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas >>>> through the Summit CFP tool [3] through March 8th. Don't forget to put >>>> your brainstorming etherpad up on the Denver Forum page [4]. >>>> >>>> This is not a classic conference track with speakers and presentations. >>>> OSF community members (participants in development teams, operators, >>>> working groups, SIGs, and other interested individuals) discuss the topics >>>> they want to cover and get alignment on and we welcome your participation. >>>> The Forum is your opportunity to help shape the development of future >>>> project releases. More information about the Forum [1]. >>>> >>>> If you have questions or concerns, please reach out to >>>> speakersupport at openstack.org. >>>> >>>> Cheers, >>>> Jimmy >>>> >>>> [1] https://wiki.openstack.org/wiki/Forum >>>> [2] https://www.openstack.org/summit/denver-2019/ >>>> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations >>>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >>>> ___________________________________________ >>>> >>>> >>> Hopefully that helps! >>> >>> -Kendall (diablo_rojo) >>> >> > > -- > Chris Morgan > - Kendall Nelson (diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.l.tullis at intel.com Wed Feb 27 22:15:45 2019 From: michael.l.tullis at intel.com (Tullis, Michael L) Date: Wed, 27 Feb 2019 22:15:45 +0000 Subject: [Starlingx-discuss] [docs][meetings] docs team meeting minutes 2/27/2019 Message-ID: <3808363B39586544A6839C76CF81445EA1ABDE3C@ORSMSX104.amr.corp.intel.com> For notes and new action items from our docs team meeting today, see our etherpad: https://etherpad.openstack.org/p/stx-documentation Join us if you have interest in StarlingX docs! We meet Wednesdays, and call logistics are here: https://wiki.openstack.org/wiki/Starlingx/Meetings. -- Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Feb 27 22:31:00 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 27 Feb 2019 16:31:00 -0600 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <20190227220801.GA12980@sm-workstation> References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> <20190227220801.GA12980@sm-workstation> Message-ID: <5C770FA4.6010409@openstack.org> Sean, > Sean McGinnis > February 27, 2019 at 4:08 PM > > To be clear, the issue isn't needing help writing up the submission. > So great > if someone can attend or watch for topics coming up that can be pulled > out into > Forum ideas, but the crux is that there are a lot of things discussed > at these > events and it may take several days after it is over to realize, "hey, > that > would be really useful if we could discuss that at the Forum." Totally understood. That's why we're suggesting to put a few (I counted five Ops specific Forum talks in Berlin) placeholder sessions in for Ops with a couple of high level sentences, to be defined later. We're happy to help update the Forum suggestions after y'all have had a chance to parse Meetup outcomes into Forum topics that makes sense. > > I don't think what Erik asked for is unreasonable. The Ops Meetup event is > exactly the target we want feeding into Forum discussions. If we can > give a > week after the event for the Ops Meetup ends for this processing to > happen, I > think we increase the odds of an effective and useful Forum. I understand the POV, but keep in mind we're also trying to program against many other interests and we have deadlines that we have to reach with regards to getting comms out to the rest of the community. We've extended the deadline by two days, which I hope will give the Ops Community enough time to parse the info from the Meetup into a few bite-size bits that we can use as placeholders on the schedule, with details TBD. I want to re-emphasize, Kendall and I are happy to help in any way possible on this. If you want to pass along some napkin notes, we can do help get those into the schedule :) It's critical that we provide at least a straw man schedule to the community as early as possible, so we can identify conflicts and travel considerations for our attendees. Thanks, Jimmy > > Can we please extend that deadline out a few more days to make sure we > get this > valuable input? > > Sean > Kendall Nelson > February 27, 2019 at 3:57 PM > Hello :) > > On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan > wrote: > > I think the issue is that forum submissions building on what gets > discussed in Berlin can't be expected to be finalised whilst > attendees to the berlin meetup are still traveling. It's not that > Erik can't pull these things together, in fact he's an old hand at > this, it's more that this process isn't reasonable if there's so > little time to collate what we learn in Berlin and feed it forward > to Denver. Frankly it sounds like because the planning committee > needs 5 weeks, Erik can have two days. Seem unfair. > > > Honestly, the decision process doesn't take much time, aside from > organizing a time that all 10 people can meet across x timezones (a > thing unto itself). Its the community feedback period, giving people > enough time to secure travel approval from their management, loading > the sessions into the actual schedule app, and other print deadlines > that force us to have everything set this far out. > > I will definitely help the ops community in whatever way I can! Do you > have remote attendance set up for the meetup? > > > Chris > > On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson > > wrote: > > Another- nother thought: You could take a look at what is > submitted by project teams closer to the deadline and see if > your ideas might fit well with theirs since they are looking > for feedback from operators anyway. In the past I have always > hoped for more engagement in the forum sessions I've submitted > but only ever had one or two operators able to join us. > > -Kendall (diablo_rojo) > > On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson > > wrote: > > Hello :) > > On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur > > wrote: > > Erik, > > I definitely understand the timeline is tight. One of > the reasons that we publish the schedule so early is > to enable community members to plan their schedule > early, especially as there is more overlap with the > main Summit Schedule in Denver. Additionally, travel > approval is often predicated upon someone showing > they're leading/moderating a session. > > Before publishing the schedule, we print a draft > Forum schedule for community feedback and start > promotion of the schedule, which we have to put up on > the OpenStack website and apps at 5 weeks out. > Extending the date beyond the 10th won't give the > Forum Selection Committee enough time to complete > those tasks. > > I think if the Ops team can come up with some high > level discussion topics, we'll be happy to put some > holds in the Forum schedule for Ops-specific content. > diablo_rojo has also offered to attend some of the Ops > sessions remotely as well, if that would help you all > shape some things into actual sessions. > > > I'm definitely happy to help as much as I can. If you'll > have something set up that I can call into (zoom, webex, > bluejeans, hangout, whatever), I definitely will. I could > also read through etherpads you take notes in and help > summarize things into forum proposals. > > Another thing to note is that whatever you/we submit, it > doesn't have to be award winning :) Its totally possible > to change session descriptions and edit who the speaker is > later. > > Other random thought, I know Sean McGinnis has attended a > lot of the Operators stuff in the past so maybe he could > help narrow things down too? Not to sign him up for more > work, but I know he's written a forum propsal or two in > the past ;) > > > I wish I could offer a further extension, but > extending it another week would push too far into the > process. > > Cheers, > Jimmy >> Erik McCormick >> February 27, 2019 at 12:43 PM >> Jimmy, >> >> I won't even get home until the 10th much less have >> time to follow up >> with anyone. The formation of those sessions often >> come from >> discussions spawned at the meetup and expanded upon >> later with folks >> who could not attend. Could we at least get until >> 3/17? I understand >> your desire to finalize the schedule, but 6 weeks out >> should be more >> than enough time, no? >> >> Thanks, >> Erik >> Jimmy McArthur >> February 27, 2019 at 12:04 PM >> Hi Erik, >> >> We are able to extend the deadline to 11:59PM >> Pacific, March 10th. That should give the weekend to >> get any additional stragglers in and still allow the >> Forum Programming Committee enough time to manage the >> rest of the approval and publishing process in time >> for people's travel needs, etc... >> >> For the Ops Meetup specifically, I'd suggest going a >> bit broader with the proposals and offering to fill >> in the blanks later. For example, if something comes >> up and everyone agrees it should go to the Forum, >> just submit before the end of the Ops session. >> Kendall or myself would be happy to help you add >> details a bit later in the process, should >> clarification be necessary. We typically have enough >> spots for the majority of proposed Forum sessions. >> That's not a guarantee, but food for thought. >> >> Cheers, >> Jimmy >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> Erik McCormick >> February 27, 2019 at 11:31 AM >> Would it be possible to push the deadline back a >> couple weeks? I expect there to be a few session >> proposals that will come out of the Ops Meetup which >> ends the day before the deadline. It would be helpful >> to have a little time to organize and submit things >> afterwards. >> >> Thanks, >> Erik >> >> Jimmy McArthur >> February 27, 2019 at 10:40 AM >> Hi Everyone - >> >> A quick reminder that we are accepting Forum [1] >> submissions for the 2019 Open Infrastructure Summit >> in Denver [2]. Please submit your ideas through the >> Summit CFP tool [3] through March 8th. Don't forget >> to put your brainstorming etherpad up on the Denver >> Forum page [4]. >> >> This is not a classic conference track with speakers >> and presentations. OSF community members >> (participants in development teams, operators, >> working groups, SIGs, and other interested >> individuals) discuss the topics they want to cover >> and get alignment on and we welcome your >> participation. The Forum is your opportunity to help >> shape the development of future project releases. >> More information about the Forum [1]. >> >> If you have questions or concerns, please reach out >> to speakersupport at openstack.org >> . >> >> Cheers, >> Jimmy >> >> [1] https://wiki.openstack.org/wiki/Forum >> [2] https://www.openstack.org/summit/denver-2019/ >> [3] >> https://www.openstack.org/summit/denver-2019/call-for-presentations >> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >> ___________________________________________ >> > > Hopefully that helps! > > -Kendall (diablo_rojo) > > > > -- > Chris Morgan > > > > - Kendall Nelson (diablo_rojo) > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Chris Morgan > February 27, 2019 at 3:25 PM > I think the issue is that forum submissions building on what gets > discussed in Berlin can't be expected to be finalised whilst attendees > to the berlin meetup are still traveling. It's not that Erik can't > pull these things together, in fact he's an old hand at this, it's > more that this process isn't reasonable if there's so little time to > collate what we learn in Berlin and feed it forward to Denver. Frankly > it sounds like because the planning committee needs 5 weeks, Erik can > have two days. Seem unfair. > > Chris > > > > -- > Chris Morgan > > Kendall Nelson > February 27, 2019 at 1:19 PM > Another- nother thought: You could take a look at what is submitted by > project teams closer to the deadline and see if your ideas might fit > well with theirs since they are looking for feedback from operators > anyway. In the past I have always hoped for more engagement in the > forum sessions I've submitted but only ever had one or two operators > able to join us. > > -Kendall (diablo_rojo) > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Kendall Nelson > February 27, 2019 at 1:14 PM > Hello :) > > On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur > wrote: > > Erik, > > I definitely understand the timeline is tight. One of the reasons > that we publish the schedule so early is to enable community > members to plan their schedule early, especially as there is more > overlap with the main Summit Schedule in Denver. Additionally, > travel approval is often predicated upon someone showing they're > leading/moderating a session. > > Before publishing the schedule, we print a draft Forum schedule > for community feedback and start promotion of the schedule, which > we have to put up on the OpenStack website and apps at 5 weeks > out. Extending the date beyond the 10th won't give the Forum > Selection Committee enough time to complete those tasks. > > I think if the Ops team can come up with some high level > discussion topics, we'll be happy to put some holds in the Forum > schedule for Ops-specific content. diablo_rojo has also offered > to attend some of the Ops sessions remotely as well, if that would > help you all shape some things into actual sessions. > > > I'm definitely happy to help as much as I can. If you'll have > something set up that I can call into (zoom, webex, bluejeans, > hangout, whatever), I definitely will. I could also read through > etherpads you take notes in and help summarize things into forum > proposals. > > Another thing to note is that whatever you/we submit, it doesn't have > to be award winning :) Its totally possible to change session > descriptions and edit who the speaker is later. > > Other random thought, I know Sean McGinnis has attended a lot of the > Operators stuff in the past so maybe he could help narrow things down > too? Not to sign him up for more work, but I know he's written a forum > propsal or two in the past ;) > > > I wish I could offer a further extension, but extending it another > week would push too far into the process. > > Cheers, > Jimmy >> Erik McCormick >> February 27, 2019 at 12:43 PM >> Jimmy, >> >> I won't even get home until the 10th much less have time to follow up >> with anyone. The formation of those sessions often come from >> discussions spawned at the meetup and expanded upon later with folks >> who could not attend. Could we at least get until 3/17? I understand >> your desire to finalize the schedule, but 6 weeks out should be more >> than enough time, no? >> >> Thanks, >> Erik >> Jimmy McArthur >> February 27, 2019 at 12:04 PM >> Hi Erik, >> >> We are able to extend the deadline to 11:59PM Pacific, March >> 10th. That should give the weekend to get any additional >> stragglers in and still allow the Forum Programming Committee >> enough time to manage the rest of the approval and publishing >> process in time for people's travel needs, etc... >> >> For the Ops Meetup specifically, I'd suggest going a bit broader >> with the proposals and offering to fill in the blanks later. For >> example, if something comes up and everyone agrees it should go >> to the Forum, just submit before the end of the Ops session. >> Kendall or myself would be happy to help you add details a bit >> later in the process, should clarification be necessary. We >> typically have enough spots for the majority of proposed Forum >> sessions. That's not a guarantee, but food for thought. >> >> Cheers, >> Jimmy >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> Erik McCormick >> February 27, 2019 at 11:31 AM >> Would it be possible to push the deadline back a couple weeks? I >> expect there to be a few session proposals that will come out of >> the Ops Meetup which ends the day before the deadline. It would >> be helpful to have a little time to organize and submit things >> afterwards. >> >> Thanks, >> Erik >> >> Jimmy McArthur >> February 27, 2019 at 10:40 AM >> Hi Everyone - >> >> A quick reminder that we are accepting Forum [1] submissions for >> the 2019 Open Infrastructure Summit in Denver [2]. Please submit >> your ideas through the Summit CFP tool [3] through March 8th. >> Don't forget to put your brainstorming etherpad up on the Denver >> Forum page [4]. >> >> This is not a classic conference track with speakers and >> presentations. OSF community members (participants in development >> teams, operators, working groups, SIGs, and other interested >> individuals) discuss the topics they want to cover and get >> alignment on and we welcome your participation. The Forum is >> your opportunity to help shape the development of future project >> releases. More information about the Forum [1]. >> >> If you have questions or concerns, please reach out to >> speakersupport at openstack.org . >> >> Cheers, >> Jimmy >> >> [1] https://wiki.openstack.org/wiki/Forum >> [2] https://www.openstack.org/summit/denver-2019/ >> [3] >> https://www.openstack.org/summit/denver-2019/call-for-presentations >> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >> ___________________________________________ >> > > Hopefully that helps! > > -Kendall (diablo_rojo) > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ada.cabrales at intel.com Wed Feb 27 22:49:39 2019 From: ada.cabrales at intel.com (Cabrales, Ada) Date: Wed, 27 Feb 2019 22:49:39 +0000 Subject: [Starlingx-discuss] [ Testing ] Meeting notes - 02/26/2019 Message-ID: <4F6AACE4B0F173488D033B02A8BB5B7E7CD78DD2@FMSMSX114.amr.corp.intel.com> Agenda for 2/26/2019 Attendees: Maria, Cristopher, Elio, Fernando, JC, Jose, JP, Numan, Richo 1. Regression selection progress - 15 min Numan: Making changes in test cases based on containers and patch elimination - ~90% done Updates being done in the test management tool. Those will be exported to plain text files and submitted to the repo. Ceph test cases WIP (those are required for Ceph upgrade testing). Storage domain will be uploaded first. First upload will be done by EOW. For automation - let's begin with networking, nova, storage and maintenance Horizon - done, Security - working on updates, Heat - test cases selected. Please begin to upload test cases. Take the spreadsheet as an index. Upload that into the repo. Simplex and gnocchi done - upload to the repo this week Sysinventory selected, to be uploaded this week. System Test will follow next week. -- Include a weekly check of the plan. 2. Feature testing Documentation: If you have guides/documentation that can be shared, please talk with the documentation team. Meetings on Wednesday 12:30 Pacific https://storyboard.openstack.org/#!/search?project_id=1046 For signed builds - review the email sent by Ken and work on enabling them. Networking tests - networking team selected 10 test cases. For containerized OVS - please make sure we have covered both deployment scnearios - ovs and ovs/dpdk Thank to Chris to the review he did to the Test cases. OpenStack patch reduction - Numan to provide their config for running RefStack. - done We can use that for tempest runs. Review who can take the tempest task. - Ada For conteinerized OpenStack - develop tests for a service working on a container. Tempest will be for the openstack services. 3. Containers Numan's team is using stein ISO for daily testing. A launchpad for the 2+2 problem we found is here: https://bugs.launchpad.net/starlingx/+bug/1817723 Will review with stein ISO and verify it. 4. Opens: N/A From cesar.lara at intel.com Wed Feb 27 23:29:00 2019 From: cesar.lara at intel.com (Lara, Cesar) Date: Wed, 27 Feb 2019 23:29:00 +0000 Subject: [Starlingx-discuss] [build][meetings] Build team meeting agenda 2/28/2019 Message-ID: <0B566C62EC792145B40E29EFEBF1AB47105FA7CD@fmsmsx104.amr.corp.intel.com> Build team meeting Agenda for 2/28/2019 - Cengn Update - Build system proposal for Ubuntu - Victor R - Build signing support - opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Wed Feb 27 23:43:46 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Wed, 27 Feb 2019 17:43:46 -0600 Subject: [Starlingx-discuss] [build][meetings] Build team meeting agenda 2/28/2019 In-Reply-To: <0B566C62EC792145B40E29EFEBF1AB47105FA7CD@fmsmsx104.amr.corp.intel.com> References: <0B566C62EC792145B40E29EFEBF1AB47105FA7CD@fmsmsx104.amr.corp.intel.com> Message-ID: Link to tomorrow's presentation : https://docs.google.com/presentation/d/1ck7vGH50AIAjUx9GNrIGtowG5qg7OYUBNdJyY-5ZvDc/edit?usp=sharing Feedback more than welcome Victor Rodriguez On Wed, Feb 27, 2019 at 5:29 PM Lara, Cesar wrote: > > Build team meeting > > > > Agenda for 2/28/2019 > > > > - Cengn Update > > - Build system proposal for Ubuntu – Victor R > > - Build signing support > > - opens > > > > Regards > > > > Cesar Lara > > Software Engineering Manager > > OpenSource Technology Center > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From shuicheng.lin at intel.com Fri Feb 22 07:11:34 2019 From: shuicheng.lin at intel.com (Lin, Shuicheng) Date: Fri, 22 Feb 2019 07:11:34 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> Hi Jaewook, For the 8080 change, you could find the history in below mail: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003017.html For the PXE mode, you could use “system host-show controller-1 | grep install” to get controller-1 install status. Please make sure controller-1 is configured to boot with disk first. Just manuall choose pxeboot for the first time installation. Otherwise, if controller-1 is configured to using pxeboot as first priority, it will lead to deadloop of installation. Best Regards Shuicheng From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Friday, February 22, 2019 2:54 PM To: starlingx-discuss Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, [image.png] And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 69011 bytes Desc: image003.png URL: From kyle.oh95 at gmail.com Fri Feb 22 07:26:32 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Fri, 22 Feb 2019 16:26:32 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> References: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> Message-ID: Hi Shuicheng, Thank you for your kind explain :) For the port one, it really was understandable why the port had been changed. But for the PXE one, still I couldn't get any change. As you said, system host-show controller-1 | grep install does not change from the first one install_output = text install_state = None install_state_info = None And also, the display doesn't seem to be changed. It does not reboot at all. It keeps showing 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. Again.. I rechecked my BIOS setting, but it was not the problem. Do you have any suggestion? Best Regards, Jaewook. 2019년 2월 22일 (금) 오후 4:11, Lin, Shuicheng 님이 작성: > Hi Jaewook, > > For the 8080 change, you could find the history in below mail: > > > http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003017.html > > > > For the PXE mode, you could use “system host-show controller-1 | grep > install” to get controller-1 install status. > > Please make sure controller-1 is configured to boot with disk first. Just > manuall choose pxeboot for the first time installation. > > Otherwise, if controller-1 is configured to using pxeboot as first > priority, it will lead to deadloop of installation. > > > > Best Regards > > Shuicheng > > > > *From:* Jaewook Oh [mailto:kyle.oh95 at gmail.com] > *Sent:* Friday, February 22, 2019 2:54 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] Duplex PXE Booting seems failed > > > > Hello StarlingX Team, > > > > I finally solved the horizon error, the port number was different. > > I don't know why the port was changed, but anyway the port number was > 8080, not 80. > > > > But I'm now facing new obstacles, Duplex PXE Booting. > > > > I succeed to connect PXE mode, but no more process.. > > > > In Controller-0, I can find below result, > > > > And another node that should've been controller-1, shows below letters on > the display. > > > > 1) All-in-one > > > > Loading rel-19.01/installer-bzImage......... > > Loading > rel-19.01/installer-initrd............................................................................ready. > > > > > > I waited this task for a day, but no changes. > > > > Any help would be very appreciated. > > > > Best Regards, > > Jaewook. > > > > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 69011 bytes Desc: not available URL: From austin.sun at intel.com Fri Feb 22 07:39:56 2019 From: austin.sun at intel.com (Sun, Austin) Date: Fri, 22 Feb 2019 07:39:56 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Jaewook: 1. could you share the hw info for controller-1 ? and check bios setting ? is it using UEFI ? VTx/Iommu enable or not ? 2. Could you try access controller-1 and press Alt+F10 to see any log if the system is bare metal ? Thanks. BR Austin Sun. From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Friday, February 22, 2019 2:54 PM To: starlingx-discuss Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, [image.png] And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 47105 bytes Desc: image002.png URL: From Chris.Winnicki at windriver.com Mon Feb 25 22:03:26 2019 From: Chris.Winnicki at windriver.com (Winnicki, Chris) Date: Mon, 25 Feb 2019 22:03:26 +0000 Subject: [Starlingx-discuss] Regression test cases for networking testing In-Reply-To: <3CAA827B7A79BA46B15B280EC82088FE48277D61@ALA-MBD.corp.ad.wrs.com> References: <1466AF2176E6F040BD63860D0A241BBD46C8C793@FMSMSX109.amr.corp.intel.com>, <3CAA827B7A79BA46B15B280EC82088FE48277D61@ALA-MBD.corp.ad.wrs.com> Message-ID: <7E4792BA14B1DE4BAB354DF77FE0233ABC89A895@ALA-MBD.corp.ad.wrs.com> Hi All Here is my feedback - respective to the row numbers in the "Regression tests Networking .xlsx" spreadsheet: Row 5-6: Remove TC: no vif model in stx Row 20-27: Remove the testcase: feature is depricated Row 41-42: Remove the testcase: n/a in STX Row 64: Correct the TC name: “i raised” to “is raised” Row: 68: Remove TC: not applicable Row 71: Remove TC: not applicable Row 72: Remove TC: not applicable Row 75: Remove TC: not applicable Row 81: Remove TC: not applicable Row 81: Remove TC: not applicable due to https://storyboard.openstack.org/#!/story/2004455 Row 82: Change priority to: 4 Row 86, 101, 102-106: Remove TC: No infra network in STX Row 109-111: Low value Row: 112-116: Change priority to: 3 Row 117, 119: N/A in STX Row: 133: VM misspeled with “vem” Row 137-138: Change priority to: 3 Row 139: Remove TC: No infra network in STX Row 140-143: Change priority to: 4 Row 146: Remove TC: No infra network in STX Row 148: Remove TC: No infra network in STX Row 149-151: Remove TC: No infra network in STX Chris Winnicki - MTS - SYS - PV chris.winnicki at windriver.com 613-963-1329 ________________________________ From: Waheed, Numan Sent: Friday, February 22, 2019 2:17 PM To: Martinez Monroy, Elio; Xu, Chenjie; starlingx-discuss at lists.starlingx.io; Winnicki, Chris Cc: Cabrales, Ada; Khalil, Ghada; Zhao, Forrest Subject: RE: Regression test cases for networking testing Hi Chris, Can you please also review these test cases. Thanks, Numan. From: Martinez Monroy, Elio Sent: February-22-19 1:59 PM To: Xu, Chenjie ; starlingx-discuss at lists.starlingx.io Cc: Cabrales, Ada ; Khalil, Ghada ; Waheed, Numan ; Zhao, Forrest Subject: Regression test cases for networking testing Hello guys, I’m sharing the list of regression test cases for networking, please let me know if you consider that we need to add some other scenario. This test is based on a full analysis of different domains. Besides this, we are trying to perform a good scope coverage , wiping out those domains and features that StarlingX is not using such as AVS and go on. Please let me know if you have further questions or suggestions. We are in the process of adjusting some test cases according with new features and convention names such as Provider net. So, this list can be adjusted and may change in future days. [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 zhiwei.he at intel.com Tue Feb 26 03:01:39 2019 From: zhiwei.he at intel.com (He, Zhiwei) Date: Tue, 26 Feb 2019 03:01:39 +0000 Subject: [Starlingx-discuss] issue about create network on horzon Message-ID: <09777F12A863964D9F4AE780D4FEA3E83E654928@SHSMSX104.ccr.corp.intel.com> Hi Expert; We have try to using "Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Jan-11 (link)" to make SR IOV network, When the create network with dashboard ,but fail due to the "Danger:An error occurred, please try again later", attached horizon log for you 2019-02-19 21:29:53,534 [ERROR] django.request: Internal Server Error: /admin/networks/create/ in the horzon log [cid:image001.jpg at 01D4CDC2.A59FF4A0] Thanks! zhiwei -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8602 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: horizon.log Type: application/octet-stream Size: 58015 bytes Desc: horizon.log URL: From emccormick at cirrusseven.com Wed Feb 27 17:31:33 2019 From: emccormick at cirrusseven.com (Erik McCormick) Date: Wed, 27 Feb 2019 12:31:33 -0500 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <5C76BD8E.4070504@openstack.org> References: <5C76BD8E.4070504@openstack.org> Message-ID: Would it be possible to push the deadline back a couple weeks? I expect there to be a few session proposals that will come out of the Ops Meetup which ends the day before the deadline. It would be helpful to have a little time to organize and submit things afterwards. Thanks, Erik On Wed, Feb 27, 2019, 11:42 AM Jimmy McArthur wrote: > Hi Everyone - > > A quick reminder that we are accepting Forum [1] submissions for the 2019 > Open Infrastructure Summit in Denver [2]. Please submit your ideas through > the Summit CFP tool [3] through March 8th. Don't forget to put your > brainstorming etherpad up on the Denver Forum page [4]. > > This is not a classic conference track with speakers and presentations. > OSF community members (participants in development teams, operators, > working groups, SIGs, and other interested individuals) discuss the topics > they want to cover and get alignment on and we welcome your participation. > The Forum is your opportunity to help shape the development of future > project releases. More information about the Forum [1]. > > If you have questions or concerns, please reach out to > speakersupport at openstack.org. > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/denver-2019/ > [3] https://www.openstack.org/summit/denver-2019/call-for-presentations > [4] https://wiki.openstack.org/wiki/Forum/Denver2019 > ___________________________________________ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emccormick at cirrusseven.com Wed Feb 27 18:43:18 2019 From: emccormick at cirrusseven.com (Erik McCormick) Date: Wed, 27 Feb 2019 13:43:18 -0500 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <5C76D125.2040404@openstack.org> References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> Message-ID: Jimmy, I won't even get home until the 10th much less have time to follow up with anyone. The formation of those sessions often come from discussions spawned at the meetup and expanded upon later with folks who could not attend. Could we at least get until 3/17? I understand your desire to finalize the schedule, but 6 weeks out should be more than enough time, no? Thanks, Erik On Wed, Feb 27, 2019 at 1:04 PM Jimmy McArthur wrote: > > Hi Erik, > > We are able to extend the deadline to 11:59PM Pacific, March 10th. That should give the weekend to get any additional stragglers in and still allow the Forum Programming Committee enough time to manage the rest of the approval and publishing process in time for people's travel needs, etc... > > For the Ops Meetup specifically, I'd suggest going a bit broader with the proposals and offering to fill in the blanks later. For example, if something comes up and everyone agrees it should go to the Forum, just submit before the end of the Ops session. Kendall or myself would be happy to help you add details a bit later in the process, should clarification be necessary. We typically have enough spots for the majority of proposed Forum sessions. That's not a guarantee, but food for thought. > > Cheers, > Jimmy > > Erik McCormick February 27, 2019 at 11:31 AM > Would it be possible to push the deadline back a couple weeks? I expect there to be a few session proposals that will come out of the Ops Meetup which ends the day before the deadline. It would be helpful to have a little time to organize and submit things afterwards. > > Thanks, > Erik > > Jimmy McArthur February 27, 2019 at 10:40 AM > Hi Everyone - > > A quick reminder that we are accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas through the Summit CFP tool [3] through March 8th. Don't forget to put your brainstorming etherpad up on the Denver Forum page [4]. > > This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. > > If you have questions or concerns, please reach out to speakersupport at openstack.org. > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/denver-2019/ > [3] https://www.openstack.org/summit/denver-2019/call-for-presentations > [4] https://wiki.openstack.org/wiki/Forum/Denver2019 > ___________________________________________ > > From mihalis68 at gmail.com Wed Feb 27 21:25:55 2019 From: mihalis68 at gmail.com (Chris Morgan) Date: Wed, 27 Feb 2019 16:25:55 -0500 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> Message-ID: I think the issue is that forum submissions building on what gets discussed in Berlin can't be expected to be finalised whilst attendees to the berlin meetup are still traveling. It's not that Erik can't pull these things together, in fact he's an old hand at this, it's more that this process isn't reasonable if there's so little time to collate what we learn in Berlin and feed it forward to Denver. Frankly it sounds like because the planning committee needs 5 weeks, Erik can have two days. Seem unfair. Chris On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson wrote: > Another- nother thought: You could take a look at what is submitted by > project teams closer to the deadline and see if your ideas might fit well > with theirs since they are looking for feedback from operators anyway. In > the past I have always hoped for more engagement in the forum sessions I've > submitted but only ever had one or two operators able to join us. > > -Kendall (diablo_rojo) > > On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson > wrote: > >> Hello :) >> >> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur >> wrote: >> >>> Erik, >>> >>> I definitely understand the timeline is tight. One of the reasons that >>> we publish the schedule so early is to enable community members to plan >>> their schedule early, especially as there is more overlap with the main >>> Summit Schedule in Denver. Additionally, travel approval is often >>> predicated upon someone showing they're leading/moderating a session. >>> >>> Before publishing the schedule, we print a draft Forum schedule for >>> community feedback and start promotion of the schedule, which we have to >>> put up on the OpenStack website and apps at 5 weeks out. Extending the date >>> beyond the 10th won't give the Forum Selection Committee enough time to >>> complete those tasks. >>> >>> I think if the Ops team can come up with some high level discussion >>> topics, we'll be happy to put some holds in the Forum schedule for >>> Ops-specific content. diablo_rojo has also offered to attend some of the >>> Ops sessions remotely as well, if that would help you all shape some things >>> into actual sessions. >>> >> >> I'm definitely happy to help as much as I can. If you'll have something >> set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I >> definitely will. I could also read through etherpads you take notes in and >> help summarize things into forum proposals. >> >> Another thing to note is that whatever you/we submit, it doesn't have to >> be award winning :) Its totally possible to change session descriptions and >> edit who the speaker is later. >> >> Other random thought, I know Sean McGinnis has attended a lot of the >> Operators stuff in the past so maybe he could help narrow things down too? >> Not to sign him up for more work, but I know he's written a forum propsal >> or two in the past ;) >> >> >>> >>> I wish I could offer a further extension, but extending it another week >>> would push too far into the process. >>> >>> Cheers, >>> Jimmy >>> >>> Erik McCormick >>> February 27, 2019 at 12:43 PM >>> >>> Jimmy, >>> >>> I won't even get home until the 10th much less have time to follow up >>> with anyone. The formation of those sessions often come from >>> discussions spawned at the meetup and expanded upon later with folks >>> who could not attend. Could we at least get until 3/17? I understand >>> your desire to finalize the schedule, but 6 weeks out should be more >>> than enough time, no? >>> >>> Thanks, >>> Erik >>> >>> Jimmy McArthur >>> February 27, 2019 at 12:04 PM >>> >>> Hi Erik, >>> >>> We are able to extend the deadline to 11:59PM Pacific, March 10th. That >>> should give the weekend to get any additional stragglers in and still allow >>> the Forum Programming Committee enough time to manage the rest of the >>> approval and publishing process in time for people's travel needs, etc... >>> >>> For the Ops Meetup specifically, I'd suggest going a bit broader with >>> the proposals and offering to fill in the blanks later. For example, if >>> something comes up and everyone agrees it should go to the Forum, just >>> submit before the end of the Ops session. Kendall or myself would be happy >>> to help you add details a bit later in the process, should clarification be >>> necessary. We typically have enough spots for the majority of proposed >>> Forum sessions. That's not a guarantee, but food for thought. >>> >>> Cheers, >>> Jimmy >>> >>> >>> _______________________________________________ >>> Airship-discuss mailing list >>> Airship-discuss at lists.airshipit.org >>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>> >>> Erik McCormick >>> February 27, 2019 at 11:31 AM >>> Would it be possible to push the deadline back a couple weeks? I expect >>> there to be a few session proposals that will come out of the Ops Meetup >>> which ends the day before the deadline. It would be helpful to have a >>> little time to organize and submit things afterwards. >>> >>> Thanks, >>> Erik >>> >>> Jimmy McArthur >>> February 27, 2019 at 10:40 AM >>> Hi Everyone - >>> >>> A quick reminder that we are accepting Forum [1] submissions for the >>> 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas >>> through the Summit CFP tool [3] through March 8th. Don't forget to put >>> your brainstorming etherpad up on the Denver Forum page [4]. >>> >>> This is not a classic conference track with speakers and presentations. >>> OSF community members (participants in development teams, operators, >>> working groups, SIGs, and other interested individuals) discuss the topics >>> they want to cover and get alignment on and we welcome your participation. >>> The Forum is your opportunity to help shape the development of future >>> project releases. More information about the Forum [1]. >>> >>> If you have questions or concerns, please reach out to >>> speakersupport at openstack.org. >>> >>> Cheers, >>> Jimmy >>> >>> [1] https://wiki.openstack.org/wiki/Forum >>> [2] https://www.openstack.org/summit/denver-2019/ >>> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations >>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >>> ___________________________________________ >>> >>> >> Hopefully that helps! >> >> -Kendall (diablo_rojo) >> > -- Chris Morgan -------------- next part -------------- An HTML attachment was scrubbed... URL: From sean.mcginnis at gmx.com Wed Feb 27 22:08:02 2019 From: sean.mcginnis at gmx.com (Sean McGinnis) Date: Wed, 27 Feb 2019 16:08:02 -0600 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> Message-ID: <20190227220801.GA12980@sm-workstation> On Wed, Feb 27, 2019 at 01:57:42PM -0800, Kendall Nelson wrote: > > > > I think the issue is that forum submissions building on what gets > > discussed in Berlin can't be expected to be finalised whilst attendees to > > the berlin meetup are still traveling. It's not that Erik can't pull these > > things together, in fact he's an old hand at this, it's more that this > > process isn't reasonable if there's so little time to collate what we learn > > in Berlin and feed it forward to Denver. Frankly it sounds like because the > > planning committee needs 5 weeks, Erik can have two days. Seem unfair. > > > > Honestly, the decision process doesn't take much time, aside from > organizing a time that all 10 people can meet across x timezones (a thing > unto itself). Its the community feedback period, giving people enough time > to secure travel approval from their management, loading the sessions into > the actual schedule app, and other print deadlines that force us to have > everything set this far out. > > I will definitely help the ops community in whatever way I can! Do you have > remote attendance set up for the meetup? > To be clear, the issue isn't needing help writing up the submission. So great if someone can attend or watch for topics coming up that can be pulled out into Forum ideas, but the crux is that there are a lot of things discussed at these events and it may take several days after it is over to realize, "hey, that would be really useful if we could discuss that at the Forum." I don't think what Erik asked for is unreasonable. The Ops Meetup event is exactly the target we want feeding into Forum discussions. If we can give a week after the event for the Ops Meetup ends for this processing to happen, I think we increase the odds of an effective and useful Forum. Can we please extend that deadline out a few more days to make sure we get this valuable input? Sean From emccormick at cirrusseven.com Wed Feb 27 23:51:49 2019 From: emccormick at cirrusseven.com (Erik McCormick) Date: Wed, 27 Feb 2019 18:51:49 -0500 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <5C770FA4.6010409@openstack.org> References: <5C76BD8E.4070504@openstack.org> <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> <20190227220801.GA12980@sm-workstation> <5C770FA4.6010409@openstack.org> Message-ID: On Wed, Feb 27, 2019 at 5:31 PM Jimmy McArthur wrote: > > Sean, > > Sean McGinnis February 27, 2019 at 4:08 PM > > To be clear, the issue isn't needing help writing up the submission. So great > if someone can attend or watch for topics coming up that can be pulled out into > Forum ideas, but the crux is that there are a lot of things discussed at these > events and it may take several days after it is over to realize, "hey, that > would be really useful if we could discuss that at the Forum." > > Totally understood. That's why we're suggesting to put a few (I counted five Ops specific Forum talks in Berlin) placeholder sessions in for Ops with a couple of high level sentences, to be defined later. We're happy to help update the Forum suggestions after y'all have had a chance to parse Meetup outcomes into Forum topics that makes sense. OK, I surrender. I submitted 3 generic topics (as that's my limit) as placeholders for topics TBD. Additionally, Chris Morgan will submit two long-standing regular sessions for Ceph-related topics and the Ops Meetup Team gathering sometime soon. If I need to do anything else with them right now, please let me know. > > > I don't think what Erik asked for is unreasonable. The Ops Meetup event is > exactly the target we want feeding into Forum discussions. If we can give a > week after the event for the Ops Meetup ends for this processing to happen, I > think we increase the odds of an effective and useful Forum. > > I understand the POV, but keep in mind we're also trying to program against many other interests and we have deadlines that we have to reach with regards to getting comms out to the rest of the community. We've extended the deadline by two days, which I hope will give the Ops Community enough time to parse the info from the Meetup into a few bite-size bits that we can use as placeholders on the schedule, with details TBD. I put in the placeholders and am happy to update them if you can show me how. I won't know the bite-sized tidbits until I get back and talk to those who were not in attendance. We are short quite a number of regular attendees for this one due to other conflicts and it being an expensive week to be in Berlin. I hope this is acceptable. > > I want to re-emphasize, Kendall and I are happy to help in any way possible on this. If you want to pass along some napkin notes, we can do help get those into the schedule :) It's critical that we provide at least a straw man schedule to the community as early as possible, so we can identify conflicts and travel considerations for our attendees. In future, we would love to know cutoff dates as soon as you know what they are. We don't have a lot of control over exact dates of the meetup as it's based primarily on the availability of the host organization. However, if it comes soon enough we can try to influence the date and plan for it as best we can. I would also be curious to hear from anyone who is basing their travel choices on the approval status of a Forum session. I believe that this number is 0, but I'm ready to be proven wrong. > > Thanks, > Jimmy > > > Can we please extend that deadline out a few more days to make sure we get this > valuable input? > > > Sean > Kendall Nelson February 27, 2019 at 3:57 PM > Hello :) > > On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan wrote: >> >> I think the issue is that forum submissions building on what gets discussed in Berlin can't be expected to be finalised whilst attendees to the berlin meetup are still traveling. It's not that Erik can't pull these things together, in fact he's an old hand at this, it's more that this process isn't reasonable if there's so little time to collate what we learn in Berlin and feed it forward to Denver. Frankly it sounds like because the planning committee needs 5 weeks, Erik can have two days. Seem unfair. > > > Honestly, the decision process doesn't take much time, aside from organizing a time that all 10 people can meet across x timezones (a thing unto itself). Its the community feedback period, giving people enough time to secure travel approval from their management, loading the sessions into the actual schedule app, and other print deadlines that force us to have everything set this far out. > > I will definitely help the ops community in whatever way I can! Do you have remote attendance set up for the meetup? > We have no capacity for remote attendees other than etherpads. I'm happy to Skype you in for things as needed, but there's no good way to have multiple attendees there 100% of the time. We have no resources for such things :(. >> >> Chris >> >> On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson wrote: >>> >>> Another- nother thought: You could take a look at what is submitted by project teams closer to the deadline and see if your ideas might fit well with theirs since they are looking for feedback from operators anyway. In the past I have always hoped for more engagement in the forum sessions I've submitted but only ever had one or two operators able to join us. >>> I have always made a habit of going through other session topics and scrapping ones of our own that were redundant. For Sydney, I had put up an FFU session that conflicted with one Arkady proposed. We chose to combine them and worked together on it. That's how it should be. I always prefer devs and ops to be in collective sessions as opposed to silo'd off on their own. That should be what the forum is all about. -Erik >>> -Kendall (diablo_rojo) >>> >>> On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson wrote: >>>> >>>> Hello :) >>>> >>>> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur wrote: >>>>> >>>>> Erik, >>>>> >>>>> I definitely understand the timeline is tight. One of the reasons that we publish the schedule so early is to enable community members to plan their schedule early, especially as there is more overlap with the main Summit Schedule in Denver. Additionally, travel approval is often predicated upon someone showing they're leading/moderating a session. >>>>> >>>>> Before publishing the schedule, we print a draft Forum schedule for community feedback and start promotion of the schedule, which we have to put up on the OpenStack website and apps at 5 weeks out. Extending the date beyond the 10th won't give the Forum Selection Committee enough time to complete those tasks. >>>>> >>>>> I think if the Ops team can come up with some high level discussion topics, we'll be happy to put some holds in the Forum schedule for Ops-specific content. diablo_rojo has also offered to attend some of the Ops sessions remotely as well, if that would help you all shape some things into actual sessions. >>>> >>>> >>>> I'm definitely happy to help as much as I can. If you'll have something set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I definitely will. I could also read through etherpads you take notes in and help summarize things into forum proposals. >>>> >>>> Another thing to note is that whatever you/we submit, it doesn't have to be award winning :) Its totally possible to change session descriptions and edit who the speaker is later. >>>> >>>> Other random thought, I know Sean McGinnis has attended a lot of the Operators stuff in the past so maybe he could help narrow things down too? Not to sign him up for more work, but I know he's written a forum propsal or two in the past ;) >>>> >>>>> >>>>> >>>>> I wish I could offer a further extension, but extending it another week would push too far into the process. >>>>> >>>>> Cheers, >>>>> Jimmy >>>>> >>>>> Erik McCormick February 27, 2019 at 12:43 PM >>>>> >>>>> Jimmy, >>>>> >>>>> I won't even get home until the 10th much less have time to follow up >>>>> with anyone. The formation of those sessions often come from >>>>> discussions spawned at the meetup and expanded upon later with folks >>>>> who could not attend. Could we at least get until 3/17? I understand >>>>> your desire to finalize the schedule, but 6 weeks out should be more >>>>> than enough time, no? >>>>> >>>>> Thanks, >>>>> Erik >>>>> >>>>> Jimmy McArthur February 27, 2019 at 12:04 PM >>>>> >>>>> Hi Erik, >>>>> >>>>> We are able to extend the deadline to 11:59PM Pacific, March 10th. That should give the weekend to get any additional stragglers in and still allow the Forum Programming Committee enough time to manage the rest of the approval and publishing process in time for people's travel needs, etc... >>>>> >>>>> For the Ops Meetup specifically, I'd suggest going a bit broader with the proposals and offering to fill in the blanks later. For example, if something comes up and everyone agrees it should go to the Forum, just submit before the end of the Ops session. Kendall or myself would be happy to help you add details a bit later in the process, should clarification be necessary. We typically have enough spots for the majority of proposed Forum sessions. That's not a guarantee, but food for thought. >>>>> >>>>> Cheers, >>>>> Jimmy >>>>> >>>>> >>>>> _______________________________________________ >>>>> Airship-discuss mailing list >>>>> Airship-discuss at lists.airshipit.org >>>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>>>> >>>>> Erik McCormick February 27, 2019 at 11:31 AM >>>>> Would it be possible to push the deadline back a couple weeks? I expect there to be a few session proposals that will come out of the Ops Meetup which ends the day before the deadline. It would be helpful to have a little time to organize and submit things afterwards. >>>>> >>>>> Thanks, >>>>> Erik >>>>> >>>>> Jimmy McArthur February 27, 2019 at 10:40 AM >>>>> Hi Everyone - >>>>> >>>>> A quick reminder that we are accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas through the Summit CFP tool [3] through March 8th. Don't forget to put your brainstorming etherpad up on the Denver Forum page [4]. >>>>> >>>>> This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. >>>>> >>>>> If you have questions or concerns, please reach out to speakersupport at openstack.org. >>>>> >>>>> Cheers, >>>>> Jimmy >>>>> >>>>> [1] https://wiki.openstack.org/wiki/Forum >>>>> [2] https://www.openstack.org/summit/denver-2019/ >>>>> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations >>>>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >>>>> ___________________________________________ >>>>> >>>> >>>> Hopefully that helps! >>>> >>>> -Kendall (diablo_rojo) >> >> >> >> -- >> Chris Morgan > > > - Kendall Nelson (diablo_rojo) > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > Chris Morgan February 27, 2019 at 3:25 PM > I think the issue is that forum submissions building on what gets discussed in Berlin can't be expected to be finalised whilst attendees to the berlin meetup are still traveling. It's not that Erik can't pull these things together, in fact he's an old hand at this, it's more that this process isn't reasonable if there's so little time to collate what we learn in Berlin and feed it forward to Denver. Frankly it sounds like because the planning committee needs 5 weeks, Erik can have two days. Seem unfair. > > Chris > > > > -- > Chris Morgan > Kendall Nelson February 27, 2019 at 1:19 PM > Another- nother thought: You could take a look at what is submitted by project teams closer to the deadline and see if your ideas might fit well with theirs since they are looking for feedback from operators anyway. In the past I have always hoped for more engagement in the forum sessions I've submitted but only ever had one or two operators able to join us. > > -Kendall (diablo_rojo) > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Kendall Nelson February 27, 2019 at 1:14 PM > Hello :) > > On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur wrote: >> >> Erik, >> >> I definitely understand the timeline is tight. One of the reasons that we publish the schedule so early is to enable community members to plan their schedule early, especially as there is more overlap with the main Summit Schedule in Denver. Additionally, travel approval is often predicated upon someone showing they're leading/moderating a session. >> >> Before publishing the schedule, we print a draft Forum schedule for community feedback and start promotion of the schedule, which we have to put up on the OpenStack website and apps at 5 weeks out. Extending the date beyond the 10th won't give the Forum Selection Committee enough time to complete those tasks. >> >> I think if the Ops team can come up with some high level discussion topics, we'll be happy to put some holds in the Forum schedule for Ops-specific content. diablo_rojo has also offered to attend some of the Ops sessions remotely as well, if that would help you all shape some things into actual sessions. > > > I'm definitely happy to help as much as I can. If you'll have something set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I definitely will. I could also read through etherpads you take notes in and help summarize things into forum proposals. > > Another thing to note is that whatever you/we submit, it doesn't have to be award winning :) Its totally possible to change session descriptions and edit who the speaker is later. > > Other random thought, I know Sean McGinnis has attended a lot of the Operators stuff in the past so maybe he could help narrow things down too? Not to sign him up for more work, but I know he's written a forum propsal or two in the past ;) > >> >> >> I wish I could offer a further extension, but extending it another week would push too far into the process. >> >> Cheers, >> Jimmy >> >> Erik McCormick February 27, 2019 at 12:43 PM >> >> Jimmy, >> >> I won't even get home until the 10th much less have time to follow up >> with anyone. The formation of those sessions often come from >> discussions spawned at the meetup and expanded upon later with folks >> who could not attend. Could we at least get until 3/17? I understand >> your desire to finalize the schedule, but 6 weeks out should be more >> than enough time, no? >> >> Thanks, >> Erik >> >> Jimmy McArthur February 27, 2019 at 12:04 PM >> >> Hi Erik, >> >> We are able to extend the deadline to 11:59PM Pacific, March 10th. That should give the weekend to get any additional stragglers in and still allow the Forum Programming Committee enough time to manage the rest of the approval and publishing process in time for people's travel needs, etc... >> >> For the Ops Meetup specifically, I'd suggest going a bit broader with the proposals and offering to fill in the blanks later. For example, if something comes up and everyone agrees it should go to the Forum, just submit before the end of the Ops session. Kendall or myself would be happy to help you add details a bit later in the process, should clarification be necessary. We typically have enough spots for the majority of proposed Forum sessions. That's not a guarantee, but food for thought. >> >> Cheers, >> Jimmy >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> >> Erik McCormick February 27, 2019 at 11:31 AM >> Would it be possible to push the deadline back a couple weeks? I expect there to be a few session proposals that will come out of the Ops Meetup which ends the day before the deadline. It would be helpful to have a little time to organize and submit things afterwards. >> >> Thanks, >> Erik >> >> Jimmy McArthur February 27, 2019 at 10:40 AM >> Hi Everyone - >> >> A quick reminder that we are accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas through the Summit CFP tool [3] through March 8th. Don't forget to put your brainstorming etherpad up on the Denver Forum page [4]. >> >> This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. >> >> If you have questions or concerns, please reach out to speakersupport at openstack.org. >> >> Cheers, >> Jimmy >> >> [1] https://wiki.openstack.org/wiki/Forum >> [2] https://www.openstack.org/summit/denver-2019/ >> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations >> [4] https://wiki.openstack.org/wiki/Forum/Denver2019 >> ___________________________________________ >> > > Hopefully that helps! > > -Kendall (diablo_rojo) > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > From tony at bakeyournoodle.com Thu Feb 28 00:10:26 2019 From: tony at bakeyournoodle.com (Tony Breeds) Date: Thu, 28 Feb 2019 11:10:26 +1100 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: References: <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> <20190227220801.GA12980@sm-workstation> <5C770FA4.6010409@openstack.org> Message-ID: <20190228001024.GD13081@thor.bakeyournoodle.com> On Wed, Feb 27, 2019 at 06:51:49PM -0500, Erik McCormick wrote: > In future, we would love to know cutoff dates as soon as you know what > they are. We don't have a lot of control over exact dates of the > meetup as it's based primarily on the availability of the host > organization. However, if it comes soon enough we can try to influence > the date and plan for it as best we can. Given it's the same format every time they're known now? See: https://wiki.openstack.org/wiki/Forum for the format. So we know the post Denver summit is in Shnaghai: [tony at thor ~]$ python3 Python 3.7.2 (default, Jan 16 2019, 19:49:22) [GCC 8.2.1 20181215 (Red Hat 8.2.1-6)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import datetime >>> T=datetime.date(2019,11,4) >>> print('Etherpads %s' % (T - datetime.timedelta(weeks=11))) Etherpads 2019-08-19 >>> print('Deadline %s' % (T - datetime.timedelta(weeks=7))) Deadline 2019-09-16 >>> > I would also be curious to hear from anyone who is basing their travel > choices on the approval status of a Forum session. I believe that this > number is 0, but I'm ready to be proven wrong. There are companies that only fund 'speakers' for travel and there are some developer types (like myself) that will be moderating forum sessions (hopefully) but not talking at the summit. So there certainly *are* people in this situation. Tony. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL: From emccormick at cirrusseven.com Thu Feb 28 00:21:54 2019 From: emccormick at cirrusseven.com (Erik McCormick) Date: Wed, 27 Feb 2019 19:21:54 -0500 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <20190228001024.GD13081@thor.bakeyournoodle.com> References: <5C76D125.2040404@openstack.org> <5C76E02F.4010906@openstack.org> <20190227220801.GA12980@sm-workstation> <5C770FA4.6010409@openstack.org> <20190228001024.GD13081@thor.bakeyournoodle.com> Message-ID: On Wed, Feb 27, 2019 at 7:10 PM Tony Breeds wrote: > > On Wed, Feb 27, 2019 at 06:51:49PM -0500, Erik McCormick wrote: > > > In future, we would love to know cutoff dates as soon as you know what > > they are. We don't have a lot of control over exact dates of the > > meetup as it's based primarily on the availability of the host > > organization. However, if it comes soon enough we can try to influence > > the date and plan for it as best we can. > > Given it's the same format every time they're known now? > See: https://wiki.openstack.org/wiki/Forum for the format. > > So we know the post Denver summit is in Shnaghai: > > [tony at thor ~]$ python3 > Python 3.7.2 (default, Jan 16 2019, 19:49:22) > [GCC 8.2.1 20181215 (Red Hat 8.2.1-6)] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> import datetime > >>> T=datetime.date(2019,11,4) > >>> print('Etherpads %s' % (T - datetime.timedelta(weeks=11))) > Etherpads 2019-08-19 > >>> print('Deadline %s' % (T - datetime.timedelta(weeks=7))) > Deadline 2019-09-16 > >>> > Deadline for Berlin was 44 days before the summit. Deadline for this one was 51 days (now 49). The extra week I asked for would bring it in line exactly, so +1 to your code and I get the extra week. > > I would also be curious to hear from anyone who is basing their travel > > choices on the approval status of a Forum session. I believe that this > > number is 0, but I'm ready to be proven wrong. > > There are companies that only fund 'speakers' for travel and there are > some developer types (like myself) that will be moderating forum > sessions (hopefully) but not talking at the summit. > > So there certainly *are* people in this situation. > As per my previous comments, I submit to penance for underestimating the varied travel situations attendees face. My apologies > Tony. From kyle.oh95 at gmail.com Thu Feb 28 01:43:32 2019 From: kyle.oh95 at gmail.com (Jaewook Oh) Date: Thu, 28 Feb 2019 10:43:32 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Austin, 1. - Here is the spec Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz RAM : 32GB (Is this the problem? I already saw for the controller 64GB RAM is needed, but I'm not sure, cause the installation was just stuck literally, SSD : 500GB SuperMicro - Bios Setting: I enabled and disabled as the instruction said. And at first try, I didn't used UEFI, after failure, I changed it into UEFI, but the result was same. I enabled VTx/Iommu. 2. I used bare metal one.. however when I pressed the buttons, nothing happened. And the controller-1 is just stopped as I said before. Thank you for helping me :) Best Regards, Jaewook -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.cordoba.malibran at intel.com Thu Feb 28 02:37:07 2019 From: erich.cordoba.malibran at intel.com (Cordoba Malibran, Erich) Date: Thu, 28 Feb 2019 02:37:07 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> Message-ID: <50734A18-FDF6-49B2-B571-117E53076D8D@intel.com> Hi, On PXE booting the serial output is used instead of the screen. You can change this on the grub menu (hit “e” when grub appears) by replacing ttyS0 to tty0. -Erich From: Jaewook Oh Date: Wednesday, February 27, 2019 at 7:12 PM To: "Lin, Shuicheng" Cc: starlingx-discuss Subject: Re: [Starlingx-discuss] Duplex PXE Booting seems failed Hi Shuicheng, Thank you for your kind explain :) For the port one, it really was understandable why the port had been changed. But for the PXE one, still I couldn't get any change. As you said, system host-show controller-1 | grep install does not change from the first one install_output = text install_state = None install_state_info = None And also, the display doesn't seem to be changed. It does not reboot at all. It keeps showing 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. Again.. I rechecked my BIOS setting, but it was not the problem. Do you have any suggestion? Best Regards, Jaewook. 2019년 2월 22일 (금) 오후 4:11, Lin, Shuicheng >님이 작성: Hi Jaewook, For the 8080 change, you could find the history in below mail: http://lists.starlingx.io/pipermail/starlingx-discuss/2019-February/003017.html For the PXE mode, you could use “system host-show controller-1 | grep install” to get controller-1 install status. Please make sure controller-1 is configured to boot with disk first. Just manuall choose pxeboot for the first time installation. Otherwise, if controller-1 is configured to using pxeboot as first priority, it will lead to deadloop of installation. Best Regards Shuicheng From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Friday, February 22, 2019 2:54 PM To: starlingx-discuss > Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Feb 28 06:47:29 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 28 Feb 2019 06:47:29 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed References: Message-ID: Hi : Are you using iso built by yourself ? or taking iso directly from cengn? From: Jaewook Oh [mailto:jwoh95 at dcn.ssu.ac.kr] Sent: Thursday, February 28, 2019 9:30 AM To: Sun, Austin > Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex PXE Booting seems failed Hi Austin, I thought I had already replied to the mail on 22, but it seems there were some mistakes. Here are the information. 1. - Here is the spec Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz RAM : 32GB (Is this the problem? I already saw for the controller 64GB RAM is needed, but I'm not sure, cause the installation was just stuck literally, SSD : 500GB SuperMicro - Bios Setting: I enabled and disabled as the instruction said. And at first try, I didn't used UEFI, after failure, I changed it into UEFI, but the result was same. I enabled VTx/Iommu enable or not ? 2. I used bare metal one.. however when I pressed the buttons, nothing happened. And the controller-1 is just stopped as I said before. Thank you for helping me :) Best Regards, Jaewook. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwoh95 at dcn.ssu.ac.kr Thu Feb 28 06:50:58 2019 From: jwoh95 at dcn.ssu.ac.kr (Jaewook Oh) Date: Thu, 28 Feb 2019 15:50:58 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi, I used Feb 18th's boot image, Thanks. Jaewook. 2019년 2월 28일 (목) 오후 3:47, Sun, Austin 님이 작성: > > > Hi : > > Are you using iso built by yourself ? or taking iso directly from > cengn? > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jwoh95 at dcn.ssu.ac.kr Thu Feb 28 06:52:39 2019 From: jwoh95 at dcn.ssu.ac.kr (Jaewook Oh) Date: Thu, 28 Feb 2019 15:52:39 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: <50734A18-FDF6-49B2-B571-117E53076D8D@intel.com> References: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> <50734A18-FDF6-49B2-B571-117E53076D8D@intel.com> Message-ID: Hi Erich, Let me check that way, thanks for the advice :) BR, Jaewook. 2019년 2월 28일 (목) 오전 11:37, Cordoba Malibran, Erich < erich.cordoba.malibran at intel.com>님이 작성: > Hi, > > > > On PXE booting the serial output is used instead of the screen. You can > change this on the > > grub menu (hit “e” when grub appears) by replacing ttyS0 to tty0. > > > > -Erich > -------------- next part -------------- An HTML attachment was scrubbed... URL: From juan.carlos.alonso at intel.com Thu Feb 28 06:59:29 2019 From: juan.carlos.alonso at intel.com (Alonso, Juan Carlos) Date: Thu, 28 Feb 2019 06:59:29 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190226 Message-ID: <8557B550001AFB46A43A0CCC314BF85153C9E96A@FMSMSX108.amr.corp.intel.com> Status of the Sanity Test for last CENGN ISO - f/Stein branch: bootimage.iso from 2019-Feb-26 (link) Status: GREEN =========================================== Sanity Test is executed in a Containers - Bare Metal Environment Simplex Setup Manual [PASS] Provisioning Manual [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 54 TCs PASS ] =========================================== Sanity Test is executed in a Containers - Virtual Environment Simplex Setup 04 TCs [PASS] Provisioning Manual [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 02 TCs [PASS] TOTAL: [ 58 TCs PASS ] Duplex Setup 04 TCs [] Provisioning Manual [] Sanity OpenStack 55 TCs [] Sanity Platform In Development TOTAL: [ 59 TCs PASS ] ------------------------------------------------------------------ Regards. Juan Carlos Alonso -------------- next part -------------- An HTML attachment was scrubbed... URL: From jose.perez.carranza at intel.com Thu Feb 28 13:45:21 2019 From: jose.perez.carranza at intel.com (Perez Carranza, Jose) Date: Thu, 28 Feb 2019 13:45:21 +0000 Subject: [Starlingx-discuss] issue about create network on horzon In-Reply-To: <09777F12A863964D9F4AE780D4FEA3E83E654928@SHSMSX104.ccr.corp.intel.com> References: <09777F12A863964D9F4AE780D4FEA3E83E654928@SHSMSX104.ccr.corp.intel.com> Message-ID: <0A5D9A624DF90343892F8F3FE7DE525A2A946DB8@fmsmsx101.amr.corp.intel.com> Hi I think this open bug is affecting that functionality: https://bugs.launchpad.net/starlingx/+bug/1804863 Regards, José From: He, Zhiwei [mailto:zhiwei.he at intel.com] Sent: Monday, February 25, 2019 9:02 PM To: 'starlingx-discuss' Cc: Li, Baoqian Subject: [Starlingx-discuss] issue about create network on horzon Hi Expert; We have try to using "Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-Jan-11 (link)" to make SR IOV network, When the create network with dashboard ,but fail due to the "Danger:An error occurred, please try again later", attached horizon log for you 2019-02-19 21:29:53,534 [ERROR] django.request: Internal Server Error: /admin/networks/create/ in the horzon log [cid:image001.jpg at 01D4CF39.70CA0400] Thanks! zhiwei -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8602 bytes Desc: image001.jpg URL: From Ian.Jolliffe at windriver.com Thu Feb 28 14:15:28 2019 From: Ian.Jolliffe at windriver.com (Jolliffe, Ian) Date: Thu, 28 Feb 2019 14:15:28 +0000 Subject: [Starlingx-discuss] [TSC] Minutes from 2/21 meeting Message-ID: <3FD61411-C370-4694-9C09-AB5294D6ED73@windriver.com> Hi all; TSC attendees: Ana, Brent, Curtis, Dean, Ian, Miguel, Saul, Shuquan Minutes: 2/21 MultiOS Is there an existing deb build system in OpenStack? - No, typically downstream There is a community planning meeting in openstack for packaging? (missed this one) Finding other people doing similar work and who can help out Public service announcement - MultiOS meeting on Mondays 7am PST will provide update and insights into experiments in flight and planned. - Please join if interested in this topic. Denver summit - workshop discussion https://etherpad.openstack.org/p/stx-denver-2019-workshop Shuquan and Curtis have updated abstract - please have a look and review Finalize by next meeting Action: Need abstract to secure slot for summit - we should list our presentation slots so we don't have conflicts. Shuquan Resources for workshop Ildiko could reach out to Vexxhost, once Curtis checks with Packet.com/John S. Action: Curtis will check with John Studarus on using packet.com infrastructure for the workshop Curtis is working with John S. on another workshop (openstack-ansible) that is also using packet.com infra Action: Shuquan will update Ildiko with some additional details for the workshop, including times that will not work for the facilitators NOTE: Curtis has the openstack-ansible workshop on Monday from 2:00 to 3:30PM https://www.openstack.org/summit/denver-2019/summit-schedule/events/23210/workshop-deploying-openstack-ansible Denver summit talks accepted on STX Congratulations to community members who had a talk accepted. On boarding and other sessions are coming together - (Project update 20 min and On boarding - 40 min) Forum sessions come next Packet next steps Curtis - Waiting for MOU from Packet, then that would go to the OpenStack Foundation for signage in some capacity Curtis - Should we have some kind of SIG or WG...how do we want to handle this? Work in a SIG initialy then spin out the other projects when they become mature? Curtis - I see at least three major areas. Some long running, some short running projects. Long term project - Performance testing, daily/weekly testing, publish results Long term project - CI/CD Short term project - IoT project using packet edge resources Options: Some concern about having another meeting, finding a slot, etc Maybe we incubate it informally a bit more, and then place the work into the appropriate existing subteams Decision: keep it as a standing item at the TSC meeting for the time being OpenStack work At Risk for current release - needs some help upstream. see minutes from Project call 2/20 Nova patches at risk of missing cut off - some not staffed, some are in review cycles - PTG items at risk Full details at https://docs.google.com/spreadsheets/d/1udAtEpQljV2JZVs-525UhWyx-5ePOaSSkKD1CS27ohU/edit?usp=sharing Live Migration Patch w/ Pinning (numa_topology) active, but need to monitor to see if it's going to land soon Shared/Dedicated vcpus on the same host or standardize CPU resource tracking: At Risk Shared VCPU Extension these haven't been active for ~9 weeks vCPU model unassigned, no chance of this being done for this release now Clean Up Orphan Instances likely to suffer same lack of attention in community when code posted Server Group Show Enhancement Numa Topology API need Core attention on these two Add support for emulated virtual TPM - needs attention Disk Performance Fixes Extra Spec Validation - these two are suffering from lack of reviews by Cores Action: attend nova meeting to raise request for review - list the review items on review schedule for the Nova team - provide more visibility NOTES: New project that may be of interest - Open Source Evolved Packet Core: https://www.opennetworking.org/news-and-events/press-releases/onf-sprint-launch-open-evolved-mobile-core-omec-open-source-project/ ZTP conference might be of interest : https://www.layer123.com/zta-agenda-day1/ Regards; Ian From scott.little at windriver.com Thu Feb 28 14:34:40 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Feb 2019 09:34:40 -0500 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> Message-ID: Jenkins under git is basically a snapshot of the jenkins home directory, or a subset thereof.   I think it really needs to be a git unto itself. Scott On 2019-02-25 12:52 p.m., Jones, Bruce E wrote: > Great idea! Maybe stx-tools? > > brucej > > -----Original Message----- > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > Sent: Monday, February 25, 2019 9:50 AM > To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io > Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git > > Hi Scott, > > I think that is a great idea! > > I would suggest a new stx-automation or stx-ci repository, also not sure where is the best place, I would suggest github, but for sure Dean will have better insights on this :) > > -Erich > > On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: >> The idea was floated several weeks ago that we should place the >> jenkins scripts used by starlingx.cengn.ca builds under git revision >> control, and publish them somewhere. >> >> If we are all agreed this would be a good thing, I would like to move >> forward with that proposal. >> >> Where should we publish it, github or openstack? >> >> If openstack, I'll need some pointers on how to set up the new git. >> >> >> Thanks >> >> Scott >> >> >> >> _______________________________________________ >> 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 Don.Penney at windriver.com Thu Feb 28 14:56:41 2019 From: Don.Penney at windriver.com (Penney, Don) Date: Thu, 28 Feb 2019 14:56:41 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: <9700A18779F35F49AF027300A49E7C765FE85D06@SHSMSX101.ccr.corp.intel.com> <50734A18-FDF6-49B2-B571-117E53076D8D@intel.com> Message-ID: <6703202FD9FDFF4A8DA9ACF104AE129FBA44BC73@ALA-MBD.corp.ad.wrs.com> You can also define this as an installation parameter when configuring the node. So when you do: system host-update 2 personality=controller you can also set the console at this time, such as: system host-update 2 personality=controller console= or: system host-update 2 personality=controller console=tty0 The default console setting is ttyS0,115200, which you can see with a “system host-show controller-1” command. From: Jaewook Oh [mailto:jwoh95 at dcn.ssu.ac.kr] Sent: Thursday, February 28, 2019 1:53 AM To: Cordoba Malibran, Erich Cc: Jaewook Oh; Lin, Shuicheng; starlingx-discuss Subject: Re: [Starlingx-discuss] Duplex PXE Booting seems failed Hi Erich, Let me check that way, thanks for the advice :) BR, Jaewook. 2019년 2월 28일 (목) 오전 11:37, Cordoba Malibran, Erich >님이 작성: Hi, On PXE booting the serial output is used instead of the screen. You can change this on the grub menu (hit “e” when grub appears) by replacing ttyS0 to tty0. -Erich -------------- next part -------------- An HTML attachment was scrubbed... URL: From vm.rod25 at gmail.com Thu Feb 28 16:16:56 2019 From: vm.rod25 at gmail.com (Victor Rodriguez) Date: Thu, 28 Feb 2019 10:16:56 -0600 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> Message-ID: As discussed in build meeting, the new repo might live in: https://github.com/starlingx-staging Saul can help with the creation of the repo regards On Thu, Feb 28, 2019 at 8:36 AM Scott Little wrote: > > Jenkins under git is basically a snapshot of the jenkins home directory, > or a subset thereof. I think it really needs to be a git unto itself. > > Scott > > > On 2019-02-25 12:52 p.m., Jones, Bruce E wrote: > > Great idea! Maybe stx-tools? > > > > brucej > > > > -----Original Message----- > > From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] > > Sent: Monday, February 25, 2019 9:50 AM > > To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git > > > > Hi Scott, > > > > I think that is a great idea! > > > > I would suggest a new stx-automation or stx-ci repository, also not sure where is the best place, I would suggest github, but for sure Dean will have better insights on this :) > > > > -Erich > > > > On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: > >> The idea was floated several weeks ago that we should place the > >> jenkins scripts used by starlingx.cengn.ca builds under git revision > >> control, and publish them somewhere. > >> > >> If we are all agreed this would be a good thing, I would like to move > >> forward with that proposal. > >> > >> Where should we publish it, github or openstack? > >> > >> If openstack, I'll need some pointers on how to set up the new git. > >> > >> > >> Thanks > >> > >> Scott > >> > >> > >> > >> _______________________________________________ > >> 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 yang.liu at windriver.com Thu Feb 28 16:50:29 2019 From: yang.liu at windriver.com (Liu, Yang) Date: Thu, 28 Feb 2019 16:50:29 +0000 Subject: [Starlingx-discuss] [Containers] Sanity Test (no-proxy) - ISO 20190226 References: <19C65A6E92EA384D809B1772130CD7F862187677@ALA-MBD.corp.ad.wrs.com> <3CAA827B7A79BA46B15B280EC82088FE4827B24C@ALA-MBD.corp.ad.wrs.com> Message-ID: <19C65A6E92EA384D809B1772130CD7F8621876D3@ALA-MBD.corp.ad.wrs.com> Load: f/stein 2019-02-26 ( http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190226T183733Z/outputs/iso/ ) Environment: Bare metal, no proxy, no mirror Simplex ----------- Overall Status: Yellow Pass Rate: 21/22 (95.5%) Issues: 1. #1816177: AIO-SX: stx-openstack application failed after lock/unlock controller (Pods were all healthy even though app failed. Workaround: reapply the app) Duplex ---------- Overall Status: Yellow Pass Rate: 24/29 (82.8%) Issues: 1. #1818088 Containers: platform memory threshold alarms seen on AIO-DX systems since stx-openstack apply 2. #1818095 Containers: ceph-mon failed on active controller after a failed swact Notes: - Force reboot, reboot including lock/unlock controller test cases skipped due to current known limitation with containers Standard (2+3) -------------------- Overall Status: Yellow Pass Rate: 34/35 (97.1%) Issues: 1. stx-openstack reapply failed at applying armada-manifest after swact to controller-1 (This issue does not happen on subsequent reapply from controller-1) Notes: - Force reboot controller test case skipped due to current known limitation with containers Dedicated Storage (2+2+2) ------------------------------------ Overall Status: Yellow Pass Rate: 32/35 (91.4%) Issues: 1. stx-openstack reapply failed at applying armada-manifest after swact to controller-1 (This issue does not happen on subsequent reapply from controller-1) 2. #1818118 Containers: vm unreachable for minutes after live migration or vm reboot Notes: - Force reboot controller test case skipped due to current known limitation with containers ===================== Latest Recommended Load ===================== http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein/centos/20190226T183733Z/outputs/iso/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Feb 28 17:16:27 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Feb 2019 17:16:27 +0000 Subject: [Starlingx-discuss] k3 announced Message-ID: <9A85D2917C58154C960D95352B22818BC3AD8152@fmsmsx121.amr.corp.intel.com> FYI - A new project was just announced - a small footprint K8S distribution. Might be worth a look and a compare/contrast with our approach. https://rancher.com/blog/2019/2019-02-26-introducing-k3s-the-lightweight-kubernetes-distribution-built-for-the-edge/ brucej -------------- next part -------------- An HTML attachment was scrubbed... URL: From build.starlingx at gmail.com Thu Feb 28 17:24:44 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Feb 2019 12:24:44 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 171 - Failure! Message-ID: <952961211.26.1551374689954.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 171 Status: Failure Timestamp: 20190228T154231Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T151328Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-centos76/20190228T151328Z DOCKER_BUILD_ID: jenkins-f-centos76-20190228T151328Z-builder MY_REPO: /localdisk/designer/jenkins/f-centos76/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T151328Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos76/centos/20190228T151328Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos76 From build.starlingx at gmail.com Thu Feb 28 17:24:52 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Feb 2019 12:24:52 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_centos76_pike - Build # 2 - Still Failing! In-Reply-To: <775262187.34.1550174394958.JavaMail.javamailuser@localhost> References: <775262187.34.1550174394958.JavaMail.javamailuser@localhost> Message-ID: <697160145.29.1551374693007.JavaMail.javamailuser@localhost> Project: STX_build_centos76_pike Build #: 2 Status: Still Failing Timestamp: 20190228T151328Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T151328Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From hayde.martinez.landa at intel.com Thu Feb 28 18:00:08 2019 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Thu, 28 Feb 2019 18:00:08 +0000 Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required Message-ID: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> Hi All, Guillermo and I are currently working on the StarlingX in a box project, we are helding weekly meetings on Thursdays at 9:30 am PDT, We’ll send an update with the Zoom link soon, if anyone is interested in joining the efforts we welcome you. We’ve been doing some research and looking for different options, first of all we were told to consider the python vbox installer As part of this effort [0], but we want to bring to the table another options. 1) Vagrant [1] - This tool has proven itself over time to provide solutions for development environments easily and fast. 2) GoVM [2]- This tool is young in comparison and it's currently under development but so far has proven itself to be faster and more flexible than vagrant. Vagrant: Pros: - Has been around for a long time - It is well documented - A lot of people is used to it - Has a lot of provisioning plug-ins - Flexible and easy. Cons: - It is not as fast as GoVM. - It has a lot of overhead taking in count what we need from it - The ramp up is slower compare to GoVM. GoVM: Pros: - It has a small footprint. - It runs very fast (it is made on Go) - The ramp up is faster. - The main developers sits three desks from us (hehe (:) - It has a "compose" like option Cons: - It is not well known yet - The documentation is still lacking - It does not have that many plug ins - It is still under development (which can also be a pro because it will get better) We also are considering to use Packer[3] to create the main images we are going to work with. Packer is a tool that is well integrated with vagrant since it is also from hashicorp but GoVM can work with those images as well. Right now we are having an issue with creating the base images from starlingx ISO since the installation method is not standard and it requires to create send an user and double password, We are working on solutions for this, will keep you updated. Please share your thoughts and comments, let us know if you need more information or details on these, and also if you now another tool that works well and can help us in this effort. [0] https://review.openstack.org/#/c/637958/ [1] https://www.vagrantup.com/ [2] https://github.com/govm-project/govm [3] https://packer.io/ From bruce.e.jones at intel.com Thu Feb 28 18:32:36 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Feb 2019 18:32:36 +0000 Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required In-Reply-To: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> References: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3AD8265@fmsmsx121.amr.corp.intel.com> Nice to see this moving forward! I have a few questions. * What makes one of these tools faster than the others? Faster at creating the images? Do the images run faster? * What did the Airship team use to create Airship in a Bottle? * Is GoVM capable of doing what we need it to do? brucej -----Original Message----- From: Martinez Landa, Hayde [mailto:hayde.martinez.landa at intel.com] Sent: Thursday, February 28, 2019 10:00 AM To: starlingx-discuss at lists.starlingx.io Cc: Ponce Castaneda, Guillermo A Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required Hi All, Guillermo and I are currently working on the StarlingX in a box project, we are helding weekly meetings on Thursdays at 9:30 am PDT, We’ll send an update with the Zoom link soon, if anyone is interested in joining the efforts we welcome you. We’ve been doing some research and looking for different options, first of all we were told to consider the python vbox installer As part of this effort [0], but we want to bring to the table another options. 1) Vagrant [1] - This tool has proven itself over time to provide solutions for development environments easily and fast. 2) GoVM [2]- This tool is young in comparison and it's currently under development but so far has proven itself to be faster and more flexible than vagrant. Vagrant: Pros: - Has been around for a long time - It is well documented - A lot of people is used to it - Has a lot of provisioning plug-ins - Flexible and easy. Cons: - It is not as fast as GoVM. - It has a lot of overhead taking in count what we need from it - The ramp up is slower compare to GoVM. GoVM: Pros: - It has a small footprint. - It runs very fast (it is made on Go) - The ramp up is faster. - The main developers sits three desks from us (hehe (:) - It has a "compose" like option Cons: - It is not well known yet - The documentation is still lacking - It does not have that many plug ins - It is still under development (which can also be a pro because it will get better) We also are considering to use Packer[3] to create the main images we are going to work with. Packer is a tool that is well integrated with vagrant since it is also from hashicorp but GoVM can work with those images as well. Right now we are having an issue with creating the base images from starlingx ISO since the installation method is not standard and it requires to create send an user and double password, We are working on solutions for this, will keep you updated. Please share your thoughts and comments, let us know if you need more information or details on these, and also if you now another tool that works well and can help us in this effort. [0] https://review.openstack.org/#/c/637958/ [1] https://www.vagrantup.com/ [2] https://github.com/govm-project/govm [3] https://packer.io/ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From hayde.martinez.landa at intel.com Thu Feb 28 18:40:34 2019 From: hayde.martinez.landa at intel.com (Martinez Landa, Hayde) Date: Thu, 28 Feb 2019 18:40:34 +0000 Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD8265@fmsmsx121.amr.corp.intel.com> References: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> <9A85D2917C58154C960D95352B22818BC3AD8265@fmsmsx121.amr.corp.intel.com> Message-ID: Hi Bruce, Answering your questions: - It is faster at both creating the images, running the images and also the ramp up for beginners, but I'll let Guillermo add more to this answer - Airship uses both Vagrant and CLI tools with Openstack Helm (OSH)[0] - Yes it is, once again it does not provides all the plug ins that Vagrant does, but it works for our main objective. On a side note the weekly meeting is now listed on the Wiki/StarlingX meeting site [1]. And currently working on updating the etherpad [2] which is also live now. [0] https://github.com/openstack/airship-in-a-bottle/blob/master/README.md [1] https://wiki.openstack.org/wiki/Starlingx/Meetings#9:30_am_PDT_.2F_1730_UTC_-_STX_in_a_box_Team_Call [2] https://etherpad.openstack.org/p/stx-inabox On 2/28/19, 12:32 PM, "Jones, Bruce E" wrote: Nice to see this moving forward! I have a few questions. * What makes one of these tools faster than the others? Faster at creating the images? Do the images run faster? * What did the Airship team use to create Airship in a Bottle? * Is GoVM capable of doing what we need it to do? brucej -----Original Message----- From: Martinez Landa, Hayde [mailto:hayde.martinez.landa at intel.com] Sent: Thursday, February 28, 2019 10:00 AM To: starlingx-discuss at lists.starlingx.io Cc: Ponce Castaneda, Guillermo A Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required Hi All, Guillermo and I are currently working on the StarlingX in a box project, we are helding weekly meetings on Thursdays at 9:30 am PDT, We’ll send an update with the Zoom link soon, if anyone is interested in joining the efforts we welcome you. We’ve been doing some research and looking for different options, first of all we were told to consider the python vbox installer As part of this effort [0], but we want to bring to the table another options. 1) Vagrant [1] - This tool has proven itself over time to provide solutions for development environments easily and fast. 2) GoVM [2]- This tool is young in comparison and it's currently under development but so far has proven itself to be faster and more flexible than vagrant. Vagrant: Pros: - Has been around for a long time - It is well documented - A lot of people is used to it - Has a lot of provisioning plug-ins - Flexible and easy. Cons: - It is not as fast as GoVM. - It has a lot of overhead taking in count what we need from it - The ramp up is slower compare to GoVM. GoVM: Pros: - It has a small footprint. - It runs very fast (it is made on Go) - The ramp up is faster. - The main developers sits three desks from us (hehe (:) - It has a "compose" like option Cons: - It is not well known yet - The documentation is still lacking - It does not have that many plug ins - It is still under development (which can also be a pro because it will get better) We also are considering to use Packer[3] to create the main images we are going to work with. Packer is a tool that is well integrated with vagrant since it is also from hashicorp but GoVM can work with those images as well. Right now we are having an issue with creating the base images from starlingx ISO since the installation method is not standard and it requires to create send an user and double password, We are working on solutions for this, will keep you updated. Please share your thoughts and comments, let us know if you need more information or details on these, and also if you now another tool that works well and can help us in this effort. [0] https://review.openstack.org/#/c/637958/ [1] https://www.vagrantup.com/ [2] https://github.com/govm-project/govm [3] https://packer.io/ _______________________________________________ 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 Feb 28 19:11:17 2019 From: Frank.Miller at windriver.com (Miller, Frank) Date: Thu, 28 Feb 2019 19:11:17 +0000 Subject: [Starlingx-discuss] StarlingX cutting over to containers Message-ID: StarlingX Community: I am pleased on behalf of the entire containers subteam to announce that the StarlingX project is ready to use containerized services. The subteam has pulled together a ton of feature devlopment, integration, testing and issue resolution to achieve stability in our four major configurations. Sanities are passing on these configs in both a no proxy/no mirror environment as well as in a proxy/mirror environment. Scott will be merging the f/stein feature branch onto master Friday morning and all builds after that point will only support a containers configuration [1,2]. We would ask that community members hold off merging commits during the day on Friday. There will be some expected limitations at this point in the project as there are a number of planned stories still in progress and a number of medium or lower priority LPs open. However, we are confident that we are ready to get a wider use across the community. For more information on containers including the recipe to bring up containers, current limitations and an FAQ see: https://wiki.openstack.org/wiki/StarlingX/Containers Frank Containers Project Lead [1] The config_controller script will now only support bringing up the platform services in containers [2] the -kubernetes option for config_controller is being removed as the script will only support a containers configuration as of Friday -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruce.e.jones at intel.com Thu Feb 28 19:12:39 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Feb 2019 19:12:39 +0000 Subject: [Starlingx-discuss] Proposal: Deployment Option Names Message-ID: <9A85D2917C58154C960D95352B22818BC3AD8300@fmsmsx121.amr.corp.intel.com> I raised an issue today in the TSC on behalf of the Docs team, to request approval for a proposal for the names of the Deployment options that StarlingX supports. Several different terms are in common use and the hope is to standardize at least our formal documents on one common set of names. We didn't have a quorum in the TSC today and were not able to close this issue. In the interests of moving things forward it was suggested to use the following names for now. I have updated the Doc mega-spec accordingly. If the TSC would like us to use different names, just let me know and I'll change the spec. Proposed Deployment Options: * All-in-one Simplex (changed from the "AIO" used in the spec previously) * All-in-one Duplex (same) * All-in-one Duplex with up to 4 Computes (changed from "AIO-Duplex with Computes") * Standard with Controller Storage (changed from "Small Standard") * Standard with Dedicated Storage (changed from "Standard") * Standard with Ironic * Multi-Region * Distributed Cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Feb 28 19:15:04 2019 From: scott.little at windriver.com (Scott Little) Date: Thu, 28 Feb 2019 14:15:04 -0500 Subject: [Starlingx-discuss] [build-report] STX_build_centos76_pike - Build # 2 - Still Failing! In-Reply-To: <697160145.29.1551374693007.JavaMail.javamailuser@localhost> References: <775262187.34.1550174394958.JavaMail.javamailuser@localhost> <697160145.29.1551374693007.JavaMail.javamailuser@localhost> Message-ID: Prior build failed on tss2 due to stx-tool update 40a9622d7716e60a28807724ce5eece22f0e1c0c Change download mechanism for tss2 Second attempt failed despite having stx-tool update a044f794c4662760f1ca89d0f8d3bec20a49c4e5  Revert 'Change download mechanism for tss2' The issue is that the original build failed to when wget resulted 404, there was no error check, and a broken tarball was produced (tar.gz of nothing) at ... /localdisk/designer/jenkins/f-centos76/stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/downloads/tss2-930.tar.gz ... and subsequent build attempt reported ...    Already have /localdisk/designer/jenkins/f-centos76/stx-tools/centos-mirror-tools/output/stx-r1/CentOS/pike/downloads/tss2-930.tar.gz ... so we fail to download any corrective content. Suggestions... 1) dl_tarball.sh should never produce a tarball after a failed wget, git clone, or whatever. 2) Before declaring 'Already have ' we should test for invalid or 'no content' tarballs. Scott On 2019-02-28 12:24 p.m., build.starlingx at gmail.com wrote: > Project: STX_build_centos76_pike > Build #: 2 > Status: Still Failing > Timestamp: 20190228T151328Z > > Check logs at: > http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T151328Z/logs > -------------------------------------------------------------------------------- > Parameters > > BUILD_CONTAINERS: false > > _______________________________________________ > 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 guillermo.a.ponce.castaneda at intel.com Thu Feb 28 19:17:53 2019 From: guillermo.a.ponce.castaneda at intel.com (Ponce Castaneda, Guillermo A) Date: Thu, 28 Feb 2019 19:17:53 +0000 Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required In-Reply-To: References: <38A5F0A7-4C20-436F-8B5F-D0AD64EB04D5@intel.com> <9A85D2917C58154C960D95352B22818BC3AD8265@fmsmsx121.amr.corp.intel.com> Message-ID: <65E61F38-BBC2-46DC-BB9E-675031454501@intel.com> Hello Bruce, Well, I did not find any other options besides Vegrant and GoVM to provide a Box as final product, so I just compared them to each other, then GoVM is a very small footprint tool, and boots images faster than Vagrant, this could be related with the language the tools are written, vagrant is mostly written in ruby and GoVM is written in Go, I could run a benchmark and share the results if that helps the community to decide. As for the image creation we are intending to use packer, no matter if we use Vagrant or GoVM, so the image creation speed is not something we can compare at this point. Thanks and regards. On 2/28/19, 12:40 PM, "Martinez Landa, Hayde" wrote: Hi Bruce, Answering your questions: - It is faster at both creating the images, running the images and also the ramp up for beginners, but I'll let Guillermo add more to this answer - Airship uses both Vagrant and CLI tools with Openstack Helm (OSH)[0] - Yes it is, once again it does not provides all the plug ins that Vagrant does, but it works for our main objective. On a side note the weekly meeting is now listed on the Wiki/StarlingX meeting site [1]. And currently working on updating the etherpad [2] which is also live now. [0] https://github.com/openstack/airship-in-a-bottle/blob/master/README.md [1] https://wiki.openstack.org/wiki/Starlingx/Meetings#9:30_am_PDT_.2F_1730_UTC_-_STX_in_a_box_Team_Call [2] https://etherpad.openstack.org/p/stx-inabox On 2/28/19, 12:32 PM, "Jones, Bruce E" wrote: Nice to see this moving forward! I have a few questions. * What makes one of these tools faster than the others? Faster at creating the images? Do the images run faster? * What did the Airship team use to create Airship in a Bottle? * Is GoVM capable of doing what we need it to do? brucej -----Original Message----- From: Martinez Landa, Hayde [mailto:hayde.martinez.landa at intel.com] Sent: Thursday, February 28, 2019 10:00 AM To: starlingx-discuss at lists.starlingx.io Cc: Ponce Castaneda, Guillermo A Subject: [Starlingx-discuss] [StarlingX in a box] Community Feedback Required Hi All, Guillermo and I are currently working on the StarlingX in a box project, we are helding weekly meetings on Thursdays at 9:30 am PDT, We’ll send an update with the Zoom link soon, if anyone is interested in joining the efforts we welcome you. We’ve been doing some research and looking for different options, first of all we were told to consider the python vbox installer As part of this effort [0], but we want to bring to the table another options. 1) Vagrant [1] - This tool has proven itself over time to provide solutions for development environments easily and fast. 2) GoVM [2]- This tool is young in comparison and it's currently under development but so far has proven itself to be faster and more flexible than vagrant. Vagrant: Pros: - Has been around for a long time - It is well documented - A lot of people is used to it - Has a lot of provisioning plug-ins - Flexible and easy. Cons: - It is not as fast as GoVM. - It has a lot of overhead taking in count what we need from it - The ramp up is slower compare to GoVM. GoVM: Pros: - It has a small footprint. - It runs very fast (it is made on Go) - The ramp up is faster. - The main developers sits three desks from us (hehe (:) - It has a "compose" like option Cons: - It is not well known yet - The documentation is still lacking - It does not have that many plug ins - It is still under development (which can also be a pro because it will get better) We also are considering to use Packer[3] to create the main images we are going to work with. Packer is a tool that is well integrated with vagrant since it is also from hashicorp but GoVM can work with those images as well. Right now we are having an issue with creating the base images from starlingx ISO since the installation method is not standard and it requires to create send an user and double password, We are working on solutions for this, will keep you updated. Please share your thoughts and comments, let us know if you need more information or details on these, and also if you now another tool that works well and can help us in this effort. [0] https://review.openstack.org/#/c/637958/ [1] https://www.vagrantup.com/ [2] https://github.com/govm-project/govm [3] https://packer.io/ _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss From bruce.e.jones at intel.com Thu Feb 28 19:21:48 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Feb 2019 19:21:48 +0000 Subject: [Starlingx-discuss] StarlingX cutting over to containers In-Reply-To: References: Message-ID: <9A85D2917C58154C960D95352B22818BC3AD8331@fmsmsx121.amr.corp.intel.com> Congratulations Frank and the entire team ! This is a huge accomplishment and both very challenging and very important. Great job everyone! brucej From: Miller, Frank [mailto:Frank.Miller at windriver.com] Sent: Thursday, February 28, 2019 11:11 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] StarlingX cutting over to containers StarlingX Community: I am pleased on behalf of the entire containers subteam to announce that the StarlingX project is ready to use containerized services. The subteam has pulled together a ton of feature devlopment, integration, testing and issue resolution to achieve stability in our four major configurations. Sanities are passing on these configs in both a no proxy/no mirror environment as well as in a proxy/mirror environment. Scott will be merging the f/stein feature branch onto master Friday morning and all builds after that point will only support a containers configuration [1,2]. We would ask that community members hold off merging commits during the day on Friday. There will be some expected limitations at this point in the project as there are a number of planned stories still in progress and a number of medium or lower priority LPs open. However, we are confident that we are ready to get a wider use across the community. For more information on containers including the recipe to bring up containers, current limitations and an FAQ see: https://wiki.openstack.org/wiki/StarlingX/Containers Frank Containers Project Lead [1] The config_controller script will now only support bringing up the platform services in containers [2] the -kubernetes option for config_controller is being removed as the script will only support a containers configuration as of Friday -------------- next part -------------- An HTML attachment was scrubbed... URL: From sgw at linux.intel.com Thu Feb 28 19:51:59 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 28 Feb 2019 11:51:59 -0800 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> Message-ID: <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> On 2/28/19 8:16 AM, Victor Rodriguez wrote: > As discussed in build meeting, the new repo might live in: > > https://github.com/starlingx-staging > > Saul can help with the creation of the repo > Repo created: https://github.com/starlingx-staging/jenkins.git Sau! > regards > > On Thu, Feb 28, 2019 at 8:36 AM Scott Little wrote: >> >> Jenkins under git is basically a snapshot of the jenkins home directory, >> or a subset thereof. I think it really needs to be a git unto itself. >> >> Scott >> >> >> On 2019-02-25 12:52 p.m., Jones, Bruce E wrote: >>> Great idea! Maybe stx-tools? >>> >>> brucej >>> >>> -----Original Message----- >>> From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] >>> Sent: Monday, February 25, 2019 9:50 AM >>> To: scott.little at windriver.com; starlingx-discuss at lists.starlingx.io >>> Subject: Re: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git >>> >>> Hi Scott, >>> >>> I think that is a great idea! >>> >>> I would suggest a new stx-automation or stx-ci repository, also not sure where is the best place, I would suggest github, but for sure Dean will have better insights on this :) >>> >>> -Erich >>> >>> On Fri, 2019-02-22 at 16:50 -0500, Scott Little wrote: >>>> The idea was floated several weeks ago that we should place the >>>> jenkins scripts used by starlingx.cengn.ca builds under git revision >>>> control, and publish them somewhere. >>>> >>>> If we are all agreed this would be a good thing, I would like to move >>>> forward with that proposal. >>>> >>>> Where should we publish it, github or openstack? >>>> >>>> If openstack, I'll need some pointers on how to set up the new git. >>>> >>>> >>>> Thanks >>>> >>>> Scott >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From erich.cm.lists at yandex.com Thu Feb 28 19:54:23 2019 From: erich.cm.lists at yandex.com (Erich Cordoba) Date: Thu, 28 Feb 2019 11:54:23 -0800 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> References: <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> Message-ID: <7280911551383663@iva1-3d0d937e850f.qloud-c.yandex.net> An HTML attachment was scrubbed... URL: From chris at openstack.org Thu Feb 28 20:19:43 2019 From: chris at openstack.org (Chris Hoge) Date: Thu, 28 Feb 2019 12:19:43 -0800 Subject: [Starlingx-discuss] StarlingX cutting over to containers In-Reply-To: <9A85D2917C58154C960D95352B22818BC3AD8331@fmsmsx121.amr.corp.intel.com> References: <9A85D2917C58154C960D95352B22818BC3AD8331@fmsmsx121.amr.corp.intel.com> Message-ID: <77CBC683-F457-4006-B6D8-785D6A1D17FA@openstack.org> As the Loci PTL, I’m happy to work with the StarlingX team in any way I can to help with the adoption of OpenStack Loci images. Congratulations to the team! Chris Hoge Loci PTL > On Feb 28, 2019, at 11:21 AM, Jones, Bruce E wrote: > > Congratulations Frank and the entire team ! This is a huge accomplishment and both very challenging and very important. Great job everyone! > > brucej > > From: Miller, Frank [mailto:Frank.Miller at windriver.com] > Sent: Thursday, February 28, 2019 11:11 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] StarlingX cutting over to containers > > StarlingX Community: > > I am pleased on behalf of the entire containers subteam to announce that the StarlingX project is ready to use containerized services. The subteam has pulled together a ton of feature devlopment, integration, testing and issue resolution to achieve stability in our four major configurations. Sanities are passing on these configs in both a no proxy/no mirror environment as well as in a proxy/mirror environment. Scott will be merging the f/stein feature branch onto master Friday morning and all builds after that point will only support a containers configuration [1,2]. We would ask that community members hold off merging commits during the day on Friday. > > There will be some expected limitations at this point in the project as there are a number of planned stories still in progress and a number of medium or lower priority LPs open. However, we are confident that we are ready to get a wider use across the community. For more information on containers including the recipe to bring up containers, current limitations and an FAQ see:https://wiki.openstack.org/wiki/StarlingX/Containers > > Frank > Containers Project Lead > > [1] The config_controller script will now only support bringing up the platform services in containers > [2] the –kubernetes option for config_controller is being removed as the script will only support a containers configuration as of Friday > _______________________________________________ > 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 Thu Feb 28 21:05:42 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Feb 2019 16:05:42 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_pre_installer - Build # 172 - Still Failing! In-Reply-To: <89012347.24.1551374682201.JavaMail.javamailuser@localhost> References: <89012347.24.1551374682201.JavaMail.javamailuser@localhost> Message-ID: <222766621.32.1551387943631.JavaMail.javamailuser@localhost> Project: STX_build_pre_installer Build #: 172 Status: Still Failing Timestamp: 20190228T192635Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T185920Z/logs -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-centos76/20190228T185920Z DOCKER_BUILD_ID: jenkins-f-centos76-20190228T185920Z-builder MY_REPO: /localdisk/designer/jenkins/f-centos76/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T185920Z/logs PUBLISH_LOGS_BASE: /export/mirror/starlingx/feature/centos76/centos/20190228T185920Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-centos76 From build.starlingx at gmail.com Thu Feb 28 21:05:46 2019 From: build.starlingx at gmail.com (build.starlingx at gmail.com) Date: Thu, 28 Feb 2019 16:05:46 -0500 (EST) Subject: [Starlingx-discuss] [build-report] STX_build_centos76_pike - Build # 3 - Still Failing! In-Reply-To: <1444104316.27.1551374690830.JavaMail.javamailuser@localhost> References: <1444104316.27.1551374690830.JavaMail.javamailuser@localhost> Message-ID: <351543254.35.1551387947918.JavaMail.javamailuser@localhost> Project: STX_build_centos76_pike Build #: 3 Status: Still Failing Timestamp: 20190228T185920Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/feature/centos76/centos/20190228T185920Z/logs -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: false From ildiko.vancsa at gmail.com Thu Feb 28 21:31:53 2019 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 28 Feb 2019 22:31:53 +0100 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> Message-ID: <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> Hi, Thank you for the feedback. Here is an updated diagram incorporating your comments: https://www.dropbox.com/s/0qczsc6pl55j9i4/StarlingX_Diagram_SimplifiedArchitecture.jpg?dl=0 Please let me know your thoughts. Thanks, Ildikó > On 2019. Feb 22., at 21:42, Gowan, Jeff wrote: > > I agree with Bart. > -Jeff > > On 2/22/19, 5:14 AM, "Wensley, Barton" wrote: > > Ildikó, > > I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. > > For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. > > Bart > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: February 22, 2019 4:09 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Feedback needed on updated overview diagram > > Hi StarlingX Community, > > We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 > > We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. > > I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? > > > Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? > > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > 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 dtroyer at gmail.com Thu Feb 28 22:42:56 2019 From: dtroyer at gmail.com (Dean Troyer) Date: Thu, 28 Feb 2019 16:42:56 -0600 Subject: [Starlingx-discuss] [build] publishing CENGN jenkins scripts via git In-Reply-To: <7280911551383663@iva1-3d0d937e850f.qloud-c.yandex.net> References: <93fbd3d2-b121-eb49-4741-d4018f5c2bf4@windriver.com> <4ad0c17e983a034b1351ed0136070a13973fdacc.camel@intel.com> <9A85D2917C58154C960D95352B22818BC3AD4C45@fmsmsx121.amr.corp.intel.com> <81cf14b7-7762-44df-77b6-e59a6a31ff50@linux.intel.com> <7280911551383663@iva1-3d0d937e850f.qloud-c.yandex.net> Message-ID: On Thu, Feb 28, 2019 at 1:54 PM Erich Cordoba wrote: > I would prefer a more generic name in case we switch from Jenkins to another automation system. I asked around the edges of that earlier and it appears to mostly be a snapshot of a jenkins home directory. There is likely not to be a lot of non-Jenkins uses, specific tools that may be more widely useful should probably be pulled out anyway. dt -- Dean Troyer dtroyer at gmail.com From bruce.e.jones at intel.com Thu Feb 28 22:55:17 2019 From: bruce.e.jones at intel.com (Jones, Bruce E) Date: Thu, 28 Feb 2019 22:55:17 +0000 Subject: [Starlingx-discuss] Feedback needed on updated overview diagram In-Reply-To: <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> References: <5CDBBEDBFFF82E4C9E004A2C0F42FE58BAA6763F@ALA-MBD.corp.ad.wrs.com> <53B57CC9-F9C3-4C88-BE19-F48DED4F7281@windriver.com> <14A48C18-A4AD-4452-9B21-9A51541FC711@gmail.com> Message-ID: <9A85D2917C58154C960D95352B22818BC3AD863A@fmsmsx121.amr.corp.intel.com> LGTM, nicely done. -----Original Message----- From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] Sent: Thursday, February 28, 2019 1:32 PM To: Gowan, Jeff ; Wensley, Barton Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Feedback needed on updated overview diagram Hi, Thank you for the feedback. Here is an updated diagram incorporating your comments: https://www.dropbox.com/s/0qczsc6pl55j9i4/StarlingX_Diagram_SimplifiedArchitecture.jpg?dl=0 Please let me know your thoughts. Thanks, Ildikó > On 2019. Feb 22., at 21:42, Gowan, Jeff wrote: > > I agree with Bart. > -Jeff > > On 2/22/19, 5:14 AM, "Wensley, Barton" wrote: > > Ildikó, > > I like version -01 - with the kubernetes component names. Each component is already in the "Kubernetes Components" box so you aren't losing any detail by dropping the "kube-" prefix. > > For the OpenStack components, I'd lean towards using the functional names (Compute, Identity, Block Storage) instead of the code names. Anyone familiar with OpenStack will understand either, but for those less OpenStack knowledge, the functional names will be easier to understand. > > Bart > > -----Original Message----- > From: Ildiko Vancsa [mailto:ildiko.vancsa at gmail.com] > Sent: February 22, 2019 4:09 AM > To: starlingx-discuss at lists.starlingx.io > Subject: [Starlingx-discuss] Feedback needed on updated overview diagram > > Hi StarlingX Community, > > We are working on an updated overview diagram for StarlingX to highlight the work on containerization: https://www.dropbox.com/sh/7fz6ae9moi89e5l/AABBG5PzzJAv7BKKJ1aEdBDja?dl=0 > > We have two versions adding Kubernetes components to the diagram in a dedicated section and update the open source components on the bottom. The difference between the two versions is the way to refer to the Kubernetes items, -01 is using component names and -02 is using the CLI reference where applicable. > > I would prefer version -01 for simplicity as well as making it clear that this is an overview diagram as opposed to a detailed architecture diagram. What do you think? > > > Another angle to think about is readability of the diagram for which it would be good to reduce the number of boxes with text. We could do the same approach with the OpenStack components as I described above and switch to ‘Compute’, ‘Identity’, ‘Block Storage’, etc and drop a few of the currently listed components and indicate it is not a comprehensive list. What would be your preference? > > > Thanks and Best Regards, > Ildikó > > > > _______________________________________________ > 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 jwoh95 at dcn.ssu.ac.kr Thu Feb 28 01:29:59 2019 From: jwoh95 at dcn.ssu.ac.kr (Jaewook Oh) Date: Thu, 28 Feb 2019 10:29:59 +0900 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Austin, I thought I had already replied to the mail on 22, but it seems there were some mistakes. Here are the information. 1. - Here is the spec Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz RAM : 32GB (Is this the problem? I already saw for the controller 64GB RAM is needed, but I'm not sure, cause the installation was just stuck literally, SSD : 500GB SuperMicro - Bios Setting: I enabled and disabled as the instruction said. And at first try, I didn't used UEFI, after failure, I changed it into UEFI, but the result was same. I enabled VTx/Iommu enable or not ? 2. I used bare metal one.. however when I pressed the buttons, nothing happened. And the controller-1 is just stopped as I said before. Thank you for helping me :) Best Regards, Jaewook. 2019년 2월 28일 (목) 오전 10:12, Sun, Austin 님이 작성: > Hi Jaewook: > > > > 1. could you share the hw info for controller-1 ? and check bios > setting ? is it using UEFI ? VTx/Iommu enable or not ? > > 2. Could you try access controller-1 and press Alt+F10 to see any log > if the system is bare metal ? > > > > > > Thanks. > > BR > Austin Sun. > > > > *From:* Jaewook Oh [mailto:kyle.oh95 at gmail.com] > *Sent:* Friday, February 22, 2019 2:54 PM > *To:* starlingx-discuss > *Subject:* [Starlingx-discuss] Duplex PXE Booting seems failed > > > > Hello StarlingX Team, > > > > I finally solved the horizon error, the port number was different. > > I don't know why the port was changed, but anyway the port number was > 8080, not 80. > > > > But I'm now facing new obstacles, Duplex PXE Booting. > > > > I succeed to connect PXE mode, but no more process.. > > > > In Controller-0, I can find below result, > > > > [image: image.png] > > > > And another node that should've been controller-1, shows below letters on > the display. > > > > 1) All-in-one > > > > Loading rel-19.01/installer-bzImage......... > > Loading > rel-19.01/installer-initrd............................................................................ready. > > > > > > I waited this task for a day, but no changes. > > > > Any help would be very appreciated. > > > > Best Regards, > > Jaewook. > > > > ================================================ > *Jaewook Oh* (오재욱) > IISTRC - Internet Infra System Technology Research Center > 369 Sangdo-ro, Dongjak-gu, > 06978, Seoul, Republic of Korea > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > -- ================================================ *Jaewook Oh* (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea Tel : +82-2-820-0841 | Mobile : +82-10-9924-2618 E-mail : jwoh95 at dcn.ssu.ac.kr ================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 47105 bytes Desc: not available URL: From zhiwei.he at intel.com Thu Feb 28 03:05:24 2019 From: zhiwei.he at intel.com (He, Zhiwei) Date: Thu, 28 Feb 2019 03:05:24 +0000 Subject: [Starlingx-discuss] the version of 20190111T060000Z not found in official web Message-ID: <09777F12A863964D9F4AE780D4FEA3E83E65C51D@SHSMSX104.ccr.corp.intel.com> Hi expert, I want to download a starlingx image with version of "20190111T060000Z", because this version has pass sanity test. Like the below link, "http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190111T060000Z/outputs/iso/" but it seem the version" 20190111T060000Z" just keep 1 month on the official web, question 1 : how to download historic version ? question 2: which stable version can be recommend to customer? Or the stable version can be keep in official web? Thanks! zhiwei -------------- next part -------------- An HTML attachment was scrubbed... URL: From austin.sun at intel.com Thu Feb 28 06:28:16 2019 From: austin.sun at intel.com (Sun, Austin) Date: Thu, 28 Feb 2019 06:28:16 +0000 Subject: [Starlingx-discuss] Duplex PXE Booting seems failed In-Reply-To: References: Message-ID: Hi Jaewook: Are you using iso built by yourself ? or taking iso directly from cengn? From: Jaewook Oh [mailto:jwoh95 at dcn.ssu.ac.kr] Sent: Thursday, February 28, 2019 9:30 AM To: Sun, Austin Cc: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Duplex PXE Booting seems failed Hi Austin, I thought I had already replied to the mail on 22, but it seems there were some mistakes. Here are the information. 1. - Here is the spec Intel(R) Xeon(R) CPU D-1557 @ 1.50GHz RAM : 32GB (Is this the problem? I already saw for the controller 64GB RAM is needed, but I'm not sure, cause the installation was just stuck literally, SSD : 500GB SuperMicro - Bios Setting: I enabled and disabled as the instruction said. And at first try, I didn't used UEFI, after failure, I changed it into UEFI, but the result was same. I enabled VTx/Iommu enable or not ? 2. I used bare metal one.. however when I pressed the buttons, nothing happened. And the controller-1 is just stopped as I said before. Thank you for helping me :) Best Regards, Jaewook. 2019년 2월 28일 (목) 오전 10:12, Sun, Austin >님이 작성: Hi Jaewook: 1. could you share the hw info for controller-1 ? and check bios setting ? is it using UEFI ? VTx/Iommu enable or not ? 2. Could you try access controller-1 and press Alt+F10 to see any log if the system is bare metal ? Thanks. BR Austin Sun. From: Jaewook Oh [mailto:kyle.oh95 at gmail.com] Sent: Friday, February 22, 2019 2:54 PM To: starlingx-discuss > Subject: [Starlingx-discuss] Duplex PXE Booting seems failed Hello StarlingX Team, I finally solved the horizon error, the port number was different. I don't know why the port was changed, but anyway the port number was 8080, not 80. But I'm now facing new obstacles, Duplex PXE Booting. I succeed to connect PXE mode, but no more process.. In Controller-0, I can find below result, [image.png] And another node that should've been controller-1, shows below letters on the display. 1) All-in-one Loading rel-19.01/installer-bzImage......... Loading rel-19.01/installer-initrd............................................................................ready. I waited this task for a day, but no changes. Any help would be very appreciated. Best Regards, Jaewook. ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss -- ================================================ Jaewook Oh (오재욱) IISTRC - Internet Infra System Technology Research Center 369 Sangdo-ro, Dongjak-gu, 06978, Seoul, Republic of Korea Tel : +82-2-820-0841 | Mobile : +82-10-9924-2618 E-mail : jwoh95 at dcn.ssu.ac.kr ================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 47105 bytes Desc: image001.png URL: From aspiers at suse.com Thu Feb 28 15:51:29 2019 From: aspiers at suse.com (Adam Spiers) Date: Thu, 28 Feb 2019 15:51:29 +0000 Subject: [Starlingx-discuss] [all] [forum] Forum Submissions are open! In-Reply-To: <20190228001024.GD13081@thor.bakeyournoodle.com> References: <5C76E02F.4010906@openstack.org> <20190227220801.GA12980@sm-workstation> <5C770FA4.6010409@openstack.org> <20190228001024.GD13081@thor.bakeyournoodle.com> Message-ID: <20190228155129.3mvmms4c6jsrjdcv@pacific.linksys.moosehall> Tony Breeds wrote: >On Wed, Feb 27, 2019 at 06:51:49PM -0500, Erik McCormick wrote: >> I would also be curious to hear from anyone who is basing their travel >> choices on the approval status of a Forum session. I believe that this >> number is 0, but I'm ready to be proven wrong. > >There are companies that only fund 'speakers' for travel and there are >some developer types (like myself) that will be moderating forum >sessions (hopefully) but not talking at the summit. > >So there certainly *are* people in this situation. I can confirm that. I almost missed attending Berlin because I did not have a speaking session approved, despite having two self-healing SIG sessions to moderate. This nearly happened again with Denver 2019 in fact. I suspect the problem here is not companies valuing developer sessions less than presentations (certainly not in the case of my employer anyway!), but rather that the Forum and PTG sessions / schedules are determined much later than that of the main summit, by which time many companies need to have already approved and booked travel in order to avoid expensive flights / hotels. Therefore I would request that if possible the idea is considered to bring this planning forward so that it happens roughly at the same time as the Summit. I do appreciate that might cause unmanageably high workloads for certain Foundation staff, but if so maybe there is a middle ground which could work? Cheers, Adam