Wednesday, 2016-07-06

-openstackstatus- NOTICE: All python 3.5 jobs are failing today, we need to build new xenial images first.06:28
openstackgerritOpenStack Proposal Bot proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/33638906:46
openstackgerritMerged openstack/requirements: Add python-watcherclient to global-requirements  https://review.openstack.org/33774207:12
*** jpena|off is now known as jpena07:13
openstackgerritMerged openstack/requirements: Updated from global requirements  https://review.openstack.org/33733307:23
*** coolsvap has joined #openstack-requirements11:05
coolsvapprometheanfire, sigmavirus_away i am available for today's meeting11:14
openstackgerritThomas Bechtold proposed openstack/requirements: Add networking-cisco to the projects list  https://review.openstack.org/33820511:46
coolsvaptoabctl, the check-requirements job is non voting in networking-cisco11:54
coolsvapI dont know how we can conduct meeting today if we have spamming in #openstack-meeting11:54
coolsvaptonyb prometheanfire number80 sigmavirus_away dims coreycb` dirk ^^11:55
coolsvapanyone around?11:57
number80ack11:58
toabctlack11:58
number80coolsvap: if openstack bot was here, we could have done it here11:58
coolsvapnumber80, yes11:58
coolsvapi have pinged in infra11:59
coolsvapbut there is no response yet11:59
coolsvapwe have openstack bot here though11:59
number80right, I missed it11:59
number80well, let's just do it here12:00
coolsvapI am not sure if we can start meeting here?12:00
number80we won't disturb anyone12:00
coolsvaptonyb, can we start meeting here?12:00
coolsvapnumber80, should i just try to start here?12:01
coolsvaptoabctl, dirk prometheanfire ^^12:01
number80coolsvap: I'm for it until we fix spam issue12:01
coreycb`coolsvap, sounds good to me12:01
prometheanfirecoolsvap: I thought we had it in #openstack-meeting?12:01
coolsvapprometheanfire, there is a spam attack12:02
coolsvapi am starting meeting here12:02
coolsvap#startmeeting requirements12:02
openstackMeeting started Wed Jul  6 12:02:22 2016 UTC and is due to finish in 60 minutes.  The chair is coolsvap. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
openstackThe meeting name has been set to 'requirements'12:02
coolsvap#topic rollcall12:02
prometheanfireah12:02
number80o/12:02
coreycb`o/12:02
prometheanfireo/12:02
coolsvappoeple we have a spam attack in #openstack-meeting so we have started meeting here12:03
coolsvapI am not sure if it will be recorded or not12:03
number80coolsvap: it will be12:03
coolsvapif not i will send the log to mailing list12:03
coolsvapalright lets see number8012:04
coolsvap#topic Any controversies in the Queue?12:04
coolsvapI think we have a lot to discuss here today12:04
coolsvap#link https://review.openstack.org/335455/12:04
prometheanfirethe bump of oslo-concurrency in liberty for a sec bug12:04
coolsvapprometheanfire, alright lets go ahead12:05
coolsvapi was putting some reviews in master12:05
prometheanfirecoolsvap: you linked first :P12:05
coolsvapi will come back to it again12:05
coolsvapstable first12:05
prometheanfire#link https://review.openstack.org/33727712:05
coolsvapprometheanfire, can you provide a link?12:05
coreycb`I have to agree with tonyb on that one, I'm -1 until we know it's the last resort12:06
number80-1 too12:06
prometheanfirethe problem is that raising the version of olso-conc there will also make us raise the version of other things (oslo utils being the first)12:06
prometheanfiremy +1 was only from the perspective of a distro person, from a reqs perspective it's not fun12:07
number80I think we need to define and set a policy for security-related bumps12:07
number80yeah, as a downstream, I already did the update12:08
prometheanfireya, I target upper-constraints already12:08
number80but I can imagine other people trying to be more conservative and backport security patches12:08
coreycb`same here, as much as possible we target u-c12:08
coreycb`it seems like there should be a way to backport to 2.3.112:09
prometheanfireya, it's fair to try and really push for that12:09
number80*nods*12:10
coolsvapcoreycb`, can you add a review comment with your view?12:11
coreycb`coolsvap, yes I already did12:11
prometheanfireya, I should add another comment as well, clarifying my views12:11
coolsvapcoreycb`, missed it sorry thanks12:11
coolsvapprometheanfire, yes please12:12
coreycb`apevec said it's not possible because stable/liberty was at 2.6.0, but I don't think that's a good enough argument12:12
coreycb`it's just a tag in git12:12
number80well, we also have to accomodate stablemaint constraints in this case12:13
prometheanfiretrue12:13
number80maybe they'd be ok to push it as a hotfix release?12:14
prometheanfireit'd be nice12:14
coreycb`ok rookie question, can you fill me in on where to view stablemaint constraints?12:15
prometheanfirehttp://docs.openstack.org/project-team-guide/stable-branches.html12:16
prometheanfire#link http://docs.openstack.org/project-team-guide/stable-branches.html12:16
coolsvapwe need someone to check for update related to hotfix or something to work with, dhellmann dims?12:16
coreycb`ah you're talking about support phases12:16
number80we can ask apevec, he's part of stablemaint too12:18
coolsvapnumber80, can you update team and review related to your discussion with apavec?12:18
coolsvapalright12:21
coolsvapi think we need to sync with tonyb about next steps or any of the stable cores regarding next steps12:21
coolsvap#action sync up with tonyb about next steps or any of the stable cores regarding next steps12:21
coolsvapmoving on12:22
coolsvapwe have to decide upon policy to allow requirements with similar functionality but with different attributes like performance12:23
*** jpena is now known as jpena|lunch12:23
coolsvapwe have couple of reviews related to it in the queue12:23
coolsvap#link https://review.openstack.org/33768312:24
coolsvapam I disconnected?12:24
prometheanfireya, similliarlly we just merged another json lib12:25
prometheanfirecoolsvap: no :P12:25
prometheanfirethe new json lib is cython and quicker as well12:25
coolsvapprometheanfire, thanks for the ack I think we need to decide on policy for it12:26
number80coolsvap: ack12:26
coolsvapI think if the library has promising attributes over the previous one with better support on distros12:26
coolsvapwe should be more accommodating on adding these12:26
number80well, I'd like more concrete arguments than "it's faster"12:26
number80not against it, just allow flexibility to distro12:27
number80for instance hiredis can be an optional deps as redis-py will use its parser when installed and benefit from perf bumps12:27
coolsvapnumber80, agreed but most will come with that attribute (being faster than previous one)12:27
prometheanfiretracking it in UC would help as a packager, we basically do so for the entire python dep tree12:27
number80proposal: having an optional-requirements12:27
number80we can these in optional-requirements12:28
prometheanfirefor anything 'plugin' related?12:28
number80stuff that are not required for runtime but could provide additional nice feeature12:28
number80prometheanfire: depends on plugin definition :)12:28
coolsvapnumber80, agree but we need some mechanism to manage that across projects12:29
prometheanfiremight work, but would need to verry strictly define what optional means12:29
number80Yes12:29
prometheanfirewhich projects get to define what's optional12:29
prometheanfireI would think the project that submitted this would think it's not optional12:30
coolsvapnumber80, can you draft something which we can discuss12:30
coolsvap#link https://etherpad.openstack.org/p/optional-requirements-draft12:30
number80coolsvap: will do12:30
coolsvapjust created a etherpad for the same12:30
coolsvapnumber80, thanks12:30
prometheanfireaction for it?12:31
coolsvap#action number80 to draft optional-requirements to discuss in next meeting12:31
number80but for immediate purpose, if the guys offers concrete data that hiredis is necessary for their workflow, I'm not against adding it12:31
number80thanks12:31
coolsvapanything else in the queue?12:32
prometheanfireya, I'm ok with it, generally12:32
prometheanfirenothing else controversial I think12:32
number80*nods*12:32
coolsvapmoving on12:33
coolsvap#topic Additional Gating - Updates12:33
coolsvapprometheanfire, any updates related to it?12:33
prometheanfirenot at the moment12:34
coolsvapprometheanfire, np I just added it to recurring meeting topic12:35
coolsvapI was about to say no update is just as valid as any other update12:35
prometheanfirethat's fine, real life has been busy for the last month and will be for the next couple weeks12:36
prometheanfireI have a recouring reminder that I need to get more details on it, so it won't be forgotten though12:36
coolsvapprometheanfire, np it was action item for you and tonyb and I think review https://review.openstack.org/#/c/333650/ in good shape12:37
coolsvap#link https://review.openstack.org/#/c/333650/12:37
coolsvapmoving on12:37
coolsvap#topic Tasks from Etherpad12:37
prometheanfiresure12:37
coolsvapanyone has any updates related to tasks from etherpad12:37
coolsvapwe already covered the gating part12:37
coolsvap#link https://etherpad.openstack.org/p/requirements-tasks12:38
coolsvapI think we can move on the topic with no updates this week.12:40
coolsvap#topic Volunteer for next 2 meetings12:41
coolsvap#info prometheanfire is running the meeting on 13 July12:41
coolsvapAny volunteer for July 20 meeting?12:41
coreycb`coolsvap, I can take that one12:41
coolsvapcoreycb`, thanks12:42
coolsvap#info coreycb  is running the meeting on 20 July12:42
coolsvap#topic Open Discussion12:43
coolsvapI think we call the meeting here12:45
prometheanfiresgtm12:45
coolsvapprometheanfire, number80 coreycb` ^^12:45
coolsvapalright12:45
coreycb`coolsvap, I don't have anything else12:45
coolsvap#endmeeting12:45
openstackMeeting ended Wed Jul  6 12:45:50 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-07-06-12.02.html12:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-07-06-12.02.txt12:45
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-07-06-12.02.log.html12:45
coreycb`thanks coolsvap12:45
coolsvapThank you everyone12:46
prometheanfirecya next week12:46
coolsvapI am happy that we have the meeting log12:46
number80coolsvap: thank you for running the meeting :)12:46
coolsvapI might not be present for next week meeting12:46
coolsvapI thought about today's meeting last week12:47
coolsvaplets see :)12:47
toabctlthx coolsvap12:47
prometheanfire:P12:47
coolsvapsee you all around12:47
*** sigmavirus_away is now known as sigmavirus13:24
*** jpena|lunch is now known as jpena13:35
*** coreycb` has quit IRC13:38
*** coreycb has joined #openstack-requirements13:38
*** rbrndt has joined #openstack-requirements13:59
prometheanfireI know we talked about it before, but doug's submissions are only to verify single changes are good (pass tests), we still prefer to wait for the daily mass generate-constraints update?15:37
openstackgerritDavid TARDIVEL proposed openstack/requirements: Add watcher-dashboard project to projects.txt  https://review.openstack.org/33758515:56
openstackgerritMerged openstack/requirements: Add --save option to normalize-requirements command  https://review.openstack.org/33316716:29
coolsvapprometheanfire, i agree i think we had a lot of discussion about it in meetings16:40
coolsvapwe need more people to look at the dims u-c constraint test patches16:41
coolsvapand triggering them as needed16:41
prometheanfireok, that's why I haven't been +2ing them16:45
coolsvapprometheanfire, its alright if people +2/+1 them we need to make sure they are not merged16:47
coolsvapwe only merge the generated from *** patches16:47
coolsvapfor bot patches16:47
prometheanfireyarp16:48
*** jpena is now known as jpena|off17:10
openstackgerritMerged openstack/requirements: Add monasca-api to projects.txt  https://review.openstack.org/33661117:35
openstackgerritMerged openstack/requirements: Add monasca-persister to projects.txt  https://review.openstack.org/33661417:35
openstackgerritKaiyan Sheng proposed openstack/requirements: Add monasca-statsd to projects.txt  https://review.openstack.org/33842417:47
openstackgerritRick Aulino proposed openstack/requirements: Bump global-requirements.txt for Elasticsearch python client to 2.3.0.  https://review.openstack.org/33842517:48
openstackgerritKaiyan Sheng proposed openstack/requirements: Add monasca-notification to projects.txt  https://review.openstack.org/33843818:08
*** sigmavirus is now known as sigmavirus_away21:52
*** david-lyle_ has joined #openstack-requirements22:21
*** david-lyle_ is now known as david-lyle22:35
*** rbrndt has quit IRC22:55

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!