Skip to content

Commit

Permalink
WIP incident events
Browse files Browse the repository at this point in the history
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
  • Loading branch information
afrittoli committed Jan 24, 2023
1 parent 83aa9ea commit e679a65
Show file tree
Hide file tree
Showing 5 changed files with 164 additions and 3 deletions.
File renamed without changes.
File renamed without changes.
157 changes: 157 additions & 0 deletions continuous-operations.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,157 @@
<!--
---
linkTitle: "Continuous Operations Events"
weight: 70
description: >
Continuous Operations Events
---
-->
# Continuous Operations Events

Continuous Operations events are related to the operation of services deployed in target environments, tracking of incidents and their remediation. Incidents, and their resolution, can be detected by a number of different actors, like the end-user, a quality gate, a monitoring system, an SRE through a ticketing system or event the service itself.
Multiple events may be associated to the same incident as well as its resolution, coming from diverse sources.

## Subjects

This specification defines two subjects in this stage: `environment` and `service`. The term `service` is used to represent a running Artifact. A `service` can represent a binary that is running, a daemon, an application, a docker container. The term `environment` represent any platform which has all the means to run a `service`.

| Subject | Description | Predicates |
|---------|-------------|------------|
| [`environment`](#environment) | An environment where to run services | [`created`](#environment-created), [`modified`](#environment-modified), [`deleted`](#environment-deleted)|
| [`service`](#service) | A service | [`deployed`](#service-deployed), [`upgraded`](#service-upgraded), [`rolledback`](#service-rolledback), [`removed`](#service-removed), [`published`](#service-published)|

### `environment`

An `environment` is a platform which may run a `service`.

| Field | Type | Description | Examples |
|-------|------|-------------|----------|
| id | `String` | Uniquely identifies the subject within the source. | `1234`, `maven123`, `builds/taskrun123` |
| source | `URI-Reference` | [source](../spec.md#source) from the context | `staging/tekton`, `tekton-dev-123`|
| name | `String` | Name of the environment | `dev`, `staging`, `production`, `ci-123`|
| url | `String` | URL to reference where the environment is located | `https://my-cluster.zone.my-cloud-provider`|

### `service`

A `service` can represent for example a binary that is running, a daemon, an application or a docker container.

| Field | Type | Description | Examples |
|-------|------|-------------|----------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` |
| source | `URI-Reference` | [source](../spec.md#source) from the context | `staging/tekton`, `tekton-dev-123`|
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` |
| artifactId | `Purl` | Identifier of the artifact deployed with this service | `pkg:oci/myapp@sha256%3A0b31b1c02ff458ad9b7b81cbdf8f028bd54699fa151f221d1e8de6817db93427`, `pkg:golang/mygit.com/myorg/myapp@234fd47e07d1004f0aed9c` |

## Events

### `environment created`

This event represents an environment that has been created. Such an environment can be used to deploy services in.

- Event Type: __`dev.cdevents.environment.created.0.1.0`__
- Predicate: created
- Subject: [`environment`](#environment)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `tenant1/12345-abcde`, `namespace/pipelinerun-1234` ||
| source | `URI-Reference` | [source](../spec.md#source) from the context | ||
| name | `String` | Name of the environment | `dev`, `staging`, `production`, `ci-123`||
| url | `String` | URL to reference where the environment is located | `https://my-cluster.zone.my-cloud-provider`||

### `environment modified`

This event represents an environment that has been modified.

- Event Type: __`dev.cdevents.environment.modified.0.1.0`__
- Predicate: modified
- Subject: [`environment`](#environment)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `tenant1/12345-abcde`, `namespace/pipelinerun-1234` ||
| source | `URI-Reference` | [source](../spec.md#source) from the context | ||
| name | `String` | Name of the environment | `dev`, `staging`, `production`, `ci-123`||
| url | `String` | URL to reference where the environment is located | `https://my-cluster.zone.my-cloud-provider`||

### `environment deleted`

This event represents an environment that has been deleted.```

- Event Type: __`dev.cdevents.environment.deleted.0.1.0`__
- Predicate: deleted
- Subject: [`environment`](#environment)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `tenant1/12345-abcde`, `namespace/pipelinerun-1234` ||
| source | `URI-Reference` | [source](../spec.md#source) from the context | ||
| name | `String` | Name of the environment | `dev`, `staging`, `production`, `ci-123`||

### `service deployed`

This event represents a new instance of a service that has been deployed

- Event Type: __`dev.cdevents.service.deployed.0.1.0`__
- Predicate: deployed
- Subject: [`service`](#service)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` ||
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` ||
| artifactId | `Purl` | Identifier of the artifact deployed with this service | `0b31b1c02ff458ad9b7b81cbdf8f028bd54699fa151f221d1e8de6817db93427`, `927aa808433d17e315a258b98e2f1a55f8258e0cb782ccb76280646d0dbe17b5`, `six-1.14.0-py2.py3-none-any.whl` ||

### `service upgraded`

This event represents an existing instance of a service that has been upgraded to a new version

- Event Type: __`dev.cdevents.service.upgraded.0.1.0`__
- Predicate: upgraded
- Subject: [`service`](#service)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` ||
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` ||
| artifactId | `Purl` | Identifier of the artifact deployed with this service |`pkg:oci/myapp@sha256%3A0b31b1c02ff458ad9b7b81cbdf8f028bd54699fa151f221d1e8de6817db93427`, `pkg:golang/mygit.com/myorg/myapp@234fd47e07d1004f0aed9c` ||

### `service rolledback`

This event represents an existing instance of a service that has been rolled back to a previous version

- Event Type: __`dev.cdevents.service.rolledback.0.1.0`__
- Predicate: rolledback
- Subject: [`service`](#service)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` ||
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` ||
| artifactId | `Purl` | Identifier of the artifact deployed with this service | `pkg:oci/myapp@sha256%3A0b31b1c02ff458ad9b7b81cbdf8f028bd54699fa151f221d1e8de6817db93427`, `pkg:golang/mygit.com/myorg/myapp@234fd47e07d1004f0aed9c` ||

### `service removed`

This event represents the removal of a previously deployed service instance and is thus not longer present in the specified environment

- Event Type: __`dev.cdevents.service.removed.0.1.0`__
- Predicate: removed
- Subject: [`service`](#service)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` ||
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` ||

### `service published`

This event represents an existing instance of a service that has an accessible URL for users to interact with it. This event can be used to let other tools know that the service is ready and also available for consumption.

- Event Type: __`dev.cdevents.service.published.0.1.0`__
- Predicate: published
- Subject: [`service`](#service)

| Field | Type | Description | Examples | Mandatory ✅ \| Optional ⚪ |
|-------|------|-------------|----------|----------------------------|
| id | `String` | Uniquely identifies the subject within the source. | `service/myapp`, `daemonset/myapp` ||
| environment | `Object` ([`environment`](#environment)) | Reference for the environment where the service runs | `{"id": "1234"}`, `{"id": "maven123, "source": "tekton-dev-123"}` ||
8 changes: 6 additions & 2 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -491,14 +491,18 @@ dedicated document in the spec:
- __[Source Code Version Control](source-code-version-control.md)__: Events
emitted by changes in source code or by the creation, modification or
deletion of new repositories that hold source code.
- __[Continuous Integration](continuous-integration-pipeline-events.md)__:
- __[Continuous Integration](continuous-integration.md)__:
includes events related to building, testings, packaging and releasing
software artifacts, usually binaries.
- __[Continuous Deployment](continuous-deployment-pipeline-events.md)__:
- __[Continuous Deployment](continuous-deployment.md)__:
include events related with environments where the artifacts produced by the
integration pipelines actually run. These are usually services running in a
specific environment (dev, QA, production), or embedded software running in
a specific hardware.
- __[Continuous Operations](continuous-operations.md)__: include events related
to the health of the services deployed and running in a specific environment.
Health may refer to different aspects such as performance, availability,
response time and more.

The grouping may serve in future as a reference for different CDEvents
compliance profiles, which can be supported individually by implementing
Expand Down
2 changes: 1 addition & 1 deletion tools/event-version.sh
Original file line number Diff line number Diff line change
Expand Up @@ -158,7 +158,7 @@ VERSION="${MAJOR_VERSION}.${MINOR_VERSION}.${PATCH_VERSION}${DRAFT_VERSION}"
sed -i ".backup" -e 's,"dev.cdevents.*","dev.cdevents.'${SUBJECT}'.'${PREDICATE}'.'${VERSION}'",g' "${SCHEMA_FILE}"

# Update examples in docs
for doc in core source-code-version-control continuous-integration-pipeline-events continuous-deployment-pipeline-events; do
for doc in core source-code-version-control continuous-integration continuous-deployment; do
sed -i ".backup" -e 's,__`dev.cdevents.'${SUBJECT}'.'${PREDICATE}'.*`__,__`dev.cdevents.'${SUBJECT}'.'${PREDICATE}'.'${VERSION}'`__,g' "${doc}.md"
done

Expand Down

0 comments on commit e679a65

Please sign in to comment.