Posted	Nick	Remark
#openstack-nova - 2019-11-15
18:04:17	melwitt	gibi: updated ^
18:18:47	openstackgerrit	Dustin Cowles proposed openstack/nova-specs master: Update provider config spec for identification conflicts https://review.opendev.org/693414
18:18:56	eandersson	gibi thanks a lot for fixing that bug
18:19:02	eandersson	I completely forgot to open a bug for it.
18:26:41	gibi	melwitt: +2 thank you!
18:26:49	gibi	eandersson: no worries
18:26:57	melwitt	thanks!
19:21:45	openstackgerrit	Matt Riedemann proposed openstack/nova master: doc: mention that rescuing a volume-backed server is not supported https://review.opendev.org/694584
20:29:01	efried	melwitt: aren't you doing something with host status UNKNOWN? http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010887.html
20:29:23	efried	ah https://blueprints.launchpad.net/nova/+spec/policy-rule-for-host-status-unknown
21:27:56	mriedem	s/doing/done/!
22:07:14	efried	yeah, once I saw I had even approved it, it all came back to me.
23:01:34	openstackgerrit	Merged openstack/nova master: Always trait the compute node RP with COMPUTE_NODE https://review.opendev.org/688979
23:01:39	openstackgerrit	Merged openstack/nova master: docs: Extract rescue from reboot https://review.opendev.org/694529
23:11:09	openstackgerrit	Merged openstack/nova master: Remove fixed sqlalchemy-migrate deprecation warning filters https://review.opendev.org/690704
23:13:06	efried	mriedem: quick ack on https://review.opendev.org/#/c/689823/ if you can please
23:17:43	mriedem	i thought you thought set commands should be a full overwrite?
23:22:24	efried	mriedem: Didn't we agree earlier that adding --amend to a `set` would mean "add on"?
23:22:41	efried	And there's no way to do partial removals with --amend, you have to implement an `unset`?
23:23:15	efried	I don't love it, but it's simple(r than the alternatives)
23:24:42	mriedem	i left some comments
23:24:54	mriedem	we have some docs to update
23:40:54	efried	Thanks mriedem. I actually tried `set` with no ``-trait`` before I posted my comments, it does indeed wipe out all the traits on the provider.
23:41:01	efried	With that, I'm out o/
23:41:12	mriedem	\o
23:48:48	mriedem	just played the clean version of big poppa by notorious big to my kid and had to explain what "macking" means
23:48:54	mriedem	harder than you'd think
23:49:55	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add revert_snapshot_based_resize conductor RPC method https://review.opendev.org/638047
23:49:55	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add RevertResizeTask https://review.opendev.org/638046
23:49:56	openstackgerrit	Matt Riedemann proposed openstack/nova master: Confirm cross-cell resize while deleting a server https://review.opendev.org/638268
23:49:56	openstackgerrit	Matt Riedemann proposed openstack/nova master: Revert cross-cell resize from the API https://review.opendev.org/638048
23:49:57	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add CrossCellWeigher https://review.opendev.org/614353
23:49:57	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add archive_deleted_rows wrinkle to cross-cell functional test https://review.opendev.org/651650
23:49:58	openstackgerrit	Matt Riedemann proposed openstack/nova master: Support cross-cell moves in external_instance_event https://review.opendev.org/658478
23:49:58	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add functional test for anti-affinity cross-cell migration https://review.opendev.org/661859
23:49:59	openstackgerrit	Matt Riedemann proposed openstack/nova master: Add cross-cell resize policy rule and enable in API https://review.opendev.org/638269
23:49:59	openstackgerrit	Matt Riedemann proposed openstack/nova master: libvirt: flatten rbd image during cross-cell move spawn at dest https://review.opendev.org/691991
23:50:00	openstackgerrit	Matt Riedemann proposed openstack/nova master: WIP: Add negative test to delete server during cross-cell resize claim https://review.opendev.org/688832
23:50:00	openstackgerrit	Matt Riedemann proposed openstack/nova master: WIP: Enable cross-cell resize in the nova-multi-cell job https://review.opendev.org/656656
#openstack-nova - 2019-11-16
00:39:07	openstackgerrit	Merged openstack/nova stable/train: Use admin neutron client to gather port resource requests https://review.opendev.org/694015
00:39:12	openstackgerrit	Merged openstack/nova stable/train: Use admin neutron client to see if instance has qos ports https://review.opendev.org/694018
00:39:23	openstackgerrit	Merged openstack/nova master: Remove duplicate ServerMovingTests._resize_and_check_allocations https://review.opendev.org/694538
00:45:00	openstackgerrit	Merged openstack/nova master: Use wrapper class for NeutronFixture get_client https://review.opendev.org/693453
07:48:38	openstackgerrit	Merged openstack/nova master: api-ref: re-work migrate action post-conditions https://review.opendev.org/694103
07:48:45	openstackgerrit	Merged openstack/nova master: doc: mention that rescuing a volume-backed server is not supported https://review.opendev.org/694584
07:50:18	openstackgerrit	Merged openstack/nova master: Remove super old br- neutron network id compat code https://review.opendev.org/693411
08:28:42	openstackgerrit	Merged openstack/nova master: Block deleting compute services with in-progress migrations https://review.opendev.org/694389
10:05:48	openstackgerrit	Balazs Gibizer proposed openstack/nova stable/stein: Use admin neutron client to query ports for binding https://review.opendev.org/694665
16:34:00	openstackgerrit	Balazs Gibizer proposed openstack/nova stable/stein: Use admin neutron client to see if instance has qos ports https://review.opendev.org/694668
#openstack-nova - 2019-11-17
07:57:50	adrianc	artom: Hi, regarding the Mellanox CI question, it indeed runs on Mellanox hardware but SR-IOV once configured, behaves the same across vendors. Also we are stabilizing the CI as it was feeling a bit under the weather lately.
#openstack-nova - 2019-11-18
06:21:03	openstackgerrit	OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.opendev.org/694717
08:36:12	bauzas	good morning Nova
08:47:02	gibi	bauzas: good morning
08:47:13	bauzas	:)
08:47:27	bauzas	ta, you too
09:29:56	brinzhang	good morning :)
09:49:55	bauzas	brinzhang: heh, good morning !
09:56:53	brinzhang_	bauzas: gibi: I was updated the flavor explosion spec after PTG, and base gibi's comments updated again, please review, Thanks :P
09:57:26	brinzhang_	bauzas: gibi: spec https://review.opendev.org/#/c/663563/
09:57:38	bauzas	cool, I'll try
10:13:45	gibi	ack
10:16:07	kashyap	aspiers: If you're about, want to update the SLES versions here? -- https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix#Distro_minimum_versions
10:29:06	openstackgerrit	pangliye proposed openstack/nova master: Fix misspell word https://review.opendev.org/694741
10:32:10	openstackgerrit	Stephen Finucane proposed openstack/nova master: Stop testing Python 2 https://review.opendev.org/687954
10:32:11	openstackgerrit	Stephen Finucane proposed openstack/nova master: zuul: Make functional job inherit from openstack parents https://review.opendev.org/688425
10:33:35	kashyap	Anyone familiar with Debian here: why was "sid" (the 'unstable' version) chcked here? -- https://wiki.openstack.org/wiki/LibvirtDistroSupportMatrix
10:34:01	kashyap	zigo: ^
10:34:51	bauzas	kashyap: ask zigo
10:34:54	bauzas	heh
10:36:03	kashyap	:-)
10:36:18	kashyap	"sid" is the unstable edition; normally I'd check the "stable" version to be there
10:36:31	kashyap	Does Infra gate uses Debian "sid"? Maybe it's for #openstack-infra
10:37:07	zigo	kashyap: This looks wrong in many ways, for example, the qemu version ...
10:37:22	kashyap	zigo: Yeah! I'm right now undoing the mess, whoever did that
10:37:36	kashyap	zigo: So, to be clear, these are the versions from 'stable':
10:37:58	kashyap	- libvirt: 5.0.0-4
10:38:06	zigo	kashyap: In buster, we have qemu 1:3.1+dfsg-8+deb10u3
10:38:12	zigo	(ie: 3.1)
10:38:26	kashyap	- QEMU: 3.1
10:38:30	kashyap	zigo: Indeed
10:38:58	zigo	libvirt 5.0.0
10:39:16	kashyap	zigo: BTW, the version you see there for QEMU was checked on 2018-APR-05 -- so at _that_ time Buster indeed had 2.11 QEMU
10:39:20	zigo	kashyap: I believe it's just outdated ...
10:39:23	kashyap	So that's correct based on what was there at that time
10:39:36	zigo	Right.
10:39:53	kashyap	Yes, it is outdated. Updating these MediaWiki pages are a *pain* in the neck
10:40:16	zigo	Yeah, the syntax is ... hum... suboptimal, to use nice words! :)
10:41:20	kashyap	zigo: Refresh the page, and check if the Buster ("stable") looks correct now
10:42:13	zigo	kashyap: Well, it looks ok to me, though instead of Buster ("sid") you may want to write Bullseye ("sid") and write what's there.
10:43:55	kashyap	zigo: Right, let me do that
10:44:10	kashyap	I'll update the Buster ("sid") --> Bullseye ("sid")
10:45:36	kashyap	zigo: Am I correct in saying that what's at top-left (the 4.1.1) indicates the Bullseye ("sid") version? -- https://tracker.debian.org/pkg/qemu
10:45:45	kashyap	Also what does the "1:" mean?
10:46:26	zigo	kashyap: That's an "EPOCH".... basically, this is for when we do a mistake with the upstream version, and need to "upgrade" to a lower version.
10:46:34	zigo	So, that's distro specific ...
10:46:40	kashyap	Ah, right. The same concept exists in Fedora.
10:46:50	zigo	1:2.3.4 is higher that 2.3.5
10:46:51	kashyap	Much frowned upon, though. :-)
10:47:05	kashyap	Right.
10:47:18	zigo	We try to avoid it as much as possible, because that's very confusing when writting dependency, and a mistake may happen very fast...

Earlier   Later