Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2019-04-04
00:51:52 mriedem even if it was templated, it would be the full url when pulled out of the CellMapping object attribute
00:52:06 sean-k-mooney :(
00:52:30 sean-k-mooney the patch mentioned it was transfroming the notificaiton to the versioned form
00:52:46 sean-k-mooney was this previouly sent via the unversioned endpoint
00:53:05 mriedem i doubt it
00:53:35 sean-k-mooney ok so it is a regression in stien and i agree it a security concern too.
00:53:59 sean-k-mooney how did you come across it
00:54:00 mriedem the unversioned notification sent RequestSpec.to_legacy_request_spec_dict()
00:54:18 mriedem tssurya -1ed a change of mine saying i should add more stuff to that notification since i added a new field to the Destination object
00:55:06 mriedem https://review.openstack.org/#/c/614035/
00:55:08 sean-k-mooney mriedem: ah ok i similarly modifed a field in one of my patches and it ended up changin the image metadata notificaion
00:55:23 sean-k-mooney which i undersand in a way but i also was confused by
00:55:43 sean-k-mooney it seams that we not have to version some object when field in an objec support new values
00:56:00 sean-k-mooney previousl we did not version bump object for compostion
00:56:10 sean-k-mooney only when fields were added or removed
00:56:38 mriedem gibi_off: stephenfin: https://review.openstack.org/#/c/508506/28/nova/notifications/objects/request_spec.py@334 - if we don't need those i don't tihnk we should be sending them out of nova on the notification bus
01:02:16 sean-k-mooney mriedem: do we want to even include the cell here https://review.openstack.org/#/c/508506/28/nova/notifications/objects/request_spec.py@284
01:02:55 mriedem idk, the legacy notification for select_destinations didn't send all of this stuff
01:02:58 mriedem so i don't know why it was all added
01:03:13 mriedem the legacy notification sent a legacy more minimal view of the request spec
01:03:23 mriedem this version is everything
01:03:57 mriedem sending the name/uuid of the cell is meh to me
01:04:18 mriedem sending the URLs with credentials to connect to the cell...that's a bad idea
01:04:20 sean-k-mooney ya i was just looking at what the to_legacy_request_spec_dict function did
01:04:59 sean-k-mooney i would proably change 'cell': fields.ObjectField('CellMappingPayload', nullable=True),
01:05:01 mriedem well i threw this on the RC2 etherpad so i guess can wait for others to look and provide an opinion
01:05:14 sean-k-mooney to 'cell': fields.UUIDFiled(nullable=True),
01:05:45 sean-k-mooney and then drop the CellMappingPayload object entirely
01:06:32 sean-k-mooney i think we require the host to be unique across all cells anyway though so the cell is uudi is not really needed
01:09:24 mriedem i'm dropping off
01:09:32 sean-k-mooney o/
01:45:18 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Add in_tree field to RequestGroup object https://review.openstack.org/649534
01:45:18 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: Pass node uuid to new Destination.node_uuid https://review.openstack.org/649533
01:45:19 openstackgerrit Tetsuro Nakamura proposed openstack/nova master: node_uuid from RequestSpec to ResourceRequest https://review.openstack.org/649535
02:20:19 ileixe Hi forks.
02:20:20 openstackgerrit Matt Riedemann proposed openstack/nova master: Obfuscate CellMappingPayload database_connection and transport_url https://review.openstack.org/649775
02:20:27 ileixe Is this bp https://review.openstack.org/#/c/599598/ abonded at all?
02:20:36 ileixe abandoned*
02:21:04 ileixe We need this functionality a lot, so I wonder about it.
02:22:34 openstackgerrit Matt Riedemann proposed openstack/nova master: Obfuscate CellMappingPayload database_connection and transport_url https://review.openstack.org/649775
02:24:13 mriedem melwitt: added you and others https://review.openstack.org/#/c/649775/
02:24:18 mriedem wip until people chew on the alternatives
02:27:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Add nova-status upgrade check for minimum required cinder API version https://review.openstack.org/649759
02:27:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove MIN_COMPUTE_MULTIATTACH conditions in API https://review.openstack.org/649757
02:27:40 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Drop pre-cinder 3.44 version compatibility https://review.openstack.org/621061
02:31:51 openstackgerrit zhufl proposed openstack/nova master: Remove reading xvpconf_template in xvp.py https://review.openstack.org/649777
02:36:29 openstackgerrit Bhagyashri Shewale proposed openstack/nova master: Ignore root_gb for BFV in simple tenant usage API https://review.openstack.org/612626
02:37:23 openstackgerrit Ghanshyam Mann proposed openstack/nova-specs master: Spec for API inconsistency cleanup https://review.openstack.org/603969
02:44:02 openstackgerrit Takashi NATSUME proposed openstack/nova master: Change a log level for overwriting allocation https://review.openstack.org/649788
03:26:43 openstackgerrit Alex Xu proposed openstack/nova master: [DNM] debug the LM test https://review.openstack.org/649807
04:31:37 openstackgerrit Jake Yip proposed openstack/nova master: Add --before to nova-manage db archive_deleted_rows https://review.openstack.org/556751
06:07:33 openstackgerrit Huqiang Wang proposed openstack/nova-specs master: Separate the vCPUs into different pools based on priority https://review.openstack.org/649882
07:31:10 openstackgerrit Huqiang Wang proposed openstack/nova-specs master: Separate the vCPUs into different pools based on priority https://review.openstack.org/649882
08:30:12 openstackgerrit zhaixiaojun proposed openstack/nova master: Update description of valid whitelist https://review.openstack.org/642403
08:33:02 openstackgerrit zhaixiaojun proposed openstack/nova master: Update description of valid whitelist https://review.openstack.org/642403
08:34:38 kashyap Is there some 'tox' shortcut to build _just_ one releases's specs?
08:34:47 kashyap `tox -e docs train` or something like that
08:44:52 openstackgerrit Michael Still proposed openstack/nova master: Hacking N362: Don't abbrev/alias privsep import https://review.openstack.org/649190
08:44:53 openstackgerrit Michael Still proposed openstack/nova master: Improve test coverage of nova.privsep.fs. https://review.openstack.org/648602
08:44:53 openstackgerrit Michael Still proposed openstack/nova master: Improve test coverage of nova.privsep.path. https://review.openstack.org/648601
08:44:54 openstackgerrit Michael Still proposed openstack/nova master: Add test coverage for nova.privsep.libvirt. https://review.openstack.org/648616
08:44:54 openstackgerrit Michael Still proposed openstack/nova master: Improve test coverage of nova.privsep.fs, continued. https://review.openstack.org/648603
08:44:55 openstackgerrit Michael Still proposed openstack/nova master: Privsepify ipv4 forwarding enablement. https://review.openstack.org/635431
08:44:55 openstackgerrit Michael Still proposed openstack/nova master: Add test coverage for nova.privsep.qemu. https://review.openstack.org/649191
08:44:56 openstackgerrit Michael Still proposed openstack/nova master: Privsep the ebtables modification code. https://review.openstack.org/635435
08:44:56 openstackgerrit Michael Still proposed openstack/nova master: Remove unused FP device creation and deletion methods. https://review.openstack.org/635433
08:44:57 openstackgerrit Michael Still proposed openstack/nova master: Move iptables rule fetching and setting to privsep. https://review.openstack.org/636508
08:44:57 openstackgerrit Michael Still proposed openstack/nova master: Move adding vlans to interfaces to privsep. https://review.openstack.org/635436
08:44:58 openstackgerrit Michael Still proposed openstack/nova master: Move router advertisement daemon restarts to privsep. https://review.openstack.org/639281
08:44:58 openstackgerrit Michael Still proposed openstack/nova master: Move dnsmasq restarts to privsep. https://review.openstack.org/639280
08:44:59 openstackgerrit Michael Still proposed openstack/nova master: Move setting of device trust to privsep. https://review.openstack.org/639283
08:44:59 openstackgerrit Michael Still proposed openstack/nova master: Move calls to ovs-vsctl to privsep. https://review.openstack.org/639282
08:45:00 openstackgerrit Michael Still proposed openstack/nova master: Cleanup the _execute shim in nova/network. https://review.openstack.org/639581
08:45:00 openstackgerrit Michael Still proposed openstack/nova master: Move final bridge commands to privsep. https://review.openstack.org/639580
08:45:01 openstackgerrit Michael Still proposed openstack/nova master: We no longer need rootwrap. https://review.openstack.org/554438
08:49:58 openstackgerrit zhaixiaojun proposed openstack/nova master: Update description of valid whitelist for non-admin user https://review.openstack.org/642403
09:17:14 openstackgerrit Lee Yarwood proposed openstack/nova master: libvirt: Avoid building an encryptor when device_path isn't provided https://review.openstack.org/649951
09:33:49 stephenfin kashyap: Not that I'm aware of, no. It's all or nothing
09:35:33 openstackgerrit Takashi NATSUME proposed openstack/nova master: Change a log level for overwriting allocation https://review.openstack.org/649788
09:47:35 openstackgerrit Boxiang Zhu proposed openstack/nova master: Make evacuation respects anti-affinity rule https://review.openstack.org/649953
10:21:37 openstackgerrit Boxiang Zhu proposed openstack/nova master: Use the functional test test_parallel_evacuate_with_server_group https://review.openstack.org/649963
11:17:35 awalende following problem: I had a semi-failed migration. The instance has been migrated to another host and is working so far. However, not everything has been adjusted in the db and I get the following log repeatedly in the source host:
11:17:53 awalende Y_MB': 2048, u'DISK_GB': 21}}
11:17:53 awalende Instance a3fcb5a8-74e3-42f9-9659-428ffe710c19 has been moved to another host schwalm. There are allocations remaining against the source host that might need to be removed: {u'resources': {u'VCPU': 2, u'MEMOR
11:18:20 awalende Where can I find the responsible parts in the db to clean up this mess?
11:24:26 tssurya awalende: depending on the release you are running this would be the "allocations" table in the nova_api or placement database
11:24:43 awalende It's queens :)
11:24:57 tssurya you could use the https://docs.openstack.org/osc-placement/latest/cli/index.html#resource-provider-allocation-delete CLI to remove the allocation against the migration record on the source host
11:25:06 tssurya ah if queens its nova_api database
11:25:09 tssurya allocations table
11:26:11 tssurya awalende: you should be able to find records for that migration_uuid as the consumer against the source resource_provider
11:28:10 awalende select * from allocations where consumer_id='a3fcb5a8-74e3-42f9-9659-428ffe710c19';
11:28:34 awalende this gave me 3 rows, so I simply have to overwrite the resource_provider_id with the id from the new host?
11:29:11 tssurya awalende: the consumer_id is name of your instance ? or the migration_uuid ?
11:29:28 awalende instance id
11:29:46 tssurya ah so these are the allocations against the new host for your instance
11:30:02 awalende ah okay
11:30:10 tssurya could you verify by checking the resource_provider_id ? these three records should be the ones you should NOT delete
11:30:40 tssurya what you should do is query with consumer_id=migration_uuid
11:30:45 awalende is there a smart way to find out the resource_provider_id of each computehost?

Earlier   Later