| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-sdks - 2022-09-21 | |||
| 23:11:22 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Updates server_volume for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858834 | |
| 23:14:29 | opendevreview | Merged openstack/ansible-collections-openstack master: Updated network module docs https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858642 | |
| #openstack-sdks - 2022-09-22 | |||
| 04:49:41 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Bump minimum required openstacksdk release to 0.101.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858670 | |
| 05:55:07 | frickler | now I'm confused, why does the failing job on yoga use sdk from master? but maybe then it will be fixed now and we don't actually need the backport | |
| 06:11:57 | gtema | frickler, some month ago it was noticed that devstack on stable branches was using sdk from same branch and we said it was wrong. I guess back those days it was changed to be using master one | |
| 06:12:10 | gtema | and yes, I guess the fix should help | |
| 06:20:38 | frickler | hmm, o.k., maybe then sdk master should also run jobs against stable devstack to avoid such regressions | |
| 06:22:57 | gtema | oh, another 5-6 long running jobs? ;-) | |
| 06:33:01 | frickler | well the alternative is to make those jobs non-voting in devstack and essentially ignore them that way. if you want to claim that sdk is backwards compatible, you either need to test it or that claim doesn't have much substance | |
| 06:33:24 | gtema | yeah, right | |
| 07:11:46 | opendevreview | Merged openstack/ansible-collections-openstack master: Bump minimum required openstacksdk release to 0.101.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858670 | |
| 11:11:11 | opendevreview | Christian Rohmann proposed openstack/openstacksdk master: Add support for updated_at field for volume snapshots https://review.opendev.org/c/openstack/openstacksdk/+/858289 | |
| 11:19:44 | opendevreview | Bence Romsics proposed openstack/python-openstackclient master: Improve help text for network create --external https://review.opendev.org/c/openstack/python-openstackclient/+/858708 | |
| 12:26:31 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Update quota for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/851483 | |
| 13:11:31 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Updates volume for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/853749 | |
| 14:11:42 | opendevreview | Jakob Meng proposed openstack/ansible-collections-openstack master: Specifically build master in tripleo periodic job https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858760 | |
| 14:14:53 | opendevreview | Merged openstack/openstacksdk master: Add support for updated_at field for volume snapshots https://review.opendev.org/c/openstack/openstacksdk/+/858289 | |
| 14:44:56 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Updates server_volume for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858834 | |
| 14:45:25 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Updates server_volume for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858834 | |
| 16:04:38 | opendevreview | Stephen Finucane proposed openstack/python-openstackclient master: doc: Update nova command mapping https://review.opendev.org/c/openstack/python-openstackclient/+/858952 | |
| 16:24:15 | opendevreview | Artem Goncharov proposed openstack/python-openstackclient master: Conditionally skip ndp_proxy tests https://review.opendev.org/c/openstack/python-openstackclient/+/858955 | |
| 16:25:12 | gtema | frickler, jm1: I think ^^ can be used to address ndp_proxy tests of master osc with older sdk | |
| 16:53:55 | opendevreview | Merged openstack/ansible-collections-openstack master: Specifically build master in tripleo periodic job https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858760 | |
| 17:31:07 | opendevreview | Rafael Castillo proposed openstack/ansible-collections-openstack master: Updates server_volume for 2.0.0 https://review.opendev.org/c/openstack/ansible-collections-openstack/+/858834 | |
| 17:43:39 | jm1 | gtema: great :) | |
| 20:23:38 | opendevreview | Dr. Jens Harbott proposed openstack/python-openstackclient master: DNM: Test job with capped sdk https://review.opendev.org/c/openstack/python-openstackclient/+/858569 | |
| 21:07:12 | Daviey | Hi, please could some review https://review.opendev.org/c/openstack/openstacksdk/+/853703 , thanks | |
| #openstack-sdks - 2022-09-23 | |||
| 05:03:58 | frickler | gtema: o.k., that's a step forward at least. one down, two to go ;) https://zuul.opendev.org/t/openstack/build/4e67f635ac524001a010ef2fa4d46ef7 | |
| 07:12:37 | opendevreview | Merged openstack/openstacksdk master: Add support for fault object per Server API https://review.opendev.org/c/openstack/openstacksdk/+/853703 | |
| 07:19:03 | Daviey | (Thanks gtema!) | |
| 08:20:49 | opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Initialize tests of real clouds https://review.opendev.org/c/openstack/openstacksdk/+/859026 | |
| 08:47:06 | opendevreview | Jakob Meng proposed openstack/ansible-collections-openstack master: Force major version bump in pbr https://review.opendev.org/c/openstack/ansible-collections-openstack/+/859053 | |
| 08:57:57 | gtema | @frickler you are in the infra team, aren't you? | |
| 09:01:00 | frickler | gtema: pleading guilty | |
| 09:14:57 | gtema | so, back from meeting | |
| 09:15:19 | gtema | I am working on the concept of running sdk/osc functional tests against real clouds | |
| 09:15:24 | gtema | I have now creds for Cleura | |
| 09:15:43 | gtema | and I want to make non voting jobs for running those | |
| 09:16:00 | gtema | now the point (we did it in our zuul this way) | |
| 09:16:28 | gtema | in order to run this tests in check I need to define jobs in config project (meaning project-config) | |
| 09:17:25 | gtema | here I would need to put credentials of the clouds, define jobs that prepare clouds.yaml for sdk/osc (and I do this with token and not pwd to reduce chance of leak) and revokation of the token afterwards | |
| 09:18:07 | gtema | would this be accepted by infra (to put such jobs into the project-config) or we should better consider setting up a 3rdparty CI for all of that? | |
| 09:34:58 | gtema | frickler: https://review.opendev.org/c/openstack/project-config/+/859060 + https://review.opendev.org/c/openstack/openstacksdk/+/859026 are wips for that | |
| 09:54:24 | opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Initialize tests of real clouds https://review.opendev.org/c/openstack/openstacksdk/+/859026 | |
| 09:55:40 | frickler | gtema: you could put the secrets into the sdk repo, too, I'm not sure that project-config is needed for that. but I'm not sure how to circumvent the restriction that secrets can only be used in post-merge jobs | |
| 09:56:10 | frickler | also, do we need to serialize jobs? or could multiple jobs run with the same credentials in parallel? | |
| 09:56:22 | gtema | by placing them in the project-config repo, this is for sure. That way sdk would be able to use those jobs in check | |
| 09:56:56 | gtema | parallelization is a bit different question where I have no answer yet. cleanup is the similar one | |
| 09:57:09 | gtema | but first we should have some base for running them at all | |
| 09:57:52 | gtema | for the reference how we do it in our setup: | |
| 09:57:54 | gtema | https://github.com/opentelekomcloud-infra/zuul-project-config/blob/master/zuul.d/jobs.yaml#L72 | |
| 09:58:17 | gtema | and used i.e. here: https://github.com/opentelekomcloud/python-otcextensions/blob/master/.zuul.yaml#L40 | |
| 09:59:13 | gtema | in our setup zuul-project-config is also a config repo. And jobs with secrets defined in a config repo can be used in non post-review pipelines | |
| 09:59:43 | frickler | o.k., I'll have a look later. what I've done in a similar situation is use a static node that gets pre-configured with the credentials out-of-band | |
| 09:59:57 | gtema | https://zuul-ci.org/docs/zuul/latest/config/secret.html describes this | |
| 10:00:30 | gtema | Since it works for us I know for sure this way works. I am not so relaxed at placing those jobs into project-config though | |
| 10:00:54 | gtema | at minimum we would need to limit projects which can use those jobs | |
| 10:01:19 | gtema | but maintaining it this way can get out of control | |
| 10:49:44 | opendevreview | Takashi Natsume proposed openstack/python-openstackclient master: Fix wrong assertion methods https://review.opendev.org/c/openstack/python-openstackclient/+/857046 | |
| 12:25:07 | opendevreview | Merged openstack/ansible-collections-openstack master: Force major version bump in pbr https://review.opendev.org/c/openstack/ansible-collections-openstack/+/859053 | |
| 13:33:27 | opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Extend project cleanup https://review.opendev.org/c/openstack/openstacksdk/+/859087 | |
| 13:44:40 | opendevreview | Artem Goncharov proposed openstack/openstacksdk master: Extend project cleanup https://review.opendev.org/c/openstack/openstacksdk/+/859087 | |
| 14:07:39 | jm1 | gtema: oh nice, you got access to another cloud?! Never heard of Cleura before though 😅 | |
| 14:07:51 | gtema | citycloud | |
| 14:08:12 | jm1 | gtema: but i guess you still need access to rackspace, ovh and vexxhost for testing the floating ip stuff? | |
| 14:08:13 | gtema | and this uncovers quite a mess in sdk | |
| 14:08:33 | gtema | making func tests to work on various clouds is going to be a challenge | |
| 14:09:04 | gtema | but side effect is that tests and code will be improved to beter detect features of the cloud | |
| 14:12:43 | jm1 | gtema: but i guess you still need access to rackspace, ovh and vexxhost for testing the floating ip stuff? | |
| 14:12:54 | gtema | yes | |
| 14:14:11 | jm1 | we could ping fungi and ask nicely whether he would give us access to rackspace or ovh or vexxhost tenants. then we would be able to fix openstacksdk and they could remove the 0.61.0 pin.. | |
| 14:14:48 | fungi | it would need new tenants | |
| 14:15:23 | jm1 | fungi: hello fungi :) maybe you know how to get new tenants? or maybe an inofficial access for quick and dirty tests? | |
| 14:15:38 | gtema | fungi, btw any structural objections of going https://review.opendev.org/c/openstack/project-config/+/859060 way for testing? | |
| 14:15:51 | opendevreview | OpenStack Release Bot proposed openstack/python-openstackclient stable/zed: Update .gitreview for stable/zed https://review.opendev.org/c/openstack/python-openstackclient/+/859099 | |
| 14:15:52 | opendevreview | OpenStack Release Bot proposed openstack/python-openstackclient stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed https://review.opendev.org/c/openstack/python-openstackclient/+/859100 | |
| 14:15:54 | opendevreview | OpenStack Release Bot proposed openstack/python-openstackclient master: Update master for stable/zed https://review.opendev.org/c/openstack/python-openstackclient/+/859101 | |
| 14:15:54 | fungi | we already use multiple tenants to securely separate our control plane from our test nodes since different systems need automated access. we definitely wouldn't give jobs access to those, for security reasons | |
| 14:15:55 | opendevreview | OpenStack Release Bot proposed openstack/python-openstackclient master: Switch to 2023.1 Python3 unit tests and generic template name https://review.opendev.org/c/openstack/python-openstackclient/+/859102 | |
| 14:16:27 | fungi | but we could facilitate discussion with the current donor providers about getting additional tenants for sdk testing | |
| 14:16:37 | gtema | that is clear, but maybe there are some spare tenants | |
| 14:16:50 | fungi | mordred used to do that for shade, though he was manually testing it | |
| 14:17:33 | gtema | correct. We can still have this form of manual tests in particular clouds, but I would like to establish non voting jobs for various clouds | |
| 14:17:41 | jm1 | fungi: that would be awesome! we really would like to get sdk fixed :D how and where to approach them? | |
| 14:17:41 | gtema | this brings benefits to everybody | |
| 14:19:19 | jm1 | fungi: do you know people inside ovh or vexxhost or rackspace? i have really no idea of openinfra's internals so i would need some guidance here but iam willing to help :) | |
| 14:20:30 | jm1 | fungi: we need something playground for gtema before he gets bored and runs away 🙊😋 | |
| 14:21:22 | gtema | who can be bored in this world ;-) | |
| 14:26:08 | jm1 | gtema: i would get you access to our cloud if that would help. but rdo is so close to upstream that devstack jobs usually keep us happy 🤷 | |
| 14:26:49 | gtema | well, everybody is close to devstack and still we have so many issues | |
| 14:26:52 | fungi | we have a "council" which includes representatives from some of those providers, yes: https://docs.opendev.org/opendev/system-config/latest/project.html#governance | |
| 14:29:35 | jm1 | fungi: nice! you are talking about "OpenDev Council"? | |
| 14:30:18 | jm1 | gtema: you are not part of the council, are you? | |
| 14:30:25 | gtema | nope | |
| 14:31:54 | gtema | while according to the spec I should have a seat there (if I read it right) | |
| 14:32:21 | jm1 | fungi: do you and the council meet periodically? maybe gtema and i could join one time and we could discuss cloud access with providers? (in case that would be within scope of your meetings) | |
| 14:34:41 | fungi | there's no formal meeting of the council, it's more "people who self-identify as representatives of hosted projects and service donors" and the point of contact is the service-discuss@lists.opendev.org mailing list | |
| 14:35:52 | fungi | i'm officially on the council since our governance says it expressly includes "members of any OpenDev project core team" | |
| 14:36:21 | fungi | (and as a root sysadmin for the opendev collaboratory i'm also a core reviewer for most of the opendev projects) | |
| 14:36:50 | fungi | though if you're looking for a singular point of contact for the collaboratory, clarkb is our current service coordinator | |