Difference between revisions of "Meetings/Barbican"
< Meetings
(→Agenda) |
(→Agenda) |
||
| Line 11: | Line 11: | ||
== Agenda == | == Agenda == | ||
* January 5, 2015 | * January 5, 2015 | ||
| − | ** Quota BP | + | ** Kilo 1 Released [redrobot] |
| + | ** Quota BP [redrobot] | ||
* December 15, 2014 | * December 15, 2014 | ||
Revision as of 18:18, 5 January 2015
Weekly Barbican Meeting
The Barbican project team holds a weekly team meeting in #openstack-meeting-alt:
- Weekly on Mondays at 2000 UTC
- The blueprints that are used as a basis for the Barbican project can be found at https://blueprints.launchpad.net/barbican
- Notes for previous meetings can be found here.
- Chair (to contact for more information): jraim (#openstack-barbican @ Freenode)
Agenda
- January 5, 2015
- Kilo 1 Released [redrobot]
- Quota BP [redrobot]
- December 15, 2014
- Barbican Mid-Cycle [redrobot]
- December 8, 2014
- Integration Docs [redrobot]
- Bugs [redrobot]
- Castellan [redrobot]
- Content types [rellerreller]
- Any feedback on etherpad page, https://etherpad.openstack.org/p/barbican-formats-discussion?
- December 1, 2014
- Consider video conference to discuss and hopefully land our many outstanding blueprints
- November 24, 2014
- Validation for Typed Container data (Certificates, etc) [rm_work]
- Castellan scope: include CertMgr / ContainerMgr support? [rm_work]
- Content type
- November 17, 2014
- RFC 7030
- See Ade's notes - https://etherpad.openstack.org/p/thoughts_on_certs
- New Key Manager library (Castellan)
- RFC 7030
- November 10, 2014
- New Core Reviewers
- RFC 7030
- October 27, 2014
- Kilo Design Sessions
- Atalla ESKM Plugin
- Barbican T-Shirts
- October 6, 2014
- Kilo development is open
- Sep 29, 2014
- Juno RC1
- CR https://review.openstack.org/#/c/110817/ review and merge before Juno final?
- Kilo Design Sessions
- Juno RC1
- Sep 22, 2014
- (woodster) Added 'How should we handle content type for secrets' block to Kilo design discussion etherpad.
- Sep 15, 2014
- jenkins.cloudkeep.io
- Metadata Storage: https://etherpad.openstack.org/p/barbican_metadata
- API Stability
- Documentation sync up with new API
- (woodster) Juno roadmap addition: Refactor Barbican python client to use new Keystone auth components
- (woodster) Various additions made to the Kilo design etherpad.
- Need someone to look at https://review.openstack.org/#/c/118697/ comment from Nathan. Based on vote I made this change.
- Sep 8, 2014
- Kilo Design Sessions
- Juno roadmap discussions: https://etherpad.openstack.org/p/barbican-juno-final-roadmap
- Sep 1, 2014
- Kilo Design Sessions
- Aug 25, 2014
- CR Sizes (jvrbanac)
- String interpolation in debug logging (redrobot, rellerreller)
- Python 3 support (rellerreller)
- Aug 18, 2014
- Juno Home Stretch (woodster)
- Aug 11, 2014
- Barbican Integration
- Barbican as a Keystone service
- Aug 4, 2014
- #openstack-barbican on eavesdrop
- July 28, 2014
- Add more type in order post (https://review.openstack.org/#/c/87405/) waiting for review.
- Kilo conference presentation submissions
- July 21, 2014
- (redrobot) Expiring Launchpad BPs after 5 days
- July 14, 2014
- barbican-core nominations vote count
- can we plan better to make such change https://review.openstack.org/#/c/103431?
- python-barbicanclient release schedule
- June 30, 2014
- Mid-cycle meetup next week
- Keystone events blueprint
- (atiwari) https://review.openstack.org/#/c/98174/ (Do we need to worry about backward compatibility?)
- June 23, 2014
- Mid-cycle meetup in two weeks.
- June 16, 2014
- Mid-cycle meetup
- June 9, 2014
- barbican-specs repo
- juno-1 release coming up
- mid-cycle meetup
- https://review.openstack.org/#/c/98473 (is it merge ready? kind of blocker)
- https://review.openstack.org/#/c/97844/ (is it merge ready?)
- https://review.openstack.org/#/c/98174 (is it merge ready?)
- Testing code pattern
- Any progress on eventing system (atiwari).
- Can tenant_id removal from uri deserve v2 api version(atiwari).
- June 2, 2014
- Hacking enabled on pep8 gate
- New barbican-specs repository
- Order model changes for https://blueprints.launchpad.net/barbican/+spec/api-orders-add-more-types
- New field "meta of type JsonBlob" and "container_id of type String"
- Meera is adding Barbican tempest tests https://blueprints.launchpad.net/tempest/+spec/add-basic-tests-for-barbican
- Comments, Suggestions or disagreement?
- May 5, 2014
- https://review.openstack.org/#/c/82189/ (is it merge ready?)
- https://review.openstack.org/#/c/88463/ (review required- API change proposal Key generation)
- https://review.openstack.org/#/c/81310/ (review required- Adding target support for policy enforcement.)
- https://review.openstack.org/#/c/90613/ (review required- API change proposal certificate generation order)
- The Advanced Services Common Requirements team wanted to discuss the current status of the Barbican and its readiness to utilize the Barbican for Certificate/key generation and for storing the tenant's certificates sercurely in the system.
- Can we get an update or talk about this in today's meeting.
- April 28, 2014
- Action items:
- all: Review/contribute to Malini's etherpad: https://etherpad.openstack.org/p/juno-key-manager-chapter
- all: Review atiwari's CR to modify the crypto plugin interface: https://review.openstack.org/#/c/82189/
- core: Consider beefing up barbican docs related to current crypto plugin operation, as prep for the OpenStack summit
- Action items:
- April 7, 2014
Meeting organizers
- Publish the agenda 24h in advance
- Mail the agenda to the list and invite participants
- Ask each person responsible for an action from the previous meeting to prepare a line of the form, for each action item: . #info nickname description of the action link to the diff / mailing list thread etc. describing the implementation of the action
- Use http://meetbot.debian.net/Manual.html to get an automatic summary
- Prepare an outline for the meeting to speed things up (see http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-10-16.00.log.html for an actual example)
- Record decisions and commitments; review in the next meeting
