| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2017-03-23 | |||
| 18:41:02 | ankur-gupta-f4 | wasn't planning on it. what would be easier | |
| 18:41:11 | ankur-gupta-f4 | our guys will also be introducing Octavia to the SDK as well | |
| 18:41:46 | dtroyer | SDK isn't 1.0 yet, so OSC itself isn't going to use it for anything else for a while. | |
| 18:42:20 | ankur-gupta-f4 | so then I should continue down the skeleton path where all the client bindings happen in the native python-octaviaclient lib | |
| 18:42:25 | dtroyer | eventually it should, but I'm revisiting the openstackclient.api stuff to be able to dump some of the existing lib dependencies sooner | |
| 18:42:55 | ankur-gupta-f4 | Could you comment on this then: https://review.openstack.org/#/c/448331/ to clarify | |
| 18:43:03 | dtroyer | think through the transition plan if you ever want to change that | |
| 18:43:44 | ankur-gupta-f4 | i think its mostly about getting it done at this point since we are trying to get it all done by Pike. Poor planning, but Neutron has put us on the clock | |
| 18:44:14 | ankur-gupta-f4 | also in team meeting there was a discussion about whether the namespace should be "loadbalancer" or "load balancer" | |
| 18:45:03 | dtroyer | is python-octaviaclient a thing already? | |
| 18:45:08 | ankur-gupta-f4 | indeed | |
| 18:45:19 | ankur-gupta-f4 | https://github.com/openstack/python-octaviaclient | |
| 18:45:36 | ankur-gupta-f4 | there is nothing in it yet except the stuff im trying to push up | |
| 18:46:26 | ankur-gupta-f4 | there isn't a release of it yet | |
| 18:46:29 | dtroyer | so why are you creating a stand-alone lib and also an SDK implementation? | |
| 18:47:37 | ankur-gupta-f4 | given what you have mentioned we will halt the SDK implementation I believe and just make a stand alone lib | |
| 18:47:59 | dtroyer | ok. there are a LOT of patterns in the existing client libs that should not be recreated | |
| 18:48:09 | ankur-gupta-f4 | what should be avoided | |
| 18:48:16 | dtroyer | most of it :) | |
| 18:48:38 | dtroyer | seriously, I don't know of a good reference for that | |
| 18:48:56 | ankur-gupta-f4 | okay, reword the question. How would you set it up | |
| 18:49:24 | dtroyer | look at OSC's api tree, which is based off using the KSA session directly and building a low-level API for the REST layer | |
| 18:50:29 | dtroyer | that's what I wanted in the SDK for OSC to use, if that's all you are building, that's the level you need, not the entire manager/resource mapping stuff. | |
| 18:50:48 | dtroyer | even lower level is what is in Shade | |
| 18:51:12 | dtroyer | basically, you want to write your REST client layer to take a KSA session and do things | |
| 18:53:05 | ankur-gupta-f4 | i.e. this? https://review.openstack.org/#/c/448331/2/octaviaclient/client.py | |
| 18:54:29 | dtroyer | yes, OMG, do not do that | |
| 18:54:36 | ankur-gupta-f4 | haha okay | |
| 18:55:12 | dtroyer | that's all the stuff that KSA's Session handles. OSC's ClientManager used to have to do a LOT of work to bypass all that. | |
| 18:56:00 | ankur-gupta-f4 | okay. Burn it all. Try it again seems to be the general message ;) | |
| 18:56:30 | dtroyer | look at OSC's api.objectstore stuff. That _all_ we have for the entire thing | |
| 18:56:50 | dtroyer | the command classes call that instead of swiftclient (which BTW wasn't a thing when I wrote that) | |
| 18:57:55 | ankur-gupta-f4 | looking | |
| 18:59:39 | dtroyer | the code in object_store_v1.py was largely lifted from the original swift CLI so it looks a lot different from everything else for that reason, but that's the sort of structure I would suggest you consider | |
| 19:00:35 | ankur-gupta-f4 | okay. looks simple. But object store still uses the SDK. | |
| 19:00:36 | dtroyer | Shade is even simpler, their equivalent for OSC would be to just make REST calls directly in the command take_action() methods. | |
| 19:00:48 | ankur-gupta-f4 | what is Shade? | |
| 19:01:14 | dtroyer | https://github.com/openstack-infra/shade | |
| 19:01:24 | dtroyer | infra's cross-cloud compatibility layer | |
| 19:01:38 | dtroyer | what OSC is to a CLI, Shade is to trying to use the client libs | |
| 19:02:06 | dtroyer | except that it also addresses the multitude of ways a deployer can configure clouds so the app dev doesn't have to think about that more than necessary | |
| 19:02:16 | dtroyer | as Monty says, Shade's existence is a bug. | |
| 19:04:12 | ankur-gupta-f4 | okay. Will simplify everything down to make REST calls directly to the API. Won't touch SDK for now. | |
| 19:04:50 | dtroyer | I still like the separation between cliff command classes and a Python API layer, but not much more than that. Your call though | |
| 19:05:24 | dtroyer | it lets you re-use things in multiple commands | |
| 19:05:47 | ankur-gupta-f4 | That is a call for the Octavia cores. I will be happy if I can get a 'loadbalancer list' command working soon :) | |
| 19:06:51 | dtroyer | so maybe OSC's api.image_v2 stuff is closer to what you need. but that's all they do, list() | |
| 19:10:46 | ankur-gupta-f4 | but in the octaviaclient and not OSC | |
| 19:11:44 | ankur-gupta-f4 | well lets see where this takes us | |
| 19:11:46 | ankur-gupta-f4 | thanks | |
| 19:12:26 | ankur-gupta-f4 | and since I have you dtroyer: https://review.openstack.org/#/c/382023/ is good to go | |
| 19:13:49 | dtroyer | cool | |
| 19:14:26 | ankur-gupta-f4 | Fun in the sun. Time to hop in the pool :) | |
| 19:22:58 | ankur-gupta-f4 | dtroyer: if you are still here. General question. Even without using SDK for the client. Would it be useful to add Octavia to the SDK for other use cases? | |
| 19:24:30 | dtroyer | maybe? I don't know how far briancurtin intends to extend SDK support, but I'm sure at some point an app is going to watn to talk to it | |
| 19:31:55 | ankur-gupta-f4 | briancurtin: ^^ thoughts? | |
| 19:59:16 | openstackgerrit | Ankur proposed openstack/python-openstackclient master: Add support for Octavia Plugin https://review.openstack.org/447068 | |
| 20:03:37 | openstackgerrit | Dean Troyer proposed openstack/golang-client master: Convert examples into proper stand-alone commands https://review.openstack.org/449303 | |
| 20:27:41 | openstackgerrit | Ankur proposed openstack/python-openstackclient master: Network L3 Router Commands for OSC https://review.openstack.org/385729 | |
| 20:30:15 | openstackgerrit | Merged openstack/python-openstackclient master: OSC Extension Show https://review.openstack.org/382023 | |
| 21:10:03 | openstackgerrit | Merged openstack/golang-client master: Convert examples into proper stand-alone commands https://review.openstack.org/449303 | |
| 22:14:43 | reedip | o/ | |
| 23:06:35 | openstackgerrit | Dean Troyer proposed openstack/golang-client master: Final CTI update https://review.openstack.org/449353 | |
| #openstack-sdks - 2017-03-24 | |||
| 00:47:26 | openstackgerrit | Dean Troyer proposed openstack/golang-client master: Fix gofmt issues https://review.openstack.org/449376 | |
| 00:48:14 | openstackgerrit | Dean Troyer proposed openstack/golang-client master: Final CTI update https://review.openstack.org/449353 | |
| 01:54:09 | reedip | stevemar : there > | |
| 01:54:11 | reedip | ? | |
| 02:26:25 | openstackgerrit | Huanxuan Ao proposed openstack/osc-lib master: Nit: Reorder some until methods in alphabetic order https://review.openstack.org/444086 | |
| 04:29:02 | openstackgerrit | Huanxuan Ao proposed openstack/osc-lib master: Nit: Reorder some util methods in alphabetic order https://review.openstack.org/444086 | |
| 08:12:37 | openstackgerrit | ZhangHongtao proposed openstack/python-openstackclient master: Replaces uuid.uuid4 with uuidutils.generate_uuid() https://review.openstack.org/449475 | |
| 09:25:28 | openstackgerrit | Huanxuan Ao proposed openstack/python-openstackclient master: Surport to check multi users by "group check user" https://review.openstack.org/449520 | |
| 10:41:55 | openstackgerrit | Huanxuan Ao proposed openstack/python-openstackclient master: Unified the version marks of options in OSC https://review.openstack.org/449559 | |
| 12:20:24 | reedip | o/ | |
| 12:28:30 | rabel | o/ reedip | |
| 12:28:43 | reedip | hi rabel ... :) | |
| 12:28:49 | reedip | whats up? | |
| 12:29:14 | rabel | nothing much... having fun with openstack. ;) | |
| 12:29:28 | rabel | and you? | |
| 12:30:22 | reedip | done with openstack for today ! ... just came here so that if someone needs me on a Friday Night... well... you understand | |
| 12:31:00 | rabel | :D | |
| 12:31:54 | rabel | what time is it at your place? here it is only 1:30 pm, so i have a few more hours before weekend. | |
| 12:32:08 | reedip | what abt u ? Its morning evening, afternoon or early morning ?? | |
| 12:32:42 | reedip | ohh .. so you are in Europe.. | |
| 12:32:50 | rabel | yes | |
| 12:33:04 | reedip | Well, its 8:30 here | |
| 12:33:24 | reedip | PM | |
| 12:33:37 | reedip | Phillipiness.. for the next 2 weeks.. what about u? | |
| 12:33:42 | rabel | ah, so really friday night. | |
| 12:33:59 | reedip | well yeah .... | |
| 12:34:30 | reedip | y jealous ? | |
| 12:34:32 | rabel | you're working from there? | |
| 12:34:50 | reedip | WHat else would I be doing on IRC | |
| 12:34:53 | rabel | because phillipines is sun, sea, stuff like that. ;) | |
| 12:34:54 | reedip | except work ! | |
| 12:35:10 | reedip | you can imagine then what I am doing on a friday night | |
| 12:35:14 | rabel | meeting your openstack pals on a friday nicht ;) | |
| 12:35:15 | reedip | in front of a laptop | |
| 12:35:18 | reedip | on the IRC | |
| 12:35:20 | reedip | for Openstack | |
| 12:35:56 | reedip | so you are near germany? | |