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