07:20:01 <prometheanfire> #startmeeting requirements
07:20:02 <openstack> Meeting started Wed Nov 22 07:20:01 2017 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:20:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:20:06 <openstack> The meeting name has been set to 'requirements'
07:20:19 <prometheanfire> ping tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis
07:20:25 <prometheanfire> #topic roll-call
07:20:27 <prometheanfire> o/
07:21:21 <tonyb> Oh today? man I'm confused
07:22:50 <prometheanfire> tonyb: yep, todays wednesday right?
07:22:51 <dirk> o/
07:23:27 <tonyb> prometheanfire: Yeah somehow I had it in my head that we moved to Thursday I don't knwo why
07:23:44 <dirk> Except for prometheanfire , I think he's still on Tuesday?
07:23:55 <prometheanfire> nah, 1:23 am here
07:24:06 <prometheanfire> ok
07:24:08 <prometheanfire> #topic Any controversies in the Queue?
07:24:26 <prometheanfire> I don't think so
07:24:41 <dirk> Any comments on the lower-constraints stuff?
07:24:53 <prometheanfire> dirk is doing good work on the zuul stuff still :D
07:25:08 <dirk> I think i screwed up the last revision but before it was passing
07:25:35 <dirk> I would like to add a devstack run now against LC
07:25:37 <tonyb> dirk: I haven't looked yet :(
07:25:50 <prometheanfire> tonyb: we need your depsolver as well :p
07:26:36 <dirk> tonyb: another, unrelated one for you: https://review.openstack.org/518448
07:26:48 <dirk> See referenced bug report
07:27:00 <tonyb> prometheanfire: It is true, It's on my todo list (to clean it up) but it wont happen this month
07:27:04 <prometheanfire> but as far as the lower-constraints stuff, looks ok
07:27:06 <dirk> I haven't tested that change myself yet
07:27:11 <prometheanfire> tonyb: christmas present then :D
07:27:24 <tonyb> prometheanfire: :)
07:27:58 <tonyb> dirk: okay I'll look at that.  I confess I'm confused why this is a problem now, IIRC it only came up with $project was only half doign requirements management
07:28:56 <dirk> tonyb: it might be a Problem for some longer time already
07:29:31 <dirk> It's just that a coworker now discovered it, but Am almost sure it was lurking for a while
07:29:56 <dirk> One thing I noticed is that we don't add constraints for py36
07:30:13 <prometheanfire> we don't test it either iirc
07:30:15 <tonyb> dirk: but doesn't pulling stuff from git violate the main idea of requirements?
07:30:34 <prometheanfire> tonyb: even if it's a sha?
07:30:39 <dirk> tonyb: ceilosca is weird
07:30:41 <tonyb> It can't be, deterministicly, coinstallable if it's from git
07:31:00 <dirk> tonyb: it's basically a patch on top of ceilometer
07:31:01 <tonyb> prometheanfire: but that isn't representable in u-c
07:31:19 <dirk> It's not using it as a python2 module
07:31:30 <prometheanfire> hmm
07:31:34 <tonyb> dirk: but how is in fundamentally different from neurton or horizon?
07:31:49 <prometheanfire> tonyb: in that case ya...
07:32:13 <dirk> tonyb: they don't hardcode the Sha maybe?
07:32:42 <dirk> I need to look at it in more detail. That patch was only the first shot after a few min
07:32:54 <prometheanfire> pip install git+git://github.com/aladagemre/django-notification.git@2927346f4c513a217ac8ad076e494dd1adbf70e1
07:32:57 <dirk> I was hoping someone else would test it
07:33:19 <prometheanfire> not sure about reqs.txt
07:33:27 <tonyb> prometheanfire: nope, https://github.com/openstack/monasca-ceilometer/blob/master/test-requirements.txt#L2
07:34:01 <prometheanfire> well, they are not pointing to a sha
07:34:06 <prometheanfire> that should be rejected
07:34:39 <tonyb> dirk: my issue is that with your chnage we then will allow nova to add git+hhtps://some.random.server/aweome/lib
07:34:47 <tonyb> and we'll never see it as a problem
07:35:15 <tonyb> What they're doign is fine for them but they're not managed so they shoud just switch the job to non-voting
07:36:30 <prometheanfire> ya, without enforcement of at least a sha (tags could be redefined) I don't like it
07:36:34 <tonyb> *if* ceilometer were on pypi we could just list it which is a thing we're trying to get to but there are challenges
07:36:47 <dirk> tonyb: good point
07:39:24 <tonyb> so I guess pause to reflect and discuss again next week?
07:39:40 <dirk> +1
07:39:50 <prometheanfire> ya, I changed my vote for now, but sounds good
07:39:54 <dirk> I think won't fix might be the right answer
07:40:33 <prometheanfire> # other items (closed discussion)?
07:40:36 <prometheanfire> #topic other items (closed discussion)?
07:41:48 <prometheanfire> if nothing else I think it's time for open discussion
07:42:22 <tonyb> +1
07:42:43 <dirk> I have no other times
07:43:04 <prometheanfire> #topic open discussion
07:43:09 <prometheanfire> for a min then close
07:43:20 <dirk> other than I might be adding a tw py36 job (non-voting) at some point in the future
07:43:27 <dirk> when infra merges the depending patchsets
07:43:32 <tonyb> dirk: cool
07:43:38 <dirk> this way we can run a bit against python 3.6 and find new problems
07:43:51 <tonyb> dirk: If you do that you'll need to massgae u-c to include py3.6
07:44:08 <dirk> tonyb: yeah, was looking at that
07:44:12 <prometheanfire> that sounds fine, my main question is what OS?
07:44:18 <tonyb> otherwise u-c will ignore you and you'll get $latest versions for stuff
07:44:19 <dirk> Opensuse
07:44:23 <prometheanfire> is 18.04 defaulting to it?
07:44:28 <tonyb> tw == tumbleweed
07:44:29 <prometheanfire> that works too :D
07:44:37 <tonyb> prometheanfire: Yeah we'll get it then alos
07:44:49 <prometheanfire> ah, thought they were sticking with 3.5
07:44:51 <dirk> I am not sure, but it seems likely that Ubuntu updates to that version as well
07:44:54 <prometheanfire> nice to hear, 3.6 is awesome
07:45:31 <dirk> Yep, first one that is actually faster than py27 ;-)
07:45:42 <prometheanfire> lol
07:45:49 <prometheanfire> just use pypy
07:46:03 <prometheanfire> #endmeeting