| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2020-01-22 | |||
| 10:53:26 | openstackgerrit | Radosław Piliszek proposed openstack/js-openstack-lib master: WIP: New nodejs jobs https://review.opendev.org/702132 | |
| 11:19:44 | openstackgerrit | Sagi Shnaidman proposed openstack/ansible-collections-openstack master: Fix argument spec for os_subnet and os_zone https://review.opendev.org/703554 | |
| 11:55:59 | openstackgerrit | Merged openstack/ansible-collections-openstack master: Fix os_user_role issue to grant a role in a domain https://review.opendev.org/703428 | |
| 12:30:05 | sshnaidm | this patch needs some love: https://review.opendev.org/#/c/703342/ | |
| 19:09:47 | openstackgerrit | Radosław Piliszek proposed openstack/js-openstack-lib master: WIP: New nodejs jobs https://review.opendev.org/702132 | |
| #openstack-sdks - 2020-01-23 | |||
| 07:08:40 | openstackgerrit | Bram Verschueren proposed openstack/ansible-collections-openstack master: Add os_routers_info module https://review.opendev.org/703927 | |
| 07:26:00 | openstackgerrit | Bram Verschueren proposed openstack/ansible-collections-openstack master: fix os_user_role for groups in multidomain context https://review.opendev.org/703930 | |
| 10:56:08 | elmiko | dtantsur: is there another ansible meeting during the office hour today? | |
| 11:25:27 | dtantsur | elmiko: probably? sshnaidm? | |
| 11:26:01 | sshnaidm | elmiko, dtantsur I think as usual, ansible-sig mtg | |
| 11:26:50 | sshnaidm | I'll start it anyway, if no participants will close, 16.00 UTC | |
| 11:26:54 | elmiko | thanks dtantsur and sshnaidm | |
| 11:27:14 | dtantsur | elmiko: did you want to discuss anything re API SIG? | |
| 11:27:18 | elmiko | i am travelling currently and i might not be able to be around for the meeting | |
| 11:27:28 | elmiko | no, i don't think i have any specific topics | |
| 11:27:58 | sshnaidm | if you're here, please vote :) https://review.opendev.org/#/c/703342/ | |
| 11:28:00 | elmiko | i /still/ would like to get back to a few PRs for the guidelines, but i have not found any spare time | |
| 11:32:00 | dtantsur | same.. | |
| 11:32:08 | elmiko | ^5 | |
| 11:33:01 | elmiko | bbl o/ | |
| 11:33:48 | dtantsur | mordred, gtema, when you have time, a very simple CI fix: https://review.opendev.org/#/c/703739/ | |
| 12:00:04 | gtema | ok | |
| 12:03:57 | dtantsur | thx | |
| 12:04:05 | gtema | wlcm | |
| 12:07:43 | sshnaidm | dtantsur, how do I make clean node with SDK? that's all I found: https://docs.openstack.org/openstacksdk/train/user/proxies/baremetal.html#openstack.baremetal.v1._proxy.Proxy.set_node_provision_state | |
| 12:09:10 | dtantsur | sshnaidm: you mean, run cleaning? what exactly are you trying? | |
| 12:09:27 | sshnaidm | dtantsur, run cleaning, yes | |
| 12:10:09 | dtantsur | sshnaidm: this is the call to run manual cleaning, yes. I can help you more if you tell me the context. | |
| 12:10:33 | sshnaidm | dtantsur, I think I need a parallel to "openstack baremetal node clean " | |
| 12:10:55 | dtantsur | sshnaidm: okay, so do set_node_provision_state('clean', clean_steps=...) | |
| 12:11:10 | dtantsur | eeehhmm, missed a node, but I think you get an idea | |
| 12:14:55 | dtantsur | sshnaidm: you can ping me for any related reviews (it's actually quite encouraged) | |
| 12:15:17 | sshnaidm | dtantsur, ack, preparing now ansible module for that in tripleo | |
| 12:15:38 | dtantsur | sshnaidm: they it's even more encouraged (tripleo has a.. hmm.. known track of misunderstanding ironic ;) | |
| 12:16:19 | sshnaidm | dtantsur, traditions | |
| 12:16:33 | sshnaidm | dtantsur, it's everything :) | |
| 12:22:13 | dtantsur | :D | |
| 13:19:49 | openstackgerrit | Merged openstack/openstacksdk master: Use the bifrost bionic CI job https://review.opendev.org/703739 | |
| 14:14:19 | openstackgerrit | Hervé Beraud proposed openstack/python-openstackclient master: Incorrect title for service provider https://review.opendev.org/703600 | |
| 15:59:10 | sshnaidm | whoever is available for ansible sig meeting, in 2 minutes | |
| 15:59:34 | dtantsur | in another meeting, but lurking | |
| 16:00:25 | sshnaidm | dtantsur, mordred gtema odyssey4me mnaser | |
| 16:00:33 | sshnaidm | just pinging all from etherpad | |
| 16:00:37 | sshnaidm | dtantsur, ack | |
| 16:00:48 | sshnaidm | #startmeeting api-sig | |
| 16:00:49 | openstack | Meeting started Thu Jan 23 16:00:48 2020 UTC and is due to finish in 60 minutes. The chair is sshnaidm. Information about MeetBot at http://wiki.debian.org/MeetBot. | |
| 16:00:50 | openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | |
| 16:00:52 | openstack | The meeting name has been set to 'api_sig' | |
| 16:00:58 | odyssey4me | heh, somehow I'm in three meetings at once :) | |
| 16:01:07 | sshnaidm | who is available? | |
| 16:01:17 | gtema | me | |
| 16:01:21 | sshnaidm | if there are conflict we can change time meeting | |
| 16:01:33 | dtantsur | I'd prefer to, to be honest | |
| 16:01:52 | dtantsur | and since we're occupying the API SIG slot, we should probably set up a special meeting for our working group | |
| 16:01:58 | sshnaidm | ok, will create a poll in etherpad about a new time | |
| 16:02:02 | dtantsur | an hour earlier later would work for me, for example | |
| 16:02:07 | dtantsur | * or later | |
| 16:02:25 | dtantsur | sshnaidm: you can start a doodle or similar | |
| 16:02:34 | sshnaidm | dtantsur, yeah, good idea | |
| 16:02:43 | odyssey4me | yeah, or we could agree on a SIG meeting time... when trying to get https://review.opendev.org/697278 done I couldn't find an appropriate set time for the SIG to set the schedule | |
| 16:03:14 | dtantsur | odyssey4me: if we don't use one of the meeting channels, we can probably use any time that works for us | |
| 16:03:14 | sshnaidm | ok, we'll see in doodle which is best | |
| 16:03:46 | odyssey4me | dtantsur: yep, easy enough - I just wanted to make it easy to communicate and get updates | |
| 16:03:54 | sshnaidm | #action sshnaidm to choose better time for sig meeting | |
| 16:04:09 | sshnaidm | So, as you can know from openstack-discuss list the tranisition is in the progress. Tracking of it is in our etherpad: https://etherpad.openstack.org/p/openstack-ansible-modules | |
| 16:04:18 | sshnaidm | In these weeks I'd ask everybody for reviewes asap not to block peoples workflow, please. Take a look: https://review.opendev.org/#/c/703342/ | |
| 16:04:28 | sshnaidm | We have in CI the same job that was running before in Ansible PRs, so we're covered at least the same as before now. | |
| 16:04:44 | sshnaidm | went over all PRs in github for OS ansible modules and left a message about tranistion, but it can be still merges. We'll sync all things when modules will be removed from 2.10 completely. It will happen in next 3 weeks when ansible folks fix their sync of docs from collections. | |
| 16:04:44 | sshnaidm | Meanwhile I'll prepare these PRs in ansible github. | |
| 16:05:55 | sshnaidm | There are some issues with collection names and using them in roles/playbooks, so we'll need to mention the full collection names for now, "FQCN" | |
| 16:06:01 | sshnaidm | gtema, to your question ^ | |
| 16:06:54 | gtema | yupp. But I think once modules are removed in ansible it is fine | |
| 16:07:08 | sshnaidm | gtema, in 2.10 only though | |
| 16:07:11 | gtema | I think we also need to agree to accept new modules WITHOUT os_ prefix | |
| 16:07:44 | sshnaidm | gtema, yeah, so another requirement from ansible team was not renaming till 2.11 | |
| 16:08:06 | sshnaidm | since it can cause problems with collection and their usage, which may change any time | |
| 16:08:17 | gtema | also I will revive mordred's patch for implementing base Module class in the module_utils, it makes life easier (did this for my own collection same) | |
| 16:08:18 | sshnaidm | I think we can wait a little with renaming | |
| 16:08:43 | sshnaidm | gtema, yeah, just need to rebase it | |
| 16:08:51 | gtema | sshnaidm: ansuble guys want that in our repo we do not rename modules? | |
| 16:08:59 | gtema | i thought it was ok with BOTMETA | |
| 16:09:02 | sshnaidm | we are good now to develop new modules, we already have a few in reviews | |
| 16:09:26 | sshnaidm | gtema, it's not so easy, turns out, and things are changing fast there | |
| 16:10:00 | gtema | crap, it's like with Openshift - things are changing and thus no release possible. What are you doing there at RedHat ;-) | |
| 16:10:11 | sshnaidm | just talked this week with bcoca, Paul, gundalow on ansible-devel and to be safe it's worth to wait with renaming | |
| 16:10:12 | dtantsur | drinking | |
| 16:10:23 | gtema | that's for sure | |
| 16:10:42 | sshnaidm | gtema, yeah, it's our main purpose here :D | |
| 16:10:51 | gtema | ok, but then let's agree on accepting new modules without prefix | |
| 16:11:15 | gtema | you drink, and I am dying 4th day already | |
| 16:11:18 | sshnaidm | gtema, I'm not sure if it worth it, when finally renaming we can do it in bulk | |
| 16:11:23 | odyssey4me | sounds sensible to me, I guess the ask for preventing renames for a while is to allow a deprecation period | |
| 16:11:56 | odyssey4me | if the deprecation notice is up, but new modules don't have the prefix - then we're good | |
| 16:11:59 | sshnaidm | gtema, and to have it with os_ is keeping consistency | |
| 16:12:20 | gtema | ok, #agreed | |
| 16:12:46 | sshnaidm | so that all I have from ansible team for now | |
| 16:13:03 | gtema | what about release jobs? | |
| 16:13:05 | sshnaidm | we're good to add more tests, more jobs | |
| 16:13:14 | sshnaidm | gtema, yeah, good point | |
| 16:13:16 | gtema | I would be happy to start consuming collection from my projects | |