Monday, 2015-12-21

*** haomaiwang has joined #openstack-swift00:01
*** chlong has joined #openstack-swift00:05
*** hogepodge has quit IRC00:16
*** hogepodge has joined #openstack-swift00:22
*** ianbrown has quit IRC00:23
*** ianbrown has joined #openstack-swift00:24
*** hogepodge has quit IRC00:27
*** dslevin_ has joined #openstack-swift00:35
notmynamemattoliverau: I asked about the general christmas decorations that shops put up this time of year in Oz. you (IIRC) said that they used to do a lot more with the fake snow and stuff, but now it's more summer-ish00:42
notmynamemattoliverau: do you have all the holiday music piped into all the stores? especially the ones about cold and snow and stuff?00:42
*** hogepodge has joined #openstack-swift00:43
notmynamemattoliverau: or is there some australian holiday genre about "I'm dreaming of a sunny christmas" or "let it shine, let it shine, let it shine"?00:43
mattoliveraunotmyname: some places still use fake snow, but mainly they just your xmas decoriations on the windows.00:44
notmynamebut is it all about snowflakes and fat men in red overcoats?00:44
mattoliverauAnd yes, Christmas carols playing everywhere. There are some Australianised carols, but mostly just the normal ones. Inculding white christmas and frosty the snow man00:45
notmynamelol. ok00:45
mattoliveraulots of tinsel and boubles.00:46
notmynameevergreen fir trees00:46
mattoliveraunotmyname: https://www.youtube.com/watch?v=r1aYkutjXfQ00:47
notmynamelol00:48
notmynameis that a real thing? I can't tell if that's a joke or not :-)00:49
notmynameI mean, I think it is, but...00:50
notmyname(a joke, that is)00:50
notmynameit also seems like something aussies would do (how's that for a stereotype! ;-)00:50
mattoliverauyeah, more of a joke, but its Australia (everything is a joke), so it'll still be played in stores on christmas (sometimes).00:51
*** nadeem has joined #openstack-swift00:51
notmynamelol00:52
*** haomaiwang has quit IRC01:01
*** haomaiwang has joined #openstack-swift01:01
*** dslevin_ has quit IRC01:02
*** haomaiwang has quit IRC01:07
*** ianbrown has quit IRC01:11
*** ianbrown has joined #openstack-swift01:12
*** nadeem has quit IRC01:39
*** bkmz has quit IRC01:51
*** bkmz has joined #openstack-swift01:51
kota_hello01:52
kota_Chrismas week?01:53
notmynameyeah. probably going to be a slower week this week and next01:53
kota_notmyname: sounds good for enjoyining vacation :)01:54
*** ianbrown has quit IRC01:57
*** ianbrown has joined #openstack-swift01:58
*** haomaiwang has joined #openstack-swift01:59
*** haomaiwang has quit IRC02:01
*** haomaiwa_ has joined #openstack-swift02:01
*** rminmin has joined #openstack-swift02:16
mattoliveraukota_: o/02:34
*** ianbrown has quit IRC02:39
*** ianbrown has joined #openstack-swift02:43
*** sanchitmalhotra has joined #openstack-swift02:56
*** haomaiwa_ has quit IRC03:01
*** haomaiwang has joined #openstack-swift03:01
*** wanghua has quit IRC03:23
*** ianbrown has quit IRC03:26
*** links has joined #openstack-swift03:26
*** ianbrown has joined #openstack-swift03:26
*** asettle is now known as asettle-afk03:34
*** haomaiwang has quit IRC04:01
*** haomaiwang has joined #openstack-swift04:01
*** ianbrown has quit IRC04:10
*** ianbrown_ has joined #openstack-swift04:10
*** proteusguy_ has quit IRC04:23
*** mahatic has joined #openstack-swift04:26
*** haomaiwang has quit IRC04:33
*** proteusguy_ has joined #openstack-swift04:35
*** ppai has joined #openstack-swift04:46
*** trifon has joined #openstack-swift04:57
*** klrmn has quit IRC05:01
*** haomaiwa_ has joined #openstack-swift05:02
*** trifon has quit IRC05:03
*** nadeem has joined #openstack-swift05:11
*** ianbrown_ has quit IRC05:12
*** ianbrown_ has joined #openstack-swift05:12
*** nadeem has quit IRC05:17
*** nadeem has joined #openstack-swift05:18
*** SkyRocknRoll has joined #openstack-swift05:37
*** sanchitmalhotra has left #openstack-swift05:38
*** sanchitmalhotra has joined #openstack-swift05:39
*** nadeem has quit IRC05:44
*** SkyRocknRoll has quit IRC05:58
*** haomaiwa_ has quit IRC06:01
*** haomaiwang has joined #openstack-swift06:01
*** SkyRocknRoll has joined #openstack-swift06:16
*** eranrom has joined #openstack-swift06:48
*** SkyRocknRoll has quit IRC06:50
*** ppai has quit IRC06:56
*** ChubYann has quit IRC06:59
*** haomaiwang has quit IRC07:01
*** haomaiwang has joined #openstack-swift07:01
*** SkyRocknRoll has joined #openstack-swift07:04
*** dslevin_ has joined #openstack-swift07:06
openstackgerritPeter Lisák proposed openstack/swift: Change schedule priority of daemon/server in config  https://review.openstack.org/23879907:06
*** ppai has joined #openstack-swift07:08
*** wanghua has joined #openstack-swift07:08
*** dslevin_ has quit IRC07:11
*** chlong has quit IRC07:13
*** SkyRocknRoll has quit IRC07:23
openstackgerritHisashi Osanai proposed openstack/swift: Fix duplication for headers in Access-Control-Expose-Headers  https://review.openstack.org/25839207:27
*** SkyRocknRoll has joined #openstack-swift07:41
*** dslevin_ has joined #openstack-swift08:00
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:01
*** silor has joined #openstack-swift08:05
*** dslevin_ has quit IRC08:05
openstackgerritrenminmin proposed openstack/python-swiftclient: Add default region name for swift SLI  https://review.openstack.org/25987908:06
*** rledisez has joined #openstack-swift08:07
*** silor has quit IRC08:12
*** silor has joined #openstack-swift08:12
*** Jeffrey4l has quit IRC08:15
*** silor1 has joined #openstack-swift08:15
*** silor has quit IRC08:16
*** silor1 is now known as silor08:16
*** mac_ified has quit IRC08:17
*** Jeffrey4l has joined #openstack-swift08:22
openstackgerritrenminmin proposed openstack/python-swiftclient: Add default region name for swift SLI  https://review.openstack.org/25988708:24
*** chlong has joined #openstack-swift08:30
*** jsuchome has joined #openstack-swift08:33
*** geaaru has joined #openstack-swift08:40
openstackgerritMahati Chamarthy proposed openstack/swift: Modify unit tests to include real crypto  https://review.openstack.org/21145108:50
*** dslevin_ has joined #openstack-swift08:54
*** dslevin_ has quit IRC08:59
*** daemontool has joined #openstack-swift09:00
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:01
nttHi, how can I check the used space in a swift cluster?09:13
ntttotal used space, for all projects.09:13
*** kei_yama_ has joined #openstack-swift09:16
*** kei_yama has quit IRC09:16
jsuchomehello! could anyone review https://review.openstack.org/#/c/189258/ ?09:28
*** openstack has joined #openstack-swift15:36
*** openstackstatus has joined #openstack-swift15:36
*** ChanServ sets mode: +v openstackstatus15:36
*** daddyjoseph97 has joined #openstack-swift15:44
*** SkyRocknRoll has joined #openstack-swift15:48
*** Jeffrey4l has quit IRC15:49
pdardeauGood morning!15:53
*** changbl has quit IRC15:54
*** daddyjoseph97 has quit IRC16:00
*** esker has quit IRC16:06
*** klrmn has joined #openstack-swift16:15
*** stevemar_znc is now known as stevemar16:28
*** gyee has joined #openstack-swift16:37
*** schizo is now known as bwall16:38
*** gmmaha has joined #openstack-swift16:41
*** diazjf has joined #openstack-swift16:43
*** zaitcev has joined #openstack-swift16:44
*** ChanServ sets mode: +v zaitcev16:44
*** diazjf1 has joined #openstack-swift16:48
*** diazjf has quit IRC16:50
*** klrmn has quit IRC17:09
openstackgerritAlistair Coles proposed openstack/swift: EC: Avoid conflicts when ssync'ing fragments  https://review.openstack.org/18140717:14
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527617:27
*** SkyRocknRoll has quit IRC17:40
*** gyee has quit IRC17:51
*** aix has quit IRC17:58
notmynamegood morning.17:59
* notmyname is in-and-out this week and next18:00
*** ChubYann has joined #openstack-swift18:00
janonymous_ o/ cool, merry christmas nd hpy new year in advance :)18:01
*** chsc has joined #openstack-swift18:01
notmynamethanks18:03
*** dslevin_ has joined #openstack-swift18:05
*** kevinc has joined #openstack-swift18:13
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Updated from global requirements  https://review.openstack.org/8873618:15
*** rledisez has quit IRC18:15
*** rledisez has joined #openstack-swift18:18
*** klrmn has joined #openstack-swift18:19
*** dslevin__ has joined #openstack-swift18:20
*** dslevin_ has quit IRC18:20
*** gyee has joined #openstack-swift18:22
*** gyee has quit IRC18:25
*** geaaru has quit IRC18:27
*** kevinc has quit IRC18:30
*** acoles is now known as acoles_18:32
*** eranrom has joined #openstack-swift18:32
*** dslevin__ has quit IRC18:36
*** rledisez has quit IRC18:37
*** petertr7_away is now known as petertr718:51
*** gyee has joined #openstack-swift18:53
*** dslevin_ has joined #openstack-swift18:54
*** trifon has joined #openstack-swift18:56
*** petertr7 is now known as petertr7_away19:02
*** changbl has joined #openstack-swift19:05
*** dslevin_ has quit IRC19:16
openstackgerritThiago da Silva proposed openstack/swift: decouple versioned writes from COPY  https://review.openstack.org/26017919:30
tdasilvawbhuber, jrichli: ^^^ this should be the first patch in getting copy middleware fixed up19:31
jrichlitdasilva: thanks a bunch!  I will check it out.19:32
tdasilvawbhuber, jrichli: tomorrow I will work on rebase copy middleware to depend on this patch19:32
*** zhill has joined #openstack-swift19:34
jrichlisounds great.  I hope you get to enjoy the holidays too ;-)19:34
tdasilvajrichli: i will be going on break after wed! hope you have some time off too19:37
jrichlitdasilva: ah, that's good.  I have been on break since Wednesday.  Just been doing  a little work here and there.  I hope to get a lot accomplished between the 27th and the 4th!19:41
*** dslevin_ has joined #openstack-swift19:48
*** esker has joined #openstack-swift19:53
*** esker has quit IRC19:54
*** esker has joined #openstack-swift19:54
*** dslevin_ has quit IRC20:00
*** pc6411 is now known as pchng20:14
openstackgerritEran Rom proposed openstack/swift: Container-Sync to check the right client exception  https://review.openstack.org/26020420:15
ZyricGood Morning20:15
*** zhill has quit IRC20:18
*** janonymous_ has quit IRC20:26
*** zhill has joined #openstack-swift20:29
mattoliveraumorning20:31
*** zhill has quit IRC20:31
*** esker has quit IRC20:42
*** esker has joined #openstack-swift20:43
*** changbl has quit IRC21:14
*** petertr7_away is now known as petertr721:19
notmynamehello mattoliverau and Zyric21:27
*** asettle-afk has quit IRC21:37
notmynametdasilva: if you get a chance before you take off, could you take another glance at patch 241978 ?21:49
patchbotnotmyname: https://review.openstack.org/#/c/241978/ - Add support for storage policies to have more than...21:49
onovysomeone for review pls? https://review.openstack.org/#/c/251151/222:03
*** petertr7 is now known as petertr7_away22:05
*** tonyb has joined #openstack-swift22:19
tonybnotmyname: anychance you can remove your -2 from https://review.openstack.org/#/c/174343/ and https://review.openstack.org/#/c/173982/ ?22:21
tonyb(both kilo requirements updates)22:21
notmynametonyb: why?22:25
tdasilvanotmyname: sure22:26
notmynametdasilva: thanks22:26
tonybnotmyname: because it will help with swift co-installability for kilo.22:26
onovyaaa global requirements :)22:28
*** asettle has joined #openstack-swift22:28
notmynametonyb: our of curiosity, how so? my understanding is that the global file is used in the gates, regardless of what the per-project requirements file is22:29
onovytonyb, it's moving version only up. so swift accept NEWER versions fine. co-installability is fine22:29
notmynamealso, what onovy said ;-)22:30
tonybnotmyname: the upper contrainsts file is used in liberty/mitaka not in kilo22:30
onovyswift will work with greenlet 0.3.1 and 0.3.2 too. so use 0.3.2 from other projects (requirements) and swift will be fine too22:31
onovy(example)22:31
tonybnotmyname: the *requirements files in each project still need to be in sync or you end up with projectX installing a library that breaks projectY22:31
onovyno, that's package maintaner work22:32
onovyand i'm packing swift for debian, so i should know it :)22:32
tonybonovy: but the dependancy parser in pip isn't as good as it could be (that's being worked on) so that doesn't work.22:32
onovyso fix pip is correct way? :)22:32
tdasilvaZyric: hi, re patch 241978, I just had a question about the new methods in StoragePolicyCollection, couldn't find how they are being used. what am I missing?22:33
tonybonovy: like I said that's being worked on but it's complex the global-requirements is the way OpenStack as a whole deals with it.22:33
patchbottdasilva: https://review.openstack.org/#/c/241978/ - Add support for storage policies to have more than...22:33
onovyif project X want eventlet >=0.3.2 and projectY want eventlet >=0.3.1 then 0.3.2 will be installed. -> it's working correctly22:33
*** asettle has quit IRC22:34
torgomatic_Zyric: ping22:35
Zyrictdasilva: I don't believe they are used yet, it's a new feature so I just included all the functions I believed would be useful.22:35
onovyand i'm merging glob-req in my project (swauth). but i understand why swift is not doing the same22:35
Zyrictorgomatic_: hello hello! Hope you're feeling better :)22:36
torgomatic_Zyric: yes, for the moment :)22:36
onovyif swift don't need new version, why force to update? there are many envs where swift live without others openstack projects (and it our company is on of it).22:36
torgomatic_Zyric: notmyname said you wanted to talk to me about the auditor stuff22:36
Zyrictorgomatic_: That's right, I had a few questions relating to how and where it plugs into the middleware22:37
ZyricWhich configs to edit, etc.22:37
torgomatic_yeah, I should probably come up with a sample project and stick it in a review comment or something22:37
Zyrictorgomatic_ that would be super useful. I'm having a bit of trouble getting it going in my swift system but it works fine in the tests22:38
onovytonyb, so, can you explain better why it's needed?22:38
onovyok, time to go to bed. good night22:41
onovytonyb, continue with notmyname, thanks :)22:41
tonybonovy: So you're right that the swift change only raises the minimums but the swiftclient one adds a ban on requests 2.8.0 which is needed.22:42
notmynameonovy: I was loving the questions you were asking :-)22:42
tonybonovy: ok, sorry I've been tryign to get my thoughts in order22:42
tonybnotmyname, onovy: so there are 2 aspects the technical one where the python-swiftclient requirement on requests can break other openstack libraries if installed globally, and social contract that OpenStack projects opt into the requirements updates.  I understadn that swift more than pretty much anything else walks the line between installing as part of OpenStack and isoloated.22:45
tonybnotmyname, onovy: If you can't/wont take the python-swiftclient update will you at least take a specific review for the requests change?22:46
tonybnotmyname, onovy: it'd be my preference to take the whoel things as it makes spotting things easier but somethign is better than notthing.22:47
notmynametonyb: ...also composing my thoughts22:50
*** dslevin_ has joined #openstack-swift22:51
*** dslevin_ has quit IRC22:55
notmynametonyb: I'm more open to accepting just updating the requests line22:57
notmynamehowever...22:57
notmynametonyb: so I install swiftclient first and for some reason I get 2.4.0 installed. and swiftclient works. then I install something else and it upgrades requests. and swiftclient and the other thing work. or I install Other first and get requests per g-r. then I install swiftclient and it works22:57
notmynameso what is the problem with coinstallability?22:58
*** km__ has joined #openstack-swift23:00
notmynametonyb: perhaps I'm missing somethign about how things are installed and the way dependencies are resolved23:01
tonybnotmyname: Install projectX which has !=2.4.0 , <2.8.0 and that's fine.  You install swiftclient which just says > 1.x (or similar) and get 2.8.0 which *may* be fine for swift or not (I'd need to check why we banned 2.8.0) but will break projectX23:02
tonybbut that may only be true if you use -U23:02
tonybnotmyname: I have to admit I've confused myself now.23:02
*** dslevin_ has joined #openstack-swift23:03
notmynametonyb: to be clear, in general, I really like and support the idea behind global requirements. we should make things easier for packagers (including distros). I'm all for that, and I don't want to stand in the way23:03
notmynamewhich is why I'd be more open to just the requests line23:03
notmynameespecially if anyone can tell me why things break as-is today23:04
*** chsc has quit IRC23:04
notmynamepart of making things easier for packagers, IMO, is not upgrading packages every time someone starts using a new feature23:05
tonybnotmyname: Yeah we're working on how to do that better but sadly we have legacy we need to carry around.23:06
notmynamebut what is that? what is broken today that accepting this patch (or a more limited requests-only one) will fix?23:06
tonybnotmyname: so I think the swiftclient requirements is only a problem iff someone pip install -U's swftclient23:06
notmynamewhich is effectively what's done if you install without -U and don't have requests already installed23:07
lifeless^ that23:08
lifelessnotmyname: so that would be a good and interesting discussion to have (not upgrading minimums rapidly)23:08
lifelessnotmyname: and its one I'd like to have, but its (hopefully obviously) non-trivial23:09
notmynameso to make sure I understand, the problem needing fixing is the situation where swiftclient is installed before other openstack projects and also is the first app on the system to pull in requests and then you want to bring in other openstack projects who have merged the requests limiter from g-r?23:11
notmynamelifeless: I too would like to have it (ie see my review comments from 2014 on this topic on the proposal bot patches). but I'm not sure it's obviously non-trivial. at least not to those of us who don't have a deep history of distro building23:13
tonybnotmyname: Yes.23:14
tonyblifeless: I'd like to be in the room while that's discussed.23:15
notmynametonyb: is the implication that you'd also need a kilo release and the same patches to be in master (and what about liberty)?23:15
*** Jeffrey4l has joined #openstack-swift23:15
lifelessnotmyname: so the non-triviality is that we have no described mechanism to express 'using requests < X will be horribly insecure'23:17
lifelessnotmyname: *other* than setting a minimum23:17
lifeless(substitute any other thing there too - 'use Cinder 2015.4'23:18
notmynamelifeless: you've just introduced a new variable. I though we were talking about a solver for versions for generic dependency X. is there some other technical thing about requests?23:18
lifelessnotmyname: no, its not a solver issue; its that making things within a code base only work when a dependency is above some version - higher than the expressed minimum in the dependency list - creates a sort of mystery meat experience for users23:19
tonybnotmyname: to be frank I haven't looked at liberty becase I decided to start with kilo23:19
tonybnotmyname: I don't think this mandates a release but I'd need to think harder about that.23:19
notmynametonyb: is there a specific security thing in requests that necessitates a min version bump, as lifeless hints?23:20
tonybnotmyname: I'll look.23:21
lifelessnotmyname: sorry, I was using a single example of the reason why 'not raising minimums' is non-trivial.23:21
lifelessnotmyname: for requests *in specific*, let me check the reasons we've been updating minimums23:21
lifelessso 2.8.0 broke some gate jobs23:23
lifelessbug 150376823:23
openstackbug 1503768 in python-glanceclient "keystoneclient.exceptions.RequestTimeout with requests==2.8.0" [Undecided,New] https://launchpad.net/bugs/1503768 - Assigned to Flavio Percoco (flaper87)23:23
notmynamedoesn't this effectively turn in to "you must be running the latest release of any dependency" if any project hitting any bug in a dependency requires all openstack projects to raise minimum versions to the first version after the bug int he dependency is fixed?23:25
tonybnotmyname: it wasn't a security issue that raised the minimum.  It was oslo.vmware needed to use file:// urls which (aparently) weren't supported in <2.2.023:25
pdardeaunotmyname:23:26
pdardeaunotmyname: ping23:26
tonyblifeless: yeah that's what capped the requests23:26
lifelesswe bumped to 2.6.0 because of issues with docker-py23:26
notmynamepdardeau: what's up?23:27
lifeless2.2.0 was because of oslo.vmware file:// support23:27
tonybhttps://review.openstack.org/#/c/123714/ is what raised kilo from requests>=1.2.1 to requests>=2.2.023:27
pdardeaunotmyname: hey, just wanted to give an update on the device count increase feature23:27
lifelesshowever23:28
lifelesshttp://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2015-229623:28
pdardeaui'm planning to push wip next week and possibly even the non-wip by end of next week23:28
notmynamepdardeau: nice23:28
lifelessrequests 2.6.0 is the minimum to avoid known security issues23:28
lifeless( from http://docs.python-requests.org/en/latest/community/vulnerabilities/ )23:28
pdardeaunotmyname: i'll be off on vacation remainder of this week, but will be working all next week23:28
notmynamepdardeau: me too ;-)23:28
lifelessand 2.3.0 has a couple of bad vulns23:29
lifelessnotmyname: so the interaction of the solver here is that only the first reference to a package is honoured by pip23:29
pdardeauall: best wishes for the holidays and i'll return next Monday23:29
lifelessnotmyname: we're working on that, and once fixed we can consider doing partial-upgrades of dependencies across openstack23:29
notmynamepdardeau: thanks for the update. I'm off this week and next and just in and out. I'm looking forward to it!23:29
notmynamethe security issue(s) is very different than file or docker support. that's a good reason to upgrade the min version23:30
lifelessnotmyname: one of the complexities of embracing skewed minimums across openstack though is testing: and note that *all* distributors distribute only a single version of requests.23:31
lifelessnotmyname: so we don't help distributors at all by having differing minimums: they upgrade as soon as anything they distribute needs the upgrade23:31
notmynametonyb: so if you submit a patch for the requests line and leave a comment (or commit message) referencing the security stuff to stable/kilo for swiftclient, I'll approve it23:31
*** trifon has quit IRC23:33
notmynamelifeless: I understand that. but this isn't a problem that came into being with openstack. it's something that distros have always been doing. one compatible version number is very different than your example of a project enabling/disabling things based on newer versions23:34
notmyname*newer versions of dependencies. and I include "having security holes" in that too23:35
*** ianbrown_ has quit IRC23:35
notmynameand having a reasonable set of "here's requirements" common across openstack is good. like I said, I agree with and support the ideas behind global requirements23:35
*** ianbrown_ has joined #openstack-swift23:35
notmynameI just have some problems with the practical aspects of how it's implemented23:36
*** kei_yama has joined #openstack-swift23:36
*** trifon has joined #openstack-swift23:37
lifelessnotmyname: so, we need to get those laid out somewhere; I can't come up with creative solutions until I know the concerns :)23:40
notmyname1) I don't like that any other project using a just-released feature in a third party library can compel a single project's deployers to rebuild packages when they upgrade (for changes that project doesn't require)23:41
notmyname2) I don't like the exact string match solver for g-r. it means I can't just add an exclusion or satisfy requirements by accepting things more broadly (eg libfoo>=1.0 in requirements is not compatible with libfoo>=1.5 in g-r)23:41
notmyname3) g-r assumes all requirements are found on pypi and installable with pip. ie python libraries. that's not the case at all, and thus the requirements file is always incomplete and doesn't cover all the dependency concerns23:41
lifelessnotmyname: the reason I talked about enabling/disabling things is that there are really three implementation choices: all the same, different everywhere, and all-the-same-oldest-version-with-internal-enablement-of-new-things23:41
lifelessnotmyname: so 3) - have you looked at bindep ?23:43
notmynameI don't know what that is23:43
lifelessnotmyname: https://github.com/openstack-infra/bindep/blob/master/README.rst23:43
*** ho has quit IRC23:44
lifelessnotmyname: its a thing I wrote to solve the inability to refer to system packages as dependencies23:44
lifelessnotmyname: so I'd like to see good answers for 3, its a non-tiny field itself: do we have one project coordinating all the deps,23:45
lifelessor do we have one coordination point per language/packaging system ?23:45
lifelessnotmyname: on 1 and 2, they are the result of the current choice from the solutioon space I referred to above23:46
notmynameI'm pretty sure one of the main reasons docker et al get so much hype is because devs can package whatever latest greatest they want in their sandbox without the sysadmins having to make a dependnecy solver ;-)23:46
lifelessnotmyname: the choices again: all-the-same-highest-minimum, all-the-same-lowest-minimum-plus-selective-enablement, project-local-minimums23:48
lifelessnotmyname: currently openstack's official policy is all-the-same-highest-minimum.23:48
lifelessnotmyname: it causes 1) above23:49
lifelessnotmyname: and 2) above23:49
notmynameI understand the logic that gets there. I just don't like the destination23:50
lifelessnotmyname: if we adopt project-local-minimums23:50
lifelessnotmyname: we need to have a solver in pip first (to avoid https://github.com/pypa/pip/issues/988 )23:52
lifelessnotmyname: we also need some rule to ensure that there is *a* consistent version across all of openstack [or we can't co-install everything]23:52
lifelessnotmyname: we also have a testing gap that can arise - right now we don't test minimums at all, and if we do we can at least test one minimum across everything23:53
lifelessif there are project-local minimums23:53
lifelesswe have to figure out some way to test each project with its actual minimums23:54
lifelessnotmyname: sure, I'm trying to figure out some way to meet your needs23:56
*** changbl has joined #openstack-swift23:57
lifelessanyhoo23:58
*** ho has joined #openstack-swift23:59

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