September 2019 - Starlingx-discuss

[Starlingx-discuss] REMINDER about updating STX REST API DOCUMENTATION
by Waines, Greg 06 Mar '20

06 Mar '20

ALL StarlingX-Contributors, This email is probably about 5 months too late ... apologies. ATTENTION back in ~ September 2018, the StarlingX Documentation Team converted all of our StarlingX REST API Documents from those ugly wadl and yaml files into .rst / restructuredText files; basically aligning with the way all the other services in OpenStack are documenting REST APIs. The new API DOCS (.rst files) are now located under the applicable repos (or sub-repos). It is the responsibility of the contributor who changes / updates / creates STX REST APIs to also update the STX REST API DOCUMENTATION. ( ... again, apologies for telling you this 5 months late ... ) The HOWTO info on updating the new REST API DOCS can be found here: https://docs.starlingx.io/contributor/api_contribute_guide.html Greg. p.s. If you do know that you've changed an STX API in the last 5 months and know that you have NOT done the corresponding STX API DOC change, then minimally you need to raise a StarlingX Launchpad Bug on the issue with the details of the missing changes.

1 1

Re: [Starlingx-discuss] FW: [Build] Build layering reviews
by Scott Little 22 Oct '19

22 Oct '19

Returning this discussion to the mailing list. If possible, join the Build call next week. https://wiki.openstack.org/wiki/Starlingx/Meetings 1) When mock installs for the first time. it uses rpms that have been download via lst file. The mock pseudo-layer lst files capture reflect the rpms needed by mock. The mock lst's are merged with the layers lst's. In this way, the mock rpms don't have to be listed in each and every layer's lst. 2) Adding tools to generate an lst file reflacting the output of a build layer, and adding that lst for consumprion by higher layers, is indeed a possibility possibility I wanted to persue. Reference to that output lst could then be added to as a new arg to the download script when invoked by a higher layer, or a config file could specify where to find it (cengn is the likely default supplier). compile layer) The compile layer is a true layer, built prior to the distro layer. Only a few build related packages go here. Compilers, language interpreters, rpm. I wanted those packages in place so that all distro layer packages build with the same tools. Scott On 2019-09-25 10:24 p.m., Chen, Haochuan Z wrote: > > Still not clear about mock layer. > > 1, In build container, mock is already installed, why request to > download mock required package firstly? > > 2, To build distro or flock layer, we could add compile layer’s tis > rpm in distro and flock layer’s lst file. By download compile layer’s > binary in mirror, it could also ensure user building package with same > tool. > > Why introduces compile layer? > > Thanks! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > *From:*Scott Little <scott.little(a)windriver.com> > *Sent:* Thursday, September 26, 2019 12:25 AM > *To:* Chen, Haochuan Z <haochuan.z.chen(a)intel.com> > *Subject:* Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > See inline ... > > Scott > > On 2019-09-23 11:00 a.m., Chen, Haochuan Z wrote: > > Hi Scott > > I studied your patch and some questions. > > 1, why there is mock and compile layer, what's usage or intention > for these two layers? > > Build-pkgs uses a tool called mock to create a reproducible > compilation sandbox. It is chroot like environmnet into which rpms > are installed to construct a minimal build environment. > > The mock layer is not built. I created it as a placeholder for the > lst files that downloads all the rpms that mock requires. Prior to > building a layer, the lst files for both the layer being build, and > the mock pseudo layer, need to be processed. Without the mock pseudo > layer, we would have to replicate that list of mock required rpms in > each and ever layer's lst files. > > The concept ran into a bit of trouble because some of the rpms needed > by mock are themselves built by the compile or distro layers (with a > newer revision). So the > mock pseudo layer might actually omit those rpms from it's lst file, > and they needed to be listed in the layer lst files instead. > > The compile layer is a true layer, built prior to the distro layer. > Only a few build related packages go here. Compilers, language > interpreters, rpm. I wanted those packages in place so that all > distro layer packages build with the same tools. > > > > 2, for download_mirror.sh, it generate rpm list by merge file in > config/centos/<layer>/<rpm list file name> and rpm list file in > stx/<project name> > > But for generate-cgcs-centos-repo.sh, it use rpm list file in > centos-mirror-tools folder. Rpm package should be added in two rpm > list file. > > It is not good for maintenance. What about remove rpm list file > in centos-mirror-tools folder > > /rpms_centos.lst/rpms_centos3rdparties.lst/rpms_3rdparties.lst/other_downloads.lst/ > tarball-dl.lst/ > > That was considered and debated. The concern was that the many git > repos that make up the layer would list different versions of the same > package. Then what do we do? Throw an error? Silently use the > newest package? So we elected to keep binary rpms needed to satisfy > dependencies listed in a central place. > > At some point we may want to explore allowing lst files specify > required package but not version (beyond a possible minimum version) > when on the master branch, and have a way to 'lock down' the versions > only for a release branch. > > 3, Question about setup yum repo for rpm tailing with “tis” such > as xxx.*tis*.x86_64.rpm or xxx.*tis*.noarch.rpm > > In this patch https://review.opendev.org/#/c/681821/1 > > /There is such line in > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo/ > > /[Starlingx-cengn_distro_layer]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//std/rpmbuild/RPMS// > > /enabled=1/ > > /[Starlingx-cengn_distro_layer-rt]/ > > /name=Starlingx-cengn_distro_layer/ > > /baseurl=http://127.0.0.1:8088/localdisk/loadbuild//*/slittle1/restructure3b/*//rt/rpmbuild/RPMS// > > /enabled=1/ > > also in > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > My understanding is rpm tailing with “tis” should also upload to > cengn, rpm name listed in > centos-mirror-tools/config/centos/flock/rpms_centos3rdparties.lst > > So these three files should be unnecessary, with cengn update for > layered build. > > config/centos/flock/yum.repos.d/StarlingX_cengn_distro_layer.repo > > config/centos/flock/yum.repos.d/StarlingX_cengn_compile_layer.repo > > config/centos/distro/yum.repos.d/StarlingX_cengn_compile_layer.repo > > For development testing, I had to hack together a simulated cengn by > running lighttpd on 127.0.0.1:8088 and allowing it to serve up files > from builds of lower layers > > restructure3a == layer-comiler layer build > > restructure3b == layer-distro layer build > > restructure3c == layer-flock layer build (although there shouldn't be > a repo entry referring to that one) > > Finalizing the repo entries would have to wait until cengn was up an > running. > > 4, In generate-cgcs-centos-repo.sh there is --layer-dir, and such > content in your patch commit message > > /generate-cgcs-centos-repo.sh \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-compile/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/std/rpmbuild/RPMS/ > \/ > > /--layer-dir=/localdisk/loadbuild/slittle1/layer-distro/rt/rpmbuild/RPMS/ > \/ > > //import/mirrors/starlingx/ > > For all rpm download from cengn, --layer-dir is unnecessary to > generate link, correct? > > This is another way to do cross layer development testing without > support from cengn. Again the goal is to allow an upper layer build > to download rpms from a lower layer build on the same machine. > > 5, could you share > build-tools/build-iso/centos_required_build_layer.cfg, share to me > > Did that not get published in my reviews? Content is very simple. > > compile,file:///localdisk/loadbuild/slittle1/restructure3a/centos_compile_iso_image.inc > distro,file:///localdisk/loadbuild/slittle1/restructure3b/centos_distro_iso_image.inc > flock,file:///localdisk/loadbuild/slittle1/restructure3c/centos_flock_iso_image.inc > > 6, For distro/compiler/flock, all are separate layer? > > Yes > > My current step > > /repo init -u https://opendev.org/starlingx/manifest.git > <https://opendev.org/starlingx/manifest.git>/ > > /apply this patch to .repo/manifests/ > > /https://review.opendev.org/#/c/681914/1/ > > /repo init -m compile.xml/ > > /repo sync/ > > /apply these to patch/ > > /https://review.opendev.org/#/c/681821/1/ > > /https://review.opendev.org/#/c/681828/1/ > > /./download_mirror.sh -n -g -l flock -c > config/centos/compiler/yum.conf.sample -S / > > /./toCopy/generate-cgts-centos-repo output/stx-r1/CentOS/pike// > > /build-pkgs/ > > /build-iso/ > > BR! > > Martin, Chen > > SSP, Software Engineer > > 021-61164330 > > -----Original Message----- > From: Scott Little <scott.little(a)windriver.com> > <mailto:scott.little@windriver.com> > Sent: Thursday, September 19, 2019 9:54 PM > To: Chen, Haochuan Z <haochuan.z.chen(a)intel.com> > <mailto:haochuan.z.chen@intel.com> > Subject: Re: FW: [Starlingx-discuss] [Build] Build layering reviews > > Most of the required changes were already merged. > > I'll scan the spec when time permits to see if I missed anything. > > Scott > > On 2019-09-16 12:01 p.m., Chen, Haochuan Z wrote: > > > Hi Scott > > > > > > I read your patch for build layering, but could not find patch > for build script. > > > > > > Description in spec https://review.opendev.org/#/c/672288/12/ > <https://review.opendev.org/#/c/672288/12/> > > > Modifications to package build scripts ... build-pkgs, > > > build-srpms-parallel, build-srpms-serial, build-rpms-parallel, > build-rpms-serial (cgcs-root): > > > > > > Thanks > > > > > > Martin, Chen > > > SSP, Software Engineer > > > 021-61164330 > > > > > > -----Original Message----- > > > From: Xie, Cindy > > > Sent: Friday, September 13, 2019 12:24 PM > > > To: Chen, Haochuan Z <haochuan.z.chen(a)intel.com > <mailto:haochuan.z.chen@intel.com>> > > > Cc: Hu, Yong <yong.hu(a)intel.com <mailto:yong.hu@intel.com>> > > > Subject: FW: [Starlingx-discuss] [Build] Build layering reviews > > > > > > Martin, > > > I am wondering if you will be interested to working on this > task. To me, having layering build and provide efficiency to > developers are very important for StarlingX. It also provide a > chance that you and work together w/ WR folks being more close > collaboration. Let me know your interested level. > > > > > > Thx. -cindy > > > > > > -----Original Message----- > > > From: Scott Little <scott.little(a)windriver.com > <mailto:scott.little@windriver.com>> > > > Sent: Friday, September 13, 2019 4:55 AM > > > To: starlingx-discuss(a)lists.starlingx.io > <mailto:starlingx-discuss@lists.starlingx.io> > > > Subject: [Starlingx-discuss] [Build] Build layering reviews > > > > > > My prototype code for the layered build has been posted to gerrit. > > > (listed below) > > > > > > I was briefly able to build all layers, and produce an iso with > the same package content as the cengn build. Then I was diverted > by non-trivial changes to the restructuring work. What I have > posted is now several weeks out of date and will almost certainly > will not work. The devil is in keeping the lst files in sync with > the ever changing master branch. > > > > > > Other commitments will prevent me from resuming this work until > November. If anyone wants to whip the lst files into shape and > try to get the build working again, be my guest. > > > > > > Final delivery will require changes to the CENGN build scripts > (Don or Myself), and a freeze on packaging changes will likely be > required for aprox 3 days to finalize the lst files. > > > > > > Scott > > > > > > ---------------- <Snip> ---------------- > > > > > > https://review.opendev.org/#/c/681821/1 > > > > > > https://review.opendev.org/#/c/681914/1 > > > > > > https://review.opendev.org/#/c/681823/1 > > > > > > https://review.opendev.org/#/c/681824/1 > > > > > > https://review.opendev.org/#/c/681828/1 > > > > > > https://review.opendev.org/#/c/681832/2 > > > > > > https://review.opendev.org/#/c/681834/1 > > > > > > https://review.opendev.org/#/c/681836/1 > > > > > > https://review.opendev.org/#/c/681835/1 > > > > > > https://review.opendev.org/#/c/681842/1 > > > > > > https://review.opendev.org/#/c/681847/1 > > > > > > https://review.opendev.org/#/c/681848/1 > > > > > > https://review.opendev.org/#/c/681851/1 > > > > > > https://review.opendev.org/#/c/681852/1 > > > > > > https://review.opendev.org/#/c/681854/1 > > > > > > https://review.opendev.org/#/c/681856/1 > > > > > > https://review.opendev.org/#/c/681890/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681892/1 > > > > > > https://review.opendev.org/#/c/681898/1 > > > > > > https://review.opendev.org/#/c/681900/1 > > > > > > https://review.opendev.org/#/c/681901/1 > > > > > > https://review.opendev.org/#/c/681902/1 > > > > > > > > > > > > > > > _______________________________________________ > > > Starlingx-discuss mailing list > > > Starlingx-discuss(a)lists.starlingx.io > <mailto:Starlingx-discuss@lists.starlingx.io> > > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss >

7 14

[Starlingx-discuss] Please help to review STX Wiki for Time Sensitive Networking
by Le, Huifeng 14 Oct '19

14 Oct '19

Brent, Matt, Ruijing, As following up on story: [Feature] Time Sensitive Networking (https://storyboard.openstack.org/#!/story/2005516) and approved spec https://review.opendev.org/#/c/666768/, we had done the POC to deploy and run TSN application on STX environment, the detail process and learning are summarized at Wiki: https://wiki.openstack.org/wiki/StarlingX/Networking/TSN which can be served as deliverable of task "StarlingX user guide on how to deploy TSN in VM". Could you please help to review the Wiki and let me know if you have any comments. Thanks much! Best Regards, Le, Huifeng

3 6

[Starlingx-discuss] [DOCS] New location of Ansible bootstrap playbook (bootstrap.yml)
by Zhou, Wei 10 Oct '19

10 Oct '19

Hi, My following commit is merged today. It restructures StarlingX ansible-playbooks repo. https://opendev.org/starlingx/ansible-playbooks/commit/6e6e564a4f5a92020f82… As a result, the deployment/installation guild (e.g. for AIO-SX https://docs.starlingx.io/deploy_install_guides/current/bare_metal_aio_simp…) needs to be updated to address the new location of bootstrap playbook. The path for the bootstrap playbook (bootstrap.yml) is changed from /usr/share/ansible/stx-ansible/playbooks/bootstrap/bootstrap.yml to /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml. Thanks, -Wei

3 5

[Starlingx-discuss] move storage node in replication group
by von Hoesslin, Volker 10 Oct '19

10 Oct '19

hello, i have 3 storage nodes and after provisioning nodes 1+2 are in replication group 0 and node 3 are in replication group 1?! how can i move node 3 to group 0? greetings, volker

2 4

[Starlingx-discuss] [multi-os] What is the correct workflow to submit requests in OBS
by Cordoba Malibran, Erich 09 Oct '19

09 Oct '19

Hi, I'm trying to send a request to the fm-common project in OBS, however apparently the workflow I follow is incorrect and creates unexpected results What I do is: - From the project's web page[0] I click on "Branch package", this creates a branched package in my account[1] - Checkout the project, I do this with: `osc co home:erichcm:branches:Cloud:StarlingX:1.0/fm-common` - For this task I'm editing the _service file and testing locally with `osc service run` and `osc build --local-package --no-verify openSUSE_Leap_15.1` - I delete all the non-needed files and keep only the _service file. Then I do a `osc ar` to make this changes - I commit the changes with `osc commit`. At this point, I see in the web page of my branched project that a set of files were created. - I click on "Submit package". The created request[2] not only contains the diff of the _service, it contains the diff of all files created after I did a `osc commit`. What should be the correct workflow for submit request in OBS? Thanks -Erich - [0] https://build.opensuse.org/package/show/Cloud:StarlingX:2.0/fm-common - [1] https://build.opensuse.org/package/show/home:erichcm:branches:Cloud:Starlin… - [2] https://build.opensuse.org/request/show/734131

3 3

[Starlingx-discuss] openSUSE: High Availability Installation Update
by Arce Moreno, Abraham 08 Oct '19

08 Oct '19

Hi, Please find a preliminary update [0] of our journey to install the created "high availability" packages from our openSUSE StarlingX project space [1]. These procedure will be repeated once the packages are generated using the non-yet merged StarlingX HA Upstream Specfiles [2]. In summary: The following packages were successfully installed, no missing zypper or python dependencies: - sm-common - libsm-db1 - sm The following packages were successfully installed after additional zypper and/or python packages were installed, work in progress to add them into their respective specfile: - sm-tools - sm-client - sm-api You will find in the guide: 1. The openSUSE based Vagrant image 2. The installation of the packages and package binaries execution 3. Output for both installation and package binaries execution [0] https://github.com/xe1gyq/starlingx/blob/master/multios/opensuse_ha_install… [1] https://build.opensuse.org/project/show/Cloud:StarlingX:2.0 [2] https://review.opendev.org/#/c/679686/

2 4

Re: [Starlingx-discuss] Weekly StarlingX non-OpenStack distro meeting
by Xie, Cindy 02 Oct '19

02 Oct '19

All, This meeting is on tomorrow, but Yong HU will chair the meeting as I have a conflict at the same slot. Yong will publish the agenda soon. Thanks. - cindy -----Original Appointment----- From: Xie, Cindy Sent: Thursday, April 25, 2019 5:42 PM To: Xie, Cindy; 'zhaos'; Wold, Saul; 'starlingx-discuss(a)lists.starlingx.io'; 'Rowsell, Brent' Cc: Armstrong, Robert H; 'Komiyama, Takeo'; 'Eslimi, Dariush'; 'Seiler, Glenn'; 'Peng Tan'; 'Chen, Jacky'; Gomez, Juan P; 'Waines, Greg'; 'Zhi Zhi2 Chang'; 'Badea, Daniel'; Jones, Bruce E; Chen, Tingjie; 'Carlos Cebrian'; Cobbley, David A; Hu, Wei W Subject: Weekly StarlingX non-OpenStack distro meeting When: Wednesday, September 25, 2019 9:00 PM-10:00 PM (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi. Where: https://zoom.us/j/342730236 * Cadence and time slot: o Wednesday 9AM Winter EDT (10PM China time, US PDT Winter time 6AM) * Call Details: o Zoom link: https://zoom.us/j/342730236 o Dialing in from phone: o Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 876 9923 o Meeting ID: 342 730 236 o International numbers available: https://zoom.us/u/ed95sU7aQ * Meeting Agenda and Minutes: o https://etherpad.openstack.org/p/stx-distro-other

3 4

[Starlingx-discuss] Cannot allocate a VM - STX2.0-AIO-SX - Error 500
by Mariano Ucha 01 Oct '19

01 Oct '19

Hi all! I'm having a trouble now trying to allocate a VM con Openstack. I'm using STX 2.0 AIO-SX with DPDK so when i'm trying to allocate a VM with a flavor that have hw:mem_page_size=large metadata the system gives me *error 500 **No valid host was found. There are not enough hosts available.* File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 1346, in schedule_and_build_instances instance_uuids, return_alternates=True) File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 800, in _schedule_instances return_alternates=return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations instance_uuids, return_objects, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations return cctxt.call(ctxt, 'select_destinations', **msg_args) File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 178, in call retry=self.retry) File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/transport.py", line 128, in _send retry=retry) File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send call_monitor_timeout, retry=retry) File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send raise result *Logs from Nova Scheduler* 2019-09-23 17:37:56.537 1 INFO nova.filters [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Filter NUMATopologyFilter returned 0 hosts 2019-09-23 17:37:56.537 1 INFO nova.filters [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Filter NUMATopologyFilter returned 0 hosts 2019-09-23 17:37:56.538 1 INFO nova.filters [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Filtering removed all hosts for the request with instance ID '66175096-37a4-4a2c-b23a-e7a4a6f10ca1'. Filter results: ['RetryFilter: (start: 1, end: 1)', 'ComputeFilter: (start: 1, end: 1)', 'AvailabilityZoneFilter: (start: 1, end: 1)', 'AggregateInstanceExtraSpecsFilter: (start: 1, end: 1)', 'ComputeCapabilitiesFilter: (start: 1, end: 1)', 'ImagePropertiesFilter: (start: 1, end: 1)', 'NUMATopologyFilter: (start: 1, end: 0)'] 2019-09-23 17:37:56.538 1 INFO nova.filters [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Filtering removed all hosts for the request with instance ID '66175096-37a4-4a2c-b23a-e7a4a6f10ca1'. Filter results: ['RetryFilter: (start: 1, end: 1)', 'ComputeFilter: (start: 1, end: 1)', 'AvailabilityZoneFilter: (start: 1, end: 1)', 'AggregateInstanceExtraSpecsFilter: (start: 1, end: 1)', 'ComputeCapabilitiesFilter: (start: 1, end: 1)', 'ImagePropertiesFilter: (start: 1, end: 1)', 'NUMATopologyFilter: (start: 1, end: 0)'] *Logs from Nova Conductor* 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager Traceback (most recent call last): 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 1346, in schedule_and_build_instances 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager instance_uuids, return_alternates=True) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 800, in _schedule_instances 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return_alternates=return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager instance_uuids, return_objects, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return cctxt.call(ctxt, 'select_destinations', **msg_args) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 178, in call 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager retry=self.retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/transport.py", line 128, in _send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager retry=retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager call_monitor_timeout, retry=retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager raise result 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager NoValidHost_Remote: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager Traceback (most recent call last): 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return func(*args, **kwargs) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/manager.py", line 168, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager allocation_request_version, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager allocation_request_version, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager claimed_instance_uuids) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager raise exception.NoValidHost(reason=reason) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager NoValidHost: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Failed to schedule instances: NoValidHost_Remote: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner return func(*args, **kwargs) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/manager.py", line 168, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule claimed_instance_uuids) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager Traceback (most recent call last): 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 1346, in schedule_and_build_instances 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager instance_uuids, return_alternates=True) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/conductor/manager.py", line 800, in _schedule_instances 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return_alternates=return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager instance_uuids, return_objects, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return cctxt.call(ctxt, 'select_destinations', **msg_args) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 178, in call 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager retry=self.retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/transport.py", line 128, in _send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager retry=retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager call_monitor_timeout, retry=retry) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager raise result 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager NoValidHost_Remote: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager Traceback (most recent call last): 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager return func(*args, **kwargs) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/manager.py", line 168, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager allocation_request_version, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager allocation_request_version, return_alternates) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager claimed_instance_uuids) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager raise exception.NoValidHost(reason=reason) 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager NoValidHost: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.542 1 ERROR nova.conductor.manager 2019-09-23 17:37:56.627 1 WARNING nova.scheduler.utils [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner return func(*args, **kwargs) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/manager.py", line 168, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule claimed_instance_uuids) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. : NoValidHost_Remote: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.627 1 WARNING nova.scheduler.utils [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] Failed to compute_task_build_instances: No valid host was found. There are not enough hosts available. Traceback (most recent call last): File "/var/lib/openstack/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 229, in inner return func(*args, **kwargs) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/manager.py", line 168, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 96, in select_destinations allocation_request_version, return_alternates) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 265, in _schedule claimed_instance_uuids) File "/var/lib/openstack/lib/python2.7/site-packages/nova/scheduler/filter_scheduler.py", line 302, in _ensure_sufficient_hosts raise exception.NoValidHost(reason=reason) NoValidHost: No valid host was found. There are not enough hosts available. : NoValidHost_Remote: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.630 1 WARNING nova.scheduler.utils [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] [instance: 66175096-37a4-4a2c-b23a-e7a4a6f10ca1] Setting instance to ERROR state.: NoValidHost_Remote: No valid host was found. There are not enough hosts available. 2019-09-23 17:37:56.630 1 WARNING nova.scheduler.utils [req-f57095ac-6539-4efb-a6a5-f27aebb0a27c edbcf8808d8a4f48a39b8eebb3951292 8ae61d9905d94b8aa66193b20a3ab973 - default default] [instance: 66175096-37a4-4a2c-b23a-e7a4a6f10ca1] Setting instance to ERROR state. How can i change Nova log mode to DEBUG? Anything more i can check? Regards, Mariano

3 5

[Starlingx-discuss] [fault][gui][ha][metal][nfv][update] Project operations - RESPONSE NEEDED
by Ildiko Vancsa 01 Oct '19

01 Oct '19

Hi, I’m reaching out about an open review that proposes to merge six of the StarlingX projects into one: https://review.opendev.org/#/c/683410/ As this proposal affects 1/3 of the project teams I would like to have a community discussion about this rearrangement. I have a few questions to discuss: * Are all of these projects still active? * From functionality perspective the project teams cover very different areas. What are the motivating factors behind the proposed change? * Does this proposal help with organizing work and onboarding new contributors? I would like to have feedback from the project team members and community members on the above questions as well as in general in response to the proposed change. Please respond to this thread and share your views. I also checked some details and based on the StarlingX wiki the projects listed in the subject have no meetings and their wiki pages are also very brief in providing information about what they do and how to participate. I think this is something to look into in general and it should be the responsibility of all project teams and contributors. I propose to have a liaison from every team to look into addressing this topic to make sure this is an ongoing activity along with the technical development work. What do you think about this idea? Thanks and Best Regards, Ildikó

5 5