Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid using "infrastructure" terminology for all cloud #1530

Merged
merged 6 commits into from
Mar 22, 2021
Merged

Avoid using "infrastructure" terminology for all cloud #1530

merged 6 commits into from
Mar 22, 2021

Conversation

rakyll
Copy link
Contributor

@rakyll rakyll commented Mar 10, 2021

Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
terminology because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.

Renaming "infrastructure_service" to "platform" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.

Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call

Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.

Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
@rakyll
Copy link
Contributor Author

rakyll commented Mar 11, 2021

PTAL

@@ -42,7 +42,7 @@ groups:
note: >
Availability zones are called "zones" on Google Cloud.
examples: ['us-east-1c']
- id: infrastructure_service
- id: platform
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only hits I get on google for "Cloud platform" is GCP as a whole...

@carlosalberto
Copy link
Contributor

Ping @rakyll (it looks there are a pair of unaddressed comments)

@carlosalberto carlosalberto merged commit 2d8bdf2 into open-telemetry:main Mar 22, 2021
jrcamp added a commit to jrcamp/opentelemetry-collector that referenced this pull request Mar 25, 2021
cloud.infrastructure_service -> cloud.platform
cloud.zone -> cloud.availability_zone

These changes were made in:

open-telemetry/opentelemetry-specification#1495
open-telemetry/opentelemetry-specification#1530

Will make changes in contrib next.
jrcamp added a commit to jrcamp/opentelemetry-collector that referenced this pull request Mar 25, 2021
cloud.infrastructure_service -> cloud.platform
cloud.zone -> cloud.availability_zone

These changes were made in:

open-telemetry/opentelemetry-specification#1495
open-telemetry/opentelemetry-specification#1530

Will make changes in contrib next.
jrcamp added a commit to jrcamp/opentelemetry-collector that referenced this pull request Mar 25, 2021
cloud.infrastructure_service -> cloud.platform
cloud.zone -> cloud.availability_zone

These changes were made in:

open-telemetry/opentelemetry-specification#1495
open-telemetry/opentelemetry-specification#1530

Will make changes in contrib next.
bogdandrutu pushed a commit to open-telemetry/opentelemetry-collector that referenced this pull request Mar 25, 2021
* Updates for cloud semantic conventions

cloud.infrastructure_service -> cloud.platform
cloud.zone -> cloud.availability_zone

These changes were made in:

open-telemetry/opentelemetry-specification#1495
open-telemetry/opentelemetry-specification#1530

Will make changes in contrib next.

* fix oc conversion
ThomsonTan pushed a commit to ThomsonTan/opentelemetry-specification that referenced this pull request Mar 30, 2021
…y#1530)

* Avoid using "infrastructure" terminology for all cloud

Infrastructure in cloud has a specific connotation for concepts
explained in Infrastructure-as-a-Service (IaaS). Avoid this
termilogy because it's exclusive of some other services/platforms
that is represented by the "cloud" namespace.

Renaming "infrastructure_service" to "service" also due to the new
key length limits we are considering and infrastructure_service is
a lengthy choice.
@pmm-sumo
Copy link
Contributor

BTW, since renaming is essentially a braking change, how should it work for specs v1.0+?

@tigrannajaryan
Copy link
Member

BTW, since renaming is essentially a braking change, how should it work for specs v1.0+?

Hopefully once Telemetry Schemas are implemented renaming can be handled though them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet