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
Propose Events SIG #91
Conversation
Thanks! |
Nice work, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we want the same cadence as the Interoperability SIG
Agreed Co-authored-by: Mattias Linnér <54929896+m-linner-ericsson@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excited for the new sig!
NIT: we might update the list in https://github.com/cdfoundation/toc/tree/master/sigs/README.md as well, but it would be ok to do so in a follow-up PR too. |
@afrittoli , the README is already in this PR :) |
Current info on the events workstream in the Interop SIG: https://github.com/cdfoundation/sig-interoperability/tree/master/workstreams/events_in_cicd |
@e-backmark-ericsson shall weinclude the link to https://github.com/cdfoundation/sig-interoperability/tree/master/workstreams/events_in_cicd in the PR? |
@afrittoli , I don't see that we have any more valid information on that link that is not already part of this PR - The charter is here, the meetings doc is linked from the PR and the README is kind of out of date I would say when we become a SIG. Do you agree? But of course I'll add Isaac as our appointed sponsor. I'm very glad to have you on board, @imosquera! :) |
Sounds good, thank you! |
The SIG has been approved: https://lists.cd.foundation/g/cdf-toc/message/614 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a quick comment inline.
- How are events related and how are they ordered (links vs trace context)? | ||
|
||
### Outcome | ||
The group is working on a standardized event protocol that caters for technology agnostic machine-to-machine communication in CI/CD systems. This specification will be published, reviewed and agreed upon between relevant Linux Foundation projects/members. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious to understand the need for a new protocol. with a lot of companies standardizing on either grpc, httpv2 or websockets for communication between tooling do we really need something at this lower level or are you talking about having a common schema for events with a set of APIs inside these tools that provides communication in a standard way? the other concern i have around implementing a protocol is the growing number of SaaS/Cloud offerings in the market, getting data in and out of tools that are deployed on-premises will require security teams to get involved in approving connectivity between disparate tools. i ❤️ the initiative between the Interoperability SIG and the Event SIG. Sould also be aware of other standards in this segment around CNAB that purpose to do the same thing, although implemented a little differently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @leefaus, thank you for your comment and for the link to CNAB.
Our intention is indeed to work at a higher level on the stack; we definitely do not intend to create another grpc, httpv2 or websockets. We could call the result of our work a common schema instead of protocol; in any case it sounds like we should make sure our intentions are clear in the documentation. Our plan is - at least for cloud native platforms - is to base our work on top of CloudEvents which includes SDKs for several programming languages, and bindings for several protocols.
This is a proposal for the Events in CI/CD workstream to become a SIG