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

Use variables to define workshop specific values #80

Closed
Sabryr opened this issue Feb 1, 2019 · 3 comments
Closed

Use variables to define workshop specific values #80

Sabryr opened this issue Feb 1, 2019 · 3 comments

Comments

@Sabryr
Copy link
Contributor

Sabryr commented Feb 1, 2019

This is to use the _config.yml (as in hpc-in-a-day lesson) to define, for example queing system used
e.g from hpc-in-a day

this is the scheduler to be used for the workshop
possible values: lsf, slurm, pbs
workshop_scheduler: "slurm"
workshop_login_host: "cray-1"
workshop_shared_fast_filesystem: "/fastfs"

@aturner-epcc is working on a full solution for this. But due to time constraint I will fix the first few lessons (as it is easier than manually editing from my part) on my folk.

@psteinb
Copy link
Contributor

psteinb commented Feb 4, 2019

As mentioned in #79, this is tackled in #73 . I propose to review this one and merge it. Feel free to suggest alternatives so we can start a discussion on them. I am a bit irritated by this issue and some comments on #79. Does this all mean, that people don't like #73? If so, could you please comment on it directly. Otherwise, I'd suggest to close this issue and sort out with @aturner-epcc and others who works on what. From what I read, I hope we are not working at the same thing at the same time.

@Sabryr
Copy link
Contributor Author

Sabryr commented Feb 4, 2019

Sorry my bad, I overlooked "Rewrite of cluster lesson #73" as it is so broad. Git grep show that you have the workshop variables in it as well-. Hope you could push this PR through soon

@Sabryr Sabryr closed this as completed Feb 4, 2019
@psteinb
Copy link
Contributor

psteinb commented Feb 4, 2019 via email

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

2 participants