| *** zehicle_ has quit IRC | 00:12 | |
| *** zehicle_ has joined #openstack-defcore | 00:18 | |
| *** galstrom is now known as galstrom_zzz | 00:42 | |
| *** galstrom_zzz is now known as galstrom | 00:58 | |
| openstackgerrit | Chris Hoge proposed openstack/defcore: Added 2016A Swift Scoring Matrix https://review.openstack.org/290592 | 01:10 |
|---|---|---|
| *** galstrom is now known as galstrom_zzz | 02:26 | |
| *** MarkAtwood has quit IRC | 02:30 | |
| *** galstrom_zzz is now known as galstrom | 02:47 | |
| *** galstrom is now known as galstrom_zzz | 04:06 | |
| *** MarkAtwood has joined #openstack-defcore | 04:08 | |
| *** MarkAtwood has quit IRC | 04:12 | |
| *** MarkAtwood has joined #openstack-defcore | 04:38 | |
| *** markvoelker has quit IRC | 05:28 | |
| *** pcaruana has quit IRC | 05:48 | |
| *** MarkAtwood has quit IRC | 06:11 | |
| *** MarkAtwood has joined #openstack-defcore | 06:24 | |
| *** markvoelker has joined #openstack-defcore | 06:29 | |
| *** markvoelker has quit IRC | 06:34 | |
| *** lifeless has quit IRC | 07:06 | |
| *** pcaruana has joined #openstack-defcore | 07:32 | |
| openstackgerrit | Chris Hoge proposed openstack/defcore: Added cinder scoring for Mitaka release cycle https://review.openstack.org/290271 | 07:48 |
| openstackgerrit | Chris Hoge proposed openstack/defcore: Added 2016A Swift Scoring Matrix https://review.openstack.org/290592 | 07:53 |
| *** markvoelker has joined #openstack-defcore | 07:56 | |
| *** MarkAtwood has quit IRC | 08:00 | |
| *** MarkAtwood has joined #openstack-defcore | 08:00 | |
| *** markvoelker has quit IRC | 08:02 | |
| *** pilgrimstack has quit IRC | 08:26 | |
| *** pilgrimstack has joined #openstack-defcore | 08:26 | |
| *** MarkAtwood has quit IRC | 08:34 | |
| *** pilgrimstack has quit IRC | 09:45 | |
| *** pilgrimstack has joined #openstack-defcore | 09:48 | |
| *** markvoelker has joined #openstack-defcore | 09:58 | |
| *** markvoelker has quit IRC | 10:03 | |
| *** MarkAtwood has joined #openstack-defcore | 10:15 | |
| *** MarkAtwood has quit IRC | 10:20 | |
| *** lifeless has joined #openstack-defcore | 11:07 | |
| *** MarkAtwood has joined #openstack-defcore | 11:16 | |
| *** MarkAtwood has quit IRC | 11:20 | |
| *** edmondsw has joined #openstack-defcore | 11:54 | |
| *** markvoelker has joined #openstack-defcore | 11:59 | |
| *** MarkAtwood has joined #openstack-defcore | 12:17 | |
| *** MarkAtwood has quit IRC | 12:22 | |
| *** galstrom_zzz is now known as galstrom | 12:54 | |
| *** galstrom is now known as galstrom_zzz | 12:55 | |
| *** cjvolzka has joined #openstack-defcore | 12:59 | |
| *** dwalleck has joined #openstack-defcore | 15:02 | |
| *** edmondsw has quit IRC | 15:13 | |
| *** lifeless has quit IRC | 15:13 | |
| gema | markvoelker: you around? | 15:21 |
| markvoelker | hi | 15:21 |
| gema | markvoelker: when I do the scoring with the tabulate_scores, do I change the next.json before or after? | 15:22 |
| gema | I am not quite understanding what it does with the input json | 15:22 |
| markvoelker | It doesn't matter. The tabulate_scores script doesn't do anything to the json, it just reads weights from it. | 15:22 |
| gema | or maybe I should give the last json | 15:22 |
| markvoelker | SO, you should feed it next.json | 15:22 |
| gema | markvoelker: but first I need to put my findings about the new capabilities there, yes? | 15:23 |
| gema | or else how does it know? | 15:23 |
| markvoelker | Right. So: | 15:23 |
| markvoelker | 1.) Make changes to scoring.txt | 15:23 |
| markvoelker | 2.) Run tabulate_scores.py -j ../next.json -s scorint.txt | 15:24 |
| markvoelker | 3.) ?!?!? | 15:24 |
| markvoelker | 4.) PRofit! | 15:24 |
| markvoelker | =) | 15:24 |
| gema | profit? | 15:24 |
| gema | xDDD | 15:24 |
| gema | now I am totally lost | 15:24 |
| gema | and then based on the scoring I change the json? | 15:25 |
| gema | and after that I score it again or I stop there for now? | 15:26 |
| markvoelker | So basically, all the tabulate_scores script does is read the weights out of the json file (for example: https://github.com/openstack/defcore/blob/master/next.json#L2845 ). It needs those to tally up the total score for each capability in scoring.txt. It doens't modify next.json at all | 15:26 |
| markvoelker | Once you run the script, you'll have total scores for each capability | 15:26 |
| markvoelker | So then you can decide if you think they've scored high enough to include as advisory in next.json, and modify that file accordingly | 15:26 |
| gema | markvoelker: oh, it makes more sense now! | 15:27 |
| markvoelker | (the script doesn't do this for you, in part because up until very recently we didn't even have a cutoff score field, so it couldn't know whether something should be added or not) | 15:27 |
| gema | markvoelker: ok, this is starting to make a lot of sense, thank you! | 15:27 |
| markvoelker | Sure thing. One of the items on my to-do list is to make it modify the json file now that we have a cutoff score field (mostly just to prevent human error). Just haven't managed to find time to do it yet. =) | 15:28 |
| *** edmondsw has joined #openstack-defcore | 15:29 | |
| *** lifeless has joined #openstack-defcore | 15:29 | |
| gema | markvoelker: don't worry, we also need to add the tests anyway | 15:29 |
| gema | and I am not sure how you are going to find those automatically | 15:29 |
| *** lifeless has quit IRC | 15:30 | |
| *** lifeless has joined #openstack-defcore | 15:30 | |
| gema | alrighty, back to it | 15:31 |
| gema | if my cloud collaborates, I may even be able to run the tests before submitting x | 15:31 |
| gema | x) | 15:31 |
| gema | markvoelker: +1 thanks for all the support :D | 15:32 |
| markvoelker | Thanks for working on scoring! | 15:32 |
| gema | markvoelker: I imagine all keystone capabilities are discoverable by definition, but what does it mean "can be found in Keystone and via service introspection" | 15:41 |
| markvoelker | 1.) Is it in the keystone service catalog? | 15:42 |
| markvoelker | 2.) Can the API be introspected to determine if the capability is available? | 15:42 |
| markvoelker | An example of 2: | 15:42 |
| markvoelker | In Neutron, you can use a GET / call to get a list of supported extensions. So you can determine if a given extension is available or not that way. | 15:42 |
| gema | oh, I see | 15:43 |
| gema | ok, because the service catalog requires admin, afaik | 15:43 |
| gema | alright, will check that | 15:44 |
| cjvolzka | For certification I see a requirement, "You must clearly state which OpenStack projects and release versions are used in the product to set customer expectations, in a way that is conspicuous to customers" Is there any definition on where this must be provided? For example, do we need to put this in the program or is only having it in the documentation fine? | 16:12 |
| markvoelker | cjvolzka: The OpenStack Foundation sets those requirements, so I'd check with hogepodge (interop@openstack.org) | 16:18 |
| cjvolzka | markvoelker: ok, thanks :) | 16:18 |
| *** openstackgerrit has quit IRC | 17:01 | |
| *** openstackgerrit has joined #openstack-defcore | 17:02 | |
| *** pcaruana has quit IRC | 17:40 | |
| *** dwalleck has quit IRC | 18:58 | |
| *** openstackgerrit has quit IRC | 20:48 | |
| *** openstackgerrit has joined #openstack-defcore | 20:49 | |
| *** openstack has joined #openstack-defcore | 21:50 | |
| *** edmondsw has joined #openstack-defcore | 22:00 | |
| *** GheRivero has quit IRC | 22:03 | |
| *** GheRivero has joined #openstack-defcore | 22:05 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!