search

AICoE / content-pipeline

Other
3 stars 5 forks source link

Beyond AIOps - How to “open source” operations and create free data #36

Closed durandom closed 2 years ago

durandom commented 2 years ago

Talk Abstract

As IT operations become more agile and complex in a cloud-native world, the need to enhance operational efficiency grows. Gathering and applying intelligence to systems operations is the solution. The term AIOps is often used in this context, as it promises to take operations to the next level by using AI. But if data is the oil that’s driving AI - you’ll be driving on your own home-grown oil.

If open source made software great, how do we “open source” an implementation or the operation of something? We coined the term “Operate First” for this. And one Operate First goal is to create an Open Cloud environment, operated by a Community. Open means, all data is accessible by the public: metrics, logs and tickets and how software and the operations team reacts to it.

The resulting data sets, published under an open license, will spark the interest of AI researchers and will drive innovation in AIOps beyond advanced statistics and towards the self-driving cluster.

Speakers

Marcel Hild

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

https://github.com/AICoE/content-pipeline/issues/37

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

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/36#issuecomment-1085075310): >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.