April 2020 - openstack-discuss - lists.openstack.org

Retire openstack/networking-ovn
by Maciej Jozefczyk 21 Apr '20

21 Apr '20

Hello, During Ussuri cycle code from openstack/networking-ovn repository has been moved to openstack/neutron [1]. Neutron team will not accept any new changes to openstack/networking-ovn repository and we should retire this project. Patches are pushed with the topic:retire-networking-ovn <https://review.opendev.org/#/q/topic:retire-networking-ovn+(status:open+OR+…>, starting at [2]. [1] https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge [2] https://review.opendev.org/#/c/721565/ -- Best regards, Maciej Józefczyk

2 3

[Watcher]IRC meeting on April 22
by licanwei 21 Apr '20

21 Apr '20

Hi, Tomorrow at 08:00 UTC on #openstack-meeting-alt. pls update the meeting agenda if you have something want to be discussed. Thanks, | | licanwei_cn | | 邮箱：licanwei_cn(a)163.com | 签名由网易邮箱大师定制

1 0

[tc] Self-nominations (or non-nominations) for TC Chair
by Jean-Philippe Evrard 20 Apr '20

20 Apr '20

Hello everyone, As we already have multiple candidates for chairing the TC candidates, we'll need to run some elections (create a poll), it will be easier than to vote on the multiple candidacies in governance. But before I can proceed ahead, I need the full list of candidates. As I haven't seen the reply from everyone in the tc channel, we'll need to have a nomination period. If you're interested to be the chair of the TC, please propose a patch in governance before Monday April 20, 2020 at 1100 UTC. If you don't intend to run, please also tell me: if I have answers from all the tc members before Monday (I already know the plans for mnaser, mugsie, evrardjp, njohnston, knikolla), we can proceed earlier. I will proceed with a private poll to your email addresses mentioned in governance repo. I am not specialist in civs, though, so any help is welcomed. The poll results will be as much anonymous as possible, and I will publish the anonymized results over the ML, as we did previously. Good luck to the candidates! Regards, Jean-Philippe Evrard (evrardjp)

1 2

[tc][congress] Retiring the Congress project
by Nate Johnston 20 Apr '20

20 Apr '20

Recently the TC has worked on determining the criteria for when an OpenStack project should be retired. When there was not a PTL nominee, that triggered the TC to review the health of the Congress project per [1], and the TC has determined [2] that development work on the Congress project has ceased. Based on that we are going to start the process of governance removal in the Victoria cycle as specified in the Mandatory Repository Retirement resolution [3] and detailed in the infra manual [4]. Pursuant to these procedures, Congress will move out of the opendev.org/openstack/ namespace and into the opendev.org/x/ namespace. If interest in Congress revives, development can restart in it's new location and potentially Congress could be re-added to OpenStack governance. Our thanks and appreciation to Eric and all of those who have contributed to the Congress project over the years. Thanks, Nate Johnston [1] https://governance.openstack.org/tc/reference/dropping-projects.html [2] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/latest.log.html#t202… [3] https://governance.openstack.org/tc/resolutions/20190711-mandatory-reposito… [4] https://docs.opendev.org/opendev/infra-manual/latest/drivers.html#retiring-…

2 2

[tc] TC Meeting time for Victoria cycle Leaderless projects discussions
by Ghanshyam Mann 20 Apr '20

20 Apr '20

Hello Everyone, As you know, PTL election is finished for the Victoria cycle and we have 6 projects without PTL nomination and 1 project with two late candidiacy[1]. TC will hold the two adhoc meetings for the leadership or the next plan discussions for these projects on IRC #openstack-tc channel. 1. April 20th: 3PM-4PM UTC 2. April 21th: 3PM-4PM UTC [1] https://etherpad.opendev.org/p/victoria-leaderless -gmann

1 0

OpenStack Murano "yaql" error
by İzzettin Erdem 20 Apr '20

20 Apr '20

Hello folk, Is there anyone who used murano before? I am trying to install Murano on devstack stable/train release. When i try to deploy an environment, it throws an error. At murona-engine logs error is: "func.__yaql_function__ = fd: murano.dsl.dsl_exception.MuranoPlException: [AttributeError]: 'method' object has no attribute '__yaql_function__'" Any suggestioıns? Thanks. Regards.

1 0

[keystone][horizon][keycloak] Custom error page possible?
by Paweł Cituk 20 Apr '20

20 Apr '20

Hi All, openstack version: Stain keycloak version: 8.0.0 I have configured keystone+horizon to use SSO (Keycloak). In Keycloak database there are two sorts of users: 1. Those who have attribute "domain" which is mapped into openstack's domain 2. Those who do not have this attribute If Keycloak's user without attribute "domian" or it is a non-existent user in keystone, is successfully authenticated (in Keycloak) then keystone returns json: {u'error': {u'message': u'The request you have made requires authentication.', u'code': 401, u'title': u'Unauthorized'}} How to configure keystone to return more user friendly error page (custom one)? If it's possible, then what about other services which they parse this reponse? Regards, Pawel

1 0

Edge sessions on the virtual PTG - ACTION NEEDED
by Ildiko Vancsa 20 Apr '20

20 Apr '20

Hi, I’m reaching out to you as I’m organizing the sessions for the OSF Edge Computing Group to go through edge related topics that are in interest on the official schedule[2] of the virtual PTG[1]. As this area is relevant for several OpenStack projects as well it would be great to have contributors of these projects attending the edge sessions and contribute to our discussions including cross-project collaboration related items. The working group members are currently considering to book three blocks (~2 hours) to cover reference architecture and testing discussions as well as topics that are in interest for cross—project collaboration. More details are on our PTG planning etherpad[3]. I created a Doodle poll[4] with time slots that are doable around the globe. Please __fill it out as soon as you can__ if you are interested in joining. The current approach is to look into the most popular slot to turn it into a cross-project discussion as well as booking the three most popular slots overall to cover the aforementioned topics. Please let me know if you have any questions. Thanks and Best Regards, Ildikó [1] http://lists.openstack.org/pipermail/edge-computing/2020-April/000699.html [2] https://ethercalc.openstack.org/126u8ek25noy [3] https://etherpad.opendev.org/p/ecg_virtual_ptg_planning_june_2020 [4] https://doodle.com/poll/gpd4hg6ambryi8c9

1 1

[all] Lower-constraints in some projects broken - update your repos
by Andreas Jaeger 20 Apr '20

20 Apr '20

Lower-constraints should test that the minimal requirements work together. The way we use the install-command in tox.ini, pip often ignores the constraints and install a newer package then requested. First Example: cloudkitty (see [1], [2] ,[3] , [4]) The repo has: install_command = pip install -c{env:UPPER_CONSTRAINTS_FILE:https://releases.openstack.org/constraints/upper/master} {opts} {packages} and in lower-constraints.txt: "python-keystoneclient==1.9.0" And this runs the test with "keystoneclient==4.0.0" [1] Removing the install_command [3] or moving constraints from install_command into deps [2] gives "ERROR: Could not find a version that satisfies the requirement python-keystoneclient==1.9.0" So, this works as expected - but means this repo never tested what it expected to test. Second example: kolla-cli [5] Removing the install_command with constraints, suddenly lower-constraints fails with: "Could not find a version that satisfies the requirement mypy==0.6" Same problem as with cloudkitty. I fear that every repo that has constraints in its install_command has broken lower-constraints file. Just remove it and see that nothing works anymore ;/ Therefore, I suggest for repos to remove install_command - the default is just fine in newer tox (3.x) - and fix their lower-constraints.txt to really test that the specified package versions work together. Information about lower-constraints.txt is at [6], Andreas References: [1] https://review.opendev.org/720767 [2] https://review.opendev.org/720768 [3] https://review.opendev.org/720770 [4] https://review.opendev.org/720775 [5] https://review.opendev.org/#/c/720754/3 [6] https://docs.openstack.org/project-team-guide/dependency-management.html -- Andreas Jaeger aj(a)suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB

6 22

[barbican] Question about container policy rule:container_acl_read
by Krzysztof Pawłowski 19 Apr '20

19 Apr '20

Hi, I have a question about policy for container consumers. Am I correctly understanding that the below policy in code should allow users with read acl to create consumer for container? policy.DocumentedRuleDefault( name='consumers:post', check_str='rule:admin or rule:container_non_private_read or ' + 'rule:container_project_creator or ' + 'rule:container_project_admin or rule:container_acl_read', scope_types=[], description='Creates a consumer.', operations=[ { 'path': '/v1/containers/{container-id}/consumers', 'method': 'POST' } ] ), policy.RuleDefault( name='container_acl_read', check_str="'read':%(target.container.read)s"), It's not working for me and I want to be sure if I'm doing something wrong or it's designed to work other ways. My current solution is below policy to allow role 'creator' to update consumers: {"consumers:post": "rule:admin or rule:creator or rule:container_non_private_read or rule:container_project_creator or rule:container_project_admin or rule:container_acl_read"} Greets, Krzysztof Pawłowski

1 0