Open radiantone opened 3 years ago
The CD server (gitlab) needs to have ssh privilages to the host balsam services are running on, which isn't going to be possible from github actions). We won't be able to do continuous deployment from public github repo I think.
This is for the central balsam API services VM/Host. Not for Balsam packages.
The central services are not running in ALCF, so the ALCF Gitlab server does not get us any closer
Ohhhhhhh. Gotcha.
Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Michael (Misha) Salim @.> Sent: Sunday, October 31, 2021 12:33:00 PM To: argonne-lcf/balsam @.> Cc: Customer Support @.>; Assign @.> Subject: Re: [argonne-lcf/balsam] Test ansible playbook to perform rolling update on balsam services from gitlab CD (Issue #112)
The central services are not running in ALCF, so the ALCF Gitlab server does not get us any closer
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://github.com/argonne-lcf/balsam/issues/112#issuecomment-955745934, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGCTZ2NMG4HGVMNIT27BOVTUJVVTZANCNFSM5HBNKQBA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Just to clarify, balsam services should be HPC-site independent and therefore CD can be coordinated from this repository (i.e. Github actions) rather than a Gitlab server.
We'll only use Gitlab CI/CD for the tests that need to run behind a particular facility's firewall (e.g. testing Balsam on ALCF-Theta)