Add SIG-Runtime Charter #319

quinton-hoole · 2019-11-14T00:44:12Z

This is an MD formatted version of the original:

@bgrant0607 @brendandburns @caniszczyk @lizrice @amye

bgrant0607 · 2020-01-06T21:06:51Z

sigs/runtime-charter.md

+    effort by the two groups and maintain clear and consistent messaging
+    to our end user community and projects.
+*   **[CNCF Security SIG](https://github.com/cncf/sig-security)**
+    - works on the more general area of cloud-native security including a


Chopped authentication in 2

bgrant0607 · 2020-01-06T21:10:19Z

Typos aside, LGTM. This is ready for a vote.

stackedsax · 2020-01-07T01:46:16Z

sigs/runtime-charter.md

+
+
+
+*   General authentication, authorization, accounting, auditing, etc (even though these clearly apply to )


"(even though these clearly apply to )" looks like an incomplete sentence.

Yup, will fix.

justincormack · 2020-01-07T14:14:51Z

sigs/runtime-charter.md

+
+
+*   General authentication, authorization, accounting, auditing, etc (even though these clearly apply to )
+    - because AAA, etc is clearly the domain of the [CNCF Security SIG](https://github.com/cncf/sig-app-delivery).


this should link to Security SIG not app delivery

raravena80 · 2020-01-07T14:37:04Z

sigs/runtime-charter.md

+
+
+*   **[Several Kubernetes SIGs](https://github.com/kubernetes/community)**
+    cover Kubernetes-specific workload, scheduling, autoscaling, execution


Can we add sig-node here?

This item refers to all kubernetes sigs generally, including sig-node. I don't think it's a good idea to enumerate them all explicitly, because there are very many of them, and they change over time.

lizrice · 2020-01-07T14:46:54Z

sigs/runtime-charter.md

+    pertains to helping to ensure that the required underlying workload
+    execution abstractions and mechanisms are suitably provided to support
+    these application-level delivery needs.
+*   **Note regarding Container Registries/Repositories** and the like:


Should this SIG have a relationship with OCI?

My opinion is that the relevant projects (e.g., containerd, cri-o) should engage with OCI, or relevant Kubernetes SIGs, or other projects, or other foundations as needed.

I think both apply. Will update.

dfeddema · 2020-01-17T01:53:20Z

sigs/runtime-charter.md

+**Current TOC Liaison:**  Brendan Burns and Brian Grant
+
+**[Proposed] Co-Chairs:** [Quinton Hoole](https://www.linkedin.com/in/quintonhoole/),
+  [Ricardo Aravena](https://www.linkedin.com/in/raravena), 1 TBD


I am Diane Feddema and I'm interested in being a SIG-Runtime co-chair. I'm a Principal Software Engineer at Red Hat in the AI Center of Excellence in the CTO's office. I have a background in HPC and have been working on AI/ML applications and benchmarking at Red Hat for 7 years. I'm interested in this role because I'm working with our hardware partners to enable hardware accelerators (GPU, FPGAs, etc) that will run on Kubernetes/Openshift. www.linkedin.com/in/dianefeddema

Thanks Diane. I think that the SIG would greatly appreciate your assistance. Any objections?

@dfeddema to formalize this I've added you as a nominee and up for a vote to be discussed in the next TOC meeting. As per https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#elections

umohnani8 · 2020-01-21T20:49:22Z

I am Urvashi Mohnani and I am interested in being a Tech Lead for the SIG-Runtime. I am a Software Engineer at Red Hat in the Openshift Runtimes/Node team and a CRI-O maintainer. I have been working in the container technologies space, building up CRI-O, podman, skopeo, and buildah, for about 3 years now. I am interested in this role because I have been working closely with the technology used by container runtimes and am excited by the opportunity to help guide/shape the future in this space.
https://www.linkedin.com/in/urvashi-mohnani

quinton-hoole · 2020-01-22T04:42:47Z

Thanks Urvashi.

It would be great to have you contribute to the SIG. Regarding Tech Leadership, the TOC SIG guidelines specify:

"Each SIG has multiple tech leads who are recognized as (1) experts in the SIG area, (2) leaders of projects in the SIG’s area (3) demonstrating the ability to provide the balanced technical leadership required to produce the required unbiased outputs of the SIG."

This SIG area, in turn, is defined as covering:

Workload execution and management systems, components and interfaces used in modern cloud-native
environments
are in scope, including:

generalized orchestration, autoscaling, scheduling, execution, container
runtimes, sandboxing, virtualization, image packaging and distribution and specialized architectures thereof, e.g.
- those aimed specifically at Edge, IoT, Batch, Big Data, AI/ML, etc
- those incorporating specialized computing elements beyond CPUs, including GPUs, TPUs, FPGAs, ASICs, etc.

We strive to understand the fundamental characteristics of different approaches with respect to availability, scalability, performance, consistency, ease-of-use, cost and operational complexity; and relate these to their suitability to various cloud-native use cases.

Given that your experience in the space appears to be limited to contributing to container runtime and image related projects for 2-3 years, do you consider yourself to meet the above criteria across the full scope of the SIG? If so, please provide further details.

feiskyer · 2020-01-22T06:16:58Z

sigs/runtime-charter.md

+**[Proposed] Co-Chairs:** [Quinton Hoole](https://www.linkedin.com/in/quintonhoole/),
+  [Ricardo Aravena](https://www.linkedin.com/in/raravena), 1 TBD
+
+**[Proposed] Tech Leads:** [Klaus Ma](http://www.klaus1982.cn/about/), 2 TBD


Hi, I'm Pengfei Ni and I'm interested in being the co tech-lead of sig-runtime. I'm a software engineer at Microsoft Azure and maintainer of the kubernetes project. I have extensive experience in Cloud Computing, Kubernetes and Software Defined Networking (SDN). I have given presentations on KubeCon China/NA, ArchSummit, LC3, and so on. And here is my linkedin https://www.linkedin.com/in/feisky/.

I am also interested in being a tech lead for sig-runtime. I am a Principal Engineer at Red Hat. I am an early libcontainer maintainer, OCI maintainer, and runc maintainer. I lead the CRI-O project. I have contributed to docker and kubernetes and I'm an active participant in sig-node. I have given talks at Dockercon, Kubecon and Linux Plumbers Conference. Happy to provide more details if needed. Thanks!

Thanks all.

@feiskyer I've added you as a nominee (if nobody else has an objection)

@mrunalp can you sync up with @umohnani8 (also about @quinton-hoole's question above) since only one of you can be nominated due to both of you being at Red Hat, (2/3 supermajority discouraged) and only one more tech-lead nominee slot available.

Elections rules described here: https://github.com/cncf/toc/blob/master/sigs/cncf-sigs.md#elections

@quinton-hoole @raravena80 sorry for the late response. Thanks for providing more clarification around what the needs would be for a tech lead in this sig. Please nominate @mrunalp, but I am looking forward to actively being involved with the sig.

dims · 2020-01-22T14:51:28Z

sigs/runtime-charter.md

+
+
+*   generalized orchestration, autoscaling, scheduling, execution, container
+    runtimes, sandboxing, virtualization, image packaging and distribution and specialized architectures thereof, e.g. 


"image packaging and distribution" -> "image packaging/distribution" ( the 2 and(s) read odd).

quinton-hoole · 2020-03-04T19:36:04Z

Addressed final comments - ready to merge.
@amye @caniszczyk please merge.

Quinton Hoole and others added 2 commits November 13, 2019 16:24

Add SIG-Runtime Charter

a69f12f

Fixed minor typos and author

486b1a6

bgrant0607 reviewed Jan 6, 2020

View reviewed changes

stackedsax reviewed Jan 7, 2020

View reviewed changes

justincormack reviewed Jan 7, 2020

View reviewed changes

raravena80 reviewed Jan 7, 2020

View reviewed changes

lizrice reviewed Jan 7, 2020

View reviewed changes

dfeddema reviewed Jan 17, 2020

View reviewed changes

feiskyer reviewed Jan 22, 2020

View reviewed changes

dims reviewed Jan 22, 2020

View reviewed changes

Addressed final comments. Ready to merge.

6b7118d

amye closed this Mar 5, 2020

amye reopened this Mar 5, 2020

amye merged commit 80266a9 into cncf:master Mar 5, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add SIG-Runtime Charter #319

Add SIG-Runtime Charter #319

quinton-hoole commented Nov 14, 2019

bgrant0607 Jan 6, 2020

quinton-hoole Mar 4, 2020

quinton-hoole Mar 4, 2020

bgrant0607 commented Jan 6, 2020

stackedsax Jan 7, 2020

quinton-hoole Jan 22, 2020

quinton-hoole Mar 4, 2020

justincormack Jan 7, 2020 •

edited

quinton-hoole Jan 22, 2020

quinton-hoole Mar 4, 2020

raravena80 Jan 7, 2020

quinton-hoole Mar 4, 2020

lizrice Jan 7, 2020

bgrant0607 Jan 8, 2020

quinton-hoole Jan 22, 2020

quinton-hoole Mar 4, 2020

dfeddema Jan 17, 2020

quinton-hoole Jan 22, 2020

raravena80 Feb 1, 2020

umohnani8 commented Jan 21, 2020

quinton-hoole commented Jan 22, 2020

feiskyer Jan 22, 2020

mrunalp Jan 22, 2020

raravena80 Feb 1, 2020

umohnani8 Feb 1, 2020

dims Jan 22, 2020

quinton-hoole commented Mar 4, 2020




		* General authentication, authorization, accounting, auditing, etc (even though these clearly apply to )



		* General authentication, authorization, accounting, auditing, etc (even though these clearly apply to )
		- because AAA, etc is clearly the domain of the [CNCF Security SIG](https://github.com/cncf/sig-app-delivery).



		* [Several Kubernetes SIGs](https://github.com/kubernetes/community)
		cover Kubernetes-specific workload, scheduling, autoscaling, execution



		* generalized orchestration, autoscaling, scheduling, execution, container
		runtimes, sandboxing, virtualization, image packaging and distribution and specialized architectures thereof, e.g.

Add SIG-Runtime Charter #319

Add SIG-Runtime Charter #319

Conversation

quinton-hoole commented Nov 14, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bgrant0607 commented Jan 6, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

justincormack Jan 7, 2020 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

umohnani8 commented Jan 21, 2020

quinton-hoole commented Jan 22, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

quinton-hoole commented Mar 4, 2020

justincormack Jan 7, 2020 •

edited