Jump to: navigation, search

Difference between revisions of "Meetings/KeystoneMeeting"

(Regular attendees)
(Main Agenda)
Line 14: Line 14:
 
Please add agenda items to the bottom of this section's list (be sure to include your <code>irc_handle</code>!).
 
Please add agenda items to the bottom of this section's list (be sure to include your <code>irc_handle</code>!).
  
<b>2015-11-17</b>
+
<b>2015-11-24</b>
* HMT Phase 1 & Phase 2 <code>henrynash</code>
+
* Backend driver versioning<code>henrynash</code>
** At the summit we endorsed the 2-phase approach to HMT.  Phase 1 being to store top-level domains as projects.  For phase 2 (the actually reseller case where a cloud provider, delegates part of they cloud to a reseller who in turn sells this to their own customers), the request was to investigate using Federation instead of the proposed hierarchy of projects acting as domains. The analysis of this has been carried out and was sent to the dev list (see: http://lists.openstack.org/pipermail/openstack-dev/2015-October/078063.html)
+
** We are have number of new driver versions required for Mitaka
** As outlined in the mail, I believe we cannot solve this with federation, but should implement the planned hierarchy of projects acting as domains.
+
** I have created two patches for these, which are under review (Assignment: https://review.openstack.org/#/c/242853/, and Role: https://review.openstack.org/#/c/247805/) which are under review
* New reno-based process for release notes <code>bknudson</code>
+
** From the comments, it isn't clear to me that we have a consensus of views on a) How we should be doing this (e.g. what about DB models), but more importantly WHY we are doing this (e.g. is this to ensure customer N-1 drivers still work?)
** https://review.openstack.org/#/c/244343/
+
** Let;s clarify the goals and approach.
* Online Schema Migration
 
** https://review.openstack.org/#/c/245186/
 
** https://review.openstack.org/#/c/241603/
 
* Should return the endpoints from endpoint_group when using "endpoint_filter.sql" as catalog's backend driver? <code>davechen</code>
 
** Currently, when get a project scoped token, only the endpoints from endpoint_project table will return, it's looks like to me a serious bug. But if you call API: list_endpoints_for_project, keystone will also pull out the endpoints from  endpoint_group project association.
 
** https://bugs.launchpad.net/keystone/+bug/1516469
 
  
 
==== Review of Keystone Blueprints for No-Spec Requires Status ====
 
==== Review of Keystone Blueprints for No-Spec Requires Status ====

Revision as of 08:39, 21 November 2015

Weekly Keystone team meeting

If you're interested in identity, authentication, authorization, and/or policy for OpenStack, we hold public meetings weekly on IRC in #openstack-meeting, on Tuesdays at 18:00 UTC. Please feel free to add items to the agenda below with your name and we'll cover them.

Regular attendees

Add yourself to this list to be pinged prior to each meeting:

ajayaa, amakarov, ayoung, breton, browne, davechen, david8hu, dolphm, dstanek, ericksonsantos, geoffarnold, gyee, henrynash, hogepodge, htruta, jamielennox, joesavak, lbragstad, lhcheng, marekd, morganfainberg, nkinder, raildo, rodrigods, roxanaghe, samueldmq, shaleh, stevemar, tsymanczyk, topol, vivekd, wanghong, claudiub, rderose, samleon, xek, MaxPC

Agenda for next meeting

Main Agenda

Please add agenda items to the bottom of this section's list (be sure to include your irc_handle!).

2015-11-24

  • Backend driver versioninghenrynash
    • We are have number of new driver versions required for Mitaka
    • I have created two patches for these, which are under review (Assignment: https://review.openstack.org/#/c/242853/, and Role: https://review.openstack.org/#/c/247805/) which are under review
    • From the comments, it isn't clear to me that we have a consensus of views on a) How we should be doing this (e.g. what about DB models), but more importantly WHY we are doing this (e.g. is this to ensure customer N-1 drivers still work?)
    • Let;s clarify the goals and approach.

Review of Keystone Blueprints for No-Spec Requires Status

Please add BPs to the bottom of this sections list that should be reviewed as not requiring a spec (include your irc_handle!).

Keystone Weekly Bug Reports

Bugs for the various Keystone repositories are collects and published to the following links. (lbragstad)


Roles

Please keep this as a standing topic until we have consensus on direction

Previous meetings

Logs and meeting summaries of previous meetings are located here.