assets.md

OpenTelemetry managed assets

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

Credential Storage

• 1Password Teams
  • Team account: https://opentelemetry.1password.com/
  • https://github.com/1Password/1password-teams-open-source#opentelemetry
  • PR: 1Password/for-open-source#364
  • Admins: @open-telemetry/governance-committee

Community Resource Accounts

Actuated

Link: https://actuated.dev/blog/arm-ci-cncf-ampere Doc: Using Actuated

• GitHub App available for repositories to get ARM64 Actions runners.
• Admin: N/A. The program is managed by the CNCF and Actuated. The only available admin task is to add the GitHub App to a repository.

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

Link: https://console.equinix.com/projects/6f1c9af6-0470-42da-8f22-59d0df245f6b

• Reserved bare metal machines for the community to run performance tests and other assets on
• Admin: Juraci Paixão Kröhling @jpkrohling and OTel TC via the mailing list address

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.

Artifact repositories

NuGet OpenTelemetry organization

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

• All .NET SIG maintainers are administrators of this organization.
• Organization e-mail (cncf-opentelemetry-net-maintainers@lists.cncf.io) is owned by CNCF.

MyGet OpenTelemetryCNCF account

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

• registered under the service account (cncf-opentelemetry-net-maintainers@lists.cncf.io).
• 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

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:

• @bogdandrutu
• @carlosalberto
• @jack-berg
• @trask

PyPI

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

• Owner: @codeboten

Communication channels

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

• Owners: @open-telemetry/governance-committee
• Members: SIG maintainers and individuals appointed by maintainers

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 cncf-opentelemetry-net-maintainers@lists.cncf.io

• 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 cncf-opentelemetry-ruby@lists.cncf.io

• Used as a service account e-mail for Ruby SIG. All Ruby SIG maintainers @open-telemetry/ruby-maintainers are moderators of this list. Owned by CNCF.
• Moderators: add member.

Mailing list cncf-opentelemetry-governance@lists.cncf.io

• 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

• Accounts
  • cncf-opentelemetry@cncf.io
  • cncf-opentelemetry-meeting-1@cncf.io
  • cncf-opentelemetry-meeting-2@cncf.io
  • cncf-opentelemetry-meeting-3@cncf.io
  • cncf-opentelemetry-meeting-4@cncf.io
• Admins: @open-telemetry/governance-committee
• Note: while the account passwords are available in the Governance Committee 1Password, logging in from a new IP address will require being a member https://lists.cncf.io/g/cncf-otel-zoomadmins with at least moderator rights so you can see pending (unapproved) messages and retrieve the One-Time Password that is sent when you log in. To join https://lists.cncf.io/g/cncf-otel-zoomadmins, go to that URL and click "Apply For Membership In This Group". Then ask in the #opentelemetry-gc for someone to approve your membership and then to give you owner rights.

Zapier account

Link: https://zapier.com

• Used to automatically add links to Zoom meeting recordings to a publicly viewable Google spreadsheet
• Used to automatically add repo maintainers to new security incidents
• Admins: @open-telemetry/governance-committee (GitHub password is available in the OpenTelemetry Governance 1Password)

Google Workspace accounts

• Accounts
  • admin@opentelemetry.io
• Admins: @open-telemetry/governance-committee
• Used to manage the OpenTelemetry community calendar
• Used to manage the Google Custom Search for opentelemetry.io/search

Google account for cncf-opentelemetry-governance@lists.cncf.io

• Admins: @open-telemetry/governance-committee
• Used for community Google Docs
• Used to manage Zoom

Bot accounts

Easy CLA

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

For support:

• Check the EasyCLA status page
• Open an OpenTelemetry community issue
• Ask in the #easycla Slack channel
• Open an EasyCLA Jira ticket

Docker Hub

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

OpenTelemetry Bot

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

• Admins: @open-telemetry/technical-committee (GitHub password and associated 2FA for the @opentelemetrybot account are available in the Technical Committee 1Password)

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 107717825+opentelemetrybot@users.noreply.github.com
   

   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 public_repo 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.

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