-
Notifications
You must be signed in to change notification settings - Fork 46
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #86 from wackxu/sig-scalability
add sig scalability charter
- Loading branch information
Showing
2 changed files
with
72 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
# Scalability Special Interest Group | ||
|
||
SIG Scalability is responsible for defining and driving scalability goals for KubeEdge. We also coordinate and contribute to general system-wide scalability and performance improvements (not falling into the charter of other individual SIGs) by driving significant architectural changes and finding bottlenecks, as well as providing guidance and consultations about any scalability and performance related aspects of Kubernetes. We are actively working on finding and removing various scalability bottlenecks which will lead us towards pushing the entire system's scalability higher. | ||
|
||
The [charter](https://github.com/kubeedge/community/blob/master/sig-scalability/charter.md) defines the scope and governance of the Scalability Special Interest Group. | ||
|
||
## Meetings | ||
|
||
- Regular SIG Meeting: [Monday at 15:30 UTC+8](https://zoom.us/j/4167237304) (biweekly, starts on Jun. 28th 2022). [Convert to your timezone](https://www.thetimezoneconverter.com/?t=10%3A00 am&tz=GMT%2B8&). | ||
- [Meeting notes and Agenda](https://docs.google.com/document/d/1PeuZzfLjU8oIduKI2nFeckKAhhckME4tqCZ33WmORBI/edit#heading=h.252sw1n3b1vb). | ||
- [Meeting Calendar](https://calendar.google.com/calendar/embed?src=8rjk8o516vfte21qibvlae3lj4%40group.calendar.google.com) | [Subscribe](https://calendar.google.com/calendar?cid=OHJqazhvNTE2dmZ0ZTIxcWlidmxhZTNsajRAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ) | ||
|
||
## Contact | ||
|
||
- [#sig-scalability slack channel](https://kubeedge.slack.com) | ||
- [Open Community Issues](https://github.com/kubeedge/community/issues) | ||
- [Mailing list](https://groups.google.com/forum/#!forum/kubeedge) | ||
|
||
## Leadership | ||
|
||
### Chairs | ||
|
||
The Chairs of the SIG run operations and processes governing the SIG. | ||
|
||
***TODO*** | ||
|
||
### Technical Leads | ||
|
||
The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions. | ||
|
||
|
||
|
||
- Shiwei Xu (@wackxu), Huawei |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# SIG Scalability Charter | ||
|
||
This charter adheres to the conventions described in [KubeEdge Open Governance](https://github.com/kubeedge/community/blob/master/GOVERNANCE.md) and uses the Roles and Organization Management outlined in the governance doc. | ||
|
||
## Scope | ||
|
||
SIG Scalability's primary responsibilities are to define and drive scalability goals for KubeEdge. This involves defining, testing and measuring performance and scalability related Service Level Indicators (SLIs) and ensuring that every KubeEdge release meets Service Level Objectives (SLOs) built on top of those SLIs. | ||
|
||
We also coordinate and contribute to general system-wide scalability and performance improvements (that don't fall into the charter of another individual SIG) by driving significant architectural changes and finding bottlenecks, as well as providing consultations about any scalability and performance related aspects of KubeEdge. | ||
|
||
### In scope | ||
|
||
#### Code, Binaries and Services: | ||
|
||
- Scalability and performance testing frameworks. such as Edgemark | ||
|
||
- Scalability and performance tests jobs | ||
|
||
#### Cross-cutting and Externally Facing Processes | ||
|
||
- Defining what does “KubeEdge scales” mean by defining (or approving) individual performance SLIs/SLOs, ensuring they are all oriented on user experience and consistent with each other. | ||
- Ensuring that each official KubeEdge release satisfies all scalability and performance related requirements. | ||
- Establishing and documenting best practises on how to design and/or implement KubeEdge features in scalable and performant way. Educating contributors and consulting individual designs/implementations to ensure that those are widely used. | ||
- Finding system bottlenecks and coordinating improvement on cross-cutting architectural changes. | ||
|
||
### Out of scope | ||
- Improving performance/scalability of features falling into charters of individual SIGs. | ||
|
||
## Roles and Organization Management | ||
|
||
This SIG follows and adheres to the Roles and Organization Management outlined in KubeEdge Open Governance and opts-in to updates and modifications to KubeEdge Open Governance. | ||
|
||
### Additional responsibilities of Chairs | ||
|
||
- Manage and curate the project boards associated with all sub-projects ahead of every SIG meeting so they may be discussed | ||
- Ensure the agenda is populated 24 hours in advance of the meeting, or the meeting is then cancelled | ||
- Report the SIG status at events and community meetings wherever possible | ||
- Actively promote diversity and inclusion in the SIG | ||
- Uphold the KubeEdge Code of Conduct especially in terms of personal behavior and responsibility |