Skip to content

Latest commit

 

History

History
2594 lines (2040 loc) · 96.6 KB

working-group-notes-2023.md

File metadata and controls

2594 lines (2040 loc) · 96.6 KB
Raw
tags
CDEvents

CDEvents Working Group Meeting Notes

hackmd-github-sync-badge

This document contains the notes from the CDEvents Working Group.

Meeting Details

Schedule

  • Tuesday meetings are held at 3pm UTC during summer time and at 4pm UTC during winter time)
  • Monday meetings are held at 11am UTC during summer time and at 12pm UTC during winter time).

Previous Years

Template

Participants:

  • Name / affiliation / TZ

Links:

Agenda:

  • New attendees
  • Action Items
  • <addme>

Topics for coming meetings

Dec 18, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple, CST
  • Brett Smith, SAS, UTC-4
  • Christian Provenzano, Fidelity, UTC-4

Agenda:

  • New attendees

  • Action Items

    • Ben to prepare a demo on the maintainability topic
      • Plan to work on it next week
      • Demo in 2024
    • Owen to create an issue about capitalizing URI
    • Andrea to archive meeting notes for 2023
    • Andrea to create an issue about conformance groups: pending
    • Andrea to update the Artifact PR based on feedback: pending.
    • Andrea to update the SBOM PR based on feedback: done

  • (Sean/Ben) Ticket/Approvals Proposal

    • Tickets/issues
    • Draft proposal
    • Proposal planned for 1st/2nd week in Jan 2024
    • Sean/Ben to compare the current proposal against existing ticketing systems (GitHub issues, etc)

  • (Jalander) Generate Java SDK v0.3.0

    • PR is merged.
    • Conformance testing?
    • Apple looking to have an up to date Java SDK
    • Apple experiencing issues with some of the APIs
    • Andrea to make an Release Candidate in Jan to let people test it

  • (Andrea) Spelling PR cdevents/spec#173

    • Andrea to update the config to exclude code sections in markdown

  • (Andrea) SBOM uri cdevents/spec#171

  • (Brett) CDEvents Workshop

    • More work coming on this in the next weeks
      • Need a go client for the EPR API
      • Workshop should not ask users to post JSON via curl :)
    • Blog post to announce the EPR
      • It mentions SAS so it needs internal approval

  • (Andrea) Custom events cdevents/spec#168

    • Allowing for custom events expands the audience for events
    • If we do allow custom events, we need a good set of rules
      • We need to protect both producers and consumers
    • The SDKs could provide hooks to parse the subject/context
    • The schema should be hosted on the tool side, we could provide in the context a field that points to the schema
    • Andrea to formalise the proposal in an hackmd linked into the issue

Dec 11, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Christian Provenzano, Fidelity, UTC-4
  • Andrew Larsen, SAS, UTC-4
  • Owen Bower Adams, IGS, UTC
  • Jalander Ramagiri, Ericsson Software Technology, UTC

Links:

Agenda:

Dec 4, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Brett Smith, SAS, UTC-4
  • Ben Powell, Apple, CST
  • Jalander Ramagiri, Ericsson Software Technology, UTC
  • Owen Bower Adams, IGS, UTC
  • Andrew Larsen, SAS, UTC-4

Links:

Agenda:

  • New attendees

  • Action Items

  • (Andrea/Emil) Proposal for Governance and Contributor Ladder

    • Any objections to merging the PR? Ok to merge it now.

  • Introduce semantic conventions for CI/CD observability with OpenTelemetry

  • (Ben) Connecting & linking events

    • PR
    • Will work on resolving the comments this week

  • (Ben) Maintainability of schemas, examples, and tests

  • (Brett) Workshop for CDF with CDEvents

    • WIP Event Provenance Registry
    • We should create a workshop repo under CDEvents "Event Provenance Registry workshop". Set Brett and Andrew as maintainers.
    • Action: Emil

  • (Sean/Ben) Ticket/Approvals Proposal

  • (Andrea) Artifact events cdevents/spec#143

    • PR available cdevents/spec#172
    • Artifact scanned event upcoming
    • Discussions about what scanning an artifact means and how it should be noted in events. Different scan types need to be possible to provide.
    • Scanning is made for example to find CVEs. 'binary.analyzed' migt be an option, to also cater for other types of binary analyses
    • Also source code, Docker base images and deployments are scanned at SAS. Would it be better to have a 'scan.performed' event instead, to not limit to binaries only?
    • The links proposal should be able to help declaring what artifacts has passed a certain scanning step or not, etc.

  • (Andrea) SBOM uri cdevents/spec#171

    • What about capitalizing 'URI' in our parameters? What are the concerns regarding SDKs when it comes to paremeters formats?
    • Owen to write an issue to track that discussion
    • Concistency is key. Regardless of if we choose capitalizing all abbreviations or not.
    • Golang is opinionated about capitalizing URI so we might need to stick with that.

  • (Jalander) Generate Java SDK v0.3.0

  • (Andrea) Custom events cdevents/spec#168

Nov 27, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Brett Smith, SAS, UTC-4
  • Ben Powell, Apple, UTC+1
  • Jalander Ramagiri, Ericsson Software Technology, UTC

Links:

Agenda:

  • New attendees

    • Andrew Larsen, SAS, welcome!

  • (Andrea) Proposal for Governance and Contributor Ladder

  • (Ben) Connecting & linking events

    • PR
    • Examples to be updated

  • (Ben) Maintainability of schemas, examples, and tests

    • cdevents/spec#170
    • Very painful today to make changes to the CDEvents context
    • Ben to prepare a demo next week
    • Examples today have two functions:
      • Documentation
      • Testing (SDK conformance)
    • Automation will generate
      • Schemas - factor up duplicate schema fragments
      • Examples for testing purposes
    • Template engine:
    • Emil:
      • Hopefully not too many context changes in future
      • It would be good to still validate any example we provide
    • Ben: would like to handle testing of examples in a separate proposal
    • Brett:
      • Jinja - very powerful, it can become hard to read at times
      • gomplate - could as well use go template directly
        • Ben: gomplate provides a CLI on top of go template
      • examples should always pass the schema
      • Why not using the examples using the SDK?
        • SDKs are dependant on the examples
        • Chicken and egg issue with updating schema, examples, and SDK

  • (Brett) Workshop for CDF with CDEvents

  • (Sean/Ben) Ticket/Approvals Proposal

  • (Andrea) Artifact events cdevents/spec#143

  • (Andrea) SBOM uri cdevents/spec#171

  • (Andrea) Custom events cdevents/spec#168

Nov 20, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Jalander Ramagiri, Ericsson Software Technology, UTC
  • Ben Powell, Apple, CST
  • Sean Brennan, Bloomberg, EST
  • Andrea Frittoli, IBM, UTC

Links:

Agenda:

  • New attendees

  • Action Items

  • (Adam) Flux CD Integration with CDEvents

    • Discussion held in Flux dev meeting
    • fluxcd/flux2#4339
    • Showcased a receiver & provider demo
    • Reciever (consumer) will get a PR up soon
    • The provider (producer) will need some more discussions before being implemented
    • Where should source change events be sent from, when Flux directly integrates with e.g. GitHub?
    • (Emil) The CDEvents protocol doesn't dictate who should send what event
    • (Emil) It's important that the same event is not sent from multiple producers. Events should be unique.
    • (Emil, Ben) The event should be sent as close to the source of the occurrence as possible. I.e. SCM related events should be sent from the SCM system if possible.
    • (Emil) It's up to the system integrator to decide what tool sends what events.

  • (Jalander) Design approach Gerrit CDEvents integration

    • (Emil) Would it be relevant/helpful to also have Argo-events in this picture? argoproj/argo-events#2841
    • (Andrea) We shouldn't maintain a lot of tool specific CDEvents implementations. With our limited community we need to take concious decisions on what tools to provide plugins or translators for
    • (Emil) Webhook vs Gerrit 'stream-event' (inbout vs outbound connection & https vs ssh)?

  • Connecting & linking events

  • Ticket/Approvals Proposal

  • (Andrea) Proposal for Governance and Contributor Ladder

    • Targeting final review at next CDEvents meeting

  • Postponed to next meeting: (Andrea) Harbor integration & custom events

  • Java SDK updates

Nov 13, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple, CST
  • Sean Brennan, Bloomberg, EST
  • Jalander Ramagiri, Ericsson Software Technology, UTC

Links:

Agenda:

  • New attendees

    • Felipe Silveira, Farfetch
      • Focussed on CI/CD, ArgoCD, Workflow, Jenkins

  • Action Items

  • <addme>

  • (Andrea) Proposal for Governance and Contributor Ladder

    • Once we have an agreed version we can
      • Start GB elections
      • Setup GitHub reviewes/maintainers teams and files

  • (Andrea) Updates from KubeCon+CloudNativeCon NA

    • Make projects and companies available on the CDEvents website cdevents/cdevents.dev#36
    • Harbor
      • Still supportive of CDEvents adoption
      • CDEvents notifications must cover all event types. For Harbor events that are not defined by the CDEvents spec
        • A schema should be defined
        • The schema could be maintained on Harbor side
        • Versioning to be clarified
        • Extension mechanism on CDEvents side
        • Proposal: cdevents/spec#168
      • Other registries to look into
    • CNCF App Delivery TAG
      • Still interested in CDEvents
      • Need contributors to work with Podtato Head
    • Argo CD / Workflow
      • Still interested in CDEvents
      • (Initial) implementation could be achieved via Argo Notifications
        • Use templates instead of SDKs
      • Met together with CNOE.io team repr
    • CNOE.io
      • IDP platform, very interested in CDEvents
      • Define capabilities as well as CNOE favourite set of tools
      • Would like to support interoperability
        • Make it easy to swap tools
        • Single language for a Backstage plugin to surface data to users
      • Would need IaaS events
      • Will help drive implementation in Argo CD/Workflow and possibly other tools
    • Guac.sh
      • Interested in ingesting SBOM through CDEvents
      • SBOM link in artifact events
        • Artifact type already in purl
        • SBOM type is not important for guac (for now at least)
      • Should try and include in upcoming v0.4
      • Interested in asyncapi.io / openapi definitions for CDEvents
    • Pelorus project for DORA metrics
    • Harness
      • CDEvents integration may be technically simple
      • Engineering focussed on end-user demand, CDEvents not in scope yet
      • May be possible to build a POC in collaboration with Dev Advocacy
    • Dagger.io
      • Interested in pipeline observability
      • Looked into distributed tracing, however the lack of fan-in was a showstopper
      • CDEvents is an interesting alternative as long as it supports fan-in/fan-out
    • Some vendors associated the idea of interoperability with making it easiers for users to leave their platform
      • My take on this is that it also makes it easier for users to adopt their platform. Users should stay because the platform is excellent in solving their problem, not because of lock-in and attrition.
      • Ben: how do we alleviate that fear? Similar to early days of SQL.

  • Connecting & linking events

    • PR
    • New link type
      • Connecting of the graph
      • Attach metadata to nodes in the graph
      • Commit 1. New PR coming up to separate the two things
      • Commit 2. Adding optional links to context
      • Commit 3. Examples being added

  • Tickets / Approvals

    • Probably two separate proposals
    • Tickets first, only a couple of outstanding questions
      • How to link tickets to anything else
      • Trying to envision how a consumer would use this events
      • We won't model the consumer workflow in the protocol
    • Next week or two ready for initial review

  • Java SDK

    • Generating the SDK - review pending

  • Flux

    • Flux integration work in progress
      • Planning to present to flux community this week or next

Nov 6, 2023

Participants:

  • Name / affiliation / TZ
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple, CST
  • Sean Brennan, Bloomberg, EST

Links:

Agenda:

  • New attendees

  • Action Items

    • Ben, Add reviewers to Spinnaker FE PR

  • Hacktoberfest

    • Project
    • No resolved issues this time

  • CDEvents integrations

    • Project: https://github.com/orgs/cdevents/projects/4
    • Proposed implementations at Apple that could potentially be open-sourced if the community is interested
      • Event bus - with authentication/autorization
      • Collector - for collecting events in a distributed way. Might not be needed at this stage, before we reach a certain scale of events sent
      • Links service - for connecting events
      • Events storage - for storing and retrieving events
    • Does the CDEvents SDK propagate for any specific infrastructure?
      • No, they should all be based on the corresponding Cloudevents SDK

  • Connecting & linking events

    • PR
    • (Andrea) Fan-out/fan-in support
      • Supported today through links
      • It would be nice to support through CDEvents context alone
        • What about adding a list of parent_ids into the context (together with chain_id) for a simple solution for fan-out/fan-in?
        • Alternative add the link list into the context?
      • NIT: could we call the chain_id a graph_id

  • <addme>

Oct 30, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, he/him, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Sean Brennan, Bloomberg, UTC-4

Links:

Agenda:

Oct 23, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, he/him, IBM, PDT
  • Ben Powell, Apple, CST
  • Emil Bäckmark, Ericsson, UTC+2
  • Sean Brennan, Bloomberg, EST
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1
  • Owen Bower Adams, Intelligent Growth Solutions, BST

Meeting Recording

Links:

  • v0.4 Roadmap

    • Planned for TBD

  • New meeting schedule (reminder)

  • Connecting Events

    • Connecting/linking events
    • Ben to address comments on the links section
    • Ben will update the PR with schema updates (all events)
    • Ben plans to create a mock CI/CD system to demonstrate links to demonstrate CDEvents at Apple

  • Ticket Proposal

    • Sean and Ben met weekly to discuss about this
    • Approvals
      • Dedicated subject or use the tickets subject
      • At Apple: an approval is every time a manual approval is involved
      • Good for auditing
        • Example, during freeze, two step approval process is required
      • Emil: at Ericsson, approval is only at review time
      • Alternative: add "approved" preticate to all (many) events
      • Ben and Sean to identify pros/cons of the two options
        • A new "approval" subject (declined, accepted?, in progress)
        • Add "approval" predicate to several existing subjects
    • Tickets
      • ticket subject
      • Predicates could be what happened or the ticket state
      • Emil: workflow can be customised per project/team, predicates should not dictate the workflow names
    • Approvals
      • Owen:
        • Automated approval can be part of the model
        • An approval can come from humans or machines or a combination
        • It would be good to include this in the "approval" subject docs
      • Emil:
        • PRs can be automatically approved if they are small enough

  • PR Reviews

  • Deprecation of fields

    • Option1 - Document on the markdown, define an ETA for removal
    • Option2 - Keep the deprecate fields forever
    • Option3 - Just update the version and drop the field
    • Related PR
      • PR not urgent, good to use to define the deprecation process
    • Action Andrea to capture this in a ticket

  • SDKs Updates

    • Java
    • Rust
      • Scaffolding started as part of Hacktoberfest
    • .NET
      • Owen: have been working wih a manually generated .NET SDK for a couple of months. Work is starting on a generated version.
    • Ben: what languages are tools written in?
    • Swift used heavly at Apple

  • CDEvents Use Cases

    • Owen to present internal use cases for CDEvents (added to the agenda in a few weeks)

  • Spinnaker

    • Ben to add reviewers to the Front End PR

  • <other topics, please add>

Oct 9, 2023

Participants:

  • Name / affiliation / TZ
  • Emil Bäckmark, Ericsson, UTC+1
  • Andrea Frittoli, IBM, UTC+1
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1

Links:

  • v0.4 Roadmap

    • Planned for TBD

  • New attendees

  • Adam working on a Flux integration

  • Connecting Events

  • Proposed New Meeting Schedule:

    • CDEvents APAC meeting, 10am UTC, every 4 weeks on Monday, starting 30/10
    • CDEvents EMEA/NA meeting 1, 3pm UTC, every other Tuesday, starting on 17/10 (no change!)
    • CDEvents EMEA/NA meeting 2, 3pm UTC, every other Monday, starting on 09/10 (takes the slot that used to be SIG Events)
    • SIG Events, 3pm UTC, every 4 weeks on Monday, starting 16/10 (same time, different week)
      • Topics that are broader than CDEvents, e.g. VSMI or events in general

  • PR Reviews

  • SDKs Updates

    • Java
      • Part 1 of generating the SDK is merged
      • Part 2 to be reviewed?

  • Spinnaker integration

    • Jalander working on addressing review comments

  • Ben: can we add links to recording in these notes?

    • Andrea to share the link to the videos

  • <other topics, please add>

Oct 3, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC+1
  • Ben Powell, Apple, CST
  • Emil Bäckmark, Ericsson, UTC+2
  • Daniel Han, Bloomberg, EDT

Links:

  • v0.4 Roadmap

    • Planned for TBD

  • New attendees

    • Sean Brennan - Bloomberg
      • E2E visibility
      • Automation in pipelines

  • Discuss introduction of new ticket/issue events, with Sean Brennan, base on Slack chat

    • Also detailed in issue 164
    • Sean: Product approvals through issues
    • Ben: CDEvents for ticketing systems needed at Apple
    • Link between PRs and issues
      • At bloomberg: Jira ID in the PR title
      • Emil: at Ericsson, specific syntax in the commit message
      • Andrea: CDEvents should define the data model of how tickets and CSM/other events are connected
    • What does the data model look like?
      • Possibly a ticket subject
      • Several events:
        • Create event is needed
        • Ben: we will need a "resolved" event too. It would be important for deploy/rollback use cases
        • Sean: updates / transition events, e.g. approval
        • Do we need to track all ticket events?
          • Emil: we should not replicate the whole data model of ticketing systems
          • Ben: we can optional components of the tickets spec
          • Sean: if we define events, consumers may use those they need
      • Daniel: identify the bare minimum data model we can start with
        • We can add more fields, but we need to be careful and not to slip into adding too much
    • Next steps:

  • Meetings Schedule Review

    • Weekly alternate times
    • SIG Events bi-weekly
    • Proposal for new meeting schedule
      • Every other Monday and every other Tuesday
      • Reduce APAC meeting to monthly/optional

  • OTel proposal

  • Connecting/linking events

    • Ben to document advantages of using separate link events

  • Hacktoberfest

  • PR Reviews

  • SDKs Updates

    • Java
      • Part 1 of generating the SDK is merged
      • Part 2 to be reviewed?

Sep 19, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli. IBM, UTC+1

Links:

Sep 19, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, he/him, IBM, UTC+1
  • Ben Powell, Apple, CST
  • Daniel Han, Bloomberg, EDT
  • Emil Bäckmark, Ericsson, UTC+2
  • Dotan Horovits, Logz.io, CNCF, UTC+3
  • Adam Kenihan
  • Evan Elms

Links:

Agenda:

Sep 11, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Andrea Frittoli, IBM, UTC+1
  • Victor Lu

Links:

Agenda:

  • New attendees

  • Action Items

  • Visualisation POC (@SIG Events meeting)

    • PR: cdevents/visualisation#1
    • GitHub Action with hosted worker
    • Visualization independent from tools
    • Two kind of visualization tools
      • CDEvents specific
      • Generic (Grafana based)
    • Dependency to the link model
      • Current assumption do not affect the visualisation codebase much
      • Data collection part depends on the link model
    • POC Demo Recording

  • (Victor) Comparison of different CI/CD

    • It would be nice to have a comparision table to understand which tool can be used for what
    • Discussion forum would be helpful too

  • Hacktoberfest

    • Action for all: label issues for hacktoberfest

  • Release Planning

    • A few PR were merged
    • We could make a release if it takes too long for connecting events to be implemented

  • SDK Updates

    • Java v0.1.2 released
    • Dotnet SDK
      • obowersa plans to contribute the SDK
      • slack thread
      • Would be good to plan a presentation / discussion in the CDEvents WG

  • Integration updates

  • Connecting/linking events

    • Ben has some action items to update the PR based on the latest discussion
    • List of parent ids to be removed for now and potentially added back later on

  • <addme>

Sep 5, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Ben Powell, Apple, CST

Agenda:

  • Connecting/linking events, using trace spans

    • How to create/finish spans
      • We could hide the complexity of calling a Links Service, when producing events, within the SDK.
      • Having a links service as part of producing an event adds a synchronous/blocking call, unless the links service is also called through the asynchronous message bus
    • Specific or generic relations types
    • Links/relationships between events is critically important if not all info relevant for a consumer is contained within a specific event.
      • Should a service.deployed event contain all relevant info from artifact.packaged and change.merged event, or should the relationships between the events be used to find that info.
    • What should the global id / trace id be called?
      • Global id, Trace id, Context id, Trail id, Lifecycle id, ...
      • Ben will create a poll on CDEvents Slack to vote for the right term
    • For now the parent id will be removed from the PR, just keeping the global id in there.
    • To be discussed further and eventually decided on:
      • Should the relationships/links be contained in the Links Spec and event data in CDEvents spec, or should it all be combined in the CDEvents spec?
        • Span id to be the only relationship to keep in the CDEvents spec, and the rest of relationships in the Links spec?
        • Separating the data from relationships introduced a dependency between the two, both ways, and they need to evolve hand-in-hand

  • Hacktoberfest

Aug 28, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Brad McCoy, Basiq, UTC+11
  • Adam Kenihan, UTC+1

Agenda:

  • Incident Events

    • (Brad) shows an implementation of incident.reported event with Atlassian Jira

  • GitHub Actions

  • OpenTelemetry integration. Not much news. Looking forward to discussion on Sept 5.

Aug 22, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Ben Powell, Apple, CST
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1
  • Daniel Han, Bloomberg, EDT
  • Evan Elms
  • Name / affiliation / TZ

Links:

Agenda:

Aug 14, 2023

Meeting canceled since no one showed up

Aug 8, 2023

Participants:

  • Andrea Frittoli, IBM, UTC+1
  • Emil Bäckmark, Ericsson, UTC+2
  • Ben Powell, Apple, CST
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1
  • Tracy Ragan, DeployHub / Ortelius
  • Adam Kenihan

Links:

Agenda:

  • New attendees

  • Action Items

  • Hacktoberfest 2023:

    • From CDF TOC meeting:
      • Roxanne wants to know by August 31st
        • Which projects plan to participate
        • Blog posts need to be live and sent to CDF by September 29th
        • Project contact persons need to be identified
      • Hacktoberfest 2022 info on CDF Website
      • Ideally list of participating projects and contact persons by next TOC meeting on Aug 15th
    • Shall CDEvents participate?
      • It requires a little bit of initial investment, but not too much
      • The more we invest, the better the return, see Jenkins 2022 https://www.jenkins.io/events/hacktoberfest/
      • It requires extra review bandwidth during the event
      • Good for new reviewers and prospective reviewers to refine their skills and build review numbers
      • It usually brings mostly occasional contributors, but it may help us tackling our bug backlog and implement small improvements on docs, tools and website
    • If we participate, we need:
      • One person driving the effort (contact for CDF)
      • List of interested CDEvents projects, and project/areas ideas
      • A blog post or github issue
      • Ideally (but optional) list of interested reviewers / mentors
    • Tracy:
      • We should participate
      • Happy to write a blog post
      • Security Events?
      • Point of contact for the CDF
    • Ben: security events might be too much for hacktoberfest
    • Emil: hacktobefest should be easy to review
    • Topics:
      • Ben:
        • SDK code generation, modelling
        • Documentation
        • Abstraction layers
      • Andrea:
        • CLI
        • Autogeneration of docs
        • Investigate async
    • 2022 Project: https://github.com/orgs/cdevents/projects/3/views/1

  • Connecting events

  • v0.4 Release

  • v1.0 release

  • <please add>

July 31, 2023

Participants:

  • Andrea Frittoli, IBM, UTC+1
  • Neil McGonigle, Fidelity, UTC+1

Links:

Agenda:

July 25, 2023

Participants:

  • Ben Powell, Apple, CST
  • Andrea Frittoli, IBM, UTC+1
  • Daniel Han, Bloomberg, EDT
  • Neil McGonigle, Fidelity, UTC+1

Links:

Agenda:

  • New attendees

  • Action Items

  • (Ben) New optional fields for change events

    • created change event should contain a top level description

    • commit array should be present in change events

    • Branch info in change events

    • Bundle artifacts are required to avoid sending one event for each single artifact

      • Example deployment @ Apple with 500+ artifacts
      • This is a single deployment, and there are many deployments

    • Ben: adding more fields, but make them optional

      • Note: optional -> mandatory is a breaking change
      • Requiring API Calls is not good for interoperability as they shift the issue of interoperability

    • Dan: for test cases we have testcaserun which could generate 1000s if events

      • How would bundling help?

    • Dan: is there a cadence for releases

      • Andrea: We are automating the SDKs updates
      • Andrea: Currently we plan releases on demand, we could switch to a regular cadence if we have enough contributions
      • (A) Andrea to make a proposal for regular release candence

    • Ben: How do we help people transition from customData to CDEvents data

    • Daniel: we could add helpers/adapters in the SDK that help with that

    • (A) Ben to create an issue to track this discussion

  • (Ben) Not all data in events can be disclosed to everyone

    • Some team cannot broadcast their events to all
    • Identity of sender
    • Ben to create an issue
    • Dan: can we have an FAQ page, recommendation about things
      • How do I deal with security
      • How do I add data to the subject
      • Can be open-ended i.e. we have the question, not the answer yet
        • Andrea: we have the primer today, but that does not answer specific questions
        • Ben: it should not be in the spec
        • Daniel: create an issue

  • (Ben) What about Ticket/Feature/Issues

    • Brad McCoy is interested in this feature
    • Steve Pereira from VSMI

  • Connecting Events

  • Bundling of events

    • Daniel: Binding events in the some format, so that they are sent out all together, it could help consumers connect the dots

July 17, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC+1

Links:

Agenda:

July 11, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC+1
  • Ben Powell, Apple, UTC+5
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1

Links:

Agenda:

  • New attendees

  • Action Items

    • (Ben) Meeting with Spinnaker for CDEvents demo
      • Ben to create the meeting in the next ~1w
      • Invite Spinnaker team as optional
    • (Andrea) Create an issue / doc / slack channel to discuss artifact events

  • CDEvents Visualization - Reference Architecture

  • Connecting Events

    • PR
    • (Andrea) How do we handle proposals?
      • Switch to hackmd
      • Add a proposal folder in the spec repo
      • Use a separate repo
      • Else?
    • (Andrea) Trying to visualise the connecting events proposal in a simple example

      • How do we carry the context?

        • Where global_id, parent_id and links come from in each step?

      • How does each of those help us in connecting those three events

June 30, 2023

Participants:

  • Victor Lu
  • Ben Powell
  • Emil Bäckmark
  • Andrea Frittoli

Agenda: Session dedicated at Connecting Events

  • PR
  • Review of comments on the PR, discussion tracked in comments
  • We could use some of the nomenclature from the VSMI reference arch

June 27, 2023

Participants:

  • Name / affiliation / TZ
  • Emil Bäckmark, Ericsson, UTC+2
  • Fatih Degirmenci, CDF, UTC+2
  • Tracy Ragan, DeployHub / Ortelius
  • Daniel Han / Bloomberg / NY
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1
  • Neil McGonigle, Fidelity, UTC+1

Links:

Agenda:

  • New attendees

    • Carmit from JFrog

  • Action Items

    • (Ben) Meeting with Spinnaker for CDEvents demo
      • The PR is being reviewed
      • Meeting still TBD

  • SDK Updates

    • Golang: v0.3.2 patch release

      • Fix the CDEvents spec version
      • Set CloudEvents Id

    • Java:

      • Release v0.1.2 - ready to be done
      • Generating the SDK

    • Security Events:

      • Ortelius and GUAC talking to develop security use cases / events

  • Tools Adoption Updates

  • CDF Online meeting

  • Artifact events

    • Carmit:

      • Events produced by an artifact registry
        • bundling of artifacts
        • promotion of artifacts/bundles
        • distribution
        • release

    • Dan:

      • Tagging of artifacts as event

    • Carmit:

      • Generally events should contain only event data
      • More data about the artifact can be pulled via APIs

    • Emil: What is the bundling of events specifically

    • Carmit: a bundle is a group of artifacts (like docker image, helm chart etc), a bundle can inculde up to 1k artifacts

    • (Andrea) Create initial tickets to track the events

    • Artifact pull/pushed/deleted but also moved (for artifactory)

    • Artifact scanning events are security type of events and should be produced by the tool the perform the security scan

    • Quota events in Harbor may not be good candidates for CDEvents

    • Archiving may be relevant from an audit trail point of view, less relevant from and SDLC point of view

    • Tags could be used to indicate that an artifact is ready for promotion or deployment

    • Emil: start a document about events from registries

      • Capture events for different artifact registry
      • Collaborate on the document
      • Use this document as input for the specification work
      • Create a slack channel for artifact registry specific discussions

  • Issue tracking events

    • Carmit: it would be interesting to have those associated with artifacts

  • Spec Topics

    • Connecting Events
      • PR ready for review

  • Collaborations

    • VSM Interoperability
      • New monthly meeting for CDEvents + VSMI collaboration
      • Meeting Notes
        • Steve introduced the VSMI Topology and Ontology
        • CDEvents is part of picture
    • CNCF App Delivery TAG
      • Looking for contributors to drive/work on a version of podtato-head based on CDEvents

  • CDEvents visualisation

  • <addme>

Jun 19, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Neil McGonigle, Fidelity Investments, UTC
  • Andrea Frittoli, IBM, UTC+1
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

    • Ben to arrange a meeting with Spinnaker team for CDEvents demo

  • (Brad) Update on GitHub action for CDEvents

    • Mock end point implemented
    • Testing different example, getting ready for first version
    • To be presented in the next version

  • (Brad) Events for featureas and issues

    • CDEvents in scope for features and issues?
      • Issues can be associated with incidents as well
      • Related to VSM interop
      • Related to connecting events discussion
      • Source code events could be associated to issues/features delivered in a certain code change

  • (Andrea) Harbor proposal pull request

    • Changes on CDEvents side may be required
    • (Emil) We should be consciuous about the use cases associated with events when adding new events
    • (Emil) Are events related to CD? We don't have a definition today of what is in scope for CD
      • Relevant for triggering a CI/CD workflow
      • Relevant for observation of a CI/CD overall workflow
    • (Emil) We should invite JFrog to the conversation about relevant events for artifact registries
    • (Neil) What kind of events (if any) does artifactory support today?

  • (Andrea) Parent-child pipelines use case cdevents/spec#142

    • (Emil) Is this within a pipeline execution or upstream/downstream dependencies?
    • (Emil) Example: a test step is replaced with a call to an external test system which may have its own pipeline and events. How do events from the test system refer back to the original pipeline?

  • v0.4 Planning (in progress):

Jun 13, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC+1
  • Ben Powell, Apple, CST
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1

Links:

Agenda:

  • Action Items (None)

  • CDF TOC:

    • Voting for the CDF TOC representatives ongoing
    • Please vote if you're eligible!

  • CDF Outreach Committee:

    • Proposed project updates:
      • CDEvents, a common specification for Continuous Delivery events: it drives interoperability and brings disruption in the CD ecosystem with a growing and active community. Contributors from 20 companies, 142 twitter followers, 85 GitHub stars.
        • Releases v0.2, v0.3: test and incident events, initial software supply chain security. Java SDK to Maven.
        • Tools: Jenkins, Testkube, Spinnaker (implementing), Tekton (experimental), ArgoCD (RFC), Harbor (RFC). More tools have expressed interest (Shipwright, JX, Tracetest, JReleaser, Flux)
        • Collaborations: VSM Interop, CNCF App Delivery TAG, OpenSSF, CDF SIG Interop
        • Interested companies: Fidelity (adopter), SAS, Apple, Ericsson, IBM and more
        • What’s next: connecting events, visualisation, supply chain security, more tools and adoption

  • Connecting events

  • Spinnaker

    • Ben to arrange a meeting for a demo of the current implementation

  • Fidelity adoption:

    • User story
    • Starting from the central point: Jenkins
    • Looking forward to artifactory plugin
    • Challenges:
      • Versioning (of Jenkins)
      • Implementation of the plugin (Jenkins documentation issue)
    • Events are sent to a Kafka queue
    • Goals:
      • Improve developer experience: automatic audit trail for artifacts, track via commit id
      • Visibility towards management of application landscape
    • Non-relational DBs are really beneficial
      • But they do present challenges with versioning
      • Posgres provide a JSON type column

  • CDEvents visualisation

  • Python SDK

    • Adopting pydantic in progress
    • Release to pypi in progress
    • Question: generation of the SDK?

  • v0.4 Planning (in progress):

Jun 5, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Andrea Frittoli, IBM, UTC+1
  • Name / affiliation / TZ

Links:

Agenda:

May 30, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Ben powell, Apple, CST
  • Fatih Degirmenci, CDF, UTC+2
  • Andrea Frittoli, IBM, UTC+1
  • Jalander Ramagiri, Ericsson Software Technology, UTC+1
  • Daniel Han, Bloomberg, UTC-4
  • Andrew Fenner, Ericsson Software Technology, UTC+1
  • Adam Kenihan, Ericsson Software Technology, UTC+1
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • Welcome Daniel Han!

    • Standardization around testing
    • Special focus on integration testing
    • Interested in contributing back to CDEvents

  • TOC Project representatives

    • Process
      • 4 seats from 9 projects in TOC
    • Nominations
      • The nomination period starts on May 22, 2023 and ends on June 5, 2023.
    • Emil has volunteered to be nominated from CDEvents. The nomination will be submitted later today.

  • CDEvents visualization discussion - Adam/Andrew/Jalander from Ericsson Software Technology

    • Follow-up: track slide questions on github
    • Discuss libraries vs. services in this area
    • Share screenshots of demos?
    • Issue on visualizing CDEvents: cdevents#25

  • Update on Connecting Events

  • CDEvents usage at Bloomberg - Daniel Han from Bloomberg

  • (Andrea) Signed CDEvents

    • We should probably delegate signature to the envelope layer
      • That would allow us to sign the entire payload
      • Which CE headers would we like to be included in the signature?
    • Trying to restart the conversation on CloudEvents side
    • It would be really useful to have a security expert involved in the discussion
    • Signatures associated to the envelope layer means that they would only be available with certain bindings
      • That should be acceptable

  • Updates:

    • CDEvents + Argo:
    • CDEvents + Harbor:
    • CDEvents + other registries
      • JFrog, meeting today
      • Chainguard, planning POC
    • CDEvents + GitHub:
      • Brad working on a GitHub App
        • SCM events
        • Pipeline events (GH Actions)
    • CDEvents + Testkube:
      • Implemented in dev
      • Release coming soon
    • CDEvents + Spinnaker
      • PRs ready for review
      • Demo available for Spinnaker meetings
      • Ben to ping people on Spinnaker side
        • Organise a meeting to see the demo with all interested parties

  • CDEvents v0.4 planning

  • Other topics?

May 22, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Brad McCoy, Basiq, UTC+10
  • Name / affiliation / TZ

Links:

Agenda:

  • Updates from last meeting

    • Discussed connecting events
    • Ben presented a proposal
    • Ben to make a PR, discuss internally at Apple and then present to the group

  • Brad created a PRs to update licensing

  • v0.3 review

    • Blog post

  • Updates from CDCon

    • CDEvents Summit

      • Events broker

        • Challenges with Kafka. It would be great to get a sharable feedback on Kafka experiences
        • Should it be part of CDEvents or reference architecture
        • FRSCA use an opinionated set of tools, but as an example to represent their reference architecture

      • Platform and CDEvents

        • submit CDEvents to the evidence storage and then the platform take over
        • Then you can switch between tools (Tekton, Jenkins, etc) as long as they can provide CDEvents JSON to the storage

      • Modeling feature flags

        • In the context of OpenFeature, should model feature flags (and perhaps configurations in general) in CDEvents?
        • We don’t support those events today, but that’s something we could model more accurately
        • Feature flag changes are a runtime event, with no deployment involved
        • Is that a deployment too? CDEvents could help make common terminology here
        • If we put feature flags data in deployments, a change to feature flags would require a new deployment event. Too much granularity can become difficult to manage

      • How do we get CDEvents in big cloud vendors?

        • We should have projects in the CDF adopting CDEvents, explain benefits at TOC
        • Users that use CDF tools adopt CDEvents and can explain the benefits
        • It becomes easier to talk to commercial CI/CD tools first, and then to cloud providers
        • What about CDEvents for GitHub actions?
          • We’re building an adapter, but really we should have CDEvents natively eventually

      • Cloud is not the only place where we deliver software, creating momentum there would help too

      • Hosting CDEvents presentations for the benefits of other projects

      • Visualization

        • It would be nice to have an open source framework (react?) to visualise events
        • Visualisation can be good do demonstrate the value of CDEvents
        • Similar project in the JS space
        • UI would be really a cherry on the cake on top of standardisation, it can add great value

      • Benefit from artifactory and other registries if they had a plugin that generates CDEvents automatically

      • End users can help by talking to vendors about features they’d like to see in products

    • Michael Crenshaw reached out about implementing CDEvents in Argo CD

      • GitOps, update from registry use case
      • Also generating events
      • Michael to start the process on Argo side

  • Argo

  • CDEvents in the OSS keynote, thank you Tracy!

  • Include updated architecture picture in docs

    • It would be good to show what kind of events are used where
    • Links to examples

  • Configuration changes

    • Not part of the CDEvents scope today
    • Good match for VSMI scope

  • GitHub adapter

    • Brad to start this week
    • Adam is also working on similar adapter for Gitlab
    • SCM, Pipeline and Testing event can all be in scope, so we could provide visualizatio of GitHub and GitLab pre-merge pipelines
    • With GitLab we used to talk to Kevin
    • Interoperability stories
      • Switch betweeb GitLab and GitHub, combined with other tools (e.g. Tekton and Testkube)
      • Send test events from Tekton first, then adopt Testkube - similar CDEvents are sent and consumers are not affected
    • Brad to create issues to track this

  • SDK updates

    • Golang v0.3
    • Java updated to v0.1.2
      • Working on a release for v0.1.2
      • Working on integrating JReleaser too
      • Next: automation for the Java SDK

    • Python

  • Implementation updates

  • V0.4 planning

  • Other topics?

May 16, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Ben Powell, Apple
  • Tracy Ragan
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • TOC Project representatives

    • cdfoundation/toc#202
    • 4 seats from 9 projects in TOC
    • The nomination period starts on May 22, 2023 and ends on June 5, 2023.
    • Eligible Voters
      • Are you on the voters list? If not, and if you consider yourself a contributor to CDF or any of its projects, you could sign up on this form.

  • v0.3 release

    • Tracking issue: cdevents#24
    • Release done, announcements missing

  • v0.4 release

    • Focus: Connecting events

  • Connecting Events

    • https://hackmd.io/-Or6hobHSLWVj4duAWX7nA
    • A lot of discussion around the links model, clearing out some misconceptions about Eiffel and nailing down some scenarios and use cases for the links/parents
    • To find other events than the parents there is a need for a "links service", i.e. a database of previously sent events (often called Event Repository in Eiffel)
    • Ben will provide a draft PR hopefully later this week

  • <addme>

May 2, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+2
  • Andrea Frittoli, IBM, UTC+1
  • Name / affiliation / TZ

Links:

Agenda:

May 2, 2023

Meeting canceled due to too few participants

April 24, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, UTC+1
  • Emil Bäckmark, Ericsson, UTC+2

Links:

Agenda:

April 4, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Tracy Ragan, DeployHub, CDF TOC, UTC-7
  • Evan Elms
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • Release v0.2 status

    • Remaining actions:
      • Andrea to finish the announcements

  • Release v0.3 status

  • SDK updates

    • Golang
      • v0.2 released
      • SDK is now generated from schemas hosted in the spec repo
      • SDK now runs tests against the examples defined in the spec repo
    • Python
      • Working on GitHub Actions to automate stuff
    • Java

  • Testing events

  • Tools integrations

    • Spinnaker
    • Jenkins
      • Progressing well
      • Hopefully be contributed to open source by May
    • TestKube

  • Connecting Events

  • Upcoming meetings

    • Monday April 10th.
      • Bank Holiday in Sweden, but not everywhere else so the meeting is kept.
    • Tuesday April 18th.
      • Canceled due to KubeCon Europe? To be discussed on Slack

March 27, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • Release v0.2 status

    • Release notes

    • Documentation

    • Golang SDK

      • Added support for multiple versions
        • Always produce latest version
        • Parse any compatible future version (minor/patch)
        • Parse any compatible old version (minor/patch)
        • Unknown data in future versions is ignored for now
      • V0.2 updates WIP
        • 80% implemented generating the SDK

    • Next steps:

      • Release golang SDK
      • Move to v0.3-draft on main
      • Andrea to finish the announcements

  • Python SDK

    • New contributor from Fidelity to work on pydantic issue
    • Evan continued working on release automation for Python and Java

  • Testing events

    • The existing PR will need to be updated based on v0.2

  • Tools integrations

    • Spinnaker
      • RFC merged!
      • It should be ok to start the implementation
    • Jenkins
      • Framework up, pipelinerun events
      • Work happening internally at Fidelity for now

  • Connecting Events

  • v0.3 Roadmap

March 21, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple, UTC-6
  • Jalander Ramagiri, Ericsson Software Technology, UTC
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

    • n/a

  • Release v0.2 status

    • All spec PRs merged
    • Website update ready
    • Golang SDK
      • Added support for multiple versions
        • Always produce latest version
        • Parse any compatible future version (minor/patch)
        • Parse any compatible old version (minor/patch)
        • Unknown data in future versions is ignored for now
      • Release 0.1.1 and 0.1.2
      • Main branch updated to 0.1.2
      • V0.2 updates WIP (incident events)
    • Next steps:

  • Python SDK

    • CI linting using flake8 working locally (ready to go)
    • Release to pypi
      • Vanilla framework is already there
      • TOML file with metadata required
    • Next step: v0.1 release

  • Testing events

    • The existing PR will need to be updated based on v0.2

  • Tools integrations

    • Spinnaker
      • RFC is getting close to merge
      • It should be ok to start the implementation
    • Jenkins
      • Framework up, pipelinerun events
      • Work happening internally at Fidelity for now

  • Connecting Events

    • https://hackmd.io/-Or6hobHSLWVj4duAWX7nA
    • Make a PR with hybrid approach so we can have hands on experience
    • Continue working on the DORA metrics POC and try to apply different way of connecting events

March 13, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Andrea Frittoli, IBM, UTC
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • Incident Events

    • PR Merged
    • Next steps
      • Include in SDKs
        • Andrea Create and issue for each SDK
      • Cut a release
      • Update the website with the new event group

  • v0.2 Roadmap

  • SDKs

    • Python SDK
      • We will need pypi publishing
    • Java SDK
      • For v0.2 (or v0.3) for Maven central repository
      • Naming: defined in the pom files dev.cdevents/java-sdk
    • Go SDK
      • Managed by the tooling directly
    • Investigate external tool for secrets for release mgmt
      • 1password
    • Discorability of SDKs important for integrations
    • Licensing
      • Apache 2.0 license should be in all SDK repos

  • Testing events

  • Tools integrations

    • Spinnaker RFC
    • Jenkins
      • Fidelity plans to contribute a CDEvents plugin

  • <addme>

March 7, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Andrea Frittoli, IBM, UTC
  • Robert Reeves, Liquibase, UTC-6
  • Name / affiliation / TZ

Links:

Agenda:

  • Action Items

  • Spinnaker integration:

    • Robert's proposed plan is:
      • Spinnaker to support CDEvents - RFC
      • Ben talking about Spinnaker + CDEvents on behalf of Apple

  • Incident events

    • "Continuous Operations" or "Continuous Operation"?
      • No reference in the json schema
      • let's keep the plural version for now
      • we can discuss with SIG interop about naming

  • URI vs. URI-reference

    • Proposal: keep URI-reference as enforcement, propose URI as best practice in the spec
    • Extend cdevents/spec#116 to include best practices

  • Connected events

    • What would it take to have more options optional?
    • What it would look like from syntax POV

  • Testing events

  • Tools integrations

    • Spinnaker RFC
    • Jenkins
      • Fidelity plans to contribute a CDEvents plugin

  • SDK Updates

    • Python SDK
      • Erik in between jobs
      • No may not expect updates until May/June
    • Java SDK
      • Should be ready for v0.1

  • <addme>

Feb 27, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Andrea Frittoli, IBM, UTC

Links:

Agenda:

  • Action Items

    • (Andrea) Create an issue about defining the process for formal releases cdevents#23
    • (Andrea) Add details about tracing contexts in Connecting events
      • Still pending
    • Connected events
      • Flesh out Hybrid approach section (Ben)
      • Ask AI/ML what links proposal works best (Ben/Emil)
    • Spinnaker RFC
      • Review new commits on RFC (Ben)

  • Incident events

    • Comments to be answered

  • Connected events

    • Need to clarify the difference between various IDs (trace, context, global)
    • For hybrid approach, how does it work from a consumer POV if either or both links and global ID can be provided? Needs to be clarified

  • Testing events

    • Comments to be answered

  • Tools integrations

  • Spinnaker RFC

    • Review new commits on RFC (Ben)

  • SDK Updates

    • Python SDK
      • Erik in between jobs
      • No may not expect updates until May/June
    • Java SDK
      • Should be ready for v0.1

  • Events for Supply Chain

    • To be discussed at SIG Events this afternoon
    • Signatures, SBOM, etc

  • <add me>

Feb 21, 2023

Participants:

  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple, CST
  • Robert Reeves, Liquibase, CST
  • Fatih Degirmenci, CDF, UTC+1

Links:

Agenda:

  • Action Items

    • (Andrea) Create an issue about defining the process for formal releases
    • (Ben) Add use cases about Global ID in Connecting events
    • (Andrea) Add details about tracing contexts in Connecting events

  • Incident events

  • Connected events

    • Flesh out Hybrid approach section (Ben)
      • Expand on how to relate test artifact events to eachother, which can be done by relying on Eiffel instead of the global ID.
    • Ask AI/ML what links proposal works best (Ben/Emil)

  • Testing events

  • Tools integrations

  • Spinnaker RFC

    • Review new commits on RFC (Ben)

  • SDK Updates

    • Can we generate SDKs from our schemas?
      • Similar generations has been done at Liquibase (Robert)
      • OpenAPI/Swagger
        • Used everywhere
        • JSON/Yaml
      • Smithy
        • Heavily used in AWS

  • <add me>

Feb 13, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, GMT
  • Emil Bäckmark, Ericsson, CET
  • Ben Powell, Apple, CST
  • Brad McCoy, Basiq, AEST

Links:

  • v0.2 Roadmap
    • Planned for Feb 16th
      • (Andrea) Should we reschedule?
      • We could release even if we have incident events alone

Agenda:

  • Action Items

    • We can document in the primer that if there is risk of confusion between an object and its execution we should append Run to the subject

  • Test events

    • Ole cannot join today
    • Ole to review latest comments on PR
    • Emil would like to review

  • Release process - how long changes can be merged before a release

    • Relatively informal process for now
    • Favouring speed for now, initial 0.x release
    • More formal process required in future
      • (Andrea) Create an issue about defining the process

  • Incident events

    • Review remaining comments
    • Subject Type
      • Type is optional
      • We should link standard fields in table to the core
      • Goal should be to make things as easy as possible
      • Separate PR to document subject type is a more clear way in scope for 0.2
      • Andrea to check the go SDK - if it's required
      • We should document that it's the same as what's in the event type

  • Connecting events

    • (A) Ben to add use cases about Global ID
    • (A) Andrea to add details about tracing contexts

  • SDK updates

    • Java
    • Golang
    • Python

  • Tool integration updates

    • Spinnaker
    • Jenkins
    • Jenkins-X
    • Tekton
    • Kubetest

  • v0.2 Roadmap Review

Feb 7, 2023

Participants:

  • Name / affiliation / TZ
  • Andrea Frittoli, IBM, GMT
  • Ben Powell, Apple
  • Emil Bäckmark, Ericsson, GMT+1
  • Robert Reeves, Liquibase / CDF TOC, CST (GMT-6)

Links:

Agenda:

  • Action Items

    • We can document in the primer that if there is risk of confusion between an object and its execution we should append Run to the subject

  • Spinnaker RFC for CDEvents

    • Lessen scope of RFC and then iterate
      • RFC originally wanted to rework Spinnaker's architecture, which is very difficult, so instead we lessened the scope to just have Spinnaker first injest CDEvents
        • If this goes well, we can look to re-architecting Spinnaker to utilize more of CDEvents
    • Integrating CDEvents with Spinnaker
    • Jalander created the RFC: spinnaker/governance#299
    • From the meeting:
      • Limited to a new event type in Spinnaker
      • The CDEvents event type in Spinnaker will be able to inject any CDEvent and define reactions to it
      • RFC limited for now to receiving events (to reduce scope)
      • Next RFC for sending events
    • Robert: what does CDEvents give Spinnaker Users?
    • Ben:
      • End users: plugin any system that uses CDEvents to trigger Spinnaker
      • Spinnaker maintainers: no need to maintain /add ad-hoc integration

  • Jenkins and CDEvents

    • Fidelity interested in it
    • A CloudEvents plugin for Jenkins exists today
    • Project (GSoC?): create a CDEvents pluing
      • Mentor required

  • Tekton and CDEvents

  • Jenkins X and CDEvents

  • Test events

    • Ben: abort -> cancel (consistency)

  • Incident events

    • Andrea to update the PR
    • Next step after merge golang SDK

  • Connecting events

    • Proposed plan:
      • next meeting (SIG meeting) for further notes from all parties
      • decision in two meetings (two weeks from now)
      • we can use customData to begin with to carry the information

  • SDK updates

    • Java
    • Golang
      • Plan to update once test/incident events are in
    • Python

  • <addme>

Jan 30, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ole Lensmar, Kubeshop, UTC+1

Links:

Agenda:

  • Action Items

  • Test events

    • PR proposed by Ole (thank you!)
      • TestCase / TestSuite: should we rename to TestCaseRun / TestSuiteRun
        • Consistent with TaskRun / PipelineRun
        • Emil: PipelineRun / TaskRun is tekton specific
        • Execution could be an alternative, but it's very long
      • Json schema editing is error prone
        • It would be good to have automation for boiler plate schema parts
      • Agreed that we will use *Run events
      • We can document in the primer that if there is risk of confusion between an object and its execution we should append Run to the subject
        • Emil to create an issue
        • We probably don't need to add "Run" to the "build" events, since Build is a verb already

  • Incident events

    • Draft PR
    • Design in hackmd
    • Incident reported
      • Ticket reference should be an URI
      • URI Optional or Mandatory
      • URI vs. details protect potential sensitive data in the Ticket
    • Do we need alerts?
      • Eiffel has a proposed extension about alerts
      • In eiffel an alert should be sent when there is an incident
      • Alerts are not necessarly associated to a "negative" occurrence
      • Alert events might be considered later, but not as part of the incident events PR
    • Andrea to update the PR

  • Environment uses URL (as field name) instead of URI

  • Connecting events

    • Design doc
    • No progress since last discussed
    • Comments welcome

  • Roadmap Review

Jan 24, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple

Links:

Agenda:

  • Action Items

    • Java SDK migration: (Adam) Working on a single PR
    • Spinnaker RFC: meeting setup for Jan 31st (thanks Ben)
    • Notes for 2022 archived (notes moved to CDEvents community repo)
      • Action Andrea: archive SIG Events notes too

  • Test events

    • PR proposed by Ole (thank you!)
    • Review cycle ongoing
    • More feedback welcome

  • Incident events

    • Draft PR
    • Design in hackmd
    • Reviews welcome
    • Incident will require triaging / ticketing
    • Incident
      • Detected
      • Reported -> Include a references to a ticket
      • Resolved
    • We don't want to replicate the entire lifecycle of tickets
    • Severity could be on the incident
      • Keep in custom data for now to keep things simple
    • Priority on the ticket
    • Track decision reasoning, not in the spec directly but supporting document (tbd)

  • Connecting events

    • Design doc
    • No progress since last discussed
    • Comments welcome

  • Event versions

    • Ben - The current approach with versions requires string splitting
      • For the SDK it makes (de-)serilization more complex
    • Action:
      • Document the reason for the current version structure
      • Andrea to create an issue / PR

Jan 16, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Brad McCoy, Basiq, UTC+10
  • Ole Lensmar, Kubeshop, UTC+1
  • Bruno Lopes, Kubeshop, UTC+1

Links:

Agenda:

  • Action items from last week

  • Shall we archive meeting notes from 2022?

    • (Andrea) Create an archive file for CDEvents and SIG
    • (Andrea) Sync to GitHub, add link to past ones

  • Test events

    • Proposal by Ole (TestKube) https://github.com/kubeshop/cdevents-spec/blob/main/testing-events.md
      • Moving events to a dedicated bucket
      • Tests can be executed outside of CI
    • Are CDEvents only for automated scenarios?
      • Not necessarily!
    • Agreed: Move test events to a new bucket
      • Update schema
    • Test types
      • Could be an enum
      • We could start with plain string
      • Work in the interop WG about standard naming

  • Incident events

    • cdevents/spec#59
    • (@menehune23) proposed to start with a minimalist model
    • (Emil) We need a formal definition of incidents
    • Minimal data model (starting point)
      • Subject: Incident
      • Attributes:
        • ID, Source (mandatory in all subjects)
        • Environment (reference, mandatory)
        • Service or Artifact (reference, optional)
      • Predicates:
        • reported
        • resolved

  • Conferences

  • Other updates?

    • Jenkins X
      • Starting back after holidays, next week meeting
    • Python SDK

Jan 10, 2023

Participants:

  • Andrea Frittoli, IBM, UTC
  • Emil Bäckmark, Ericsson, UTC+1
  • Ben Powell, Apple
  • Jalander Ramagiri, Ericsson Software Technology, UTC

Links:

Agenda:

  • Spec Updates

    • Connecting events, design WIP

  • SDK Updates

    • Golang
      • No updates
    • Java
      • Adam is working on it
      • Update to the continuous deployment events
      • Needs review: cdevents/sdk-java#12
    • Python

  • Tool Updates

    • Spinnaker
    • RFC
    • Proposal: setup an ad-hoc meeting to discuss and progress on the RFC