Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-08-10
15:11:34 mriedem oh i know why
15:11:36 mriedem it's deleted
15:11:45 mriedem and when the RT gets InstanceNotFound, it deletes the allocations
15:12:13 jaypipes is it just me or is the gate getting better...
15:12:16 mriedem dtantsur: i've been leaning on dansmith for that change
15:12:21 mriedem dtantsur: but he's out the rest of the week
15:12:28 mriedem dtantsur: so it's likely rc2 at this point
15:12:43 dtantsur yeah, it's fine, as long as it gets into Pike at all
15:12:51 mriedem jaypipes: except for the slow nodes and timeouts, it's not bad
15:14:28 mriedem gibi: i wonder why https://review.openstack.org/#/c/492548/ keeps saying it can't merge?
15:14:34 mriedem but don't rebase the entire series...
15:15:00 gibi mriedem: I think it is because I adding the test at the end of the test_server.py
15:15:23 jaypipes mriedem, bauzas, sdague: should be simple review: https://review.openstack.org/#/c/491822/
15:15:31 gibi mriedem: but I can try locally
15:16:19 gibi mriedem: yes, the evac patch conflicts on the file ending
15:16:23 gibi mriedem: master has test_resize_not_enough_resource at the end
15:16:35 gibi mriedem: but Jay's branch doesn't contain that
15:17:19 gibi mriedem: I will have no time today to do the evac fix in the init_host so if this is important somebody can take over. But tomorrow I can continue
15:17:53 openstackgerrit Sylvain Bauza proposed openstack/nova master: Make compute log less verbose with allocs autocorrection https://review.openstack.org/492571
15:18:09 bauzas mriedem: HTH ^
15:18:14 openstackgerrit Dmitry Tantsur proposed openstack/nova master: Deprecate bare metal filters https://review.openstack.org/492563
15:19:34 dtantsur bauzas, mriedem, easy win for your review stats ^^ (like if you needed more, heh)
15:21:16 gibi mriedem, dansmith: I think this is ready to go in, Jay was +2 already but I needed to rebase: https://review.openstack.org/#/c/491529/
15:22:06 jaypipes gibi: hey, there's an urgent request for your assistance here: http://lists.openstack.org/pipermail/openstack/2017-August/045339.html
15:26:02 gibi jaypipes: seems like s spam :)
15:27:11 mriedem bauzas: sdague: melwitt: i triaged https://bugs.launchpad.net/nova/+bug/1709594
15:27:13 openstack Launchpad bug 1709594 in OpenStack Compute (nova) "live-migration without '--block-migrate" failed with "No sql_connection parameter is established"" [High,Triaged]
15:27:18 mriedem it's a superconductor issue,
15:27:27 mriedem the xenapi driver tries to get host aggregates during a live migration,
15:27:32 mriedem and the aggregates are in the API DB now,
15:27:36 jaypipes gibi: was just joking you.
15:27:43 mriedem so this is an upcall attempt from the compute service, in a cell with no access to the api db
15:28:07 gibi jaypipes: ohh. OK. You got me :)
15:34:04 mriedem gibi: i think we could deal with the source allocation cleanup bug as a backport
15:39:35 gibi mriedem: ack
15:41:11 mriedem it's only a problem unless the compute comes back online
15:41:21 mriedem s/unless/until/
15:44:07 ioggstream mriedem: +1 [stack@c1f-ops-dirp00 openshift-on-openstack]$ o server group create deleteme-sg-3 --policy soft-anti-affinity --os-compute-api-version 2.15
15:44:22 sdague mriedem: good call
15:46:42 mriedem ioggstream: cool
15:49:30 openstackgerrit Spencer Yu proposed openstack/python-novaclient master: Nova client should retry with Retry-After value https://review.openstack.org/447766
15:49:52 mriedem ioggstream: going to update that bugzilla?
15:50:03 mriedem btw, it's nice to see my ibm red hat bugzilla account is still active
15:50:07 mriedem and has permissions to ibm bugs
15:51:00 ioggstream mriedem: yes, I'll do it. I've an rh account: I'll try with it.
15:51:30 ioggstream mriedem: my issue is now that heat doesn't seem to support soft-anti-affinity
15:52:35 bauzas dtantsur: edleafe: I'm confused by the ironic upgrade path (see https://review.openstack.org/#/c/492563/2)
15:52:56 bauzas dtantsur: edleafe: we could potentially have old ironic nodes to schedule with a pike scheduler
15:53:12 dtantsur bauzas: well, we're not removing anything, are we?
15:53:23 bauzas dtantsur: sure, but you send a signal with those deprecations
15:53:38 bauzas I just don't want operators to freak out
15:53:39 dtantsur well, in Queens the old style of scheduling is not going to be possible
15:53:46 dtantsur we have to send some signal about that coming
15:54:00 bauzas so it's just a wording issue
15:54:26 dtantsur re upgrade https://docs.openstack.org/ironic/latest/admin/upgrade-guide.html#upgrading-from-ocata-to-pike
15:54:41 dtantsur we should change s/recommended/required/, I'm going to have another update anyway
15:54:52 bauzas but the point is, if you deprecate in Pike, that means you accept operators to not use those opts by the Pike timeframe, which could be a bit of concern if they roll out upgrades
15:55:06 bauzas dtantsur: I briefly looked at your relnotes too
15:55:24 bauzas dtantsur: and haven't found any clear ask for providing resource classes for nodes
15:55:37 dtantsur bauzas: this is coming as part of https://review.openstack.org/#/c/491773/
15:55:37 bauzas (talking of https://docs.openstack.org/releasenotes/ironic/unreleased.html )à
15:55:42 bauzas ah cool
15:56:06 bauzas dtantsur: so I guess some linkage between relnotes could be appreciated
15:56:21 bauzas like, ironic has to be upgraded before compute nodes obviously
15:56:35 bauzas but ironic can be upgraded after placement and scheduler, right
15:56:48 dtantsur I guess so, yeah
15:57:14 bauzas and before you run a fresh pike nova-compute, you have to update your ironic cloud to set the resource classes
15:57:29 bauzas that is the upgrade ordering I care, since operators would query for
15:57:30 dtantsur right, we can do it while still running Ocata
15:58:18 dtantsur should this patch be finished today? I have meetings, then I'd prefer to bail out (I'm in EU time)
16:00:22 bauzas dtantsur: you mean the notes ?
16:00:48 ildikov mriedem: quick meeting if you're available
16:00:57 dtantsur bauzas: this nova patch
16:01:10 bauzas dtantsur: well, mriedem will cut the rc1 tag tonight for us (as well, I'm CEST) so that would mean those notes would require a backport if we want them in the pike tree
16:01:39 dtantsur this sounds like "today"..
16:01:57 dtantsur edleafe: is it possible you take on fixing release note wording for ^^^?
16:02:10 bauzas dtantsur: ideally, I'd have appreciated to see https://review.openstack.org/#/c/491773/ landed first, but I guess we need to send them concurrently to the gate
16:03:04 dtantsur bauzas: ironic is not branched today, so it may wait a bit, I think
16:03:14 edleafe bauzas: dtantsur: I'll review after API-WG meeting
16:03:19 dtantsur cool
16:03:30 bauzas dtantsur: oh right, not the same cadence than us
16:03:51 bauzas well, I can push a new rev
16:04:00 bauzas edleafe: ^
16:04:01 dtantsur if you don't mind!
16:04:16 edleafe I never mind
16:04:20 edleafe :)
16:06:03 mriedem pushing what now?
16:06:13 mriedem we already have stuff in the nova release notes that say ironic gets upgraded before nova
16:06:18 mriedem for some unrelated features, like boot from volume
16:06:26 mriedem we don't need to say that 5 times
16:07:10 bauzas mriedem: context is https://review.openstack.org/#/c/492563/
16:10:12 edleafe mriedem: it's the sixth time that will sink in
16:13:35 dtantsur edleafe, bauzas: updated ironic part (docs and reno)
16:13:47 dtantsur wording suggestions are welcome, my wording can be awful sometimes
16:14:07 mriedem this doesn't have to be done in pike does it?
16:14:18 mriedem seems like too many moving parts
16:14:21 dtantsur mriedem: these filters won't work in Queens, no?
16:14:33 mriedem idk
16:14:37 mriedem i just,
16:14:58 mriedem i can only have my head wrapped around 10 different RC1 stop ship omfg blocking issues at one time

Earlier   Later