search

AICoE / content-pipeline

Other
3 stars 5 forks source link

Operate First: How to open source cloud operations #17

Closed durandom closed 2 years ago

durandom commented 2 years ago

Talk Abstract

Open source has become the defining way of developing software. But how do we open-source the operation of software?

The Operate First Community Cloud is a peer-to-peer mentoring environment for running software in production, as well as a community for Cloud Native SREs to share knowledge about production practices.

Using the same community-building process of open source projects, but extended to ops procedures and data.

Did you ever want to peek into a data center?

See how Kubernetes, ArgoCD, Kubeflow, Prometheus and other workloads are deployed and operated including the real configs. We’ll take you on a ride through the user-facing onboarding processes and the back office, where SRE’s perform state-of-the-art DevOps through GitOps and bot automation.

Experienced SRE’s will find an outlet for sharing their knowledge and new talent get’s a chance to grow into an SRE role and get their hands on cloud-native projects in a production environment.

If you want to modernize your own environment, come and build on the community knowledge to get you bootstrapped.

Speakers

Marcel Hild

What conference(s) are you submitting this proposal to?

Project repo link, or other relevant resources

Link to abstract

https://docs.google.com/document/d/1t8KajPMjPdQrEaGWUkdMst8VNKtbQBr3QwvwGTMmmDQ/edit#heading=h.1dw18qfqm0fo

Was this proposal accepted?

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

schwesig commented 2 years ago

i think this can be closed? devconf.cz 2022 is over and the talk/topics was presented as far as I know

sesheta commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

sesheta commented 2 years ago

@sesheta: Closing this issue.

In response to [this](https://github.com/AICoE/content-pipeline/issues/17#issuecomment-1083185034): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.