| openstackgerrit | Fei Long Wang proposed openstack/zaqar-specs: Spec for more reserved queue attributes https://review.openstack.org/257622 | 00:18 |
|---|---|---|
| *** tej has quit IRC | 00:37 | |
| *** tej has joined #openstack-zaqar | 00:44 | |
| Eva-i | flwang: flwang1: ping | 00:46 |
| flwang1 | Eva-i: pong | 00:46 |
| Eva-i | flwang: how to conveniently run functional tests for python-zaqarclient? | 00:47 |
| Eva-i | flwang: for now I only know a way in which I modify tox.ini | 00:48 |
| flwang1 | export ZAQARCLIENT_AUTH_FUNCTIONAL=1 | 00:48 |
| flwang1 | then run 'nosetests -sv tests.functional' | 00:48 |
| Eva-i | flwang1: oh, thank you. =) Perhaps we can make special tox environment for functional tests. | 00:50 |
| flwang1 | generally tox use virtual env, which doesn't really work with functional test | 00:50 |
| flwang1 | at least sometimes | 00:50 |
| *** tej has quit IRC | 00:53 | |
| Eva-i | flwang1: oki | 00:55 |
| *** openstack has joined #openstack-zaqar | 01:08 | |
| Eva-i | flwang1: for me this additional env seems to work: http://pastebin.com/iydPA8S2 | 01:08 |
| flwang1 | Eva-i: ok | 01:10 |
| flwang | vkmc: any luck you around? | 01:18 |
| openstackgerrit | Fei Long Wang proposed openstack/python-zaqarclient: Add support for subscription create v2 https://review.openstack.org/249395 | 01:24 |
| Eva-i | flwang1: flwang: can I use something like {'ttl': 60, 'body': 'sexy'} as test message in functional test or it is not welcomed? | 01:49 |
| flwang1 | Eva-i: hmm... let's use something suitable for enterprise usage | 01:51 |
| flwang1 | personally, i don't think it's a good practice including some words in a formal code repo | 01:52 |
| Eva-i | flwang1: like {'ttl': 60, 'body': 'attractive'} ? | 01:52 |
| Eva-i | flwang1: oh, okay | 01:52 |
| flwang1 | {'ttl': 60, 'body': 'image.upload'} | 01:52 |
| Eva-i | #success today I stopped doing one bad practice | 01:58 |
| openstackstatus | Eva-i: Added success to Success page | 01:58 |
| *** lane_kong has joined #openstack-zaqar | 02:03 | |
| lane_kong | ping flwang, flwang1 | 02:04 |
| *** csoukup has joined #openstack-zaqar | 02:15 | |
| openstackgerrit | Eva Balycheva proposed openstack/python-zaqarclient: Fix freeze of Claim object's age property https://review.openstack.org/257649 | 02:18 |
| *** csoukup has quit IRC | 02:19 | |
| *** mdnadeem has joined #openstack-zaqar | 02:59 | |
| *** mdnadeem has quit IRC | 03:01 | |
| *** mdnadeem has joined #openstack-zaqar | 03:01 | |
| openstackgerrit | Fei Long Wang proposed openstack/python-zaqarclient: Add support for subscription create v2 https://review.openstack.org/249395 | 03:11 |
| mdnadeem | flwang: Hi good morning, | 03:16 |
| flwang1 | mdnadeem: hi | 03:17 |
| mdnadeem | can you point out what is wrong in claim patch | 03:17 |
| *** davideagnello has quit IRC | 03:17 | |
| mdnadeem | It will be helpfull to rectify it. | 03:17 |
| mdnadeem | https://review.openstack.org/#/c/213165/ | 03:18 |
| openstackgerrit | Merged openstack/python-zaqarclient: Deprecated tox -downloadcache option removed https://review.openstack.org/256717 | 03:18 |
| flwang1 | mdnadeem: did you test the patch? | 03:20 |
| flwang1 | Eva-i is testing it and found a bug | 03:20 |
| Eva-i | flwang1: flwang: I think python language is the most non-enterprize language. It's named after Monty Python and tutorials are full of spam and eggs. | 03:20 |
| Eva-i | mdnadeem: hello | 03:20 |
| mdnadeem | flwang1, No i did not test it locally, I dnt allocate a testing machine here, but i will sort out soon . | 03:21 |
| mdnadeem | Eva-i, hii | 03:21 |
| flwang1 | mdnadeem: so could you collaborate with Eva-i and work it out? i would like to try it before approve | 03:22 |
| mdnadeem | flwang1,Sure, | 03:22 |
| mdnadeem | Eva-i, may be today i will setup my machine and test it. | 03:23 |
| flwang1 | mdnadeem: thanks | 03:24 |
| flwang1 | mdnadeem: btw, can you rebase your v2 patches? | 03:24 |
| mdnadeem | flwang1, I was waiting for your patches to get merged then i rebase | 03:25 |
| mdnadeem | *your v1 patches | 03:25 |
| flwang1 | mdnadeem: oic | 03:26 |
| mdnadeem | flwang1, I request you to review this spec https://review.openstack.org/#/c/246147/, | 03:26 |
| flwang1 | we really need more core reviews :( | 03:26 |
| mdnadeem | such that we can target it to complete in M2. | 03:26 |
| flwang1 | i did | 03:26 |
| mdnadeem | Agree | 03:26 |
| flwang1 | give we basically had agreement in the weekly meeting | 03:27 |
| mdnadeem | flwang1, It need +2 to get merged | 03:28 |
| flwang1 | mdnadeem: i know :D man | 03:29 |
| mdnadeem | hahaha, | 03:29 |
| flwang1 | just commented | 03:29 |
| flwang1 | i will approve it after you posted another patch set | 03:29 |
| flwang1 | we can start to code now | 03:30 |
| flwang1 | are you going to pick any part of it? | 03:30 |
| flwang1 | mdnadeem: i don't have much bandwidth for M-2 TBH | 03:30 |
| mdnadeem | yes, as you mentioned i have already 2 patches , i will update it according to it | 03:30 |
| mdnadeem | https://review.openstack.org/#/c/238006/ | 03:31 |
| mdnadeem | https://review.openstack.org/#/c/238396/ | 03:31 |
| mdnadeem | basically, i will update these patches according to spec | 03:32 |
| flwang1 | mdnadeem: awesome, btw, pls update the commit msg of these two patches | 03:33 |
| mdnadeem | flwang1, Thanks for reminding, i will | 03:33 |
| flwang1 | thank you for the effort :) | 03:34 |
| openstackgerrit | MD NADEEM proposed openstack/zaqar-specs: HTTP put improvement for existing resource https://review.openstack.org/246147 | 03:49 |
| *** flwang1 has quit IRC | 03:49 | |
| *** david-lyle has quit IRC | 03:50 | |
| *** dmowrer has joined #openstack-zaqar | 03:54 | |
| *** david-lyle has joined #openstack-zaqar | 03:58 | |
| *** dmowrer has quit IRC | 03:59 | |
| *** david-lyle has quit IRC | 04:01 | |
| *** david-lyle has joined #openstack-zaqar | 04:02 | |
| *** boris-42_ has quit IRC | 04:13 | |
| openstackgerrit | Eva Balycheva proposed openstack/zaqar: WIP. Make zaqar-bench use credentials from os_client_config https://review.openstack.org/255051 | 04:14 |
| *** davideagnello has joined #openstack-zaqar | 04:19 | |
| *** davideagnello has quit IRC | 04:24 | |
| *** openstackstatus has quit IRC | 04:24 | |
| *** openstack has joined #openstack-zaqar | 04:25 | |
| *** openstackstatus has joined #openstack-zaqar | 04:26 | |
| *** ChanServ sets mode: +v openstackstatus | 04:26 | |
| Eva-i | mdnadeem: Fei Long asked me to figure out what tests claimsv2 patch might be missing. I think your patch is missing "tests/functional/queues/v2/test_claims.py" functional test. | 04:30 |
| mdnadeem | Eva-i, Please have a look at this https://review.openstack.org/#/c/213165/11/zaqarclient/tests/queues/claims.py | 04:33 |
| mdnadeem | it include functional test | 04:33 |
| Eva-i | mdnadeem: oki, I'm checking | 04:35 |
| mdnadeem | Eva-i, cool | 04:35 |
| Eva-i | mdnadeem: oki, I see even more little problems now. Will describe it now in the patch. | 04:46 |
| mdnadeem | Eva-i, I am setting up my system, let me test it first. | 05:10 |
| Eva-i | mdnadeem: I left you a personal message | 05:21 |
| mdnadeem | ok | 05:35 |
| Eva-i | mdnadeem: also forgot to say, when Fei Long said "Eva-i is testing it and found a bug" he meant this bug: https://bugs.launchpad.net/python-zaqarclient/+bug/1525994. This bug is not related to your claimsv2 patch, your patch just inherits this bug from zaqarclient.queues.v1.claim.Claim. | 05:55 |
| openstack | Launchpad bug 1525994 in Python client library for Zaqar "Age property of Claim object returns wrong values on subsequent calls" [Medium,In progress] - Assigned to Eva Balycheva (ubershy) | 05:55 |
| mdnadeem | Eva-i, Thanks | 06:00 |
| *** davideagnello has joined #openstack-zaqar | 06:20 | |
| *** dmowrer has joined #openstack-zaqar | 06:22 | |
| *** davideagnello has quit IRC | 06:25 | |
| *** dmowrer has quit IRC | 06:27 | |
| *** davideagnello has joined #openstack-zaqar | 08:20 | |
| *** davideagnello has quit IRC | 08:25 | |
| openstackgerrit | Shu Muto proposed openstack/python-zaqarclient: Drop py33 support https://review.openstack.org/257730 | 08:36 |
| *** openstackgerrit has quit IRC | 09:47 | |
| *** openstackgerrit has joined #openstack-zaqar | 09:47 | |
| *** davideagnello has joined #openstack-zaqar | 10:00 | |
| *** vipul has quit IRC | 10:30 | |
| *** openstackgerrit has quit IRC | 10:32 | |
| *** openstackgerrit has joined #openstack-zaqar | 10:32 | |
| *** vipul has joined #openstack-zaqar | 10:35 | |
| *** dmowrer has joined #openstack-zaqar | 11:16 | |
| *** ig0r_ has quit IRC | 11:20 | |
| *** dmowrer has quit IRC | 11:20 | |
| *** vipul has quit IRC | 11:50 | |
| *** vipul has joined #openstack-zaqar | 11:59 | |
| *** davideagnello has quit IRC | 12:34 | |
| openstackgerrit | MD NADEEM proposed openstack/python-zaqarclient: Added support to claims https://review.openstack.org/213165 | 12:36 |
| openstackgerrit | MD NADEEM proposed openstack/python-zaqarclient: Flavor show cli support for v2 https://review.openstack.org/250258 | 13:00 |
| openstackgerrit | MD NADEEM proposed openstack/python-zaqarclient: Flavor update cli support for v2 https://review.openstack.org/250253 | 13:08 |
| *** dmowrer has joined #openstack-zaqar | 13:17 | |
| *** AAzza has quit IRC | 13:19 | |
| *** AAzza has joined #openstack-zaqar | 13:19 | |
| *** AAzza has quit IRC | 13:24 | |
| *** AAzza has joined #openstack-zaqar | 13:24 | |
| *** whydidyoustealmy has joined #openstack-zaqar | 13:35 | |
| *** shakamunyi has joined #openstack-zaqar | 13:35 | |
| *** whydidyoustealmy is now known as superflyy | 13:36 | |
| *** tej has joined #openstack-zaqar | 13:47 | |
| *** dmowrer has quit IRC | 13:52 | |
| *** dmowrer has joined #openstack-zaqar | 13:53 | |
| *** sriram has joined #openstack-zaqar | 13:57 | |
| *** dmowrer has quit IRC | 13:57 | |
| *** rcernin has joined #openstack-zaqar | 14:02 | |
| *** tej has quit IRC | 14:05 | |
| *** njohnsto_ has joined #openstack-zaqar | 14:07 | |
| *** vipul has quit IRC | 14:13 | |
| *** dmowrer has joined #openstack-zaqar | 14:14 | |
| mdnadeem | vkmc: ping | 14:14 |
| vkmc | mdnadeem, pong | 14:14 |
| mdnadeem | vkmc, do you see any usecase for claim cli support? | 14:15 |
| *** dynarro has joined #openstack-zaqar | 14:15 | |
| mdnadeem | like Query Claim, renew , delete a claim | 14:15 |
| *** csoukup has joined #openstack-zaqar | 14:16 | |
| mdnadeem | https://wiki.openstack.org/wiki/Zaqar/specs/api/v1.1#Claim_Messages | 14:16 |
| vkmc | mdnadeem, well yeah | 14:16 |
| vkmc | mdnadeem, how would you manage claims otherwise? | 14:17 |
| mdnadeem | vkmc, I guess claim should use by some automated script while processing a job | 14:18 |
| *** vipul has joined #openstack-zaqar | 14:19 | |
| mdnadeem | if we claim messages by cli, it return a list of messages on terminal, which of no use untill we grep all messages by some script and process it | 14:20 |
| mdnadeem | vkmc, Sorry i know its very kiddis question, however i cant relate its use case for implemeting its cli support | 14:21 |
| mdnadeem | dynarro, ^^ any suggestion | 14:23 |
| vkmc | brb | 14:31 |
| mdnadeem | ok | 14:33 |
| Eva-i | good morning | 14:41 |
| *** tej has joined #openstack-zaqar | 14:45 | |
| ryansb | mdnadeem: yeah, that's right | 14:47 |
| *** malini has joined #openstack-zaqar | 14:48 | |
| ryansb | the use case would (most likely) be claiming some number of messages, then parsing the JSON out and doing something with the messages | 14:49 |
| *** AAzza has quit IRC | 14:51 | |
| *** mdnadeem has quit IRC | 14:52 | |
| Eva-i | mdnadeem: maybe CLI can be useful for people who can't or don't want to program on python, but know bash. | 14:52 |
| *** AAzza has joined #openstack-zaqar | 14:52 | |
| *** mdnadeem has joined #openstack-zaqar | 14:55 | |
| ryansb | or for some reason want to parse stdout instead of using the http API | 14:55 |
| ryansb | heaven knows why they'd want that | 14:55 |
| mdnadeem | Eva-i, good morning :) | 15:04 |
| *** ametts has joined #openstack-zaqar | 15:05 | |
| mdnadeem | ryansb, Sorry, i am not getting your point | 15:05 |
| mdnadeem | You mean there is no use case of cli support for claim? | 15:06 |
| ryansb | no, I'm saying there is | 15:06 |
| ryansb | I'm just saying that I'm not sure how prevalent that use case is outside "interactively playing with zaqar" | 15:07 |
| ryansb | which IS a good use case, and an important one to help people use zaqar | 15:07 |
| mdnadeem | ryansb, hmmm got it. | 15:08 |
| *** AAzza has quit IRC | 15:08 | |
| mdnadeem | make sense to me | 15:08 |
| ryansb | I just have a hard time imagining someone writing a big program in bash and using the CLI client to claim/ack messages | 15:08 |
| Eva-i | ryansb: yes, you're right | 15:09 |
| *** boris-42_ has joined #openstack-zaqar | 15:12 | |
| *** AAzza has joined #openstack-zaqar | 15:13 | |
| Eva-i | Other openstack services usually have CLI functionality for occasional operations. Most of the CLI commands are needed so rare, that they can be executed manually by human once and forgotten. That's why I think CLI interface is mostly for humans. | 15:25 |
| Eva-i | Zaqar's operations on claims are different. They're needed only on massive workloads and require automation. | 15:25 |
| *** pradk has joined #openstack-zaqar | 15:39 | |
| *** njohnsto_ has quit IRC | 15:55 | |
| *** njohnsto_ has joined #openstack-zaqar | 15:55 | |
| *** rcernin has quit IRC | 15:58 | |
| *** ametts has quit IRC | 16:07 | |
| *** davideagnello has joined #openstack-zaqar | 16:31 | |
| *** mpanetta has joined #openstack-zaqar | 16:34 | |
| *** davideagnello has quit IRC | 16:36 | |
| *** dynarro has quit IRC | 16:38 | |
| *** flwang1 has joined #openstack-zaqar | 16:41 | |
| flwang1 | vkmc: ping | 16:42 |
| Eva-i | flwang: hello | 16:44 |
| flwang1 | Eva-i: hi | 16:46 |
| flwang1 | Eva-i: btw, as for your comments in the HTTP PUT spec, if we use 409, then we will break the idempotence of PUT | 16:47 |
| flwang1 | but your point is a good point | 16:47 |
| Eva-i | flwang1: okay, then maybe 204 is better. I'm sure you have more experience with that. | 16:50 |
| flwang1 | Eva-i: it's not an easy problem :) | 16:56 |
| flwang1 | mdnadeem: around? | 17:00 |
| *** david-lyle has quit IRC | 17:02 | |
| *** malini has quit IRC | 17:11 | |
| *** david-lyle has joined #openstack-zaqar | 17:12 | |
| *** Eva-i has quit IRC | 17:13 | |
| *** davideagnello has joined #openstack-zaqar | 17:14 | |
| *** dmowrer has quit IRC | 17:25 | |
| *** tej has quit IRC | 17:25 | |
| *** davideagnello has quit IRC | 17:29 | |
| *** malini has joined #openstack-zaqar | 17:31 | |
| *** mdnadeem has quit IRC | 17:35 | |
| *** dmowrer has joined #openstack-zaqar | 17:43 | |
| *** Eva-i has joined #openstack-zaqar | 17:45 | |
| *** malini has quit IRC | 17:49 | |
| *** malini has joined #openstack-zaqar | 17:55 | |
| *** flwang1 has quit IRC | 18:11 | |
| Eva-i | flwang: ping | 18:14 |
| *** dmowrer has quit IRC | 18:37 | |
| *** malini has quit IRC | 18:45 | |
| *** tej has joined #openstack-zaqar | 18:48 | |
| *** dmowrer has joined #openstack-zaqar | 18:53 | |
| *** tej has quit IRC | 18:57 | |
| *** dmowrer has quit IRC | 18:57 | |
| *** malini has joined #openstack-zaqar | 19:00 | |
| *** dmowrer has joined #openstack-zaqar | 19:01 | |
| *** tej has joined #openstack-zaqar | 19:01 | |
| *** dmowrer has quit IRC | 19:01 | |
| *** dmowrer has joined #openstack-zaqar | 19:01 | |
| *** tej_ has joined #openstack-zaqar | 19:14 | |
| *** tej has quit IRC | 19:14 | |
| *** davideagnello has joined #openstack-zaqar | 19:29 | |
| *** openstackgerrit has quit IRC | 19:32 | |
| *** openstackgerrit has joined #openstack-zaqar | 19:32 | |
| *** davideagnello has quit IRC | 19:34 | |
| flwang | Eva-i: yes? | 19:36 |
| Eva-i | flwang: would you like to update Zaqar wiki page to make it contain information not only for RESTful API, but also for websockets? | 19:37 |
| flwang | Eva-i: it would be nice, however | 19:38 |
| Eva-i | flwang: it's too early? | 19:39 |
| flwang | i don't think wiki is a good place for api ref | 19:39 |
| flwang | we should use the offical api ref side | 19:39 |
| Eva-i | flwang: i'm not saying about api ref now | 19:39 |
| flwang | but for websocket, we can add it into developer docs | 19:39 |
| flwang | Eva-i: if so, are sure we have enough resource to do that? | 19:39 |
| *** flwang1 has joined #openstack-zaqar | 19:40 | |
| Eva-i | flwang: i'm not going to describe websocket API, just want to say that Zaqar has persistent connections feature. For now Wiki tells that Zaqar has only RESTful API and even opposes it against persistent connections which are usual. See the API section. | 19:44 |
| flwang | Eva-i: ok, got it. for that case, i'm good to add it. | 19:44 |
| flwang | just go for it | 19:44 |
| Eva-i | flwang: flwang1: just want few lines | 19:44 |
| Eva-i | flwang: flwang1: oki | 19:45 |
| flwang | Eva-i: thank you! | 19:45 |
| Eva-i | flwang: I can also tell the viewers of the wiki page, that Zaqar team is currently reworking documentation. Maybe I'll also make a small instruction on how to build docs from "doc/user-guide" by maven? | 19:47 |
| Eva-i | flwang: would you like that? | 19:48 |
| flwang | Eva-i: to get our user guide doc? | 19:49 |
| Eva-i | flwang: yes | 19:49 |
| flwang | Eva-i: i'm good | 19:50 |
| Eva-i | flwang: oki | 19:58 |
| *** tej has joined #openstack-zaqar | 20:18 | |
| *** tej_ has quit IRC | 20:20 | |
| flwang | flaper87: ping | 20:24 |
| *** malini has quit IRC | 20:45 | |
| *** tej has quit IRC | 20:45 | |
| *** dmowrer has quit IRC | 20:53 | |
| *** dmowrer has joined #openstack-zaqar | 20:56 | |
| *** dmowrer has quit IRC | 21:01 | |
| Eva-i | flwang: can I paste a some text from one of the Zaqar's specifications to wiki? Both wiki and spec have Attribution 3.0 Unported (CC BY 3.0) license. | 21:09 |
| flwang | which spec? | 21:10 |
| Eva-i | flwang: this one https://specs.openstack.org/openstack/zaqar-specs/specs/backlog/persistent-transport.html, first paragraph | 21:11 |
| *** flwang1 has quit IRC | 21:16 | |
| *** sriram has quit IRC | 21:17 | |
| *** dmowrer has joined #openstack-zaqar | 21:18 | |
| Eva-i | flwang: it's just written so good =) But, of course, I can try to explain websocket connections using my words. | 21:19 |
| *** njohnst__ has joined #openstack-zaqar | 21:21 | |
| *** dmowrer has quit IRC | 21:23 | |
| *** njohnsto_ has quit IRC | 21:25 | |
| flwang | Eva-i: i think it's ok for the copy | 21:28 |
| *** flwang1 has joined #openstack-zaqar | 21:31 | |
| *** davideagnello has joined #openstack-zaqar | 21:31 | |
| *** pradk has quit IRC | 21:33 | |
| *** davideagnello has quit IRC | 21:35 | |
| *** davideagnello has joined #openstack-zaqar | 21:39 | |
| *** david-lyle has quit IRC | 21:58 | |
| *** david-lyle has joined #openstack-zaqar | 22:00 | |
| Eva-i | flwang: I'll need to make attribution inside the Wiki for this. In the end I decided to write my own explanation... I have updated the wiki and you can see changes. | 22:05 |
| flwang1 | ok, cool | 22:07 |
| *** rcernin has joined #openstack-zaqar | 22:16 | |
| Eva-i | flwang: flwang1: I almost finished figuring out details for API reference. Tomorrow will ask Anne Gentle few last questions. | 22:22 |
| flwang | it's awesome | 22:22 |
| Eva-i | flwang: flwang1: what would you like me to focus now? | 22:22 |
| flwang | i haven't dig into the config ref work | 22:22 |
| flwang | depends on how much work left in your hand now | 22:23 |
| Eva-i | flwang: 1. some my things are waiting for approval 2. I need to finish writing two patches (and in one of them I'm stuck and don't know what to do) 3. Want to spend some time learning django and angularjs, then join development of Zaqar UI. | 22:31 |
| flwang | Eva-i: do you have a sizing in your mind for api ref work? | 22:32 |
| Eva-i | 4. If everything is smooth, start writing Zaqar API | 22:32 |
| Eva-i | flwang: we can talk now about documentation, though I don't have much information. I can say there are huge problems. | 22:33 |
| Eva-i | *I don't have all information needed | 22:33 |
| flwang | sure | 22:35 |
| *** davideagnello has quit IRC | 22:36 | |
| *** davideagnello has joined #openstack-zaqar | 22:37 | |
| flwang1 | do you have a sizing in your mind for api ref work? | 22:40 |
| Eva-i | flwang: first of all, I think our focus in this release cycle to migrate/convert some Zaqar docs to the official places is in conflict with Doc team currently striving to reorganize/convert everything. For example, now I'm starting to think it's impossible, and it's better for us to write our local API reference in .rst format for now. | 22:43 |
| flwang | Eva-i: hmm... really? | 22:43 |
| flwang | so you mean the swagger/rst work can't be done in this release? | 22:44 |
| Eva-i | flwang1: flwang: I'm not sure about it before tomorrow | 22:44 |
| flwang | ok | 22:45 |
| flwang | then, let's wait | 22:45 |
| flwang | otherwise, our discussion may be based on a wrong assumption | 22:45 |
| Eva-i | flwang1: flwang: did you read how Doc team will reoganize API ref? They want api-ref to be generated automatically from project source code. | 22:45 |
| Eva-i | flwang1: flwang: they want to extract endpoints, http methods and return codes automatically. | 22:47 |
| flwang | then it would be great and we can save much effort | 22:47 |
| flwang | Eva-i: so it would be nice if you can confirm with lana and anne if the new format will happen in Mitaka | 22:52 |
| flwang | then we can know if we should focus on this work | 22:52 |
| flwang | btw, i just checked the config ref | 22:53 |
| Eva-i | flwang: flwang1: many of OpenStack projects are using "routes" python library for wsgi. And doc team wrote a tool to extract api-related information directly from the source code which is using this library. If I'm not mistaken Zaqar is using "falcon" library for this. I'm not sure it's possible to extract API information. And if it's possible, the tool need to be written for | 22:53 |
| flwang | most of the docs now are rst formst | 22:53 |
| Eva-i | extracting API information. | 22:53 |
| flwang | that's right | 22:54 |
| flwang | we're using falcon | 22:54 |
| flwang | you said 'wrote a tool' so do you mean there is a tool already? | 22:54 |
| Eva-i | flwang: the doc team specs say that DocBook/WADL format will not be supported(be frozen) after 16 january. Then swagger/rst will come. | 22:55 |
| Eva-i | flwang: they have a prototype of this tool and it's working now with Murano project, if I understand it correctly | 22:57 |
| Eva-i | flwang: this tool is located now in this repository https://github.com/russell/fairy-slipper | 22:58 |
| Eva-i | flwang: you can try to git clone this tool, execute migrate.sh and run_server.sh to see how future API reference will look like | 22:58 |
| Eva-i | flwang: after migrate.sh you can find swagger/rst sources in created "api_doc" directory inside repository | 22:59 |
| Eva-i | flwang: these files are in the future format | 23:00 |
| *** david-lyle has quit IRC | 23:01 | |
| Eva-i | flwang: migrate.sh is now buggy and will throw some errors, but run_server will execute normally and you will be able see partial API reference. | 23:01 |
| flwang | Eva-i: good to know | 23:01 |
| *** david-lyle has joined #openstack-zaqar | 23:01 | |
| flwang | i think we may need a plugin for the tool | 23:01 |
| flwang | to support falcon | 23:01 |
| Eva-i | flwang: there is more information in this document https://github.com/russell/fairy-slipper/blob/master/doc/source/usage.rst . In the end you can find the information about this tool - controllers/routes_inspector.py. | 23:03 |
| *** mpanetta has quit IRC | 23:06 | |
| flwang | i see | 23:06 |
| flwang | Eva-i: i may need have a talk with russell | 23:07 |
| flwang | to see if it's possible to let the tool work with falcon/zaqar | 23:07 |
| Eva-i | flwang: there are other projects which do not use "routes" library for wsgi: http://specs.openstack.org/openstack/docs-specs/specs/liberty/api-site.html#proposed-change. I wonder how doc team will handle their API references. This is the first question that I want to ask tomorrow. | 23:09 |
| Eva-i | flwang: the second one is about: can Zaqar have API-reference in the official place, but without dynamic updates extracted from the code? | 23:11 |
| flwang | Eva-i: those are good questions, IMO. personally, i can't see why we can't maintain the files manually | 23:13 |
| flwang | but let's wait for the comments from anne | 23:13 |
| flwang | Eva-i: btw, as for the zaqar ui, if you want to join | 23:13 |
| flwang | you don't need much information about django and angularjs | 23:14 |
| flwang | if you know how to horizon works and some knowledge of js, then you should be able to do it | 23:14 |
| flwang | now i'm going to complete the client work asap | 23:16 |
| flwang | and then complete the config ref and zaqar UI in M-2 | 23:16 |
| Eva-i | flwang: for me Zaqar UI is the most exciting task after websocket task | 23:17 |
| flwang | Eva-i: cool | 23:17 |
| flwang | Eva-i: i think after i figure out the basic workflow, then you can just add new feature to it and it should be easy | 23:18 |
| Eva-i | flwang: yeah, I'll see some UIs from other projects also | 23:18 |
| flwang | you can just take manila ui or magnum ui as a reference | 23:19 |
| flwang | they're inspiring me :) | 23:19 |
| *** rcernin has quit IRC | 23:20 | |
| *** flwang1 has quit IRC | 23:21 | |
| Eva-i | flwang: in my life I try to not to offer any help, when I'm not sure I can fully provide it. Now I'm starting to think I made a real mistake when I offered my help for API-ref and "User Guide" which doc team decided to restructure during Mitaka. Hopefully not much time passed and maybe there's still the time someone smarter than me will take these tasks. | 23:27 |
| flwang | Eva-i: it's ok, you have done a great job | 23:30 |
| *** csoukup has quit IRC | 23:30 | |
| flwang | Eva-i: so have about we swap the tasks :) | 23:30 |
| flwang | you take the config ref | 23:30 |
| flwang | and i will talk with doc team about the api-ref work given there are many unsure things | 23:31 |
| flwang | as for the new rst format of config ref, you can refer this https://github.com/openstack/openstack-manuals/tree/master/doc/config-ref-rst | 23:31 |
| flwang | brb, lunch | 23:32 |
| Eva-i | flwang: I think it would be wonderful! | 23:32 |
| Eva-i | flwang: I want to take config-ref | 23:32 |
| *** david-lyle_ has joined #openstack-zaqar | 23:33 | |
| *** david-lyle has quit IRC | 23:36 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!