Actions
Bug #16876
closed
AWS dev cluster
Story points:
-
Description
Should:
- be created in the same AWS account as pirca/jutro
- isolated VPC
- initially, have the same VM sizes as pirca
- point to Arvados' dev repo, same versions as ce8i5
- have ce8i5 as its LoginCluster
Updated by Peter Amstutz over 3 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 3 years ago
- Status changed from In Progress to New
- Description updated (diff)
Updated by Javier Bértoli over 3 years ago
- Status changed from New to In Progress
- Description updated (diff)
Updated by Javier Bértoli over 3 years ago
- % Done changed from 0 to 70
- Added the instances through terraform, commits 6f25ba4..7f1e32e@terraform
- Added the corehost entries for DNS
- Added the google oauth entries
- Added general setup through saltstack, commit 6caea25..3b33aab@saltstack
Still pending federation setup on ce8i5 and surely some tweaking on tordo
Updated by Javier Bértoli over 3 years ago
Tweaked initial setup (commits 3b33aab..29be30b@saltstack):
- Re-enabled Google's login to get an initial user
- Added the correct shell's VM id otherwise,
AutoSetupNewUsersWithVmUUIDwon't work (du'h!)
Updated by Javier Bértoli over 3 years ago
- % Done changed from 70 to 90
Federation is up and running (commit 23a29b2..103ba1c@saltstack)
Setting up compute vm.
Updated by Javier Bértoli over 3 years ago
- Added a jenkins' diagnostic job
- Added a jenkins' Production Ready Testing job
- Run an initial job that failed
Updated by Javier Bértoli over 3 years ago
- % Done changed from 90 to 100
- Status changed from In Progress to Resolved
The failure was caused by the bug described in this ticket. Peter copied the collection to the cluster, re-run the test and it passed.
Actions