Friday, 2015-03-27

*** annegentle has joined #openstack-api00:06
*** sigmavirus24_awa is now known as sigmavirus2400:48
*** annegentle has quit IRC01:14
sigmavirus24elmiko: that's just how unittest wants the arguments01:14
sigmavirus24elmiko: testr just uses that to appropriately print the results. unittest.TestCase.assertEqual should always be passed as expected, actual01:15
*** annegentle has joined #openstack-api01:17
*** annegentle has quit IRC01:48
*** sigmavirus24 is now known as sigmavirus24_awa02:14
*** annegentle has joined #openstack-api02:48
*** annegentle has quit IRC02:54
*** annegentle has joined #openstack-api03:50
*** annegentle has quit IRC03:55
*** annegentle has joined #openstack-api04:08
*** annegentle has quit IRC04:13
*** annegentle has joined #openstack-api05:19
*** annegentle has quit IRC05:24
*** annegentle has joined #openstack-api06:20
*** annegentle has quit IRC06:25
*** etoews has quit IRC07:29
*** annegentle has joined #openstack-api08:22
*** annegentle has quit IRC08:27
*** e0ne has joined #openstack-api10:18
*** annegentle has joined #openstack-api10:23
*** annegentle has quit IRC10:29
*** annegentle has joined #openstack-api11:24
*** annegentle has quit IRC11:29
*** cdent has joined #openstack-api11:37
*** e0ne is now known as e0ne_11:48
*** e0ne_ is now known as e0ne11:49
*** annegentle has joined #openstack-api12:22
*** annegentle has quit IRC12:23
*** kaufer has joined #openstack-api12:40
*** sigmavirus24_awa is now known as sigmavirus2412:57
*** e0ne is now known as e0ne_13:03
elmikosigmavirus24: thanks for the response, i ended up looking at the testtools.TestCase.assertEqual source13:03
elmikoit calls out the variables as (expected, observed)13:03
*** e0ne_ is now known as e0ne13:11
*** annegentle has joined #openstack-api13:24
*** annegentle has quit IRC13:29
*** kaufer has quit IRC13:32
*** annegentle has joined #openstack-api13:43
*** kaufer has joined #openstack-api13:45
*** annegentle has quit IRC14:07
*** etoews has joined #openstack-api14:20
*** annegentle has joined #openstack-api14:32
*** e0ne is now known as e0ne_14:36
*** e0ne_ is now known as e0ne14:48
*** annegentle has quit IRC15:04
*** annegentle has joined #openstack-api15:05
*** fifieldt has quit IRC15:21
openstackgerritMiguel Grinberg proposed openstack/api-wg: Metadata guidelines document  https://review.openstack.org/14122915:28
*** annegentle has quit IRC16:06
*** e0ne is now known as e0ne_16:20
*** e0ne_ is now known as e0ne16:26
*** e0ne is now known as e0ne_16:27
*** e0ne_ is now known as e0ne16:27
etoewslooks like there's support across the board for json in the api wg repo https://review.openstack.org/#/c/167869/16:45
etoewsconsidering it's not a guideline i think it's good to merge.16:46
sigmavirus24agreed etoews16:49
sigmavirus24who are our cores again?16:49
etoewsme, jaypipes, and cyeoh16:49
etoewsthis is a rare case where i'm okay with a self merge16:50
etoewsi gotta ping those 2 and get them in here.16:50
sigmavirus24heh fair16:50
*** ChanServ sets mode: +o sigmavirus2416:50
*** ChanServ sets mode: -o sigmavirus2416:51
sigmavirus24I just sent cyeoh an invite via IR16:51
sigmavirus24*IRC but he might miss it16:51
etoewsi see him on #openstack-dev16:52
openstackgerritMerged openstack/api-wg: Allow JSON files for JSON Schemas and JSON examples  https://review.openstack.org/16786916:59
cdentetoews, sigmavirus24: is there any ongoing conversation about getting the various project apis all under the same http host and port?17:04
*** annegentle has joined #openstack-api17:04
etoewscdent: do you mean in devstack17:04
etoews?17:04
etoewsor the world?17:05
cdentI was thinking more general.17:05
sigmavirus24cdent: that's come up on the ML17:05
cdentObviously there are ways to do it if you tweak a bunch of knobs17:05
sigmavirus24I believe ayoung was working on that a lot17:05
cdentbut it is not something that is easy17:05
sigmavirus24I believe ayoung's idea was to have stuff like17:05
sigmavirus24host.com/image/images/detail/{image-id}17:05
sigmavirus24or host.com/horizon{/horizon's/paths/here}17:06
sigmavirus24host.com/compute{/nova's/stuff/here}17:06
* cdent nods17:06
sigmavirus24So each service's paths would be underneath one other path17:06
sigmavirus24but yeah, I prefer subdomains personally for that17:06
sigmavirus24(Even though people were complaining about SSL certificates being harder with sub-domains)17:07
cdentsubdomains would be another reasonable way to do it, I guess17:07
cdentless painful in terms of dealing with already-known paths17:07
sigmavirus24Yep17:07
sigmavirus24Very clear separation of concerns: images.mycloud.com and compute.mycloud.com17:08
cdentthe proliferation of ports bothers me for some reason that I can't quite explain17:08
sigmavirus24cdent: I get that17:08
sigmavirus24I think that, however, isn't much of an API concern but more of a deployer/operator concern17:08
* cdent nods17:09
sigmavirus24That's my opinion though17:09
cdentcertainly in theory it should be an api concern (it's all just uris) but in practice that may not be true :(17:09
* sigmavirus24 thinks subdomains map better to services than other methods but that's also probably just my opinion17:09
sigmavirus24ayoung's other thing has also always been about being able to build a better horizon17:10
sigmavirus24And making the APIs work better with a pure js horizon17:10
cdentcan't full-flight CORS help with that?17:10
sigmavirus24yep17:11
cdentsigh, that should above should be shouldn't17:12
cdentI think I'm getting rather tired. Long week.17:12
cdentmeh17:12
*** e0ne is now known as e0ne_17:26
*** e0ne_ is now known as e0ne17:28
*** e0ne is now known as e0ne_17:39
*** cdent has left #openstack-api17:49
*** e0ne_ has quit IRC17:50
*** e0ne has joined #openstack-api18:00
*** e0ne has quit IRC18:03
*** e0ne has joined #openstack-api18:35
*** annegentle has quit IRC18:40
*** annegentle has joined #openstack-api18:41
*** e0ne is now known as e0ne_18:50
*** e0ne_ has quit IRC18:55
*** e0ne has joined #openstack-api18:58
*** e0ne is now known as e0ne_19:02
*** e0ne_ is now known as e0ne19:07
etoewshttps://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Errors19:27
elmikoetoews: hey, thinking about the guidelines template19:45
elmikoi'm not quite sure the best format for this, as people tend to freestyle19:45
elmikoand i don't think it would be efficient to have a template that rides alongside the actual guideline proposal19:46
etoewselmiko: when i did my guideline for errors i actually started by looking at a nova spec19:48
etoewsthis goes back to an irc meeting we had a while ago where i suggested a spec-like format for guidelines.19:48
etoewspeople were hesitant to change it mid-cycle19:49
etoewsi think we could still benefit from a more spec-like format19:49
sigmavirus24etoews: I agree19:49
elmikoetoews: ok, i like the idea of spec-like guideline but i was hesitant to create something that people might view as too heavyweight19:50
etoewsbasically just a handful of suggested sections with a small amount of verbiage describing what's expected in each section19:50
sigmavirus24the date time format guideline would have benefited from more guideance19:50
sigmavirus24yep19:50
elmikoawesome, thanks guys =)19:50
sigmavirus24also prevents the way we were moving towards clustering topics that a handful of people saw as related19:50
etoewselmiko: =)19:51
elmikomy main concern is that if we create a template that has, for lack of better term, meta-data about the guideline then we might need to strip that when presenting all the guidelines19:51
elmikoi'm not sure if that's a big concern though19:52
etoewsi'm not sure either. i was tempted to add the current design stuff to the guideline but --forward looking-- it just becomes noise.19:58
etoewssame goes for guidance on how to adopt the guide line19:59
etoewscurrently i just have it in a comment19:59
*** e0ne is now known as e0ne_20:00
*** e0ne_ is now known as e0ne20:00
*** e0ne is now known as e0ne_20:40
*** e0ne has joined #openstack-api20:41
*** e0ne is now known as e0ne_20:57
*** e0ne_ is now known as e0ne20:58
*** annegentle has quit IRC21:10
*** e0ne has quit IRC21:18
openstackgerritEverett Toews proposed openstack/api-wg: A guideline for errors  https://review.openstack.org/16779321:26
*** kaufer has quit IRC21:38
*** annegentle has joined #openstack-api22:04
*** annegentle has quit IRC23:19

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