First blog post on OpenSLO blog section. Here we will be posted all news and +interesting initiatives. If you are interested in writing your own blog post +create a pull request on our GitHub repository.
diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/blog/hello/index.html b/blog/hello/index.html new file mode 100644 index 0000000..d73ab93 --- /dev/null +++ b/blog/hello/index.html @@ -0,0 +1,18 @@ +
First blog post on OpenSLO blog section. Here we will be posted all news and +interesting initiatives. If you are interested in writing your own blog post +create a pull request on our GitHub repository.
February 21, 2024
OpenSLO Project Meeting: February 2024
September 23, 2022
SLOconf Talks
First community meeting in 2024
During the meeting, several agenda items were discussed and decisions were made regarding the OpenSLO project.
Source of Truth for OpenSLO manifest: +The group decided to use Go structs as the source of truth for the OpenSLO manifest. This decision was made to ensure more control over validation. The plan is to generate JSON Schema/CRDs based on Go structs.
Labels Support: +Labels support is to be extended for all objects’ metadata, including adding labels to Objective.
Oslo Conversion Removal: +The decision was made to remove the conversion entirely and extend oslo documentation on the usage of annotations for vendor-specific conversions. The focus will be on improving the SDK instead of expanding oslo’s responsibilities.
Action Items: +Several action items were noted, including documenting new use cases of OpenSLO, ensuring full Kubernetes compatibility, and considering bringing OpenSLO under CNCF’s umbrella.
The next meeting is scheduled the next month. Precise date TBD.
In May 2022 another SLOconf took place, we want to share with you a few of the most interesting talks from that conference. +If you want to find more of talks like that, here is the playlist with all SLOconf 2022 videos.
Starting with talk about OpenSLO and alerting. It is good place to start to understand what is current position of OpenSLO.
Understanding what is reliability of service and why it is important, gives us better understanding why we should use SLO.
How we can understand the need for SLOs in a real life scenario and how to declare objectives based on that scenario.
What problems you can encounter during implementing meaningful SLO for your platform.
How to better understand your latency SLOs using histograms.
How we can use knowledge from different branches of the IT industry in our work.
The last video isn’t exactly from SLOconf 2022 but from SLOconf Monthly Meetup. We want to share it with you anyway because it is great place to give your talk +and talk with others interested in SLOs instead of waiting for SLOconf 2023.
In these talk Wayne shares story how create a large number of SLOs automatically for a large number of assets in your organization.
Create declarative definitions of SLOs that describe thresholds, metrics, and goals for your applications and infrastructure.
Create simple automated GitOps workflows with any CI/CD tool that ensures your SLOs are correctly formatted. Just run oslo validate slos.yaml.
OpenSLO is designed to be implementation neutral and allow multiple vendors and other projects to describe and share SLOs in a well-defined format.
February 21, 2024
OpenSLO Project Meeting: February 2024
September 23, 2022
SLOconf Talks