Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-10-02
20:51:58 mriedem yes
20:52:06 sean-k-mooney ok cool
20:52:12 mriedem console proxy was a docs thing
20:52:50 mriedem my point is sev landed late with a ton of churn over 2 releases (speaking as an outside observer to that series), so i wouldn't be surprised if there aren't more hairy issues
20:52:59 mriedem seems like every issue in that series is very hard to resolve
20:53:34 mriedem i also won't be surprised when there are issues with PCPU - we haven't seen issues because we're not using it anywhere yet
20:53:50 mriedem but in 18 months...watch out!
20:54:24 sean-k-mooney well there kind of is one but it was an issue we defeind as out of scope
20:54:31 sean-k-mooney it related to https://review.opendev.org/#/c/686079/
20:55:52 sean-k-mooney you can only have flaoting instnace and pinned instance on the same host and not have mempage issue if you enable the numa aware memory tracking using hw:mem_page_size=<any valid value>
20:56:01 sean-k-mooney but we know it would not address that
20:58:55 efried mriedem: the console token thing we just merged? That wasn't a docs issue.
20:59:12 efried it may not have been related to an actual blueprint either though, not sure.
21:00:02 sean-k-mooney the console issue was passing the path argument in case it was not required right?
21:00:10 dansmith I think he means the cells console proxy doc thing
21:00:16 efried no
21:00:36 efried https://review.opendev.org/#/c/686066/ Reduce scope of 'path' query parameter to noVNC consoles
21:00:50 dansmith this: https://review.opendev.org/#/c/686271/
21:01:14 efried no
21:01:16 efried -----^
21:01:25 dansmith efried: I mean he==mriedem, not you
21:01:30 efried right
21:01:43 efried and confirmed it wasn't a blueprint, it was a bug
21:01:54 efried anywho
21:02:26 sean-k-mooney im going to call it a night o/
21:05:49 mriedem efried: oh i wasn't thinking of the serial console thing
21:06:13 mriedem efried: it was a bug fix for a novnc 1.1.0 regression or something but dug a bit too deep
21:06:20 efried y
21:06:27 mriedem and actually wouldn't have been caught had it not been backported and released on stable
21:07:16 mriedem speaking of, dansmith can you get https://review.opendev.org/#/c/686063/ on stein so we can do a stein release tomorrow?
21:07:22 mriedem i think that's the last thing i was waiting on
21:07:38 dansmith okay
21:25:05 openstackgerrit Eric Fried proposed openstack/nova master: Allow versioned discovery unauthenticated https://review.opendev.org/685181
21:27:12 openstackgerrit Eric Fried proposed openstack/nova master: Modify nova routing table to process null requests https://review.opendev.org/518119
21:46:48 ozzzo Is there an "openstack" command corresponding to every "nova" and "nova-manage" command?
21:47:20 ozzzo For example, can I do "nova-manage service-disable <HV UUID>" via openstack?
21:48:49 ozzzo or "nova service-list" ?
21:49:11 ozzzo The obvious thing to try would be "openstack service list" but that does something different
21:56:23 mriedem yes,
21:56:31 mriedem https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/compute-service.html#compute-service-set
21:56:47 mriedem nova-manage and nova/openstack CLIs are not the same
21:57:18 mriedem the former doesn't use apis, but hits the db directly when the api isn't available, and doesn't require a token, the latter requires a token and uses the api
21:57:40 mriedem you're also looking for this https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/compute-service.html#compute-service-list
21:58:15 ozzzo very nice, thank you!
22:01:59 openstackgerrit Takashi NATSUME proposed openstack/nova master: Fix unit of hw_rng:rate_period https://review.opendev.org/683051
22:02:08 openstackgerrit Takashi NATSUME proposed openstack/nova master: Update keypairs in saving an instance object https://review.opendev.org/683043
22:02:17 openstackgerrit Takashi NATSUME proposed openstack/nova master: Move Destination object tests to their own test class https://review.opendev.org/683017
22:18:56 ozzzo Is there an "openstack" command for "nova-manage cell_v2 discover-hosts" ?
22:19:02 mriedem no
22:20:15 mriedem there is a config option to enable it in a periodic task if you don't want to hit the command line
22:20:30 ozzzo ok ty
22:20:35 mriedem https://docs.openstack.org/nova/latest/configuration/config.html#scheduler.discover_hosts_in_cells_interval
22:27:36 melwitt mriedem: at first glance I wondered if this is related to the recent eventlet tpool proxy change, but it's reported against ocata https://bugs.launchpad.net/nova/+bug/1845759
22:27:36 openstack Launchpad bug 1845759 in OpenStack Compute (nova) "Openstack nova-compute service gives cant start new thread with oslo messaging" [Undecided,New]
22:28:18 mriedem i saw it in triage but didn't have thoughts on it
22:29:32 melwitt me neither. I've never seen anything like it before
22:33:53 ozzzo I was thinking that "openstack compute service delete" would behave similar to "openstack resource provider delete" but the service did not come back when I typed "nova-manage cell_v2 discover_hosts"
22:34:02 ozzzo how can I re-create the hypervisor service that I deleted?
22:38:21 artom sean-k-mooney, https://review.opendev.org/#/c/685387/? Yeah
22:39:19 melwitt ozzzo: I think just create it again https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/service.html#service-create the service command is different than the resource provider command, the resource provider command modifies only the placement service database and the service command modifies both the nova service database and the placement service database (by way of the placement API)
22:44:38 ozzzo ok I'll try that, ty!
22:45:52 melwitt 'openstack compute service delete' will delete the records of the service in the nova database and then it will do an equivalent REST API call as 'openstack resource provider delete' to the placement service
22:50:08 ozzzo that didn't seem to work; I typed "openstack service create --name us01odc-dev1-hv001 --enable nova-compute" but I still only have 2 hypervisor services under "openstack compute service list"
22:51:09 ozzzo It looks like I created a new service called us01odc-dev1-hv001 under "openstack service list"
22:51:28 ozzzo it looks like "service" and "compute service" are 2 different things
22:52:06 melwitt yeah... I'm looking at the doc and the <type> looks like it should be one of compute, identity, volume but I'm not 100% sure
22:52:19 ozzzo on the "compute service" man page I only see delete, list and set, there is no create
22:54:22 openstackgerrit Eric Fried proposed openstack/nova master: Add a way to spy on function calls in test https://review.opendev.org/686207
22:54:23 openstackgerrit Eric Fried proposed openstack/nova master: Replace mock with spy in test https://review.opendev.org/686208
22:54:36 efried gibi, dansmith: There ^
22:55:08 efried (recommend looking at the test deltas first)
22:56:06 ozzzo I stop/started nova-compute on the hypervisor; that appears to have re-created the service
22:56:16 ozzzo thanks for your advice melwitt!
22:57:37 ozzzo I'm trying to figure out how to remove, repair and re-add broken hypervisors
22:57:41 melwitt ozzzo: oh, yeah ok, all you have to do it start the service, I guess that makes sense -_- heh. I guess just delete that extra service from earlier so it won't confuse you later
22:57:56 melwitt whatever that was, the one that didn't help
22:58:02 ozzzo righton
22:59:52 ozzzo I guess service means 2 things in OS; there's a "nova" service that has multiple service providers, managed by "openstack service" but there's also a "nova-compute" service that runs on each of those service providers, managed by "openstack compute service"
23:02:53 melwitt yeah, it looks like the unified client (openstackclient) lumps all the services together for the 'service list' but when you do a 'service create' you have to specify the <type> which is either 'compute' (nova), 'identity' (keystone), 'volume' (cinder) etc and they are compartmentalized like that
23:04:01 melwitt and the <type> lets the client know which REST API to call
23:04:52 ozzzo ok, I'm starting to get it
23:05:01 melwitt but it sounds like there's no validation on the <type> so it allows anything and tries to do a lookup in the service catalog and doesn't raise an error? that seems odd
23:05:45 melwitt I'm just speculating, I'd have to look in the code to know for sure
23:09:52 openstackgerrit Merged openstack/nova stable/train: Imported Translations from Zanata https://review.opendev.org/685534
23:09:58 openstackgerrit Merged openstack/nova master: Restore console proxy deployment info to cells v2 layout doc https://review.opendev.org/686271
23:40:14 openstackgerrit Eric Fried proposed openstack/nova master: Replace mock with spy in test https://review.opendev.org/686208
#openstack-nova - 2019-10-03
00:22:54 openstackgerrit Merged openstack/nova stable/stein: Reduce scope of 'path' query parameter to noVNC consoles https://review.opendev.org/686063
02:21:19 SonPham have any project for nova for snapshot(keep memory and process state) like bp? : https://blueprints.launchpad.net/nova/+spec/live-snapshot-vms
02:23:11 openstackgerrit Merged openstack/nova stable/queens: Hook resource_tracker to remove stale node information https://review.opendev.org/676282
03:03:53 openstackgerrit Matt Riedemann proposed openstack/nova stable/train: Restore console proxy deployment info to cells v2 layout doc https://review.opendev.org/686325
03:28:32 openstackgerrit Merged openstack/nova master: Test heal port allocations in nova-next https://review.opendev.org/669879
04:23:10 SonPham hi
04:23:12 SonPham I would like to propose a new feature for Nova
04:23:37 SonPham after i create a blueprint
04:24:00 SonPham What should I do next?
06:37:13 SonPham hi
07:30:55 kashyap SonPham: The blueprint needs to get 'approved' by "cores" for the current development cycle.
07:32:29 kashyap SonPham: For that, you might want to hang around here on this channel and ask when you see 'activity'
07:33:35 kashyap SonPham: Another way to socialize your idea is to write a quick email to the 'openstack-discuss' list with [nova] tag, describing the potential feature.
07:35:46 SonPham kashyap who 'activity' ?

Earlier   Later