Tuesday, 2016-09-06

*** armax has quit IRC02:13
prometheanfiretonyb: anything other than a feeling?02:20
tonybprometheanfire: Yeah Just documentingn it now02:21
tonybprometheanfire: Alos https://bugs.launchpad.net/openstack-requirements/+bug/162043602:21
openstackLaunchpad bug 1620436 in OpenStack Global Requirements "Constraints generation is NOT py35 ready" [Undecided,Confirmed] - Assigned to Tony Breeds (o-tony)02:21
tonybprometheanfire: tl;dr: we work on xenial by luck not design :(02:21
prometheanfireyep02:25
prometheanfireah, wonderful02:27
tonybprometheanfire: No idea how to fix it properly, I have a really gross hack but they real fix needs a node with py27, py34 and py3502:29
prometheanfiregentoo node? :P02:31
prometheanfirebut ya, the only issue I see is hardcoding UC to 3402:31
tonybprometheanfire: Yeah that's the hard one to fix02:33
prometheanfirehttps://launchpad.net/ubuntu/+source/python3.4/02:33
prometheanfireit's available, so that's good02:33
tonybstops on 'w' so it doesn't compile for 'x', I tried to find a py35 on trusty but the only repo I found set off my bogofilter02:34
prometheanfirehttps://launchpad.net/ubuntu/+source/python3.4/3.4.4-2ubuntu3 specifically02:34
prometheanfireI don't have an ubuntu 16.06 system handy atm02:36
prometheanfiredownloading now02:38
tonybprometheanfire: that's deleted :( https://launchpad.net/ubuntu/+source/python3.4/3.4.4-2ubuntu3/+publishinghistory02:39
prometheanfire:|02:40
prometheanfireI'm in image-create02:40
prometheanfireso I should be able to boot and test in a couple of min02:40
prometheanfireand we need to support python34 for mitaka and older?02:41
tonybYeah, but the old releases are less of an issue as we have stable branches there, so as long as there is at least one proposal node that still runs trusty we're okay02:43
prometheanfireso, new releases are supporting python3.4 and python3.5?02:45
prometheanfirealso, searched the repo and no python34 or 3.402:45
prometheanfirenewton (new releases)?02:45
tonybprometheanfire: I think offically we're only supporting Xenial which means py35 *but* not all teams/jobs are read for that in python3 so the reality is we need to work with 34 and 3502:47
prometheanfireok, ya02:47
prometheanfirenova for instance has py34 and 35 tests02:48
prometheanfireso, for py34 it sounds like we need to use trusty02:49
prometheanfireif we use system python02:49
prometheanfirenot sure if openstack should just switch to virtualenvs or not... (I like the idea at first thought)02:50
openstackgerritMatthew Thode proposed openstack/requirements: Use python3.5 to calculate freezes  https://review.openstack.org/36563603:06
prometheanfiretonyb: ^ I think we should take that and continue to work with infra on py34 issues.03:06
tonybprometheanfire: we03:09
prometheanfiretonyb: yes?03:09
tonybve talkded about it at simmits since Vancouver and the answer is always 'meh'03:09
prometheanfireah03:09
prometheanfirewell, now it's a bigger issue I think03:10
prometheanfireit could just be us that needs all the pythons on one node03:11
prometheanfirein which case we could probably ask for a custom image03:11
*** zhugaoxiao has quit IRC03:14
*** zhugaoxiao has joined #openstack-requirements03:14
tonybI'm not certain that a venv will really help us here.03:15
prometheanfiredo we REQUIRE py34 and py35 to be installed at the same time in the same system?03:15
prometheanfireI'm still trying to understand the issue03:15
tonybprometheanfire: the issue is that *some* projects are still gating on trusty and some are on xenial (and a few on both)03:18
tonybprometheanfire: this means that our constraints files need to be appropriate for all pythongs we use in our CI03:19
tonybso while we don't have a hard requirement on py34 and py35 it's somethign we have to live with for a while03:19
prometheanfireright03:19
tonybthe *best* way to do that is have python2.7, python3.4 and python3.5 binaries available, but that's not going to happen anytime soon so we need to come up with an appropriate fallbak03:20
prometheanfireso that means requirements (as a project) needs to run on/in py27/34/3503:20
tonybyeah03:20
prometheanfirewe also need to recieve updates to UC for each03:21
tonybs/recieve/generate/ but yes03:21
prometheanfireright03:21
prometheanfirewe may have to do what nova did and have a job per specific version of python03:21
prometheanfirefor our general gate that is03:21
prometheanfireas far as recieving updates go I'm not sure if that needs all three pythons available or not03:22
prometheanfireI don't think so, but that's a gut feeling03:22
tonybfor human initiated changes 'meh' what ever, but for the bot yes the *best* way needs all 3 binaries03:23
tonybprometheanfire: right now we can't gate on both trusty and xenial, but that's somewhat easy to fix03:23
prometheanfirewhy does the bot need all three?03:23
tonybbut 365636 needs twaeking to do that thing03:24
prometheanfiretonyb: ya, I'm aware of the trusty OR xenial issue03:24
prometheanfirethe easiest way (like you said before) was to just run python303:25
prometheanfireif that's ok with you I'll change refrences to 35 to that03:26
tonybprometheanfire: When we genterate the updates we do somethign like for python in python2.7 python3.4 ; do viritualenv -p $pyhton venv; ./venve/bin/pip install -r global-requirements; ./venve/bin/pip freeze >> fu; done ; merge fu03:26
prometheanfireah03:26
prometheanfireya, that would be a pain03:26
prometheanfireif we are doing virtualenvs anyway, can we just tell it to compile / install python34?03:27
tonybprometheanfire: Sure that's what I'm doing but feel free to do it also03:27
tonybprometheanfire: we *can* if there is no better way but the node this runs on is lon lived so we need to be careful03:29
prometheanfiredidn't know it was long lived03:29
openstackgerritMatthew Thode proposed openstack/requirements: Use python3 to calculate freezes  https://review.openstack.org/36563603:30
openstackgerritTony Breeds proposed openstack/requirements: Use python3 to calculate freezes  https://review.openstack.org/36563603:34
tonybJust re-wrords the commit message and adds a link to the bug03:34
prometheanfirek03:35
prometheanfireok, commented on bug my understanding of what needs doing03:37
prometheanfireanyway, probably going to bed soonish, so, nn for now03:42
tonybprometheanfire: cool, rest well03:43
openstackgerritJulian Edwards proposed openstack/requirements: Add new dependency statsd for oslo_middleware  https://review.openstack.org/36583703:43
prometheanfireok, voted on that one, now I sleep :D03:45
*** coolsvap_ has joined #openstack-requirements03:52
*** jamesd has joined #openstack-requirements04:32
*** rcarrillocruz has quit IRC06:02
openstackgerritMerged openstack/requirements: Use python3 to calculate freezes  https://review.openstack.org/36563606:06
odyssey4me@tonyb responded to your question in https://review.openstack.org/36130906:22
tonybodyssey4me: Thanks.06:24
odyssey4metonyb my concern with the liberty requirements changes is that we end up unwinding it and the whole thing unravels06:25
odyssey4methe ideal would have been to reduce the client versions instead of increasing lib versions I think - I guess liberty was a learning time for requirements & u-c06:26
tonybYeah, we still don't have a good gate for manual u-c bumps but we're working on it06:27
openstackgerritJulian Edwards proposed openstack/requirements: Add new dependency statsd for oslo_middleware  https://review.openstack.org/36583706:28
odyssey4methanks tonyb - let's see how that shakes out06:29
tonybodyssey4me: Yeah :)06:29
openstackgerritIhar Hrachyshka proposed openstack/requirements: Block oslo.db 4.13.1  https://review.openstack.org/36556507:07
*** jpena|off is now known as jpena07:08
openstackgerritOpenStack Proposal Bot proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/36476207:12
*** tsufiev_ is now known as tsufiev08:13
*** HenryG_ is now known as HenryG10:46
*** jpena is now known as jpena|lunch11:48
prometheanfiretonyb: busy?11:57
prometheanfireor, been busy11:58
prometheanfiredon't really have a question11:58
*** jpena|lunch is now known as jpena12:48
*** jpena is now known as jpena|off13:19
*** jpena|off is now known as jpena13:36
*** zigo has quit IRC14:25
*** zigo has joined #openstack-requirements14:32
*** zigo is now known as Guest3914714:33
*** Guest39147 has quit IRC14:39
*** zigo_ has joined #openstack-requirements14:42
*** zigo_ has quit IRC14:47
*** zigo_ has joined #openstack-requirements14:48
*** jpena is now known as jpena|away15:03
openstackgerritOpenStack Release Bot proposed openstack/requirements: update constraint for XStatic-smart-table to new release 1.4.13.2  https://review.openstack.org/36619415:14
*** zigo_ is now known as zigo15:20
*** armax has joined #openstack-requirements15:29
*** stevemar has quit IRC16:31
openstackgerritMerged openstack/requirements: Update requirements for project Karbor (Smaug)  https://review.openstack.org/35337117:02
*** armax has quit IRC17:11
*** armax has joined #openstack-requirements17:26
openstackgerritMike Fedosin proposed openstack/requirements: Add glare and its client to projects list  https://review.openstack.org/36628218:22
number80late requests :)18:31
prometheanfireyep, talking to him now18:31
prometheanfireI think we'll need to get it in18:31
prometheanfireso everything is coinstallable18:32
number80yep, I think it was an oversight, as glare comes from glance originally18:33
prometheanfireyep18:34
openstackgerritOpenStack Release Bot proposed openstack/requirements: update constraint for oslo.db to new release 4.13.2  https://review.openstack.org/36629819:15
openstackgerritMatthew Thode proposed openstack/requirements: Block oslo.db 4.13.0 and 4.13.1  https://review.openstack.org/36556519:21
*** coolsvap_ has quit IRC19:32
openstackgerritNikhil Komawar proposed openstack/requirements: Bump g-r python-glanceclient to 2.5.0  https://review.openstack.org/36063319:43
*** jpena|away is now known as jpena|off20:15
tonybprometheanfire: where's you discusiion with Mike? so I can read it and ask reasonable question (if I have any)?22:26
prometheanfirehe pm'd me22:27
prometheanfiretonyb: https://gist.github.com/prometheanfire/8012ab2ac0ca13cca8c27cabb804bf3922:28
tonybprometheanfire: Thanks.22:30
prometheanfireyarp22:34
prometheanfirehuh, my hero twice over https://i.imgur.com/7SZJubo.jpg22:35
prometheanfiretonyb: do projects updates care about which branch projects.txt is sourced from?22:37
prometheanfirewill removing a project from master (but remaining in mitaka) still deliver updates to the project that was removed from our mitaka branch to their mitaka branch?22:38
tonybprometheanfire: I don't follow your question but each branch is independant.  So there it doesn't matter if $project is in mitaka and newton but not in liberty or master (for a very strange example) ... does that help?22:40
prometheanfiretonyb: ok, so project foo will still get updates to mitaka if it is still listed in projects.txt in mitaka in requirements?23:29
tonybprometheanfire: Yup23:30
prometheanfirecool23:30
prometheanfireso I think glare would probably like to get into newton23:30
tonybprometheanfire: That's not clear from your conversation or from discussin it with the glance PTL23:33
tonybprometheanfire: we'll wait and see what the glare lead says when they wake up23:33
prometheanfireya, they have to initiate of course23:34
openstackgerritKirill Zaitsev proposed openstack/requirements: Bump minmal version of oslo.log to 3.11  https://review.openstack.org/36641823:56

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