Wednesday, 2016-04-20

openstackgerritMerged openstack/defcore: Added keystone scoring for Mitaka release cycle.  https://review.openstack.org/29784703:45
openstackgerritMerged openstack/defcore: fix some typos/punctuation in CoreCriteria.rst  https://review.openstack.org/30715303:55
openstackgerritMerged openstack/defcore: Leave capabilities advisory until tests updated  https://review.openstack.org/30526904:01
*** markvoelker has quit IRC04:34
*** markvoelker has joined #openstack-defcore04:35
*** markvoelker has quit IRC04:40
openstackgerritChris Hoge proposed openstack/defcore: Added 2016A Swift Scoring Matrix  https://review.openstack.org/29059204:52
openstackgerritChris Hoge proposed openstack/defcore: Added 2016A Swift Scoring Matrix  https://review.openstack.org/29059205:01
openstackgerritChris Hoge proposed openstack/defcore: Added 2016A Swift Scoring Matrix  https://review.openstack.org/29059205:02
*** pilgrimstack has joined #openstack-defcore06:42
*** pilgrimstack has quit IRC07:11
*** pilgrimstack has joined #openstack-defcore08:06
*** markvoelker has joined #openstack-defcore12:18
*** cjvolzka has joined #openstack-defcore12:58
*** edmondsw has joined #openstack-defcore13:38
*** amit213 has quit IRC15:06
*** amit213 has joined #openstack-defcore15:08
openstackgerritChris Hoge proposed openstack/defcore: Added cinder scoring for Mitaka release cycle  https://review.openstack.org/29027115:54
*** lcazares has joined #openstack-defcore15:56
*** lcazares has quit IRC15:57
*** lcazares has joined #openstack-defcore15:59
*** galstrom_zzz is now known as galstrom16:29
docaedoman, sorry I missed a really interesting 20 minute section of the meeting today :(17:08
hogepodgeTo be clear, if a fixture is an interop capability, I have no problem with failing a test because that fixture fails. Not saying there's not room for improvement on the test, but free passes should be given for technicalities.17:14
hogepodgeIf a fixture is not an interop capability there's a strong case to not require it until the problem is fixed.17:15
markvoelkerhogepodge: and, in a perfect world, if a test has a fixture that's another required capability, that required capability would also have a test, right?17:19
markvoelkerWhich would probably fail in most of the cases where the fixture failed....17:19
docaedoThe part I don't understand is that what matters is "can users all make use of a certain ability" and if you can make a volume, but can't get rid of it, that's only half the feature17:21
docaedo"identify a need for an unmount test" is the part I would have been disagreeing with - yes, there's a need for that, but it should all be part of "do volumes work here?"17:22
markvoelkerdocaedo: typing while in a meeting here, so you'll have to pardon slow replies.  Maybe some background is useful:17:24
markvoelkerdocaedo: so, the tricky bit is how we define a "Capability" and how we test that Capability.  You can argue one Capability = 1 API, or you could argue that multiple API's (e.g. everything in a CRUD) = 1 Capability.17:25
hogepodgemarkvoelker one would hope so17:25
*** lcazares has quit IRC17:25
markvoelkerdocaedo: also important to consider multiple ways to do things17:25
markvoelkerdocaedo: for example, there are some tests that create images with glance v1 as part of a fixture17:26
markvoelkerIf we require v2 but don't require v1...17:26
markvoelkeretc etc17:26
hogepodgemarkvoelker if that's not the case, my preferred course of action is to count test as fail and write new test to cover gap, and not flag on technicality17:26
*** lcazares has joined #openstack-defcore17:26
markvoelkerOr if a fixture uses the import task vs image create17:27
docaedoI can appreciate how it gets tricky - I think from my perspective the value of defcore/refstack/interop though is that users have the same experience across openstack clouds17:27
docaedoand that's tough because openstack allows a dozen competing ways to solve the same problem, and operators want flexibility to do whatever they feel like doing (but they still want to be certified anyway)17:28
*** MarkAtwood has joined #openstack-defcore17:29
markvoelkerdocaedo: right.  And so in some cases we might get into situations where, surprisingly, the market hasn't clearly picked a winner among the various ways to do some part of a CRUD operation, sadly. =/17:29
docaedo(I'm not driving towards a great point with a perfect answer here, FYI :) Just trying to understand more of the background and politics around this stuff)17:29
markvoelkerOh, you don't have a perfect answer?  Well, you'll fit right in around here then. =)17:30
docaedoI've finally found my home!17:30
* markvoelker has to tune back into his meeting for a bit17:31
hogepodgemarkvoelker import task is deprecated and admin only. It is not interop. If you watch the Vancouver summit video about the task API, the speaker acknowledges the task api is not discoverable or interoperable18:02
markvoelkerhogepodge: Sure, just an example.  Maybe image-list is a better one.18:03
hogepodgeWe flagged in that instance. One year later the underlying problem is not fixed.18:05
hogepodgeWe tried to set policies to encourage upstreaming and fixing by vendors, but those policies seem to have not provided the proper incentives to do that.18:07
markvoelkerI'd argue that there's been progress toward it though.  Lots of discussion about dropping the nova proxy API's and making that policy, glance moving toward depracting v1, etc.18:08
hogepodgeThe immediate issue was a v2 proxy, which is desired but still a wish list item18:08
hogepodgeMaybe requiring direct image will fix that, but those who depend on task api will probably object and the unified APIs is also wip, making it a long term interop candidate18:09
hogepodgeSo, as of today, one of the most important aspects of cloud has no interoperable interface.18:10
*** lcazares is now known as Guest7490518:11
*** luzC is now known as lcazares18:11
markvoelkerYup. And there is no way to fix that overnight.18:11
hogepodgeNetworking will be another can of worms. Some clouds don't want to give you any control over network, and we have no good way to guarantee network connectivity in an interop way18:12
markvoelkerAll fine candidates for our forthcoming report on major interop issues that OpenStack has today. =)18:14
*** MarkAtwood has quit IRC18:15
*** lcazares has quit IRC18:15
*** luzC has joined #openstack-defcore18:16
*** luzC- has joined #openstack-defcore18:19
*** luzC- has quit IRC18:20
*** luzC- has joined #openstack-defcore18:24
*** luzC has quit IRC18:25
*** luzC- is now known as luzC18:25
*** lcazares has joined #openstack-defcore18:28
*** galstrom has quit IRC18:35
*** galstrom_zzz has joined #openstack-defcore18:35
*** galstrom_zzz is now known as galstrom18:35
*** woodster_ has joined #openstack-defcore18:39
*** galstrom has quit IRC19:00
*** galstrom has joined #openstack-defcore19:00
openstackgerritMerged openstack/defcore: Added 2016A Swift Scoring Matrix  https://review.openstack.org/29059220:32
*** MarkAtwood has joined #openstack-defcore21:00
openstackgerritChris Hoge proposed openstack/defcore: Added cinder scoring for Mitaka release cycle  https://review.openstack.org/29027121:01
hogepodgemarkvoelker: eglute: ^^21:01
*** luzC has quit IRC21:16
*** luzC has joined #openstack-defcore21:21
*** edmondsw has quit IRC22:24
*** galstrom is now known as galstrom_zzz22:36

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