17:00:10 <alaski> #startmeeting nova_cells
17:00:11 <openstack> Meeting started Wed Sep  9 17:00:10 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:16 <openstack> The meeting name has been set to 'nova_cells'
17:00:31 <alaski> good <regional time of day> everyone
17:00:39 <bauzas> \o
17:00:48 <lalit_d> \o
17:00:55 <bauzas> mornooning
17:01:04 <alaski> bauzas: :)
17:01:22 <alaski> #topic Tempest tests
17:01:26 <vineetmenon> o/
17:01:55 <alaski> there were a few issues with testing recently
17:01:57 <belmoreira> o/
17:02:13 <alaski> but afaik it came down to tempest test names changing
17:02:20 <bauzas> yup
17:02:23 <alaski> and therefore bypassing the blacklist that was setup
17:02:56 <bauzas> that's why I'm working on directly providing the Devstack changes :)
17:03:13 <alaski> the tempest feature flags?
17:03:51 <bauzas> yup
17:04:02 <alaski> awesome
17:04:03 <belmoreira> alaski: is this related with the failures in 213041 and 201606
17:04:10 <lalit_d> alaski: https://review.openstack.org/#/c/213041 in this patch some tempest and grenade tests were failing
17:04:10 <bauzas> it needs to modify a bit Tempest as well
17:04:53 <alaski> belmoreira: lalit_d doesn't look like it.  it was the gate-tempest-dsvm-cells job that was failing
17:05:13 <alaski> bauzas: okay
17:05:22 <bauzas> alaski: +1
17:05:40 <alaski> that seems like an effort that we could have multiple people on
17:05:48 <bauzas> lalit_d: the bug alaski was talking was https://bugs.launchpad.net/nova/+bug/1492255
17:05:49 <openstack> Launchpad bug 1492255 in OpenStack Compute (nova) "Cells gate job fails because of 2 network tests" [Critical,Fix committed] - Assigned to Sylvain Bauza (sylvain-bauza)
17:06:06 <bauzas> alaski: yeah, just trying to look first
17:06:37 <belmoreira> alaski: we don't understand why those patches are failing... we may need some help
17:07:00 <bauzas> belmoreira: are you sure it's coming from your side?
17:07:20 <lalit_d> bauzas: ok
17:07:24 <alaski> bauzas: okay.  if you could use help let me know and I'll see if we can get people involved
17:07:37 <alaski> belmoreira: okay.  the ironic-pxe failure is unrelated
17:07:46 <bauzas> alaski: for the moment, I'm reviewing the Tempest tests to see which features are having a flag
17:07:47 <belmoreira> I believe not... that's why it is more difficult for us
17:07:50 <alaski> not sure on the grenade one right now, but I can take a look
17:08:10 <bauzas> alaski: I should write an etherpad so any people could see which tests would need which flags etc.
17:08:16 <alaski> bauzas: +1
17:08:28 <bauzas> okay, paperwork time !:
17:08:29 <bauzas> :p
17:08:58 <bauzas> alaski: sounds a low-hanging-fruit also
17:09:09 <alaski> yeah
17:09:23 <bauzas> alaski: I should ask the Upstream Training to see if some people would want to help us
17:09:46 <alaski> that would be great.  they're good simple changes
17:09:53 * bauzas has some thoughts on that
17:10:10 <alaski> I think we've got testing covered for now
17:10:15 <alaski> #topic Open Reviews
17:10:24 <bauzas> I was actually running the Upstream Training for the last 2 cycles but this cycle I can't (Tokyo with family) but surely I can ask
17:10:31 <alaski> there are some reviews still listed on the agenda at https://wiki.openstack.org/wiki/Meetings/NovaCellsv2
17:10:37 <alaski> however we're in feature freeze
17:11:03 <bauzas> alaski: one remaning point about testing, but can be discussed during opens
17:11:05 <alaski> so reviews are still helpful, but the focus is going to be on bugs for a bit
17:11:11 <alaski> bauzas: okay
17:11:14 <bauzas> (open discussion)
17:11:25 <belmoreira> alaski: ok
17:11:45 <bauzas> alaski: I guess all the changes are in the etherpad of doom ?
17:12:01 <bauzas> alaski: I mean https://etherpad.openstack.org/p/liberty-nova-priorities-tracking ?
17:12:05 <alaski> bauzas: I believe so.  I added them a bit ago
17:12:20 <alaski> yeah, they're there
17:12:23 <bauzas> belmoreira, lalit_d: see above, if you feel some change is missing
17:12:25 <bauzas> coolness
17:13:24 <alaski> once RC1 is picked and there are no critical bugs coming up we can get back to pushing on these features again
17:13:32 <belmoreira> bauzas: is good
17:13:47 <alaski> but for now reviews will be slow on features
17:14:02 <alaski> #topic Open Discussion
17:14:15 <belmoreira> alaski: do we need to submit again the flavor spec for M?
17:14:27 <bauzas> belmoreira: I guess thru a fast-approval, yes
17:14:29 <alaski> belmoreira: yes.  but it can be approved quickly
17:15:01 <belmoreira> I would like to continue with the work during this period
17:15:19 <belmoreira> is ok if we continue to update the patch?
17:15:19 <bauzas> belmoreira: you still can, that's just for merging :)
17:15:26 <alaski> belmoreira: okay.  we can't merge it but you can keep working
17:15:57 <alaski> bauzas: you had a thing for open discussion?
17:15:57 <bauzas> so I had one point
17:16:03 <bauzas> yeah
17:16:11 <belmoreira> my question is: should we continue work in the same patch or because we need a new spec we also need to resubmit the patch?
17:16:19 <alaski> belmoreira: same patch is good
17:16:31 <belmoreira> alaski: thanks
17:16:32 <alaski> the -2 will go away after feature freeze
17:16:43 <belmoreira> great
17:16:45 <bauzas> so we have an exception raising on the cell-parent
17:16:58 <bauzas> that's confusing for people troubleshooting cells
17:17:26 <bauzas> I'm trying to tackle the issue in https://review.openstack.org/#/c/218473/ and some other DNM change
17:18:01 <bauzas> since it's pretty hard to trace why, I wonder by how much we should just catch the exception and leave with it
17:18:03 <alaski> https://review.openstack.org/#/c/220666/
17:18:29 <alaski> bauzas: right now I'm of the opinion that we just catch it
17:18:29 <bauzas> alaski: yeah, that one just shows up that there is a problem when saving
17:18:44 <lalit> alaski: in https://review.openstack.org/#/c/213041 gate-grenade-dsvm  and gate-grenade-dsvm-partial-ncpu are failing .. do you have any idea
17:18:51 <bauzas> alaski: so, there is a problem, but I wonder whether it's good to hide it
17:19:04 <alaski> lalit: I don't right know.  I will need to take a look
17:19:17 <bauzas> lalit: I gonna look at those once we're done, okay?
17:19:25 <bauzas> oh that too ^
17:19:32 <alaski> bauzas: the db change that caused the exception is just exposing a problem that already existed
17:19:39 <bauzas> alaski: zactly
17:19:43 <alaski> so I don't think the problem is new, just the exception
17:19:47 <bauzas> alaski: +1
17:20:08 <bauzas> alaski: but you know, that's far different from pretending it never existed :p
17:20:17 <alaski> definitely
17:20:28 <alaski> I think a log would be great there, instead of the exception
17:20:50 <bauzas> so, we can just throw the exception under the bus and leave with it, that just means that we know that we have a problem but we assess it's not easily fixable
17:21:02 <bauzas> alaski: sounds a good idea
17:21:42 <alaski> well, it's likely that it isn't easily fixable.  since it's cells and all :)
17:21:44 <bauzas> we're just in StringFreeze, so that would defer to Muppet, but I'm fine with that
17:22:01 <alaski> logging may help us narrow down the cause though
17:22:14 <alaski> bauzas: I think johnthetubaguy just sent out something saying that new logs are fine
17:22:24 <alaski> modifying logs is more of the issue
17:22:42 <bauzas> alaski: well, I did read johnthetubaguy's new rule of world, but I probably missed that - I thought it was only for bugfixing
17:23:12 <alaski> #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/073942.html
17:23:25 <bauzas> meaning that fixing a bug is far more important than just leave the bug because of i18n, which I +1 on that
17:23:58 <bauzas> hah "Additional strings are generally OK"
17:24:03 <lalit> alaski: okay, regarding removing the soft delete. in model_query itself unknown column for delete exception is raising which is before result..can you suggest for further proceed
17:24:05 <bauzas> bauzas: typey typey
17:24:08 <alaski> yeah.  it seemed pretty general to me
17:24:20 <alaski> lalit: I commented on the review
17:25:43 <alaski> lalit: basically, for now I think we do need to keep soft-delete
17:25:54 <alaski> anything else for today?
17:26:17 <lalit> alaski: ok thanks
17:26:33 <alaski> lalit: np
17:27:05 <alaski> thanks everyone
17:27:14 <alaski> #endmeeting