Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SIG-Runtime Charter #319

Merged
merged 3 commits into from Mar 5, 2020

Conversation

quinton-hoole
Copy link
Contributor

@quinton-hoole quinton-hoole commented Nov 14, 2019

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
Copy link
Contributor

@bgrant0607 bgrant0607 Jan 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chopped authentication in 2

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack.

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@bgrant0607
Copy link
Contributor

@bgrant0607 bgrant0607 commented Jan 6, 2020

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




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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

@quinton-hoole quinton-hoole Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, will fix.

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.



* 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).
Copy link
Contributor

@justincormack justincormack Jan 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should link to Security SIG not app delivery

Copy link
Contributor Author

@quinton-hoole quinton-hoole Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup.

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.



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

@raravena80 raravena80 Jan 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add sig-node here?

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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:
Copy link
Contributor

@lizrice lizrice Jan 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this SIG have a relationship with OCI?

Copy link
Contributor

@bgrant0607 bgrant0607 Jan 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

@quinton-hoole quinton-hoole Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think both apply. Will update.

Copy link
Contributor Author

@quinton-hoole quinton-hoole Mar 4, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

**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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

@quinton-hoole quinton-hoole Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor

@raravena80 raravena80 Feb 1, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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
Copy link

@umohnani8 umohnani8 commented Jan 21, 2020

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
Copy link
Contributor Author

@quinton-hoole quinton-hoole commented Jan 22, 2020

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.

**[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
Copy link
Contributor

@feiskyer feiskyer Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/.

Copy link

@mrunalp mrunalp Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

Copy link
Contributor

@raravena80 raravena80 Feb 1, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.



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

@dims dims Jan 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@quinton-hoole
Copy link
Contributor Author

@quinton-hoole quinton-hoole commented Mar 4, 2020

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

@amye amye closed this Mar 5, 2020
@amye amye reopened this Mar 5, 2020
@amye amye merged commit 80266a9 into cncf:master Mar 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet