summaryrefslogtreecommitdiff
path: root/sig-multicluster
diff options
context:
space:
mode:
authorJonathan MacMillan <dvorak@google.com>2017-10-11 16:34:50 -0700
committerJonathan MacMillan <dvorak@google.com>2017-10-13 10:13:16 -0700
commitf8e1cbd0920f4a181759664095d80775e4e672c0 (patch)
treee81c7d3ae9fa982e3a9b9a88600d23807a170663 /sig-multicluster
parent5bd42a9126ceebc44fd3630d4a531cd2ed76acac (diff)
Update files in the community repo to point to multicluster rather than federation.
Diffstat (limited to 'sig-multicluster')
-rw-r--r--sig-multicluster/ONCALL.md76
-rw-r--r--sig-multicluster/OWNERS6
-rw-r--r--sig-multicluster/README.md29
3 files changed, 111 insertions, 0 deletions
diff --git a/sig-multicluster/ONCALL.md b/sig-multicluster/ONCALL.md
new file mode 100644
index 00000000..72aca202
--- /dev/null
+++ b/sig-multicluster/ONCALL.md
@@ -0,0 +1,76 @@
+# Overview
+
+We have an oncall rotation for Federation in the SIG. The role description is as
+follows:
+
+* Ensure that the testgrid (https://k8s-testgrid.appspot.com/sig-multicluster)
+ is green. This person will be the point of contact if testgrid turns red.
+ Will identify the problem and fix it (most common scenarios: find culprit PR
+ and revert it or free quota by deleting leaked resources). Will also report
+ most common failure scenarios and suggest improvements. Its up to the sig or
+ individuals to prioritize and take up those tasks.
+
+Oncall playbook:
+https://github.com/kubernetes/community/blob/master/contributors/devel/on-call-federation-build-cop.md
+
+# Joining the rotation
+
+Add your name at the end of the current rotation schedule if you want to join
+the rotation. Anyone is free to join as long as they can perform the expected
+work described above. No special permissions are required but familiarity with
+existing codebase is recommended.
+
+# Swapping the rotation
+
+If anyone is away on their oncall week (vacation, illness, etc), they are
+responsible for finding someone to swap with (by sending a PR, approved by that
+person). Swapping one week for another is usually relatively uncontentious.
+
+# Extending the rotation schedule
+
+Anyone can extend the existing schedule by assigning upcoming weeks to people in
+the same order as the existing schedule. cc the rotation members on the PR so
+that they know. Please extend the schedule unless there are atlease 2 people
+assigned after you.
+
+# Current Oncall schedule
+
+```
+25 September - 1 October: Madhu (https://github.com/madhusudancs)
+2 October - 8 October: Shashidhara (https://github.com/shashidharatd)
+9 October - 15 October: Christian (https://github.com/csbell)
+16 October - 22 October: Nikhil Jindal (https://github.com/nikhiljindal)
+23 October - 29 October: Irfan (https://github.com/irfanurrehman)
+30 October - 5 November: Maru (https://github.com/marun)
+6 November - 12 November: Jonathan (https://github.com/perotinus)
+(Madhu to be removed from next rotation)
+```
+
+# Past 5 rotation cycles
+
+```
+(Adding Irfan)
+7 August - 13 August: Nikhil Jindal (https://github.com/nikhiljindal)
+14 August - 20 August: Shashidhara (https://github.com/shashidharatd)
+21 August - 27 August: Christian (https://github.com/csbell)
+28 August - 3 September: Madhu (https://github.com/madhusudancs)
+4 September - 10 September: Irfan (https://github.com/irfanurrehman)
+11 September - 17 September: Maru (https://github.com/marun)
+18 September - 24 September: Jonathan (https://github.com/perotinus)
+
+
+(Adding Jonathan)
+26 June - 2 July: Nikhil Jindal (https://github.com/nikhiljindal)
+3 July - 9 July: Shashidhara (https://github.com/shashidharatd)
+10 July - 16 July: Christian (https://github.com/csbell)
+17 July - 23 July: Madhu (https://github.com/madhusudancs)
+24 July - 30 July: Maru (https://github.com/marun)
+31 July - 6 August: Jonathan (https://github.com/perotinus)
+
+
+22-28 May: Nikhil Jindal (https://github.com/nikhiljindal)
+29 May - 4 June: Shashidhara (https://github.com/shashidharatd)
+5 June - 11 June: Madhusudan (https://github.com/madhusudancs)
+12 June - 18 June: Maru (https://github.com/marun)
+19 June - 25 June: Christian (https://github.com/csbell)
+```
diff --git a/sig-multicluster/OWNERS b/sig-multicluster/OWNERS
new file mode 100644
index 00000000..da6b0996
--- /dev/null
+++ b/sig-multicluster/OWNERS
@@ -0,0 +1,6 @@
+reviewers:
+ - csbell
+ - quinton-hoole
+approvers:
+ - csbell
+ - quinton-hoole
diff --git a/sig-multicluster/README.md b/sig-multicluster/README.md
new file mode 100644
index 00000000..926d8822
--- /dev/null
+++ b/sig-multicluster/README.md
@@ -0,0 +1,29 @@
+<!---
+This is an autogenerated file!
+
+Please do not edit this file directly, but instead make changes to the
+sigs.yaml file in the project root.
+
+To understand how this file is generated, see generator/README.md.
+-->
+# Multicluster SIG
+
+Covers multi-cluster Kubernetes use cases and tooling. This includes: application resiliency against availability zone outages; hybrid clouds; spanning of multiple could providers; application migration from private to public clouds (and vice versa); and other similar subjects. This SIG was formerly called sig-federation and focused on the Federation project, but expanded its charter to all multi-cluster concerns in August 2017.
+
+## Meetings
+* [Tuesdays at 16:30 UTC](https://plus.google.com/hangouts/_/google.com/k8s-mc) (biweekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=16:30&tz=UTC).
+
+Meeting notes and Agenda can be found [here](https://docs.google.com/document/d/18mk62nOXE_MCSSnb4yJD_8UadtzJrYyJxFwbrgabHe8/edit).
+Meeting recordings can be found [here](https://www.youtube.com/watch?v=iWKC3FsNHWg&list=PL69nYSiGNLP0HqgyqTby6HlDEz7i1mb0-).
+
+## Leads
+* Christian Bell (**[@csbell](https://github.com/csbell)**), Google
+* Quinton Hoole (**[@quinton-hoole](https://github.com/quinton-hoole)**), Huawei
+
+## Contact
+* [Slack](https://kubernetes.slack.com/messages/sig-multicluster)
+* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-multicluster)
+
+<!-- BEGIN CUSTOM CONTENT -->
+
+<!-- END CUSTOM CONTENT -->