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

Update amazon to use the platform_family of amazon not RHEL #971

Merged
merged 1 commit into from
Apr 3, 2017

Conversation

lamont-granquist
Copy link
Contributor

i think we've finally decided not to move amazon to fedora in #960

i still think everyone is wrong, but i got my fedora_derived?
chef-sugar helper so its a mute point now...

chef-boneyard/chef-rfc#252

i think we've finally decided not to move amazon to fedora in #960

i still think everyone is wrong, but i got my `fedora_derived?`
chef-sugar helper so its a mute point now...

chef-boneyard/chef-rfc#252

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
@lamont-granquist
Copy link
Contributor Author

Grammar trolling in commit messages is about the best I can do for 4/1

@lamont-granquist
Copy link
Contributor Author

@chef/client-core agreed?

and it looks like faraday is screwed, but this should be green.

@thommay
Copy link
Contributor

thommay commented Apr 3, 2017

i refuse to merge this until you correct mute to moot. But otherwise 👍

@lamont-granquist
Copy link
Contributor Author

Burn

@lamont-granquist lamont-granquist merged commit 96ac18a into master Apr 3, 2017
@lamont-granquist lamont-granquist deleted the lcg/amazon-platform-family branch April 3, 2017 16:19
@tas50 tas50 changed the title add amazon platform_family Update amazon to use the platform_family of amazon not RHEL Apr 11, 2017
@tas50 tas50 added the Type: Enhancement Adds new functionality. label Apr 11, 2017
svanzoest added a commit to sous-chefs/apache2 that referenced this pull request Apr 11, 2017
svanzoest added a commit to sous-chefs/apache2 that referenced this pull request Apr 12, 2017
support amazon as a platform_family as per chef/ohai#971
cwjohnston pushed a commit to cwjohnston/sensu-chef that referenced this pull request May 26, 2017
Per chef/ohai#971 Amazon Linux is detected as
platform_family "amazon" starting with Ohai 13.0

This should fix one source of issues reported by Amazon Linux users
under Chef 13+

Closes sensu#558
cwjohnston pushed a commit to cwjohnston/sensu-chef that referenced this pull request Jun 14, 2017
Per chef/ohai#971 Amazon Linux is detected as
platform_family "amazon" starting with Ohai 13.0

This should fix one source of issues reported by Amazon Linux users
under Chef 13+

Closes sensu#558
@et304383
Copy link

Just ran into this trying out Chef 13.

Amazon Linux is based off CentOS 6, hence still running sysvinit and using epel 6.

Is there a documented discussion as to why this change was necessary?

This change pretty much broke every cookbook under the sun that was relying on it being under the "rhel" identifier (if moving to Chef 13).

@coderanger
Copy link
Contributor

If anyone has further questions on this change, feel free to ask in Slack or the mailing list but this issue is not the place.

@chef chef locked and limited conversation to collaborators Jun 17, 2017
@lamont-granquist
Copy link
Contributor Author

It was absolutely wrong to have it in the 'rhel' family -- everyone else in that family tracks the upstream and platform_versions are consistent such that "rhel 6.3 = centos 6.3 = oracle 6.3 = scientific 6.3".

amazon does not track a consistent release of rhel and it used to be rhel5 userland + updated rhel6 kernels. then it largely shifted to rhel6 for a long time which somewhat masked the fact that it wasn't really rhel -- although platform_version comparisons to detect RHEL6 or RHEL7 would often go completely haywire. now amazon linux is deviating from rhel7 in major ways and again its no longer correctly that its rhel6 or rhel7.

i argued that it should be changed to a platform_family of 'fedora' so that code which had a fedora check and only did the latest stuff would tend to still work correctly on amazon, which would have been less disruptive (and i'd argue makes platform_family as a concept more useful) but was pretty much the lone voice in that argument:

there were also public discussions in the chef community meetings (the thursday meetings) on several different occasions over this.

the way we wound up here was literally a 2 year long public argument discussion.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Enhancement Adds new functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants