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

Propose Events SIG #91

Merged
merged 3 commits into from Mar 1, 2021
Merged

Conversation

e-backmark-ericsson
Copy link
Contributor

This is a proposal for the Events in CI/CD workstream to become a SIG

@dlorenc
Copy link
Contributor

dlorenc commented Jan 28, 2021

Thanks!

@afrittoli
Copy link
Member

Nice work, thank you!

Copy link
Contributor

@m-linner-ericsson m-linner-ericsson left a 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

sigs/sig-events.md Outdated Show resolved Hide resolved
Agreed

Co-authored-by: Mattias Linnér <54929896+m-linner-ericsson@users.noreply.github.com>
Copy link

@ravilach ravilach left a 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!

@afrittoli
Copy link
Member

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.

@e-backmark-ericsson
Copy link
Contributor Author

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 :)

@e-backmark-ericsson e-backmark-ericsson marked this pull request as ready for review February 2, 2021 08:32
@e-backmark-ericsson
Copy link
Contributor Author

Current info on the events workstream in the Interop SIG: https://github.com/cdfoundation/sig-interoperability/tree/master/workstreams/events_in_cicd

@afrittoli
Copy link
Member

@e-backmark-ericsson shall weinclude the link to https://github.com/cdfoundation/sig-interoperability/tree/master/workstreams/events_in_cicd in the PR?
We could also add our ToC sponsor, @imosquera how kindly offered to be the sponsor for our SIG

@e-backmark-ericsson
Copy link
Contributor Author

@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! :)

@afrittoli
Copy link
Member

Sounds good, thank you!

@afrittoli
Copy link
Member

The SIG has been approved: https://lists.cd.foundation/g/cdf-toc/message/614 🎉

Copy link

@leefaus leefaus left a 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.
Copy link

@leefaus leefaus Feb 23, 2021

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.

Copy link
Member

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.

@dlorenc dlorenc merged commit d2c886d into cdfoundation:master Mar 1, 2021
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

6 participants