add meeting minutes for the latest sync 2019/01/30

Signed-off-by: Steven Zou <[email protected]>
CliftonDobrich · Jan 31, 2019 · de907a6 · de907a6
1 parent e4f7292
commit de907a6
Show file tree

Hide file tree

Showing 8 changed files with 100 additions and 6 deletions.
diff --git a/README.md b/README.md
@@ -6,6 +6,14 @@ A place for Harbor community related material.
 
 The Harbor Project holds bi-weekly community calls. To join or watch previous meeting notes and recordings, please see [meeting schedule](MEETING_SCHEDULE.md).
 
+## Workgroups
+
+Workgroup is a virtual team of aggregating the efforts of all the interested parties who have same focus on the specific topic and are willing to do significant contributions to that topic.
+
+|  Group  |  Missions  | Coordinator |  Members |
+|---------|------------|-------------|----------|
+| [Replication](./workgroups/wg-replication/README.md) |Deliver a new replication service (next generation replication) to support the kinds of content replication requirements from the Harbor community|Steven Zou@VMware ([steven-zou](https://github.com/steven-zou))|Steven Zou@VMware ([steven-zou](https://github.com/steven-zou)) / Wenkai Yin@VMware ([ywk253100](https://github.com/ywk253100)) / De Chen@CaiCloud ([cd1989](https://github.com/cd1989)) / Fanjian Kong@Qihoo360 ([kofj](https://github.com/kofj)) / Mingming Pei@Netease ([mmpei](https://github.com/mmpei) / Lei Yuan@HuaWei ([yuanshuhan](https://github.com/yuanshuhan))|
+
 ## Structure
 
 * **presentations**: keeps the related slides about Harbor

diff --git a/workgroups/wg-replication/sync-meetings/2018-12-21/minutes.md b/workgroups/wg-replication/sync-meetings/2018-12-21/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2018/12/21
-Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2018-12-25/minutes.md b/workgroups/wg-replication/sync-meetings/2018-12-25/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2018/12/25
-Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2019-01-04/minutes.md b/workgroups/wg-replication/sync-meetings/2019-01-04/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2019/01/04
-Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2019-01-08/minutes.md b/workgroups/wg-replication/sync-meetings/2019-01-08/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2019/01/08
-Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2019-01-16/minutes.md b/workgroups/wg-replication/sync-meetings/2019-01-16/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2019/01/16
-Attendees: Wenkai yin@VMware, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud
+Attendees: Wenkai yin@VMware, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2019-01-22/minutes.md b/workgroups/wg-replication/sync-meetings/2019-01-22/minutes.md
@@ -1,7 +1,7 @@
 # Replication WG meeting minutes
 
 Date: 2019/01/22
-Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, Mingming Pei@Netease
 
 ## Updates
 

diff --git a/workgroups/wg-replication/sync-meetings/2019-01-30/minutes.md b/workgroups/wg-replication/sync-meetings/2019-01-30/minutes.md
@@ -0,0 +1,86 @@
+# Replication WG meeting minutes
+
+Date: 2019/01/30
+
+Attendees: Wenkai yin@VMware, Fanjian kong@Qihoo360, Lei Yuan@Huawei, Steven Z@VMware, De Chen@Caicloud, Mingming Pei@Netease
+
+## Updates
+
+First, Steven Z updates some workgroup operation stuff:
+
+* Create replication workgroup document folder in the `goharbor/community` repository to keep related docuemnts or meeting minutes of sync meetings
+* Introduce the replication NG DEV epic created in the `harbor` repository
+
+Second, component owners update the DEV progresses:
+
+_Fanjian Kong_:
+
+* Owner of `policy management` feature
+* Programing some code, working on the polciy management API. - Overall progress: 5%
+* need to accelerate DEV progress
+
+_Wenkai Yin_:
+
+* Owner of `replication operation`, `adapter registry` and `controller` components
+* PR of replication wrapper job has been merged
+* PR of flow controller has been submitted
+
+_De Chen_:
+
+* Owner of `registry management` component
+* Programing code of this part - Overall progress: 50%
+* Do reseearch for the DockerHub adapter
+
+_Mingming Pei_:
+
+* Owner of `hooks` and `replication manager` (rename it to `Execution Manager`) components
+* `Execution Manager` is ongoing - Overall : 5%
+* Programing code of `hooks` - Overall: 40%
+
+_Lei Yuan_:
+
+* Owner of `scheduler` component
+* Need to extend the interface of `scheduler` to support stop job
+* Almost done, will submit PR within this week
+
+## Issues
+
+Issue 1: What's the meaning of pull/push mode in the replication policy UI wizard? It is not defined in the policy model.
+
+> It's only a feature in the UI front end as a quick way for user to define the policy.
+> Pull mode means the dest registry is the current Harbor, the system will automatically fill in the dest registry info with current Harbor
+> Push mode means the src registry is the current Harbor, similar with pull mode, the system will automatically fill in the src registry info with current Harbor
+
+Issue 2: Missing `Overwritten` settings in the replication policy wizard UI?
+
+> It should be there
+
+Issue 3: Support enable/disable the replication policy?
+
+> Yes, we support
+
+Issue 4: What we should handle the data schema and API endpoints? Migration and comparability should be considered?
+
+> API endpoints changes will break the API comparability
+> Migration script should be updated to cover the database schema changes
+
+Isuse5: Ignore the OAuth access token authentication mode in registry management as no use cases existing so far?
+
+> OK
+
+Issue 6: Should make sure legacy harbor can replicate with new harbor?
+
+> YES
+
+Issue 7: There might be issues when listing namespaces from the DockerHub? No API to list other public namespaces outside of the account?
+
+> Let user input the other namespaces.
+
+Issue 8: Some metadata like the `publicity` of namespace may need to replicate to the destination registry
+
+> Namespace can bring some metadata. Whether or not identify or use depends on the concrete implementations of the adapters.
+
+## Next Steps
+
+* Chinese Spring Festival is coming, will cancel the sync meetings of next and next next
+* Enhance collaboration, especially between the owners whose components have overlaps with each other