15:01:34 #startmeeting neutron_upgrades 15:01:35 Meeting started Mon May 23 15:01:34 2016 UTC and is due to finish in 60 minutes. The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:36 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:38 The meeting name has been set to 'neutron_upgrades' 15:01:40 hello all 15:01:44 hi 15:02:04 rossella_s feels sick today, she won't join us 15:02:43 we don't have any action items from the last meeting. 15:03:03 #topic Partial Multinode Grenade 15:03:36 I am not aware of any progress made on that one, except the fact that we got rolling upgrades tag merged 15:03:38 #link https://review.openstack.org/#/c/286817/ 15:04:00 hello 15:04:06 generally, the next steps are documented in: 15:04:07 #link https://etherpad.openstack.org/p/neutron-multinode-jobs-newton 15:04:38 hmm I was thinking that rolling upgrades requires no downtime acenario 15:04:40 scenario* 15:04:54 korzen: no, it requires 'some form' of per-component upgrades 15:05:10 since we can upgrade agents independently of neutron-servers, it's enough 15:05:18 we just needed to prove that with gate jobs. 15:05:42 I believe if we need a tag for no-downtime, we would need to come up with a new one 15:05:59 that would require rolling-upgrades one but would add more requirements. 15:07:03 sc68cal: any progress around multinode grenade that I am not aware the last week? 15:07:09 ihrachys, have someone tried to introduce any breaking changes and run the grenade to see if it catch the bug? 15:07:43 korzen: nope. do I hear a suggestion to add an action item to your plate? ;) 15:08:15 ihrachys, I would be my pleasure 15:08:26 :) 15:08:44 #action korzen to send a breaking patch to validate multinode grenade job catches rolling breakages 15:08:48 thanks korzen! :) 15:09:03 #topic Object implementation 15:09:33 ok, on objects front, we are near merging allowed address pairs patch: https://review.openstack.org/#/c/287756/ 15:09:48 we also merged subnet object: 15:09:50 #link https://review.openstack.org/#/c/264273/ 15:10:05 we need to proceed with its adoption in the db code. 15:10:15 korzen: will you have time for that latter part? 15:10:33 obviously, I don't expect it to work on the first iteration due to missing sorting/pagination support in base object class 15:10:34 ihrachys, I'm already have some code 15:10:45 but it would be great to start digging to see what we miss 15:10:48 korzen: great! 15:11:07 I should have something to discuss bu the next meeting 15:11:11 for sorting/pagination support, we need: 15:11:22 1. expanded api test coverage for those features. first bit: https://review.openstack.org/#/c/306272/ 15:11:55 2. support for that in get_objects: https://review.openstack.org/#/c/300055/13 15:12:18 * ihrachys notes that the former has +2 but failed in gate, will investigate right after the meeting. 15:12:55 also, for all who help with the effort, pretty please, we need volunteers to cover more resources with sorting/pagination api tests 15:13:16 there is not much reason to spin on more new objects right now before we get this set in place 15:13:22 what should be the resources? 15:13:32 like subnet and port? 15:13:33 korzen: subnet, subnetpool, for one thing. 15:13:56 korzen: yes. any 1st class resource that can currently recieve sorting/pagination criteria 15:14:20 which is anything that is not a resource extension (like address pairs that are embedded into ports and hence are not fetched on their own) 15:14:36 (that's why we can move forward with address pairs but not e.g. subnets or subnetpools) 15:14:43 It seems like we are the only ones in the meeting right now ;) 15:15:03 korzen: that's what we have, sadly. 15:15:15 so I will just run it thru really quick. 15:15:37 ok, that was it for objects and generally on how to contribute to the effort in a more effective way. 15:15:47 #topic Open discussion 15:15:59 now it's time to raise patches/concerns. 15:16:38 I had some question but forgot what it was, nothing important I guesss 15:16:41 before someone asks to review a new object, please make sure you read above and understand it may not be the current burning thing and hence reviews can be delayed. 15:17:33 ok, I guess nothing burning apart from what was already covered. 15:17:55 we will shut it down shortly and give ourselves 40 mins to do some progress in code and reviews. 15:18:01 thanks korzen for joining 15:18:03 #endmeeting