Jump to: navigation, search

Difference between revisions of "Meetings/Karbor"

(Agenda(2016-12-06 0900 UTC))
(Agenda (2017-08-29 0900 UTC))
(47 intermediate revisions by 6 users not shown)
Line 9: Line 9:
 
* Additional [http://eavesdrop.openstack.org/meetings/smaug/ summaries] before project rename
 
* Additional [http://eavesdrop.openstack.org/meetings/smaug/ summaries] before project rename
  
=== Agenda(2016-12-06 0900 UTC) ===
+
=== Agenda (2017-09-26 0900 UTC) ===
* About the operation_logs API (chenying)
+
* Adding more protection parameters retention period
** state in operation_logs have several values (running/finished/failed)
+
  (https://review.openstack.org/#/c/498193/)
** "finished" means  protection restAPI is called successfully or the protection action have been done successfully
 
 
 
 
 
* Open discussion
 
 
 
=== Agenda(2016-11-29 1500 UTC) ===
 
* Open discussion
 
 
 
=== Agenda(2016-11-22 0900 UTC) ===
 
* Open discussion
 
 
 
=== Agenda(2016-11-15 1500 UTC) ===
 
*Multi-tenant Isolation in Managing the Checkpoints(leon_wang)
 
**Spec is at https://review.openstack.org/#/c/372846/
 
* Protection Plugin API: https://review.openstack.org/397156 and https://review.openstack.org/348163
 
* Open discussion
 
 
 
=== Agenda(2016-11-08 0900 UTC) ===
 
* Adding Karbor into Kolla and implementing container deployment (xiangxinyong)
 
* Karbor integrated with Freezer Plan (xiangxinyong)
 
* Open discussion
 
 
 
=== Agenda(2016-11-01 1500 UTC) ===
 
 
 
*Checkpoint API -- Partial Delete
 
**Add support to select which entities to delete, multiple entities backup copies from a plan.
 
**The scene:
 
**The user create a plan with several volumes. These volumes don't have any relationships.
 
**Add these resources to one plan, the user just want to protect them at the same time point.
 
**So he have a request that operating the backup copies in one checkpoint separately.
 
**
 
**After creating a plan with volumes, then the user do a backup acton with this plan using
 
**create checkpoint API. Every volume produces a backup copy. The user only want to delete
 
**one or port of backup copies produced from one checkpoint about the plan.
 
 
 
*Open discussion
 
 
 
=== Agenda(2016-10-11 0900 UTC) ===
 
* Barcelona design summit
 
**https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=karbor
 
**https://etherpad.openstack.org/p/karbor-ocata-design-summit-topics
 
* Add patch list in etherpad to improve the efficiency of reviewing/merging patches (zengchen)
 
**https://etherpad.openstack.org/p/karbor-ocata-reviews
 
* Questions about algorithm of building resource graph (zengchen)
 
**http://lists.openstack.org/pipermail/openstack-dev/2016-October/105390.html
 
 
 
=== Agenda (2016-09-27 0900 UTC) ===
 
* Add patch list in etherpad to improve the efficiency of reviewing/merging patches (zengchen)
 
** https://etherpad.openstack.org/p/karbor-newton-reviews
 
* Barcelona design session(zhonghua-lee)
 
 
 
=== Agenda (2016-09-20 1500 UTC) ===
 
* Dashboard tasks (scheduled operations, polling statuses, edit plan)
 
* Plan status
 
* Show plan when resource is deleted
 
* Delete flow and garbage collection
 
* Protectable plugins: validate status
 
* Glance protectable & protection: kernel & ramdisk
 
 
 
=== Agenda (2016-09-13 0900 UTC) ===
 
* Enable ConsistencyGroup and full vm protection (snapshot/backup) through Karbor (yinwei)
 
* Enable replicate protection plugin(yinwei)
 
* Decouple checkpoint API from provider API to become an standalone API(leon_wang)
 
**Spec is at https://review.openstack.org/#/c/369170/
 
*Add a dict type parameter for Protectable Instances API(chenying)
 
**
 
**Now the resource instances only can be queried from defaut region.
 
**If there are several regions in one site/keystone, we can not query resource instances
 
**from different region endpoint. We may need a parameter for the region name.
 
**
 
**The scene of database protection: If we want to use Protectable Instances API to
 
**query database instances from verdor's backup software. We must pass
 
**some parameters about authentication to the restfull API of verdor's backup software.
 
**
 
**I think we should add a dict type parameter to Protectable Instances API. The key and
 
**value in parameter, whitch is needed for implementing some protectable plugins.
 
**
 
* Open discussion
 
 
 
=== Agenda (2016-09-06 1500 UTC) ===
 
* Generic database Bank implementation(chenying)
 
**https://review.openstack.org/#/c/365823/
 
* Open discussion
 
 
 
=== Agenda (2016-08-30 0900 UTC) ===
 
* Delete 'crontab' time format for time trigger, and support RFC2445 (zengchen)
 
* Rename window September 2nd (yuvalbr)
 
* Open discussion
 
 
 
=== Agenda (2016-08-16 0900 UTC) ===
 
* Dashboard Items Review (xiangxinyong)
 
** https://review.openstack.org/#/q/project:openstack/smaug-dashboard+status:open
 
* Support checkpoint scheduled clean (xiangxinyong)
 
** https://review.openstack.org/#/c/351670/
 
* The new implementation about the 'suspend/resume' operation (zengchen)
 
** https://review.openstack.org/#/c/349869/
 
** https://bugs.launchpad.net/karbor/+bug/1606467
 
* New protection plugin I/S implementation (yuvalbr)
 
* Open discussion
 
 
 
=== Agenda (2016-08-09 1500 UTC) ===
 
* Mascot and name selection (saggi)
 
* Open discussion
 
 
 
=== Agenda (2016-08-02 0900 UTC) ===
 
* Mascot and name selection (saggi)
 
* Add a new executor for Operation Engine service (zengchen)
 
** https://bugs.launchpad.net/smaug/+bug/1608415
 
* Scheduled Operation Improvements Proposal (xiangxinyong)
 
** https://etherpad.openstack.org/p/scheduledoperation
 
* Volume OPTIONS_SCHEMA Improvements Proposal (xiangxinyong)
 
** https://etherpad.openstack.org/p/volumeschema
 
* Open discussion
 
 
 
=== Agenda (2016-07-26 1500 UTC) ===
 
* Add pause and resume interface for scheduled operations
 
** https://bugs.launchpad.net/smaug/+bug/1606467
 
* Where to show the status of restoration?
 
** https://etherpad.openstack.org/p/restorestate
 
* add policy for checkpoints management(zhonghua-lee)
 
** https://etherpad.openstack.org/p/edward
 
*Mark the source of checkpoint data
 
    Scenario: The tenant want to query the checkpoint data with the condition that the data is protected automatically or manually.
 
    Create checkpoint API can be called by operationengine automatically. It also can be executed manually.
 
    Consider adding a field to checkpoint data to mark this backup action being executed automatically or manually.
 
    But the restapi of create_checkpoint also can be called by other project. Maybe it is executed using the policy of the project.
 
* Open discussion
 
 
 
=== Agenda (2016-07-19 0900 UTC) ===
 
* Announcements
 
* Protection Plugins
 
* Barcelona Summit
 
* Free discussion
 
 
 
=== Agenda (2016-07-11 1100 UTC) ===
 
* Smaug name change
 
* Barcelona last call
 
* Open discussion
 
 
 
=== Agenda (2016-07-05 0900 UTC) ===
 
* core nomination
 
* enhance restore object with status and resource info
 
* Open discussion
 
 
 
=== Agenda (2016-06-28 1500 UTC) ===
 
* Triumphant return of the PTL
 
* Open Issues
 
* Open discussion
 
 
 
=== Agenda (2016-06-21 0900 UTC) ===
 
* Smaug Big Tent congratulations
 
* Testing
 
* Patches and reviews
 
* Documentation
 
* Open discussion
 
 
 
=== Agenda (2016-06-14 1500 UTC) ===
 
* Core nominations
 
* Testing
 
* Documentation
 
* TC meeting prep
 
* Open discussion
 
 
 
=== Agenda (2016-06-07 1500 UTC) ===
 
* Core nominations
 
* Status updates
 
* Testing
 
* Documentation
 
* Big Tent
 
* Open discussion
 
 
 
=== Agenda (2016-05-17 1400 UTC) ===
 
* Status updates
 
* Task flow improvements (ybrik)
 
* New time for meeting
 
* Patch stagnation
 
* Open discussion
 
 
 
=== Agenda (2016-05-03 1400 UTC) ===
 
* OpenStack Summit update
 
* Status updates
 
* Task flow improvements (ybrik)
 
* Open Issues
 
 
 
=== Agenda (2016-04-19 1400 UTC) ===
 
* Operation Logs Discussion
 
* Open Issues
 
 
 
=== Agenda (2016-04-05 1400 UTC) ===
 
*Announcements
 
* Operation Log
 
** What is missing?
 
** Does it include protect with schedule, protect without schedule and delete?
 
* Protectables status
 
** Openstack Clients
 
* Workflow Engine
 
* Add parameters for Create Plan API
 
** http://paste.openstack.org/show/492976/
 
* How to Create Restore with every resource and resource paramters?
 
** http://paste.openstack.org/show/492978/
 
* Smaug Python Client
 
** Progress report
 
* UI
 
** Progress report
 
* CI
 
** Add python  3 CI
 
* Open Bugs
 
* Open Issues
 
 
 
=== Agenda (2016-03-22 1400 UTC) ===
 
*Announcements
 
* Merge Proposed Smaug API v1.0 
 
**  Missing operation log will be added in another patch
 
* REST API
 
** What is missing?
 
* Protectables status
 
** Openstack Clients
 
* Workflow Engine
 
** Protection Provider
 
** Protection Plugin & Service
 
* Smaug Python Client
 
** Progress report
 
* UI
 
** Progress report
 
* CI
 
** Add python  3 CI
 
* Open Bugs
 
* Open Issues
 
 
 
=== Agenda (2016-03-08 1400 UTC) ===
 
* Merge Proposed Smaug API v1.0 
 
**  Missing operation log will be added in another patch
 
* REST API
 
** The RESTAPI of resource checkpoints https://review.openstack.org/#/c/286412/2
 
**  RestAPIs of trigger.https://review.openstack.org/#/c/286406/
 
**  RestAPIs of Scheduled Operation https://review.openstack.org/#/c/287036/
 
*Protectables status
 
** ProtectableRegistry https://review.openstack.org/#/c/281783/
 
** protectable RPC handlers https://review.openstack.org/#/c/285921/
 
** Cinder https://review.openstack.org/#/c/285611/3
 
** Nova https://review.openstack.org/#/c/286542/3
 
*Protection Plugin & Service
 
** Design doc for Protection Service https://review.openstack.org/#/c/261455/
 
** Swift bank plugin https://review.openstack.org/#/c/279929/
 
** Cinder Volume plugin https://review.openstack.org/#/c/286458/
 
** Server Nova plugin 
 
** Networking Plugin
 
** Provider and ProviderRegistry https://review.openstack.org/#/c/281618/
 
** workflow https://review.openstack.org/#/c/285149/ , https://review.openstack.org/#/c/281011/
 
*Operation Engine Status
 
** Spec trigger https://review.openstack.org/#/c/271210/
 
** Time trigger patch https://review.openstack.org/#/c/271196/
 
** https://review.openstack.org/#/c/274339/ , https://review.openstack.org/#/c/282263/, https://review.openstack.org/#/c/276081/
 
* CI
 
** Add python 3 CI
 
* Open Bugs
 
* Open Issues
 
 
 
=== Agenda (2016-02-23 1400 UTC) ===
 
* Announcements
 
* Merge Proposed Smaug API v1.0 
 
**  Missing operation log will be added in another patch
 
* Smaug UI Design
 
**http://www.screencast.com/t/SLqCyOwtBRl
 
** new sub projects for dashboard and client for Smaug  https://review.openstack.org/#/c/281019/
 
* Protection Service design spec 
 
**https://review.openstack.org/#/c/261455/
 
*  protection-plugin-design
 
**https://blueprints.launchpad.net/smaug/+spec/protection-plugin-design
 
* time trigger design 
 
** https://review.openstack.org/#/c/271210/
 
*Operation Service Status
 
*Api Service Status
 
*Protection Service Status
 
*Open Issues
 
*Open Bugs
 
 
 
=== Agenda (2016-01-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
 
** https://review.openstack.org/244756
 
* Pluggable Proection Provider QA
 
** https://review.openstack.org/262264
 
* Protection Service tasks
 
** https://etherpad.openstack.org/p/smaug-bootsrap
 
* 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 
 
**https://review.openstack.org/#/c/244756/
 
**https://docs.google.com/presentation/d/1JYO1VIlTkGTF6lvKEMcsHkaST3mYFxuarpcNTJ3HBhk/edit?pref=2&pli=1#slide=id.p20
 
**https://review.openstack.org/#/c/255211/
 
*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
 
***https://review.openstack.org/#/c/259311/
 
**Base Service class
 
***https://review.openstack.org/#/c/259901/
 

Revision as of 08:12, 26 September 2017

Weekly Karbor meeting

If you're interested in Data Protection as Service(Karbor) for OpenStack, we have a weekly meetings on IRC. Please feel free to add your topic to the agenda below. When adding topics please leave your IRC name. meeting information:

  • #openstack-meeting
  • Tuesday at 1500 UTC each even week and 0900 UTC each odd week

Previous Meetings

Agenda (2017-09-26 0900 UTC)

  • Adding more protection parameters retention period
(https://review.openstack.org/#/c/498193/)