*** annegentle has joined #openstack-api | 00:06 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 00:48 | |
*** annegentle has quit IRC | 01:14 | |
sigmavirus24 | elmiko: that's just how unittest wants the arguments | 01:14 |
---|---|---|
sigmavirus24 | elmiko: testr just uses that to appropriately print the results. unittest.TestCase.assertEqual should always be passed as expected, actual | 01:15 |
*** annegentle has joined #openstack-api | 01:17 | |
*** annegentle has quit IRC | 01:48 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 02:14 | |
*** annegentle has joined #openstack-api | 02:48 | |
*** annegentle has quit IRC | 02:54 | |
*** annegentle has joined #openstack-api | 03:50 | |
*** annegentle has quit IRC | 03:55 | |
*** annegentle has joined #openstack-api | 04:08 | |
*** annegentle has quit IRC | 04:13 | |
*** annegentle has joined #openstack-api | 05:19 | |
*** annegentle has quit IRC | 05:24 | |
*** annegentle has joined #openstack-api | 06:20 | |
*** annegentle has quit IRC | 06:25 | |
*** etoews has quit IRC | 07:29 | |
*** annegentle has joined #openstack-api | 08:22 | |
*** annegentle has quit IRC | 08:27 | |
*** e0ne has joined #openstack-api | 10:18 | |
*** annegentle has joined #openstack-api | 10:23 | |
*** annegentle has quit IRC | 10:29 | |
*** annegentle has joined #openstack-api | 11:24 | |
*** annegentle has quit IRC | 11:29 | |
*** cdent has joined #openstack-api | 11:37 | |
*** e0ne is now known as e0ne_ | 11:48 | |
*** e0ne_ is now known as e0ne | 11:49 | |
*** annegentle has joined #openstack-api | 12:22 | |
*** annegentle has quit IRC | 12:23 | |
*** kaufer has joined #openstack-api | 12:40 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 12:57 | |
*** e0ne is now known as e0ne_ | 13:03 | |
elmiko | sigmavirus24: thanks for the response, i ended up looking at the testtools.TestCase.assertEqual source | 13:03 |
elmiko | it calls out the variables as (expected, observed) | 13:03 |
*** e0ne_ is now known as e0ne | 13:11 | |
*** annegentle has joined #openstack-api | 13:24 | |
*** annegentle has quit IRC | 13:29 | |
*** kaufer has quit IRC | 13:32 | |
*** annegentle has joined #openstack-api | 13:43 | |
*** kaufer has joined #openstack-api | 13:45 | |
*** annegentle has quit IRC | 14:07 | |
*** etoews has joined #openstack-api | 14:20 | |
*** annegentle has joined #openstack-api | 14:32 | |
*** e0ne is now known as e0ne_ | 14:36 | |
*** e0ne_ is now known as e0ne | 14:48 | |
*** annegentle has quit IRC | 15:04 | |
*** annegentle has joined #openstack-api | 15:05 | |
*** fifieldt has quit IRC | 15:21 | |
openstackgerrit | Miguel Grinberg proposed openstack/api-wg: Metadata guidelines document https://review.openstack.org/141229 | 15:28 |
*** annegentle has quit IRC | 16:06 | |
*** e0ne is now known as e0ne_ | 16:20 | |
*** e0ne_ is now known as e0ne | 16:26 | |
*** e0ne is now known as e0ne_ | 16:27 | |
*** e0ne_ is now known as e0ne | 16:27 | |
etoews | looks like there's support across the board for json in the api wg repo https://review.openstack.org/#/c/167869/ | 16:45 |
etoews | considering it's not a guideline i think it's good to merge. | 16:46 |
sigmavirus24 | agreed etoews | 16:49 |
sigmavirus24 | who are our cores again? | 16:49 |
etoews | me, jaypipes, and cyeoh | 16:49 |
etoews | this is a rare case where i'm okay with a self merge | 16:50 |
etoews | i gotta ping those 2 and get them in here. | 16:50 |
sigmavirus24 | heh fair | 16:50 |
*** ChanServ sets mode: +o sigmavirus24 | 16:50 | |
*** ChanServ sets mode: -o sigmavirus24 | 16:51 | |
sigmavirus24 | I just sent cyeoh an invite via IR | 16:51 |
sigmavirus24 | *IRC but he might miss it | 16:51 |
etoews | i see him on #openstack-dev | 16:52 |
openstackgerrit | Merged openstack/api-wg: Allow JSON files for JSON Schemas and JSON examples https://review.openstack.org/167869 | 16:59 |
cdent | etoews, 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-api | 17:04 | |
etoews | cdent: do you mean in devstack | 17:04 |
etoews | ? | 17:04 |
etoews | or the world? | 17:05 |
cdent | I was thinking more general. | 17:05 |
sigmavirus24 | cdent: that's come up on the ML | 17:05 |
cdent | Obviously there are ways to do it if you tweak a bunch of knobs | 17:05 |
sigmavirus24 | I believe ayoung was working on that a lot | 17:05 |
cdent | but it is not something that is easy | 17:05 |
sigmavirus24 | I believe ayoung's idea was to have stuff like | 17:05 |
sigmavirus24 | host.com/image/images/detail/{image-id} | 17:05 |
sigmavirus24 | or host.com/horizon{/horizon's/paths/here} | 17:06 |
sigmavirus24 | host.com/compute{/nova's/stuff/here} | 17:06 |
* cdent nods | 17:06 | |
sigmavirus24 | So each service's paths would be underneath one other path | 17:06 |
sigmavirus24 | but yeah, I prefer subdomains personally for that | 17:06 |
sigmavirus24 | (Even though people were complaining about SSL certificates being harder with sub-domains) | 17:07 |
cdent | subdomains would be another reasonable way to do it, I guess | 17:07 |
cdent | less painful in terms of dealing with already-known paths | 17:07 |
sigmavirus24 | Yep | 17:07 |
sigmavirus24 | Very clear separation of concerns: images.mycloud.com and compute.mycloud.com | 17:08 |
cdent | the proliferation of ports bothers me for some reason that I can't quite explain | 17:08 |
sigmavirus24 | cdent: I get that | 17:08 |
sigmavirus24 | I think that, however, isn't much of an API concern but more of a deployer/operator concern | 17:08 |
* cdent nods | 17:09 | |
sigmavirus24 | That's my opinion though | 17:09 |
cdent | certainly 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 opinion | 17:09 | |
sigmavirus24 | ayoung's other thing has also always been about being able to build a better horizon | 17:10 |
sigmavirus24 | And making the APIs work better with a pure js horizon | 17:10 |
cdent | can't full-flight CORS help with that? | 17:10 |
sigmavirus24 | yep | 17:11 |
cdent | sigh, that should above should be shouldn't | 17:12 |
cdent | I think I'm getting rather tired. Long week. | 17:12 |
cdent | meh | 17:12 |
*** e0ne is now known as e0ne_ | 17:26 | |
*** e0ne_ is now known as e0ne | 17:28 | |
*** e0ne is now known as e0ne_ | 17:39 | |
*** cdent has left #openstack-api | 17:49 | |
*** e0ne_ has quit IRC | 17:50 | |
*** e0ne has joined #openstack-api | 18:00 | |
*** e0ne has quit IRC | 18:03 | |
*** e0ne has joined #openstack-api | 18:35 | |
*** annegentle has quit IRC | 18:40 | |
*** annegentle has joined #openstack-api | 18:41 | |
*** e0ne is now known as e0ne_ | 18:50 | |
*** e0ne_ has quit IRC | 18:55 | |
*** e0ne has joined #openstack-api | 18:58 | |
*** e0ne is now known as e0ne_ | 19:02 | |
*** e0ne_ is now known as e0ne | 19:07 | |
etoews | https://wiki.openstack.org/wiki/API_Working_Group/Current_Design/Errors | 19:27 |
elmiko | etoews: hey, thinking about the guidelines template | 19:45 |
elmiko | i'm not quite sure the best format for this, as people tend to freestyle | 19:45 |
elmiko | and i don't think it would be efficient to have a template that rides alongside the actual guideline proposal | 19:46 |
etoews | elmiko: when i did my guideline for errors i actually started by looking at a nova spec | 19:48 |
etoews | this goes back to an irc meeting we had a while ago where i suggested a spec-like format for guidelines. | 19:48 |
etoews | people were hesitant to change it mid-cycle | 19:49 |
etoews | i think we could still benefit from a more spec-like format | 19:49 |
sigmavirus24 | etoews: I agree | 19:49 |
elmiko | etoews: ok, i like the idea of spec-like guideline but i was hesitant to create something that people might view as too heavyweight | 19:50 |
etoews | basically just a handful of suggested sections with a small amount of verbiage describing what's expected in each section | 19:50 |
sigmavirus24 | the date time format guideline would have benefited from more guideance | 19:50 |
sigmavirus24 | yep | 19:50 |
elmiko | awesome, thanks guys =) | 19:50 |
sigmavirus24 | also prevents the way we were moving towards clustering topics that a handful of people saw as related | 19:50 |
etoews | elmiko: =) | 19:51 |
elmiko | my 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 guidelines | 19:51 |
elmiko | i'm not sure if that's a big concern though | 19:52 |
etoews | i'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 |
etoews | same goes for guidance on how to adopt the guide line | 19:59 |
etoews | currently i just have it in a comment | 19:59 |
*** e0ne is now known as e0ne_ | 20:00 | |
*** e0ne_ is now known as e0ne | 20:00 | |
*** e0ne is now known as e0ne_ | 20:40 | |
*** e0ne has joined #openstack-api | 20:41 | |
*** e0ne is now known as e0ne_ | 20:57 | |
*** e0ne_ is now known as e0ne | 20:58 | |
*** annegentle has quit IRC | 21:10 | |
*** e0ne has quit IRC | 21:18 | |
openstackgerrit | Everett Toews proposed openstack/api-wg: A guideline for errors https://review.openstack.org/167793 | 21:26 |
*** kaufer has quit IRC | 21:38 | |
*** annegentle has joined #openstack-api | 22:04 | |
*** annegentle has quit IRC | 23:19 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!