07:00:00 #startmeeting requirements 07:00:01 Meeting started Wed Jan 24 07:00:00 2018 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:00:05 The meeting name has been set to 'requirements' 07:00:10 #topic rollcall 07:00:12 tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis 07:00:16 ping 07:00:26 o/ 07:02:09 o/ 07:02:49 well, long enough 07:02:58 #topic controversies in the Queue? 07:03:00 coolsvap: I believe for removing msgpack-python a pure recheck isn't enough 07:03:36 was going to bring it up in bugs, but ya, that's the only outstanding thing 07:03:38 Well, the g lower-constraints patch:-) 07:03:56 dirk: okay, I thought it was working prev, unfortunately I cannot look at log.o.o from my work 07:04:01 not sure that's needed for the freeze :p 07:04:26 And 2nd related question is whether we want to consistently bump mins of oslo* or the like 07:04:59 I believe last cycle I discovered that the mins weren't really correct anymore 07:05:22 I still don't get why we are doing a lower-constraints.txt in the requirements repo 07:05:23 (in the sense of resulting in a working devstack run) 07:05:29 where will it be used 07:06:12 Initially for the coinstallability test of the lower bounds 07:06:35 I agree that projects might have their own lower bounds for independent install 07:06:51 what about after initially 07:07:10 co-installability alone doesn't mean anything 07:07:21 I'd really like to add a devstack run on the mins 07:07:51 So that we see that the mins result in a working system 07:08:02 for what reason? openstack only has one constraints that are considered canonical 07:08:54 For non containerized systems we need to understand which are mins that the distribution needs to meet 07:09:31 so, it's just to keep our minimums honest? 07:09:35 Not all distro can freely bump versions of everything. So tjey don't always provide the uc 07:09:45 Version for Openstack 07:09:56 Most of it 07:10:12 yeah it also came during PTG 07:10:23 Of course one can argue that in times where cron gets containerized whether that is still a realistic assumption 07:10:46 But at least for my background it still is 07:10:52 I almost think we may need some governance guidance of some sort, I see your point, but this does extend what we say openstack supports 07:11:26 in any case, this first pass allows us to test the code that interacts with lower-constraints.txt 07:11:36 the code can be tested here for use in other projects 07:12:36 I think its pretty much similar to what we say with u-c, I guess 07:13:14 kinda, I think 07:13:30 anyway, this stage is fine, but what we say with this info is more unknown 07:13:57 prometheanfire: agreed 07:14:26 I'm fine with not changing whst we commit to for now 07:14:36 It just gives an option to do more 07:15:11 ok, anything else? 07:15:50 msgpack? 07:16:45 Will look at msgpsck latrr today's 07:16:54 I cannot comment on it, I cannot see the failure logs 07:16:58 ya, that's what I imagine 07:16:59 dirk: thanks! 07:17:09 I believe we might need some more releases to happen first 07:17:24 ok, next 07:17:35 #topic PTG 07:17:36 E.g. the rename needs to propagate via a release 07:17:56 ya, that's always a pain 07:18:15 removing caps is similiar 07:19:04 https://etherpad.openstack.org/p/rocky-PTG-requirements is where we are writing topics 07:19:24 our meeting time/room will be when we think it's a good time 07:19:29 #link https://etherpad.openstack.org/p/rocky-PTG-requirements 07:20:41 I suppose we should start putting topics there 07:21:06 the lower-constraints stuff and the per-project requirements should be diferent 07:22:28 anyway, moving on 07:22:43 #topic Open Discussion 07:24:34 nothing from my side atm 07:25:01 Me neither 07:25:29 ok, just adding stuff to the etherpad 07:25:34 gonna close this now :D 07:25:37 #endmeeting