Versions Compared

Old Version 1

changes.mady.by.user Ashley Griffin

Saved on

compared with

New Version 2

changes.mady.by.user Ashley Griffin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


  1. Log into the AWS instance

  2. Running free -h  will show no active swap running
  3. Use df -h  to check available space on the hard drive
  4. Create the SWAP file with 64G by running sudo fallocate -l 64G /swapfile 
  5. You can verify the size of the swapfile using ls -lh /swapfile 

  6. Next we will enable the swapfile using the following step:

    Code Block
    sudo chmod 600 /swapfile
ls -lh /swapfile
sudo mkswap /swapfile      # mark the file as swap space
sudo swapon /swapfile      # enable
sudo swapon --show         # verify


  7. Finally, make the swap file permanent:

    Code Block
    sudo cp /etc/fstab /etc/fstab.bak
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
cat /etc/fstab        # verify


Set up the CI runner:

...

  1. Create a new self-hosted runner at https://github.com/JCSDA/spack-stack/actions/runners?tab=self-hosted. You can use the default runner group, but pick a name that helps identify the purpose of the runner,  such as "ubuntu-ci-c6a-x86_64". Keep the labels the same as the name. Note, the security token will change with each runner. 
  2. Document the new self hosted runner in a txt file at https://github.com/JCSDA-internal/jedi-tools/tree/develop/CI-tools/selfhosted
  3. Add a new spack-stack workflow file in https://github.com/JCSDA/spack-stack/tree/develop/.github/workflows. It is easier to build off of an existing workflow file, but make sure your architecture is consistent and the runner name gets updated at multiple locations inside the yaml.