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

Prepare AiiDAlab deployment on Azure with AiiDA 2.x and test it #419

Open
giovannipizzi opened this issue Aug 29, 2022 · 7 comments
Open
Labels
priority/mission-critical Needs to be fixed (before next event)

Comments

@giovannipizzi
Copy link
Member

@csadorf @unkcpz @superstar54 @chrisjsewell @mbercx

@giovannipizzi giovannipizzi added this to the Tutorial Oct 2022 milestone Aug 29, 2022
@csadorf csadorf self-assigned this Aug 30, 2022
@csadorf csadorf added the priority/mission-critical Needs to be fixed (before next event) label Aug 30, 2022
@csadorf
Copy link
Collaborator

csadorf commented Sep 16, 2022

I have prepared a test deployment at https://aiida-tutorial-2022-test.aiidalab.xyz based on the revised docker stack with Python 3.9.4 and AiiDA 2.0.0.

@mbercx
Copy link
Member

mbercx commented Sep 26, 2022

With @csadorf's help, I've adapted the docker stack to our needs for the tutorial (Installing QE, aiida-quantumespresso, ...), and have updated the versions to the latest releases (see email for link). This should be close to the final deployment we want to use for the tutorial. For the testing on Azure, I've made the following assignments based on the presenters of the corresponding sessions in the schedule:

If you're running Quantum ESPRESSO for your sections, you still need to set up the pw.x code:

verdi code setup --label pw --computer localhost --remote-abs-path /opt/conda/bin/pw.x --input-plugin quantumespresso.pw --non-interactive

And install the SSSP efficiency pseudopotential family:

aiida-pseudo install sssp

Additional Notes:

@unkcpz
Copy link
Member

unkcpz commented Sep 27, 2022

It might be an issue that when the first time starts the AiiDAlab server, I encountered a timeout and the server failed to start error. I have to refresh to relaunch the server. If there is an option to increase the timeout might be helpful. @csadorf @mbercx

@mbercx
Copy link
Member

mbercx commented Sep 27, 2022

Thanks @unkcpz for letting us know! I'll adapt the timeout in the terraform setup.

@csadorf just to be sure, the value to be adapted is the startTimeout here, right?

singleuser:
[...]
  memory:
    limit: 4G
    guarantee: 2G
  cpu:
    limit: 3.0
    guarantee: 1.0
  startTimeout: 300

@csadorf
Copy link
Collaborator

csadorf commented Sep 27, 2022

Thanks @unkcpz for letting us know! I'll adapt the timeout in the terraform setup.

@csadorf just to be sure, the value to be adapted is the startTimeout here, right?

Yes, I believe that should be sufficient. I'm just a bit surprised that this has not been an issue during your tests.

@mbercx
Copy link
Member

mbercx commented Sep 27, 2022

I'm just a bit surprised that this has not been an issue during your tests.

Yeah, strange that the issue only pops up now. The timeout is currently at 120s, maybe @unkcpz was just unlucky. 😅

I'll update the deployment later tonight, after I'm done with testing the basic workflows section.

@ramirezfranciscof
Copy link
Member

* [ ]  Writing workflows - [Basics](https://aiida-tutorials.readthedocs.io/en/tutorial-2022-intro/sections/writing_workflows/index.html): I'll take care of these (Up to and including Debugging)

* [ ]  Writing workflows - [Advanced](https://aiida-tutorials.readthedocs.io/en/tutorial-2022-intro/sections/writing_workflows/index.html): @ramirezfranciscof can you test from the Real-world example?

Donzo #439. Actually, I didn't notice the difference you pointed out there between up to debugging / after debuggin, so I just went through all the workflow section, sorry! I hope I didn't overstep on what you were checking @mbercx .

@csadorf csadorf removed their assignment Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/mission-critical Needs to be fixed (before next event)
Projects
None yet
Development

No branches or pull requests

5 participants