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

Create missing Ansible playbooks - Mac OS #212

Closed
bblondin opened this issue Feb 13, 2018 · 17 comments
Closed

Create missing Ansible playbooks - Mac OS #212

bblondin opened this issue Feb 13, 2018 · 17 comments
Assignees
Milestone

Comments

@bblondin
Copy link
Contributor

Ref: #6

We currently don't have a playbooks for Mac OS

Its more important to get a playbook working on this platform first then we can work on incorporating it into the greater main playbooks

@gdams
Copy link
Member

gdams commented Feb 13, 2018

I'm happy to work on this, I might request an extra mac to test the playbook on.

@jdekonin
Copy link
Contributor

Not that the entire playbook is of use. But I found homebrew and a very few extras enabled me to compile on my macbook pro. "Testing the Playbook" section might be of value.

https://github.com/geerlingguy/mac-dev-playbook

@sxa
Copy link
Member

sxa commented Nov 19, 2018

From @jdekonin Please make sure curl is also included in the playbook as per #404.

@sxa sxa added this to the 2018 November B milestone Nov 19, 2018
@jdekonin
Copy link
Contributor

As notes in eclipse-openj9/openj9#3790 when running openjdk-tests there setup requirements on the system.

vi /etc/sysctl.conf
kern.sysv.shmmax=314572800
kern.sysv.shmall=76800

@sxa
Copy link
Member

sxa commented Nov 29, 2018

@cwillhelm Are you able to progress this? Any current blockers?

@cwillhelm
Copy link
Contributor

cwillhelm commented Nov 29, 2018

No current blockers other than some stuff that has to be done from the GUI. It's possible to script it using something like pyautogui, but that's kind of a hacky workaround. I also need a Mac for testing, unfortunately the one we are using is OSX 10.10, and can't be upgraded to 10.11 or beyond. Not sure how big of an impact that will have.

It's still a work in progress though, I'm putting everything in a single playbook file first, and will separate out the other aspects (like CPAN, Freemarker, etc) once it's confirmed to be working.

@sxa
Copy link
Member

sxa commented Nov 29, 2018

Out existing machines at adoptopenjdk are all 10.10 so that version is fine by me for the purposes of this ;-)
Which things need to be installed via the GUI?

Please provide updates in this work item since sharing a log of what we've tried and got working / failed to get working is always useful. We do of course have the work in https://github.com/AdoptOpenJDK/openjdk-infrastructure/pull/219/files to base from.

@cwillhelm
Copy link
Contributor

For the GUI stuff,

System Preferences -> Sharing

    Turn On Screen Sharing, allow access for Adminstrators (default)
    Turn On Remote Login, allow access for Adminstrators (default)

System Preferences -> Sharing

    Turn On Remote Login, allow access for jenkins

test it out
ssh jenkins@machine name

I'll keep you posted about what has and hasn't worked soon, just making a fresh image of this mac for testing.

@cwillhelm
Copy link
Contributor

Very alpha version has been written, hasn't been tested yet. Will throw it towards a machine when I get the chance.

@sxa
Copy link
Member

sxa commented Dec 3, 2018

@cwillhelm Can you create a PR with what you've got, prefixed with [WIP] so we know it's incomplete? Would be best to have it in github even if it's not yet complete :-)

@cwillhelm
Copy link
Contributor

cwillhelm commented Dec 3, 2018

@sxa555 done, very rough -- it's currently about half functional (figuring out some HTTPS issues @ line 268)

@cwillhelm
Copy link
Contributor

https://blog.bearandgiraffe.com/ansible-github-and-a-failed-to-validate-the-ssl-certificate-story-a8a10ea17512

There's some weird issues specifically related to Ansible, Git, Python, and MacOS that causes certificates issues with Github (since they reject TLS 1.1 connections). Based on my findings and these fixes (which apply to MacOS 10.12+) we may have to mirror the jdk files to a different repository in order to properly download them on MacOS 10.10. I'm going to do some investigation to see if this does in fact work on 10.12+, but in the meantime that's the current blocker on where we are at with the playbook.

I tried the solutions in the above link, as well as some other ones on the internet and did not have any success.

@sxa
Copy link
Member

sxa commented Dec 5, 2018

Hmmm that surprises me a little since the build machines at adoptopenjdk are all 10.10 and they do currently manage to pull frmo git without problems.

@jdekonin
Copy link
Contributor

eclipse-openj9/openj9#4375 requests changes to the requirements on an OSX install. Setting umask to 0002 and /etc/sysctl.conf values for
kern.sysv.shmmax=125839605760
kern.sysv.shmall=30722560

I attempted to use launchctl config system umask 002 or launchctl config user umask 002 as per apple documentation, but that didn't work for me. I made the change within the jenkins user .bashrc umask 0002 which did work.

@jdekonin
Copy link
Contributor

Taken from discussion with @cwillhelm, pmset -a sleep 0 might be of use in stopping the mac from going to sleep and becoming disabled in jenkins.

@sxa sxa removed this from the 2018 November B milestone Mar 7, 2019
@sxa sxa added this to the Backlog milestone Mar 7, 2019
@sxa
Copy link
Member

sxa commented Mar 8, 2019

@gdams Ref the work you did to set up a 10.12 box for #711, what needed to be done manually over and above the playbook execution? I know you mentioned the extra boot JDK but I'm guessing there was probably more manual steps required? Would be good to have the current state documented here.

@gdams
Copy link
Member

gdams commented Jul 30, 2019

playbook merged

@gdams gdams closed this as completed Jul 30, 2019
@karianna karianna modified the milestones: Backlog, July 2019 Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants