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

promote EL7 as the recommended platform #4384

Closed
donsizemore opened this issue Dec 14, 2017 · 4 comments
Closed

promote EL7 as the recommended platform #4384

donsizemore opened this issue Dec 14, 2017 · 4 comments

Comments

@donsizemore
Copy link
Contributor

donsizemore commented Dec 14, 2017

Per @pdurbin and @landreev in commit 10b302b on #4157

in our repo there are a number of places where we reference el6: Vagrant files, Docker files, the Installation Guide, and probably other stuff I'm not thinking about. A future pull request would switch all of it from el6 to el7." — @pdurbin

We are going to 7 on the new production servers, on AWS. Whether upgrading is worth the trouble on our local test servers... yeah, probably. It was a bit of a pain to figure out how to install these packages on CentOS 6, so that Kevin could test it... because everything is so old there. We should promote 7 as the recommended platform. — @landreev

@pdurbin
Copy link
Member

pdurbin commented Dec 20, 2017

@donsizemore and I just talked about his pull request (#4385) at http://irclog.iq.harvard.edu/dataverse/2017-12-20#i_61662 and in summary I think he's done (thanks!) but I'd like to take a swing at tweaking the guides to emphasize RHEL7/CentOS7 (el7 for short) over RHEL6/CentOS6 (el6). I also may take a quick look at upgrading the Minishift images from el6 to el7.

@pdurbin pdurbin assigned pdurbin and unassigned donsizemore Dec 20, 2017
@pdurbin
Copy link
Member

pdurbin commented Dec 21, 2017

I also may take a quick look at upgrading the Minishift images from el6 to el7.

@pameyer pointed out to me that these images are already using el7. Great!

That means at this point this issue should be a review of the Installation Guide.

pdurbin added a commit to donsizemore/dataverse that referenced this issue Dec 21, 2017
pdurbin added a commit to donsizemore/dataverse that referenced this issue Dec 21, 2017
pdurbin added a commit to donsizemore/dataverse that referenced this issue Dec 21, 2017
pdurbin added a commit to donsizemore/dataverse that referenced this issue Dec 21, 2017
@pdurbin
Copy link
Member

pdurbin commented Dec 21, 2017

I made my main update to the guides in 98ad217 and am moving this issue to code review so @landreev @dlmurphy and anyone else who may be interested can take a look.

@donsizemore is going to take a look into getting vagrant destroy working again (as discussed at http://irclog.iq.harvard.edu/dataverse/2017-12-21#i_61766 ) but I'm ok with the pull request being merged as-is.

@pdurbin
Copy link
Member

pdurbin commented Jan 3, 2018

@donsizemore we discussed this issue in standup this morning and @landreev is happy with the changes that have been made to the docs (especially with regard to the version of R for TwoRavens) so we moved it to QA. I'm not too worried about the vagrant destroy thing since I documented a workaround in the Vagrantfile. If you're really itching to work on pull request #4385 some more please get in touch before pushing any commits. Thanks!

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

No branches or pull requests

5 participants