| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-08-31 | |||
| 00:19:35 | openstackgerrit | Ian Wienand proposed openstack/openstacksdk master: Switch nodepool test to containers https://review.opendev.org/748932 | |
| 11:37:57 | openstackgerrit | Yang JianFeng proposed openstack/openstacksdk master: [WIP] Add CRUD methods for Neutron router ndp proxy https://review.opendev.org/749036 | |
| 11:41:59 | openstackgerrit | Yang JianFeng proposed openstack/python-openstackclient master: [WIP] Add router ndp proxy commands https://review.opendev.org/749038 | |
| #openstack-sdks - 2020-09-01 | |||
| 17:58:07 | johnavp1989 | Hello. I'm hoping to submit a fix for this bug: https://storyboard.openstack.org/#!/story/2007710 | |
| 17:58:49 | johnavp1989 | But I'm wondering what the state of python2 support is. Does python2 support need to be implemented or has it been dropped entirely at this point? | |
| 18:33:43 | smcginnis | johnavp1989: py2 support has been dropped for all but a few projects now. openstacksdk is one that has dropped it and only support python3.6 and later. (https://opendev.org/openstack/openstacksdk/src/branch/master/setup.cfg#L15-L19) | |
| 19:38:19 | johnavp1989 | smcginnis: okay thank you | |
| 19:41:25 | openstackgerrit | John Petrini proposed openstack/openstacksdk master: Don't set list_type to dict for server groups, this is not what the API returns. https://review.opendev.org/749381 | |
| 19:59:28 | openstackgerrit | John Petrini proposed openstack/openstacksdk master: Don't set list_type to dict for server groups, this is not what the API returns. https://review.opendev.org/749381 | |
| 20:07:41 | openstackgerrit | John Petrini proposed openstack/openstacksdk master: Don't set list_type to dict for server groups, this is not what the API returns. https://review.opendev.org/749381 | |
| #openstack-sdks - 2020-09-02 | |||
| 12:52:47 | frickler | is anyone still working on microversion support for volume? I found https://review.opendev.org/695044 by dtroyer which does some preparation but what next? | |
| 13:05:49 | frickler | mordred: also is there any PTG activity planned for this team? or maybe the question should be: who's up as next ptl? :-/ | |
| 13:07:04 | frickler | slaweq: did you see my comments on 723280? I don't think we should break things for older clouds | |
| 13:41:50 | gtema | why, it's just a busy summer. | |
| 13:42:24 | slaweq | frickler: yes, I saw it but I didn't had time to change patch accordingly | |
| 13:42:25 | gtema | unfortunately there was no real work on microversions so far. And since there is no real movement since last PTG - no real topics to discuss | |
| 13:42:30 | slaweq | I will do that later this week probably | |
| 13:42:33 | slaweq | frickler: thx for review | |
| 13:42:34 | gtema | but agree, we should start planing | |
| 13:55:45 | nightmare_unreal | hello can someone take a look at these 2 patches. both are same but by different people . We need someone review to resolve this | |
| 13:55:57 | nightmare_unreal | https://review.opendev.org/#/c/740455/ , https://review.opendev.org/#/c/746405/ | |
| 13:57:49 | nightmare_unreal | both of these patches addresses the same issue. | |
| 17:24:24 | openstackgerrit | Rafael Weing채rtner proposed openstack/openstacksdk master: Introduce `schema_version` in the attribute mapping API https://review.opendev.org/749562 | |
| 17:24:24 | openstackgerrit | Rafael Weingärtner proposed openstack/openstacksdk master: Introduce `schema_version` in the attribute mapping API https://review.opendev.org/749562 | |
| 18:36:17 | openstackgerrit | Rafael Weing채rtner proposed openstack/python-openstackclient master: Introduce `schema_version` in the federated attribute mapping API https://review.opendev.org/749572 | |
| 18:36:17 | openstackgerrit | Rafael Weingärtner proposed openstack/python-openstackclient master: Introduce `schema_version` in the federated attribute mapping API https://review.opendev.org/749572 | |
| 20:26:17 | openstackgerrit | Rafael Weing채rtner proposed openstack/python-openstackclient master: Add source_ip_prefix and destination_ip_prefix to metering label rules https://review.opendev.org/749591 | |
| 20:26:17 | openstackgerrit | Rafael Weingärtner proposed openstack/python-openstackclient master: Add source_ip_prefix and destination_ip_prefix to metering label rules https://review.opendev.org/749591 | |
| 20:44:20 | openstackgerrit | Rafael Weing채rtner proposed openstack/openstacksdk master: Add source_ip_prefix and destination_ip_prefix to metering label rules https://review.opendev.org/746586 | |
| 20:44:20 | openstackgerrit | Rafael Weingärtner proposed openstack/openstacksdk master: Add source_ip_prefix and destination_ip_prefix to metering label rules https://review.opendev.org/746586 | |
| #openstack-sdks - 2020-09-03 | |||
| 00:47:32 | openstackgerrit | Brin Zhang proposed openstack/python-openstackclient master: Add server migrate list CLI https://review.opendev.org/675304 | |
| 13:38:21 | nikparasyr | hello, i've noticed that for many resources such as projects, domains etc via the openstacksdk its not possible to get the tags of these resources | |
| 13:38:48 | nikparasyr | am i missing something or is that true? is there any blueprint to implement this? | |
| 13:39:04 | gtema | not all resources support tagging (not talking that resources you refer doesn't) | |
| 13:40:32 | gtema | generally a standard way to implement this is to mixin resource.TagMixin (https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/network/v2/port.py#L17) | |
| 13:40:51 | gtema | this will enable all standard tag operations | |
| 13:41:28 | gtema | and projects do that already, so there is support for tags there | |
| 13:41:36 | gtema | https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/identity/v3/project.py#L17 | |
| 13:42:11 | nikparasyr | domains dont: https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/identity/v3/domain.py#L17 | |
| 13:42:29 | nikparasyr | which was the resource i started looking at | |
| 13:43:06 | gtema | domains do not support tags as a feature at all | |
| 13:43:19 | gtema | it's nothing SDK can do about | |
| 13:44:26 | nikparasyr | hmmmmm, i thought they did but maybe im wrong, ( i actually have tagged domains that i do via terraform -> gophercloud ) but maybe im missing something | |
| 13:45:08 | nikparasyr | i'll have a look. this is a good starting point in any case. i might come back with more questions :P. thanks a lot | |
| 13:45:48 | gtema | are you talking about identity domain or something else? | |
| 13:46:20 | gtema | since I do not see terraform managing identity domains at all | |
| 13:48:00 | nikparasyr | yes about identity domain. via tf i do this via: https://www.terraform.io/docs/providers/openstack/r/identity_project_v3.html#is_domain but i have to double check gophercloud to see exactly how they have implemented it | |
| 13:48:38 | nikparasyr | but by creating it like this i can set tags, and via cli i can see them via a openstack domain show <id> and via the sdk i cannot | |
| 13:48:39 | gtema | this is still managing a project concept, and not the domain | |
| 13:49:19 | gtema | which SDK call you use? | |
| 13:50:55 | nikparasyr | i used both: conn.identity.domains() and conn.list_domains(), given the new information im pretty sure i can scrape this info via projects() | |
| 13:51:07 | gtema | use conn.identity.projects() | |
| 13:51:19 | gtema | since in keystone there are 2 concepts: projects and domains | |
| 13:51:26 | gtema | projects support tags, domains not | |
| 13:51:45 | nikparasyr | ok. thanks a lot :) | |
| 13:51:45 | gtema | and project can be "is_domain" | |
| 13:52:02 | gtema | wlcm | |
| 15:58:25 | noonedeadpunk | hi everyone! Need some help with sdk regarding placement... I figured out that regarding placement we can only send get/post/put/etc. But not really sure I got the way to send data for post.... | |
| 15:59:32 | noonedeadpunk | sol ike hgave no issues with `conn.placement.get('/resource_providers/3088cbfe-2bd7-415d-a83e-b32cd2c1f44f') | |
| 16:00:11 | gtema | look in https://opendev.org/openstack/openstacksdk/src/branch/master/openstack/compute/v2/server.py#L231 for example of sending data with post | |
| 16:00:14 | noonedeadpunk | but not sure how conn.placement.post works, as it claims that it's Malformed JSON | |
| 16:00:19 | elmiko | API SIG office hour now open | |
| 16:00:21 | gtema | inside it is plain python requests | |
| 16:00:24 | noonedeadpunk | and no args to pass data to | |
| 16:01:08 | noonedeadpunk | gtema: will try this, thanks | |
| 16:01:31 | gtema | sad email you have sent | |
| 16:01:39 | elmiko | sorry, had to be done | |
| 16:01:49 | gtema | yes, sure. We all said that | |
| 16:02:06 | elmiko | we've done a lot of good things with this sig over the years though. i'm proud of all the contributions people have made =) | |
| 16:02:16 | gtema | great | |
| 16:02:47 | elmiko | i'm glad we finally merged the service discovery stuff though lol | |
| 16:03:21 | gtema | hehe | |
| 16:56:37 | elmiko | well, it's been a good run. thanks to everyone for their contributions =) | |
| 16:57:12 | elmiko | have a good weekend all, and stay safe out there! o/ | |
| 21:00:52 | openstackgerrit | Merged openstack/openstacksdk master: Add func test for compute microversion 2.3 https://review.opendev.org/741514 | |
| 21:05:32 | openstackgerrit | Merged openstack/openstacksdk master: Add tests for compute microversion 2.2 and 2.10 https://review.opendev.org/741295 | |
| 21:05:33 | openstackgerrit | Merged openstack/openstacksdk master: Switch nodepool test to containers https://review.opendev.org/748932 | |
| 22:01:16 | openstackgerrit | Merged openstack/python-openstackclient master: Allow openstack flavor set to update flavor description using name https://review.opendev.org/733688 | |
| #openstack-sdks - 2020-09-04 | |||
| 08:41:51 | openstackgerrit | Dmitry Tantsur proposed openstack/openstacksdk master: Fix a bogus error in config loader when using several args with dashes https://review.opendev.org/749903 | |
| 08:41:55 | dtantsur | gtema, mordred and others: could I get an urgent review of ^^^ please? it's breaking ironicclient | |
| 08:42:02 | gtema | oki | |
| 12:30:42 | openstackgerrit | Slawek Kaplonski proposed openstack/python-openstackclient master: Support tagging Neutron ports on creation https://review.opendev.org/723280 | |
| 12:44:08 | openstackgerrit | Merged openstack/openstacksdk master: Fix a bogus error in config loader when using several args with dashes https://review.opendev.org/749903 | |
| 12:44:29 | noonedeadpunk | Hey! have some weird failure for conn.compute.wait_for_server. http://paste.openstack.org/show/797474/ | |
| 12:45:02 | noonedeadpunk | If I set status='SHUTOFF' it returns server | |
| 12:45:08 | noonedeadpunk | as expected | |
| 12:45:21 | noonedeadpunk | I thought that retry should be implemented in wait_for_server? | |
| 12:45:57 | gtema | what do you want to achieve? By default wait_for will loop until defined "status" is achieved | |
| 12:46:17 | gtema | and this default state is "active" for the server | |
| 12:46:43 | noonedeadpunk | That's excactly what I need. But instead it just instantly fails if provided status != actual server status | |
| 12:47:28 | noonedeadpunk | If I don't provide statuse it fails the same way with `AttributeError: fetch` | |
| 12:47:41 | gtema | aah, now I got it | |
| 12:49:03 | noonedeadpunk | and I'm pretty sure server is valid object.... | |
| 12:49:12 | gtema | conn.get_server is currently not returning a proper resource object | |
| 12:49:22 | gtema | you instead need conn.compute.get_server | |
| 12:49:40 | gtema | then it should work | |
| 12:50:32 | gtema | those conn.get_xxx functions return mostly dict for Ansible and other users, while if you need to use deeper functions - you need to use same "layer" | |
| 12:59:34 | noonedeadpunk | gtema: ah.... | |
| 13:00:18 | noonedeadpunk | not obvious:) was just using dir() to get list of objects | |
| 13:00:22 | noonedeadpunk | TIL | |