Revision as of 16:57, 2 June 2014

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

• June 2, 2014
  • Hacking enabled on pep8 gate
  • New barbican-specs repository

• 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.
    • https://blueprints.launchpad.net/barbican/+spec/add-wrapping-key-to-barbican-server

• 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

• April 7, 2014
  • malini - update on Secuirty Guide documentation
  • alee_/atiwari - Crypto plugin changes
  • arunkant - Target support in barbican policy enforcement [1]
  • jraim - Support for debug mode start in barbican [2], can be merged?

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