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

image-index: remove platform.features field #672

Merged
merged 1 commit into from
May 19, 2017

Conversation

stevvooe
Copy link
Contributor

@stevvooe stevvooe commented May 11, 2017

While the intended use of the platform.features field was to express
the availability of hardware instructions on CPUs, the practicality of
expressing and implementing such a standard has been called into
question. Much of the functionality is usually hidden deep within kernel
code or is defined by hardware vendors in ways that will make the field
unusable without future additions. Applications that can make use of such
field will likely have other requirements on top of this field that are
specific to a deployment.

In that regard, it is best to remove this field and defer to hardware to
make the decision about what can be run.

Signed-off-by: Stephen J Day [email protected]

Closes #622

@AkihiroSuda
Copy link
Member

Can we still reserve the field name and mark it MUST NOT BE USED?

@stevvooe
Copy link
Contributor Author

Can we still reserve the field name and mark it MUST NOT BE USED?

Yes.

@stevvooe
Copy link
Contributor Author

@AkihiroSuda @vbatts Updated to be a reserved property.

@vbatts
Copy link
Member

vbatts commented May 15, 2017

LGTM

Approved with PullApprove

@stevvooe
Copy link
Contributor Author

@opencontainers/image-spec-maintainers PTAL

@philips
Copy link
Contributor

philips commented May 17, 2017

LGTM

Approved with PullApprove

@philips
Copy link
Contributor

philips commented May 17, 2017

@stevvooe conflicts :(

@stevvooe
Copy link
Contributor Author

@philips BAH!!! So close. Wait right there...

While the intended use of the `platform.features` field was to express
the availability of hardware instructions on CPUs, the practicality of
expressing and implementing such a standard has been called into
question. Much of the functionality is usually hidden deep within kernel
code or is defined by hardware vendors in ways that will make the field
unusable without future additions. Applications that can make use of such
field will likely have other requirements on top of this field that are
specific to a deployment.

In that regard, it is best to remove this field and defer to hardware to
make the decision about what can be run.

Signed-off-by: Stephen J Day <[email protected]>
@stevvooe
Copy link
Contributor Author

@vbatts @philips PTAL

@vbatts
Copy link
Member

vbatts commented May 18, 2017

LGTM

Approved with PullApprove

@vbatts
Copy link
Member

vbatts commented May 19, 2017

@philips review please

@philips
Copy link
Contributor

philips commented May 19, 2017

LGTM

Approved with PullApprove

@vbatts vbatts merged commit 5ebcc54 into opencontainers:master May 19, 2017
@stevvooe stevvooe deleted the remove-features-field branch May 19, 2017 18:38
@stevvooe
Copy link
Contributor Author

Thanks, folks!

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.

5 participants