Conversation
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/3986/Result ❌ FAILUREBIRDHOUSE_DEPLOY_BRANCH : magpie-networking DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-91.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/618/NOTEBOOK TEST RESULTS |
| export MAGPIE_NETWORK_PEM_FILES=key.pem # These files must be relative paths from the MAGPIE_NETWORK_PEM_DIR directory | ||
| export MAGPIE_NETWORK_PEM_PASSWORDS= |
There was a problem hiding this comment.
Looks like the must be : separated from below parsing. I assume any path is remapped as is with the same hierarchy? Maybe a small comment/example can help for this.
For the passwords case, I assume that "no-password" files would need ::<pwd>: for example if the 3rd out of 4 files provided needs a password? Similarly, an example comment to help users configure it correctly.
| # https://pavics-magpie.readthedocs.io/en/latest/configuration.html#network-mode-settings | ||
| export MAGPIE_NETWORK_PEM_DIR='${BIRDHOUSE_DATA_PERSIST_ROOT}/magpie_pem' | ||
| export MAGPIE_NETWORK_ENABLED=false # Note: by default network mode is off (false) | ||
| export MAGPIE_NETWORK_INSTANCE_NAME= # Note: this must be a unique name in the network so no default is set |
There was a problem hiding this comment.
Could we do something, like a pre-compose... file, that verifies that it is set if enabled, logs an error & aborts if detected?
| [//]: # (list changes here, using '-' for each new entry, remove this when items are added) | ||
| ## Changes | ||
|
|
||
| - Update `magpie` to version 5.0.0 |
There was a problem hiding this comment.
Since it is a major, a note is warranted to indicate that it does not impact existing DB/migration stuff. It only adds extra tables if network mode is enabled, but fully backward compatible.
Expecting @tlvu will have this question 😉
There was a problem hiding this comment.
It only adds extra tables if network mode is enabled, but fully backward compatible.
Confirmed fully backward compatible, only DB migration I see:
[alembic.runtime.migration] Running upgrade 5e5acc33adce -> 2cfe144538e8, Add Network_Tokens Table`)
Now that I have a test machine with Magpie 5, how can I try this network mode with you guys?
There was a problem hiding this comment.
I guess I can spin up another PAVICS instance and try network mode with myself but I don't enough juice :(
I only have 2 dev VM and the other VM is stuck testing the Jupyter config refactoring :(
There was a problem hiding this comment.
Is your instance accessible from the web?
We'll have to exchange PEM keys and register each other's instances accordingly.
There was a problem hiding this comment.
Is your instance accessible from the web?
Yes
We'll have to exchange PEM keys and register each other's instances accordingly.
Ready when you guys are ready.
There was a problem hiding this comment.
My test instances aren't available outside my network. If you want to test this before approving this PR I can send you a minimal working example that should be testable on your VMs. If you give me a few days I can send you that separately so you can test it out yourself.
There was a problem hiding this comment.
Since this network mode is not enabled by default, I assume there are no risk of regressions. I was simply curious how this network mode actually works and whether the documentation is complete. I can approve as-is and we can test later if that is more convenient for you guys.
There was a problem hiding this comment.
No worries. If you want to test it out a bit I've added a proposed example here Ouranosinc/Magpie#648 that will let you test out the network mode locally.
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/3989/Result ❌ FAILUREBIRDHOUSE_DEPLOY_BRANCH : magpie-networking DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-91.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/620/NOTEBOOK TEST RESULTS |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/4000/Result 🆘 ABORTEDBIRDHOUSE_DEPLOY_BRANCH : magpie-networking DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-133.rdext.crim.ca
|
|
Version https://github.com/Ouranosinc/Magpie/tree/5.0.1 to be considered. |
Overview
This update to Magpie introduces network mode.
This is disabled by default to ensure backwards compatibility but can be enabled by setting
MAGPIE_NETWORK_ENABLED=truein your local environment file.Note that enabling network mode also requires setting
MAGPIE_NETWORK_INSTANCE_NAMEto a unique name within the network.This change also introduces the ability to set all configuration options for Magpie's network mode as environment variables in the local environment file.
Note that all of these configuration options will be ignored if
MAGPIE_NETWORK_ENABLEDisfalse.Changes
Non-breaking changes
Breaking changes
Related Issue / Discussion
Additional Information
CI Operations
birdhouse_daccs_configs_branch: master
birdhouse_skip_ci: false