Earlier  
Posted Nick Remark
#openstack-nova - 2017-03-16
21:37:38 mriedem dansmith: ok
21:37:41 mriedem high five
21:37:47 mriedem \o\
21:37:49 mriedem /o/
21:37:51 dansmith o/*
21:37:55 mriedem o/.
21:38:08 melwitt .\o
21:38:10 mriedem i'm just going to steal the classics from melwitt
21:38:13 jroll o/'
21:38:17 dtp armpit bump?
21:38:18 jroll cheeeeeers
21:38:20 dansmith ~~.\o/.~~
21:38:24 melwitt lol
21:38:25 mriedem odor lines?
21:38:30 dansmith smell lines yeah
21:38:32 mriedem ha
21:38:50 dansmith I am in portland after all, where showers are optional
21:39:56 dtp ok mriedem, reading now
21:46:51 dtp what does the services table contain?
21:47:27 mriedem services
21:47:34 dtp hehe
21:47:45 dtp like . . . keystone?
21:47:50 mriedem no
21:47:54 mriedem info about the actual nova services
21:47:59 mriedem like nova-compute, nova-scheduler, etc
21:48:03 mriedem the host/binary/topic fields
21:48:05 mriedem service versoin
21:48:06 mriedem enabled/disabled
21:48:07 mriedem et
21:48:08 mriedem *etc
21:48:16 mriedem https://developer.openstack.org/api-ref/compute/#compute-services-os-services
21:48:20 dtp ah. thank you
21:48:30 mriedem heh "Lists all running Compute services for a tenant," that's wrong
21:48:34 mriedem services are not per-tenant
21:48:40 mriedem sdague: more api-ref fun ^
21:49:04 mriedem that should be "for a region" right?
21:49:11 mriedem or a cell i guess
21:49:28 mriedem but i'm not sure we want to start using the c word in the api ref yet
21:49:29 dansmith not a cell
21:49:34 dansmith yeah, don't say that
21:49:35 mriedem true,
21:49:39 mriedem api isn't in the cell
21:49:42 dansmith say for a deployment or region or something
21:49:45 mriedem yeah
21:50:39 melwitt dtp: to see how it's used, look at nova/db/sqlalchemy/models.py at Service to see the data model, then look at nova/objects/service.py to see the object API and you can sort of trace how it's used from using that as a starting point. also look at nova/service.py
21:51:40 dtp ok, thanks
21:51:52 mriedem dansmith: guh, we need to update this at some point too https://docs.openstack.org/ops-guide/arch-scaling.html#cells-and-regions
21:52:45 dansmith hmm, yeah
21:58:41 openstack Launchpad bug 1673616 in openstack-manuals "Scaling in Operations Guide - cells section needs to be updated" [Undecided,New]
21:58:41 mriedem dansmith: i've opened a docs bug https://bugs.launchpad.net/openstack-manuals/+bug/1673616
21:58:51 mriedem dansmith: you might want to add/update/fix whatever i put in the description
22:00:12 dansmith okay
22:00:29 dansmith looks alright to me at first skim but I'll think on it a bit
22:01:15 openstackgerrit Matt Riedemann proposed openstack/nova master: api-ref: fix description in os-services https://review.openstack.org/446757
22:18:05 openstackgerrit melanie witt proposed openstack/nova master: Improve descriptions for hostId, host, and hypervisor_hostname https://review.openstack.org/446761
22:18:37 melwitt mriedem: ^ patch for the host* api-ref stuff
22:26:39 openstackgerrit Octave Orgeron proposed openstack/nova-specs master: Enables MySQL Cluster Support for Nova https://review.openstack.org/446631
22:33:55 mriedem melwitt: thanks, comments inline
22:45:56 cfriesen is there a known issue in newton where pre_live_migration() can hit an RPC timeout waiting for a really big glance image to download to the destination?
22:56:52 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Updated from global requirements https://review.openstack.org/446777
23:10:52 openstack Launchpad bug 1673628 in OpenStack Compute (nova) "api-ref: 'tags' field is not in response parameters docs for "GET /servers/{server_id}"" [Medium,Confirmed]
23:10:52 mriedem easy bug fix https://bugs.launchpad.net/nova/+bug/1673628
23:11:07 mriedem cfriesen: that's not a newton specific limitation
23:11:15 mriedem that's a latent issue forever
23:11:41 mriedem cfriesen: see https://review.openstack.org/#/c/419662/1
23:13:36 openstackgerrit Matt Riedemann proposed openstack/nova-specs master: Repropose tag-instance-when-boot https://review.openstack.org/415315
23:13:45 mriedem Kevin_Zheng: are you ok with the updates i made to ^?
23:18:20 mriedem melwitt: i think your func test change might be causing a race issue with global state
23:20:01 mriedem yeah you need to use fake.restore_nodes
23:24:09 sbezverk hello, I need to check liveness of nova placement api process, could you recommen any methods to check not just that the socket is opened but also that the process is alive and sane.
23:24:26 mriedem sbezverk: make a curl request to / ?
23:24:54 mriedem that's testing much more than just the process is running
23:25:01 sbezverk mriedem: would it not just check apachie liveness?
23:25:28 mriedem making a curl request to the actual endpoint's root would provide the versions available, which means it's up and running and accepting requests
23:25:31 mriedem and serving a response
23:25:51 mriedem i don't know if a token is required for GET / on the placement endpoint though
23:26:22 sbezverk mriedem: cool, thank you very much. I was not sure if curling for root is sufficient
23:26:53 mriedem yup that will get you the versions available
23:39:19 openstackgerrit Ghanshyam Mann proposed openstack/nova master: Add api-ref for filter/sort whitelist https://review.openstack.org/421760
23:39:52 sbezverk mriedem: any known issue with placement in ocata you are aware?
23:39:55 openstackgerrit Matt Riedemann proposed openstack/nova master: Fix functional regression/recreate test for bug 1671648 https://review.openstack.org/446685
23:39:56 openstack bug 1671648 in OpenStack Compute (nova) ocata "Instances are not rescheduled after deploy fails" [High,In progress] https://launchpad.net/bugs/1671648 - Assigned to Matt Riedemann (mriedem)
23:40:21 mriedem sbezverk: nothing major for placement that i can think of
23:40:33 mriedem sbezverk: we did release some fixes for ocata in 15.0.1 earlier in the week,
23:40:39 mriedem so if you're upgrading, i'd use 15.0.1
23:41:13 sbezverk mriedem: I brining up at the gate ocata images in kolla-kubernetes project
23:41:41 sbezverk what worked with stable/newton seems broken in ocata, but it might be our issue too..
23:42:57 mriedem sbezverk: i guess i'd need a more specific example of what's not working
23:43:56 Sukhdev dear Nova folks, after fresh install of devstack, Nova continue to return "No Valid host found" error - can somebody provide some wisdom, please? See the details here - http://paste.openstack.org/show/603034/
23:44:29 sbezverk mriedem: :) glad you asked. When I start instance I get " Placement API service is not responding." in nova scheduler log
23:44:59 mriedem sbezverk: are you starting the placement service before the nova-scheduler service?
23:45:04 sbezverk mriedem: it looks like connectivity issue but nothing change other than just version of images
23:45:12 mriedem is there a "placement" endpoint in the service catalog?
23:45:37 sbezverk mriedem: yep, service catalog shows placement entries
23:45:38 mriedem is nova.conf for the scheduler configured to use placement in the [placement] section, and are the credentials in there correct?
23:46:13 sbezverk mriedem: all valid points, but as I said nothing changed in the gate job other than image version
23:46:30 mriedem the scheduler didn't use placement in newton,
23:46:34 mriedem so that's a main different with ocata
23:46:38 sbezverk mriedem: was there any change in endpoint registrations between newton and ocata?
23:46:46 mriedem in newton, only the nova-compute service tried connecting to the placement service

Earlier   Later