Earlier  
Posted Nick Remark
#openstack-nova - 2019-02-12
10:20:38 abhishekk I have tried to set default_log_levels = sqlalchemy=INFO but its not working
10:20:51 gibi bauzas: push your new revision up and I will check the functional test
10:20:56 bauzas ack
10:21:01 bauzas it will fail your change tho
10:21:06 openstackgerrit Lee Yarwood proposed openstack/nova master: compute: Reject migration requests when source is down https://review.openstack.org/623489
10:21:33 bauzas gibi: I'll just add a new change for correctly using the right mdev before tho
10:21:36 gibi bauzas: you mean it will fail the functional test? That is OK I will check that
10:21:46 lyarwood sean-k-mooney / stephenfin / mdbooth_ ^ I'd appreciate your thoughts on my bugfix above if you have time today
10:22:33 lyarwood oh and is anyone else having weird issues building releasenotes on f29?
10:23:54 stephenfin and tries building releasenotes to check
10:24:44 lyarwood stephenfin: /src/openstack/nova/releasenotes/source/rocky.rst:3436:Duplicate explicit target name: "rest api version history". - is the error I'm getting locally
10:27:45 stephenfin lyarwood: That doesn't sound like something F29 specific. That would happen if someone had defined the same target in two release notes, which it looks like someone has
10:28:01 stephenfin though it's building just fine for me...
10:28:42 lyarwood stephenfin: kk there must be some cruft in my local repo somewhere
10:29:10 stephenfin 'git clean -xfd -e .tox' <-- I should have this aliased
10:42:21 openstackgerrit Boris Bobrov proposed openstack/nova master: Fix memtune parameters according to libvirt docs https://review.openstack.org/636301
10:43:43 openstackgerrit Boris Bobrov proposed openstack/nova master: Fix memtune parameters according to libvirt docs https://review.openstack.org/636301
12:00:24 openstackgerrit Zhenyu Zheng proposed openstack/nova master: Add method to allow reset fields for root bdm in BDM obj https://review.openstack.org/614672
12:10:32 openstackgerrit Boris Bobrov proposed openstack/nova master: Add configs for AMD SEV https://review.openstack.org/636318
12:45:27 openstackgerrit Jim Rollenhagen proposed openstack/nova master: Ironic: bump minimum API version to 1.38 https://review.openstack.org/636326
12:45:46 jroll TheJulia: ^ sanity check me that this is cleanup we want to do, please
13:14:09 mriedem http://logs.openstack.org/67/620667/3/check/tempest-full/8fa0aa0/controller/logs/screen-n-api.txt.gz?level=TRACE#_Feb_12_00_25_30_615423
13:14:09 mriedem tssurya: i think we might have some traces in the api logs that are saying a cell is down when it's really something else
13:14:37 mriedem although it looks like there are some MQ issues in those logs
13:37:39 lyarwood mriedem: https://review.openstack.org/#/c/551302/ - has been rebased and should be ready to review again if you have anytime this week.
13:38:25 mriedem lyarwood: yup in the queue
13:38:45 mriedem did you see the conversation in there about rollback also being busted?
13:40:06 lyarwood mriedem: so I think mdbooth was addressing that in a follow up here https://review.openstack.org/#/c/551349/2
13:40:56 lyarwood mdbooth: ^ I can also rebase / refresh that if you'd like
13:42:11 mdbooth lyarwood mriedem: Yeah, although not having time to address that too is probably the biggest reason I haven't looked at this in ages.
13:42:33 mdbooth Definitely a thing, though.
13:49:23 openstackgerrit Balazs Gibizer proposed openstack/nova master: Ensure that bandwidth and VF are from the same PF https://review.openstack.org/623543
13:57:30 openstackgerrit Boris Bobrov proposed openstack/nova master: Extract SEV-specific bits on host detection https://review.openstack.org/636334
14:00:55 stephenfin sean-k-mooney: Thoughts? http://paste.openstack.org/show/B9unIL8e2KpeSMBGaINe/
14:02:03 stephenfin sean-k-mooney: I'm annoyed by the fact we have no central definition (for docs) or validation of flavour extra specs. Thinking it might be a good, easy spec for T (for the ones we're not deprecating with the cpu-resources spec
14:05:43 bauzas stephenfin: we have documentation for flavor extra specs
14:05:52 bauzas unless I misunderstand your concern
14:06:27 sean-k-mooney stephenfin: we do it called the glance metadef registry
14:06:31 bauzas https://docs.openstack.org/nova/latest/user/flavors.html
14:06:51 stephenfin bauzas: Yup, but it's not "in code" or verified against the code, unlike e.g. the nova.conf options
14:06:57 bauzas ahah
14:07:04 bauzas well
14:07:08 gibi bauzas: if you have time, can you push this two-patch backport? https://review.openstack.org/#/c/623358/1
14:07:08 bauzas AFAIK, we said meh
14:07:14 sean-k-mooney stephenfin: https://github.com/openstack/glance/blob/master/etc/metadefs/compute-cpu-pinning.json
14:07:21 bauzas gibi: looking
14:07:22 sean-k-mooney that is in code in a way
14:07:24 gibi bauzas: thanks
14:07:51 bauzas gibi: oh that one
14:07:58 bauzas gibi: silverlining, already reviewed it
14:08:53 sean-k-mooney stephenfin: it is intended to be used for validating glance metadata entries and its used but horizon to generate teh ui with the dropdown vlaues and for validation
14:09:22 sean-k-mooney it also has defintions for the flavor extra specs too.
14:09:45 mriedem tssurya: dansmith: i left comments in the down cell servers view builder change, the series is going to have to be rebased
14:10:00 sean-k-mooney stephenfin: what might make sense it to extract it into a seperate repo that glance,nova and cinder can all import and share
14:10:00 stephenfin sean-k-mooney: Aye, I knew about. If that was ever kept up-to-date though, I'm not sure if it still is. Barely any edits in years https://github.com/openstack/glance/tree/master/etc/metadefs
14:10:33 stephenfin I didn't know that it supported flavour extra specs though. That's good to know
14:10:59 stephenfin sean-k-mooney: Aye, I think so. I'll have a look into it when I get a chance. Just been annoying me for some time now
14:11:11 sean-k-mooney stephenfin: ya it was orginally created to keep the falvor extra specs and image metadata in sync
14:11:38 sean-k-mooney if we did extract it i dont see why we could not autogenerate the docs for it too
14:13:36 openstackgerrit Artom Lifshitz proposed openstack/nova master: Remove _legacy_dict methods https://review.openstack.org/636210
14:13:37 openstackgerrit Artom Lifshitz proposed openstack/nova master: New objects to transmit NUMA config from dest to source https://review.openstack.org/634827
14:13:37 openstackgerrit Artom Lifshitz proposed openstack/nova master: Add migration param to check_can_live_migrate_destination https://review.openstack.org/634605
14:13:38 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] Use live_migration_claim() to check dest resources https://review.openstack.org/634606
14:13:38 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] Introduce live_migration_claim() https://review.openstack.org/635669
14:13:39 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] LM: update NUMA-related XML on the source https://review.openstack.org/635229
14:13:39 openstackgerrit Artom Lifshitz proposed openstack/nova master: [WIP] LM: Make dest send NUMAMigrateData to the source https://review.openstack.org/634828
14:13:42 kashyap Gosh, this serial / char devices code is making me go slowly mental...
14:13:44 sean-k-mooney stephenfin: can we put it as a cross project topic with the glance and maybe cinder folks for the ptg
14:14:16 stephenfin sean-k-mooney: Good idea, that
14:15:32 sean-k-mooney stephenfin: it looks like it also cover nova host aggrage metadata too https://github.com/openstack/glance/blob/master/etc/metadefs/compute-aggr-num-instances.json
14:15:34 bauzas lyarwood: I just agree with mriedem_snow on https://review.openstack.org/#/c/628726/4
14:15:46 bauzas lyarwood: we should make backports easy by providing a series
14:15:48 bauzas WDYT ?
14:16:36 bauzas since you already identified the source of the conflicts, and you also want to backport the missing changes, I don't see any difficulty in making the backports intertwined
14:16:36 lyarwood bauzas: yeah ack sorry I totally forgot about that
14:16:50 bauzas lyarwood: ack, ping me when you're done then
14:17:29 bauzas that's what happens when you write poor interfaces
14:20:57 NewBruce sean-k-mooney any chance i can get your thoughts on a bit of a bug that looks to be related to the port binding API changes?
14:25:07 sean-k-mooney NewBruce: i saw you comments this moring
14:25:19 NewBruce awesome, sorry for chasing
14:25:44 NewBruce done some more debugging now, and feels like i isolated the point it fails
14:25:47 sean-k-mooney no worries i just havent had a chance to reply was booking flights and stuff
14:26:02 sean-k-mooney so one general question
14:26:06 NewBruce np. hope your goin' somewhere warm
14:26:24 sean-k-mooney PTG flights
14:26:25 openstackgerrit Merged openstack/nova stable/pike: Handle IndexError in _populate_neutron_binding_profile https://review.openstack.org/635921
14:26:28 NewBruce sure -
14:27:01 sean-k-mooney am you have a mixed cloud with OSA nodes and RDO nodes
14:27:21 NewBruce correct
14:27:28 sean-k-mooney is the contol plan. e.g. your contolers all RDO or is it also mixed
14:27:42 NewBruce control plane is upgrade to Rocky/OSA
14:28:21 NewBruce we have multiple sites, with the same config which dont exhibit the problem
14:28:27 sean-k-mooney ok so you have Rocky/OSA contol plane + OSA computes + some rocky/RDO computes
14:28:36 NewBruce correct
14:28:54 NewBruce looking in the setup today we have some RDO net nodes as well
14:29:20 sean-k-mooney and on the neutron side is it also a mix or all OSA for you neturon controler services
14:29:30 NewBruce so they could do with being upgraded.... but in the debugging ive done today, it seems to bail out in the call to _setup_migration_port_profile
14:29:46 dansmith mriedem_snow: okay I was thinking we should maybe try real hard to get that merged today
14:29:59 NewBruce in a successful migration, the host_id passed to _setup_migration_port_profile is the target/dest compute; whereas in a failure the host_id passed to _setup_migration_port_profile is the source
14:30:02 sean-k-mooney how the multiple portbinging code is ment to work is that the nova condocutor is first ment to check the neutron api to determin if neutron support it

Earlier   Later