Difference between revisions of "Meetings/Karbor"
< Meetings
(→Biweekly Smaug meeting) |
(→Biweekly Smaug meeting) |
||
Line 4: | Line 4: | ||
* the status of the plan | * the status of the plan | ||
**the init value of the plan status | **the init value of the plan status | ||
− | **delete and update | + | **delete and update operation of the plan, Does the status need to be validated? |
=== Agenda (2016-1-26 1400 UTC) === | === Agenda (2016-1-26 1400 UTC) === | ||
*Make an official conclusion about what plugins we'll provide. | *Make an official conclusion about what plugins we'll provide. |
Revision as of 03:09, 5 February 2016
Contents
Biweekly Smaug meeting
The Smaug project team holds a meeting in #openstack-meeting at:
- Tuesday at 1400 UTC each even week
- the status of the plan
- the init value of the plan status
- delete and update operation of the plan, Does the status need to be validated?
Agenda (2016-1-26 1400 UTC)
- Make an official conclusion about what plugins we'll provide.
- Open Issues
- whether to build task flow inside protection plugin or out side of it?
- whether restore procedure needs first import metadata from bank?
- whether checkpoint should be persisted with its brief metadata in API layer DB?
Agenda (2016-01-12 1400 UTC)
- API, Last call for comments
- Pluggable Proection Provider QA
- Protection Service tasks
- Scheduler Service Design Status
Everyone is welcome, feel free to add topics before or at the beginning of meetings.
Agenda (2015-12-22 1400 UTC)
- Smaug Overview
- Proposed Smaug API v1.0
- Open Issues
- dependency between resources: will/how smaug protect/store the attachment between volume to vm, vm to network etc.
- Scheduler service design status
- Protection service design status
- Boilerplate un-started generic infrastructure tasks
https://etherpad.openstack.org/p/smaug-bootsrap
- patches Open for review
- Base data abstraction layer
- Base Service class