| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2017-03-01 | |||
| 01:07:29 | thingee | dtroyer: we put that in one of the ceph commands back in the day. | |
| 01:07:54 | dtroyer | —dwim has been in more than one of my previous projects (do what I mean) | |
| 01:08:06 | thingee | don't shoot the messenger | |
| 01:55:22 | openstackgerrit | Qiming Teng proposed openstack/python-openstacksdk master: Reorganize cluster docs https://review.openstack.org/439110 | |
| 02:01:14 | openstackgerrit | jiahui.qiang proposed openstack/python-openstackclient master: Functional test for subnet https://review.openstack.org/435914 | |
| 02:22:21 | openstackgerrit | Merged openstack/python-openstackclient master: Update doc/source/command-objects/image.rst https://review.openstack.org/439142 | |
| 02:33:24 | reedip | ankur-gupta-f1 : anything to do ?? :P | |
| 02:34:07 | ankur-gupta-f4 | well I'm hoping you have slept since the last time we talked haha | |
| 02:34:30 | reedip | 2.5 hours ... enough to clear the cache ! | |
| 02:34:44 | ankur-gupta-f4 | :| | |
| 02:35:10 | ankur-gupta-f4 | you can address amotoki's comments on the set/unset for FIP on floating IP :P | |
| 02:36:18 | ankur-gupta-f4 | reedip: you also got a nit -1 on the TaaS patchsets | |
| 02:37:21 | reedip | I will do the TaaS after I reach office :) Will update the FIP one for now | |
| 02:38:45 | ankur-gupta-f4 | and quota unset. So much to do so little time haha. | |
| 02:39:08 | reedip | amotoki : I also faced the same issue with https://review.openstack.org/#/c/383025/ . After confirmation from sindhu , it was informed that the devstack needed to be updated. | |
| 02:39:42 | reedip | sindhu : care to explain the sdk_connection error in http://paste.openstack.org/show/600865/ for the patch https://review.openstack.org/#/c/383025 | |
| 02:39:45 | amotoki | reedip: what needs to be updated? | |
| 02:40:30 | amotoki | reedip: I used the version specified in upper-constraitnt.txt of openstacksdk, i.e., 0.9.13. what's the prbolem? | |
| 02:40:57 | ankur-gupta-f4 | amotoki: Will try recreating now | |
| 02:41:18 | amotoki | in addition to the above, it seems Ocata released versions of SDK and OSC have problems due to SDK API change. | |
| 02:41:33 | amotoki | for example, osc floating ip show <id> does not work. | |
| 02:41:50 | reedip | amotoki : ?? really ??? | |
| 02:42:25 | amotoki | reedip: http://paste.openstack.org/show/600867/ | |
| 02:42:56 | amotoki | I haven't checked all commands, but we have at least one :-( | |
| 02:43:14 | reedip | amotoki : As per what sindhu discussed with dtroyer, the sdk_connection error occurred due to devstack not being updated. I am waiting for sindhu's explanation for your question as I was also facing this issue in my local machine ( my devstack is older) but this issue is not occurring on the Gate | |
| 02:44:16 | amotoki | reedip: I created a new virtualenv and installed SDK and OSC, so i believe it does not apply to my case. | |
| 02:44:48 | amotoki | another strange behavior http://paste.openstack.org/show/600868/ | |
| 02:44:51 | ankur-gupta-f4 | well I'm getting "ImportError: No module named deprecation" | |
| 02:45:02 | amotoki | network list --external does not work. it lists non-external networks too. | |
| 02:45:07 | ankur-gupta-f4 | so i guess my env is broken | |
| 02:46:23 | reedip | amotoki : TL;DR , a lot of issues are now coming :) Let me try out the latest SDK and OSC and get back to you. ankur-gupta-f4 ; too little time is right :) | |
| 02:46:41 | amotoki | reedip: no problem | |
| 02:46:48 | reedip | amotoki: thanks | |
| 02:47:11 | ankur-gupta-f4 | rebuilding. but this seems like it may be a tomorrow (for me) issue. Thanks amotoki for bringing it to attention. And also good morning :) | |
| 02:47:44 | reedip | good ???? not for the CLI | |
| 02:48:53 | openstackgerrit | Reedip proposed openstack/python-openstackclient master: Introduce quota unset command https://review.openstack.org/376311 | |
| 02:50:47 | sindhu | reedip: amotoki : ok I finally found the conversation 12:16 PM |
|
| 02:51:34 | reedip | sindhu : is this the part of Openstack SDK 0.13 release? | |
| 02:52:58 | openstackgerrit | Reedip proposed openstack/python-openstackclient master: Introduce quota unset command https://review.openstack.org/376311 | |
| 02:59:31 | sindhu | reedip: I am not sure abt that. Should ask dtroyer :) | |
| 03:00:06 | reedip | Or check the latest 0.13 code and see if it exists :F | |
| 03:00:07 | reedip | :D | |
| 03:00:15 | reedip | thats the longer way | |
| 03:00:18 | ankur-gupta-f4 | check the release notes and it wud show whether patch 435735 merged | |
| 03:00:51 | ankur-gupta-f4 | wait its an OSC patch. SDK doesn't matter | |
| 03:01:29 | reedip | oops | |
| 03:09:49 | reedip | ankur-gupta-f4 : there are some issues with OSC as the upgrade to 0.9.13 didnt remove the workarounds for 0.9.12 | |
| 03:09:54 | reedip | sindhu : ^^ | |
| 03:10:33 | ankur-gupta-f4 | excellent | |
| 03:16:11 | reedip | ankur-gupta-f4 : vv This is under works | |
| 03:16:25 | openstackgerrit | Reedip proposed openstack/python-openstackclient master: Remove workarounds for 0.9.12 SDK version https://review.openstack.org/439299 | |
| 03:33:24 | openstackgerrit | Merged openstack/python-openstacksdk master: Reorganize cluster docs https://review.openstack.org/439110 | |
| 03:34:12 | openstackgerrit | Merged openstack/python-openstacksdk master: Reorganize workflow docs https://review.openstack.org/439028 | |
| 04:16:16 | openstackgerrit | OpenStack Proposal Bot proposed openstack/python-openstackclient master: Updated from global requirements https://review.openstack.org/439362 | |
| 07:40:02 | openstackgerrit | Akihiro Motoki proposed openstack/python-openstackclient master: "floating ip set/unset port" for OSC https://review.openstack.org/383025 | |
| 08:37:45 | openstackgerrit | Rikimaru Honjo proposed openstack/python-openstackclient master: Add a validation about options for server migrate command https://review.openstack.org/439451 | |
| 09:11:00 | openstackgerrit | Reedip proposed openstack/python-openstacksdk master: WIP Bulk Create support in OpenstackSDK https://review.openstack.org/439477 | |
| 09:23:54 | reedip_ | ankur-gupta-f4 , ankur-gupta-f4 : You need to update devstack , openstack-sdk installed deprecation as a requirement 14 days ago | |
| 09:24:03 | reedip_ | ankur-gupta-f1 ^^ | |
| 09:25:00 | reedip_ | amotoki : I am not facing any issue with floating ip show <id> | |
| 09:25:53 | reedip_ | checking the External Network issue ( I have updated my branch to master for SDK and OSC ) | |
| 09:27:46 | amotoki | reedip_: what versions (SDK/OSC) do you use? | |
| 09:28:00 | reedip_ | amotoki: 0.9.13, 3.8.1 | |
| 09:28:05 | reedip_ | thats as per pip freeze | |
| 09:29:13 | reedip_ | I am redeploying the devstack . And will retry the CLIs just to be doubly sure | |
| 09:37:51 | openstackgerrit | Qiming Teng proposed openstack/python-openstacksdk master: Add wait_for_xxx methods to cluster proxy https://review.openstack.org/439490 | |
| 09:48:31 | amotoki | reedip_: I checked the latest patch set locally and confirmed it works. | |
| 09:48:41 | amotoki | reedip_: one question remaining on the class name. | |
| 09:49:17 | amotoki | reedip_: currently SetFloatingIP is used for the class name. I wonder what class name is used when we have 'floating ip set' command in the future. | |
| 09:50:48 | reedip_ | amotoki : I am not sure about your query. Isnt the current Class name "SetFloatingIP" used for floating ip set CLI ? | |
| 09:52:09 | amotoki | reedip_: assume we have both 'openstack floating ip set port' and 'openstack floating ip set' in future | |
| 09:52:31 | reedip_ | amotoki : ok . Now its clear | |
| 09:52:35 | amotoki | reedip_: we currently use 'SetFloatingIP' for the former. what class name should be used for the latter. | |
| 09:53:01 | reedip_ | amotoki : how about keeping the same class name but using --port for setting the Port IP | |
| 09:54:21 | amotoki | reedip_: that is one option. | |
| 09:54:41 | amotoki | reedip_: I do not know the background why we chose 'floating ip set port' rather than 'floating ip set' | |
| 09:55:29 | reedip_ | amotoki : we had floating ip port associate/disassociate | |
| 09:55:50 | reedip_ | amotoki : but the actions ( associate /disassociate ) were not conforming with the Rules defined in OSC | |
| 09:56:00 | reedip_ | thats why it was proposed to move them to set / unset | |
| 09:56:16 | reedip_ | amotoki: but now this makes more sense to have port as optional | |
| 09:56:35 | reedip_ | amotoki: to keep floating ip set available for other operations | |
| 09:56:58 | reedip_ | amotoki : Can you send the neutronclient to OSC google sheet ???? Please :) | |
| 09:58:56 | reedip_ | amotoki: got it never mind :) | |
| 10:02:31 | amotoki | reedip_: if we choose 'floating ip set port' as command name, users can easily know what we are doing and --port is a required parameter. | |
| 10:02:47 | amotoki | reedip_: this is the merit of the current proposed command name. This is my understanding. | |
| 10:03:24 | amotoki | reedip_: do you need the link of my google spreadsheet? | |
| 10:03:30 | reedip_ | amotoki : yes, but if we remove port, and keep the --port option,( i.e. floating ip set --port) still they will know that the port is being set with the floating ip | |
| 10:03:42 | reedip_ | amotoki: I needed the link, I got it from history | |
| 10:04:00 | amotoki | reedip_: the link is pasteed in the OSC PTG page | |
| 10:04:04 | reedip_ | amotoki: I am fine with both "floating ip set port" and "floating ip set" | |
| 10:04:33 | amotoki | reedip_: honestly my current vote is 'set port' :) | |
| 10:04:33 | reedip_ | amotoki: Currently , there is no SET option in NeutronClient for Floating IP | |
| 10:04:45 | amotoki | reedip_: yeah, there is no. | |
| 10:05:00 | reedip_ | amotoki: so what we can do is , change the name of the class to SetFloatingIPPort | |
| 10:05:03 | amotoki | reedip_: we have description field now. | |
| 10:05:17 | amotoki | reedip_: it is okay to me if create command supports it later. | |
| 10:05:18 | reedip_ | amotoki: so that if there is ever a requirement in the future, we can consider it later | |
| 10:05:33 | amotoki | reedip_: okay | |
| 10:06:05 | amotoki | reedip_: it is just for curiosity. thanks for your time | |
| 10:06:27 | reedip_ | :) | |