Skip to content

Latest commit

 

History

History
456 lines (310 loc) · 19.6 KB

assets.md

File metadata and controls

456 lines (310 loc) · 19.6 KB

OpenTelemetry managed assets

This file is intended to list all the assets controlled by OpenTelemetry.

GitHub organization

Link: https://github.com/open-telemetry

Credential Storage

Community Resource Accounts

AWS account

Link: http://cncf-aws-opentelemetry.signin.aws.amazon.com/

  • Community account to published Lambda layers
  • Admin: Alex Boten @codeboten & Anthony Mirabella @aneurysm9

Equinix bare metal runners

Reserved bare metal machines set up as self-hosted runners for the community to run performance tests.

Equinix management console:

GitHub self-hosted runners:

  • github-benchmark-runner (16-core)
  • self-hosted (alias that repos are currently using for github-benchmark-runner)
  • Admins: @open-telemetry/admins

FOSSA

We have an OpenTelemetry team under the CNCF's enterprise account.

Link: https://app.fossa.com/

GitHub Actions large runners

Access to large runners is available to repositories on request (open a community issue), which will give access to the following runners:

  • otel-linux-latest-8-cores
  • otel-windows-latest-8-cores

Note: these pay-as-you-go GitHub-hosted runners for ARM64 are available for free for CNCF projects. CNCF and GitHub expect fair use of these provided resources. Please ensure your workloads are optimized to avoid unnecessary usage.

Admins: [@open-telemetry/admins](https://github.com/orgs/open-telemetry/teams/admins

Google Cloud account

Link: https://cloud.google.com

Grafana organization for SIG Security

Link: https://grafana.com/orgs/otelsigsecurity

  • Used to provide an overview of open security incidents in the org and historical data on how quickly we respond to incidents
  • Users: SIG-Security Maintainers, Technical and Governance Committees
  • Admins: Juraci Paixão Kröhling @jpkrohling & Armin Ruech @arminru

The GitHub organization open-telemetry-private also exists for this purpose.

Netlify

Link: https://app.netlify.com/login

Oracle Cloud account

Link: https://www.oracle.com/cloud/sign-in.html

  • Community account to run CLOWarden
  • Admin: @austinlparker (password is available in the OpenTelemetry Governance 1Password)

Artifact repositories

NuGet OpenTelemetry organization

Link: https://www.nuget.org/organization/OpenTelemetry

  • All .NET SIG maintainers are administrators of this organization.
  • Organization e-mail ([email protected]) is owned by CNCF.

MyGet OpenTelemetryCNCF account

Link: https://www.myget.org/feed/Packages/opentelemetry

  • registered under the service account ([email protected]).
  • Individual accounts of .NET SIG maintainers are administrators of the OpenTelemetry feed.
  • Admin: manage members.

NPM OpenTelemetry Organization

Link: https://www.npmjs.com/settings/opentelemetry/packages

  • Ask any of the following people if you need access
  • Owner: Mayur Kale @mayurkale22
  • Admin: Daniel Dyla @dyladan
  • Member: Bogdan Drutu @bogdandrutu

Crates

Link: https://crates.io/teams/github:open-telemetry:rust-publishers

Owners: @open-telemetry/rust-publishers

Maven

Link: https://repo1.maven.org/maven2/io/opentelemetry/

Maven doesn't have the concept of an "organization account", but these individual OpenTelemetry members have been given rights to publish under io.opentelemetry:

PyPI

Link: https://pypi.org/user/opentelemetry/

PHP Extras

SIG Extra Repositories: https://github.com/opentelemetry-php

Owners:

Packagist: https://packagist.org/?query=open-telemetry

Owners:

Communication channels

CNCF Community Group

Used by the End-User SIG to organize events (e.g. OTel Q&A, OTel in Practice, feedback sessions, etc.).

CNCF are the owners of the group, so certain requests (e.g. adding/removing organizers) need to be requested via on of these:

Link: https://community.cncf.io/opentelemetry/

opentelemetry-calendar-contributors Google Group

Used to provide write access to public OpenTelemetry calendar. See docs/how-to-handle-public-calendar.md.

Link: https://groups.google.com/g/opentelemetry-calendar-contributors

OpenTelemetry Calendar Invites Google Group

Used to automatically invite members to all OpenTelemetry calendar events, so that time is blocked on their calendars.

Link: https://groups.google.com/g/opentelemetry-calendar

  • Owners: @mtwo

Mailing list [email protected]

  • Used to register service accounts and as a NuGet OpenTelemetry organization e-mail. All .NET SIG maintainers are part of this list. Owned by CNCF.
  • Admin: add member.

Mailing list [email protected]

Mailing list [email protected]

  • Private mailing list for OpenTelemetry Governance Committee.
  • All GC members AND CNCF reps (Amye Scavarda Perrin, Chris Aniszczyk, Taylor Waggoner) are on the list and are list moderators.
  • Admin: CNCF (via CNCF Service Desk ticket).

YouTube channel OpenTelemetry

Link: https://www.youtube.com/channel/UCHZDBZTIfdy94xMjMKz-_MA/videos

  • Ask any of the following people if you need to manage the feed:
    • Owners: Amye Scavarda Perrin (CNCF rep), Sergey Kanzhelev
    • Managers: Alolita Sharma, Alan West, Austin Parker, Ben Sigelman, Eddy Nakamura

Zoom accounts

Zapier account

Link: https://zapier.com

Google Workspace accounts

Google account for [email protected]

Bot accounts

Related: Guidelines for adding new GitHub extensions.

Easy CLA

This is not really an OpenTelemetry asset as we do not have any credentials or admin access for it.

For support:

Docker Hub

  • We publish images from CI to Docker hub using https://hub.docker.com/u/otelbot account. The bot is registered using [email protected] email address and Technical Committee members are owners of this account. The Admin for bot security credentials for CI is @tigrannajaryan

otelbot

This is a GitHub App owned by @open-telemetry that you can use when automating common GitHub tasks in OpenTelemetry repos such as release automation tasks.

This GitHub App has the following permissions:

This GitHub App addresses two common issues:

  1. Since you can't push directly to main from workflows (due to branch protections), the next best thing is to generate a pull request from the automation and use an account which has signed the CLA as the commit author.

    The OpenTelemetry Bot account has signed the CNCF CLA, and you can assign it as the commit author in your automation:

    git config user.name otelbot
git config user.email [email protected]

    It is recommended to push to branch names that start with otelbot/, and to add a branch protection rule for otelbot/**/* with the same setup as documented for dependabot/**/*.

    [!WARNING] Branch protection rule ordering matters, so you will need to delete the **/** branch protection rule temporarily, then add the otelbot/**/* branch protection rule, then add back the **/** branch protection rule.

  2. When you use the built-in secrets.GITHUB_TOKEN to generate a pull request from inside a GitHub Action, workflows will not run on that new pull request without closing and re-opening it manually (this limitation is in place to prevent accidental recursive workflow runs).

    The OpenTelemetry GitHub organization has a GitHub Action secret (OTELBOT_PRIVATE_KEY) and a GitHub Action variable OTELBOT_APP_ID that can be used to create a GitHub App token which will bypass this limitation, e.g.

    - uses: actions/create-github-app-token@v1
  id: app-token
  with:
    app-id: ${{ vars.OTELBOT_APP_ID }}
    private-key: ${{ secrets.OTELBOT_PRIVATE_KEY }}

- name: Create pull request
  env:
    # not using secrets.GITHUB_TOKEN since pull requests from that token do not trigger workflows
    GH_TOKEN: ${{ steps.app-token.outputs.token }}
  run: ...

Warning

The otelbot is and needs to remain a public GitHub App in order for EasyCLA to be able to verify its CLA status.

OpenTelemetry Bot

Note

Consider using the otelbot GitHub App instead.

This is a community-owned bot account that you can use when automating common GitHub tasks (e.g. release automation tasks).

Important: You do not need to (and should not) give this account any permissions to any OpenTelemetry repository.

Link: @opentelemetrybot

The OpenTelemetry Bot addresses two common issues:

  1. Since you can't push directly to main from workflows (due to branch protections), the next best thing is to generate a pull request from the automation and use an account which has signed the CLA as the commit author.

    The OpenTelemetry Bot account has signed the CNCF CLA, and you can assign it as the commit author in your automation:

    git config user.name opentelemetrybot
git config user.email [email protected]

    It is recommended to push to branch names that start with opentelemetrybot/, and to add a branch protection rule for opentelemetrybot/**/* with the same setup as documented for dependabot/**/*. Note that branch protection rule ordering matters, so you will need to delete the **/** branch protection rule temporarily, then add the opentelemetrybot/**/* branch protection rule, then add back the **/** branch protection rule.

  2. When you use the built-in secrets.GITHUB_TOKEN to generate a pull request from inside of a GitHub Action, workflows will not run on that new pull request without closing and re-opening it manually (this limitation is in place to prevent accidental recursive workflow runs).

    The OpenTelemetry GitHub organization has a GitHub Action secret named OPENTELEMETRYBOT_GITHUB_TOKEN, which is a Personal Access Token for @opentelemetrybot with repo, workflow and read:org scope for the OpenTelemetry Bot that you can use to bypass this limitation.

    The personal access token also has workflow scope which is needed when merging upstream changes of .github/workflow files into opentelemetrybot's forks (these forks are used for automatically opening PRs against external repos).

    Maintainers can open an issue in the community repository to have their repository granted access to this organization secret.

Slack

The slack user OpenTelemetry Admin is community owned and can be used for self-servicing slack (e.g. as Channel Manager to rename spaces).

Security

The SIG Security has access to the following tools, with GC and TC members welcome to request access to them as well. Find more details under tools on the SIG Security GitHub repository.

  • Advisories Dashboard
  • Snyk