Jump to: navigation, search

Difference between revisions of "Meetings/KeystoneMeeting"

(Review of Keystone Blueprints for No-Spec Requires Status)
(Agenda for next meeting)
Line 16: Line 16:
 
* 3/17
 
* 3/17
 
** requirements.txt: Should requirements.txt be for the expected installation (e.g., LDAP, fernet?) or only actual requirements? - https://review.openstack.org/#/c/162360/ <code>bknudson</code>
 
** requirements.txt: Should requirements.txt be for the expected installation (e.g., LDAP, fernet?) or only actual requirements? - https://review.openstack.org/#/c/162360/ <code>bknudson</code>
 +
** db2 ci: talk about the issue of IBM DB2 CI, how to fix it and how to re-enable it. <code>yanfengxi</code>
  
 
* 3/10
 
* 3/10

Revision as of 08:40, 16 March 2015

Weekly Keystone team meeting

If you're interested in identity 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:

dolphm, ayoung, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, nkinder, lloydm, shrekuma, ksavich, hrybacki, rharwood, grantbow, vdreamarkitex, raildo, rodrigods, amakarov, ajayaa, hogepodge, breton, lhcheng, nonameentername, samueldmq, htruta, amolock, wanghong, fmarco76

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!).

  • 3/17
    • requirements.txt: Should requirements.txt be for the expected installation (e.g., LDAP, fernet?) or only actual requirements? - https://review.openstack.org/#/c/162360/ bknudson
    • db2 ci: talk about the issue of IBM DB2 CI, how to fix it and how to re-enable it. yanfengxi
  • 3/10
    • JSON Home: Support for experimental/disabled. When we approved the spec for moving away from extensions, we specified that resources might be appear as "experimental" (if they were still maturing) or "disabled" (if that features had been turned off by a config switch) in the JSON Home response. Concern, however, has been raised as to whether this is a valid way of using JSON Home. The new domain-config-database support is the first new resources to use this....before we merge its JSON Home support, let's make sure we are still happy with this approach. (henrynash)
    • keystone vs Keystone (https://review.openstack.org/#/c/162561/) breton

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)

Previous meetings

Logs and meeting summaries of previous meetings are located here.