August 2019 - openstack-discuss - lists.openstack.org

[question][placement][rest api][403]
by 崔恒香 19 Aug '19

19 Aug '19

This is my problem with placement rest api.(Token and endpoint were OK) {"errors": [{"status": 403, "title": "Forbidden", "detail": "Access was denied to this resource.\n\n Policy does not allow placement:resource_providers:list to be performed. ", "request_id": "req-5b409f22-7741-4948-be6f-ea28c2896a3f" }]} Regards, Cuihx

2 1

Some questions about contributing a golang project
by Douglas Zhang 18 Aug '19

18 Aug '19

Hello everyone, My colleagues and me have been working on an openstack admin project(like horizon, but more efficient) using Golang, and now we are willing to contribute it to openstack community. While looking through the project creators' guide [1], we have met some questions that need to be answered: As this project is written by go, it is not possible to register it on PyPI, would this have any influence? Would openstack community accept golang projects as its related projects? [1] https://docs.openstack.org/infra/manual/creators.html#give-openstack-permis… Thanks, Douglas

3 2

[all][tc] U Cycle Naming Poll
by Doug Hellmann 18 Aug '19

18 Aug '19

Every OpenStack development cycle and release has a code-name. As with everything we do, the process of choosing the name is open and based on input from communty members. The name critera are described in [1], and this time around we were looking for names starting with U associated with China. With some extra assistance from local community members (thank you to everyone who helped!), we have a list of candidate names that will go into the poll. Below is a subset of the names propsed, including those that meet the standard criteria and some of the suggestions that do not. Before we start the poll, the process calls for us to provide a period of 1 week so that any names removed from the proposals can be discussed and any last-minute objections can be raised. We will start the poll next week using this list, including any modifications based on that discussion. 乌镇镇 [GR]:Ujenn [PY]:Wuzhen https://en.wikipedia.org/wiki/Wuzhen 温州市 [GR]:Uanjou [PY]:Wenzhou https://en.wikipedia.org/wiki/Wenzhou 乌衣巷 [GR]:Ui [PY]:Wuyi https://en.wikipedia.org/wiki/Wuyi_Lane 温岭市 [GR]:Uanliing [PY]:Wenling https://en.wikipedia.org/wiki/Wenling 威海市 [GR]:Ueihae [PY]:Weihai https://en.wikipedia.org/wiki/Weihai 微山湖 [GR]:Ueishan [PY]:Weishan https://en.wikipedia.org/wiki/Nansi_Lake 乌苏里江 Ussri https://en.wikipedia.org/wiki/Ussuri_River (the name is shared among Mongolian/Manchu/Russian; this is a common Latin-alphabet transcription of the name. Pinyin would be Wūsūlǐ) 乌兰察布市 Ulanqab https://en.wikipedia.org/wiki/Ulanqab (the name is in Mongolian; this is a common Latin-alphabet transcription of the name. Pinyin would be Wūlánchábù) 乌兰浩特市 Ulanhot https://en.wikipedia.org/wiki/Ulanhot (the name is in Mongolian; this is a common Latin-alphabet transcription of the name. Pinyin would be Wūlánhàotè) 乌兰苏海组 Ulansu (Ulansu sea) (the name is in Mongolian) 乌拉特中旗 Urad https://en.wikipedia.org/wiki/Urad_Middle_Banner (the name is in Mongolian; this is a common Latin-alphabet transcription of the name. Pinyin would be Wūlātè) 东/西乌珠穆沁旗 Ujimqin https://en.wikipedia.org/wiki/Ujimqin (the name is in Mongolian; this is a common Latin-alphabet transcription of the name. Pinyin would be Wūzhūmùqìn) Ula "Miocene Baogeda Ula" (the name is in Mongolian) Uma http://www.fallingrain.com/world/CH/20/Uma.html Unicorn Urban Unique Umpire Utopia Umbrella Ultimate [1] https://governance.openstack.org/tc/reference/release-naming.html

20 59

[keystone] Keystone Team Update - Week of 12 August 2019
by Colleen Murphy 17 Aug '19

17 Aug '19

# Keystone Team Update - Week of 12 August 2019 ## News ### Feature Proposal Freeze This week is our scheduled feature proposal freeze[1], see status summary post[2]. [1] https://releases.openstack.org/train/schedule.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008549.h… ### Trusts API While implementing system scope and default roles for the trusts API we discovered an inconsistency in the error handling for the GET trust details request: most of our APIs do RBAC enforcement first thing, and return a 403 if the resource is missing so as not to divulge whether there's a record in the database for the requested resource. The GET trust details request does the database lookup first and exposes a 404 to the user if the record is missing. We discussed in the bug report[3] whether this is desireable, intended, acceptable, or dangerous behavior, and so far have converged on not fixing the issue in the interest of not breaking the API contract. If you have feelings to the contrary, please speak up in the bug report. [3] https://bugs.launchpad.net/bugs/1840288 ## Action Items * knikolla to finish initial implementation proposal of renewable group membership next week * kmalloc to finish initial implementation proposal of resource options migration next week ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. The topic for next week's office hour will be: feature proposal review - we'll walk through code implementations (if available) and answer any questions, or discuss design details if code is not available yet The location for next week's office hour will be: https://meet.jit.si/keystone-office-hours Add topics you would like to see covered during office hours to the etherpad: https://etherpad.openstack.org/p/keystone-office-hours-topics ## Open Specs Ongoing specs: https://bit.ly/2OyDLTh ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 15 changes this week, which included support for auth receipts in keystoneauth[4], the IPv6 community goal work[5], and some more changes to implement access rules in application credentials[6]. [4] https://review.opendev.org/675049 [5] https://review.opendev.org/671903 [6] https://review.opendev.org/#/q/status:merged+topic:bp/whitelist-extension-f… ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 47 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews * Train Roadmap Stories - System scope/default roles (https://trello.com/c/ERo50T7r , https://trello.com/c/RlYyb4DU) + https://review.opendev.org/#/q/status:open+topic:implement-default-roles+la… + https://review.opendev.org/#/q/status:open+topic:trust-policies + https://review.opendev.org/#/q/topic:bug/1805409 - Federated attributes for users (https://trello.com/c/dEmSumDQ) + https://review.opendev.org/#/q/status:open+topic:bp/support-federated-attr - Application credential access rules (https://trello.com/c/dJsWMI4W) + https://review.opendev.org/#/q/status:open+topic:bp/whitelist-extension-for… * Closes bugs - Honor group_members_are_ids for user_enabled_emulation https://review.opendev.org/674782 - Cleanup session on delete https://review.opendev.org/674139 - token: consistently decode binary types https://review.opendev.org/665617 * Oldest - OpenID Connect improved support https://review.opendev.org/373983 ## Bugs This week we opened 6 new bugs and closed 3. Bugs opened (6) Bug #1840288 (keystone:High) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1840288 Bug #1840291 (keystone:Medium) opened by Rabi Mishra https://bugs.launchpad.net/keystone/+bug/1840291 Bug #1840090 (keystone:Undecided) opened by Adrian Turjak https://bugs.launchpad.net/keystone/+bug/1840090 Bug #1840403 (keystone:Undecided) opened by Ariya Jantaravises https://bugs.launchpad.net/keystone/+bug/1840403 Bug #1839748 (keystoneauth:High) opened by Adrian Turjak https://bugs.launchpad.net/keystoneauth/+bug/1839748 Bug #1840235 (keystoneauth:Undecided) opened by Rabi Mishra https://bugs.launchpad.net/keystoneauth/+bug/1840235 Bugs closed (1) Bug #1840288 (keystone:High) https://bugs.launchpad.net/keystone/+bug/1840288 Bugs fixed (2) Bug #1839577 (keystone:Medium) fixed by Adrian Turjak https://bugs.launchpad.net/keystone/+bug/1839577 Bug #1839748 (keystoneauth:High) fixed by Adrian Turjak https://bugs.launchpad.net/keystoneauth/+bug/1839748 ## Milestone Outlook https://releases.openstack.org/train/schedule.html This week is feature proposal freeze week for the keystone team, which as mentioned previously is being extended for some initiatives. Oslo feature freeze is in two weeks: anything we need to complete for oslo.policy needs to be merged before then. Oslo.limit is still pre-1.0 so feature freeze won't apply to it. The PTL nomination period is also in two weeks: while I intend to run again I'm also happy to answer questions about the role if anyone wants to also put their name in. Final release for non-client libraries (keystonemiddleware, keystoneauth) is in three weeks. Feature freeze and client library freeze is in four weeks. This is also the soft string freeze and the requirements freeze and the community goals deadline. ## Shout-outs Keystoneauth now supports multi-factor authentication and auth receipts[7]. Thanks to Adrian for tackling this ahead of the library freeze deadline! [7] https://docs.openstack.org/keystoneauth/latest/authentication-plugins.html#… ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[keystone] Feature proposal freeze status
by Colleen Murphy 17 Aug '19

17 Aug '19

This week is the keystone team's feature proposal freeze week. Here's a status update for our planned features for this cycle[1]: * Add Fine Grained Restrictions to Application Credentials[2]: implementation is proposed and ready for review[3], most work is merged, some patches remaining for review, client work not started * Expiring Group Memberships Through Mapping Rules[4]: implementation not yet proposed, 1-week extension granted[5] * Explicit Domain IDs[6]: Complete[7] * Immutable Resources[8]: Implementation proposed[9], partially WIP; depends on resource options work * Resource options for all resource types[10]: implementation not yet proposed, 1-week extension granted[11] * Extend user API to support federated attributes[12]: proposed and ready for review[13] We're only holding spec work accountable to the feature proposal freeze deadline. Other roadmap features[14], including system scope and default roles work, is open for code proposals until feature freeze week. [1] http://specs.openstack.org/openstack/keystone-specs/ [2] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/ca… [3] https://review.opendev.org/#/q/topic:bp/whitelist-extension-for-app-creds [4] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/ex… [5] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008513.h… [6] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/ex… [7] https://review.opendev.org/605235 [8] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/im… [9] https://review.opendev.org/#/q/topic:immutable-resources [10] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/re… [11] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008546.h… [12] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/su… [13] https://review.opendev.org/#/q/topic:bp/support-federated-attr [14] https://trello.com/b/ClKW9C8x/keystone-train-roadmap

1 0

[keystone] Feature proposal freeze exception for resource options
by Colleen Murphy 16 Aug '19

16 Aug '19

Work is underway to implement resource options for all resources[1] but the code has not been proposed yet. Since the implementation is close to ready to review, and because immutable resources[2] depends on it, we're proposing a 1-week extension to our feature proposal freeze deadline[3]. This will also push out the work for immutable resources, but the majority of this feature has been implemented[4] and will only require a rebase on top of the resource options work. If you have any concerns about this, please let me or the team know. Colleen [1] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/re… [2] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/train/im… [3] https://releases.openstack.org/train/schedule.html [4] https://review.opendev.org/#/q/topic:immutable-resources

1 0

[goal][python3] Train unit tests weekly update (goal-4)
by Corey Bryant 16 Aug '19

16 Aug '19

This is the goal-4 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. There are 4 weeks remaining for completion of Train community goals [2]. == How can you help? == If your project has failing tests please take a look and help fix. Python 3.7 unit tests will be self-testing in Zuul. Failing patches: https://review.openstack.org/#/q/topic:python3-train +status:open+(+label:Verified-1+OR+label:Verified-2+) If your project has patches with successful tests please help get them merged. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3 -train+is:open Patch automation scripts needing review: https://review.opendev.org/#/c/666934 == Ongoing Work == Thank you to all who have contributed their time and fixes to enable patches to land. We're down to 23 projects with failing tests. == Completed Work == All patches have been submitted to all applicable projects for this goal. Merged patches: https://review.openstack.org/#/q/topic:python3-train +is:merged == What's the Goal? == To ensure (in the Train cycle) that all official OpenStack repositories with Python 3 unit tests are exclusively using the 'openstack-python3-train-jobs' Zuul template or one of its variants (e.g. 'openstack-python3-train-jobs-neutron') to run unit tests, and that tests are passing. This will ensure that all official projects are running py36 and py37 unit tests in Train. For complete details please see [1]. == Reference Material == [1] Goal description: https://governance.openstack.org/tc/goals/train/ python3-updates.html [2] Train release schedule: https://releases.openstack.org/train /schedule.html (see R-5 for "Train Community Goals Completed") Storyboard: https://storyboard.openstack.org/#!/story/2005924 Porting to Python 3.7: https://docs.python.org/3/whatsnew/3.7.html#porting-to-python-3-7 Python Update Process: https://opendev.org/openstack/governance/src/branch/master/resolutions/2018… Train runtimes: https://opendev.org/openstack/governance/src/branch/master/reference/runtim… train.rst Thanks,

1 0

[ironic][ptl] Taking a break - i.e. disconnecting for a few weeks in September
by Julia Kreger 16 Aug '19

16 Aug '19

Greetings everyone, For my own mental health and with various things that have occurred in my life these past six months, I will be disconnecting for two weeks during the month of September, starting on the 6th. To put icing on the cake, I then have business related travel the two weeks following my return that will inhibit regular IRC access during peak contributor days/hours. In my absence, Dmitry Tantsur has agreed to take care of my PTL responsibilities. This will include the time through requirements freeze and quite possibly include the creation of the stable/train branch if necessary. That being said, fear not! I still intend to run for Ironic's PTL for the next cycle! -Julia

2 1

[neutron][OVN] Instance not getting metadata
by Zufar Dhiyaulhaq 16 Aug '19

16 Aug '19

Hi, I have set up OpenStack with OVN enabled (manual install) and I can create Instance, associate floating IP and test the ping. But my Instance not getting metadata from OpenStack. I check the reference architecture, https://docs.openstack.org/networking-ovn/queens/admin/refarch/refarch.html the compute nodes should have installed ovn-metadata-agent but I don't find any configuration document about ovn-metadata-agent. I have configured the configuration files like this: [DEFAULT] nova_metadata_ip = 10.100.100.10 [ovs] ovsdb_connection = unix:/var/run/openvswitch/db.sock [ovn] ovn_sb_connection = tcp:10.101.101.10:6642 But the agent always fails. Full logs: http://paste.openstack.org/show/757805/ Anyone know whats happen and how to fix this error? Best Regards, Zufar Dhiyaulhaq

2 3

[monasca][ptl] Out of office
by Witek Bedyk 16 Aug '19

16 Aug '19

Hello everyone, I will be out of office from August 19th until 30th. In Monasca related matters please contact: Martin Chacon Piza <martindavid.chaconpiza1(a)est.fujitsu.com> Thanks Witek

1 0